Bug 578765 - vnc and rdesktop and virt-manager does not allow screen saver to work
Summary: vnc and rdesktop and virt-manager does not allow screen saver to work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rdesktop
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-01 10:02 UTC by Mohammed Arafa
Modified: 2014-06-18 09:12 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 16:29:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 224207 0 None None None Never

Description Mohammed Arafa 2010-04-01 10:02:49 UTC
Description of problem:
i use krdc to vnc and rdp to other machines and virtual machines. i noticed that the screen saver does not kick in when krdc is in full screen mode.

i also use virt-manager to view my virtual machines and noticed that when the viewer is in full screen mode, it too does not allow the kde's blank screen saver to kick in.

i had previously reported the bug to https://sourceforge.net/tracker/?func=detail&aid=2946948&group_id=24366&atid=381350 and to https://bugs.kde.org/show_bug.cgi?id=224207 

but now i find it in virt-manager and i am at a loss as to which component of kde is faulty here which is why i am reporting it against kdebase.

thanks for listening


Version-Release number of selected component (if applicable):


How reproducible:
every time

Steps to Reproduce:
1.run krdc session (vnc/rdp) or virt-manager session in full screen mode
2.configure kblankscreen for 1 minute
3.leave idle for more than 1 minute
  
Actual results:
nothing

Expected results:
the screen saver should kick in after 1 minute

Additional info:

Comment 1 Rex Dieter 2010-04-17 18:52:19 UTC
According to these upstream reports , it's rdesktop to blame here.

Comment 2 Rex Dieter 2010-04-17 18:53:32 UTC
let's triage this to rdesktop

Comment 3 Bug Zapper 2010-11-03 18:07:56 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-03 16:29:44 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.