This forum has been archived. All content is frozen. Please use KDE Discuss instead.

ksmserver could not be started

Tags: None
(comma "," separated)
User avatar
trixl
Registered Member
Posts
30
Karma
0
OS

ksmserver could not be started

Wed Jan 25, 2012 9:36 pm
Hi,

today I updated my KDE 4.7.4 to 4.8 using the rpms for opensuse 11.4.
Now kde doesn't start anymore and tells me that the ksmserver could not be started. Does anyone has an idea as to why this happens?

Thx.
User avatar
Hans
Administrator
Posts
3304
Karma
24
OS

Re: ksmserver could not be started

Wed Jan 25, 2012 9:41 pm
Are you sure you have updated all your packages?


Problem solved? Please click on "Accept this answer" below the post with the best answer to mark your topic as solved.

10 things you might want to do in KDE | Open menu with Super key | Mouse shortcuts
User avatar
trixl
Registered Member
Posts
30
Karma
0
OS

Re: ksmserver could not be started

Thu Jan 26, 2012 7:37 am
yes, all packages seem to have been updated. I used this repository:

http://download.opensuse.org/repositori ... SUSE_11.4/

I get the following trace:

Application: KDE Daemon (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6 0x00000000000c1688 in ?? ()
#7 0x00007f123e5d1cb6 in ?? () from /usr/lib64/libqca.so.2
#8 0x00007f1234427e50 in ?? () from /usr/lib64/kde4/kded_powerdevil.so
#9 0x0000000000000004 in ?? ()
#10 0x00007fffdb6926b8 in ?? ()
#11 0x00007f123e534fbb in _init () from /usr/lib64/libqca.so.2
#12 0x00007f123442b486 in ?? () from /usr/lib64/kde4/kded_powerdevil.so
#13 0x00007f124bfa2789 in call_init () from /lib64/ld-linux-x86-64.so.2
#14 0x00007f124bfa28c7 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#15 0x00007f124bfa6c8a in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#16 0x00007f124bfa25f6 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#17 0x00007f124bfa65da in _dl_open () from /lib64/ld-linux-x86-64.so.2
#18 0x00007f12474a7f26 in dlopen_doit () from /lib64/libdl.so.2
#19 0x00007f124bfa25f6 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#20 0x00007f12474a84cc in _dlerror_run () from /lib64/libdl.so.2
#21 0x00007f12474a7fd1 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#22 0x00007f124ad9b43b in QLibraryPrivate::load_sys (this=0x7e3210) at plugin/qlibrary_unix.cpp:209
#23 0x00007f124ad97eb4 in QLibraryPrivate::load (this=0x7e3210) at plugin/qlibrary.cpp:466
#24 0x00007f124ad9819b in QLibraryPrivate::loadPlugin (this=0x7e3210) at plugin/qlibrary.cpp:516
#25 0x00007f124b32a1a0 in KPluginLoader::load() () from /usr/lib64/libkdecore.so.5
#26 0x00007f124b32a61b in KPluginLoader::factory() () from /usr/lib64/libkdecore.so.5
#27 0x00007f12399081f3 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#28 0x00007f123990941d in ?? () from /usr/lib64/libkdeinit4_kded4.so
#29 0x00007f123990bbd1 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#30 0x00007f124bb69c52 in ?? () from /usr/lib64/libkdeui.so.5
#31 0x00007f124bb69cd4 in ?? () from /usr/lib64/libkdeui.so.5
#32 0x00007f124bb69e0b in ?? () from /usr/lib64/libkdeui.so.5
#33 0x00007f1247b43ae8 in QDBusConnectionPrivate::deliverCall (this=0x66fa10, object=0x79deb0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:947
#34 0x00007f1247b44c6e in QDBusConnectionPrivate::activateCall (this=0x66fa10, object=0x79deb0, flags=337, msg=...) at qdbusintegrator.cpp:850
#35 0x00007f1247b45561 in QDBusConnectionPrivate::activateObject (this=0x66fa10, node=..., msg=..., pathStartPos=<value optimized out>) at qdbusintegrator.cpp:1423
#36 0x00007f1247b4577b in QDBusActivateObjectEvent::placeMetaCall (this=0x78e660) at qdbusintegrator.cpp:1537
#37 0x00007f124adbf776 in QObject::event (this=0x7fffdb691680, e=<value optimized out>) at kernel/qobject.cpp:1204
#38 0x00007f1249f09b86 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#39 0x00007f1249f074e4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#40 0x00007f1249f0fb4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#41 0x00007f124bb63a86 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#42 0x00007f124adaad2c in QCoreApplication::notifyInternal (this=0x7fffdb691680, receiver=0x7fffdb691680, event=0x78e660) at kernel/qcoreapplication.cpp:876
#43 0x00007f124adae328 in sendEvent (receiver=0x0, event_type=0, data=0x615740) at kernel/qcoreapplication.h:231
#44 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x615740) at kernel/qcoreapplication.cpp:1500
#45 0x00007f124add9b83 in sendPostedEvents (s=<value optimized out>) at kernel/qcoreapplication.h:236
#46 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#47 0x00007f1246596bd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#48 0x00007f12465973b0 in ?? () from /lib64/libglib-2.0.so.0
#49 0x00007f1246597650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#50 0x00007f124add9d1f in QEventDispatcherGlib::processEvents (this=0x617770, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#51 0x00007f1249fad85e in ?? () from /usr/lib64/libQtGui.so.4
#52 0x00007f124ada9e02 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#53 0x00007f124adaa07d in QEventLoop::exec (this=0x7fffdb6915d0, flags=...) at kernel/qeventloop.cpp:204
#54 0x00007f124adae7cb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#55 0x00007f1239907967 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#56 0x0000000000407269 in _start ()
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: ksmserver could not be started

Sun Jan 29, 2012 9:06 am
Please install the debugging symbols for QCA and Power Devil. Dr Konqi should be able to help you do this (hopefully the SUSE folks have it configured for their package manager - Zypper).


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
einar
Administrator
Posts
3402
Karma
7
OS

Re: ksmserver could not be started

Sun Jan 29, 2012 9:55 am
There was mix and match of packages in the 4.8 repositories for openSUSE. As far as I can tell, this should be fixed now. Try from terminal using zypper dup --from <your KDE48 repository name>. If the issue persists you should check https://build.opensuse.org/project/moni ... lease%3A48 and upgrade when all packages are marked green.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Sun Feb 12, 2012 6:39 pm
Nearly the same problem for me.
OpenSUSE 11.4 64-bit, KDE 4.8, using the KDE Core Repo to update (same as mentioned above).
I have updated yesterday and can't login. I don't run in exactely the same error message as above, but the effect is the same. Writing this from my notebook an will come back later with the exact error message.

Things, I have tried so far:
- downgrade to KDE 4.7 and the openSUSE 11.4 Repo -> same error!
- zypper dup --from KDE_4.8_Core -> "Nothing to do"
- renamed .kde4 folder in home directory

State for all packages in KDE status monitor when switching back to 4.8 is "succeeded"

Additionally I have crosschecked all installed packages of the KDE Core Repo to the ones installed on my notebook, where everything runs fine.

At this point I am really at the end with good ideas.
Therefore any help is really welcome.

Thanks in advance
Holger

Here is the error message:

Application: KDE-Dienst (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6 0x00000000000c1688 in ?? ()
#7 0x00007fca4ad1fcb6 in ?? () from /usr/lib64/libqca.so.2
#8 0x00007fca40d30e50 in ?? () from /usr/lib64/kde4/kded_powerdevil.so
#9 0x0000000000000004 in ?? ()
#10 0x00007fffab920d18 in ?? ()
#11 0x00007fca4ac82fbb in _init () from /usr/lib64/libqca.so.2
#12 0x00007fca40d34486 in ?? () from /usr/lib64/kde4/kded_powerdevil.so
#13 0x00007fca586ef789 in call_init () from /lib64/ld-linux-x86-64.so.2
#14 0x00007fca586ef8c7 in _dl_init_internal () from /lib64/ld-linux-x86-64.so.2
#15 0x00007fca586f3c8a in dl_open_worker () from /lib64/ld-linux-x86-64.so.2
#16 0x00007fca586ef5f6 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#17 0x00007fca586f35da in _dl_open () from /lib64/ld-linux-x86-64.so.2
#18 0x00007fca53bf5f26 in dlopen_doit () from /lib64/libdl.so.2
#19 0x00007fca586ef5f6 in _dl_catch_error () from /lib64/ld-linux-x86-64.so.2
#20 0x00007fca53bf64cc in _dlerror_run () from /lib64/libdl.so.2
#21 0x00007fca53bf5fd1 in dlopen@@GLIBC_2.2.5 () from /lib64/libdl.so.2
#22 0x00007fca574e843b in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007fca574e4eb4 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007fca574e519b in ?? () from /usr/lib64/libQtCore.so.4
#25 0x00007fca57a771a0 in KPluginLoader::load() () from /usr/lib64/libkdecore.so.5
#26 0x00007fca57a7761b in KPluginLoader::factory() () from /usr/lib64/libkdecore.so.5
#27 0x00007fca462311f3 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#28 0x00007fca4623241d in ?? () from /usr/lib64/libkdeinit4_kded4.so
#29 0x00007fca46234bd1 in ?? () from /usr/lib64/libkdeinit4_kded4.so
#30 0x00007fca582b6c52 in ?? () from /usr/lib64/libkdeui.so.5
#31 0x00007fca582b6cd4 in ?? () from /usr/lib64/libkdeui.so.5
#32 0x00007fca582b6e0b in ?? () from /usr/lib64/libkdeui.so.5
#33 0x00007fca54291ae8 in ?? () from /usr/lib64/libQtDBus.so.4
#34 0x00007fca54292c6e in ?? () from /usr/lib64/libQtDBus.so.4
#35 0x00007fca54293561 in ?? () from /usr/lib64/libQtDBus.so.4
#36 0x00007fca5429377b in ?? () from /usr/lib64/libQtDBus.so.4
#37 0x00007fca5750c776 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#38 0x00007fca56656b86 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#39 0x00007fca566544e4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#40 0x00007fca5665cb4f in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#41 0x00007fca582b0a86 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#42 0x00007fca574f7d2c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#43 0x00007fca574fb328 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#44 0x00007fca57526b83 in ?? () from /usr/lib64/libQtCore.so.4
#45 0x00007fca52ce4bd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#46 0x00007fca52ce53b0 in ?? () from /lib64/libglib-2.0.so.0
#47 0x00007fca52ce5650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#48 0x00007fca57526d1f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#49 0x00007fca566fa85e in ?? () from /usr/lib64/libQtGui.so.4
#50 0x00007fca574f6e02 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#51 0x00007fca574f707d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#52 0x00007fca574fb7cb in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#53 0x00007fca46230967 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#54 0x0000000000407269 in _start ()
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: ksmserver could not be started

Tue Feb 14, 2012 2:26 am
Your backtrace comes from QCA2/Powerdevil in KDE Daemon - so make sure they are all coming from the appropriate repository.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Tue Feb 14, 2012 9:43 pm
Thanks for taking time to answer.
Unfortunately this did not help. libqca2 is installed from 4.8 Core and also kdebas4-workspace, which contains kded_powerdevil.so, is installed from the same Repo. I then checked glibc (next entry in the trace) and downgraded to a prior version, also without success.
The last thing I checked so far was everything around kdelibs4, because this package contains libkdeinit4_kded4.so, which is the last entry in the crash report. I found that kdelibs4-branding-openSUSE was installed, which was not from the 4.8 Core Repo but from OpenSUSE 11.4. I changed this package agains kdelibs4-branding-upstream. No change.
RDX0rz
Registered Member
Posts
2
Karma
0
OS

Re: ksmserver could not be started

Wed Feb 15, 2012 8:07 am
Similar problem. Newly installed Slackware 13.34 on old Pentium III box. KDE starts with the initial screen, shows disk icon, tools icon, ... but at the 4th icon and while its still fuzzy the screen goes black and stays like that. Other X11 desktops work, only KDE doesn't. Version 4.4, log mentions Segmentation fault (maybe also inability to connect to socket). Previously tried Kubuntu 10.04, it worked but I couldn't make the screen resolution what I wanted (1280x768) and other issues not KDE related, hence Slackware.
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Wed Feb 15, 2012 8:43 pm
Checked now all installed packages of KDE found under KDE-Desktop in YaST. Found three additional packages, which are not installed from 4.8 Repo:
kdebase4-openSUSE
kdebase-runtime-branding-openSUSE
dkm-branding-openSUSE

I was pretty sure that changing theses 3 packages to the KDE 4.8 repository would solve the problem, but didn't.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: ksmserver could not be started

Thu Feb 16, 2012 12:24 am
Is Qt installed from the 4.8 repository?


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Thu Feb 16, 2012 7:30 pm
Yes, QT is installed from 4.8 repository. I have checked every single installed package and can't find one, which is offered by the KDE 4.8 Core repository, but is installed from another one.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS

Re: ksmserver could not be started

Fri Feb 17, 2012 7:24 am
If you can login to a semi-functional desktop, could you try opening System Settings > Startup & Shutdown > Service Manager, and disabling all "Startup Services". Then try to login again and see if it crashes.

If it does not, try enabling them one by one until it crashes on startup, then report back here with the name of that module.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Fri Feb 17, 2012 4:12 pm
Thanks for thiniking about my problem, bcooksley!

Disabling the startup services seemed to be a good idea, but did not help either. The only difference is that the crash notification window is not opened anymore, the ksmserver error message still is shown.

I tried to start all services manually, while logged in using LXDE as temporarily desktop environment. All services are shown as "running". So the services are problably not the key.

While using LXDE I had no problems so far to use all of the KDE apps.
kantenschwein
Registered Member
Posts
20
Karma
0
OS

Re: ksmserver could not be started

Fri Feb 17, 2012 9:46 pm
Another thing, I don't understand:
I have a lot of xxx-branding-yyy packages installed. All of them are available as branding-upstream and also as branding-openSUSE in KDE 4.8 Core. I have installed all the branding-openSUSE packages. What I don't understand is the versioning of the packages. Sometimes the installed branding-openSUSE has version 4.8 and the branding-upstream 11.4 and sometimes it is vice versa.

Example:
installed: kdebase4-runtime-branding-openSUSE 11.4-33.5.2
available: kdebase4-runtime-branding-upensuse 4.8

Any idea, which packages have to be installed?


Bookmarks



Who is online

Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]