Summary: | kwin crashes when changing font configuration(OpenGL desktop effects enabled) | ||
---|---|---|---|
Product: | Mesa | Reporter: | Igor Strelnikoff <freiheits> |
Component: | Drivers/DRI/r300 | Assignee: | mesa-dev |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | critical | ||
Priority: | high | CC: | jlp.bugs |
Version: | 7.5 | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=241263 | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
dmesg
Xorg.0.log xsession_errors glxinfo |
Description
Igor Strelnikoff
2010-08-20 11:52:14 UTC
Created attachment 38022 [details]
dmesg
[ 37.416801] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 37.508028] i2c i2c-1: readbytes: ack/nak timeout [ 37.508099] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 38.191083] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 38.267091] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID [ 39.821017] i2c i2c-1: readbytes: ack/nak timeout [ 39.821085] [drm:radeon_dvi_detect] *ERROR* DVI-I-1: probed a monitor but no|invalid EDID Created attachment 38023 [details]
Xorg.0.log
Created attachment 38024 [details]
xsession_errors
Software : - OpenSUSE 11.3 i586 - Linux kernel 2.6.34-desktop (2.6.34) - KDE SC 4.5 final - Mesa 7.8.2 - Xorg server 1.8.0 Created attachment 38025 [details]
glxinfo
(In reply to comment #7) > Application: KWin (kwin), signal: Segmentation fault > [KCrash Handler] > #7 0xb6be327b in ?? () from /usr/lib/libGL.so.1 > #8 0xb6bbc107 in ?? () from /usr/lib/libGL.so.1 Please try and get debugging information for libGL. New crash report Application: KWin (kwin), signal: Segmentation fault [KCrash Handler] #7 0xb6bac27b in dri2DrawableGetMSC (psc=0x80d52e0, pdraw=0x0, ust=0xbfcfb028, msc=0xbfcfb020, sbc=0xbfcfb018) at dri2_glx.c:226 #8 0xb6b85107 in __glXGetVideoSyncSGI (count=0xbfcfb06c) at glxcmds.c:2317 #9 0xb76bb604 in KWin::SceneOpenGL::waitSync (this=0x8155e30) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/scene_opengl.cpp:781 #10 0xb76c8950 in KWin::SceneOpenGL::flushBuffer (this=0x8155e30, mask=8, damage=...) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/scene_opengl.cpp:793 #11 0xb7723c0a in KWin::SceneOpenGL::paint (this=0x8155e30, damage=..., toplevels=...) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/scene_opengl.cpp:761 #12 0xb76fbe24 in KWin::Workspace::performCompositing (this=0x814ed70) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/composite.cpp:454 #13 0xb772d49b in KWin::Workspace::qt_metacall (this=0x814ed70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfcfb35c) at /usr/src/debug/kdebase-workspace-4.5.1/build/kwin/workspace.moc:583 #14 0xb66f296d in QMetaObject::metacall (object=0x814ed70, cl=QMetaObject::InvokeMetaMethod, idx=190, argv=0xbfcfb35c) at kernel/qmetaobject.cpp:237 #15 0xb6702b1c in QMetaObject::activate (sender=0x814f020, m=0xb68265a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3272 #16 0xb6751ef5 in QTimer::timeout (this=0x814f020) at .moc/release-shared/moc_qtimer.cpp:134 #17 0xb67090e6 in QTimer::timerEvent (this=0x814f020, e=0xbfcfb8b0) at kernel/qtimer.cpp:271 #18 0xb67014e4 in QObject::event (this=0x814f020, e=0xbfcfb8b0) at kernel/qobject.cpp:1175 #19 0xb5bed1a4 in QApplicationPrivate::notify_helper (this=0x806d748, receiver=0x814f020, e=0xbfcfb8b0) at kernel/qapplication.cpp:4396 #20 0xb5bf5dd7 in QApplication::notify (this=0xbfcfbbc4, receiver=0x814f020, e=0xbfcfb8b0) at kernel/qapplication.cpp:3798 #21 0xb722f401 in KApplication::notify (this=0xbfcfbbc4, receiver=0x814f020, event=0xbfcfb8b0) at /usr/src/debug/kdelibs-4.5.1/kdeui/kernel/kapplication.cpp:310 #22 0xb7695c8f in KWin::Application::notify (this=0xbfcfbbc4, o=0x814f020, e=0xbfcfb8b0) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/main.cpp:372 #23 0xb66ec12e in QCoreApplication::notifyInternal (this=0xbfcfbbc4, receiver=0x814f020, event=0xbfcfb8b0) at kernel/qcoreapplication.cpp:732 #24 0xb671d4b4 in sendEvent (this=0x806ded0) at kernel/qcoreapplication.h:215 #25 QTimerInfoList::activateTimers (this=0x806ded0) at kernel/qeventdispatcher_unix.cpp:617 #26 0xb671dbfd in QEventDispatcherUNIX::processEvents (this=0x8052b98, flags=...) at kernel/qeventdispatcher_unix.cpp:938 #27 0xb5ca328a in QEventDispatcherX11::processEvents (this=0x8052b98, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #28 0xb66eb40d in QEventLoop::processEvents (this=0xbfcfbb14, flags=...) at kernel/qeventloop.cpp:149 #29 0xb66eb639 in QEventLoop::exec (this=0xbfcfbb14, flags=...) at kernel/qeventloop.cpp:201 #30 0xb66f0090 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #31 0xb5beaed4 in QApplication::exec () at kernel/qapplication.cpp:3672 #32 0xb77359db in kdemain (argc=1, argv=0xbfcfbe14) at /usr/src/debug/kdebase-workspace-4.5.1/kwin/main.cpp:531 #33 0x0804860b in main (argc=1, argv=0xbfcfbe14) at /usr/src/debug/kdebase-workspace-4.5.1/build/kwin/kwin_dummy.cpp:3 >>Application: kwin (4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2))) >>KDE Platform Version: 4.4.85 (KDE 4.4.85 (KDE 4.5 Beta2)) >>Qt Version: 4.7.0 >>Operating System: Linux 2.6.34-020634-generic i686 >>Distribution: Ubuntu 10.04 LTS >>-- Information about the crash: >>- What I was doing when the application crashed: >>I opened System Settings - Color Settings - Colors, and changed the color for >>Active Titlebar Text, and clicked Apply. >>The crash can be reproduced every time. Thread 1 (Thread 0xb3303720 (LWP 3611)): [KCrash Handler] #7 0xb6c719aa in dri2DrawableGetMSC (psc=0x9f5f5d0, pdraw=0x0, ust=0xbf9ce508, msc=0xbf9ce500, sbc=0xbf9ce4f8) at dri2_glx.c:249 #8 0xb6c4b21c in __glXGetVideoSyncSGI (count=0xbf9ce54c) at glxcmds.c:2317 https://bugs.kde.org/show_bug.cgi?id=241263 The classic r300 driver has been abandoned long ago. It was replaced by the Gallium driver r300g. If you have issues with r300g please file a new bug report with component Drivers/Gallium/r300 Thanks. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.