"Could not start d-bus. Can you call qdbus?"

[Guest]

There's a bug on launchpad. Please subscribe. (But do not write useless comments like "Affects me too", please)

https://bugs.launchpad.net/ubuntu/+s...1/+bug/1304805

// stupid anti-spam system prevents me from posting valid links

[BobTreat]

The Launchpad bug 1304805 now has a solution, comment #12.

[NoWorries]

I had the same problem this morning after installing 102 updates. I used my wife's mobile to find out how to start a console from the Login screen (ctrl+alt+F1) and did the update and dist-upgrade 12 hours later. All the new packages solved the problem.

[Bazzek]

Sollution

FIx uploaded in kde-workspace_4.11.8-0ubuntu5Edit /usr/bin/startkde, change:
qdbus="QT_SELECT=qt4 qdbus"
to remove the quotes
qdbus=QT_SELECT=qt4 qdbus
sorry for the breakage

Next update should contain the patch, it has not arrived for me just yet.

I guess that means this post should be marked as solved?

[bweinel]

Next update should contain the patch, it has not arrived for me just yet.

Yup.. I had the same problem here this morning after last nights updates. A quick edit of /usr/bin/startkde with nano put it back right again.
Hopefully we'll see a fix come down later in the day.

cheers,
bill

[The Liquidator]

This happened to me following last nights update.

I have tried all solutions available on the 'net. Also checked with nano the file /usr/bin/startkde and find the quotes have been removed suggesting the patch has been made. Even so, when I enter my password the screen goes blank for a couple of seconds before I am taken back to the login screen. The only way I can currently get to the desktop is to hit ctrl+alt+F1 at the login screen, then login and then type

sudo startx

I am then taken to the desktop.

I am stumped

[The Liquidator]

An update

It appears that somewhere along the line I discovered there was a problem with the .Authority file.

Renaming it from the command line (the last time I used the rm command on that file (about 3 years ago) I wiped out the entire home folder) then typing startx allowed me in, and then rebooting enabled me to go in via kdm.

[geoaraujo]

Is this fixed already by the updates? What a nasty bug!

[geoaraujo]

An update

It appears that somewhere along the line I discovered there was a problem with the .Authority file.

Renaming it from the command line (the last time I used the rm command on that file (about 3 years ago) I wiped out the entire home folder) then typing startx allowed me in, and then rebooting enabled me to go in via kdm.

It's not fixed yet. And sometimes I get a message when I run startx: "timeout in locking authority file" and can't access my desktop.

[Gavin77]

Is this fixed already by the updates? What a nasty bug!

Yes, it's been fixed already. I updated again today and it works fine now.

[geoaraujo]

Yes, it's been fixed already. I updated again today and it works fine now.

I still can't login except when running startx, ad even that fails sometimes as I've posted.

Edit: After dealing with .Xauthority, I could login normally for the first time today. It appears to be fixed now...

[vinnywright]

He He he ,,,,, I got hit with this last night (04/08/2014) ,,,,,,, I ran off updates and , Bam , couldn't get in to the GUI and I needed to get to a show we were going to watch ,,,,, Hummm me thinks ,,,,, we are still running,, and I just need to get the file from hear to the laptop to be able to watch it .

OK this should be easy enough ,,,,,, ctrl+alt+F6 to a TTY , log in , so far so good , sudo netstat -tunap (to see if SSH was running ) Aaaa yes , ifconfig (to see my ip ) , to the laptop , open dolphin , network , attach network folder , tick the ssh option and fill in the info , Success ,,,, coped the file over and got to watch my show

subsequent updates today fixed the prob and I am back in the GUI and all seams well so far

I still can't login except when running startx, ad even that fails sometimes as I've posted.

Edit: After dealing with .Xauthority, I could login normally for the first time today. It appears to be fixed now...

if you run a GUI app with sudo instead of kdesudo this (a borked .Xauthority) can happen.

VINNY

[BobTreat]

I had to log in from a Live DVD and become root of my broken system, repair apt with dpkg, remove the two offending quotation marks and all was well.

[vinnywright]

i had to log in from a live dvd and become root of my broken system, repair apt with dpkg, remove the two offending quotation marks and all was well.

??

Vinny

[BobTreat]

I could not log in and was getting the d-bus error. Turned out there was a problem with apt needing more files but was unable to get them as there was no wireless in the recovery session. I needed to fix apt first to complete the upgrade, used the commands I will paste below, ran dpkg --reconfigure -a, the opened the file in nano the launchpad solution pointed to, removed the quotes from the line he said and was able to boot back in. I'm not a developer or tech, been using ubuntu for years though, got this from Google, so I'm sure there was probably an easier way (;

sudo mount ROOT-PARTITION /mnt
for i in /sys /proc /run /dev /dev/pts; do sudo mount --bind "$i" "/mnt$i"; done
sudo cp /etc/resolv.conf /mnt/etc/
sudo chroot /mnt