LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   "noof" and "fliptext" screensavers segfault on Slackware64 current (https://www.linuxquestions.org/questions/slackware-14/noof-and-fliptext-screensavers-segfault-on-slackware64-current-4175620574/)

khronosschoty 12-30-2017 11:11 AM

"noof" and "fliptext" screensavers segfault on Slackware64 current
 
This is using 4.9.67 kernel. System is Intel(R) Core(TM) i7-7500U which has a Intel HD 620 graphics core.

dmesg shows this:

Quote:

Originally Posted by dmesg out put
[72780.126295] fliptext[13873]: segfault at 7f5e1a1f21bc ip 00007f5e1971d287 sp 00007fff370b4a80 error 4 in i965_dri.so[7f5e1926a000+7da000]
[82815.139931] noof[2830]: segfault at 9d ip 00007fbf7d71ba10 sp 00007ffc11c6e3d8 error 4 in i965_dri.so[7fbf7d343000+7da000]


Alien Bob 12-30-2017 12:27 PM

My laptop with an "Intel Corporation HD Graphics 520" GPU and an "Intel(R) Core(TM) i5-6200U CPU" has the latest Slackware64-current on it. Since it is also running Plasma5, a screensaver does not show up here.
But I ran xscreensaver-demo to try both 'fliptext' and 'noof' and neither of those are segfaulting. They just work ('noof' is nice, had not seen that before).

khronosschoty 12-30-2017 12:30 PM

Quote:

Originally Posted by Alien Bob (Post 5799725)
My laptop with an "Intel Corporation HD Graphics 520" GPU and an "Intel(R) Core(TM) i5-6200U CPU" has the latest Slackware64-current on it. Since it is also running Plasma5, a screensaver does not show up here.
But I ran xscreensaver-demo to try both 'fliptext' and 'noof' and neither of those are segfaulting. They just work ('noof' is nice, had not seen that before).

Did you make sure to try them in full screen? I should of added the issue only happens when I do the full test using xscreensaver-demo and not the demo where you see it in a small demo screen.

Alien Bob 12-30-2017 12:38 PM

They work full-screen, no segfaults.

ponce 12-30-2017 12:38 PM

I just tried them in full screen (launching them with the -root option) and all went fine (nvidia geforce 525m here).

khronosschoty 12-30-2017 12:47 PM

Turns out it only happens when I'm using spectrwm. I overlooked for some reason to test using xfce for example. And actually this might not be the case ether... I tried under spectrwm using a different user and the issue was not there. I will test this more and see if I can reproduce the issue.

khronosschoty 01-02-2018 02:48 PM

I'm not sure still how to reproduce the issue, but for some reason removing the gtk-2.0 folder in my ~/.config folder resolves the issue for me. I just thought to add this in case anyone else comes across this post, and is having the same issue.


All times are GMT -5. The time now is 09:33 PM.