messed up something with the tweak guide - hal not starting.

[brjoon1021]

I did not turn hal off. I have the KDE and Gnome edition of the 1.7 DVD installed. I went through the tweaking guide provided on the Ultimate edition site. I did not do anything sketchy... I left dbus and Hal as they were and anything else that had warnings or seemed the list bit dangerous to mess with. I only turned off things that were pretty obviously not needed for a desktop. Now when Ultimate boots up the graphical bootup goes away and drops me into the detailed bootup screen where I see that "Hal could not be started" and to "check that dbus is working". Once booted up, I checked on both of them in sessions or services, wherever it is... and dbus is running. Hal is not running for some reason even though it is checked. If I right click on Hal and "start" it startes up. Immediately after it starts I get my etheret connection back to the internet and the new hardware daemon finds out that I installed a USB printer since the last boot and the whole thing promply locks up. I will unhook the USB connection to the printer next time and see if I can at least get past the lockup. But I still have to turn Hal on every time for some reason. Before the tweaking guid, it worked perfectly.

1. Any ideas what I could have turned off while going through the tweaking guide that could have caused all of this? Again, I did not mess with Hal or dbus, but something must have affected them. I did turn off cron and anacron.

This is my favorite desktop by the way along with PCLinuxOS and Mint/Ubuntu. Everyone else should pretty much pack it in or join Ubuntu/Ultimate/Mint or PCLinuxOS IMHO because the rest of the distros are getting more and more behind on the ease of use and completeness front.

B.

[DaddyX3]

Did you check out the BUM? see if its ticked there (both dbus and HAL): System>>Admin>>Boot-Up Manager

Then in "Sessions" (System>>Preferences>>Sessions)make sure that you have "Automatically remember running applications when logging out" is ticked after you load HAL again and maybe that will get it back upon reboot.

I would recommend just going through all the settings again while going through TheeMahns How-To step by step and make sure that you undo things that you are not sure about.

[pch.shot]

I have used the tweaking guide before without any problems. Your finger may have slipped when you were in the sysv-rc-conf file. It's easy enough to do. You are not alone I have done it before.

[TheeMahn]

I did not turn hal off. I have the KDE and Gnome edition of the 1.7 DVD installed. I went through the tweaking guide provided on the Ultimate edition site. I did not do anything sketchy... I left dbus and Hal as they were and anything else that had warnings or seemed the list bit dangerous to mess with. I only turned off things that were pretty obviously not needed for a desktop. Now when Ultimate boots up the graphical bootup goes away and drops me into the detailed bootup screen where I see that "Hal could not be started" and to "check that dbus is working". Once booted up, I checked on both of them in sessions or services, wherever it is... and dbus is running. Hal is not running for some reason even though it is checked. If I right click on Hal and "start" it startes up. Immediately after it starts I get my etheret connection back to the internet and the new hardware daemon finds out that I installed a USB printer since the last boot and the whole thing promply locks up. I will unhook the USB connection to the printer next time and see if I can at least get past the lockup. But I still have to turn Hal on every time for some reason. Before the tweaking guid, it worked perfectly.

1. Any ideas what I could have turned off while going through the tweaking guide that could have caused all of this? Again, I did not mess with Hal or dbus, but something must have affected them. I did turn off cron and anacron.

This is my favorite desktop by the way along with PCLinuxOS and Mint/Ubuntu. Everyone else should pretty much pack it in or join Ubuntu/Ultimate/Mint or PCLinuxOS IMHO because the rest of the distros are getting more and more behind on the ease of use and completeness front.

B.

First thanks for the compliement it goes a long way.

I wrote that how to many a moon ago It is written with Feisty based Ultimate Edition in mind, Gutsy based (as Ultimate Edition 1.7 is) a new animal, take it as a grain of salt, remember what you got away with ... reinstall and only do what you got away with is my suggestion. Why not also take the time and write a how to to help others, give back I do so all the time. Just a suggestion not a requirement.

TheeMahn

[bpollen]

I had that problem also with 1.7.

How I corrected it:

sudo gedit /etc/init.d/rc

Change "CONCURRENCY=shell" to "CONCURRENCY=none"

Save the file and reboot.

Happened on 3 different systems. All three failed the same way. All three worked fine with Fiesty. I found it easier to turn the tweak off than to try to find out WHY it won't work. Color me lazy.

[brjoon1021]

bpollen, you are a genius. concurrency=shell to concurrency=none fixed it for me too. You saved me another reinstall only 4 days after this one. Thanks!

[bpollen]

bpollen, you are a genius. concurrency=shell to concurrency=none fixed it for me too. You saved me another reinstall only 4 days after this one. Thanks!

My motto is:

I make the mistakes so others don't have to!

And based on the number of mistakes, I am helping a whole LOTTA people....

[TheeMahn]

How I fixed it:

Code: Select all

sudo /usr/sbin/hald --daemon=yes

Will have to look into why that no longer works concurrency that is. If I get time will re-write the tweaking how to, I just have way to much on my plate right now.

TheeMahn