Bug 25156 - vuze (azureus) don't start because of a wrong Eclipse SWT config path in startup script
Summary: vuze (azureus) don't start because of a wrong Eclipse SWT config path in star...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA7-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2019-07-20 10:46 CEST by David GEIGER
Modified: 2019-08-10 02:13 CEST (History)
4 users (show)

See Also:
Source RPM: vuze-5.7.6.0-2.mga7.src.rpm
CVE:
Status comment:


Attachments

Description David GEIGER 2019-07-20 10:46:20 CEST
Testing vuze (azureus) on mageia 7 but it fails to start due a wrong Eclipse SWT config path in the startup script on a 64bit system.

SWT was moved to /usr/lib on all platforms and no more in /usr/lib64
Comment 1 David GEIGER 2019-07-20 12:50:23 CEST
Assigning to QA now,


Advisory:
========================

Our current vuze (azureus) package fails to start due a wrong Eclipse SWT config path in the startup script on a 64bit system.
So this update fixes this issue.

========================

Packages in 7/core/updates_testing:
========================
vuze-5.7.6.0-2.1.mga7.noarch.rpm

Source RPM: 
========================
vuze-5.7.6.0-2.1.mga7.src.rpm

Assignee: bugsquad => qa-bugs

Comment 2 Herman Viaene 2019-07-26 10:56:18 CEST
MGA7-64 Plasma on Lenovo B50
No installaion issues.
Starting from CLI provokes a lot of comment/warnings, but a sensible window starts "Starting your first torrent". That's as far as I'll go.
$ azureus 
Starting Azureus...

(java:13969): dbind-WARNING **: 10:49:59.985: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(WebKitWebProcess:14002): dbind-WARNING **: 10:50:00.369: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Usable browser found
Loading Azureus:
/usr/lib/jvm/jre/bin/java  -cp "/usr/lib/java/swt.jar:/usr/share/java/json_simple.jar:/usr/share/java/bcprov.jar:/usr/share/java/apache-commons-cli.jar:/usr/share/java/apache-commons-lang.jar:/usr/share/java/log4j-1.jar:/usr/share/java/azureus/Azureus2.jar:./*.jar" -Djava.library.path="/home/tester7/.azureus/app" -Dazureus.install.path="/home/tester7/.azureus/app" -Dazureus.script="/usr/bin/azureus" -Dazureus.script.version=6 -Dorg.eclipse.swt.browser.UseWebKitGTK=true -Dazureus.skipSWTcheck=1 org.gudy.azureus2.ui.swt.Main 
file:/usr/lib/java/swt.jar ; file:/usr/share/java/json_simple.jar ; file:/usr/share/java/bcprov.jar ; file:/usr/share/java/commons-cli.jar ; file:/usr/share/java/apache-commons-lang.jar ; file:/usr/share/java/log4j-1.2.17.jar ; file:/usr/share/java/azureus/Azureus2.jar ; file:/home/tester7/.azureus/app/*.jar ; file:/home/tester7/.azureus/app/
changeLocale: *Default Language* != Dutch (Belgium). Searching without country..
changeLocale: Searching for language Dutch in *any* country..
changeLocale: no message properties for Locale 'Dutch (Belgium)' (nl_BE), using 'Dutch (Netherlands)'
DEBUG::Fri Jul 26 10:50:02 CEST 2019  Successfully migrated key management

(java:14030): dbind-WARNING **: 10:50:02.491: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
UIFunctions/ImageLoad took 0ms
new shell took 200ms
new shell setup took 51ms
skin init took 150ms
MainMenu init took 50ms
pre skin widgets init took 25ms
skin widgets (1/2) init took 240ms
skin widgets (2/2) init took 75ms
pre SWTInstance init took 0ms
Init Core Columns took 75ms
SWTInstance init took 0ms
shell.layout took 76ms
---------SHOWN AT 1564131003705;2922ms
---------DONE DISPATCH AT 1564131004088;3305ms
---------READY AT 1564131004088;3305ms
shell.open took 383ms
processStartupDMS took 0ms

CC: (none) => herman.viaene
Whiteboard: (none) => MGA7-64-OK

Comment 3 Thomas Andrews 2019-08-09 13:22:53 CEST
Looks good to me. Validating. Advisory in Comment 1.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Thomas Backlund 2019-08-09 22:47:46 CEST

Keywords: (none) => advisory
CC: (none) => tmb

Comment 4 Mageia Robot 2019-08-10 02:13:54 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2019-0082.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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