Polo File Manager

Message
Author
User avatar
Fornhamfred
Posts: 255
Joined: Sun May 02, 2010 12:49 pm

Re: Polo File Manager

#31 Post by Fornhamfred »

Richard wrote: Wed Nov 28, 2018 7:32 am Looks as if you installed a new liboffice6.1 and liboffice6.0 got removed?
Libreoffice 6.0.1.1 is installed, why would this output be generated?

User avatar
Richard
Posts: 1577
Joined: Fri Dec 12, 2008 10:31 am

Re: Polo File Manager

#32 Post by Richard »

I've seen that message when using a launcher that I created using, for example, libreoffice6.0;
then after installing libreoffice6.1, I had to change all the launchers that I had created from *6.0 to *.6.1

That may not be your problem, since you say that libreoffice6.0 is actually installed.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.

User avatar
Fornhamfred
Posts: 255
Joined: Sun May 02, 2010 12:49 pm

Re: Polo File Manager

#33 Post by Fornhamfred »

No liboffice6.1 is not and has not ever been installed.

User avatar
asqwerth
Developer
Posts: 7231
Joined: Sun May 27, 2007 5:37 am

Re: Polo File Manager

#34 Post by asqwerth »

"Completely removed" polo using Synaptic (though this did not remove all the dependencies that were installed the first time round). Installed again from Test Repo using MXPI. This time, also installed the dbgsym package.

No change, still doesn't open when I click on it in whisker menu.

With terminal, still get the segmentation fault problem.

Code: Select all

$ polo-gtk
[02:47:10.070] Architecture: 64-bit
[02:47:10.070] Host Name: mx17final
[02:47:10.070] CPU Cores: 4
[02:47:10.070] RAM: 15912 MB
[02:47:10.078] [Warning] Deleted invalid lock
[02:47:10.322] Trash: Calculating trashed folder size: /home/tuaz/.local/share/Trash/files/Newaita-dark
Segmentation fault
Tried installing polo in my other MX17 partition that has the mx18-dev and the Stevo OBS repos enabled .

Doesn't help. Still not working.

I'm not bothering anymore, since I don't even use Polo.
Desktop: Intel i5-4460, 16GB RAM, Intel integrated graphics
Clevo N130WU-based Ultrabook: Intel i7-8550U (Kaby Lake R), 16GB RAM, Intel integrated graphics (UEFI)
ASUS X42D laptop: AMD Phenom II, 6GB RAM, Mobility Radeon HD 5400

User avatar
Fornhamfred
Posts: 255
Joined: Sun May 02, 2010 12:49 pm

Re: Polo File Manager

#35 Post by Fornhamfred »

asqwerth wrote: Thu Nov 29, 2018 2:55 pm "Completely removed" polo using Synaptic (though this did not remove all the dependencies that were installed the first time round). Installed again from Test Repo using MXPI. This time, also installed the dbgsym package.

No change, still doesn't open when I click on it in whisker menu.

With terminal, still get the segmentation fault problem.

Code: Select all

$ polo-gtk
[02:47:10.070] Architecture: 64-bit
[02:47:10.070] Host Name: mx17final
[02:47:10.070] CPU Cores: 4
[02:47:10.070] RAM: 15912 MB
[02:47:10.078] [Warning] Deleted invalid lock
[02:47:10.322] Trash: Calculating trashed folder size: /home/tuaz/.local/share/Trash/files/Newaita-dark
Segmentation fault
Tried installing polo in my other MX17 partition that has the mx18-dev and the Stevo OBS repos enabled .

Doesn't help. Still not working.

I'm not bothering anymore, since I don't even use Polo.
Tried this and still get the same output as previous post.
Installing with mxpi gave this output:

Code: Select all

Get:1 http://security.debian.org stretch/updates InRelease [94.3 kB]
Hit:2 http://download.virtualbox.org/virtualbox/debian stretch InRelease
Get:3 http://ftp.uk.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:4 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch InRelease [27.4 kB]
Ign:5 http://ftp.uk.debian.org/debian stretch InRelease
Hit:6 http://ftp.uk.debian.org/debian stretch Release
Get:7 http://mirrors.dotsrc.org/mx-packages/mx/repo stretch InRelease [8,136 B]
Get:8 http://mirrors.dotsrc.org/mx-packages/mx/testrepo stretch InRelease [4,967 B]
Get:9 https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease [1,480 B]
Get:11 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main amd64 Packages [168 kB]
Err:11 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main amd64 Packages
  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:168470 [weak]
   - SHA256:f017113a33c1004788e913f35bf42c5e9556099ccdcf2d058515028a9b17ccae
   - SHA1:bba34336e3d85f8bd7e0cb3f4eb26ecdde965fc6 [weak]
   - MD5Sum:143076532cef814e56ee2d211ccdf578 [weak]
  Hashes of received file:
   - SHA256:e714795dbb96d72cd1ad4ff89707643c3be1e40f95e22d2bb7aa224b9c09f150
   - SHA1:a8ebb567da879705ecf329f81f3227023b48dba7 [weak]
   - MD5Sum:00efb632c4aa33f94629036ab79e23be [weak]
   - Filesize:168361 [weak]
  Last modification reported: Thu, 29 Nov 2018 13:08:01 +0000
  Release file created at: Thu, 29 Nov 2018 13:08:50 +0000
Get:12 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main i386 Packages [173 kB]
Err:12 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main i386 Packages
  
Get:13 http://mirrors.dotsrc.org/mx-packages/mx/repo stretch/main amd64 Packages [368 kB]
Get:14 http://mirrors.dotsrc.org/mx-packages/mx/repo stretch/main i386 Packages [369 kB]
Get:15 http://mirrors.dotsrc.org/mx-packages/mx/testrepo stretch/test i386 Packages [783 kB]
Get:16 http://mirrors.dotsrc.org/mx-packages/mx/testrepo stretch/test amd64 Packages [794 kB]
Fetched 2,882 kB in 2s (1,181 kB/s)
Reading package lists...
E: Failed to fetch http://mirrors.dotsrc.org/mx-packages/antix/stretch/dists/stretch/main/binary-amd64/Packages.gz  Hash Sum mismatch
   Hashes of expected file:
    - Filesize:168470 [weak]
    - SHA256:f017113a33c1004788e913f35bf42c5e9556099ccdcf2d058515028a9b17ccae
    - SHA1:bba34336e3d85f8bd7e0cb3f4eb26ecdde965fc6 [weak]
    - MD5Sum:143076532cef814e56ee2d211ccdf578 [weak]
   Hashes of received file:
    - SHA256:e714795dbb96d72cd1ad4ff89707643c3be1e40f95e22d2bb7aa224b9c09f150
    - SHA1:a8ebb567da879705ecf329f81f3227023b48dba7 [weak]
    - MD5Sum:00efb632c4aa33f94629036ab79e23be [weak]
    - Filesize:168361 [weak]
   Last modification reported: Thu, 29 Nov 2018 13:08:01 +0000
   Release file created at: Thu, 29 Nov 2018 13:08:50 +0000
E: Failed to fetch http://mirrors.dotsrc.org/mx-packages/antix/stretch/dists/stretch/main/binary-i386/Packages.gz  
E: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  polo-file-manager
0 upgraded, 1 newly installed, 0 to remove and 180 not upgraded.
Need to get 1,347 kB of archives.
After this operation, 5,859 kB of additional disk space will be used.
Get:1 http://mirrors.dotsrc.org/mx-packages/mx/testrepo stretch/test amd64 polo-file-manager amd64 18.8-0.1~mx17+1 [1,347 kB]
Fetched 1,347 kB in 0s (1,461 kB/s)
Selecting previously unselected package polo-file-manager.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 516914 files and directories currently installed.)
Preparing to unpack .../polo-file-manager_18.8-0.1~mx17+1_amd64.deb ...
Unpacking polo-file-manager (18.8-0.1~mx17+1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up polo-file-manager (18.8-0.1~mx17+1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://download.virtualbox.org/virtualbox/debian stretch InRelease
Hit:3 http://ftp.uk.debian.org/debian stretch-updates InRelease
Ign:4 http://ftp.uk.debian.org/debian stretch InRelease
Hit:5 http://ftp.uk.debian.org/debian stretch Release
Get:6 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch InRelease [27.4 kB]
Hit:7 http://mirrors.dotsrc.org/mx-packages/mx/repo stretch InRelease
Get:8 https://mega.nz/linux/MEGAsync/Debian_9.0 ./ InRelease [1,480 B]
Get:10 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main amd64 Packages [168 kB]
Err:10 http://mirrors.dotsrc.org/mx-packages/antix/stretch stretch/main amd64 Packages
  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:168470 [weak]
   - SHA256:f017113a33c1004788e913f35bf42c5e9556099ccdcf2d058515028a9b17ccae
   - SHA1:bba34336e3d85f8bd7e0cb3f4eb26ecdde965fc6 [weak]
   - MD5Sum:143076532cef814e56ee2d211ccdf578 [weak]
  Hashes of received file:
   - SHA256:e714795dbb96d72cd1ad4ff89707643c3be1e40f95e22d2bb7aa224b9c09f150
   - SHA1:a8ebb567da879705ecf329f81f3227023b48dba7 [weak]
   - MD5Sum:00efb632c4aa33f94629036ab79e23be [weak]
   - Filesize:168361 [weak]
  Last modification reported: Thu, 29 Nov 2018 13:08:01 +0000
  Release file created at: Thu, 29 Nov 2018 13:08:50 +0000
Fetched 170 kB in 1s (165 kB/s)
Reading package lists...
E: Failed to fetch http://mirrors.dotsrc.org/mx-packages/antix/stretch/dists/stretch/main/binary-amd64/Packages.gz  Hash Sum mismatch
   Hashes of expected file:
    - Filesize:168470 [weak]
    - SHA256:f017113a33c1004788e913f35bf42c5e9556099ccdcf2d058515028a9b17ccae
    - SHA1:bba34336e3d85f8bd7e0cb3f4eb26ecdde965fc6 [weak]
    - MD5Sum:143076532cef814e56ee2d211ccdf578 [weak]
   Hashes of received file:
    - SHA256:e714795dbb96d72cd1ad4ff89707643c3be1e40f95e22d2bb7aa224b9c09f150
    - SHA1:a8ebb567da879705ecf329f81f3227023b48dba7 [weak]
    - MD5Sum:00efb632c4aa33f94629036ab79e23be [weak]
    - Filesize:168361 [weak]
   Last modification reported: Thu, 29 Nov 2018 13:08:01 +0000
   Release file created at: Thu, 29 Nov 2018 13:08:50 +0000
E: Failed to fetch http://mirrors.dotsrc.org/mx-packages/antix/stretch/dists/stretch/main/binary-i386/Packages.gz  
E: Some index files failed to download. They have been ignored, or old ones used instead.

nathan2423
Posts: 217
Joined: Tue Dec 22, 2015 8:33 am

Re: Polo File Manager

#36 Post by nathan2423 »

Disappointing but probably not surprising given lack of development - so the search for the better linux file manager will continue elsewhere: from the github page: https://github.com/teejee2008/polo/issues/27

teejee2008 commented 25 days ago

This project is not currently a priority for me. Developing this application is time-consuming and I don't have the time or finances to work for free on something that does not bring any income ( I already have a full-time job ). Making it paid also does not make any sense as very few people will buy it.

If someone wants to fork this project please go ahead. This is a open-source project that anybody can fork and develop. What is the point of open-source if everybody keeps complaining to the same developer to do the work? Open-source does not mean free labour... it means free access to code. An open source project where everyone is waiting for a single developer is pointless. It might as well be closed-source.

As far as archiving this project is concerned, I'm not finished with it. I still use it everyday and it is good enough for my use. I will be releasing another version when I get the time. It may happen tomorrow or it may happen 10 years from now. That is the nature of open-source development.

If somebody has experience with implementing drag-and-drop in GTK please go ahead and implement the changes. You can either fork this project or send me a pull request.
@teejee2008
Owner Author
teejee2008 commented 24 days ago

I have archived this project. I will be releasing this project again under a paid licence at some point in the future (maybe next year if I get the time).

If someone wants to fork this project please go ahead. This is a open-source project that anybody can fork and develop.

For people who are still using this app there is no need to be disappointed. I'm going to take my time finishing this app before I launch it again. When it launches again, it will be a finished product with a regular development cycle. And as a paid app you will have some surety that the project is sustainable.

User avatar
Jerry3904
Administrator
Posts: 21956
Joined: Wed Jul 19, 2006 6:13 am

Re: Polo File Manager

#37 Post by Jerry3904 »

That is too bad. I had high hopes for it.
Production: 5.10, MX-23 Xfce, AMD FX-4130 Quad-Core, GeForce GT 630/PCIe/SSE2, 16 GB, SSD 120 GB, Data 1TB
Personal: Lenovo X1 Carbon with MX-23 Fluxbox and Windows 10
Other: Raspberry Pi 5 with MX-23 Xfce Raspberry Pi Respin

User avatar
markol
Posts: 403
Joined: Sat Jan 30, 2021 9:33 am

Re: Polo File Manager

#38 Post by markol »

A bit of necromancing, sorry for that, but.... I really love PoloFM and it's been my default FM in non-KDE environments since I found about it (probably more than 3 years?). Is there any chance that MX community (well, dev team) would continue/fork its development? Not much to do, I believe. It works fine on several MX21XFCE machines.

Post Reply

Return to “General”