Is this expected?
It's new in f22 AFAICT.
$ kdialog --title "Test" --passivepopup "Test" 2 kdialog(10183)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kdialog' crashing...
I understand that the following works just fine but I'm just wondering if anyone knows if this is the way it's meant to be now and what the reasoning is?
$ export $(dbus-launch) && kdialog --title "Test" --passivepopup "Test" 2
Thanks, Brad
Brad Hubbard wrote:
Is this expected?
It's new in f22 AFAICT.
$ kdialog --title "Test" --passivepopup "Test" 2 kdialog(10183)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kdialog' crashing...
It's not expected that your kde login not have an active dbus session. If that's really the case, hardly anything will work.
To verify, does this return anything useful? $ echo $DBUS_SESSION_BUS_ADDRESS
it should return something like: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yC5KUykdT
I guess it's also arguable that kdialog should fail more gracefully than crash in that situation too.
-- Rex
----- Original Message -----
From: "Rex Dieter" rdieter@math.unl.edu To: kde@lists.fedoraproject.org Sent: Saturday, 10 October, 2015 11:16:33 PM Subject: Re: kdialog - Session bus not found
Brad Hubbard wrote:
Is this expected?
It's new in f22 AFAICT.
$ kdialog --title "Test" --passivepopup "Test" 2 kdialog(10183)/kdeui (kdelibs): Session bus not found To circumvent this problem try the following command (with Linux and bash) export $(dbus-launch) KCrash: Application 'kdialog' crashing...
It's not expected that your kde login not have an active dbus session. If that's really the case, hardly anything will work.
That was the case in Konsole sessions prior to late last week.
To verify, does this return anything useful? $ echo $DBUS_SESSION_BUS_ADDRESS
it should return something like: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yC5KUykdT
This works now and, sure enough, I no longer see the crashes. Looks like this was fixed in the kde/kf5 packages pushed to updates last week?
Cheers, Brad
I guess it's also arguable that kdialog should fail more gracefully than crash in that situation too.
-- Rex
kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org