On 12/12/13, Goren Buckwalk <goren.buckw...@mail.com> wrote: >> So just segfault when trying to run certain application(s)? >> If you can consistently reproduce a segfault, then that is excellent >> news - should be easier to debug. > > It happens a lot, but no single app is gaurenteed to seg fault. > >> Did you check the various logs immediately after the segfault? Eg: >> cd /var/log >> ls -lrt # most recent logs at bottom >> > Here are some examples from the syslog: > > Dec 11 19:35:52 spare kernel: [ 5424.840022] glines[11138]: segfault at 17 > ip b6e7c04a sp bfd4f0e0 error 4 in libcairo.so.2.11200.2[b6e30000+10a000] > > (clip) > > Dec 11 20:49:09 spare kernel: [ 111.144146] lxsession-logou[3009]: segfault > at 18 ip b723c48f sp bfd37f30 error 4 in > libgdk-x11-2.0.so.0.2400.10[b71e7000+ae000] > > (here's a whole series:) > > Dec 11 21:29:22 spare kernel: [ 962.601219] lxpolkit[3107]: segfault at 8 > ip 08049a91 sp bfbeb790 error 4 in lxpolkit[8048000+3000] > Dec 11 21:29:48 spare kernel: [ 988.395434] pcmanfm[3101]: segfault at 2 ip > b70f4459 sp bfffdff0 error 4 in libgdk-x11-2.0.so.0.2400.10[b709f000+ae000] > Dec 11 21:30:17 spare dbus[2154]: [system] Activating service > name='org.freedesktop.UDisks' (using servicehelper)
> (clip) >> Just re-seating your RAM can sometimes fix RAM problem. > > I pushed on everything before I connected it up to do the reinstall. Re-seating means pulling it out, and putting it back in. Same with CPU. If the motherboard is dusty. Then you might (very carefully!) do a little vacuuming over the dusty areas (after removing sensitive things and making sure you don't bump anything with the vacuum cleaner). >> > things causes it (like adding a couple of apps to the launcher, but >> > running >> > a browser like midori doesn't cause a problem. >> >> Do you consistently, or just randomly, get segfault when running those >> apps? > > It mostly seems random, one thing that seems consistant is adding apps to > the LXDE launcher on the panel. If you do 3 or 4 in row it pushes it over > the edge. I think the first series of errors above is me doing just that. Ah - could be a disk problem then - "reseat" all your connectors, everything, run the RAM check. The inconsistency does make it look like you have a hardware issue - it can be a pain, but you need to go through process of elimination. > Thanks. Hope you don't mind the direct reply + cc, let me know what is > preferred. For all debian-* lists, just reply to the list. I only got your original email because I am subscribed, so I will also get all your replies that go to the list. I do not need an extra copy directly from you :) With gmail webmail non-javascript interface (probably others too), you will need to "reply all" then select-all and cut the CC field into the TO field. Please do this thanks. No need to reply to this paragraph :) - excessive politeness is certainly tolerated, but not necessary at all. Good luck Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caosgnst2vtkq8fxf-p6k9v2f7rnnnprbkhky3a1k9dfoqxg...@mail.gmail.com
