can't load libpulsecommon-4.0, can't access failsafe runlevels, KDE borks Mint
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
can't load libpulsecommon-4.0, can't access failsafe runlevels, KDE borks Mint
I was running Linux Mint for a while.
Then I decided to update apt-get.
Somehow, I messed up something involving libpulsecommon-4.0.so.
Now, whenever I try to boot, I can't get failsafe mode.
KDE always starts, but then encounters an error and usually gives me the message "Your session lasted less than 10 seconds."
The specific error is from kded(3303)
"org.freedesktop.DBus.Error.NoReply"
timeout by MessageBus
After I click the "OK" for the error window, the screen turns grey: no mouse pointer, no desktop, just grey, with no response to input.
I haven't run out of disk space, I have destroyed GRUB or something else necessary to boot KDE.
I had heard that holding down SHIFT or ESC would give me a failsafe login - that works if the USB is booting and I select "Ubuntu -advanced" while holding SHIFT but not ESC.
I tried USB boot disks. One of them seems to be running fsck very slowly; I don't want to shut down and interrupt it in case it is doing something useful. If anyone can tell me how long I should wait for fsck to start returning output, that would be helpful.
I'm going to start trying the root prompt stuff, like fsck and dpkg, in the hope that it might repair whatever is broken.
Meanwhile, suggestions are welcome. Thanks.
Last edited by nerdofdarkness; 09-12-2014 at 07:51 AM.
Do you mean you tried to update the apt-get program? or do you mean you ran the command apt-get update (as root or using sudo)?
There is no "apt-get" package so I guess you ran the apt-get update command from a terminal, right? If you did this, did you get any error messages?
jdk
Do you mean you tried to update the apt-get program? or do you mean you ran the command apt-get update (as root or using sudo)?
There is no "apt-get" package so I guess you ran the apt-get update command from a terminal, right? If you did this, did you get any error messages?
jdk
apt-get produced a lot of output that scrolled by very quickly.
I think the only time I had to interact was when it warned me that it wanted to update GRUB, and the default was "no."
I should have gone with the default, but I chose "yes," and that's probably the moment when I destroyed my GRUB and KDE functionality.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
