HAL v0.5.7 hangs up on Fedora Core 4 with DBUS v0.62
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
HAL v0.5.7 hangs up on Fedora Core 4 with DBUS v0.62
Hi there everybody here !
I'm new here, just registered. Hope I'll have a good time with you all.
OK, so, here is my first thread.
I'm using Fedora Core 4, with many updated packages, mainly from original and stable source codes. The reason is because I can have much more control over what packages I want in my linux. I thus prefer compiling from source, rather than using these lazy rpm packages. But I do make my own rpms though, when it comes to packages that are usually removed and installed very often.
I use the following packages, which are updated from source tarballs:
And it is this last package (hal) which is problematic ! I have installed it correctly on my system, but it hangs up when you start the service.
But the strange behaviour of hald is, is that when I start it for the first time, it just exists (or the service fails); but the second time, it will hangs there, not using any CPU cycle at all, it's just hangs !
Thus, the system does not hang at boot (because it just fails), but when I start the service again, it will not show neither [OK] nor [FAIL], but it hangs.
- I tried to add the --enable-sysfs-carrier in the configure parameter, but it still didn't make it.
- I tried compiling it with GCC 3.2.3, 4.0.0, 4.0.1, 4.0.2, and 4.1.1, but it didn't change at all.
- I installed the sysfsutils 2.0.0 (I think the latest), but still didn't change too.
- I tried to see what gdb would output when I run it in, but didn't show anything. It also hanged in gdb !!!
- I also tried the rpm from rpmfind.net (Fedora development), same version 0.5.7, but it just does the exact same hang up.
- I used the patch files from the Fedora Core development source rpm package, and recompiled that one too, but it didn't work either.
- I tried to down-grade to dbus version 0.61 but it didn't make any change
- I tried to use the latest dbus also (which is now 0.90), but it didn't work either ! Even worst ! That packages is much smaller than the 0.61 and 0.62, and doesn't provide the qt bindings :-/ And the dbus-glib-0.70 does compile, it gets errors, so that is why also I use the dbus-0.62 instead of the 0.90
- I even tried to work with the udev-0.94 and udev-092, but they didn't make any difference
- I also applied the patch from the garnome-2.14.2 GNOME installer, but ... pffff, no good
I just can't see anymore, what should I check, to avoid this hal hanging.
Though, I have read a lot of articles on the net , about this, but none of them seemed to solve my problem.
Here is the configure parameter I use, please, let me know if something is wrong (I already tried to remove the cpu & optimization flags but didn't make it too. Some of the parameters are meaning-less to the configure scripts, but I just copy and paste these parameters there, because I compile a lot, and I like to copy from a parameter preset (I removed some of them too when compiling with GCC 3.x, because most of the the optimization flags are for GCC 4.x) :
Anybody succeeded putting hal-0.5.7 on Fedora Core 4, please help me !
If possible, no rpms please, just how to compile and make them work properly through these sources I have (I have all the sources of all these above packages).
And most annoying thing, is that I have been trying to solve this problem for a week now, and just could do nothing at all than trying to fix this !
I now must edit /etc/fstab manually whenever a device is plugged in, and not automatically discovered by the GNOME 2.14.2 (which I have manually compiled also) through hal and gnome-mount.
By the way, trying to make these whole packages dancing in sync was the cause of this hal problem.
I believe, that the gnome-mount does a great job for removable devices, so I have not added the --enable-fstab-sync parameter in the configure; anyway, I don't think this is supported by hal anymore these days either.
Hope someone will be able to help.
Thanks for responses.