Bug 376506 - Problem at least when synchronizing zip files
Summary: Problem at least when synchronizing zip files
Status: CONFIRMED
Alias: None
Product: krusader
Classification: Applications
Component: synchronize (show other bugs)
Version: Git
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Krusader Bugs Distribution List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-15 07:54 UTC by Toni Asensi Esteve
Modified: 2018-05-06 00:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Simple case (59.72 KB, image/png)
2017-02-15 07:55 UTC, Toni Asensi Esteve
Details
After the start button was pressed (26.28 KB, image/png)
2017-02-15 07:58 UTC, Toni Asensi Esteve
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Toni Asensi Esteve 2017-02-15 07:54:41 UTC
Using at least Kubuntu 16.10: it seems that there's a bug in Krusader at least  when synchronizing zip files. I'll attach some screenshots.
Comment 1 Toni Asensi Esteve 2017-02-15 07:55:23 UTC
Created attachment 104040 [details]
Simple case

For example, in this simple case:
Comment 2 Toni Asensi Esteve 2017-02-15 07:58:23 UTC
Created attachment 104041 [details]
After the start button was pressed

If the "Synchronize" button is pressed and then the "Start" button is pressed, then Krusader does not respond. 

if Krusader is closed and it's executed:
    ps aux | grep -i [k]rusader
then it is seen something like this even when Krusader was closed:
    user     13698  0.6  5.1 718532 82304 ?        Sl   08:13   0:06 /usr/bin/krusader
    user     13733  0.0  1.0 290172 15996 ?        S    08:25   0:00 kio_krarc.so [kdeinit5] krarc local:/run/user/1000/klauncherTJ1377.1.slave-socket local:/run/user/1000/krusadern13698.4.slave-socket
and then a command like
    killall krusader
must be executed to regretfully do that to our dear Krusader :-)

Thanks for Krusader!
Comment 3 Alex Bikadorov 2017-05-18 13:58:25 UTC
Syncing archive content seems not to be supported at all right now.
Solutions:
1. Check if user wants to do it and abort with error message
2. Make it working

(2) is more complicated, of course. But maybe it will be be a fortunate side effect after I simplify the code base...