Seriously Annoying! Find Myself Logged Out! Need Help!

[skillet]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

reinstall kdebase-kio-plugins, kdm, kdebase, kdebase-bin-kde, kdebase-data and kdebase. see if that helps

[skillet]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

OOPS. reinstall kwin too.

[MoonRise]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

GeForce FX 5600 card with the latest drivers direct from Nvidia (169.07).

To me, if X is failing, then I suspect the video driver. For excellent Nvidia help, I'd search for Dibl's Nvidia help posts. Excellently written. As a test of that theory, back up your xorg.conf file first, then do:

sudo dpkg-reconfigure xserver-xorg

Choose the Vesa driver. For other settings you are unsure of, use the defaults. You might not have the resolution you want, but it should isolate that it is or isn't the video driver.

[vbgunz]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

Thanks for the help but since I cannot trigger this issue on demand, I find it hard to follow some suggestions. I'll list my reasons below.

I don't really want to go about reinstalling some stuff that may have nothing to do with the problem. my installation of Gutsy is as old as Gutsy stable itself with a home directory of about 2 years old.

I don't really wish to try out the vesa driver *but* would agree this may be a solution *but* at the cost of losing some very valuable resolution. the performance I get is near perfect. I can play games like warsow at 1680x1050 with all options on except antialiasing at a steady 60 fps. this is with about 16 applications spread across several desktops running in the background. DVDs and color are crisp.

Although logging out mostly happens randomly, I have caught it several times almost only when switching consoles though it doesn't happen on cue. I have never been in the middle of anything and logged out. I'll paste my xorg.conf as maybe it'll show some clues I may be missing or overlooking.

My xorg.conf

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Thu Dec 13 19:09:35 PST 2007

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#  sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"

# Uncomment if you have a wacom tablet
#	InputDevice   "stylus"	"SendCoreEvents"
#	InputDevice   "cursor"	"SendCoreEvents"
#	InputDevice   "eraser"	"SendCoreEvents"
  Identifier   "Default Layout"
  Screen     "Default Screen" 0 0
  InputDevice  "Generic Keyboard"
  InputDevice  "Configured Mouse"
EndSection

Section "Files"
EndSection

Section "Module"
  Load      "glx"
EndSection

Section "InputDevice"
  Identifier   "Generic Keyboard"
  Driver     "kbd"
  Option     "CoreKeyboard"
  Option     "XkbRules" "xorg"
  Option     "XkbModel" "pc105"
  Option     "XkbLayout" "us"
EndSection

Section "InputDevice"
  Identifier   "Configured Mouse"
  Driver     "mouse"
  Option     "CorePointer"
  Option     "Device" "/dev/input/mice"
  Option     "Protocol" "ImPS/2"
  Option     "ZAxisMapping" "4 5"
  Option     "Emulate3Buttons" "true"
EndSection

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

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

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

Section "Monitor"
  Identifier   "eView 17f3"
  HorizSync    28.0 - 73.0
  Option     "DPMS" "TRUE"
  Option     "useEDID" "FALSE"
EndSection

Section "Device"
  Identifier   "nVidia Corporation NV31 [GeForce FX 5600]"
  Driver     "nvidia"
EndSection

Section "Screen"
  Identifier   "Default Screen"
  Device     "nVidia Corporation NV31 [GeForce FX 5600]"
  Monitor    "eView 17f3"
  DefaultDepth  24
  Option     "NvAGP" "1"
  SubSection   "Display"
    Virtual   1680 1050
    Depth    24
    Modes   "1680x1050"
  EndSubSection
EndSection

any help is appreciated!

[vbgunz]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

skillet, I went ahead and resintalled those applications. not sure if it is going to make a difference but hopefully it does. btw, there is no kdebase-bin-kde. did you mean kdebase-bin?

MoonRise, although I dread lowering the resolution in favor of using the vesa OR nv driver, isn't it or shouldn't it be possible to somehow get the current modelines in use? e.g., nvidia can go as high as 1680x1050 but nv only as high as 1400x900 (I believe). I tried read-edid, get-edid | parse-edid but that didn't work :/

is there anyway to find out what my current modeline is?

I think I wouldn't mind much switching to the nv driver if I could get the same resolution with more stability (if nvidia is even the problem).

[MoonRise]

Re: Seriously Annoying! Find Myself Logged Out! Need Help!

MoonRise, although I dread lowering the resolution in favor of using the vesa OR nv driver, isn't it or shouldn't it be possible to somehow get the current modelines in use? e.g., nvidia can go as high as 1680x1050 but nv only as high as 1400x900 (I believe). I tried read-edid, get-edid | parse-edid but that didn't work :/

When using that above command, this will be only a test to see if it is stable and doesn't cause the same problem. During that process, it will let you choose which resolutions you can use. I'm not sure what Vesa will allow, but you can replace the new xorg.conf file with your back up of your current one to get back what you had (must do that as root). Alternately from doing that you can re-run that command and choose "nvidia" the next time around and choose your resolution that you had. If it is stable without doing the log out problem then that "nvidia" driver probably is faulty. If that is the case, search for Dibl's Nvidia How-To. It is very well written and many have had success with it.