[Bug 1004769] New: can't start D-bus can you call qdbus-qt5
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769 Bug ID: 1004769 Summary: can't start D-bus can you call qdbus-qt5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: roeland.jansen@snow.nl QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- modified my 42.1 repos to 42.2; downloaded all packages with zypper dup -d after that I did the upgrade. All went well except for that KDE cannot start: can't start D-bus can you call qdbus-qt5 a failsafe X session works OK, and executing plasmashell gives somrt of a working environment I did test 42.2 via a network install and that one - in vmware workstation 12.5 - seems to start OK. Haven't been t/s yet. so no logs seen so far -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c1
--- Comment #1 from Roeland Jansen
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c2
--- Comment #2 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c3
--- Comment #3 from Andreas Stieger
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c4
Wolfgang Bauer
kdm.log:
kdeinit4: Communication error with launcher. Exiting! kdmgreet(8943)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
That's irrelevant, and "normal" with kdm. The first question is: can you run qdbus-qt5 manually? Or do you get an error message? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c5
--- Comment #5 from Roeland Jansen
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c6
--- Comment #6 from Wolfgang Bauer
yes, I did, whatever I tried I could not get it to work
You did what? Get an error message, or were able to run qdbus-qt5 successfully?
so (sorry abt that) redid a reinstall and formatted the 'system' LVs.
It is working. Time did not permit to t/s more; als no backup was possible.
Maybe it's closing time on this.
Well, this is definitely not a general problem, and as we cannot investigate further, there's no point in keeping this bug report open. Just one question: Did you maybe install/use Anaconda? This comes with its own Qt5 installation (in $HOME), and its installer overrides the user's PATH in ~/.bashrc so startkde will try to use Anaconda's Qt tools and fails because there's only qdbus and not qdbus-qt5 (we renamed that to make it co-installable with Qt4). There has been a forum thread recently about this: https://forums.opensuse.org/showthread.php/520628-Could-not-start-D-bus-Can-... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c7
Roeland Jansen
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c8
--- Comment #8 from Wolfgang Bauer
yes I could but that had no succes.
Sorry, but what does "that had no success" mean here? Did you get an error message when running it manually, or did Plasma still not start? (the latter would of course be obvious, because just running qdbus-qt5 won't fix anything, it was just meant as a test to determine what the problem is)
regarding the anaconda question -- no I did not.
Ok, something else might do a similar thing though, i.e. "override" the system's qtpaths (which startkde uses to determine the location of qdbus-qt5) with its own version that returns a different tool path (so qdbus-qt5 isn't found). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c9
--- Comment #9 from Roeland Jansen
Sorry, but what does "that had no success" mean here?
no effect -- it could start but no normal desktop.
Did you get an error message when running it manually, or did Plasma still not >start? (the latter would of course be obvious, because just running qdbus-qt5 >won't fix anything, it was just meant as a test to determine what the problem >is)
no did not start. plasma. The only way I could get a sort-of-UI was the fail-safe X session but that is hardly useable for me. I promise to dd the whole image from ssd to a rotating disk for later troubleshooting next time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c10
P. Otato
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c13
--- Comment #13 from Wolfgang Bauer
I am using also anaconda, and this bug forces me (and other potential users) to manually (or via a script) to edit the .bashrc file after login and before log-out.
You don't have to edit .bashrc though. Just set the paths in a start script for anaconda.
On a side-note: Why does startkde care about my paths in .bashrc at all?
Because the paths set in .bashrc affect *any* program run in the user session. (In reply to Christian Herenz from comment #12)
To clarify what happens, since that is not really clear from the initial bug report see this thread in the opensuse forums - where a fix / workaround is claimed: https://forums.opensuse.org/showthread.php/520628-Could-not-start-D-bus-Can- you-call-qdbus-qt5?p=2798385
I know about this thread because I actually took part there. And the claimed fix/workaround has been added to our KDE packages, startkde explicitly uses /usr/bin/qtpaths now to get the system Qt5 paths. And later versions don't use qtpaths at all anymore. Messing with the paths in .bashrc might cause other problems though, like applications trying to load different/incompatible versions of Qt libraries. What openSUSE version are you actually using?
additionally, see the anaconda bugtracker - where they blame it on KDE: https://github.com/ContinuumIO/anaconda-issues/issues/1206
And in another openSUSE forum thread, GNOME fails to start. https://forums.opensuse.org/showthread.php/528969-Unable-to-log-in-after-ins... Would you/they blame that on KDE too? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c14
Wolfgang Bauer
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c15
--- Comment #15 from Christian Herenz
(In reply to Christian Herenz from comment #11)
I am using also anaconda, and this bug forces me (and other potential users) to manually (or via a script) to edit the .bashrc file after login and before log-out.
You don't have to edit .bashrc though. Just set the paths in a start script for anaconda.
Which I would do in my .bashrc, as I want anaconda in every interactive shell.
On a side-note: Why does startkde care about my paths in .bashrc at all?
Because the paths set in .bashrc affect *any* program run in the user session.
.bashrc should affect only interactive shells. Thus, imho, startkde should spawn in a non-interactive shell and not execute anything in .bashrc. I see that in opensuse /etc/profile sources ${HOME}/.bashrc - but, for example, they don't do that in debian. I always thought that the standard logic is to source ~/.profile in non-interactive shells, where the user has the choice to specify whether he wants (or not) his .bashrc to be sourced or not.
Messing with the paths in .bashrc might cause other problems though, like applications trying to load different/incompatible versions of Qt libraries.
When those applications are loaded from an interactive shell, I agree, this might happen.
What openSUSE version are you actually using?
42.3
additionally, see the anaconda bugtracker - where they blame it on KDE: https://github.com/ContinuumIO/anaconda-issues/issues/1206
And in another openSUSE forum thread, GNOME fails to start. https://forums.opensuse.org/showthread.php/528969-Unable-to-log-in-after- installing-anaconda
Would you/they blame that on KDE too?
I don't blame it on kde, rather on the way opensuse uses the ${HOME}/.bashrc - which seems to be a bit unorthodox. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c16
--- Comment #16 from Christian Herenz
PS: What actually happens if you run "qdbus-qt5" in a shell? (when logged in to IceWM e.g.)
Runs just fine in my kde session, even in a shell where I have sourced my anaconda startup script. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c17
--- Comment #17 from Wolfgang Bauer
(In reply to Wolfgang Bauer from comment #13)
On a side-note: Why does startkde care about my paths in .bashrc at all?
Because the paths set in .bashrc affect *any* program run in the user session.
.bashrc should affect only interactive shells. Thus, imho, startkde should spawn in a non-interactive shell and not execute anything in .bashrc. I see that in opensuse /etc/profile sources ${HOME}/.bashrc - but, for example, they don't do that in debian. I always thought that the standard logic is to source ~/.profile in non-interactive shells, where the user has the choice to specify whether he wants (or not) his .bashrc to be sourced or not.
Well, that's something on a lower level though, unrelated to KDE. If you think that is a bug, I would suggest to file a new one against "Base System".
What openSUSE version are you actually using?
42.3
42.3 definitely has that change to explicitly use /usr/bin/qtpaths: https://build.opensuse.org/package/view_file/openSUSE:Leap:42.3/plasma5-work... Btw, they even admit that using .bashrc is not a good idea in https://github.com/ContinuumIO/anaconda-issues/issues/6439#issuecomment-3346...
You really should not add conda to your PATH like this. Use the activate script when you want to use conda, or else add it to your non login shells only.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c18
--- Comment #18 from Wolfgang Bauer
(In reply to Wolfgang Bauer from comment #14)
PS: What actually happens if you run "qdbus-qt5" in a shell? (when logged in to IceWM e.g.)
Runs just fine in my kde session, even in a shell where I have sourced my anaconda startup script.
Hm? I thought your KDE session does not start... Or what exactly is *your* problem that caused you to reopen this bug report? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c19
--- Comment #19 from Christian Herenz
(In reply to Christian Herenz from comment #16)
(In reply to Wolfgang Bauer from comment #14)
PS: What actually happens if you run "qdbus-qt5" in a shell? (when logged in to IceWM e.g.)
Runs just fine in my kde session, even in a shell where I have sourced my anaconda startup script.
Hm? I thought your KDE session does not start... Or what exactly is *your* problem that caused you to reopen this bug report?
My KDE session does not start if I have the line export PATH="/home/knusper/anaconda3/bin":$PATH -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c20
--- Comment #20 from Christian Herenz
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c21
--- Comment #21 from Christian Herenz
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c22
--- Comment #22 from Wolfgang Bauer
The kde session does not start if I have the line
export PATH="/home/knusper/anaconda3/bin":$PATH
as last line in my .bashrc.
And you still can run qdbus-qt5 then? What exactly happens when you login? Do you get the mentioned error "Can't start D-bus. Can you call qdbus-qt5", or something else? Btw, an acceptable workaround for you may probably be to add something like this to .bashrc instead:
# If not running interactively, don't do anything # This is required, otherwise error at KDE login # "Could not start D-bus. Can you call qdbus-qt5?" [ -z "$PS1" ] && return
[[ ":$PATH:" =~ ":/home/user/anaconda3/bin:" ]] || PATH="/home/user/anaconda3/bin:$PATH"
(as done by the reporter in the mentioned Anaconda bug report) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c23
--- Comment #23 from Wolfgang Bauer
It fails with the above message.
I have the updated plasma-workspace package installed:
Repository : openSUSE-Leap-42.3-Update Name : plasma5-workspace Version : 5.8.7-8.1
Well, I have absolutely no idea what we additionally could do on the KDE level about it then. (except maybe resetting the $PATH in startkde, but that's probably not a good idea either...) Seems I have to download and install Anaconda myself to investigate more. Will take some time then though. PS: maybe it would also work to add Anaconda's path *after* the system paths? I.e.:
export PATH=$PATH:/home/knusper/anaconda3/bin
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c24
--- Comment #24 from Christian Herenz
export PATH=$PATH:/home/knusper/anaconda3/bin
No, since then "python" would call system python and not anaconda python. In the meantime I file a bug against base, since to me calling .bashrc when logging in into a graphical desktop seems to be against standard *nix practice. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
Christian Herenz
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c25
--- Comment #25 from Wolfgang Bauer
(In reply to Wolfgang Bauer from comment #23)
export PATH=$PATH:/home/knusper/anaconda3/bin
No, since then "python" would call system python and not anaconda python.
Oh well. Replacing the system's python too might just cause problems as well. At least this would cause all system python modules to not be found. And I'm thrilled to see what else they replace... :-/
In the meantime I file a bug against base, since to me calling .bashrc when logging in into a graphical desktop seems to be against standard *nix practice.
Ok. JFYI, openSUSE's default ~/.bashrc states this at the very top: # There are 3 different types of shells in bash: the login shell, normal shell # and interactive shell. Login shells read ~/.profile and interactive shells # read ~/.bashrc; in our setup, /etc/profile sources ~/.bashrc - thus all # settings made here will also take effect in a login shell. So at least .bashrc is not sourced "by mistake"... Anyway, back to KDE: could you please attach the ~/.xsession-errors-:0 from a failed KDE session? Maybe it shows something... (please note that it is recreated from scratch on login though) Alternatively, run startkde in IceWM and post the output. That is with Anaconda's PATH line in place of course. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c26
--- Comment #26 from Christian Herenz
JFYI, openSUSE's default ~/.bashrc states this at the very top: # There are 3 different types of shells in bash: the login shell, normal shell # and interactive shell. Login shells read ~/.profile and interactive shells # read ~/.bashrc; in our setup, /etc/profile sources ~/.bashrc - thus all # settings made here will also take effect in a login shell.
So at least .bashrc is not sourced "by mistake"...
Yeah - but its exactly this non standard behaviour in openSUSE that causes this issue. For setting up own paths that override system libraries, ${HOME}/.bashrc is the place. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c27
--- Comment #27 from Wolfgang Bauer
Yeah - but its exactly this non standard behaviour in openSUSE that causes this issue. For setting up own paths that override system libraries, ${HOME}/.bashrc is the place.
Feel free to discuss this with the basesystem maintainers. At least it's documented... Btw, it will take me longer to try out Anaconda myself. I did try to install it meanwhile, but ran out of hard disk space... :-/ -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769
http://bugzilla.opensuse.org/show_bug.cgi?id=1004769#c28
Christian Herenz
(In reply to Christian Herenz from comment #26)
Yeah - but its exactly this non standard behaviour in openSUSE that causes this issue. For setting up own paths that override system libraries, ${HOME}/.bashrc is the place.
Feel free to discuss this with the basesystem maintainers. At least it's documented...
I created https://bugzilla.opensuse.org/show_bug.cgi?id=1078124 for this. This is the root cause for this problem. I think you should not work on fixing this, as it will work as expected when above bug is fixed. I did some research and will post follow up information there. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com