Bug 616392

Summary:	older processes can't communicate on dbus after logging in via displaymanager
Product:	Gentoo Linux	Reporter:	kavol
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	jstein
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description kavol 2017-04-23 14:56:27 UTC

I'm running some applications using xpra, e.g. kmail.
After logging on the computer physically via sddm, which starts lxqt-session, the applications running in xpra exhibit various malfunctions, like kmail unable to receive/send emails etc., with the important error message probably being this:

klauncher(18018) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.

Comment 1 Mike Gilbert gentoo-dev

2017-05-04 01:04:21 UTC

You should seek support via forums/irc/mailing lists, and report a bug when you are sure you have identified a bug.

Comment 2 kavol 2017-05-04 11:24:19 UTC

ahem, I'm pretty sure that if an application suddenly stops working (and it is reproducible in the same situation, i.e. not some random hardware glitch) then it is a bug

it might be called a 'feature' in Microsoft, but I'm still hoping that Linux (and Gentoo especially) is not there (yet)

I believe I have identified the cause of the problem - DBUS malfunction - and also described the circumstances when this happens, and if this is not enough, if you cannot reproduce on your system, then I'd expect an inquiry how to get to the root of this, telling me what should I try, which logs would be useful etc.

although I can imagine it'd be very comfortable for the developers if I could resolve it with someone else and just attach patch here, I don't believe this is how the distro processes should work ...

Comment 3 Jonas Stein gentoo-dev

2017-05-14 19:27:39 UTC

Kavol, it is sad to read that you have problems with the software. 
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3,4]. 
People help each other in their spare time and it helped often to fix or localize problems. Of course you can ask your local computer service to solve this, which safes your time. We can try to find experts in your region via [1].

Gentoo developers can only fix a bug in an ebuild, but not in upstream code and even more we must precisely explain what is broken. 

I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels. 

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] http://unix.stackexchange.com/questions/tagged/gentoo?sort=votes&pageSize=15
[3] https://forums.gentoo.org/
[4] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html