[Bug 697983] Re: Click "Deslkop" and systemsettings crashes every time

Jonathan Thomas echidnaman at kubuntu.org
Thu Jun 2 00:32:06 UTC 2011


*** This bug is a duplicate of bug 545257 ***
    https://bugs.launchpad.net/bugs/545257

** This bug has been marked a duplicate of bug 545257
   gnome-screensaver-gl-helper crashed with SIGSEGV in XF86DRIQueryVersion()

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/697983

Title:
  Click "Deslkop" and systemsettings crashes every time

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Binary package hint: systemsettings

  $ lsb_release -rd
  Description:    Ubuntu 10.04.1 LTS
  Release:        10.04

  $ apt-cache policy systemsettings
  systemsettings:
    Installed: 4:4.4.5-0ubuntu1
    Candidate: 4:4.4.5-0ubuntu1
    Version table:
   *** 4:4.4.5-0ubuntu1 0
          500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
          100 /var/lib/dpkg/status
       4:4.4.2-0ubuntu14 0
          500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

  
  I last used KPackageKit to do a full update (selected all and clicked apply) two weeks ago.  Everything was fine. I then went on vacation for two weeks

  This evening, after returning from vacation, I ran another full
  update, and things went very wrong after that.  It seems compositing
  somehow got turned on. (???)  Compositing won't work on my system.
  The result was very ugly.  (eventually I got a message telling me that
  compositing had been turned off, as it was to slow, and things got
  much better after that!)

  So I tried systemssettings -> Look & Feel -> Desktop and it crashed.
  I tried and tried and tried and it crashed every time.  Even after a
  full shutdown and boot.  I tried using the KDE Crash Handler to report
  this, but each time I tried to Install Debug Symbols I got a dialog
  saying "Could not find debug symbol packages for this application."
  So here I am.


  Here is the info I copied from the KDE Crash Handler "Developer
  Information" Tab:

  
  Application: System Settings (systemsettings), signal: Segmentation fault
  [Current thread is 1 (Thread 0x7ffbe5622760 (LWP 2436))]

  Thread 2 (Thread 0x7ffbd61d9700 (LWP 2437)):
  #0  0xffffffffff60017b in ?? ()
  #1  0x00007ffbd61d8aa0 in ?? ()
  #2  0x00007ffff81ff852 in ?? ()
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  Thread 1 (Thread 0x7ffbe5622760 (LWP 2436)):
  [KCrash Handler]
  #5  0x00007ffbd56358be in XF86DRIQueryVersion () from /usr/lib/libGL.so.1
  #6  0x00007ffbd5635a59 in XF86DRIQueryExtension () from /usr/lib/libGL.so.1
  #7  0x00007ffbd563538c in ?? () from /usr/lib/libGL.so.1
  #8  0x00007ffbd5615118 in ?? () from /usr/lib/libGL.so.1
  #9  0x00007ffbd5611531 in ?? () from /usr/lib/libGL.so.1
  #10 0x00007ffbd561170e in glXChooseVisual () from /usr/lib/libGL.so.1
  #11 0x00007ffbc090f70a in KSWidget (this=0x2c42770, parent=<value optimized out>, wf=<value optimized out>) at ../../../kcontrol/screensaver/kswidget.cpp:49
  #12 0x00007ffbc0901c54 in KSSMonitor (this=0x2b3fa80) at ../../../kcontrol/screensaver/kssmonitor.h:9
  #13 KScreenSaver::slotPreviewExited (this=0x2b3fa80) at ../../../kcontrol/screensaver/scrnsave.cpp:505
  #14 0x00007ffbc0904108 in KScreenSaver::findSavers (this=0x2b3fa80) at ../../../kcontrol/screensaver/scrnsave.cpp:473
  #15 0x00007ffbc0904f7c in KScreenSaver::qt_metacall (this=0x2b3fa80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff81053e0) at ./scrnsave.moc:104
  #16 0x00007ffbe32c5e3f in QMetaObject::activate (sender=0x2b3f830, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
  #17 0x00007ffbe32c2a63 in QObject::event (this=0x2b3f830, e=0x7ffff8105b30) at kernel/qobject.cpp:1212
  #18 0x00007ffbe3ea022c in QApplicationPrivate::notify_helper (this=0x2475940, receiver=0x2b3f830, e=0x7ffff8105b30) at kernel/qapplication.cpp:4300
  #19 0x00007ffbe3ea66fb in QApplication::notify (this=0x7ffff8105e80, receiver=0x2b3f830, e=0x7ffff8105b30) at kernel/qapplication.cpp:4183
  #20 0x00007ffbe4baba16 in KApplication::notify (this=0x7ffff8105e80, receiver=0x2b3f830, event=0x7ffff8105b30) at ../../kdeui/kernel/kapplication.cpp:302
  #21 0x00007ffbe32b306c in QCoreApplication::notifyInternal (this=0x7ffff8105e80, receiver=0x2b3f830, event=0x7ffff8105b30) at kernel/qcoreapplication.cpp:704
  #22 0x00007ffbe32dfd42 in QCoreApplication::sendEvent (this=0x246cc20) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
  #23 QTimerInfoList::activateTimers (this=0x246cc20) at kernel/qeventdispatcher_unix.cpp:603
  #24 0x00007ffbe32dc824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
  #25 0x00007ffbdfdb18c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
  #26 0x00007ffbdfdb5748 in ?? () from /lib/libglib-2.0.so.0
  #27 0x00007ffbdfdb58fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
  #28 0x00007ffbe32dc513 in QEventDispatcherGlib::processEvents (this=0x242a770, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
  #29 0x00007ffbe3f5046e in QGuiEventDispatcherGlib::processEvents (this=0x248b220, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
  #30 0x00007ffbe32b1992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
  #31 0x00007ffbe32b1d6c in QEventLoop::exec (this=0x7ffff8105dd0, flags=) at kernel/qeventloop.cpp:201
  #32 0x00007ffbe32b5aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
  #33 0x00000000004110d9 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../systemsettings/app/main.cpp:49




More information about the foundations-bugs mailing list