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.
Got Slackware 13.37. Every time I open ark and click on "new", kde crash handler opens with the standard apology and reads "Executable: ark PID: 2097 Signal: 4 (Illegal instruction)". Got 1 GB of mem on some mobo with a Athlon 1600XP. Yes this is a 9 year-old comp. That's why I installed Slack. Other than that, this system works very well. Any ideas?
Sounds like the executable binary or one of the libraries that it uses has become corrupted. Try re-installing the application, and if it still crashes, run ldd against the binary to see what libraries it links. Replace one or more of those until the problem goes away.
Got Slackware 13.37. Every time I open ark and click on "new", kde crash handler opens with the standard apology and reads "Executable: ark PID: 2097 Signal: 4 (Illegal instruction)". Got 1 GB of mem on some mobo with a Athlon 1600XP. Yes this is a 9 year-old comp. That's why I installed Slack. Other than that, this system works very well. Any ideas?
You did check the download ISO md5sum? After you burnt the image you verified the burn?
I've noticed that this only happens only if I use dolphin to open to open a usb key before using ark. If I use thunar, ark works fine. I can live with this.
Thanks to all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.