You are not logged in.
Pages: 1
Update to dbus-1.12.10-2 breaks tigervnc vncserver with
** (process:2018): WARNING **: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=GNOME environment variable: The connection is closedvncviewer connects to a black screen. My setup is standard xstartup -> /etc/X11/xinit/xinitrc -> exec gnome-session
Downgrade to dbus-1.12.10-1 fixes it.
Offline
Did you mean to post this on the Bug Tracker?
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I posted this here in case someone may find the info to be useful, better still if they managed to have tigervnc working with dbus-1.12.10-2 and want to share.
Offline
I wasn't sure since there was no question in your first post. If you haven't, I'd suggest logging a bug too to actually get it fixed; the devs mostly don't read the boards so they won't see it here.
Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
I don't think this is a bug, afaik X11 based dbus autolaunching was accidentally reintroduced with 1.12.10-1 and then willfully disabled again with -2
Offline
I don't think this is a bug, afaik X11 based dbus autolaunching was accidentally reintroduced with 1.12.10-1 and then willfully disabled again with -2
What is the proper way to start vncserver@:1.service with dbus autolaunching disabled? In other distros, I changed from exec to dbus-launch in xstartup to avoid the black screen but this just crashes in Arch.
Offline
Pages: 1