Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Acer Aspire One running Linux has suddendly stopped booting up with the following message:
Failed to start message bus: failed to bind socket "/var/run/dbus/system_bus_socket": Address already in use
sudo:sudo please use single character optionsplease
sudo:sudo no passwd entry for linpus
FATAL: Module speedstep_lib not found
Starting acpi daemon:acpid:starting up
OK
acpid: 1 rule loaded
setpci: Warning: No devices selected for AE47
/etc/rc.d/rc.last.ctrl:line 17 /sys/bus/usb/devices/5-5/power/level:No such file or directory
All of which means nothing to me but the thing ain't working! Any help would be greatly appreciated
also WHAT operating system is this ?
this is an acer netbook so i am guessing "limpus light"
that is about 5 years out of date and was loosely based on the very OLD fedora 8 ( from 5 years ago)
can you boot into single user mode or text only
( think of it as "safe mode" on Windows)
during the 3 sec. count down at the very beginning of booting
hit < enter>
then < e> for edit
use the down arrow to move to the boot line and a the number 1 to the end
a space then 1 or a 3 for text boot
then hit <b> for boot
if so then read the boor log file for the error
/var/log
the boot.0.log and xorg.log and messages
without knowing what the logs say ... i can only guess
things like the ram becoming unseated can cause it to error
or some of the ram has gone bad
or
some of the hardware became disconnected or has gone bad
there is no dvd drive
so if you "can" boot using a live USB image ?
then you can read the logs
ram / harddrive not being seated properly can cause something of the sort... try to boot from a live distro and access your hard drive to ensure that it is seated (or just open the laptop, remove the hard drive/ram, then reseat the hard drive/ram).
I think you had a hard poweroff and dbus was not able to delete the file /var/run/dbus/system_bus_socket .
Code:
find /var -name dbus -exec ls -R {} \;
gives me
/var/lib/dbus:
machine-id
/var/run/dbus:
pid system_bus_socket
The existing pid file might be the main problem .
You should organize some USB Pendrive bootable linux, boot it, mount the main partition, navigate to the /var directory and delete the dbus files (not the directories) .
[Another thing is ownership and permissions of the dbus files/directories.]
dbus itself on Puppy Linux for example gets launched by /etc/init.d/01_messagebus script .
*
Nevertheless your system boots, but refuses to launch the desktop/windowmanager .
The "blue screen" must be some sort of "/bin/whiptail" or "/bin/dialog" started by a script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.