[Bug 257451] New: suspend to ram: disturbing vt_switch mode
https://bugzilla.novell.com/show_bug.cgi?id=257451 Summary: suspend to ram: disturbing vt_switch mode Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: bluedzins@wp.pl QAContact: sndirsch@novell.com If vt_switch is just a help comparing to "ignore" mode by switching to text mode and back to X11 it should do only this. And nothing more. But currently it displays some fractals, then it locks the session (I didn't ask for that, quite contrary I set not to lock the screen), displays my signature email (what this have to do with power management ???). Honestly, my first though, gosh, I have a virus ;-) Please, do this plain and simple, just switch graphics modes, and nothing else (in other words -- follow the description of the vt_switch). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 ------- Comment #1 from seife@novell.com 2007-03-26 09:09 MST ------- Just that we understand exactly what the problem is: - what did you do (exactly)? - what happened after that? - what did you expect to happen? It looks that the xlock screen saver kicked in, but we need to determine why. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 sndirsch@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bluedzins@wp.pl -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bluedzins@wp.pl | ------- Comment #2 from bluedzins@wp.pl 2007-03-26 10:59 MST ------- If I miss any detail, please let me know, I would like to cover all needed info. 0) my intention is to configure lid closing to make suspend to ram, from previous experience I suspected it would be hard to recover the screen from suspend mode, I use this feature rather from time to time, not often 1.a) yesterday I was testing svideo out, which involved installing and reinstalling xorg-x11-server and xorg-x11-video, so today I wanted to make sure the lid close is working. It was not, the screen got black, the power led was not blinking, so I took a look at the yast settings, I noticed LID OPEN set to ignore, so I switched it to vt_switch 1.b) I rebooted the machine and tested it 2) in short, no matter what I set now, ignore, or vt_switch (LID OPEN), suspend to ram works (worse than in 10.0, reported), so here is OK, however, when I open the lid, there is strange animation going on, touchpad is not responding, if I press a key, I get the screen with login prompt, small animation in upper, left corner, the mail sig at the bottom 3) just KDE screen recover, so I could continue exactly from where I finished, if I would set lock the screen on the lid close (I didn't) I would expect normal, KDE-unlock screen dialog, not this one And about screen savers, I use only "blank screen", nothing fancy, the screen gets black and that's it. PS. I don't use kpowersave. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |bluedzins@wp.pl ------- Comment #3 from hmacht@novell.com 2007-03-27 05:08 MST ------- (In reply to comment #2)
If I miss any detail, please let me know, I would like to cover all needed info.
0) my intention is to configure lid closing to make suspend to ram, from previous experience I suspected it would be hard to recover the screen from suspend mode, I use this feature rather from time to time, not often
1.a) yesterday I was testing svideo out, which involved installing and reinstalling xorg-x11-server and xorg-x11-video, so today I wanted to make sure the lid close is working. It was not, the screen got black, the power led was not blinking, so I took a look at the yast settings, I noticed LID OPEN set to ignore, so I switched it to vt_switch
I don't have an option to define what to do for LID OPEN in YaST in openSUSE 10.2, sorry. Please clarify how you specified to vt_switch on LID OPEN.
1.b) I rebooted the machine and tested it
2) in short, no matter what I set now, ignore, or vt_switch (LID OPEN), suspend to ram works (worse than in 10.0, reported), so here is OK, however, when I open the lid, there is strange animation going on, touchpad is not responding, if I press a key, I get the screen with login prompt, small animation in upper, left corner, the mail sig at the bottom
That's xlock I suppose. Please execute xlock from a terminal and tell me if it's the same window.
3) just KDE screen recover, so I could continue exactly from where I finished, if I would set lock the screen on the lid close (I didn't) I would expect normal, KDE-unlock screen dialog, not this one
And about screen savers, I use only "blank screen", nothing fancy, the screen gets black and that's it.
PS. I don't use kpowersave.
If you don't use kpowersave, don't expect to get the kde screensaver. If you're not using kpowersave we only do some basic stuff. Anyway, please tell me your exact problem ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 bluedzins@wp.pl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|bluedzins@wp.pl | ------- Comment #4 from bluedzins@wp.pl 2007-03-27 10:18 MST -------
I don't have an option to define what to do for LID OPEN in YaST in openSUSE 10.2, sorry. Please clarify how you specified to vt_switch on LID OPEN.
Yast -> sysconf editor -> system -> power management -> events -> EVENT_BUTTON_LID_OPEN.
That's xlock I suppose. Please execute xlock from a terminal and tell me if it's the same window.
No, it is completely different. Xclock is just, well, a clock. This thing I described, there is no clock, it is some bizarre figures, fractals-like (but is random, so once it was rotating cube-frame). And with very slow drawing.
If you don't use kpowersave, don't expect to get the kde screensaver.
I don't. Lid close (configured with StR) should suspend the system, and then recover. Nothing more.
If you're not using kpowersave we only do some basic stuff.
Kpowersave is another story, but I report another report for it as soon as I get this one working. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 ------- Comment #5 from seife@novell.com 2007-03-27 10:39 MST ------- (In reply to comment #4)
That's xlock I suppose. Please execute xlock from a terminal and tell me if it's the same window.
No, it is completely different. Xclock is just, well, a clock. This thing I
xlock, not xclock.
If you don't use kpowersave, don't expect to get the kde screensaver.
I don't. Lid close (configured with StR) should suspend the system, and then recover. Nothing more.
Suspend locks the screen for security reasons, by using xlock. See /etc/powersave/events, EVENT_GLOBAL_SUSPEND*. There is a "screen_saver" in that event. Remove that and you probably won't get the xlock screensaver again. But your session will not be locked after resume. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 ------- Comment #6 from bluedzins@wp.pl 2007-03-27 12:33 MST ------- Hurray! :-D It works. Thank you very much. Sorry about the xlock-xclock :-) It was it, but how it get to suspend to ram, I don't know. I didn't change anything except LID CLOSE & OPEN. I am not closing this report, since I don't know if this xlock was intentional (imho there should be no such think, but that's just my 2 cents). Thank you:-). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 hmacht@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #7 from hmacht@novell.com 2007-04-02 02:17 MST ------- (In reply to comment #6)
Hurray! :-D It works. Thank you very much.
Sorry about the xlock-xclock :-) It was it, but how it get to suspend to ram, I don't know. I didn't change anything except LID CLOSE & OPEN.
I am not closing this report, since I don't know if this xlock was intentional (imho there should be no such think, but that's just my 2 cents).
From a security point of view, you need at least _something_. Otherwise the system would be completely vulnerable after waking up. And because of the fact that you don't use a graphical frontend like kpowersave or gnome-power-manager, we are trying to find the least common denominator, which is xlock.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=257451 behlert@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com