suddenly kubuntu wont login...

[toyarmy]

one day im on kubuntu, and everythings fine.
the next i start to load it, type in my password, and get sent back around < like a restart >
ive gone into the "failsafe" mode, and my password worked fine there, so its not the password, but im not sure what it is, or how to fix it.

thank you.

[dibl]

Re: suddenly kubuntu wont login...

Possibly something happened with your X server setup. Can you open the file /var/log/Xorg.0.log, and paste the last 20 or 30 lines of it into a post here?

[penguin.ch]

Re: suddenly kubuntu wont login...

gone into the "failsafe" mode

[sudo] apt-get clean - then: try again ...

[toyarmy]

Re: suddenly kubuntu wont login...

Possibly something happened with your X server setup. Can you open the file /var/log/Xorg.0.log, and paste the last 20 or 30 lines of it into a post here?

im not sure how to do that < yes, im basically a n00b >
but ill try the other suggestion.

[penguin.ch]

Re: suddenly kubuntu wont login...

im not sure how to do that

Do a [sudo] tail -n 30 /var/log/Xorg.0.log and "copy & paste" the resulting output

[toyarmy]

Re: suddenly kubuntu wont login...

[sudo] apt-get clean - then: try again ...

i did this, and now when i type my password a little console box pops up. :/

[toyarmy]

Re: suddenly kubuntu wont login...

im not sure how to do that

Do a [sudo] tail -n 30 /var/log/Xorg.0.log and "copy & paste" the resulting output

so, i guess im doing something wrong...

jes@desktop:~$ sudo
usage: sudo -K | -L | -V | -h | -k | -l | -v
usage: sudo [-HPSb] [-p prompt] [-u username|#uid]
      { -e file [...] | -i | -s | <command> }
jes@desktop:~$ [sudo] tail-n 30 /var/log/Xorg.0.log
bash: [sudo]: command not found
jes@desktop:~$ sudo
usage: sudo -K | -L | -V | -h | -k | -l | -v
usage: sudo [-HPSb] [-p prompt] [-u username|#uid]
      { -e file [...] | -i | -s | <command> }
jes@desktop:~$ tail-n 30 /var/log/Xorg.0.log
bash: tail-n: command not found
jes@desktop:~$ sudo tail-n 30 /var/log/Xorg.0.log
Password:
sudo: tail-n: command not found
jes@desktop:~$

[penguin.ch]

Re: suddenly kubuntu wont login...

i guess im doing something wrong

Let's put it this way: pUnctUationANDspeLLing are absolutely crucial

[toyarmy]

Re: suddenly kubuntu wont login...

jes@desktop:~$ tail -n 30 /var/log/Xorg.0.log
(**) cursor: serial speed 9600
(**) Option "SendCoreEvents"
(**) eraser: always reports core events
(**) eraser device is /dev/input/wacom
(**) eraser is in absolute mode
(**) eraser: forcing TabletPC ISD V4 protocol
(**) WACOM: suppress value is 2
(**) Option "BaudRate" "9600"
(**) eraser: serial speed 9600
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
(II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
    No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
    No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
    No such file or directory.
Error opening /dev/input/wacom : Success
(II) Configured Mouse: ps2EnableDataReporting: succeeded
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
jes@desktop:~$

?

[toyarmy]

Re: suddenly kubuntu wont login...

no help?

[Doublerob7]

Re: suddenly kubuntu wont login...

i've seen this problem posted by 3 or 4 other people, but never any answers.

i'm having the same problem, when i attempt to log into anything other than console, the screen goes blank and it comes back up with the kubuntu login screen.

i installed ubuntu 7.04 and sudo apt-"got" kubuntu-desktop from there, and now i'm stuck at the login screen

[penguin.ch]

Re: suddenly kubuntu wont login...

Anything of interest in /var/log/kdm.log ...?

[Doublerob7]

Re: suddenly kubuntu wont login...

this is what kdm.log has to say:

X Window System Version 7.2.0
Release Date: 22 January 2007
X Protocol Version 11, Revision 0, Release 7.2
Build Operating System: Linux Ubuntu
Current Operating System: Linux 1600GHz 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64
Build Date: 04 April 2007
	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 29 14:20:04 2007
(==) Using config file: "/etc/X11/xorg.conf"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
	No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
	No such file or directory.
Error opening /dev/input/wacom : Success
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
	No such file or directory.
Error opening /dev/input/wacom : Success
Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list!
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list!
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device
QImage::convertDepth: Image is a null image
QImage::smoothScale: Image is a null image
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
 Major opcode: 147
 Minor opcode: 3
 Resource id: 0x0
Failed to open device

i have no idea how many times i tried to log in, but this shows up quite a number of times. could it be that my keyboard or mouse is hanging up the system?

[penguin.ch]

Re: suddenly kubuntu wont login...

this is what kdm.log has to say

Which is (mostly) the wacom crap usual in Kubuntu (further reading).

Hmmm ... on the log-in screen, please select Console Login from the left menu, log in (as user), then issue the command startx - and tell us about your system's "response" ...

[Doublerob7]

Re: suddenly kubuntu wont login...

hostname: Unknown host
xauth: creating new authority file /home/robert/.serverauth.5425

X: user not authorized to run the X server, aborting.

Couldnt get a file descriptor referring to the console

there ya go

oh and i got rid of all the wacom crap too, i figured i didn't need a stylus or tablet in my conf file before you mentioned it :P

************************************************** **********
EDIT: FIXED
************************************************** **********

I reverted back to ubuntu gnome loading by sudo dpkg-reconfigure gdm, changing the default back to gdm, and letting it reboot. At the login screen, i chose KDE session, and when i logged in, it spat back an error saying that ksetupconfig couldn't be found. When i looked through the error log, i noticed it was trying to create folders but couldn't due to permissions.
So i logged into a gnome session and did the following:

sudo -i
cd /home/<user name>
chmod 777 .kde/
cd .kde/
mkdir share
chmod 777 *
cd share/
mkdir config
chmod 777 *

After that, the startup script apparently was satisfied, and it went along and put things in the right place and logged me in

Thanks for the help Unicorn, much appreciated. I hope that this post helps somebody in the future suffering the same problem.