Bug 389545 - Screen goes black when logging out of KDE 4
Summary: Screen goes black when logging out of KDE 4
Status: RESOLVED DUPLICATE of bug 390382
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Beta 2
Hardware: i686 Linux
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-12 20:42 UTC by kevin vandeventer
Modified: 2008-05-14 18:53 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description kevin vandeventer 2008-05-12 20:42:24 UTC 
When I click on the blue arrow at the bottom right of the desktop or select logout from the leave menu, my screen goes black and the mouse cursor disappears. I'm forced to reboot at this point. 

Here are the last few lines from /var/log/messages during the session when I tried to log out:

May 12 12:26:38 linux-rgdf gconfd (kevin-26925): GConf server is not in use, shutting down.
May 12 12:26:38 linux-rgdf gconfd (kevin-26925): Exiting
May 12 12:27:00 linux-rgdf klogd: klauncher[3162]: segfault at 8048844 ip b771b3d8 sp bf9d0670 error 7 in libX11.so.6.2.0[b7703000+11d000]
Comment 1 Stephan Binner 2008-05-13 09:00:32 UTC 
What graphic card and driver do you use? Do you have desktop effects enabled? If so, does it happen too if you disable them?
Comment 2 kevin vandeventer 2008-05-13 16:12:21 UTC 
I'm using a GeForce 8600 GTS with the nv driver. I don't have desktop effects enabled. I tried to build the nvidia drivers but when I applied the recommended patch I got the following error:

'Could not locate patch utility'
Comment 3 Stephan Binner 2008-05-14 18:37:42 UTC 
Could this be a dupe of Bug 390382?
Comment 4 Stefan Dirsch 2008-05-14 18:53:17 UTC 
Yes. Definitely.

*** This bug has been marked as a duplicate of bug 390382 ***