Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#2872 - KDE-Daemon crash after kdebase update 3.4.1-2

Attached to Project: Arch Linux
Opened by Berger (Berger) - Saturday, 25 June 2005, 10:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

The KDE-Daemon kded crashes 10 times after the update of kdebase 3.4.1-2.

This is the error message:

5228: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 2749
5228: assertion failed "(error) == NULL || dbus_error_is_set ((error))" file "dbus-bus.c" line 854 funtion send_no_return_values
kbuildsycoca running...
... the previous error once again ...
Last DCOP call before KDED crash was from application 'DCOPSERVER' to object '', function 'applicationRemoved(QCString)'
KCrash: Application 'kded' crashing...

Berger
(application/octet-stream)    kdebase-bug-backtrace (4.3 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 26 June 2005, 16:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in -3
Comment by Torsten Evers (Nightwulf) - Saturday, 25 June 2005, 10:51 GMT
I can second the bug. After downgrade to kdebase 3.4.1-1 all problems are gone.

Greets,
Torsten
Comment by Jan de Groot (JGC) - Saturday, 25 June 2005, 11:45 GMT
slay all your KDE applications, services and daemons on every upgrade. Actually, it's in the wiki, but hey, nobody reads that anyways.
Comment by Torsten Evers (Nightwulf) - Saturday, 25 June 2005, 12:39 GMT
Well, I did the upgrade (like I do *every time* I upgrade KDE-stuff) with KDE/X/KDM stopped. Please don't be that fast with prejudging of people reporting issues they think of beeing a bug. I'm using KDE since the very beginning so please stay serious.
Btw as I said, after downgrading to 3.4.1-1 the problems were *gone*.

Greets,
Torsten
Comment by Tobias Powalowski (tpowa) - Saturday, 25 June 2005, 12:57 GMT
i also cannot confirm that issue, on my system it just works, JGC comment was more a joke ;)
try to reinstall kde and keep all your packages up to date.
Comment by Torsten Evers (Nightwulf) - Saturday, 25 June 2005, 14:14 GMT
Strange joke, really :-/

but back to topic:

I don't see any reason to use the sledgehammer method of un- and reinstalling kde without any hint why this occurs. To find out from which reason these crashes occur, I created a fresh user while having kdebase-3.4.1-1 installed, then stoped all kde, kdm, X programs (verfied afterwards, that NONE is running) and upgraded to 3.4.1-2. Same crashes of kded occured.
I'll verify kdebase-3.4.1-1 PKGBUILD and the actual one to see, what changed. There must be a change causing this.
Oh, and btw: not all errors occur on every machine so there's no point in saying "this doesn't happen here".
I'll post all results of my search here.

Greets,
Torsten
Comment by Tobias Powalowski (tpowa) - Saturday, 25 June 2005, 15:24 GMT
are you running dbus and hal in daemon array?
new kdebase was built against new dbus and hal .
Comment by Torsten Evers (Nightwulf) - Saturday, 25 June 2005, 18:56 GMT
That was the solution...the new kdebase installed dbus and hal but there was no hint that they now need to be running for kde to work properly. That should be added with kdebase-3.4.1-3.
I guess the bug can be closed then.
Jan: as you can obviously see, there was a _serious_ reason for the crashes...and in addition, an avoidable reason. The wiki says, one should add hal/dbus to rc.conf DAEMONS variable if full multimedia functionalitiy is needed and I (and not only my person) try to reduce the number of daemons running all the time to the minimum and don't use many multimedia apps.
Anyway...thanks for your help.

Greets,
Torsten

Comment by Jan de Groot (JGC) - Saturday, 25 June 2005, 22:43 GMT
Well, why I was saying things like that was because someone actually reported exactly the same bug two days ago and told me to close it because it worked after a reboot...

After taking a closer look to your real error message, it seems KDE doesn't handle the case where dbus/hal is unreachable, and crashes instead of failing to run. I got this patch from KDE HEAD, but it needs quite some work I think... until now, KDE is the worst program when it comes to clean hal/dbus code. I'll rewrite their hal/dbus backend from scratch tomorrow if I get the time for it.
Comment by Torsten Evers (Nightwulf) - Saturday, 25 June 2005, 22:56 GMT
Jan, I didn't ment to attack someone personally of course. It's just that I'm with linux and kde since 1997 and I had to notice some kind of "arrogance" in the developer (not special to a certain distribution) circles during the last months which of course could be caused by the masses entering the linux area nowadays.
This was one main reason to switch from gentoo to arch because I thought the approach of arch with the user repositories and AUR seemed to be more liberal than the portage way.
And your remark concerning the wiki caused me to think of this RTFM stuff common in many communities today.
So please don't be too upset, k? :)

Greets,
Torsten

Comment by Berger (Berger) - Sunday, 26 June 2005, 09:33 GMT
Thanks a lot ! Adding hal and dbus to the daemon array solves this problem.
This bug can be closed.

Berger
Comment by Jan de Groot (JGC) - Sunday, 26 June 2005, 13:02 GMT
Well, in fact... kded should notice dbus is not running and switch to the old method without hal instead.

What happens when dbus is not running, is that an uninitialized hal context gets a shutdown. The shutdown function frees the dbus connection assigned to the context, but there is no dbus connection at all, so you get a segmentation fault in kded.

I debugged the problem for a while now and it seems like my final patch will work. The assertion errors are gone with the new version and kde media:/ will safely switch to fstab lookups if hal and/or dbus aren't running.

Loading...