Jets3t-cockpit used to work. I have not had need to use it since upgrading from Mageia 4 to Mageia 5 but wanted to try something with it today. I get: Exception in thread "main" java.lang.ExceptionInInitializerError Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:804) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:541) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:292) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:269) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:657) at org.jets3t.apps.cockpit.Cockpit.<clinit>(Cockpit.java:170) I have tried uninstalling and reinstalling the Jets3t packages just in case something went wrong due to upgrade but this has made no difference.
Assignee: bugsquad => mageiaSource RPM: (none) => jets3t-0.9.0-5.mga5.src.rpmCC: (none) => geiger.david68210
It appears we have version 0.9.0 in the rpm. The latest version is 0.9.4 and one of the items in the release notes is "Updated required libraries to latest versions: ... Log4J 1.2.17". Could it be that the Log4J library we now have in Mageia is too new for 0.9.0?
I can confirm that downloading version 0.9.4 from the Jets3t site and running cockpit.sh works.
Assignee: mageia => kde
Assignee: kde => bugsquadCC: (none) => mageia
(In reply to Mark Dawson Butterworth from comment #2) > I can confirm that downloading version 0.9.4 from the Jets3t site and > running cockpit.sh works. Assigning to the registered maintainer
CC: (none) => marja11Assignee: bugsquad => mageia
On current cauldron it works fine but confirmed here on mga5 it doesn't work anymore. Assigning to QA, Advisory: ============================= Many users have reported that jets3t (jets3t-cockpit) doesn't start anymore due to a classpath issue: "Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable." This update fixes this issue disabling by default classpath "org.apache.commons.logging.impl.Log4JLogger" in "commons-logging.properties" file. Packages in 5/core/updates_testing: ======================== jets3t-0.9.0-5.1.mga5.noarch jets3t-app-0.9.0-5.1.mga5.noarch jets3t-javadoc-0.9.0-5.1.mga5.noarch Source RPM: ======================== jets3t-0.9.0-5.1.mga5.src.rpm How to test this update request: ======================== - Just ensure that jets3t-cockpit now starts and runs properly.
Assignee: mageia => qa-bugs
Whiteboard: (none) => has_procedure
MGA5-32 on AcerD620 Xfce No installation issues jets3t-cockpit starts and shows login window for Amazon and Google Storage, so OK
CC: (none) => herman.viaeneWhiteboard: has_procedure => has_procedure MGA5-32-OK
Whiteboard: has_procedure MGA5-32-OK => has_procedure MGA5-32-OK advisoryCC: (none) => lewyssmith
Testing M5_64, OK BEFORE update: jets3t-0.9.0-5.mga5 jets3t-app-0.9.0-5.mga5 $ jets3t-cockpit Exception in thread "main" java.lang.ExceptionInInitializerError Caused by: org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. [etc as shown in Comment 0] AFTER update: jets3t-0.9.0-5.1.mga5 jets3t-app-0.9.0-5.1.mga5 $ jets3t-cockpit correctly starts the application, popping up sensible windows & dialogues. OK. Validating; advisory already in place.
Whiteboard: has_procedure MGA5-32-OK advisory => has_procedure MGA5-32-OK advisory MGA5-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2017-0002.html
Status: NEW => RESOLVEDResolution: (none) => FIXED