i crashed slack 10.2 =/

mu-tiger · 03-08-2006, 08:34 AM

Last night, i was mucking about trying to install and configure Privoxy, and totally mucked that up, but that's not my issue...i went to switch to another session, and i got a black screen...waited, waited, waited, nothing.

Finally resorted to hard boot and got the error message from kcrash handler, and made a log file, which i have no f***ing clue how to interpret...i'll skip the parts that were okay, and ask for help understanding the rest, please. I know it's a lot, but i simply don't know which to address, so i do apologise if i'm overkilling.

Quote:

#5 0x414ebd81 in kill () from /lib/libc.so.6
#6 0x4137b681 in pthread_kill () from /lib/libpthread.so.0
#7 0x4137b9fb in raise () from /lib/libpthread.so.0
#8 0x414ebb14 in raise () from /lib/libc.so.6
#9 0x414ed05d in abort () from /lib/libc.so.6
#10 0x4146d694 in __cxa_call_unexpected () from /usr/lib/./libstdc++.so.5
#11 0x4146d6d1 in std::terminate () from /usr/lib/./libstdc++.so.5
#12 0x4146d841 in __cxa_throw () from /usr/lib/./libstdc++.so.5
#13 0x4146da9c in operator new () from /usr/lib/./libstdc++.so.5
#14 0x4146db7c in operator new[] () from /usr/lib/./libstdc++.so.5
#15 0x40ef82fd in QString::setLength () from /usr/lib/qt/lib/libqt-mt.so.3
#16 0x40f015b7 in operator>> () from /usr/lib/qt/lib/libqt-mt.so.3
#17 0x4171ea83 in KlipperWidget::loadHistory ()
from /opt/kde/lib/libkdeinit_klipper.so
#18 0x4171f120 in KlipperWidget::readProperties ()
from /opt/kde/lib/libkdeinit_klipper.so
#19 0x4171c4bf in KlipperWidget::KlipperWidget ()
from /opt/kde/lib/libkdeinit_klipper.so
#20 0x41721420 in Klipper::Klipper () from /opt/kde/lib/libkdeinit_klipper.so
#21 0x4171bc1a in kdemain () from /opt/kde/lib/libkdeinit_klipper.so
#22 0x40920796 in kdeinitmain () from /opt/kde/lib/kde3/klipper.so
#23 0x0804ce12 in ?? ()
#24 0x00000001 in ?? ()
#25 0x0807aa98 in ?? ()
#26 0x00000001 in ?? ()
#27 0x00000000 in ?? ()
#28 0x00000000 in ?? ()
#29 0x0000002b in ?? ()
#30 0x00001f80 in ?? ()
#31 0x0000ffff in ?? ()
#32 0x00000000 in ?? ()
#33 0x00000000 in ?? ()
#34 0x00000000 in ?? ()
#35 0x00000000 in ?? ()
#36 0x00000000 in ?? ()
#37 0x00000000 in ?? ()
#38 0x00000000 in ?? ()
#39 0x00000000 in ?? ()
#40 0x00000000 in ?? ()
#41 0x00000000 in ?? ()
#42 0x00000000 in ?? ()
#43 0x00000000 in ?? ()
#44 0x00000000 in ?? ()
#45 0x00000000 in ?? ()
#46 0x00000000 in ?? ()
#47 0x00000000 in ?? ()
#48 0x0807a020 in ?? ()
#49 0x00000000 in ?? ()
#50 0x00000000 in ?? ()
#51 0x00000000 in ?? ()
#52 0x00000000 in ?? ()
#53 0x00000000 in ?? ()
#54 0x00000000 in ?? ()
#55 0x00000000 in ?? ()
#56 0x41063cc0 in vtable for QGArray () from /usr/lib/qt/lib/libqt-mt.so.3
#57 0x00000000 in ?? ()
#58 0x00000000 in ?? ()
#59 0x00000000 in ?? ()
#60 0x00000000 in ?? ()
#61 0x80000000 in ?? ()
#62 0x00003fff in ?? ()
#63 0x41380ff4 in ?? () from /lib/libpthread.so.0
#64 0x415d99c0 in __libc_tsd_MALLOC_data () from /lib/libc.so.6
#65 0x0805ae08 in ?? ()
#66 0xbffff628 in ?? ()
#67 0x41379bfa in pthread_mutex_unlock () from /lib/libpthread.so.0
#68 0x0804e33b in ?? ()
#69 0x00000001 in ?? ()
#70 0x0807a3e4 in ?? ()
#71 0x0807a3ec in ?? ()
#72 0x00000000 in ?? ()
#73 0x00000000 in ?? ()
#74 0x0807a3f0 in ?? ()
#75 0x00000000 in ?? ()
#76 0x00000000 in ?? ()
#77 0x00000000 in ?? ()
#78 0x080506b7 in _IO_stdin_used ()
#79 0x00000000 in ?? ()
#80 0x00000000 in ?? ()
#81 0x00000000 in ?? ()
#82 0x080506b7 in _IO_stdin_used ()
#83 0x00000000 in ?? ()
#84 0x00000000 in ?? ()
#85 0x0807a3f0 in ?? ()
#86 0x00000000 in ?? ()
#87 0x00000000 in ?? ()
#88 0x0807a3ec in ?? ()
#89 0x0807a3e4 in ?? ()
#90 0x00000001 in ?? ()
#91 0x0807a3e0 in ?? ()
#92 0x00000000 in ?? ()
#93 0x00000000 in ?? ()
#94 0x00000000 in ?? ()
#95 0x0000000c in ?? ()
#96 0x00000014 in ?? ()
#97 0x08052658 in vtable for QCString ()
#98 0x0805ae08 in ?? ()
#99 0x00000000 in ?? ()
#100 0x00000000 in ?? ()
#101 0x08052658 in vtable for QCString ()
#102 0x0805adf8 in ?? ()
#103 0x00000000 in ?? ()
#104 0x4137bffb in thread_self () from /lib/libpthread.so.0
#105 0x0804e85e in ?? ()
#106 0x00000008 in ?? ()
#107 0xbffff9a0 in ?? ()
#108 0xbffff920 in ?? ()
#109 0xbffff8a0 in ?? ()
#110 0x00000000 in ?? ()
#111 0xbffff860 in ?? ()
#112 0xffffffff in ?? ()
#113 0x4146c48d in operator delete () from /usr/lib/./libstdc++.so.5
#114 0x0804f8cd in ?? ()
#115 0x00000000 in ?? ()
#116 0xbffffa9e in ?? ()
#117 0x00000001 in ?? ()
#118 0x00000000 in ?? ()
#119 0x00000000 in ?? ()
#120 0x00000000 in ?? ()
#121 0x00000000 in ?? ()
#122 0x00000000 in ?? ()
#123 0x00000000 in ?? ()
#124 0x080506b7 in _IO_stdin_used ()
#125 0xbffffb34 in ?? ()
#126 0xbffffa78 in ?? ()
#127 0x414ee2d4 in __cxa_atexit_internal () from /lib/libc.so.6
#128 0x414d844b in __libc_start_main () from /lib/libc.so.6
#129 0x0804b771 in ?? ()

Thanks.

jomen · 03-08-2006, 08:52 AM

kcrash handler made a log because something...crashed. You did a hard reboot, which I translate to pressing the "Reset" button or killing the power while the system was running.
Everything which was running - though you may not have seen it - literally crashed because of that.
I can't interpret the log - but I don't think there is a need to do so...

mu-tiger · 03-08-2006, 09:29 AM

Hi, thanks very much for answering. i should have added i had to hardboot before and never got an error message; further, every time i end the session, and log back in, i get the same error message without hard booting. i'm very confused.

Thanks again.

mu-tiger

mu-tiger · 03-09-2006, 09:15 PM

Blah; i also forgot to say it's clipper, sigabrit error, which now that i understand what that means, have discovered some files are lost, but meh, i'm not sweatting it.

For now, i've turned off session handling and am currently seeking any ideas as i sit and wget the latest kde...on dialup, since every time i end the session, it happens again.

Thanks.

Mr_C · 03-09-2006, 11:51 PM

hear what, why don't you start afresh; rm -rf ~/.kde

jomen · 03-10-2006, 02:29 AM

Careful with this - this could solve the issue, yes.
But it will also delete the kmail-folder - not just the settings, but all the mail along with it!
Back this one up before you do that!
Same for konqueror's bookmarks, if you value them.

mu-tiger · 03-11-2006, 12:11 PM

Hrm, Thanks for your help.

i got it all installed and re-enabled session manager...but i'm kind-of afraid to try it again, having just retrieved and ordered all my browser bookmarks again and rewritten my files...i'll get brave, at some point today, and switch sessions and see if that resolved it.

A quick question: Will a manual 'sync' before i switch sessions make sure i don't lose data i'm still in the process of restoring, should clipper happen to crash again?

Also, i'm trying to determine what crashed it, i tend to blame it on mucking up a Privoxy installation and configuration, but i know that it's possible something else may have caused it...Are there "common" reasons for clipper crash, and if so, what are they, please, so i can review what i was doing and try to else may have caused this, so i can possibly avoid it in the future?

i tell you what, i used to think i didn't sleep properly, before i got on *nix ...now i know i don't...but i feel so much relief at being off windows, i can't help but to play with my new toy. ;p

Thanks again.

mu-tiger · 03-12-2006, 04:30 PM

urgh. it's still crashing. i installed cxxlibs and tried it again, and it crashed again. Tried enabling and disabling session manager, there are programs randomly crashing like...abiword, text editors, clipper, etc, so i am just LOST. i know it must be a corrupt or missing lib, i just don't know how to find it...some initiation for a newb happening, here...feels like slack is seriously hazing me. =/

titopoquito · 03-12-2006, 04:55 PM

You can try to reinstall the libraries that are shipped with Slackware if you didn't install many new ones. See "man upgradepkg" for the --reinstall option to replace existing libraries with the officially shipped libs.

mu-tiger · 03-12-2006, 09:41 PM

ohhh, i don't want to loose all my killer kernel config a mate set me up with, and not to mention a pretty darned good iptables config and all that...what i did was log into flux, 'mv .kde .kde-' then booted back into kde and! no clipper crash notification, so i hope after happily working in my text editors and word processors and maybe trying to learn to do a li'l something in gimp, i can still manage to have all my files saved and not overwritten and report a success story here. i think it's going to work, this time, cus i had to reconfigure kppp.

Thanks a lot everyone, i'm sure you'll hear from me if stuff starts messing up on me again.

Cheers!

Mr_C · 03-12-2006, 10:57 PM

ya now and then kde feels like crashing on me on exit, so I usually do that from time to time.

mu-tiger · 03-13-2006, 08:25 AM

i actually did that before, but i think i did it as root. Heh, newbies.

i bet my buddy who most often helps me sort this stuff is going to avoid me for a month...at least if i go into irc saying, "i've got *nix issues."

onebuck · 03-13-2006, 09:34 AM

Hi,

You said that random crashes occur. I think you should run memtest and see if it is a hardware problem. Several Live-cd have memtest or you could google and get memtest to save to floppy or cd.

Let it run overnight with the defaults. Memtest will test the memory deep and generally is reliable to show any errors.

By chance have you been inside your boxen lately? If not some routine maintenance may be in order. Heck just using some dry air to get rid of the bunnies and dust may help. HEAT!

mu-tiger · 03-13-2006, 11:28 PM

i didn't know what you meant, so i asked my buddy what this memtest consists of. He goes, "you mean memtestx86?" He also said, "looks like there's a patch for linux that'll skip bad ram too (if it finds any)." So that's pretty cool.

All night? It takes that long?

If that's the case, i'm getting ready to learn about this, a bit. So much to learn, so little lifetime! Sooo many pebcak errors... /whine...

In the meantime, i surely did just open my box and blow out the dust not too long ago. i know it's supposed to be bad, but i used just a regular airhose, from my neighbor's garage; i was careful, though, and wonder why this is supposed to be so bad, when they sell compressed air in cans at outrageous prices? Didn't seem to hurt anything, and the neighbor claims he does it all the time, with no ill effects...but i really don't want to mess up my baby, now that everything seems all groovy again...

Thanks.

*edit: ohhh, just saw the goodies, many, many thanks!

mu-tiger · 03-14-2006, 07:30 AM

i decided to run it, but all it did was sit there saying it was loading memtest and rapidly beeping. Ctrl, alt, backspace did nothing, as well as ctrl, alt, F6, but ctrl, alt, delete took me back to my boot menu.

i'm just wondering if perhaps it's something with the way it's configured or what that might mean, since i gave it plenty of time to finish that and run the actual test?

Thanks.