Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 493976 - x11-misc/xscreensaver-5.22 - crash in unknown hack
Summary: x11-misc/xscreensaver-5.22 - crash in unknown hack
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 All
: Normal normal (vote)
Assignee: Desktop Misc. Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-11 22:14 UTC by R. Whitney
Modified: 2014-02-01 12:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description R. Whitney 2013-12-11 22:14:05 UTC
I am running XScreenSaver 5.22 and when I leave my screen locked for an extended period of time (so far it's been an hour or more) it crashes at some point while I am gone, so I return home to an unlocked desktop.
I see that the latest stable release is 5.26 according to the author's website, yet the version in the portage repositories right now is well behind.
If it makes a difference, I'm running XFCE4 with Compiz-Fusion (which I start with fusion-icon).
I am on a 64bit proc, running kernel version 3.10.17 & using opensource nvidia video drivers.
Comment 1 Alex Legler (RETIRED) archtester Gentoo Infrastructure gentoo-dev Security 2013-12-12 11:09:55 UTC
(In reply to R. Whitney from comment #0)
> I am running XScreenSaver 5.22 and when I leave my screen locked for an
> extended period of time (so far it's been an hour or more) it crashes at
> some point while I am gone, so I return home to an unlocked desktop.

Not sure how you expect us to identify a bug using this description.

> I see that the latest stable release is 5.26 according to the author's
> website, yet the version in the portage repositories right now is well
> behind.

That's something we can rather fix.
Comment 2 R. Whitney 2013-12-12 12:17:36 UTC
Yes yes, sorry about the lack of useful information. I tried to give as much information about the packages I'm running & steps to reproduce so that hopefully someone would be able to find the time to look into it after reading this. Since it takes a fairly long about of time, the only way I could really pull off a test is by maybe running xscreensaver from cli before I go to sleep, and hope that I can catch the error that way. I'll post back when I have a little more information.
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2013-12-12 14:40:50 UTC
Which specific module was xscreensaver running when it crashed?
Comment 4 R. Whitney 2013-12-12 16:22:58 UTC
(In reply to Jeroen Roovers from comment #3)
> Which specific module was xscreensaver running when it crashed?

default configuration, following USE flags: jpeg opengl pam perl -gdm -new-login (-selinux) -suid -xinerama
Comment 5 Samuli Suominen gentoo-dev 2013-12-13 05:56:51 UTC
(In reply to R. Whitney from comment #4)
> (In reply to Jeroen Roovers from comment #3)
> > Which specific module was xscreensaver running when it crashed?
> 
> default configuration, following USE flags: jpeg opengl pam perl -gdm
> -new-login (-selinux) -suid -xinerama

i'm afraid you didn't answer the question

xscreensaver module is a separate process (executable), like:

$ qlist xscreensaver |grep lib.*misc
and here you will see a long list of possibilities

if one of them crashed, there would likely be brief mention of the segfault in syslog (messages, dmesg) -- just guessing

(yes, debugging xscreensaver crashing is daungingly long task ;)