[SOLVED] This evenings updates killed xserver

[GreyGeek]

After this evenings 111 updates Karmic never gets to the desktop login screen and merely presents a console login.

As soon as I get my eth cable connected I will see if

apt-get install -reinstall kubuntu-desktop

will work its magic again.

EDIT:
As of 11:21 PM CST, my KDE4.3.1 is still down. Reinstalling kubuntu-desktop did not work.

Looks like we'll have to wait until the dev crew gets all the files updated.

[kubicle]

Re: This evenings updates killed xserver

If you have the same issue as me, it is that kdm fails to start. The latest upgrades switched kdm to upstart as well, so there is probably something wrong with the upstart configuration.

Boot messages include a number of:

init: kdm main process terminated with status 1
init: kdm main process ended, respawning

And finally:

kdm respawning too fast, stopped

Temporary workaround:
Start kdm manually after logging in text mode:
sudo /usr/bin/kdm
('startkde' as a user should bring you directly to kde as well)

[Fintan]

Re: This evenings updates killed xserver

I can confirm this behavior.

On my desktop boot hangs for ages at
"checking battery state"
then at
"Advanced Power Management"

After a cup of coffee I get a cli login.

Don't want to try on my laptop just yet.

Looks like we are in for some fun until release

[kubicle]

Re: This evenings updates killed xserver

I checked /etc/init/kdm.conf, and looks like a simple fix (fixed the issue on my machine):

line 16:

[ ! -f /etc/X11/default-display-manager -o "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/kdm" ]

change to:

[ ! -f /etc/X11/default-display-manager -o "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/kdm" ]

[Fintan]

Re: This evenings updates killed xserver

Thankx kubicle, worked here

[caryb]

Re: This evenings updates killed xserver

I dont have a /etc/init/kdm.conf

Cary

[Rog131]

Re: This evenings updates killed xserver

I dont have a /etc/init/kdm.conf

At here, before:

:~$ ls -l /etc/init/kdm.conf
ls: cannot access /etc/init/kdm.conf: No such file or directory

and after the > kdebase-workspace 4:4.3.1-0ubuntu10:

:~$ ls -l /etc/init/kdm.conf
-rw-r--r-- 1 root root 3847 2009-09-26 02:08 /etc/init/kdm.conf

kdebase-workspace 4:4.3.1-0ubuntu10:

Changelog
kdebase-workspace (4:4.3.1-0ubuntu10) karmic; urgency=low

* Add kdm.upstart and convert kdm.postinst to upstart

and a bug report > Bug #437067: kdm does not start (upstart) - error in /etc/init/kdm.conf

[GreyGeek]

Re: This evenings updates killed xserver

I dont have a /etc/init/kdm.conf

Cary

Perhaps what worked for me will work for you.

After I logged into the console account I issed

sudo services kdm restart

and when I got the prompt back I issued

startx


which gave me the desktop.

[jwhibdon]

Re: [SOLVED] This evenings updates killed xserver

Couldn't remember that sudo services kdm restart so I just typed startx and it worked but now I have no sound at all.

[bossa]

Re: [SOLVED] This evenings updates killed xserver

I have lost KDM too and all audio has gone
Startx works to get to the desktop but there is no option to shut down from the desktop only logout

[kubicle]

Re: [SOLVED] This evenings updates killed xserver

The bug should be fixed in kdm 4:4.3.1-0ubuntu11

I have lost KDM too and all audio has gone
Startx works to get to the desktop but there is no option to shut down from the desktop only logout

Both symptoms ('no audio' and 'logout only') are likely caused by starting kde with startx, try upgrading to the latest kdm to be sure.

I dont have a /etc/init/kdm.conf

As rog131 pointed out, the file does not exist if you don't have the new (0ubuntu10 or 0ubuntu11) kdm package installed, it's an upstart conf file (older versions start with an initscript).

[GreyGeek]

Re: [SOLVED] This evenings updates killed xserver

I have lost KDM too and all audio has gone
Startx works to get to the desktop but there is no option to shut down from the desktop only logout

That's because the xserver was started from a konsole and when you "logout" the only place left to go is back to the konsole from which you started the xserver. The login screen was never loaded.

[bossa]

Re: [SOLVED] This evenings updates killed xserver

Hi kubicle

I used your suggestion about changing the etc/init/kdm.conf and that worked nicely. The KDM I have is the kdm-4:4.3.1-0ubuntu11..is that the latest ?
As for the audio seems I only loose it when using Amarok. because on logout amarok was still in my systray so I kept getting a problem when I logged back in.
By the way I keep getting blocked Amarok updates is it possible to allow them or is it not advisable ?

[Snowhog]

Re: [SOLVED] This evenings updates killed xserver

By the way I keep getting blocked Amarok updates is it possible to allow them or is it not advisable ?

Not advisable. Blocked packages are blocked for a reason, usually, because allowing them would cause breakage in other packages.

[Rog131]

Re: [SOLVED] This evenings updates killed xserver

By the way I keep getting blocked Amarok updates is it possible to allow them or is it not advisable ?

How are you trying to upgrade ?
What is the warning/error message ?


Good advices:

> Topic: The usual WARNINGS and CAVEATS about using development versions:

"claydoh":

Updating and upgrading

I recommend using the command line for updating and upgrading, especially in the alpha stage, and pretty much up to the rc stage.

this makes it much easier to see what is broken/missing/held back/to be removed before you proceed. If there is any doubts, just wait for a bit and see if it resolves later.

> Karmic Koala Alpha 6 Released - Please Read Before Testing (Ubuntu forums):

"23meg":

Once you've started testing, do not upgrade your installation blindly - especially avoid partial upgrades offered by Update Manager unless you know precisely why it's offering a partial upgrade. Regardless of which tool (APT, Update Manager, Synaptic, Aptitude) you're using to upgrade your packages, always check the list of packages to be removed, upgraded and installed before each upgrade. If in doubt, check the changelogs ("Package > Download Changelog" in Synaptic, or "aptitude changelog package_name", or at packages.ubuntu.com) to see why a package may be being removed.

Here the Amarok is version: 2:2.1.90-0ubuntu1 (2.1.90 = Amarok 2.2 Beta 2 "Red Dawn")
> [ubuntu/karmic] amarok 2:2.1.90-0ubuntu1 (Accepted)