Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Richard
On 04/07/2013 07:45 PM, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Check your screen saver settings. It sounds like it's set to lock the screen when it blanks, as that's the default.
On Sun, Apr 7, 2013 at 8:13 PM, Joe Zeff joe@zeff.us wrote:
On 04/07/2013 07:45 PM, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Check your screen saver settings. It sounds like it's set to lock the screen when it blanks, as that's the default.
Why does it lock on default? That is not the best solution. At least I know a little bit about how to fix it, but I can just imagine the person coming over from the MS world having a heart attack just trying how to keep the computer from crashing.
On Sun, 7 Apr 2013 20:40:19 -0700 Richard Vickery richard.vickeryrv@gmail.com wrote:
On Sun, Apr 7, 2013 at 8:13 PM, Joe Zeff joe@zeff.us wrote:
On 04/07/2013 07:45 PM, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Check your screen saver settings. It sounds like it's set to lock the screen when it blanks, as that's the default.
Why does it lock on default? That is not the best solution. At least I know a little bit about how to fix it, but I can just imagine the person coming over from the MS world having a heart attack just trying how to keep the computer from crashing.
It's a matter of opinion, many people would find locking to be best. People working on sensitive or important data in an area where other people or especially children were around find that useful. As far as people from the MS world...from what I've seen, they have plenty of experience with crashing computers =:)
On Apr 7, 2013 9:35 PM, "Fred Erickson" fredferickson@gmail.com wrote:
On Sun, 7 Apr 2013 20:40:19 -0700 Richard Vickery richard.vickeryrv@gmail.com wrote:
On Sun, Apr 7, 2013 at 8:13 PM, Joe Zeff joe@zeff.us wrote:
On 04/07/2013 07:45 PM, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Check your screen saver settings. It sounds like it's set to lock the screen when it blanks, as that's the default.
Why does it lock on default? That is not the best solution. At least I know a little bit about how to fix it, but I can just imagine the person coming over from the MS world having a heart attack just trying how to keep the computer from crashing.
It's a matter of opinion, many people would find locking to be best. People working on sensitive or important data in an area where other people or especially children were around find that useful. As far as people from the MS world...from what I've seen, they have plenty of experience with crashing computers =:) --
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
Allegedly, on or about 08 April 2013, Richard Vickery sent:
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
As soon as you go for the mouse or keyboard, a logon prompt appears for you to type in the password.
If that's not happening, then it's not a screensaver lockout that you're facing. But most likely a graphics crash. Sometimes that's caused by a screensaver, some of them are just not that well written, and crash when they're fired up.
On 04/08/2013 11:24 AM, Tim wrote:
Allegedly, on or about 08 April 2013, Richard Vickery sent:
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
As soon as you go for the mouse or keyboard, a logon prompt appears for you to type in the password.
If that's not happening, then it's not a screensaver lockout that you're facing. But most likely a graphics crash. Sometimes that's caused by a screensaver, some of them are just not that well written, and crash when they're fired up.
Don't mean to take this too OT, but this is now sounding like the regular "graphics crash" I have whenever I wake my laptop up from hibernation. Happens consistently with all 3.8.x kernels so far; not with the last 3.7.x kernel.
Tim Evans wrote:
On 04/08/2013 11:24 AM, Tim wrote:
Allegedly, on or about 08 April 2013, Richard Vickery sent:
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
As soon as you go for the mouse or keyboard, a logon prompt appears for you to type in the password.
If that's not happening, then it's not a screensaver lockout that you're facing. But most likely a graphics crash. Sometimes that's caused by a screensaver, some of them are just not that well written, and crash when they're fired up.
Don't mean to take this too OT, but this is now sounding like the regular "graphics crash" I have whenever I wake my laptop up from hibernation. Happens consistently with all 3.8.x kernels so far; not with the last 3.7.x kernel.
If you have an ATI/Radeon video setup and are using the stock kernel driver instead of the vendor driver, I've seen this before. There are two ways to attack this: 1 - install the vendor driver for your kernel (I have not had any problems doing this but your computer will be impure) 2 - you can try adding "nomodset" to the kernel command via editing at boot time (in case it totally screws up your video). I have had this work in about 30% of the machines I tested.
Like any advice regarding kernel command options and/or vendor drivers, use your own judgement, this is history of my experience, not advice.
On 04/08/2013 01:41 PM, Bill Davidsen wrote:
Tim Evans wrote:
On 04/08/2013 11:24 AM, Tim wrote:
Allegedly, on or about 08 April 2013, Richard Vickery sent:
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
As soon as you go for the mouse or keyboard, a logon prompt appears for you to type in the password.
If that's not happening, then it's not a screensaver lockout that you're facing. But most likely a graphics crash. Sometimes that's caused by a screensaver, some of them are just not that well written, and crash when they're fired up.
Don't mean to take this too OT, but this is now sounding like the regular "graphics crash" I have whenever I wake my laptop up from hibernation. Happens consistently with all 3.8.x kernels so far; not with the last 3.7.x kernel.
If you have an ATI/Radeon video setup and are using the stock kernel driver instead of the vendor driver, I've seen this before. There are two ways to attack this: 1 - install the vendor driver for your kernel (I have not had any problems doing this but your computer will be impure) 2 - you can try adding "nomodset" to the kernel command via editing at boot time (in case it totally screws up your video). I have had this work in about 30% of the machines I tested.
Like any advice regarding kernel command options and/or vendor drivers, use your own judgement, this is history of my experience, not advice.
Nvidia/Nouveau drivers here.
# lspci -s 01:00.0 -k 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M] (rev a1) Subsystem: Lenovo ThinkPad T61 Kernel driver in use: nouveau
I have filed bug https://bugzilla.redhat.com/show_bug.cgi?id=949666
Tim Evans wrote:
On 04/08/2013 01:41 PM, Bill Davidsen wrote:
Tim Evans wrote:
On 04/08/2013 11:24 AM, Tim wrote:
Allegedly, on or about 08 April 2013, Richard Vickery sent:
In the case where you have sensitive information that you don't want people looking at it, or children deleting it, how does one get back from this screen without rebooting and losing ones work?
As soon as you go for the mouse or keyboard, a logon prompt appears for you to type in the password.
If that's not happening, then it's not a screensaver lockout that you're facing. But most likely a graphics crash. Sometimes that's caused by a screensaver, some of them are just not that well written, and crash when they're fired up.
Don't mean to take this too OT, but this is now sounding like the regular "graphics crash" I have whenever I wake my laptop up from hibernation. Happens consistently with all 3.8.x kernels so far; not with the last 3.7.x kernel.
If you have an ATI/Radeon video setup and are using the stock kernel driver instead of the vendor driver, I've seen this before. There are two ways to attack this: 1 - install the vendor driver for your kernel (I have not had any problems doing this but your computer will be impure) 2 - you can try adding "nomodset" to the kernel command via editing at boot time (in case it totally screws up your video). I have had this work in about 30% of the machines I tested.
Like any advice regarding kernel command options and/or vendor drivers, use your own judgement, this is history of my experience, not advice.
Nvidia/Nouveau drivers here.
# lspci -s 01:00.0 -k 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M] (rev a1) Subsystem: Lenovo ThinkPad T61 Kernel driver in use: nouveau
I have filed bug https://bugzilla.redhat.com/show_bug.cgi?id=949666
I wish you luck in that, and hope you get your system working without the vendor driver. You also might just use the VESA driver, if you're not a gamer it may be fast enough to be useful.
On 04/07/2013 08:40 PM, Richard Vickery wrote:
Why does it lock on default? That is not the best solution. At least I know a little bit about how to fix it, but I can just imagine the person coming over from the MS world having a heart attack just trying how to keep the computer from crashing.
Don't ask me, I think it's silly too.
On 04/07/2013 10:45 PM, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Thanks.
Richard
You can always check the display settings on your System Settings tool.
I use KDE. For a long time KDE blanked out the screen, and all I had to do was move the mouse to un-blank it. Then came the locking option.
But then I installed the kde-screensaver package. (There's one for gnome, too; I don't know about XFCE or other desktops.) Then at last I could use the plethora of options I once had under xscreensaver. Only now they're built-in to System Settings and do not try to load as a separate terminate/stay-resident routine. I set my screensaver to display a slideshow, based on the same options I use to show a "slideshow wallpaper."
I also made sure to set screensaver on, and turn the lock off. (My computer is in a room that only I ever visit.)
Temlakos
On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Do you mean your computer is frozen (crashed) when that happens? Else it's the screen blanker, and you could simply move the mouse or use the keyboard, and the system would detect that as activity.
On Apr 8, 2013 5:18 AM, "Michael Schwendt" mschwendt@gmail.com wrote:
On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Do you mean your computer is frozen (crashed) when that happens? Else it's the screen blanker, and you could simply move the mouse or use the keyboard, and the system would detect that as activity.
-- Fedora release 19 (Schrödinger’s Cat) - Linux
3.9.0-0.rc5.git1.301.fc19.x86_64
loadavg: 0.29 0.43 0.37
It can't simply be crashed every time I simply leave it?
On Mon, 8 Apr 2013 06:52:04 -0700, Richard Vickery wrote:
On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for it to blacken the screen. Is there a combination key stroke to get x back?
Do you mean your computer is frozen (crashed) when that happens? Else it's the screen blanker, and you could simply move the mouse or use the keyboard, and the system would detect that as activity.
It can't simply be crashed every time I simply leave it?
Why not? That's what can happen with bugs in the software. I've encountered it too with F19 development (and ATI Radeon graphics). Visiting "Settings > Power" in GNOME Shell, I disabled the screen blanker (set it to "Never") or else I would return to the machine and fit it with the monitor in power-saving mode and with no way to wake it up. It's not supposed to be like that. It's misbehaviour. A bug somewhere. Currently, everything is fine again.
In other words, people in this thread have misunderstood eachother. "Locking" the screen does not refer to freezing the machine or crashing X but just to displaying a passphrase prompt after you've left the machine unattended for some time. That can be separate from the screen blanker (or screen saver) activity. Neither should make your system unusable. That's a bug.
On 04/08/2013 07:18 AM, Michael Schwendt wrote:
In other words, people in this thread have misunderstood eachother. "Locking" the screen does not refer to freezing the machine or crashing X but just to displaying a passphrase prompt after you've left the machine unattended for some time. That can be separate from the screen blanker (or screen saver) activity. Neither should make your system unusable. That's a bug.
I'm the one who brought it up. I wanted to make sure that the computer was hung, not just that the screensaver was locked.
On Apr 8, 2013 7:18 AM, "Michael Schwendt" mschwendt@gmail.com wrote:
On Mon, 8 Apr 2013 06:52:04 -0700, Richard Vickery wrote:
On Sun, 7 Apr 2013 19:45:43 -0700, Richard Vickery wrote:
Hi,
It happens often enough that I leave the computer long enough for
it to
blacken the screen. Is there a combination key stroke to get x back?
Do you mean your computer is frozen (crashed) when that happens? Else it's the screen blanker, and you could simply move the mouse or
use
the keyboard, and the system would detect that as activity.
It can't simply be crashed every time I simply leave it?
Why not? That's what can happen with bugs in the software. I've encountered it too with F19 development (and ATI Radeon graphics). Visiting "Settings > Power" in GNOME Shell, I disabled the screen blanker (set it to "Never") or else I would return to the machine and fit it with the monitor in power-saving mode and with no way to wake it up. It's not supposed to be like that. It's misbehaviour. A bug somewhere. Currently, everything is fine again.
In other words, people in this thread have misunderstood eachother. "Locking" the screen does not refer to freezing the machine or crashing X but just to displaying a passphrase prompt after you've left the machine unattended for some time. That can be separate from the screen blanker (or screen saver) activity. Neither should make your system unusable. That's a bug.
-- Fedora release 19 (Schrödinger’s Cat) - Linux
3.9.0-0.rc5.git1.301.fc19.x86_64
loadavg: 0.14 0.17 0.15
How do I find this bug in order to report it? And is it worth reporting since f19 will be beta soon, at which time I'll upgrade?
On 04/08/2013 11:57 AM, Richard Vickery wrote:
How do I find this bug in order to report it? And is it worth reporting since f19 will be beta soon, at which time I'll upgrade?
Before you do, one question: are you using nVidia graphics, and if so, are you using the proprietary drivers, or nouveau? I ask because there was a time the nVidia drivers had problems with screen savers using "line drawing," and this might be related.
On Mon, Apr 8, 2013 at 12:21 PM, Joe Zeff joe@zeff.us wrote:
On 04/08/2013 11:57 AM, Richard Vickery wrote:
How do I find this bug in order to report it? And is it worth reporting since f19 will be beta soon, at which time I'll upgrade?
Before you do, one question: are you using nVidia graphics, and if so, are you using the proprietary drivers, or nouveau?
I don't believe so; what's the command that prints the hardware?
Am 08.04.2013 21:29, schrieb Richard Vickery:
On Mon, Apr 8, 2013 at 12:21 PM, Joe Zeff <joe@zeff.us mailto:joe@zeff.us> wrote:
On 04/08/2013 11:57 AM, Richard Vickery wrote: How do I find this bug in order to report it? And is it worth reporting since f19 will be beta soon, at which time I'll upgrade? Before you do, one question: are you using nVidia graphics, and if so, are you using the proprietary drivers, or nouveau?I don't believe so; what's the command that prints the hardware?
[harry@srv-rhsoft:~]$ lspci | grep -i graphic 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
[harry@srv-rhsoft:~]$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.4 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) 00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 01:00.0 Network controller: Atheros Communications Inc. AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn] (PCI-Express) (rev 01) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
On 04/08/2013 12:29 PM, Richard Vickery wrote:
I don't believe so; what's the command that prints the hardware?
lspci | grep VGA
However, if you have to ask, you probably aren't using the binary blob drivers, either directly from the OEM, in either the kmod or akmod package, unless it's been so long since you last installed that you'd forgotten about it. And, to be honest, I don't know if that issue's ever been resolved, because I simply set my desktop to use one screen saver (I'd wanted to use them all, randomly, and that's how I ran across this.) as a work around. Still, it's worth checking, JIC.
-
Bill Davidsen -
Fred -
Joe Zeff -
Michael Schwendt -
Reindl Harald -
Richard Vickery -
Temlakos -
Tim -
Tim Evans