I also have this bug, I'm using kde on my samsung chromebook with crouton. Here
is the command lines when starting.
Entering /mnt/stateful_partition/crouton/chroots/precise...
Failed to start message bus: Failed to open
"/etc/selinux/targeted/contexts/dbus_contexts": No such file or directory
WAR
I have this bug with a recently updated Kubuntu. None of the proposed
solutions seems to work: I do not have the funny quoting in
/usr/bin/startkde, and I am not missing the qdbus executables. I have
both qdbus and qdbus-qt5 installed, both x86_64.
--
You received this bug notification because
A better fix is to run:
sudo apt-get install qdbus
This will remove an existing 32-bit package and replace it with 64-bit.
After running this, it worked fine for me without needing to change the
quotes in startkde.
I saw this here: https://liquidat.wordpress.com/2013/04/29/short-tip-
fix-qdbus-pr
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about this bug g
Upgraded from 14.04 to 15.10: #12 is not working for me. This is the output of
/usr/bin/qdbus:
/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus: symbol lookup error:
/usr/lib/x86_64-linux-gnu/qt5/bin/qdbus: undefined symbol:
_ZN7QString18toLocal8Bit_helperEPK5QChari
Any suggestions?
--
You received th
Just upgraded from 12.04 to 14.04. Same bug. Workaround in comment #12
works. This should really be fixed... upgrading between LTS versions is
still broken!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs
** Package changed: compiz (Ubuntu) => kde-workspace (Ubuntu)
** Changed in: kde-workspace (Ubuntu)
Milestone: ubuntu-14.04 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
** Package changed: kde-workspace (Ubuntu Utopic) => compiz (Ubuntu
Utopic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you ca
Just selected "KDE Plasma Workspace" at the login prompt and that fixed
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you ca
This is a big puzzle. I am fully updated on 14.04 and none of the
workarounds fixes the problem.
root@sdrbox:~# ls -l /usr/lib/i386-linux-gnu/qt4/bin/qdbus
ls: cannot access /usr/lib/i386-linux-gnu/qt4/bin/qdbus: No such file or
directory
root@sdrbox:~# ls -l /usr/lib/x86_64-linux-gnu/qt4/bin/qd
I do not understand why this bug is still present!!! I upgraded from 12.04 to
14.01.1 right after the point release. After the upgrade I couldn't start KDE
because of a buggy startkde script. Yesterday I upgraded again this package and
startkde is still buggy!
In line 'alias qdbus="QT_SELECT=qt4
Solution in #32 worked for me after an upgrade like #34 and seems to
explain the problem, but it's obviously a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop lo
Hi,
Just upgraded from kubuntu 1204 amd64 to 1404 and immediately got stuck in this
bug.
Removing the parenthesis as suggested above in #12 solved the login problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kde-workspace (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Hi,
I can confirm the bug is there upgrading Kubuntu 12.04 to 14.04 on a 64bit
system.
I could work around with (as #29):
sudo ln -s /usr/lib/i386-linux-gnu/qt4/bin/qdbus /usr/lib/x86_64-linux-
gnu/qt4/bin/qdbus
The directory existed already.
It seems there is no qdbus for x86_64-linux-gnu ava
** Branch linked: lp:ubuntu/utopic-proposed/kde-workspace
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you ca
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/kde-workspace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
** Also affects: kde-workspace (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: kde-workspace (Ubuntu Utopic)
Importance: Critical
Assignee: Jonathan Riddell (jr)
Status: Fix Released
--
You received this bug notification because you are a member of Ubu
Hi,
just upgraded Kubuntu 12.04 to 14.04.
- I confirm that the bug IS STILL THERE. ("could not start d-bus"
message shows when you try to launch KDE, after clicking Okay it goes
back to log in screen)
- also confirming than Jonathan's tip to edit /usr/bin/startkde works
great
I believe it should
A week before I upgraded my Desktop (64bit) to Kubuntu 14.04. When I restarted,
I could and can no longer get a KDE desktop - wether my desktop with Password
nor the guest-desktop. Instead, I get a window with the message "Could not
start B-bus, Can you call qdbus?", and when I click "OK", I ge
Some details may have changed since April, but the problem remained.
After upgrading to Trusty yesterday, I got the same unpleasant message
with qdbus. In my /usr/bin/startkde file, the crucial line reads:
alias qdbus="QT_SELECT=qt4 qdbus"
After removing the quotes, KDE launched successfully, but
FYI I had this problem today (installed some updates recently) and my
system refused to login after rebooting today. Removed the double-quotes
as mentioned above and it's working now. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I think we have already established that. The issue presented by this
bug report "cannot login" is resolved, any further discussion on the way
it was resolved should be done elsewhere as it just pointlessly spams
people's inbox. Thanks.
--
You received this bug notification because you are a memb
The fix in #12 is utterly wrong.
You can't absolutely use an unquoted space in an assignment:
http://www.tldp.org/LDP/abs/html/varsubn.html#EX9
The reason because it *seems* to fix is luck, the line:
qdbus=QT_SELECT=qt4 qdbus
Would start "qdbus" anyway, but without the "QT_SELECT" variable an
what about just unsetting the variable before starting X?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To m
Nah, that would bring back another issue which was to be originally
resolved by tempering with the qdbus code to begin with.
I am going to prepare a proper qdbus invocation tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
It is true that removing the quotes in the line
qdbus=QT_SELECT=qt4 qdbus
Gets around "Could not start" issue. However, a better fix would be to leave
the quotes in place and further down start up qdbus with an eval statment:
qdbus="QT_SELECT=qtr qdbus"
...
if eval $qdbus >/dev/null
it seems to me the following syntax:
A=B=C D
in dash will execute "D" with the environment variable "A" set to "B=C",
so the line:
qdbus=QT_SELECT=qt4 qdbus
would run "qdbus" once, and set "qdbus" to "QT_SELECT=qt4 qdbus":
$ qdbus=QT_SELECT=qt4 qdbus
:1.0
com.ubuntu.Upstart
...
org.freedeskto
I can confirm that it works too. Thanks so much for the quick fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbu
** Also affects: kdebase-workspace
Importance: Undecided
Status: New
** No longer affects: kdebase-workspace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login
Thank you, Jonathan! The fix did the trick for me!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qd
Thank you Jonathan!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications
Thankyou, works here too.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifica
This bug was fixed in the package kde-workspace - 4:4.11.8-0ubuntu5
---
kde-workspace (4:4.11.8-0ubuntu5) trusty; urgency=medium
* Fix patch kubuntu_dont-force-on-path.patch, previous change
broke log, sorry, LP: #1304805
-- Jonathan RiddellWed, 09 Apr 2014 09:33:32 +0100
Worked here too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about this bug go to:
THX Jonathan #12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about this bug go to:
** Branch linked: lp:ubuntu/trusty-proposed/kde-workspace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To m
Worked like a charm. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about
qdbus variable in startkde is a string, should be a command sequence.
** Package changed: qt4-x11 (Ubuntu) => kde-workspace (Ubuntu)
** Changed in: kde-workspace (Ubuntu)
Importance: Undecided => Critical
** Changed in: kde-workspace (Ubuntu)
Status: Confirmed => Triaged
** Changed in
FIx uploaded in kde-workspace_4.11.8-0ubuntu5
Edit /usr/bin/startkde, change:
qdbus="QT_SELECT=qt4 qdbus"
to remove the quotes
qdbus=QT_SELECT=qt4 qdbus
sorry for the breakage
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
[Po]lentino,
That informaion isn't actually helpful. You tried to run qdbus from a
tty without X11 server?
If so, the essage just tells you that X11 should be started and $DISPLAY
env variable should be set in order to call qdbus.
--
You received this bug notification because you are a member o
I made a bugreport like this one at about same time ( #1304856 ) anyway
,since this one is the original one, I put here some additional info
that could be useful for the devs: I logged in TTY1, run qdbus, and I
got this output:
"Could not connect to D-Bus server:
org.freedesktop.DBus.Error.NotSupp
OMG! Kubuntu
Unsupported windows XP is working.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To
Its a big bug !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about this bug go to:
I cominfirm this bug.
Please sove quickly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notificat
Ubuntu Trusty Tahr (development branch)
Release:14.04
sudo apt-get -f install
sudo apt-get install qttools5-dev-tools
sudo apt-get install dbus
sudo apt-get install dbus-qt5 < Installed
sudo apt-get install qdbus
sudo apt-get install dbus:amd64
sudo apt-get install qdbus:amd64
sudo apt
Same here.
Tried installint qt4-default
Tried installing qt5-dbus
Tried updating kde-workspace-bin (was already up to date)
No change.
Working with KUbuntu 14.04 btw
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Same here :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KDE desktop login failure: "Could not start d-bus. Can you call
qdbus?"
To manage notifications about this bug go to:
htt
Ubuntu Trusty Tahr (development branch)
Release:14.04
qdbus version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4
What I expected to happen : Install updates, reboot and log in as usual.
What actually happened: Installed updated, rebooted and got this error
upon login.
I downloaded the packa
same here on a amd64 system.
I went into the terminal by pressing Ctrl-Alt-F1. From there I tried
- sudo apt-get -f install
- sudo apt-get install dbus
- sudo apt-get install dbus-qt5 (it actually installed)
- sudo apt-get install qdbus and
- sudo apt-get install dbus:amd4
none of which solved the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: qt4-x11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1304805
Title:
KD
51 matches
Mail list logo
