SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Filesystem navigation is almost impossible with my current installation. It constantly freezes my computer. Firefox sometimes freezes also. When I first installed Slackware 13.37, there was no problem but... I compiled and installed packages from slackbuilds.org, started additional services (namely bind, yp and cups)... I don't know what's causing the problem.
No solution I'm afraid, just shared experience. If it's any consolation, I've been getting similar crashes.
From your list I have added, from Slackbuilds, faac, faad, flash, libdvdcss, libmp4v2, vlc, webcore-fonts and xvidcore.
This morning, less than 5 minutes after installing the 32bit version of slackware, the whole system crashed completely whilst browsing the main menu. The crashes seem to occur whether I'm using the nouveau driver or the nvidia driver. The crashes occur both on the 32 bit and 64 bit versions.
Further to this - I use the same slackware64 install disk that I've been using since 13.37 came out last year - the crashes only started occurring fairly recently, implying that it's either something I've added or an update. The crashes don't seem to occur if I use xfce, implying it's a KDE issue.
I switched to SalixOS Mate edition- which is based on slackware (and offers access to slackbuilds via the Sourcery application, has some of the media stuff installed 'out of the box' and the rest easily available via sourcery/gslapt).
The crashes have subsequently stopped completely.
Thanks for joining me in the pub. What kind of beer do you like, I'll pay ya a round...
Now seriously, after re-installation did 'vanilla' Slackware crashed too? Or only after updating? Or only after installing your slackbuilds? Just to 'isolate' the problem...
NO problem. You should be proud to be part of Salix, it's one of the best OS's I've ever used.
As to your question, I can't answer it 100% accurately. I muck about installing distros so much that they all kind of merge into one and individual details get lost. I'm 99% sure that the first thing I did was go through the previously compiled Slackbuild stuff and install various bits.
The problem with the crashes is that they're so unpredictable. Days can go by without one and at other times they would occur within minutes of installation.
I have the morning free, so I'll reinstall slackware and work my way through the extra packages one by one and see if I can isolate the problem, or at least, narrow the field.
Installed slackware64, updated via slapt-get, installed faac, faad, flash, gtk-qt-engine, jbigkit, libdvdcss, libmp4v2, libmpeg2, opera, splix, unrar, webcore-fonts, xvidcore and yakuake, all freshly compiled from source.
Opera open with 2 tabs going, one on this page and the other showing the cricket. Pidgin also had one window open. Clicked on the Opera title bar to bring it to the front and the whole system locked solid - sound still going in the background, but the GUI was frozen.
Having not done this bit before - which logs should I be looking in for clues as to why this is occurring?
Last edited by salparadise; 07-19-2012 at 05:51 AM.
Reason: spelling
I've backed up /var/log, Xorg.0.log is 741 lines long. Any suggestions as to what to search for within it.
/var/log/messages ended with some lines regarding nouveau,
kernel: [ 1649.478141] [drm] nouveau 0000:02:00.0: PGRAPH_TRAP_TEXTURE - VM: Trapped read at 004553ab00 status 00000a60 channel 4 (0x00002280)
kernel: [ 1649.478154] [drm] nouveau 0000:02:00.0: PGRAPH_TRAP_TEXTURE - TP1: Unhandled ustatus 0x00000003
There's a bunch of lines like this, that were the last things to be written to that file prior to/during the crash.
I can post bits here if needed.
I suspect we're in different trees in the same orchard, so to speak. I can use Dolphin without any problems, the crashes I get are random and require no user input. I had one crash yesterday when I wasn't even in physical contact with the computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
