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): 1.1.0-3.mga2 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. Reproducible: Steps to Reproduce:
Keywords: (none) => Junior_jobVersion: 3 => CauldronSource RPM: tigervnc-server1.1.0-3.mga2 => tigervnc-server-1.1.0-3.mga2
Version: Cauldron => 3
Hi, I'll try to reproduce and fix this bug. Be patient, I'm just an apprentice Regards.
Status: NEW => ASSIGNEDCC: (none) => bersuit.vera, juan.baptisteAssignee: bugsquad => bersuit.vera
Eureka! 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 ?
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.
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
CC: (none) => stormi
Ping Alfonso Vera, users are waiting for a fix in mga2 and mga3 :)
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 ... http://pkgsubmit.mageia.org/uploads/failure/3/core/updates_testing/20130825234428.juancho.valstar.14139/log/tigervnc-1.1.0-3.1.mga3/build.0.20130825234504.log I don't have the solution as yet :-( Can you help me ? Salut
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.
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 References: ======================== https://bugs.mageia.org/show_bug.cgi?id=10181 Updated packages in core/updates_testing: ======================== tigervnc-1.1.0-3.1.mga3.x86_64 tigervnc-server-1.1.0-3.1.mga3.x86_64 tigervnc-server-module-1.1.0-3.1.mga3.x86_64 tigervnc-java-1.1.0-3.1.mga3.x86_64 Source RPMs: tigervnc-1.1.0-3.1.mga3.src.rpm
Assignee: bersuit.vera => qa-bugs
Thanks Alfonso
Alfonso, we also need an update for Mageia 2, to fix bug #5045. Thanks!
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 #!/bin/bash killall x0vncserver x0vncserver display=:0 -SecurityTypes=None & sleep 4 vncviewer -compresslevel 9 localhost:0 killall x0vncserver
CC: (none) => davidwhodgins
Advisory 10181.adv committed to svn.
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
Blocks: (none) => 5045
As Alfonso pointed out to me, http://superuser.com/questions/322803/how-to-connect-to-virtualbox-remote-desktop-client-using-vnc 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.
Validating the update. Someone from the sysadmin team please push 10181.adv to updates.
Keywords: (none) => validated_updateWhiteboard: feedback => feedback MGA3-64-OK MGA3-32-OKCC: (none) => sysadmin-bugs
Update pushed: http://advisories.mageia.org/MGAA-2013-0104.html
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED