Bug 4658 - Xvnc crashes on reset
Summary: Xvnc crashes on reset
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: 4.0.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.1.0
Assignee: Pierre Ossman
URL:
Keywords: aaron_tester
Depends on:
Blocks:
 
Reported: 2013-05-24 10:04 CEST by Aaron Sowry
Modified: 2013-05-28 14:25 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Aaron Sowry cendio 2013-05-24 10:04:48 CEST 
This was tested on F18.

thinlinc-vnc-server-4.0.0post-3960.x86_64
gnome-shell-3.4.1-6.fc17.x86_64

Xvnc: rrmode.c:265: RRModeInit: Assertion `num_modes == 0' failed.
Aborted

To reproduce:
1. Start an Xvnc server - for example:

$ /opt/thinlinc/libexec/Xvnc :1 -query localhost -geometry 1024x768 -depth 16 -ac +extension Composite passwordFile=~/.vnc/passwd

2. Connect to Xvnc server, e.g.:

$ /usr/bin/vncviewer localhost:1

3. Launch a Gnome Shell session on the Xvnc server. e.g.:

$ DISPLAY=:1 dbus-launch gnome-session --session=gnome

4. Click around a bit, launch some things, move them around and wait for the crash.
Comment 1 Pierre Ossman cendio 2013-05-24 11:12:55 CEST 
It is actually simpler than that. Just starting Xvnc and xterm is enough to provoke the bug.

What happens is that RandR checks that everything is cleaned up on a server reset. Apparently we are not doing that properly.
Comment 2 Pierre Ossman cendio 2013-05-24 12:58:21 CEST 
Fixed in r27444.
Comment 3 Aaron Sowry cendio 2013-05-28 14:25:08 CEST 
Could not reproduce using xterm in an Xvnc session. Closing.
Note You need to log in before you can comment on or make changes to this bug.