Bug 31071 - qt-fsarchiver does not work properly, there is an issue with versions of qt-fsarchiver and qt-fsarchiver-terminal
Summary: qt-fsarchiver does not work properly, there is an issue with versions of qt-f...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-11-03 14:42 CET by Herman Viaene
Modified: 2022-11-09 21:26 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Herman Viaene 2022-11-03 14:42:16 CET
Description of problem:
According to the github pages qt-fsarchiver and qt-fsarchiver-terminal have to be installed.
In the current M9 alpha round 2 the version of qt-fsarchive is 0.8.5.21. When launched it complains that it needs at least version 0.8.5.10 of qt-fsarchiver-terminal, but this M9 has qt-fsarchiver-terminal 0.8.6.7. qt-fsarchive goes on, but the result is that the possible partitions are not listed.

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


How reproducible:
each time

Steps to Reproduce:
1.
2.
3.
Comment 1 sturmvogel 2022-11-03 14:46:40 CET
Duplicate of bug 28791?
Comment 2 Herman Viaene 2022-11-03 15:08:18 CET
I've read this time more thoroughly that bug, and yes, I could agree it is a dup. But in Comment 16 you state:
"After removing them (and roughly fiddling with the spec file), qt-fsarchiver-0.8.6.7-1.mga8 builds and the partitions show up properly in the main window."

So why do we have now that older not working version in M9 ???????
Comment 3 sturmvogel 2022-11-03 15:24:30 CET
DavidG (maintainer) did never update the package in Mga8 or cauldron as this package is a PITA to build, see https://bugs.mageia.org/show_bug.cgi?id=28791#c3

I only fiddled around at this time to find out if it is possible to get this fine piece of software to work...it was possible, but not in a way that it could be provided as a package update. So the package maintainer should decide what to do with this piece of software...
Comment 4 sturmvogel 2022-11-03 18:08:24 CET
Aaah i found something. 
According https://svnweb.mageia.org/packages/cauldron/qt-fsarchiver/current/SPECS/qt-fsarchiver.spec?revision=1850442&view=markup
 there is a spec file for qt-fsarchiver-0.8.6.7-3 but it was never build or pushed to the mirrors. This change was done 6 months ago..

As papoteur did the last change..cc'ing him..

CC: (none) => yves.brungard_mageia

Comment 5 papoteur 2022-11-03 18:29:51 CET
It was when I was apprentice.
Thus I have now submitted to the build system.
If feedback is OK, then I will apply also the changes to Mageia 8.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28791

Comment 6 papoteur 2022-11-03 19:00:12 CET
qt-fsarchiver-0.8.6.7-3.mga9.x86_64.rpm is now built.
Comment 7 Lewis Smith 2022-11-03 21:12:17 CET
Thank you all for working on this. I remember the original bug about it wanting the terminal installed. I thought it had been fixed...

(In reply to papoteur from comment #5)
> Thus I have now submitted to the build system.
> If feedback is OK, then I will apply also the changes to Mageia 8.
Very encouraging. If you do end up doing the M8 fix, please note that on Bug 28791.

CC: (none) => lewyssmith

Comment 8 sturmvogel 2022-11-03 21:20:22 CET
I did a short test under a 64bit Plasma cauldron with qt-fsarchiver-0.8.6.7-3.mga9 and qt-fsarchiver-terminal-0.8.6.7-1.mga9.

The initial problems (mentioned in bug 28791) don't occur. The program starts and partitions are shown. More torough test should be done by Herman and other users who use this software regularly.

BUT: It is not possible to start qt-fsarchiver from the the application menu. It fails because of a wrong link. The application menu entry points to /usr/bin/qt-fsarchiver but the real installation is under /usr/bin/qt-fsarchiver
In the last revision of the spec file, the /usr/bin/ path was removed. This change should be reverted...
Comment 9 sturmvogel 2022-11-03 21:21:50 CET
(In reply to sturmvogel from comment #8)
> The application menu entry points to
> /usr/bin/qt-fsarchiver but the real installation is under
> /usr/bin/qt-fsarchiver
> In the last revision of the spec file, the /usr/bin/ path was removed. This
> change should be reverted...

Sorry for typo:
the real installation is under /usr/sbin/qt-fsarchiver
Comment 10 papoteur 2022-11-04 21:36:10 CET
A new build is done.
qt-fsarchiver-0.8.6.7-4.mga9
Comment 11 Lewis Smith 2022-11-06 21:06:18 CET
Installing qt-fsarchiver pulled in also fsarchiver, and qt-fsarchiver-terminal whose earlier absence (if not installed) caused it not to work. So that is fixed.

fsarchiver-0.8.6-2.mga9
qt-fsarchiver-terminal-0.8.6.7-1.mga9
qt-fsarchiver-0.8.6.7-4.mga9

Could not find it in LXDE menus anywhere, so launched it from terminal (qt-fsarchiver). It popped a sudo password box, then a note about where to read ints intructions for use, then the UI. No console errors at all.
The UI showed all partitions on the disc (except swap), which was the original complaint.

For me, this is fixed, with many thanks to all who in the past worked on it, and papoteur for this coup de grace.
Will others on this bug please try it also.
I am for closing *this* Cauldron bug Fixed.

@papoteur
 bug 28791?
Will you do M8 also? If so, please note on *that* bug. Otherwise we can close it WontFix (saying it is due with M9).
Comment 12 Lewis Smith 2022-11-06 21:13:17 CET
(In reply to Lewis Smith from comment #11)
> The UI showed all partitions on the disc (except swap), which was the
> original complaint.
I meant the original complaint was that it did *not* list the disc partitions, but does now; so that also is fixed.
Comment 13 Herman Viaene 2022-11-07 10:16:12 CET
Where can I download the new versions?
Comment 14 sturmvogel 2022-11-07 15:16:08 CET
(In reply to Herman Viaene from comment #13)
> Where can I download the new versions?
It is on the cauldron mirrors already...
Comment 15 sturmvogel 2022-11-07 15:40:08 CET
fsarchiver-0.8.6-2.mga9
qt-fsarchiver-terminal-0.8.6.7-1.mga9
qt-fsarchiver-0.8.6.7-4.mga9

64 bit Plasma Netinstall Vbox machine:

Installs fine
opens fine (from application menu and terminal)
partitions are shown



One problem (don't know if it is related to my Virtualbox install):
I can close the program just fine via the "x" in the upper right corner of the application window. But if i try to close the application via the "Exit" button in the menu bar or in the application...it completely hangs itself and gets unresponsive. Won't close...
Comment 16 Lewis Smith 2022-11-08 10:01:20 CET
qt-fsarchiver-0.8.6.7-4.mga9

Well, here on real hardware, using LxQt, I can close it no problems using:
- the window title bar menu 'X Close'
- the window title bar top-right 'X'
- the application 'Exit' menu
- the application window 'Exit' button
- Alt/F4

Oh, this time the first time I launched the application (terminal), I got:

"mkdir: cannot create directory ‘/media/sda3’: File exists"

but not subsequently. Previously, comment 11, I reported "No console errors at all". This is not something to worry about, because the application launches OK. Lots of applications put out disconcerting console messages.

> close the application via the "Exit" button in the menu bar
> or in the application...it completely hangs
This looks a VirtualBox problem. What desktop were you using? I can try that.

@Herman : your response please.
Comment 17 Herman Viaene 2022-11-08 13:25:56 CET
I only have access to QA-updates, I don't do cauldron.
Comment 18 papoteur 2022-11-08 14:06:18 CET
Hi Herman,
For Mageia 8, this is here:
bug 28791
Comment 19 Lewis Smith 2022-11-09 21:10:42 CET
That bug has some very -ve comments, which preumably apply here too.
In the light of which, I tried (Cauldron):
 $ sudo qt-fsarchiver
 [sudo] password for lewis:
after which it popped its own password dialogue, then nothing happened, the terminal went unresponsive: Ctrl/C had no effect. I could find nothing 'fsarchiver' with ps to kill, but I was able to close the terminal window.
Comment 20 Lewis Smith 2022-11-09 21:26:42 CET
If this package really gets killed off (see bug 28791), then this bug and that one should be closed 'invalid' or 'wontfix'.

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