KDE startup problem still

[eddieg538]

What is happening to me after the upgrade to 304.88. Occasionally, during start up, instead of going to the graphical login, the procedure will stop at the Linux login. At this point I can usually do one of two things: I can log in manually and do sudo kdm start, or reboot. I believe it has to do with the nvidia driver 304.88 and the way it installed. I noticed when it installed a few days ago when I was running 4.10.5 it was loading different. Seems it doesn't load until kde starts because I have the large linux login showing that never did that before. Rebooting does cause my computer to boot normally sometimes. This was brought up before and thread marked solved but it isn't for me.

[dmeyer]

What is happening to me after the upgrade to 304.88. Occasionally, during start up, instead of going to the graphical login, the procedure will stop at the Linux login. At this point I can usually do one of two things: I can log in manually and do sudo kdm start, or reboot. I believe it has to do with the nvidia driver 304.88 and the way it installed. I noticed when it installed a few days ago when I was running 4.10.5 it was loading different. Seems it doesn't load until kde starts because I have the large linux login showing that never did that before. Rebooting does cause my computer to boot normally sometimes. This was brought up before and thread marked solved but it isn't for me.

When you boot the computer, just after you select the grub entry hit <ESC> to see the console output during boot then tell me if anything stands out. Sometimes hitting <ESC> is unnecessary. Usually it will kick out an error if it's got a problem. Also paste output for:

lsmod | grep nvidia

[eddieg538]

Hi. I don't have to select an entry and I don't have a grub menu. The output for the entry is:

nvidia 10286823 54

[eddieg538]

Looking at the boot menu in my grub line I see a entry at the end I don't remember seeing. Is it suppose to be there? $vt_handoff If so, what does it mean?

linux /boot/vmlinuz-3.2.0-53-generic-pae root=UUID=43a999d6-7d03-4761-ac7a-6dafcb428031 ro quiet splash acpi=force $vt_handoff

[Snowhog]

Take a look at http://www.thefanclub.co.za/how-to/h...r-grub-updates
And http://ubuntuforums.org/showthread.p...1#post12527631

[eddieg538]

Thank you Snowhog, I will give this a try and post what happens.

[eddieg538]

Neither one of the suggestions worked. It did start fine yesterday but not today. Why does it work sometimes but not other? This is my boot line in grub:

linux /boot/vmlinuz-3.2.0-53-generic-pae root=UUID=43a999d6-7d03-4761-ac7a-6dafcb428031 ro quiet splash acpi=force

Is this right or is there something missing? Thank you.

[eddieg538]

I noticed today that libkwinnvidiahack4 is still from 4.10.5 and not 4.11 which is installed. It's the library used by nvidia cards for the KDE window. This package is part of the KDE workspace module. Why is this not 4.11? Could this cause my problem?

[schnelle]

What is happening to me after the upgrade to 304.88. Occasionally, during start up, instead of going to the graphical login, the procedure will stop at the Linux login. At this point I can usually do one of two things: I can log in manually and do sudo kdm start, or reboot. I believe it has to do with the nvidia driver 304.88 and the way it installed. I noticed when it installed a few days ago when I was running 4.10.5 it was loading different. Seems it doesn't load until kde starts because I have the large linux login showing that never did that before. Rebooting does cause my computer to boot normally sometimes. This was brought up before and thread marked solved but it isn't for me.

I had this problem on both my PCs (one with open radeon and one with catalyst drivers) after upgrading to kde 4.10. I solved the problem by replacing KDM with lightdm-kde. You can find it here: https://launchpad.net/~agateau/+archive/lightdm-kde

Hope it helps.

[eddieg538]

When you installed lightdm did you have to install about 60 more packages?

[schnelle]

When you installed lightdm did you have to install about 60 more packages?

No. Maybe 5-6 packages. If I try to remove it I get this output:

nikola@laptop:~$ sudo apt-get remove lightdm-kde-greeter 

The following packages were automatically installed and are no longer required:
  libglib2.0-bin lightdm liblightdm-gobject-1-0 libxklavier16 liblightdm-qt-2-0
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  lightdm-kde-greeter

[eddieg538]

I installed the lightdm-kde-greeter and it seems to boot fine now. If I tried to install lightdm there were 60 packages but if I tried to install lightdm-kde-greeter then it was only 5-6 packages but included lightdm, go figure..I don't know if this is solved or just a work around.

[schnelle]

I installed the lightdm-kde-greeter and it seems to boot fine now. If I tried to install lightdm there were 60 packages but if I tried to install lightdm-kde-greeter then it was only 5-6 packages but included lightdm, go figure..I don't know if this is solved or just a work around.

LightDM is ubuntu's default display manager so it probably pulls a lot of ubuntu-specific gtk stuff. Kubuntu uses lightdm-kde "greeter" front end (thats why I shared lightdm-kde ppa).

Here is a brief explanation:

LightDM is a cross-desktop display manager (think KDM). It's designed to be fast and lightweight, it is written to replace GDM Gnome's display manager.
What makes LightDM interesting for KDE is it is designed to to have multiple 'greeters'. This is the front end that sits on top of the daemon and does the displaying to the user asking them for login details. This means we can have our own KDE interfaces, whilst the Gnome people do their different UIs all whilst sharing the same daemon that handles all the hard parts.

Btw, I am glad lightdm-kde solved your startup problems

[dmeyer]

I installed the lightdm-kde-greeter and it seems to boot fine now. If I tried to install lightdm there were 60 packages but if I tried to install lightdm-kde-greeter then it was only 5-6 packages but included lightdm, go figure..I don't know if this is solved or just a work around.

This has to do with Ubuntu packaging! Try to install VLC without pulling half of GTK+ in! Honestly, that Unity catastrophe and all the funny dependencies they have started to introduce leave a person with a heavier than needed KDE experience. At least you figured out a workaround. Usually just ignoring the recommended packages does the trick.