Created attachment 334550 [details] virt-manager.log Description of problem: With virt-manager-0.6.1-1.fc10 the connection to the virt host is opened read-only, but with 0.6.0 it would (ask for a password and) connect read-write. I'm running it in a VNC session started by the vncserver service. Version-Release number of selected component (if applicable): virt-manager-0.6.1-1.fc10 How reproducible: 100%
Few questions: - Are you running as a regular user or root? - If regular user, in previous versions of virt-manager, were you choosing 'Run Unprivileged' or entering root passwd when the console helper dialog launched at app startup? - Have you always run over VNC? If not, does the old version over VNC work? Thanks
The problem will be that 'vncserver' doesn't integrate well with desktop services. In particular ConsoleKit can't see any sessions running under the vncserver, and thus PolicyKit authentication won't work, and thus virt-manager will only be able to open a read-only connection. There's not much we can do about this in virt-manager - vncserver is just not sufficiently functional as a desktop environment. Instead of vncserver, I'd recommend enabling 'vino' in your regular X session, so when logging in via GDM all the session stuff gets setup correctly & you can remotely access it.
There is no regular X session; vncserver is it. Yes, the old version works in a VNC session, and asks for the root password.
The old version worked because it used consolehelper, I guess Moving to ConsoleKit - unless there is a generic way for ConsoleKit/PolicyKit to work with vncserver sessions, I guess this is a WONTFIX
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
*** Bug 523336 has been marked as a duplicate of this bug. ***
Any chance of this getting addressed?
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. 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 '10'. 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 10'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 10 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
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.
Fedora 13: I’m getting these problems related to ConsoleKit on vncserver, I cant run a regular X (so comment 2 is out of luck) sessions because the server is headless and with nv driver, X wont start without a monitor attached. Some older preference applications correctly ask for passwords, some dont ask then fail when you try to do something (pressing apply in add/remove software), and some error with policy kit warnings (firewall). Its, er, messy.