Bug 251176 - screen saver/locker crashes when it starts manually or automatically
Summary: screen saver/locker crashes when it starts manually or automatically
Status: RESOLVED DUPLICATE of bug 234689
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: locker (show other bugs)
Version: 2.0
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-14 04:49 UTC by Benoit Dufresne
Modified: 2010-10-21 02:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benoit Dufresne 2010-09-14 04:49:26 UTC
Application: kscreenlocker (2.0)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.7-server-1mnb x86_64
Distribution: "Mandriva Linux 2010.1"

-- Information about the crash:
As soon as the screen saver starts, it crashes (automatically or by pressing the lock button).  This problem is permanent and appeared recently.  May be related to an recent kernel update and a try to install the proprietary fglrx ATI/AMD driver.  Along with this new problem, the Desktop configuration in the systemsetting crashes permanently.  It is now impossible to modify any setting in the desktop configuration.

The crash can be reproduced every time.

 -- Backtrace:
Application: KDE Screen Locker (kscreenlocker), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f298da40fee in XF86DRIQueryVersion () from /usr/lib64/libGL.so.1
#6  0x00007f298da41189 in XF86DRIQueryExtension () from /usr/lib64/libGL.so.1
#7  0x00007f298da40a9c in ?? () from /usr/lib64/libGL.so.1
#8  0x00007f298da20438 in ?? () from /usr/lib64/libGL.so.1
#9  0x00007f298da1c851 in ?? () from /usr/lib64/libGL.so.1
#10 0x00007f298da1ca2e in glXChooseVisual () from /usr/lib64/libGL.so.1
#11 0x00000000004109a3 in LockProcess::createSaverWindow (this=0x7fff5d14a6b0) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:485
#12 0x0000000000414f04 in LockProcess::startSaver (this=0x7fff5d14a6b0) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:738
#13 0x00000000004152b9 in LockProcess::lock (this=0x1752890) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:285
#14 0x000000000041d102 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/main.cc:154

Reported using DrKonqi
Comment 1 woogin8r 2010-10-02 01:19:30 UTC
I can duplicate this bug on request as well.  I also suspect fglrx, and I share all of the symptoms listed.  Feel free to contact me if you need me to provide some sort of debugging information.  My kernel is 2.6.32-24-generic on Ubuntu 10.04.

Regards.
Comment 2 Benoit Dufresne 2010-10-02 07:02:39 UTC
my kernel is 2.6.33.7-server-2mnb on Mandriva 2010.1.  I tried to remove and re-install the fglrx driver with no improvement. I even tried the ati driver instead. When I click on the desktop configuration icon under the system settings tool, I can see in a split second the desktop configuration window and then it disappears.  I look inside the different output logs but I could not find any useful information.

I suspected OpenGL or Xrender but the 3D effects works fine and simple tool like xclock based on Xrender works as well.

If I start the kscreenlocker from the console I get this message :

KCrash: Application 'kscreenlocker' crashing...
sock_file=/home/bdufresne/.kde4/socket-benflow/kdeinit4__0

and in the KDE crash handler :

Application: KDE Screen Locker (kscreenlocker), signal: Segmentation fault
[KCrash Handler]
#5  0x0000000000000000 in ?? ()
#6  0x00007f897954ae14 in ?? () from /usr/lib64/dri/fglrx_dri.so
#7  0x00007f89795a48b0 in ?? () from /usr/lib64/dri/fglrx_dri.so
#8  0x00007f897959eca3 in ?? () from /usr/lib64/dri/fglrx_dri.so
#9  0x00007f89793f68da in ?? () from /usr/lib64/dri/fglrx_dri.so
#10 0x00007f89793e4f43 in ?? () from /usr/lib64/dri/fglrx_dri.so
#11 0x00007f89780fbb4e in ?? () from /usr/lib64/dri/fglrx_dri.so
#12 0x00007f8978b65424 in ?? () from /usr/lib64/dri/fglrx_dri.so
#13 0x00007f8978b65580 in ?? () from /usr/lib64/dri/fglrx_dri.so
#14 0x00007f897954ec5e in __driCreateNewScreen_20050727 () from /usr/lib64/dri/fglrx_dri.so
#15 0x00007f8984753662 in ?? () from /usr/lib64/libGL.so.1
#16 0x00007f898474f851 in ?? () from /usr/lib64/libGL.so.1
#17 0x00007f898474fa2e in glXChooseVisual () from /usr/lib64/libGL.so.1
#18 0x00000000004109a3 in LockProcess::createSaverWindow (this=0x7fff0ab29430) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:485
#19 0x0000000000414f04 in LockProcess::startSaver (this=0x7fff0ab29430) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:738
#20 0x000000000041527d in LockProcess::defaultSave (this=0x24bd270) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/lockprocess.cc:312
#21 0x000000000041d4c8 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.3/krunner/lock/main.cc:163

Regards
Comment 3 Christoph Feck 2010-10-19 15:31:59 UTC

*** This bug has been marked as a duplicate of bug 234689 ***
Comment 4 woogin8r 2010-10-21 02:55:26 UTC
I reviewed bug 234689 and, if I'm following the thread correctly, the resolution listed there is to run "aticonfig --initial" from a command line, and/or delete your "/etc/X11/xorg.conf".  I had already performed both of those procedures countless times, in every order possible.  I also tried restoring various backups of xorg.conf, but to no avail.  "aticonfig --initial" absolutely did not resolve anything for me.  The only resolution I could find was migrating to Mandriva, which seems much more stable and reliable for me.

I kind of miss Debian's packaging system, but I don't miss it *that* much.  :-)