vinagre, if server pc goes on screen-saver it don't receive any input from remote access: mouse click or any keyboard events...
Bug #869803 reported by
marcobra (Marco Braida)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vinagre (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
vinagre:
Installato: 3.2.0-0ubuntu1
Description: Ubuntu oneiric (development branch)
Release: 11.10
Candidato: 3.2.0-0ubuntu1
Tabella versione:
*** 3.2.0-0ubuntu1 0
500 http://
100 /var/lib/
vino:
Installato: 3.2.0-0ubuntu1
Candidato: 3.2.0-0ubuntu1
Tabella versione:
*** 3.2.0-0ubuntu1 0
500 http://
100 /var/lib/
Both pc are using same upgraded/updated just rebooted oneiric, i have done remote access using vinagre to remote vino.
There is no way to unlock the remote desktop.
summary: |
- remote deskto on screen-saver locked both with oneiric unstable cannot - input passwd an send click or enter or tab events.... + remote desktop is on screen-saver locked both with oneiric unstable + cannot input passwd an send click or enter or tab events.... |
summary: |
- remote desktop is on screen-saver locked both with oneiric unstable - cannot input passwd an send click or enter or tab events.... + remote desktop is on screen-saver i must unlock it cannot send any + input: passwd mouse click or enter or tab... |
description: | updated |
description: | updated |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!