Application that crashed: systemsettings Version of the application: 1.0 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-3-686 i686 What I was doing when the application crashed: I was trying to unset the background transparency setting because it was interfering with the visibility of needed text and icons on the screen. Alas, my search was in vain, although now the screen appears to be much better than it was. Mainly, it appears that the crash occurred at the moment that I was searching for anything which referred to background transparency. Thank you very much for your attention to this bug! :) -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [Current thread is 1 (Thread 0xb564e700 (LWP 2365))] Thread 2 (Thread 0xb1d17b70 (LWP 2366)): #0 0xb76e7424 in __kernel_vsyscall () #1 0xb5a1f3d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb62ce864 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb2acfb47 in ?? () from /usr/lib/libxine.so.1 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Thread 1 (Thread 0xb564e700 (LWP 2365)): [KCrash Handler] #6 0xb5dcccf7 in XVisualIDFromVisual () from /usr/lib/libX11.so.6 #7 0xb6af584e in qt_x11_getX11InfoForWindow (xinfo=0x9b5dd54, a=...) at kernel/qwidget_x11.cpp:400 #8 0xb6afa47e in QWidgetPrivate::create_sys (this=0x9b5dc60, window=58935116, initializeWindow=false, destroyOldWindow=true) at kernel/qwidget_x11.cpp:545 #9 0xb6abfc91 in QWidget::create (this=0x9b5e538, window=58935116, initializeWindow=223, destroyOldWindow=<value optimized out>) at kernel/qwidget.cpp:1253 #10 0xada507d6 in KSWidget (this=0x9b5e538, parent=0x93e6ab0, wf=...) at ../../../kcontrol/screensaver/kswidget.cpp:66 #11 0xada409ff in KSSMonitor (this=0x9644b98) at ../../../kcontrol/screensaver/kssmonitor.h:9 #12 KScreenSaver::slotPreviewExited (this=0x9644b98) at ../../../kcontrol/screensaver/scrnsave.cpp:607 #13 0xada40ec8 in KScreenSaver::setMonitor (this=0x9644b98) at ../../../kcontrol/screensaver/scrnsave.cpp:588 #14 0xada42b1c in KScreenSaver::findSavers (this=0x9644b98) at ../../../kcontrol/screensaver/scrnsave.cpp:575 #15 0xada4353b in KScreenSaver::qt_metacall (this=0x9644b98, _c=QMetaObject::InvokeMetaMethod, _id=45, _a=0xbf98c478) at ./scrnsave.moc:98 #16 0xb6587303 in QMetaObject::activate (sender=0x9365330, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112 #17 0xb6587f42 in QMetaObject::activate (sender=0x9365330, m=0xb6663d84, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186 #18 0xb65c2b37 in QTimer::timeout (this=0x9365330) at .moc/release-shared/moc_qtimer.cpp:128 #19 0xb658d65e in QTimer::timerEvent (this=0x9365330, e=0xbf98c91c) at kernel/qtimer.cpp:261 #20 0xb658239f in QObject::event (this=0x9365330, e=0xbf98c91c) at kernel/qobject.cpp:1074 #21 0xb6a67a94 in QApplicationPrivate::notify_helper (this=0x8e61610, receiver=0x9365330, e=0xbf98c91c) at kernel/qapplication.cpp:4065 #22 0xb6a6fbee in QApplication::notify (this=0xbf98cc1c, receiver=0x9365330, e=0xbf98c91c) at kernel/qapplication.cpp:3605 #23 0xb74b2e2a in KApplication::notify (this=0xbf98cc1c, receiver=0x9365330, event=0xbf98c91c) at ../../kdeui/kernel/kapplication.cpp:302 #24 0xb65721eb in QCoreApplication::notifyInternal (this=0xbf98cc1c, receiver=0x9365330, event=0xbf98c91c) at kernel/qcoreapplication.cpp:610 #25 0xb65a0e21 in QCoreApplication::sendEvent (this=0x8e65b34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #26 QTimerInfoList::activateTimers (this=0x8e65b34) at kernel/qeventdispatcher_unix.cpp:580 #27 0xb659d317 in timerSourceDispatch (source=0x8e65b70) at kernel/qeventdispatcher_glib.cpp:184 #28 idleTimerSourceDispatch (source=0x8e65b70) at kernel/qeventdispatcher_glib.cpp:231 #29 0xb5a66b38 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #30 0xb5a6a3d0 in ?? () from /lib/libglib-2.0.so.0 #31 0xb5a6a503 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #32 0xb659d041 in QEventDispatcherGlib::processEvents (this=0x8e44b28, flags=...) at kernel/qeventdispatcher_glib.cpp:407 #33 0xb6b07305 in QGuiEventDispatcherGlib::processEvents (this=0x8e44b28, flags=...) at kernel/qguieventdispatcher_glib.cpp:202 #34 0xb657083a in QEventLoop::processEvents (this=0xbf98cb90, flags=...) at kernel/qeventloop.cpp:149 #35 0xb6570c82 in QEventLoop::exec (this=0xbf98cb90, flags=...) at kernel/qeventloop.cpp:201 #36 0xb65730d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #37 0xb6a67917 in QApplication::exec () at kernel/qapplication.cpp:3525 #38 0x08052e9e in main (argc=5, argv=0xbf98cd44) at ../../../systemsettings/app/main.cpp:51 Reported using DrKonqi
This crash is being tracked at bug 188623. Please state: - X11 and Mesa version (is 3D enabled?) - graphics driver, and version - KWin compositing mode (none, XRender, OpenGL) Regards *** This bug has been marked as a duplicate of bug 188623 ***
On Sunday 04 April 2010 08:31:16 Dario Andres wrote: > https://bugs.kde.org/show_bug.cgi?id=233215 > > > Dario Andres <andresbajotierra@gmail.com> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - Status|UNCONFIRMED |RESOLVED > CC| |andresbajotierra@gmail.com > Resolution| |DUPLICATE > > > > > --- Comment #1 from Dario Andres <andresbajotierra gmail com> 2010-04-04 > 17:31:05 --- This crash is being tracked at bug 188623. > > Please state: > - X11 and Mesa version (is 3D enabled?) > - graphics driver, and version > - KWin compositing mode (none, XRender, OpenGL) > > Regards > > *** This bug has been marked as a duplicate of bug 188623 *** Presuming that the above questions have been directed to me ... 1. X11 version: It's currently 7.5, except for X11-XFS-utils, which is currently running at 7.4. Mesa version: How funny you should ask me that! I honestly haven't a clue as to the Mesa program or what it's intended to do, or how. Aside from a couple of drivers and libraries, it really is not installed at all. So what do I have, then? I have essentially libgl1-mesa-dri and -glx; I have libglu1- mesa; and I have libglw1-mesa. In addition to those, I have the two driver sets mesa-common-dev and mesa-utilities. And that's it. Fortunately, the question of version is very easily answered: it's 7.7-4 for all of the files which I possess. Alas, the question about 3D is not so easily answered: I must surmise that it is not, because my initial reaction to the question was, "Huh????" Similarly, the question of graphics driver seems to be tied up with this whole mess, too. I have a radeon 3200 built into the motherboard; unfortunately, the question of 3D graphics seems to me to be needlessly complex and, therefore, daunting. I've therefore stuck with a 2D driver for years now. I feel that I have the radeon driver installed for this card, because of the fact that it is so clearly marked Radeon, especially in LSPCI -v. Accordingly, I have drivers of version 6.12.6 installed and running at the moment. Similarly, I am drawing a blank concerning the question of compositing. It would certainly help to have access to a definition of the term. Lacking one, every time my machine points out to me that "compositing is temporarily disabled", I have to answer "Duhhhhh-h-h-h-h-h-h-h-h-h-h-h-h-h, how's that again?" I honestly have no clue at all as to what it is or what it's supposed to do for me. However, having started it just for the purpose of writing this message, I can say with some authority that it seems to be running in OpenGL mode. I'm sorry to have to subject you to such a rambling message as this one; yet your simple query touched off a storm of old, forgotten pains, which I would like some help with. So thank you very much for your query and, even more, for listening to an old man's rants. :) N.B.: It seems sometimes to matter, so I wish to mention that I am running this software on an AMD64 which usually seems to be smarter than I am. No problems in that, except that as the human component of the pair of us, I do feel a need to keep abreast of its doings at least to the point of being able to make informed decisions concerning them. Thanks once again! :) Sincerely, Willy Gommel www.wg3.net