Bug 873520

Created attachment 639102 [details]
File: core_backtrace

Created attachment 639103 [details]
File: environ

Created attachment 639104 [details]
File: backtrace

Created attachment 639105 [details]
File: limits

Created attachment 639106 [details]
File: smolt_data

Created attachment 639107 [details]
File: cgroup

Created attachment 639108 [details]
File: executable

Created attachment 639109 [details]
File: maps

Created attachment 639110 [details]
File: dso_list

Created attachment 639111 [details]
File: proc_pid_status

Created attachment 639112 [details]
File: open_fds

Created attachment 639113 [details]
File: var_log_messages

Created attachment 639114 [details]
File: build_ids

After typing su, this happened both when I typed kdesu and when I tried to run a KDE application directly. This was previously reported with F17....

backtrace_rating: 4
Package: kde-runtime-drkonqi-4.9.5-2.fc18
OS Release: Fedora release 18 (Spherical Cow)

*** Bug 885688 has been marked as a duplicate of this bug. ***

You cannot run KDE apps under su (nor sudo), neither directly nor by running kdesu under su (or sudo). You need to run kdesu directly as your user instead.

If you are seeing this crash (a qFatal("session bus not found");) when not running your application under su or sudo, your D-Bus must be seriously messed up.

I get this crash when running hp-setup (hplip) to install a wireless printer
under *XFCE4*:

[root@localhost tmp]# hp-setup -g 192.168.1.7

HP Linux Imaging and Printing System (ver. 3.13.2)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-13 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

hp-setup[10145]: debug: param=192.168.1.7
hp-setup[10145]: debug: selected_device_name=None

(process:10145): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:10145): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
hp-setup[10145]: debug: Sys.argv=['/usr/bin/hp-setup', '-g', '192.168.1.7'] printer_name=None param=192.168.1.7 jd_port=1 device_uri=None remove=False
Searching for device...
hp-setup[10145]: debug: Trying IP address 192.168.1.7
hp-setup[10145]: debug: Found: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7
hp-setup[10145]: debug: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7: back_end:hp is_hp:True bus:net model:HP_LaserJet_Professional_P1102w serial: dev_file: host:192.168.1.7 zc: port:1
hp-setup[10145]: debug: Cache miss: hp_laserjet_professional_p1102w
hp-setup[10145]: debug: Reading file: /usr/share/hplip/data/models/models.dat
hp-setup[10145]: debug: Searching for section [hp_laserjet_professional_p1102w] in file /usr/share/hplip/data/models/models.dat
hp-setup[10145]: debug: Found section [hp_laserjet_professional_p1102w] in file /usr/share/hplip/data/models/models.dat
Found device: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7
hp-setup[10145]: debug: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7: back_end:hp is_hp:True bus:net model:HP_LaserJet_Professional_P1102w serial: dev_file: host:192.168.1.7 zc: port:1
hp-setup[10145]: debug: Starting GUI loop...
hp-setup[10145]: debug: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7: back_end:hp is_hp:True bus:net model:HP_LaserJet_Professional_P1102w serial: dev_file: host:192.168.1.7 zc: port:1
hp-setup[10145]: debug: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7: back_end:hp is_hp:True bus:net model:HP_LaserJet_Professional_P1102w serial: dev_file: host:192.168.1.7 zc: port:1
hp-setup[10145]: debug: hp:/net/HP_LaserJet_Professional_P1102w?ip=192.168.1.7: back_end:hp is_hp:True bus:net model:HP_LaserJet_Professional_P1102w serial: dev_file: host:192.168.1.7 zc: port:1
hp-setup[10145]: debug: Plugin status = -1
hp-setup[10145]: debug: kdesu -- hp-plugin -u --required --reason 1 To_install_plugin_for_HP_Device
hp-setup[10145]: debug: 
(process:10154): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(process:10154): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
kdesu(10154)/kdeui (kdelibs): Session bus not found 
To circumvent this problem try the following command (with Linux and bash) 
export $(dbus-launch) 
KCrash: Application 'kdesu' crashing...
KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit
sock_file=/root/.kde/socket-localhost.localdomain/kdeinit4__0
Warning: connect() failed: : No such file or directory
KCrash: Attempting to start /usr/libexec/kde4/drkonqi directly

I wonder why KDE is involved when using XFCE,

hp-setup is trying to run kdesu:
> hp-setup[10145]: debug: kdesu -- hp-plugin -u --required --reason 1 To_install_plugin_for_HP_Device

So I guess you should try running it as non-root, it will use kdesu to get root for the parts which need it. Or alternatively, try running "kdesu hp-setup" as non-root.

I think HP designed hp-setup primarily for KDE, it is written in PyQt4, and as you can see, it uses kdesu for controlled privilege escalation.

*** Bug 860182 has been marked as a duplicate of this bug. ***

*** Bug 855739 has been marked as a duplicate of this bug. ***

*** Bug 885851 has been marked as a duplicate of this bug. ***

*** Bug 976769 has been marked as a duplicate of this bug. ***

*** Bug 998276 has been marked as a duplicate of this bug. ***

*** Bug 1005450 has been marked as a duplicate of this bug. ***

*** Bug 1034458 has been marked as a duplicate of this bug. ***

*** Bug 1045804 has been marked as a duplicate of this bug. ***

*** Bug 901485 has been marked as a duplicate of this bug. ***

*** Bug 1037446 has been marked as a duplicate of this bug. ***

*** Bug 1045594 has been marked as a duplicate of this bug. ***

*** Bug 1054494 has been marked as a duplicate of this bug. ***

*** Bug 1078552 has been marked as a duplicate of this bug. ***

*** Bug 1099365 has been marked as a duplicate of this bug. ***

*** Bug 1172071 has been marked as a duplicate of this bug. ***

*** Bug 1174038 has been marked as a duplicate of this bug. ***

*** Bug 1175652 has been marked as a duplicate of this bug. ***

Another user experienced a similar problem:

My Skype launched from another user, and I just clicked on the link in Skype. :) 

reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        kde-open http://fedoraproject.org/wiki/Updates_Policy#kernel_package
crash_function: qt_message_output
executable:     /usr/bin/kde-open
kernel:         3.18.6-200.fc21.i686
package:        kde-runtime-14.12.1-2.fc21
reason:         kde-open killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1001