kded

kded keeps crashing or terminating. This effects reading email, mounting
thumbdrives and using My Computer (sysinfo:/).

Using tail -f .xsession-errors, I see the following:

KDE Daemon (kded) already running.
DCOP aborting call from 'konqueror-12043' to 'kded'
DCOP aborting call from 'anonymous-20639' to 'kded'

The workaround I use is:
kded --check && kded --new-startup

kded will then work, but will crash/stop running shortly after. Especially,
if I right click and try to add a folder to my thumbdrive (via media:/).

I'm using openSUSE 10.2 with KDE 3.5.8 release 21.2.

This has been happening for a very long time now. I thought fixed rpms would
be available by now.

Thanks,

--
Alvin

Alvin,

this isn't a common problem. Do you have any idea what would trigger the crash?

Uwe


--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

Uwe Buckesfeld wrote:

> Alvin,
>
> this isn't a common problem. Do you have any idea what would trigger the
> crash?
>
> Uwe
>
>

I have noticed it occurs when I do either of the follow:

* start kmail. kmail will then go into offline mode and will not work. I
restart kded, then immediately restart kmail and kmail works

* In My Computer (sysinfo:/), if I right click anywhere, the context menu
takes several seconds to appear. Then the icons in My Computer revert to
the default, empty icon. kded needs to then be restarted

* If browsing my thumbdrive (via the media:/ protocol), and I right click on
a folder or try to make a folder, kded will stop working. kded will then
need to be restarted.

--
Alvin

Alvin,

please create a new (dummy) user and see if it happens for the new user too.

Uwe

Hello Uwe,

The problem exists for a new user and for root. I have learned that this
problem doesn't occur in 10.3. So, in the process of backup up my files, I
have discovered the error message: "KDE mediamanager is not running". I
came across the error message while looking at the properties of my
thumbdrive (to see available free space).

It seems that when I right-click and select Properties, there is a
considerable delay (of the order of 10 seconds) before the context menu
appears. I'm guessing that's when kded or "KDE mediamanager" dies?

I managed to backup my files and I'm just about to do a (fresh) install. I
wanted to hold off upgrading my work machine, but having to restart kded
continuously is very distracting to say the least

I hope this doesn't manifest into 10.3's KDE environment.

Cheers,

Alvin

Uwe Buckesfeld wrote:

> Alvin,
>
> please create a new (dummy) user and see if it happens for the new user
> too.
>
> Uwe

--
Alvin

On 11/19/2007 Alvin wrote:
> I managed to backup my files and I'm just about to do a (fresh)
> install. I wanted to hold off upgrading my work machine, but having
> to restart kded continuously is very distracting to say the least
> I hope this doesn't manifest into 10.3's KDE environment.

Good luck! Please report back!

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

Uwe Buckesfeld wrote:

> On 11/19/2007 Alvin wrote:
>> I managed to backup my files and I'm just about to do a (fresh)
>> install. I wanted to hold off upgrading my work machine, but having
>> to restart kded continuously is very distracting to say the least
>> I hope this doesn't manifest into 10.3's KDE environment.
>
> Good luck! Please report back!
>
> Uwe
>

So far the install went smoothly. The only issue I have is that kded is now
crashing (segfault) when I logout/shutdown/restart. I have done some
investigating and its a known bug since RC2!?!

From what I can tell, the crash is related to dbus and my NFS mounts of
which I have 2 (and at time 4). If I manually umount them, then logout,
kded does not crash. My mount settings are simply just "defaults".

The crashing kded doesn't seem to prevent the computer from completing the
logout or shutdown. It's just annoying.

I also tried to get compiz-fusion to work but it would not. I have an Intel
865G (I believe). I was hoping that the new intel driver would work where
the i810 driver (in 10.2) was too slow (compiz worked but it was too slow).

All-in-all, I think 10.3 is great.
--
Alvin

* Alvin wrote, On 11/21/2007 01:44 PM:

> So far the install went smoothly. The only issue I have is that kded is now
> crashing (segfault) when I logout/shutdown/restart. I have done some
> investigating and its a known bug since RC2!?!

Bug number, please?

> I also tried to get compiz-fusion to work but it would not. I have an Intel
> 865G (I believe). I was hoping that the new intel driver would work where
> the i810 driver (in 10.2) was too slow (compiz worked but it was too slow).

The intel driver should be better than the i810, but sometimes the blacklist is a little picky (it was about my X3100). I suggest you start a new thread on this topic, though.

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.

Uwe Buckesfeld wrote:

> * Alvin wrote, On 11/21/2007 01:44 PM:
>
>> So far the install went smoothly. The only issue I have is that kded is
>> now crashing (segfault) when I logout/shutdown/restart. I have done some
>> investigating and its a known bug since RC2!?!
>
> Bug number, please?

Sure, here's the link.
https://bugzilla.novell.com/show_bug.cgi?id=332102

It appears to be marked "Resolved"???


>
>> I also tried to get compiz-fusion to work but it would not. I have an
>> Intel 865G (I believe). I was hoping that the new intel driver would work
>> where the i810 driver (in 10.2) was too slow (compiz worked but it was
>> too slow).
>
> The intel driver should be better than the i810, but sometimes the
> blacklist is a little picky (it was about my X3100). I suggest you start a
> new thread on this topic, though.
>
> Uwe
>

I will eventually. I thought I would give compiz a shot in 10.3 cause it
didn't work in 10.2. When I try to get it going again, I will post here if
I have any questions.

Thanks.

--
Alvin

On 11/22/2007 Alvin wrote:
> Sure, here's the link.
> https://bugzilla.novell.com/show_bug.cgi?id=332102 It appears to be
> marked "Resolved"???

Because the reporter didn't communicate any more, it seems. You could re-open the bug. I see something whoch looks like a solution, did you try that? Comment #21 and the following ones.

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.