You are not logged in.

#1 2012-04-25 18:53:17

BinaryMan
Member
Registered: 2011-07-19
Posts: 14

Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

I'm at work, trying to replace compiz with xfwm4 using:

# xfwm4 --replace

Unfortunately, I can't detail everything I've done since I rebooted dbus, unaware that this would break networkmanager and kick my laptop off my home network. However, I'll try providing as much information as I can from memory.

I started off setting up vnc by following the recent comments left on the page for the tigervnc AUR listing (there's a link to the Fedora forums how to edit xorg.conf). Afterwards, I started GDM and started getting some gnome DislayWindow error, which I was able to fix by removing /usr/share/gnome-shell and reinstalling gnome-shell, but I was still having issues starting GDM. After checking /var/log/gdm/:0-greeter.log, I saw a bunch of missing gnome-session/gdm-shell errors, which I fixed by reinstalling the respective packages.

Finally, I was able to successfully start GDM and then pull up a VNC session on port 5900. Unfortunately, I had a black background without a login prompt (but my mouse worked). After checking :0-greeter.log again, I saw something about compositing errors. At this point, I remembered I had followed the Xfce4 wiki guide to permanently change the window manager from xfwm4 to compiz. So, I reflexively ran the above command, only to get some error about how it wouldn't work (something about a session name environment variable not set. So, after some more research, I figured out how to properly set the session name variable. So I set it and tried replacing compiz with xfwm4 again, only to get the following error:

Failed to connect to session manager: Failed to connect to the session manager: None of the authentication protocols specified are supported

After even more research, I read something about how this might be a problem with dbus, so I restarted dbus, which seemed to have reset the networkmanager service and my laptop is now off the network and I can't do anything more until I get home and put it back on the network.

With all this information, can someone tell me or point me in the right direction on how to change an exisiting X session's window manager so I can access it via VNC?

Thanks.

Offline

#2 2012-04-25 20:34:19

ConnorBehan
Package Maintainer (PM)
From: Long Island NY
Registered: 2007-07-05
Posts: 1,359
Website

Re: Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

Not as graceful but have you tried simply killing compiz and then starting xfwm4 with no arguments?


6EA3 F3F3 B908 2632 A9CB E931 D53A 0445 B47A 0DAB
Great things come in tar.xz packages.

Offline

#3 2012-04-26 04:52:09

BinaryMan
Member
Registered: 2011-07-19
Posts: 14

Re: Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

I did. Unfortunately, that didn't work.

However, after not being under the gun at work while trying to do this, I've been able to come up with a better solution to do this, but allow me to explain what was causing my problem first.

The changes to my xorg.conf file had me create a new section as detailed below:

Section "Module"
    Load "vnc"
EndSection

This is what ended up breaking everything. After I commented out that section, I was able to get GDM back up and working fine.

However, my ultimate solution to this was running the following commands:

# touch /var/log/vnc.0.log
# chmod 744 /var/log/vnc.0.log
# chown <user> /var/log/vnc.0.log
$ x11vnc -noxdamage -display :0.0  -forever -rfbauth $USER/.vnc/passwd -o /var/log/vnc.0.log &

In my case, I replaced <user> with my username and set that command to an alias in .bash_alias. The -noxdamage flag allows me to pull up a VNC session with compiz running. Be sure to run vncpasswd as the user you'll be running this command as so the passwd file is created in ~/.vnc/passwd. The chmodding and chowning to the log file you created makes it so you don't have to change the folder/group/permission settings on /var/log.

Also, be sure you have x11vnc installed.

Last edited by BinaryMan (2012-04-26 04:53:15)

Offline

#4 2012-04-26 08:48:30

Gusar
Member
Registered: 2009-08-25
Posts: 3,607

Re: Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

Just checking... Do you use the proprietary Nvidia driver?

Yeah, x11vnc is another possibility, but with -nodamage comes quite a performance hit and bandwidth increase, as the entire screen is constantly being refreshed instead of only the parts that need to be (the "damaged" parts).

Offline

#5 2012-04-26 12:20:59

BinaryMan
Member
Registered: 2011-07-19
Posts: 14

Re: Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

Gusar wrote:

Just checking... Do you use the proprietary Nvidia driver?

Yes.

Gusar wrote:

Yeah, x11vnc is another possibility, but with -nodamage comes quite a performance hit and bandwidth increase, as the entire screen is constantly being refreshed instead of only the parts that need to be (the "damaged" parts).

Do you have a better solution?

Offline

#6 2012-04-26 13:05:58

Gusar
Member
Registered: 2009-08-25
Posts: 3,607

Re: Replacing compiz with xfwm4 over SSH to VNC into exisiting X session

BinaryMan wrote:
Gusar wrote:

Just checking... Do you use the proprietary Nvidia driver?

Yes.

Yep, I immediately recognized the symptoms. The issue is that with the nvidia blob, X runs out of slots for extensions. The solution I came up with is disabling some extensions no one is using anymore:

Section "Module"
	Load		"vnc"
	Subsection	"extmod"
	    Option "omit xfree86-dga"
	    Option "omit xvideo-motioncompensation"
	EndSubsection
EndSection

Offline

Board footer

Powered by FluxBB