You are not logged in.
Hey Guys,
I have installed arch on a friend slightly older laptop ( it's a single core p4). Running fine for ages however she recently did system upgrade. Now we have some issue I can't resolve.
I have Segmentation Faults. Firstly what are they ?
These are the error messages at boot-up
/etc/rc.d/dbus: Line 7 1366 Segmentation fault /usr/bin/dbus-uuidgen --ensure
/etc/rc.d/hal : Line 7 1384 Segmentation fault /usr/sbin/hald
/etc/rc.d/wicd: Line 5 1407 Segmentation fault /usr/sbin/wicd &>/dev/null
and kdm seg fault but i lose the message coz it's too fast for ctrl-s but I pretty sure they have the same root cause.
Any help would be great.
Mac
Last edited by Mac Tzu (2010-04-16 09:36:48)
Remember,
If it is a Placebo You can Believe in it !!!
Offline
Did you try a complete system upgrade? Partial upgrades can lead to all kinds of problems. Try a pacman -Syu. Alternatively, if you don't like to have her upgrade for some reason, read the pacman log file to figure out what has been upgraded. Based on that and the packages in the cache you might be able to downgrade.
(my uneducated guess: a shared library has not been updated, but the segfaulting programs have, thus the segfaults)
musician & coder
http://elephly.net
http://github.com/rekado
Offline
Ok good call I will give it a shot
Remember,
If it is a Placebo You can Believe in it !!!
Offline
I can confirm that I have done fresh update. Still broken, does anyone know how I investigate these issues ?
Remember,
If it is a Placebo You can Believe in it !!!
Offline
Hmm. This doesn't sound good. Are you missing a common package or so?
Sorry, I've got no idea what might be the reason.
musician & coder
http://elephly.net
http://github.com/rekado
Offline
Thanks anyway,
I am thinking it may be a hardware issue, any idea what may cause ths issue ?
Remember,
If it is a Placebo You can Believe in it !!!
Offline
doubt it. there is nothing more software than a segfault. (as I recall, it happens when a program tries to access memory that it may not access.)
if it is hardware-related at all, then you might want to check your RAM.
musician & coder
http://elephly.net
http://github.com/rekado
Offline
How much time has passed since the last time you did a full system update?
Try creating a new user and see if the problems are still there.
Last edited by corsakh (2010-04-16 12:16:34)
Offline
corsakh, OP said the error messages are at boot up.
Mac Tzu, using a live CD check what updates pacman lastly did (/var/log/pcman.log). Try to downgrade the packages and see your system is back to normal.
Offline
Oh, these are all daemons, my bad.
I guess I would start by looking at the daemon array then. I think that both hal and kdm require dbus to run properly and wicd may need to. So the problem is likely to be coming from dbus. I don't really know what /usr/bin/dbus-uuidgen --ensure does but it from the look of it perhaps it has something to do with generating and checking UUIDs. So check that fstab, mkinitcpio and grub are all set correctly. Did she make any changes to partitions or installed a new drive recently?
Offline
How much time has passed since the last time you did a full system update?
Try creating a new user and see if the problems are still there.
Hey,
Only like two week since last upgrade
I will double check the uuid address to make sure they haven't changed.
I will report back cheers
Mac,
Remember,
If it is a Placebo You can Believe in it !!!
Offline
Ok Guys,
I have add UUID to fstab no improvement.
I agree with corsakh that Dbus is prob the key problem causing the other progs to be effected. However this doesn't help my situation.
I am seriously preplexed.
Remember,
If it is a Placebo You can Believe in it !!!
Offline
not sure if its gonna be much help, but have you tried reinstalling the affected packages? hal, wicd, and dbus would make a decent start, and perhaps all of base again too
Offline
Yes,
I have re-installed dbus hal & wicd
and i pacman -Sc 1st
then re-installed them
Remember,
If it is a Placebo You can Believe in it !!!
Offline