Switch User Fails most of the time

Bug #292500 reported by samo_nz
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: fast-user-switch-applet

When choosing Switch User from a locked screen it will show the screen-saver for a few more seconds then go straight back to the locked dialogue, if I unlock the account there is an error message saying "the X server failed, perhaps it is not configured well"

however sometimes Switch User works well..

Just did a fresh install of intrepid on a P4, 2.8GHz, 1GB RAM, GeforceFX5700

Revision history for this message
samo_nz (samo-nz) wrote :

- seems to work fine now with no modifications, maybe only the first time trying to switch user?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in gdm:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
samo_nz (samo-nz) wrote :
  • err Edit (9.9 KiB, application/octet-stream)

happened again today, freezes for a second, blank screen then the screensaver starts again, error this time was "Cannot start display, there were errors trying to start the X server"

the error box must of came up every time i clicked switch user as there was 15 boxes on top of each other when i entered my password..

I really dont know how to reproduce the bug but can give you some insight into how my intrepid is set up..

Im using the nvidia restricted driver, have compiz with the sphere and eye candy enabled, and run emerald.

other than that it is a fresh install, I've been looking through my logs but, as there are a fair few errors and none seem to of shown up at the time of the bug, I am unsure what to list here

the bug doesn't show up after managing to switch user eventually, until the next restart

Revision history for this message
samclam (poo-gmx) wrote :

I had similar problem with Intrepid.

I changed the Gnome login session to "failsafe Gnome" and logged into to each different user account without any hitches. After that I could use the normal Gnome session and log in / out & Switch to my hearts content.

Hope that helps.

Revision history for this message
samclam (poo-gmx) wrote :

Doesn't work for the Guest session, as I don't know how to login in to this account under failsafe Gnome.

You can get out of the blank screen desktop by pressing "Ctrl + Alt + Backspace" which brings you back to the Login screen.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue seems rather to be an xorg or nvidia one

Changed in gdm:
assignee: desktop-bugs → nobody
status: Incomplete → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi samo-nz,

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

Changed in xorg-server:
status: New → Incomplete
Revision history for this message
DeRock25 (thenewcrowd) wrote :

Yes, i have the same issue... happens EVERY time, i have nvidia card... but that's not the problem... it ALL started when i used the tutorial to install my bamboo fun pad.

and on the comments for the installation it notes the "instabilitly" and tells you how to fix it, not sure if it's the same thing.. but heres a link to the tutorial, dissect as you will.... if it wasn't like 20some pages i would be more specific...

http://ubuntuforums.org/showthread.php?p=4785779

# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by failsafeDexconf, using
# values from the debconf database and some overrides to use vesa mode.
#
# You should use dexconf or another such tool for creating a "real" xorg.conf
# For example:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Screen"
 Identifier "Default Screen"
 Device "Configured Video Device"
 Monitor "Configured Monitor"
 SubSection "Display"
  Depth 24
  Modes "1440x900@75" "1152x864@75" "1280x1024@75" "1024x768@43" "1280x960@60" "1024x768@60" "1280x960@85" "1024x768@70" "1280x1024@85" "1024x768@75" "1280x1024@60" "1024x768@85" "1280x960@75" "832x624@75" "1400x1050@60" "800x600@60" "1400x1050@75" "800x600@85" "1600x1200@65" "800x600@75" "1600x1200@60" "800x600@72" "1600x1200@75" "800x600@56" "1600x1200@70" "640x480@85" "1792x1344@60" "640x480@75" "1856x1392@60" "640x480@72" "1920x1440@60" "640x480@60" "2048x1536@60"
 EndSubSection
 Option "AddARGBGLXVisuals" "True"
 Defaultdepth 24
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "stylus"
 Option "Device" "/dev/input/wacom"
 Option "Type" "stylus"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
 Option "USB" "on"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "eraser"
 Option "Device" "/dev/input/wacom"
 Option "Type" "eraser"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
 Option "USB" "on"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "cursor"
 Option "Device" "/dev/input/wacom"
 Option "Type" "cursor"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
 Option "USB" "on"
EndSection

Section "InputDevice"
 Driver "wacom"
 Identifier "pad"
 Option "Device" "/dev/input/wacom"
 Option "Type" "pad"
 Option "USB" "on"
EndSection
Section "Device"
 Identifier "Configured Video Device"
 Boardname "vesa"
 Busid "PCI:1:0:0"
 Driver "nvidia"
 Screen 0
EndSection

# commented out by update-manager, HAL is now used
#Section "InputDevice"
# Identifier "Generic Keyboard"
# Driver "kbd"
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
#EndSection

# commented out by update-manager, HAL is now used
#Section "InputDevice"
# Identifier "Configured Mouse"
# Driver "mouse"
# Option "Emulate3Buttons" "true"
#EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 InputDevice "stylus" # "SendCoreEvents"
 InputDevice "cursor" # "SendCoreEvents"
 InputDevice "eraser" # "SendCoreEvents"
 InputDevice "pad"
  screen 0 "Default Screen" 0 0
EndSection

Section "Module"
 Load "glx"
 Load "GLcore"
 Load "v4l"
EndSection

Revision history for this message
DeRock25 (thenewcrowd) wrote :

well update.... i fixed my issue... while i posted it...

Section "ServerLayout"
 Identifier "Default Layout"
 InputDevice "stylus" # "SendCoreEvents"
 InputDevice "cursor" # "SendCoreEvents"
 InputDevice "eraser" # "SendCoreEvents"
 InputDevice "pad"
  screen 0 "Default Screen" 0 0
EndSection

fixed my issue... because it was orignally...

Section "ServerLayout"
 Identifier "Default Layout"
 InputDevice "stylus" "SendCoreEvents"
 InputDevice "cursor" "SendCoreEvents"
 InputDevice "eraser" "SendCoreEvents"
 InputDevice "pad"
  screen 0 "Default Screen" 0 0
EndSection

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

I was unable to reproduce it on Jaunty Jackalop 9.04. Tried switching users from the lock command and using the menu.

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

Repeated again switched among several users logged for at least 5 hours. Switching works from the lock window and the top bar menu.

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

Next I'd like to forward this issue upstream, but first it must be retested on latest Jaunty to make sure the issue still happens there with the latest code. ISO images are available at http://cdimages.ubuntu.com/daily/current/ - if you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log from this testing.

Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

This was a known bug which has now been fixed.

Changed in xorg-server (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.