Bug 10181 - vncserver script has the wrong path to start java client applet
Summary: vncserver script has the wrong path to start java client applet
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
Whiteboard: feedback MGA3-64-OK MGA3-32-OK
Keywords: Junior_job, validated_update
Depends on:
Blocks: 5045
  Show dependency treegraph
Reported: 2013-05-20 18:31 CEST by Dennis Griffin
Modified: 2013-09-19 10:29 CEST (History)
6 users (show)

See Also:
Source RPM: tigervnc-server-1.1.0-3.mga2
Status comment:


Description Dennis Griffin 2013-05-20 18:31:12 CEST
Description of problem:

When tigervnc-java and tigervnc-server are installed the java applet does not start.  The java classes are installed in /usr/share/tigervnc/classes but the vncserver script (/usr/bin/vncserver) is lookig for them in /usr/share/vnc/classes

I changed line 51 of the vncserver script to:

$vncJavaFiles = (((-d "/usr/share/tigervnc/classes") && "/usr/share/tigervnc/classes") ||

and the applet works correctly.

Version-Release number of selected component (if applicable):


How reproducible:
Always unless you change the vncserver script or the path where the tiger-java classes are installed.

Steps to Reproduce:
1.install tigervnc-java and tigervnc-server
2.start server (run vncserver)
3.try to connect from web browser to host:5801.  No connection is made.


Steps to Reproduce:
Manuel Hiebel 2013-05-21 23:40:16 CEST

Keywords: (none) => Junior_job
Version: 3 => Cauldron
Source RPM: tigervnc-server1.1.0-3.mga2 => tigervnc-server-1.1.0-3.mga2

Manuel Hiebel 2013-05-21 23:40:28 CEST

Version: Cauldron => 3

Comment 1 Alfonso Vera 2013-05-27 12:33:48 CEST

I'll try to reproduce and fix this bug. Be patient, I'm just an apprentice


CC: (none) => bersuit.vera, juan.baptiste
Assignee: bugsquad => bersuit.vera

Comment 2 Alfonso Vera 2013-06-29 11:00:34 CEST
I compile and I solve this bug for tigervnc. The package doesn't compile a long time ago . Now, it's working fine.Comin soon, I'll write the advisory and I'll commit the changes to svn
@Dennis Griffin this bug is mga2 or mga3 ?
Comment 3 Dennis Griffin 2013-06-29 18:28:50 CEST
I have this running on Mga3 but the installed version of tigervnc-server and tigervnc-java is 1.1.0-3.mga2 which is what is in core/release.
Comment 4 Samuel Verschelde 2013-08-26 15:10:05 CEST
Hi Alfonso, please see also bug #5045 for mga2 and mga3. The patches you synced from Fedora should have fixed it in cauldron, but it still needs update candidates for mga2 and mga3
Samuel Verschelde 2013-08-26 15:10:10 CEST

CC: (none) => stormi

Comment 5 Samuel Verschelde 2013-09-05 10:04:25 CEST
Ping Alfonso Vera, users are waiting for a fix in mga2 and mga3 :)
Comment 6 Alfonso Vera 2013-09-05 10:28:28 CEST
Hi Samuel.
I have a problem in the buildsystem:
I created the rpm with "bm" well done
I created the rpm with "iurt" in localhost well done
 but in the buildsystem ... 

I don't have the solution as yet :-(

Can you help me ?

Comment 7 Samuel Verschelde 2013-09-05 11:04:08 CEST
You should compare the list of installed packages in http://pkgsubmit.mageia.org/uploads/failure/3/core/updates_testing/20130825234428.juancho.valstar.14139/log/tigervnc-1.1.0-3.1.mga3/ with your iurt build. Maybe there's a difference in openjdk version or something else. 

Same causes produce same effects, so you've got to find what in the causes is different.
Comment 8 Alfonso Vera 2013-09-06 08:20:21 CEST
Yahooo!!!!!!!!!! :-P
I have uploaded a patched tigervnc for Mageia 3.

Suggested advisory:

Updated tigervnc packages to fix #mga10181 :
This update changes the java classes path /usr/share/tigervnc/classes
to /usr/share/vnc/classes

This update also add Fedora patchs:
Rebuilt xorg110 & xorg111 patch
Added patch to xorg112 & xorg113
Added patch to latest Java 7


Updated packages in core/updates_testing:

Source RPMs:

Assignee: bersuit.vera => qa-bugs

Comment 9 claire robinson 2013-09-06 08:26:29 CEST
Thanks Alfonso
Comment 10 Samuel Verschelde 2013-09-06 09:01:25 CEST
Alfonso, we also need an update for Mageia 2, to fix bug #5045. Thanks!
Comment 11 Dave Hodgins 2013-09-06 23:48:17 CEST
Here's the script I use with tigervnc.

I ssh from my system, to the remote system, as the user running X on that
system, then run the following script.

$ cat bin/myvnctiger 
killall x0vncserver
x0vncserver display=:0 -SecurityTypes=None &
sleep 4
vncviewer -compresslevel 9 localhost:0
killall x0vncserver

CC: (none) => davidwhodgins

Comment 12 Dave Hodgins 2013-09-12 23:35:11 CEST
Advisory 10181.adv committed to svn.
Comment 13 Dave Hodgins 2013-09-13 21:52:51 CEST
I've completed testing on Mageia 3 i586, and x86_64.

Few things I've found.

The description indicates the browser should connect to localhost:5801,
but I found it's actually localhost:5802.

With lxde in use on the target host, the logout button doesn't do anything.

With kde in use on the target host, if you logout before closing the
vncviewer, then when you start it again, x starts, but kde does not,
until the server is restarted.  If you don't log out of kde, then
closing/restarting the vncviewer works ok.

As per comment 7, I haven't used tigervnc-java, or tigervnc-server-module
before, so I'm not sure if this is normal.

Also, it doesn't work if the target host is running under virtualbox.

Alfonso, before I validate the update, is the above normal?

Whiteboard: (none) => feedback

claire robinson 2013-09-16 10:12:09 CEST

Blocks: (none) => 5045

Comment 14 Dave Hodgins 2013-09-17 00:02:00 CEST
As Alfonso pointed out to me,
explains why vnc doesn't work with vb.

The port number, is due to the /etc/sysconfig/vncservers settings, using
the 2:user.

The problem with logging out, seems to be normal for vnc, so I'll go ahead
and validate the update.
Comment 15 Dave Hodgins 2013-09-17 00:03:37 CEST
Validating the update.

Someone from the sysadmin team please push 10181.adv to updates.

Keywords: (none) => validated_update
Whiteboard: feedback => feedback MGA3-64-OK MGA3-32-OK
CC: (none) => sysadmin-bugs

Comment 16 Thomas Backlund 2013-09-19 10:29:25 CEST
Update pushed:

CC: (none) => tmb
Resolution: (none) => FIXED

Note You need to log in before you can comment on or make changes to this bug.