You are not logged in.

#1 2010-11-15 23:57:12

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Segmentation fault

I am not sure what to do about this. I have segmentation faults many times a day. I have to restart laptop to try to make roxterm or links to start. It is interesting that links didn't have segmentation fault until I installed e17. And with it came hal and dbus. only hal is started in rc.conf. I read that dbus will be pulled by hal anyway so no need to put it into rc.conf

I reinstalled arch linux and installed e17 already 3 times, but segmentation faults always appear.  Do people who use xfce or gnome, etc have such problems? Is this a common error? Because we essentially build our own distros with Arch and  there is a big chance for mistake. So, that must be the reason? I didn't have that in other distros on the same laptop, so I doin't know how to deal with this problem I mean my installation  is almost unusable in this state. Can anyone point me in some direction? I just don't know what to do anymore. It only give this error with no explanation and after research people only say that it might be bad compiling or code, but no real answer... I don't think I am the first and only with such problem with Arch and maybe people can help here?

Last edited by utsuwa (2010-11-15 23:58:08)

Offline

#2 2010-11-16 00:24:38

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,365
Website

Re: Segmentation fault

Are the segmentation faults across different software?    I'd be running a memtest on the machine...

Offline

#3 2010-11-16 01:05:25

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Yes... across different software. I will run memtest. But I am wondering why there was no such problem with other distros.  Although maybe it is just my bad luck - it broke only now? I will let you know about memtest results.

Last edited by utsuwa (2010-11-16 01:28:32)

Offline

#4 2010-11-16 06:17:12

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

ok, well 2 something hours into the test and no errors so far. Can't run longer than that (I am at work, they won't take it likely if they see me working on some unknown laptop most of the day, hehe). I can run longer of course, but I don't think that memory is at fault. It might be intermittent error that is still not catched yet, but segfaulting happens frequently almost on every boot, so I would expect errors to show up faster. Anything else I should pay attention to?

Last edited by utsuwa (2010-11-16 06:19:32)

Offline

#5 2010-11-16 10:29:52

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: Segmentation fault

The problem could be with your e17 installation. There are still parts left which do not run smoothly.

You may try to set up some simple WM (like openbox) as an intermediate test and check if this segfaults, too. If it does (as frequently as your current installation) there are chances that your hardware is faulty somewhere.

As for e17, depending on how you installed it, you may try to disable some modules (see e.g. https://bbs.archlinux.org/viewtopic.php … 57#p853757).

Last edited by bernarcher (2010-11-16 10:30:49)


To know or not to know ...
... the questions remain forever.

Offline

#6 2010-11-16 23:56:33

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Good idea to test it out with openbox. Is it easy to completely remove it later with just pacman -Rs openbox or whatever? Cuz I am not planning to use openbox in the future. I got tired of it, it was really nice and helpful for me in the past though.

Offline

#7 2010-11-17 08:04:54

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

I think the problem is with SLiM and not with E17. There is a problem with SLiM not closing it's stdin, which is tty1. This leads to tty1 having issues with keyboard. And one person reported programs freezing under E17 when started from terminal. I commented tty1 because of keyboard problems before finding out slim issue and it affected the programs running normally and not segfaulting (at least for now). Will post later on any changes.

Offline

#8 2010-11-17 23:46:27

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Ok, the problem is continuing. In my rc.conf I use dbus before hal (as stated in wiki). When I tried to run roxterm this morning it segfaulted. I tried to run it from xterm as a root and it complainned that it couldn't connect to dbus. Edited my rc.conf and put dbus after hal, same complaint from roxterm but it still starts after the error. And now during boot arch complains that it couldn't start dbus. So, I guess putting it after hal is not good (as wiki states anyway). So, anyone has any ideas?

Last edited by utsuwa (2010-11-17 23:47:39)

Offline

#9 2010-11-17 23:54:14

skunktrader
Member
From: Brisbane, Australia
Registered: 2010-02-14
Posts: 1,538

Re: Segmentation fault

hal automatically starts dbus if its not already running so there is no need to include it in your rc.conf

Last edited by skunktrader (2010-11-17 23:54:25)

Offline

#10 2010-11-18 07:59:48

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Exactly. So I didn't. I just have hal now in rc.conf.

Last edited by utsuwa (2010-11-18 08:00:43)

Offline

#11 2010-11-18 09:47:03

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: Segmentation fault

Did you try to start E17 without a login manager like SLiM?

Just to rule it's effects out, boot into runlevel 3 and use "startx" to start up X and E17.

If this does not help, you could set up a test user and try there.


To know or not to know ...
... the questions remain forever.

Offline

#12 2010-11-19 02:16:56

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

I will try that too

Offline

#13 2010-11-23 23:55:11

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

I have tested several things over the weekend. First of all openbox - same problem with segmentation faults. Tried running roxterm from xterm (xterm is not segfaulting yet), it showed "cannot connect to dbus" and segfaulted. So it isnot E17 problem. Something else is.
Also, tried to boot into init level 3 and run startx to avoid loading SLiM. Same thing. Trying to run programs sometimes end in segfaults.

Offline

#14 2010-11-24 00:15:09

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,059

Re: Segmentation fault

Have you tried putting dbus before hal in your daemons (regardless of what skunktrader has said)?

Offline

#15 2010-11-24 00:39:37

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Yes, I did. But I will try again with openbox and  let you know later.

Offline

#16 2010-11-24 01:11:50

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Well, i tried that and actually nothing changes. Same problem. Without dbus in rc.conf openbox doesn't segfault so much. However, I noticed that qtdesigner sometimes fails to start and vlc together with smplayer sometimes complaining about qt4 libraries or some .so file (qtGUI or something). Interestingly reinstalling qt4 fixes the problem sometimes, but it is only good until the next reboot. Then segfaults start again and qt4 problem too.

Last edited by utsuwa (2010-11-24 01:12:51)

Offline

#17 2010-11-24 03:29:55

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

ok so this is what it gives me now when I try to run roxterm from xterm:
symbol lookup error: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol: ao ating

Also, reinstalled qt and at least arora started so I can type this right now. I was thinking that maybe its something to do with hal or dbus? I tried to unistall hal (I think we don't need it anymore, because udev can do everything now), however it is a dependency of e17-extra-svn.

Other things I considred were memory and hard disk problems. Checked and there are no badblocks on the drive, memory test produced no errors.

Last edited by utsuwa (2010-11-24 03:52:02)

Offline

#18 2010-11-24 11:50:17

bernarcher
Forum Fellow
From: Germany
Registered: 2009-02-17
Posts: 2,281

Re: Segmentation fault

There seems to be be a problem with your system setup. You should probably tell us more about it. At least could you please post the DAEMONS array settings from your rc.conf. And some more info about your hardware would be in order. And check again, are there any suspicious messages during start up in the logs, dmesg, etc.?

BTW- did you try with a freshly set up test user?


To know or not to know ...
... the questions remain forever.

Offline

#19 2010-11-24 21:50:56

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

ok. I ran memtest again - almost 10 hours and no errors.

my rc.conf
(syslog-ng hal @network @netfs crond alsa slim)

besides dmesg which logs are relevant?
And what do you mean by freshly set up user? You mean erase a user and add it agian? Because I reinstalled three times already. So, each time the user was created anew.
Do I attach logs or I can just copy and paste here? They are quite big usually.

Memory : 384MB
CPU : Celeron 2GHz
Video : ATI RADEON IGP 340M

Last edited by utsuwa (2010-11-25 04:31:18)

Offline

#20 2010-11-25 21:40:23

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Anyone?

Offline

#21 2010-11-26 04:23:41

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

Ok, well it seems to me that I just cannot figure it out and I am pressed for time. I know it is my fault that arch doesn't work on my hardware. I guess some combination of hardware problems break arch and give segmentation faults.
I learned quite a lot from this problem and from fixing it. Indeed I am happy I embarked on installation of arch. I know now more than before and got more than I got from Slackware. However, because I have no time, I am abandoning this project for now.  Coming back to crunchbang. I will try to install e17 there.  Thanks to all!

I will still hang out here for sometime

Last edited by utsuwa (2010-11-26 04:26:32)

Offline

#22 2010-12-16 04:18:18

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

So, I installed crunch, stripped it off and installed E17. I have being using it for some weeks now and there were no segfaults. I guess my hardware or the way I setup arch was wrong.

Offline

#23 2011-01-05 05:54:16

utsuwa
Member
Registered: 2010-11-05
Posts: 59

Re: Segmentation fault

If anyone still reading.

Tried Arch on Compaq (another old laptop). Works great without any segmentation faults. So, I guess if you want to use Arch it is better to stay away from some Fujitsu laptops.

Offline

Board footer

Powered by FluxBB