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.
I have slackware64-current as of today (July 17) installed. With that is the gkrellm package. After my update today, upon starting gkrellm, it causes a forced logout of my user. Anybody else see this?
I also tested it by removing the configuration directory ~/.gkrellm2. And that does not fix it.
I ran an strace to attempt to see if I could deduce what was going on.
When I ran strace, the program did not crash. I deleted the ~/.gkrellm2 directory a second time. And then I started the program normally and it ran successfully.
So, problem solved? Yeah
Do I have any clue why? No.
It had stopped crashing a few days ago, but appeared again tonight. Gkrellm2 does not load, but crashes down to the login manager. My guess is that it is a hardware detection error. It is not detecting something, and then it can't do some operation and then it crashes.
This had got to be a hardware issue, because it just stopped crashing the system again. The hardware has become unstable somewhere, a software issue couldn't simply be fixed by trying again.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.