| Summary: | Xscreensaver 4.22-r1 doesn't obey gnome use flag | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mario <superm1> |
| Component: | New packages | Assignee: | Jonathan Smith (RETIRED) <smithj> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | desktop-misc |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://forums.gentoo.org/viewtopic-p-2530190.html#2530190 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
using the gnome USE flag is a bad idea for this feature... perhaps we should change the name to something else? "new-login" perhaps? if new-login is not enabled (as would be the default), users would be given an einfo about its benifits and drawbacks sound good? Yea, I like this idea alot better. fix0r3d... thanks for reporting :-) |
As of xscreensaver 4.21, a new feature was introduced that places a "New Login" button to launch a new gdmflexiserver on the Xscreensaver unlock page. Although a very useful feature for gdm users, some users (Like me and several other ATI users) are plagued by a problem that prevents them from launching additional xservers and switching VTs without corrupting the display. Personally I use gdm and like it, but would like some way to keep this feature disabled for xscreensaver. I don't particularly like the thought that anyone can come and click that button and mess up what I had running in X. I think that just using the gnome USE flag to control whether this is disabled is probably a much better idea to do. Reproducible: Always Steps to Reproduce: My current workaround is to replace this block: use gnome || has_version gnome-base/gdm \ && myconf="${myconf} --with-login-manager" \ || myconf="${myconf} --without-login-manager" with: if use gnome; then myconf="${myconf} --with-login-manager" else myconf="${myconf} --without-login-manager" fi