On 02/15/2012 08:43 AM, P Nikolic wrote: > Hi > > I am getting logs full of the following along with bad crazy Kmail behaviour > Also problems writing to my NAS drive i dare say the NAS problem is me not > finding the right setting ( i have been a suse user since suse 5.3 so a long > time with yast) any ideas anyone > > Feb 15 09:38:05 7-of-9 kernel: [ 386.295383] nepomukservices[1462]: segfault > at 100000000 ip 00007fb2b1ba0eef sp 00007fb262ffb6b0 error 4 in > libsoprano.so.4.3.0[7fb2b1b5c000+f9000] > Feb 15 09:38:55 7-of-9 kernel: [ 435.960894] nepomukservices[1512]: segfault > at 100000000 ip 00007fee7771eeef sp 00007fee5dff96b0 error 4 in > libsoprano.so.4.3.0[7fee776da000+f9000] Pete, This is nepomuk going tits up. I don't know if it is nepomuk itself or soprano causing the issue. 17:31 nirvana:~/tdegit> pacman -Qo /usr/lib/libsoprano.so.4.3.0 /usr/lib/libsoprano.so.4.3.0 is owned by soprano 2.7.4-1 > Feb 15 09:41:48 7-of-9 kernel: [ 609.009982] device eth0 entered promiscuous > mode > Feb 15 09:48:51 7-of-9 dbus[514]: [system] Activating service > name='org.kde.powerdevil.backlighthelper' (using servicehelper) > Feb 15 09:48:51 7-of-9 org.kde.powerdevil.backlighthelper: QDBusConnection: > system D-Bus connection created before QCoreApplication. Application may > misbehave. Are you explicitly loading dbus in /etc/rc.conf? If so where? In my setup (still kde3/Trinity) hal loads dbus, so I bring it up after network, but before bind: DAEMONS=(hwclock syslog-ng network hal named @netfs @ntpd @sshd @dhcp4 @crond @postfix @mysqld @dovecot @httpd @hylafax @samba @cupsd @sensors @upsd @spamd @saslauthd !kdm @avahi-daemon) Your log above looks like you have powerdevel/kde4 loading (I presume kdm) almost immediately after network. You may want to try dbus earlier in the list. See: https://wiki.archlinux.org/index.php/Rc.conf <snip other D-Bus messages> > Feb 15 10:39:30 7-of-9 dbus[514]: [system] Successfully activated service > 'org.kde.powerdevil.backlighthelper' What is loading powerdevil.backlighthelper? kdm? I don't run kde4 or kdm, but it looks like it wants dbus up and running. <snip> > Cheers Pete > Others will have to step in and give more specifics. That's all the guesses I have. -- David C. Rankin, J.D.,P.E.
