Kubuntu stuck on boot logo

[XenoNorth]

Hello!

Since a few days i have got the problem that the graphical user interface on my notebook (Thinkpad T61) won't start correctly. While booting, the system stucks at the Kubuntu boot logo. The problem started after installing the latest updates (which i do frequently), after which the system did not shut down correctly.

Version:

Ubuntu 14.04.1 LTS
Linux thinkpad 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I checked dmesg and the logfile and found at least the following problems ->

dmesg:

init: lightdm main process (1741) terminated with status 1

lightdm.log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.10.1, UID=0 PID=1741
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/40-kde-plasma.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Registered seat module xlocal
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Registered seat module surfaceflinger
[+0.03s] DEBUG: Adding default seat
[+0.03s] DEBUG: Seat: Starting
[+0.03s] DEBUG: Seat: Creating greeter session
[+0.03s] DEBUG: Seat: Failed to find session configuration default
[+0.03s] DEBUG: Seat: Failed to create greeter session

x-0-greeter.log:

QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession

Xorg.0.log:

[...]
[    63.956] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    63.956]    Entry deleted from font path.
[    63.956] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    63.956]    Entry deleted from font path.
[    63.956] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    63.956]    Entry deleted from font path.
[    63.956] (**) FontPath set to:
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/Type1,
        built-ins,
        /usr/share/fonts/X11/misc,
        /usr/share/fonts/X11/Type1,
        built-ins
[    63.956] (**) ModulePath set to "/usr/lib/xorg/modules"
[    63.956] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[    63.956] (WW) Disabling Mouse0
[    63.956] (WW) Disabling Keyboard0
[    63.956] (II) modesetting(0): using drv /dev/dri/card0
[    63.956] Number of created screens does not match number of detected devices.
  Configuration failed.

Any help would be appreciated. Thank you!

[vinnywright]

is their any chance your root partition got full ? (if so the upgrade may not have completed , no space to unpack and configure)

can you boot to recovery mode ?

VINNY

[XenoNorth]

No, the boot partition is not full, there is enought (~60 GB) free disk space. I can also boot to recovery mode... but actually this is not even necessary, because the system is booting as usual, just not the graphical interface :/

[vinnywright]

No, the boot partition is not full, there is enought (~60 GB) free disk space

,,,,I asked about the root partition "/" not /boot ,,,,,do you realy have a 60Gib /boot partition ?.

I can also boot to recovery mode... but actually this is not even necessary, because the system is booting as usual, just not the graphical interface :/

it may be necessary to repair the system ,,,,,,,,,just what do you meen by "the system is booting as usual, just not the graphical interface" do you get to the login screen? if no it is not booting as usual!!

VINNY

[XenoNorth]

Yes, sorry, i was (obviously) talking about the root partition. And no, i don't get the login screen, that is true. But otherwise the system seems to boot up normally, as i have said before, the only problem shown in dmesg is related to lightdm. While the system won't give me the login screen, it is possible to switch to a console screen and login.

[vinnywright]

ok then ,,,,,,log in to the console and do a

sudo apt-get update && sudo apt-get dist-upgrade

do you get any errors?

if yes post them ,,,,,,,,,as best you can.

VINNY

[SteveRiley]

The error Number of created screens does not match number of detected devices is likely to be a hint of some kind. Can you press Ctrl+Alt+F2 and switch to a TTY console? If so, whether you have the file /etc/X11/xorg.conf. If it exists, paste its contents into a reply here.

[ltorgo]

I have the same exact problem. Any working solution please?

[ltorgo]

I'll try to add more information. I did it on the previous post but these forums kept telling me something on links (I had no link at all on my post), and I gave up... I'm new to these forums, so I may be doing something wrong...

I have 14.01.1 LTS and added the kubuntu backports to get kde 4.14 on my previously working perfectly kubuntu (how I regret it!!!). After the upgrade and reboot it just doesn't pass the boot logo. Still compared to the previous problem report, I only have errors at the x-0-greeter.log file. The rest are without problems...

I read somewhere on trying to purge and install again nvidia-current. Did it but installing nvidia-current installs nvidia 304 I think and I had working with nvidia-331. Anyway did not work and I re-installed nvidia-331...

Thanks for any hints/help. If there is some magic way of reverting the KDE upgrade that would be perfect...

I may also add that I'm able to enter recovery mode and do a resume boot, but I get very low resolution though a "working" desktop...

[otisklt]

I have had a similar instance recently, though different video setup.
I ended up booting into recovery mode, uninstalling the amd proprietary drivers and replacing the working xorg.config with a backup, then rebooting into a basic desktop using whatever open source amd driver was working at the time of installation. Then reinstalled the amd proprietary drivers again and things are fine.

This process will require you to have a backed up xorg.config that worked at some point.

[ltorgo]

Hi itisklt,

Thanks for your reply.

I end up solving it a few days back by adding the xorg-edgers ppa and runing apt-get update on my drivers.

What I do not understand is how I had a perfectly working nvidia setup and by upgrading to kde 4.14 end up destroying that working nvidia... but anyway I solved it so no worries ;-)
Thanks