Description of problem: When I try to use beesu with vnc-server, it doesn't work Version-Release number of selected component (if applicable): 2.7 How reproducible: every time Steps to Reproduce: 1. create a launcher .desktop 2. edit the launcher 3. add beesu to the executable in the desktop laucher Actual results: the window for authentification doesn't show. It's very annoying Expected results: the window for authentication must show Additional info: When I try to launch beesu in the gnome-terminal I get this error Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: La connexion est fermée
Please make sure that the following packages are installed on your system: usermode usermode-gtk Part of the problem is that you are trying to run a terminal application using a usermode-based application. In addition, a large part of the problem also is with gnome-terminal. It will throw errors like the above when you try to launch it as superuser from a standard user account. This problem only occurs in the latest few versions of gnome-terminal, but the problem is inherent in gnome-terminal and with how it addresses DBus. Try editing the launcher with the following command line (this assumes use of Gnome 3 or Gnome Classic, which now requires gnome-terminal to be launched first in order to connect with DBus properly before launching the command): gnome-terminal -e "beesu - vncserver" Doing the above will launch vncserver (process name will be Xvnc) as superuser and will close the terminal immediately after running the process. The process itself will remain running. Does that help?
I forgot to mention that if you want the terminal to stay open and give you information relative to your new vncserver session, put the command as follows: gnome-terminal -e "beesu - vncserver && /usr/bin/bash" This will run the terminal command as superuser and then launch an instance of bash to keep the terminal open to show you the information from the vncserver session that was launched. You can then manually run "vncserver -list" in the still open terminal should you need that information, and even be able to manually run "vncserver -kill :1" to kill that session or use other numbers to kill other sessions that might be open. Following that you can type "exit" as normally and exit the superuser terminal window when finished.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.