Announcement
Collapse
No announcement yet.
"Could not start d-bus. Can you call qdbus?"
Collapse
This topic is closed.
X
X
-
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 linksLast edited by SteveRiley; Apr 10, 2014, 10:13 PM. Reason: Fixed the link. Our defenses exist for a reason.
- Top
- Bottom
Comment
-
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.
- Top
- Bottom
Comment
-
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
I guess that means this post should be marked as solved?
- Top
- Bottom
Comment
-
Originally posted by BazzekNext update should contain the patch, it has not arrived for me just yet.
Hopefully we'll see a fix come down later in the day.
cheers,
billsigpic
A person who never made a mistake never tried anything new. --Albert Einstein
- Top
- Bottom
Comment
-
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
- Top
- Bottom
Comment
-
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.
- Top
- Bottom
Comment
-
Originally posted by The Liquidator View PostAn 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.
- Top
- Bottom
Comment
-
Originally posted by Gavin77 View PostYes, it's been fixed already. I updated again today and it works fine now.
Edit: After dealing with .Xauthority, I could login normally for the first time today. It appears to be fixed now...Last edited by geoaraujo; Apr 09, 2014, 02:51 PM.
- Top
- Bottom
Comment
-
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
Originally posted by geoaraujo View PostI 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...
VINNYi7 4core HT 8MB L3 2.9GHz
16GB RAM
Nvidia GTX 860M 4GB RAM 1152 cuda cores
- Top
- Bottom
Comment
Comment