** Changed in: vino
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562423
Title:
gnome-keyring-manager interferes with the VNC server
To manage notifications about
Hit this issue today trying to enable vino from a remote ssh terminal. Took me
half a day to figure out that the server side popped up the keyring window
causing TightVnc client to hang during authentication.
Sad :(
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I haven't had this issue on recent Ubuntu releases. Is this still
reproducible?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562423
Title:
gnome-keyring-manager interferes with the VNC server
To
Weird, I can just 'kill -9' the 'gnome-keyring-prompt-3' and then it works
fine...
It isn't even really wanting/needing the keyring to be unlocked!
_why would it trigger a keyring unlock prompt if it doesn't need the
keyring unlocked_
and
_could the gnome-keyring connection just be removed c
You can also issue a 'killall gnome-keyring-daemon' from the command line if
you are ssh'ing in from a terminal first or using putty.
You can then bring up the desktop with vnc.
Full description from windows machine:
Open putty and connect.
Open vncviewer and connect.
Issue 'killall gnome-keyring-
dunno if its related/significant but
as of
24.04.2011
21:29:48
a fully updated Debian 6 also suffers this issue. and the described workaround
here works in debian 6 also. :p
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Ubuntu 10.10
#11 + #20 works ok :) thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562423
Title:
gnome-keyring-manager interferes with the VNC server
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Workaround described here DO work in 10.10
but you must NOT use gconf-editer with sudo, that's all
worked at the first try
Thanks again guys ! ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562423
workaround doesn't work in 10.10
tried 3 times as described here:
http://www.lamolabs.org/blog/4380/one-liner-gnomes-vnc-server-vino-prompts-for-the-gnome-keyring-password-on-ubuntu-10-04/
of course running gconf-aditor with sudo
but it seems that /desktop/gnome/remote_access entry is not used by
I am surprised too. This bug is really annoying.
When I want to help my parents (70 years old) they must enter a
password. It is difficult for them every time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
im surprised to see this bug has not been fixed yet;its really annoying and
makes "remote desktop" for managing a computer without physical access
virtually useless...
i suggest putting a medium priority on this one... >.<
--
You received this bug notification because you are a member of Ubunt
I appreciate that this may not be the right way to go about it but I
have managed to get this to work for me.
I currently have Ubuntu running on an old computer which I use as a
file-server, ftp -server, http intranet server and fuppes media server.
I was set to auto login and run fuppes on startu
Which version of the package did you installed to solve the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/562423
Title:
gnome-keyring-manager interferes with the VNC server
--
ubuntu-bugs m
If you're setting up a new machine or one where you haven't already set
a remote desktop password, this can be done from the command line;
vi ~/.gconf/desktop/gnome/remote_access/%gconf.xml
your base64 password
I found the same bug only when configuring Vino checking the box option:
"Configure network automatically to accept connection"
When I check this option the system asked me to set and confirm a new keyring
password that could be different respect VNC access password.
Uncheck this box or reinstal
Thanks bigdigiman, your solution worked for me.
BTW, you can generate the base64 password at the command line;
echo -n "your password" | base64
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a mem
So it is only possible to fix this from the actual machine itself?
I am currently not near this computer and it might be handy for others as well
to know how to do this from command-line (if at all possible).
But seriously, this really needs to be fixed.
--
gnome-keyring-manager interferes with
@Hans - I guess I should have made it clear that I was expecting that
you were running under the user that was to be auto-logged in.
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
ah, scrub that, i do get it to work, as long as i dont run gconf-editor
in sudo. sorry!
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
@bigdigiman
i have tried the workaround 3 times, can't get it to work :(
last time also wrote the BASE64 string manually, at least 90% sure it was no
typing error
(i copied what i had wrote, compared it in gedit, and the 2 strings did look
exactly alike)
--
gnome-keyring-manager interferes with
@Hans
I don't support/maintain or have any connection to the site. It was
simply (as stated) the first google hit for a web service that would
convert a string to BASE64. Conversions to BASE64 usually end with an
'=' character or two and are important and should not be excluded. There
could also b
@bigdigiman
converted from that site, result: password didn't work
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
There are many web pages that will do it for you.
Here is the first google hit: http://www.motobit.com/util/base64
-decoder-encoder.asp
NOTE: You will be sending your password in clear text to the web page
provider that will convert it to BASE64 for you. They won't necessarily
know it's your pass
Thanks, bigdigiman for this workaround!
It works as long as I know what my password is in BASE64.
But how do I convert a new password to BASE64?
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a mem
** Changed in: vino
Status: Unknown => New
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Bug watch added: Debian Bug tracker #581176
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581176
** Also affects: vino via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581176
Importance: Unknown
Status: Unknown
--
gnome-keyring-manager interferes with the VNC server
htt
I have found a workaround for this issue on 10.04.
Open up Applications->Accessories->Passwords and Encryption Keys
Right click Passwords:login and unlock it.
You should be able to expand the tree and find a listing for vino. Right
click and delete it.
Close Passwords and Encryption Keys.
Open
Thanks very much for the help Nigel.
I installed the 'vino' package from Debian unstable in Lucid and
confirmed the bug is still present. I also installed Karmic's package in
Lucid just to re-confirm that it solves the issue.
I'll submit this bug to the Debian bugtracker tomorrow and contact the
I just hunted down and these changes were done at debian level some time
back or upstream level, Ubuntu-specific changes in this package do not
create this problem.
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification be
The maintainer of the package will get around to it. These past weeks
they were either occupied with release or sprints. When the right folks
have the time, they will get around to it. It is extremely rude to
assign bugs to a person or team without their explicit permission
(unless you're assign
Since the package Maintainer of vino is listed as the 'Ubuntu
Development Team', isn't it logical that they be notified of this bug?
This is quite a serious usability issue and a number of people have now
taken the time to diagnose and investigate it. I'm certain that whoever
packaged it would app
@Jackflap: Please DO NOT assign bugs to others.
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
** Changed in: vino (Ubuntu)
Assignee: Ubuntu Development Team (ubuntu-dev) => (unassigned)
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Changed in: vino (Ubuntu)
Assignee: Jonh Wendell (wendell) => Ubuntu Development Team (ubuntu-dev)
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I found out there was a discussion in the developer-team of vino in 2006, see
https://bugzilla.gnome.org/show_bug.cgi?id=344839
They decided to implement an option to use gnome-keyring for security-reasons,
but they also decided to leave it off by default because "it's not really a
good ide
The problem occurs in combination with automatic login, because then the
gnome-keyring is not opened automatically. So if you boot a computer
with wakeonlan with automatic login, you won't be able to reach a vino-
session from remote because you are not able to unlock the gnome-
keyring.
The solut
** Changed in: vino (Ubuntu)
Status: New => Confirmed
** Changed in: vino (Ubuntu)
Assignee: (unassigned) => Jonh Wendell (wendell)
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net/bugs/562423
You received this bug notification because you are a memb
Yann, I tested without Gwibber set-up.
My desktop doesn't ask me to unlock my keyring when it starts up, but it
does when I try to remote desktop. It is definitely being triggered by
the remote desktop connection.
--
gnome-keyring-manager interferes with the VNC server
https://bugs.launchpad.net
Ok, the explanation can be different after a daily use. On GNOME start,
Gwibber need my password for the keyring manager to launch MSN, Facebook
IM etc... that's why the dialog popup (even if I remotly started my PC).
It seems that the keyring manager accept only one application at a time,
that's
I have the same issue. I'm running a fresh install of Lucid 10.04 beta
2. Loaded yesterday. When I log in to my server with VNC the first
time after a reboot it will ask for a password at the console before VNC
session will open. Once I enter the password at the console I'm good.
I have the sy
40 matches
Mail list logo
