IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
Hardcode them in the python files, since for some reason glade
just can't be convinced to hang onto them. I know they are deprecated,
but only as of gtk 2.24 which is much newer than our current minimal
target of RHEL6 2.18
Glade is long since deprecated, and the 'glade' tool in F15 and up doesn't
even handle glade format files!
This effectively drops support for running virt-manager on a RHEL5 host,
which has a GTK that is too old to support gtkbuilder.
The process here was:
- On RHEL6, open all glade files with glade3, use Edit->Preferences to
change format to gtk builder. (the gtk-builder-convert tool
produced all sorts of brokenness, and f16 glade3 can't even open
old glade files).
- Open these new files in glade on f16 and resave (since glade is
notorious for reformatting files over new versions, saves churn
the first time someone goes to patch the UI using a modern glade)
Our glib integration had a defect that could cause stalls when streaming
a lot of data (like doing a cat /var/log/messages)
Also, add some tweaks to make the previously stated situation perform
better anyways.
We can get weird keyerrors sometimes, if the global tick thread is
scheduled off while a synchronous tick call is run (like after we create
a vm).
Eventually we will do away with manual tick() invocations but this will
do for now.
VM getinfo returns a system error if we are polling while the guest
is being shutdown (since qemu monitor connection hangs up). Make sure
the conn really dropped before we raise this error, but doing a connection
getinfo call.
Coupled with a recent libvirt patch, try and give more info about
a couple common policykit failure scenarios, like launching virt-manager
over SSH or VNC.
Do this by checking to see if we have a 'session' with ConsoleKit: the
above culprits don't give the user a local session, which causes
PolicyKit to deny.
