Version: (using KDE 4.4.1) OS: Linux Installed from: Ubuntu Packages This current bug filed here is related to another installation of ubuntu Lucid alpha3 on another 64 bit machine ; I had experienced apparently the same bug when upgrading KDE at one time on this machine (the one I am writing this message with) where I did not get any help and where I had to reinstall completely the distribution as there is no way to safely remove globally KDE for re-installation on a machine where other desktops such as Gnome are presents. Here the problem arose after upgade from 9.04 Karmic to Lucid 10.04 ; I had after the upgrade both Gnome and KDE running but in "low resolution mode" with my 4850hd ATI graphic card ; the "fglrx" driver was no longer usable (and apparentltly it is still the case) ; then I removed it + all "fglrx" packages associated in the new distro and installed the package "xserver-xorg-video-radeon" with the associated settings in "xorg.conf" ; from there on I could use my 4850hd ATI graphic card with some 3D effects, like the 3d desktop, with Gnome but no way to open a KDE session as after logging and a display of the desktop with the first icon showing there is a crash with no error message ; consequently I need some help to debug as I do not know where KDE log its internal messages at logging time. Regards.
you are most probably seeing an x server crash. /var/log/Xorg.log.0.old might give a clue.
nope nothing of interest inside /var/log/Xorg.log.0 which is not a surprise because my feeling is that it has todo with the installation process of the KDE session as a matter of fact at the time when the setting is handled as the secong "setting" icon is not even displayed ; so I thenk it has more to do with in KDE setting someting that has todo with previous "fglrx" interface somehow but I may be wrong. So the problem is when KDE is being installed wherer can we collect a log of the process to see what is wrong ?
this is something that belongs in the ubuntu support forums before it is brought here. there is nothing in kde that prevents uninstal-reinstall cycles and it is almost certainly a packaging/distro issue to resolve.
As I got no suggestion on the machine where I have my problem with opening a kde session I tried the following to collect error message in a Gnome session : - open a console, - execute $ start kde. This is what I collected : dmoyne@ossau:~$ startkde startkde: Starting up... kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) klauncher(1765)/kio (KIOConnection) KIO::ConnectionServer::listenForRemote: Listening on "local:/tmp/ksocket-dmoyne/klauncherMT1765.slave-socket" kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so kded(1768): Failed to lock file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.lock" , last result = 2 kded(1768): Couldn't create index file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.index" kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so klauncher(1765)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/kbuildsycoca4" (pid 1771) up and running. kbuildsycoca4 running... kbuildsycoca4(1771)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/dmoyne/.kde/cache-ossau.bearn/ksycoca4" kbuildsycoca4(1771) KBuildSycoca::checkTimestamps: checking file timestamps kbuildsycoca4(1771) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(1771) kdemain: Emitting notifyDatabaseChanged () kded(1768)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/dmoyne/.kde/cache-ossau.bearn/ksycoca4" klauncher(1765)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/dmoyne/.kde/cache-ossau.bearn/ksycoca4" kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so klauncher(1765)/kio (KLauncher) KLauncher::processRequestReturn: "kconf_update" (pid 1772) up and running. Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kded(1768)/kdecore (KLibrary) kde4Factory: The library "/usr/lib/kde4/solid_hal_power.so" does not offer a qt_plugin_instance function. Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection klauncher(1765)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/dmoyne/.kde/cache-ossau.bearn/ksycoca4" kdeinit4: preparing to launch /usr/lib/libkdeinit4_kglobalaccel.so klauncher(1765)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/kglobalaccel" (pid 1804) up and running. kglobalaccel(1805): Failed to lock file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.lock" , last result = 2 kglobalaccel(1805): Couldn't create index file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.index" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "kmix" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "kwin" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "krunner" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "kxkb" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "plasma-desktop" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "amarok" kglobalaccel(1805) GlobalShortcut::setKeys: "decreaseVolume" skipping because key "" is already taken kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "kded" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "kopete" kglobalaccel(1805) GlobalShortcutsRegistry::loadSettings: Loading group "klipper" kglobalaccel(1805) GlobalShortcutsRegistry::registerKey: Registering key "Monitor Brightness Up" for "kded" : "Increase Screen Brightness" kglobalaccel(1805) KGlobalAccelImpl::grabKey: grab failed! kglobalaccel(1805) GlobalShortcut::setActive: "Increase Screen Brightness" : Failed to register "Monitor Brightness Up" kglobalaccel(1805) GlobalShortcutsRegistry::registerKey: Registering key "Monitor Brightness Down" for "kded" : "Decrease Screen Brightness" kglobalaccel(1805) KGlobalAccelImpl::grabKey: grab failed! kglobalaccel(1805) GlobalShortcut::setActive: "Decrease Screen Brightness" : Failed to register "Monitor Brightness Down" kded(1768)/kded4 Kded::loadModule: Successfully loaded module "powerdevil" kded(1768)/kded4 Kded::loadModule: Successfully loaded module "statusnotifierwatcher" QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString) QObject::connect: Cannot connect (null)::accessibilityChanged(bool, const QString) to DeviceAutomounter::deviceMountChanged(bool, const QString) kded(1768)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kded(1768)/kded4 Kded::loadModule: Successfully loaded module "device_automounter" QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.51' kded(1768)/plasma StatusNotifierWatcher::RegisterStatusNotifierItem: Registering ":1.9/org/ayatana/NotificationItem/gnome_power_manager" to system tray kdeinit4: preparing to launch /usr/lib/libkdeinit4_kcminit_startup.so kcminit(1809): Failed to lock file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.lock" , last result = 2 kcminit(1809): Couldn't create index file "/home/dmoyne/.kde/cache-ossau.bearn/kpc/kde-icon-cache.index" kcminit(1809)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/home/dmoyne/.kde/cache-ossau.bearn/ksycoca4" kdeinit4: preparing to launch /usr/lib/libkdeinit4_ksmserver.so <unknown program name>(1764)/ KStartupInfo::createNewStartupId: creating: "ossau.bearn;1268471531;338267;1764_TIME0" : "unnamed app" Could not open library ksmserver: Cannot load library /usr/lib/libkdeinit4_ksmserver.so: (libatiuki.so.1: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type) ksmserver: error while loading shared libraries: libatiuki.so.1: cannot open shared object file: No such file or directory startkde: Shutting down... klauncher: Exiting on signal 1 kglobalaccel(1805) GlobalShortcutsRegistry::unregisterKey: Unregistering key "Monitor Brightness Up" for "kded" : "Increase Screen Brightness" kglobalaccel(1805) GlobalShortcutsRegistry::unregisterKey: Unregistering key "Monitor Brightness Down" for "kded" : "Decrease Screen Brightness" startkde: Running shutdown scripts... startkde: Done. Though proceeding like this I mean opening a kede session from a live Gnome session could generate procedure realted erroe messages I think this should help understand the problem with the incriminated libs : libkdeinit4_ksmserver.so and libatiuki.so.1 which for the latter apparently is a library installed with "fglrx" driver and that is no more there ! So it looke lije this
something (ksmserver or a library it depends on) is built against the ati driver stuff, which is now missing. this is an installation problem (or a packaging problem if you are indeed using packages).
why would kde directly use an "ati" library and if so when installing free driver as now installed with "xserver-xorg-video-radeon" package libkdeinit4_ksmserver.so should then search for another lib associated with this installed driver so the fix shoud be done in "xserver-xorg-video-radeon" ; I will try if it is possible to reinstall it and chack again.
kde links against libgl, which might be replaced by the driver. if the driver uninstall didn't go cleanly, you'd see such effects. try reinstalling libgl*. but i don't know what exactly this libatiuki is, so i don't know what might have decided to link it and for what reasons.
Thanks for your help ; I reinstalled the libs "libgl*" but this did not change anything regarding the bug report as provided in my previous message ; are involved somehow in kde develpment otherwise I wish some kde developers should really do something about this bug.
I had the same problem. Someone told me to show him the ouput of this: ldd /usr/lib/libkdeinit4_ksmserver.so So i sent it to him through pastebin ( http://pastebin.com/PQCfLcJK ) it says, among other things: libatiuki.so.1 => not found then he told me to do this: ldd /usr/lib/libGL.so.1 | grep libatiuki and again: libatiuki.so.1 => not found finally, he told me to remove/rename /usr/lib/libGL.so.1, and that's what I did. After that, I can log in to Kubuntu lucid :D Seems like the ATI uninstaller does not work very well... For now, I'm seeing error messages in System Settings (or whatever is called). Don't know how to resolve them... PS: I'm not very good writing in English, so forgive me if I made a mistake.
Thanks Bartemius the fix works fine : I renamed "/usr/lib/libGL.so.1" into "_libGL.so.1" and this fix that does not make sense made the trick ; like you I do think that the uninstaller supplied by ati and which I executed does not clean properly le installation of the ati proprietary driver ; now the "libatiuki.so.1" not found is no more a problem. Thanks
Happy to see it works for you. Thanks and credits to penguin42 from #ubuntu+1 in freenode. (I just left this "for the record")
A a matter of fact it is not as simple as I thought it was as the file "/usr/lib/libGL.so.1" keeps bieng recreated from time to time ; so now when I no more can log into a KDE session I know that the incriminated file has been recreated and need a deletion !