Login configure problem, perhaps?

[wedgetail]

Background:
On my Workhorse KDE-Mini, I started noticing that Klipper went a bit funny.  I have this configured in Systemtray to pop up with Alt-A, the setting has disappeared and the settings option is now greyed out.

I started looking around in the Configure Your Desktop (CYD) earlier today in the area, a familiarisation excursion and fairly broad.:

CYD > System administration > Login Screen, this was my main interest looking for password-less log in trying to find out if I could set that up.

Later when rebooting I now get consistently to crash screen messages almost similar.

Executable: kcminit_startup PID: 3201 Signal: Segmentation fault (11)

Executable: kded4 PID: 2904 Signal: Segmentation fault (11)

Can close them and get on working, (though Klipper got some lockup on config via sys tray)


I have found one crash message is consistent , the number may change, if I try following, as soon as the last stage clicked, message pops up:

CYD [configure your desktop] > System administration > Login Screen (Configure the login manager KDM)

Executable: systemsettings PID: 9024 Signal: Segmentation fault (11)

I am rather lost as to what may be going on.

[old_guy]

wedgetail

I see you are getting both kcminit_startup and kded4 Segmentation fault. At least for the kded check out:
http://www.pclinuxos.com/forum/index.php/topic,92924.0.html

For the autologin try:
Configure Your Computer > Boot > Set up autologin ...

Earl

[wedgetail]

old_guy

Thanks you, you just gave me enough to kickstart my brain a bit.

For the autologin try:
Configure Your Computer > Boot > Set up autologin ...

This seems to be what I am looking for. I don't need to log in as user, that will save a few key punches.

The two messages will sit neatly in the middle of the screen on top of each other. Only the PID number changes.

I have decided to install gdb and see if that may give some clue.

I did also try to log in as root but the same two message soon said hallo here we meet again,  

(Still not possible to set up keyboard shortcut in tray for Klipper)

Application: KCMInit (kcminit_startup), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.6-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#7  elf_machine_rela_relative (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at ../sysdeps/i386/dl-machine.h:660
#8  elf_dynamic_do_rela (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at do-rel.h:105
#9  _dl_relocate_object (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at dl-reloc.c:268
#10 0x49c6fc06 in dl_open_worker (a=0xbfe6d2d0) at dl-open.c:339
#11 0x49c6c236 in _dl_catch_error (objname=0xbfe6d2f8, errstring=0xbfe6d2f4, mallocedp=0xbfe6d2ff, operate=0x49c6f990 <dl_open_worker>, args=0xbfe6d2d0) at dl-error.c:178
#12 0x49c70196 in _dl_open (file=0x82b4600 "/usr/lib/kde4/kcm_hotkeys.so", mode=-2147483647, caller_dlopen=0x4189dbf4, nsid=-2, argc=1, argv=0xbfe6e4f4, env=0x82b27a8) at dl-open.c:571
#13 0x49e02b7b in ?? () from /lib/libdl.so.2
#14 0x49c6c236 in _dl_catch_error (objname=0x822a07c, errstring=0x822a080, mallocedp=0x822a078, operate=0x49e02ae0, args=0xbfe6d4b0) at dl-error.c:178
#15 0x49e032fc in ?? () from /lib/libdl.so.2
#16 0x49e02c31 in dlopen () from /lib/libdl.so.2
#17 0x4189dbf4 in ?? () from /usr/lib/libQtCore.so.4
#18 0x41898814 in ?? () from /usr/lib/libQtCore.so.4
#19 0x4173d88c in ?? () from /usr/lib/libkdeinit4_kcminit_startup.so
#20 0x4173e076 in ?? () from /usr/lib/libkdeinit4_kcminit_startup.so
#21 0x4173e218 in ?? () from /usr/lib/libkdeinit4_kcminit_startup.so
#22 0x4173e2c4 in ?? () from /usr/lib/libkdeinit4_kcminit_startup.so
#23 0x411ea9bd in ?? () from /usr/lib/libQtDBus.so.4
#24 0x411ebba7 in ?? () from /usr/lib/libQtDBus.so.4
#25 0x411ec278 in ?? () from /usr/lib/libQtDBus.so.4
#26 0x411ec778 in ?? () from /usr/lib/libQtDBus.so.4
#27 0x418c320f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#28 0x43df8e44 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#29 0x43dfddf7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#30 0x44977881 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#31 0x418ad84e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#32 0x418b15bc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#33 0x418b170c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#34 0x418dc004 in ?? () from /usr/lib/libQtCore.so.4
#35 0x41080369 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#36 0x41080b70 in ?? () from /usr/lib/libglib-2.0.so.0
#37 0x41080e2a in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#38 0x418dc18b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#39 0x43eaf94a in ?? () from /usr/lib/libQtGui.so.4
#40 0x418aca5d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#41 0x418accd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#42 0x418b17e0 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#43 0x43df6bc4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#44 0x4173ea09 in ?? () from /usr/lib/libkdeinit4_kcminit_startup.so
#45 0x4173f7f4 in kdemain () from /usr/lib/libkdeinit4_kcminit_startup.so
#46 0x0804866b in _start ()

Application: KDE Daemon (kded4), signal: Segmentation fault
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.2800.6-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#7  elf_machine_rela_relative (scope=0x8432f78, reloc_mode=1, consider_profiling=0) at ../sysdeps/i386/dl-machine.h:660
#8  elf_dynamic_do_rela (scope=0x8432f78, reloc_mode=1, consider_profiling=0) at do-rel.h:105
#9  _dl_relocate_object (scope=0x8432f78, reloc_mode=1, consider_profiling=0) at dl-reloc.c:268
#10 0x49c6fc06 in dl_open_worker (a=0xbfd4be00) at dl-open.c:339
#11 0x49c6c236 in _dl_catch_error (objname=0xbfd4be28, errstring=0xbfd4be24, mallocedp=0xbfd4be2f, operate=0x49c6f990 <dl_open_worker>, args=0xbfd4be00) at dl-error.c:178
#12 0x49c70196 in _dl_open (file=0x840d618 "/usr/lib/kde4/kded_powerdevil.so", mode=-2147483647, caller_dlopen=0x4189dbf4, nsid=-2, argc=1, argv=0xbfd4d2d4, env=0x834fb38) at dl-open.c:571
#13 0x49e02b7b in ?? () from /lib/libdl.so.2
#14 0x49c6c236 in _dl_catch_error (objname=0x836be8c, errstring=0x836be90, mallocedp=0x836be88, operate=0x49e02ae0, args=0xbfd4bfe0) at dl-error.c:178
#15 0x49e032fc in ?? () from /lib/libdl.so.2
#16 0x49e02c31 in dlopen () from /lib/libdl.so.2
#17 0x4189dbf4 in ?? () from /usr/lib/libQtCore.so.4
#18 0x41898814 in ?? () from /usr/lib/libQtCore.so.4
#19 0x418988f8 in ?? () from /usr/lib/libQtCore.so.4
#20 0x418924b3 in QPluginLoader::load() () from /usr/lib/libQtCore.so.4
#21 0x4159d748 in KPluginLoader::load() () from /usr/lib/libkdecore.so.5
#22 0x4159dbbf in KPluginLoader::factory() () from /usr/lib/libkdecore.so.5
#23 0x41742960 in ?? () from /usr/lib/libkdeinit4_kded4.so
#24 0x41743c04 in ?? () from /usr/lib/libkdeinit4_kded4.so
#25 0x417467d6 in ?? () from /usr/lib/libkdeinit4_kded4.so
#26 0x4497e567 in ?? () from /usr/lib/libkdeui.so.5
#27 0x4497e63c in ?? () from /usr/lib/libkdeui.so.5
#28 0x411ea9bd in ?? () from /usr/lib/libQtDBus.so.4
#29 0x411ebba7 in ?? () from /usr/lib/libQtDBus.so.4
#30 0x411ec278 in ?? () from /usr/lib/libQtDBus.so.4
#31 0x411ec778 in ?? () from /usr/lib/libQtDBus.so.4
#32 0x418c320f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#33 0x418ade3a in QCoreApplication::event(QEvent*) () from /usr/lib/libQtCore.so.4
#34 0x43dfb63d in QApplication::event(QEvent*) () from /usr/lib/libQtGui.so.4
#35 0x43df8e44 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#36 0x43dfddf7 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#37 0x44977881 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#38 0x418ad84e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#39 0x418b15bc in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#40 0x418b170c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#41 0x418dc004 in ?? () from /usr/lib/libQtCore.so.4
#42 0x41080369 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#43 0x41080b70 in ?? () from /usr/lib/libglib-2.0.so.0
#44 0x41080e2a in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#45 0x418dc18b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#46 0x43eaf94a in ?? () from /usr/lib/libQtGui.so.4
#47 0x418aca5d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#48 0x418accd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#49 0x418b17e0 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#50 0x43df6bc4 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#51 0x4174207d in kdemain () from /usr/lib/libkdeinit4_kded4.so
#52 0x0804867b in _start ()

That will take some time to plow through 

[wedgetail]

Some more detail.
I turned the user login requirement back on to get back into root. (via Configure your Computer [circle with crossed tools]->password> BOOT>Setup auto login...)

Have logged in as root again to check a bit closer.
KCMINIT
KDED
both shows up, have the backtrace of both and will look and compare before posting to save space.

This time I started open applications and KDED pops up every time. Will check to see if they are identical.

Konqeror --> brought up two KDED

Opera ---> brings up two KDED

I can not use copy/paste from keyboard ctl-c/ctl-v  but mouse copy/paste works I believe that has been a problem all along but I did not realise as I am so used to Klipper and it first now that klipper only works partially that I had to go back the 'old ways'  

I will go back as user and see.

Oooops, I logged out intending to log in again without doing complete reboot, and the system really hangs, I had forgotten that for a long time when logging in as root it will do hang if I attempt to re-login, I have to re-start the system. That works and I am now back in user.
 

[AS]

wedgetail,

see if this (disabling nepomuk) may help 
http://www.pclinuxos.com/forum/index.php/topic,92010.msg771852.html#msg771852

http://www.pclinuxos.com/forum/index.php/topic,91250.msg764980.html#msg764980
http://www.pclinuxos.com/forum/index.php/topic,91250.msg765012.html#msg765012

AS

[wedgetail]

Done a byte comparison of the crash logs.

kded problem centers on following lines

#7  elf_machine_rela_relative (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at ../sysdeps/i386/dl-machine.h:660
#8  elf_dynamic_do_rela (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at do-rel.h:105
#9  _dl_relocate_object (scope=0x82bbc60, reloc_mode=1, consider_profiling=0) at dl-reloc.c:268
#10 0x49c6fc06 in dl_open_worker (a=0xbfe6d2d0) at dl-open.c:339
#11 0x49c6c236 in _dl_catch_error (objname=0xbfe6d2f8, errstring=0xbfe6d2f4, mallocedp=0xbfe6d2ff, operate=0x49c6f990 <dl_open_worker>, args=0xbfe6d2d0) at dl-error.c:178
#12 0x49c70196 in _dl_open (file=0x82b4600 "/usr/lib/kde4/kcm_hotkeys.so", mode=-2147483647, caller_dlopen=0x4189dbf4, nsid=-2, argc=1, argv=0xbfe6e4f4, env=0x82b27a8) at dl-open.c:571


#14 0x49c6c236 in _dl_catch_error (objname=0x8e1a554, errstring=0x8e1a558, mallocedp=0x8e1a550, operate=0x49e02ae0, args=0xbfe18ab0) at dl-error.c:178

The rest in is byte identical using kdiff3

kcminit  problem centers on this

#7  elf_machine_rela_relative (scope=0x83cf808, reloc_mode=1, consider_profiling=0) at ../sysdeps/i386/dl-machine.h:660
#8  elf_dynamic_do_rela (scope=0x83cf808, reloc_mode=1, consider_profiling=0) at do-rel.h:105
#9  _dl_relocate_object (scope=0x83cf808, reloc_mode=1, consider_profiling=0) at dl-reloc.c:268
#10 0x49c6fc06 in dl_open_worker (a=0xbfdf7700) at dl-open.c:339
#11 0x49c6c236 in _dl_catch_error (objname=0xbfdf7728, errstring=0xbfdf7724, mallocedp=0xbfdf772f, operate=0x49c6f990 <dl_open_worker>, args=0xbfdf7700) at dl-error.c:178
#12 0x49c70196 in _dl_open (file=0x83c92f0 "/usr/lib/kde4/kcm_hotkeys.so", mode=-2147483647, caller_dlopen=0x4189dbf4, nsid=-2, argc=1, argv=0xbfdf8924, env=0x83d87c8) at dl-open.c:571

#14 0x49c6c236 in _dl_catch_error (objname=0x830ca3c, errstring=0x830ca40, mallocedp=0x830ca38, operate=0x49e02ae0, args=0xbfdf78e0) at dl-error.c:178

[wedgetail]

as

Go into "Configure Your Desktop", next click on "Workspace Appearance And Behavior", click on "Desktop Search", take away the check in "Enable Nepomuk Semantic Desktop" and click on the apply button at the bottom of the screen.

Not ticked so I should be heading for root to try and see what can be done.  getting a bit sick of rebooting, any konsole command?  

Seems to be getting slightly worse, now I think when I tried to use Klipper by clicking I got another crash message.

Edit:
Made a quick visit to PCC - services, but nepomuk not listed??

[AS]

try here:
system administration -> startup and shutdown -> service manager

[wedgetail]

as
I am in root presently and that whole page you are showing is greyed out ( when I am root ==??? )
Nepomook is ticked.

konsole  

Edit:
Should have added, there is a big red sign saying Unable to contact KDED
the same in user login.

Further seems none of the services listed on the greye out page is running.

[AS]

edit the file   ~/.kde4/share/config/kdedrc
to:

...
[Module-nepomuksearchmodule]
autoload=false
...

will work on black an white terminal 

[wedgetail]

as
 

[gert@localhost config]$ pwd
/home/gert/.kde4/share/config
[gert@localhost config]$

[gert@localhost config]$ ls -l kde*
-rw-r--r-- 1 gert gert 13037 Jan 15 17:32 kdebugrc
-rw-r--r-- 1 gert gert 18053 Jan 23 10:53 kded_device_automounterrc
-rw-r--r-- 1 gert gert  4048 Jan 26 11:48 kdeglobals
[gert@localhost config]$

/home/gert/.kde4/share/config
~/.kde4/share/config/kdedrc

And yet when I was in root, I found the file and added the section you showed.
I used Konqueror to find the file, cheated as I was on the phone at the same time, only one hand.

I must have been dreaming, I have repeated the exercise but did not find the file this time, so now I wonder what file it was I edited. Looked right inside with all those sections.

I have now also looked in two extra backup files for .kde4 and in .kde4/share/config seems I have never had a file kdedrc

I have used as root, updatedb locate no sign of any kdedrc

This has become a challenge  

[AS]

[
This has become a challenge  

Please, consider a reinstall  will take few minutes, (or a little more then ten minutes ...)

[wedgetail]

as
Ouch, is it that bad.    I will check when or if this was rsync'ed it is my Workhorse not the C-Programmer OS    The customisation alone is a long process even with my notes.  I will however consider the situation as serious.

Addition:
file:///root/.kde4.bak.110419
This is a backup from the 19th April 2011 and there is no kdedrc
In your opinion should htere have been one. If this is KDE daemon then rc added seems to indicate something basic but I don't know.   

[AS]

as
Ouch, is it that bad.    I will check when or if this was rsync'ed it is my Workhorse not the C-Programmer OS    The customisation alone is a long process even with my notes.  I will however consider the situation as serious.

No, it's not that bad.
It is that if you have a good backup (mylivecd + personal data) you can restore your system  in very few time. 

Addition:
file:///root/.kde4.bak.110419
This is a backup from the 19th April 2011 and there is no kdedrc
In your opinion should htere have been one. If this is KDE daemon then rc added seems to indicate something basic but I don't know.   

Sorry, don't know. Try google 

[AS]

I saw that file /root/.kde4/share/config/kdedrc when, after turning off nepomuk using GUI, the nepomuk section changed as described before. That's all I know about.