Bug 21430 - DoubleCmd-qt fails to start after latest update
Summary: DoubleCmd-qt fails to start after latest update
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard: MGA6TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-01 07:25 CEST by aguador
Modified: 2019-02-24 11:51 CET (History)
1 user (show)

See Also:
Source RPM: doublecmd-0.6.6-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description aguador 2017-08-01 07:25:01 CEST
Sorry for the brief report, but I am late leaving. After the latest Cauldron update, doublecmd-qt fails to start. It simply hangs:

$ doublecmd-qt
Starting GuiMessageQueue
Starting Double Commander

There was not problem before updating on 31/07.
Marja Van Waes 2017-08-01 16:35:43 CEST

Source RPM: (none) => doublecmd
Assignee: bugsquad => rverschelde
CC: (none) => marja11

Comment 1 Rémi Verschelde 2017-08-01 22:16:37 CEST
fpc and lazarus were updated, not sure what impact they would have on doublecmd, but the good news is that I can now package the last doublecmd version which should hopefully fix this issue at the same time. In Mageia 6 I was stuck because lazarus was too old, and updating it meant updating fpc, which is beyond my strength :)
Rémi Verschelde 2017-08-01 22:18:24 CEST

Status: NEW => ASSIGNED

Comment 2 aguador 2017-10-14 17:36:09 CEST
Rémi, I doubt it has nothing to do with fpc or lazarus. Doublecmd-qt has now stopped working on my Mageia 6 machine where those programs have not been updated.

What I have just done is replace Doublecmd-qt with the gtk version and, voilá, it works, on both machines. (The qt version, as I recall, has simply performed better in the past.)

I do not know why DoubleCmd-Qt stopped working as I recall using it on Monday (9th and Wednesday (11th) and do not recall updating anything since then except *perhaps* the cups previously reverted in mga6. My memory may be faulty on this but offer it as a possible clue that a package recently updated in 6 may be the cuprit.
Rémi Verschelde 2017-10-25 12:17:52 CEST

Whiteboard: (none) => MGA6TOO

Comment 3 aguador 2018-03-11 18:10:49 CET
Rémi, Perhaps a newer version will work in Qt? Mageia's current 0.6.6 dates from 10-2015. I know that updating this package was held up by the need for fpc and lazarus updates that are now complete.

The 0.7 series added gvfs support (which I can get to work only sporadically in the present package) and some other goodies. Development has also picked up pace after an idle spell with releases 0.8 and 0.9 being released within less than a month of each other.

This is such a great FM that it would be nice to have it updated. I looked at the spec file, but confess that it is beyond anything I would attempt modifying even to build only for myself. :-(

Source RPM: doublecmd => doublecmd-0.6.6-1.mga6.src.rpm

Comment 4 aguador 2018-10-17 14:06:09 CEST
Pascal's fix of the libdir on aarch64 (and update to 0.8.4, thank you!) has fixed the problem in Cauldron. In addition to solving the bug, I have now had a chance to test some functions, including the improved connectivity for mtp/Android, and everything is working as it should.

This leaves two questions:
1) Shouldn't this be updated in -- or at least be backported to -- mga6 to fix the problem there?

2) Apart from the bug, the current version of Doublecmd now has a qt5 version as well as the Qt4. Given that Mageia has Qt5, should the "qt" version be dropped in favour of the "qt5" version? (https://sourceforge.net/p/doublecmd/wiki/Download/)
Comment 5 aguador 2019-02-24 11:51:27 CET
As noted, this bug was resolved by the update.

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


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