Bug 710826 - Black Screen Lockout
Summary: Black Screen Lockout
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-05 04:50 UTC by gcarter
Modified: 2011-07-03 19:20 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-03 19:20:37 UTC
Type: ---


Attachments (Terms of Use)
X info (45.48 KB, text/plain)
2011-06-05 04:50 UTC, gcarter
no flags Details

Description gcarter 2011-06-05 04:50:58 UTC
Created attachment 503044 [details]
X info

Description of problem:


Version-Release number of selected component (if applicable):
Fedora 15, KDE Desktop

How reproducible:
Use Lock Screen Function in KDE.

First time it works, hitting a key you get the prompt to type in your password and you are back to the desktop OK.

Do it again, the screen goes black, you lose your xsession.  CTRL-ALT-BACKSPACE is needed to recover.


Steps to Reproduce:
1. Use Console Lock PADLOCK Widget
2. Xscreensaver starts, then enter password to get back.
3. Do 1 &2 again.   Black Screen results.
  
Actual results:
Black Screen

Expected results:
Should display the desktop after unlocking it.

Additional info:
Fedora 15

Comment 1 Mamoru TASAKA 2011-06-05 05:03:00 UTC
Sorry, however more info is needed to understand what is happening on your X session.

First of all, KDE has its own screensaver, kscreensaver. Are you sure that you are actually using xscreensaver instead of kscreensaver or something else?

Comment 2 Mamoru TASAKA 2011-06-05 05:05:30 UTC
( To check above, please post the results of following commands:
  $ rpm -qa | grep screensaver | sort
  $ ps auwwx | grep screensaver
)

Comment 3 gcarter 2011-06-05 20:13:20 UTC
[root@kali ~]# rpm -qa | grep screensaver | sort
gnome-screensaver-3.0.0-1.fc15.x86_64
kdeartwork-screensavers-4.6.3-1.fc15.x86_64
xscreensaver-5.14-1.fc15.x86_64
xscreensaver-base-5.14-1.fc15.x86_64
xscreensaver-extras-5.14-1.fc15.x86_64
xscreensaver-extras-base-5.14-1.fc15.x86_64
xscreensaver-extras-gss-5.14-1.fc15.x86_64
xscreensaver-gl-base-5.14-1.fc15.x86_64
xscreensaver-gl-extras-5.14-1.fc15.x86_64
xscreensaver-gl-extras-gss-5.14-1.fc15.x86_64
[root@kali ~]# ps auwwx | grep screensaver
root      2763  0.0  0.0 103428   856 pts/0    S+   15:12   0:00 grep --color=auto screensaver
[root@kali ~]# )

Comment 4 gcarter 2011-06-05 20:16:13 UTC
I only set the screen saver from within KDE. (Settings Control Panel)

I do not independently launch xscreensaver separately.

-gc

Comment 5 Mamoru TASAKA 2011-06-05 21:30:47 UTC
And how did you set screensaver on KDE "Control Panel"?

Also, from the output of ps no screensavers seem to be running. Would you relogin to KDE session and try "$ ps auwwx" again?

Comment 6 gcarter 2011-06-05 23:02:55 UTC
Well, kde has its own service for launching a screen saver.

You won't see it running, unless the service tracking the idletime says its time to launch it.

Secondly, I would like to point out, KDE desktop will use:

kscreenlocker to unlock the console on the root window for

keuphoria.kss, which is launched as the screen saver on the root window.

-gc

Comment 7 Mamoru TASAKA 2011-06-06 00:59:42 UTC
Okay, thank you. Changing the component to KDE ones

Comment 8 Kevin Kofler 2011-06-06 01:07:34 UTC
Sounds like X is crashing, i.e. a graphics driver bug. What graphics driver are you using?

Comment 9 gcarter 2011-06-06 17:17:19 UTC
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_INTEL_swap_event
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_framebuffer_sRGB, 
    GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, 
    GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap, 
    GLX_INTEL_swap_event
GLX version: 1.4
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, 
    GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, 
    GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGI_make_current_read, 
    GLX_SGI_swap_control, GLX_SGI_video_sync, GLX_SGIS_multisample, 
    GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
    GLX_EXT_texture_from_pixmap, GLX_INTEL_swap_event
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV670
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20
OpenGL extensions:

Comment 10 gcarter 2011-06-08 16:22:28 UTC
The black screen when it does happen allows me to CTRL-ALT-BACKSPACE to kill the session.

So I think it might be a kwin compositor problem.

I checked the logs and did not find any output whatsoever of anything describing what happened.

So I don't think it is a kernel problem, or a X problem otherwise I wouldn't be able to continue using my machine.

-gc

Comment 11 gcarter 2011-07-03 19:20:37 UTC
Finished testing the latest ddx module for ATI video/X.

The last ati-ddx update I received has resolved this problem.

It also fixes full screen mode in Flash and  Stellararium.

-gc


Note You need to log in before you can comment on or make changes to this bug.