MX Linux Forum

Posted: **Wed Oct 24, 2018 4:36 pm**

Hi everyone! Hope you're all having a nice life!

Do any of you use Polo File Manager? I've been using it for quite some time now and found it to be really an interesting option with some handy features for a FM. The author of this app is no other than the creator of timeshift and aptik. One of the features I like the most is the "embedded terminal" which can be open by pressing F4(yes, I changed xfce4-terminal --drop-down to F3) and the fact that you can run an .iso disc into a VM directly from the app with a right click>boot in a VM. You can read more about it here https://github.com/teejee2008/polo

Here some screenshots I took

Posted: **Wed Oct 24, 2018 5:21 pm**

Did you install it from our test repository?

viewtopic.php?f=134&t=44809

Posted: **Wed Oct 24, 2018 5:53 pm**

Stevo wrote: Wed Oct 24, 2018 5:21 pm Did you install it from our test repository?

viewtopic.php?f=134&t=44809

I should really start to look into that repository. No, I didn't. I Installed it via a .deb file provided by the author here https://github.com/teejee2008/polo/releases

I did run

Code: Select all

$ apt search polo-file-manager

but it found nothing and of course it didn't since it is in the test repository.

Posted: **Tue Nov 13, 2018 11:10 am**

Yes, I use polo file manager. Finding a proper home for polo has partly driven my distro-hopping adventures. Needless to say I was quite pleased to find it in the MX repos.

Part of the charm of polo is the external tools implementation. In other distros, I had to pluck and twerk to find and install them all (I'm looking at you, pdftk). In MX, all the tools were available. (YMMV)

Code: Select all

sudo apt install clamav diffuse fish lzop mediainfo pngcrush pv rclone youtube-dl pdftk groot neofetch gnome-disk-utility

Also, kvm functionality through qemu is installed and tested, but I'm not a virtual guy, so my approach to this is a little sloppy.

I also installed the donation plugins offered by Tony George to contributors of $10 or more. Well worth it to me. He provides an install script for the donation plugins and sends updates to his contributor list.

I use it alongside Thunar, depending on the job. The best of both worlds and all.

Posted: **Tue Nov 13, 2018 11:21 am**

tomcashen wrote: Tue Nov 13, 2018 11:10 am Yes, I use polo file manager. Finding a proper home for polo has partly driven my distro-hopping adventures. Needless to say I was quite pleased to find it in the MX repos....

If you're satisfied the package in Test Repo works fine or if you find bugs, please report in this thread: viewtopic.php?f=134&t=44809&start=20

The packaging team can then decide if it's ready to be moved to the Stable Repos.

And welcome to the forum.

Posted: **Sun Nov 25, 2018 10:27 am**

I use it alongside Thunar, depending on the job. The best of both worlds and all.

So do I. I use PFM mostly when creating and/or moving files/directories since it has a embedded terminal so I find it easier to use it instead of thunar or "cding" from the terminal from one dir to another.

If you're satisfied the package in Test Repo works fine or if you find bugs, please report in this thread: viewtopic.php?f=134&t=44809&start=20

The packaging team can then decide if it's ready to be moved to the Stable Repos.

Well, I think you should move it to the stable repo so everyone can benefit from it. I've been using PFM for quite some time now, long before I started using MX and it's given me no troubles whatsoever. I find it really stable and useful.

Posted: **Sun Nov 25, 2018 10:30 am**

Still not working for me.

Posted: **Sun Nov 25, 2018 11:00 am**

asqwerth wrote: Sun Nov 25, 2018 10:30 am Still not working for me.

What isn't working for you? PFM?

Posted: **Sun Nov 25, 2018 11:19 am**

My bug report is here: viewtopic.php?p=466664#p466664

Posted: **Sun Nov 25, 2018 1:15 pm**

asqwerth wrote: Sun Nov 25, 2018 11:19 am My bug report is here: viewtopic.php?p=466664#p466664

So you can't install PFM from the test respo? Well, like I said before I've been using it for quite a while, since version 17 came out last year and I've always installed it using the .deb or .run file provided by the author here https://github.com/teejee2008/polo/releases I haven't had any mayor issues with it so far. The only thing I can complain about is that there is no translation into my own language - Spanish - and some minor features like shortcuts and stuff like that; i.e return key doesn't take me back to the previous dir, I can do it wit Alt+arrow keys though. Currently, I have nautilus and PFM alongside thunar and switch between one and the other for different things; Nautilus when working with several tabs, cause I can switch from one to another using my keyboard while in thunar I can't; Ctrl+pgdown/pgup doesn't work for this, PFM when I need to move different files/dirs to different locations and a terminal approach is quicker rather than a mouse click one, and thunar for regular stuff cause is the quickest of the three and I can navigate the system using my keboard without even needing to reach the mouse. Maybe you should try installing it the same way I did. I mean, if you haven't already done so.

Posted: **Sun Nov 25, 2018 2:51 pm**

I use Polo FM, Timeshift and Aptik too and they work fine. My polo version is 18.3.1 Beta and ,if I well remember, installed it by a link posted here (by Stevo????).
Is it possible to download the PoloFM- packages from the test-repo so that I can install it in a "working machine" to test it???
thanks

Posted: **Sun Nov 25, 2018 3:03 pm**

The test repo 18.8 debs are here: http://mxrepo.com/mx/testrepo/pool/test/p/polo/

Ignore the dbgsym (debug symbols) packages.

However, the problem wasn't that it could not install from the test repo using MX package Installer, it was that it would crash for that one user when starting up.

Posted: **Sun Nov 25, 2018 11:02 pm**

Moltke wrote: Sun Nov 25, 2018 1:15 pm
asqwerth wrote: Sun Nov 25, 2018 11:19 am My bug report is here: viewtopic.php?p=466664#p466664
So you can't install PFM from the test respo? Well, like I said before I've been using it for quite a while, since version 17 came out last year and I've always installed it using the .deb or .run file provided by the author here https://github.com/teejee2008/polo/releases I haven't had any mayor issues with it so far... Maybe you should try installing it the same way I did. I mean, if you haven't already done so.

My responses were because you said:

I think you should move it to the stable repo so everyone can benefit from it.

in an earlier post.

I'm saying "no, don't move it from Test Repo yet as the package IN THERE (ie, not from Teejee's own site) doesn't work for me. Here's my bug report."

I'm therefore using the Test Repo the way it was meant - Testing and Giving Feedback. (yes, I'm referring to a now-locked thread that kind of blew up overnight while I was sleeping

)

I don't actually need or use it. I'm happy with Sunflower and Double Commander.

Posted: **Sun Nov 25, 2018 11:05 pm**

Stevo wrote: Sun Nov 25, 2018 3:03 pm The test repo 18.8 debs are here: http://mxrepo.com/mx/testrepo/pool/test/p/polo/

Ignore the dbgsym (debug symbols) packages.

However, the problem wasn't that it could not install from the test repo using MX package Installer, it was that it would crash for that one user when starting up.

Stevo, is there more info you need to work out why it doesn't work for me? As far as I know my repos are kept very clean and standard but I can check again tonight.

Posted: **Mon Nov 26, 2018 4:20 pm**

At some point, we also have to consider that if a program works for almost all users out of the box, we should move it to main and then keep trying to solve the issues for those that aren't that fortunate.

Posted: **Mon Nov 26, 2018 4:26 pm**

I tried to install this x64 on an up to date MX-17.1, and got this error msg.

Posted: **Mon Nov 26, 2018 4:36 pm**

Does not install for me neither. Missing dependency.

Posted: **Mon Nov 26, 2018 5:03 pm**

I installed it following the link, and the suggestion, posted by Stevo http://mxrepo.com/mx/testrepo/pool/test ... _amd64.deb.
I also installed dependencies requested: P7zip-rar, libimage-exiftool-perl.
It works

Posted: **Mon Nov 26, 2018 5:58 pm**

The dbgsym (debugging symbols) packages also need the main program package, so they can debug it. If you're installing them one at a time with gdebi, do the main package first.

I install lots of debs with one fell swoop with the apt install extension we have for Dolphin to avoid these kinds of problems: maybe d_o could add the Thunar version he fixed for me for MX 18? It's in a thread that must be a year old by now...

But, again, the problem never was about installing Polo from the test repo with MXPI, only about it crashing for one user when they try and run it after it installs.

Posted: **Mon Nov 26, 2018 8:14 pm**

Just installed from a live booted 17.1 November polo-file-manager.
To see what's up have done this from command line after full updated.
This as a simulation ( using my testrep-helper-script):

Code: Select all

$ ./apt-gettestrepo --simulate install polo-file-manager 

## /etc/apt/sources.list.d/mx.list
## mx-testrepo
deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/testrepo/ stretch test
sudo apt-get -o Dir::Etc::sourcelist=/tmp/mx-testrepo-apt-sources.list.d-temp.demo.10489.1242019149/temp_source.list --simulate install polo-file-manager
Reading package lists... Done
Building dependency tree        
Reading state information... Done
The following additional packages will be installed:
  fish fish-common ipxe-qemu libaio1 libbrlapi0.6 libcacard0 libfdt1 libimage-exiftool-perl libjs-jquery libmediainfo0v5 libpcre2-32-0 libspice-server1 libtinyxml2-4
  libusbredirparser1 libvdeplug2 libxen-4.8 libxenstore3.0 libzen0v5 mediainfo p7zip-rar qemu-kvm qemu-system-common qemu-system-x86 qemu-utils seabios
Suggested packages:
  doc-base mediainfo-gui vde2 qemu-block-extra sgabios ovmf debootstrap
Recommended packages:
  libarchive-zip-perl libposix-strptime-perl libunicode-linebreak-perl javascript-common
The following NEW packages will be installed:
  fish fish-common ipxe-qemu libaio1 libbrlapi0.6 libcacard0 libfdt1 libimage-exiftool-perl libjs-jquery libmediainfo0v5 libpcre2-32-0 libspice-server1 libtinyxml2-4
  libusbredirparser1 libvdeplug2 libxen-4.8 libxenstore3.0 libzen0v5 mediainfo p7zip-rar polo-file-manager qemu-kvm qemu-system-common qemu-system-x86 qemu-utils seabios
0 upgraded, 26 newly installed, 0 to remove and 122 not upgraded.
Inst libjs-jquery (3.1.1-2 Debian:9.6/stable [all])
Inst fish-common (2.7.1-3~mx17+1 MX repository:17.0/mx [all])
Inst libpcre2-32-0 (10.22-3 Debian:9.6/stable [amd64])
Inst fish (2.7.1-3~mx17+1 MX repository:17.0/mx [amd64])
Inst qemu-system-common (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Inst ipxe-qemu (1.0.0+git-20161027.b991c67-1 Debian:9.6/stable [all])
Inst libaio1 (0.3.110-3 Debian:9.6/stable [amd64])
Inst libcacard0 (1:2.5.0-3 Debian:9.6/stable [amd64])
Inst libimage-exiftool-perl (10.40-1 Debian:9.6/stable [all])
Inst libtinyxml2-4 (4.0.1-1 Debian:9.6/stable [amd64])
Inst libzen0v5 (0.4.34-1 Debian:9.6/stable [amd64])
Inst libmediainfo0v5 (0.7.91-1 Debian:9.6/stable [amd64])
Inst libspice-server1 (0.12.8-2.1+deb9u2 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Inst libusbredirparser1 (0.7.1-1 Debian:9.6/stable [amd64])
Inst libvdeplug2 (2.3.2+r586-2.1 Debian:9.6/stable [amd64])
Inst libxenstore3.0 (4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Inst libxen-4.8 (4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Inst mediainfo (0.7.91-1 Debian:9.6/stable [amd64])
Inst p7zip-rar (16.02-1 Debian:9.6/stable [amd64])
Inst libbrlapi0.6 (5.4-7+deb9u1 Debian:9.6/stable [amd64])
Inst libfdt1 (1.4.2-1 Debian:9.6/stable [amd64])
Inst seabios (1.10.2-1 Debian:9.6/stable [all])
Inst qemu-system-x86 (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Inst qemu-utils (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Inst qemu-kvm (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Inst polo-file-manager (18.8-0.1~mx17+1 MX repository:17.0/mx [amd64])
Conf libjs-jquery (3.1.1-2 Debian:9.6/stable [all])
Conf fish-common (2.7.1-3~mx17+1 MX repository:17.0/mx [all])
Conf libpcre2-32-0 (10.22-3 Debian:9.6/stable [amd64])
Conf fish (2.7.1-3~mx17+1 MX repository:17.0/mx [amd64])
Conf qemu-system-common (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Conf ipxe-qemu (1.0.0+git-20161027.b991c67-1 Debian:9.6/stable [all])
Conf libaio1 (0.3.110-3 Debian:9.6/stable [amd64])
Conf libcacard0 (1:2.5.0-3 Debian:9.6/stable [amd64])
Conf libimage-exiftool-perl (10.40-1 Debian:9.6/stable [all])
Conf libtinyxml2-4 (4.0.1-1 Debian:9.6/stable [amd64])
Conf libzen0v5 (0.4.34-1 Debian:9.6/stable [amd64])
Conf libmediainfo0v5 (0.7.91-1 Debian:9.6/stable [amd64])
Conf libspice-server1 (0.12.8-2.1+deb9u2 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Conf libusbredirparser1 (0.7.1-1 Debian:9.6/stable [amd64])
Conf libvdeplug2 (2.3.2+r586-2.1 Debian:9.6/stable [amd64])
Conf libxenstore3.0 (4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Conf libxen-4.8 (4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 Debian:9.6/stable, Debian-Security:9/stable [amd64])
Conf mediainfo (0.7.91-1 Debian:9.6/stable [amd64])
Conf p7zip-rar (16.02-1 Debian:9.6/stable [amd64])
Conf libbrlapi0.6 (5.4-7+deb9u1 Debian:9.6/stable [amd64])
Conf libfdt1 (1.4.2-1 Debian:9.6/stable [amd64])
Conf seabios (1.10.2-1 Debian:9.6/stable [all])
Conf qemu-system-x86 (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Conf qemu-utils (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Conf qemu-kvm (1:2.8+dfsg-6+deb9u5 Debian-Security:9/stable [amd64])
Conf polo-file-manager (18.8-0.1~mx17+1 MX repository:17.0/mx [amd64])

So lot's of depenencies..
And afterwards the real installation ( without simulation.)
Installed and run even from command line with one "cannot find trash folder" warning ( not unusaual on Livesystem ) and two little Gtk-warnings.

Posted: **Tue Nov 27, 2018 1:27 pm**

I usually use "dpkg" for installing packages, or via synaptic/MxPI. You wrote: Ignore the dbgsym (debug symbols) packages in #12. Sorry but you must consider I am not strong enough.
Thanks

Posted: **Tue Nov 27, 2018 1:35 pm**

I have polo installed from test on my two test machines but on my production machine it seemed to install OK with no error messages but is not in the menu and will not run from the terminal.

Posted: **Tue Nov 27, 2018 2:01 pm**

Fornhamfred wrote: Tue Nov 27, 2018 1:35 pm I have polo installed from test on my two test machines but on my production machine it seemed to install OK with no error messages but is not in the menu and will not run from the terminal.

Are there any messages when you run "polo-gtk" in the terminal?

Posted: **Tue Nov 27, 2018 2:02 pm**

balarm wrote: Tue Nov 27, 2018 1:27 pm I usually use "dpkg" for installing packages, or via synaptic/MxPI. You wrote: Ignore the dbgsym (debug symbols) packages in #12. Sorry but you must consider I am not strong enough.
Thanks

See post #20 . The package polo-file-manager from testrepo requies a lot of additional packages installed.
As testrepo is special, easiest is to install only this package polo-file-manager with MXPI and check/watch all dependend package will be installed automatically, which was shown in post #20 for demonstation purpose, only.

Posted: **Tue Nov 27, 2018 2:40 pm**

I saw post #20; I only said what I did step by step. I run polo-gtk in the terminal and there are a lot of "Warning and Critical" messages and Polo window is there running.

Posted: **Tue Nov 27, 2018 2:44 pm**

balarm wrote: Tue Nov 27, 2018 2:40 pm I saw post #20; I only said what I did step by step. I run polo-gtk in the terminal and there are a lot of "Warning and Critical" messages and Polo window is there running.

Ahh ok, Warning on commandline - just ignore , probaly GTK-related as some GTKstuff has issues when started from command line - , Critical's I had only one or two about trash-bin or so.

Posted: **Tue Nov 27, 2018 5:02 pm**

Here the output of the terminal

Code: Select all

mx17@mx1:~
$ polo-gtk

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class
Architecture: 64-bit
Host Name: mx1
CPU Cores: 2
RAM: 2996 MB
[Warning] Deleted invalid lock

(polo-gtk:13864): Pango-CRITICAL **: pango_font_description_from_string: assertion 'str != NULL' failed

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk.css:5978:26: 'titlebar_fg_color' is not a valid color name

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of type 'GParamBoolean' in 'GtkOverlay'
MainWindow: save_session()
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of typmx17@mx1:~
$ polo-gtk

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class
Architecture: 64-bit
Host Name: mx1
CPU Cores: 2
RAM: 2996 MB
[Warning] Deleted invalid lock

(polo-gtk:13864): Pango-CRITICAL **: pango_font_description_from_string: assertion 'str != NULL' failed

(polo-gtk:13864): Gtk-WARNING **: Theme parsing error: gtk.css:5978:26: 'titlebar_fg_color' is not a valid color name

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of type 'GParamBoolean' in 'GtkOverlay'
MainWindow: save_session()
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of type 'GParamBoolean' in 'GtkOverlay'

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of type 'GParamBoolean' in 'GtkOverlay'

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()
session restored: ============================================================

(polo-gtk:13864): Gtk-CRITICAL **: gtk_toolbar_remove: assertion 'content_to_remove != NULL' failed

e 'GParamBoolean' in 'GtkOverlay'

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed

(polo-gtk:13864): Gtk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gtk/gtkoverlay.c:669: invalid child property id 1 for "pass-through" of type 'GParamBoolean' in 'GtkOverlay'

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()

(polo-gtk:13864): Gdk-CRITICAL **: gdk_window_set_cursor: assertion 'GDK_IS_WINDOW (window)' failed
MainWindow: save_session()
session restored: ============================================================

(polo-gtk:13864): Gtk-CRITICAL **: gtk_toolbar_remove: assertion 'content_to_remove != NULL' failed

Posted: **Tue Nov 27, 2018 5:26 pm**

balarm wrote: Tue Nov 27, 2018 5:02 pm Here the output of the terminal

All those warnings are due to the fact that the gtk-related GUI-elements are started within a terminal windows.
If you start it not in a terminal window, none of those warning are shown, if you capture those.
E.g. if you want try it yourself: Run polo and capure all the output like this:
Press Alt+F2 get a comand-popup window
copy and paste tis command line:

Code: Select all

bash -c 'polo-gtk 2>&1 1>/tmp/POLO_START_CAPTURE.txt'

Press enter, Polo gets started, Now close polo
and open /tmp/POLO_START_CAPTURE.txt
It looks like this without any GTK-warnings:

Code: Select all

[23:18:57.516] Architecture: 64-bit
[23:18:57.516] Host Name: mx171
[23:18:57.516] CPU Cores: 8
[23:18:57.516] RAM: 32127 MB
[23:18:57.526] [Warning] Deleted invalid lock
[23:18:58.518] found thumb: /home/fehlix/.cache/thumbnails/normal/ed373536b36b8e668a80d15cb1c38146.png
[23:18:58.521] found thumb: /home/fehlix/.thumbnails/normal/d58d4a382f805eb2ed0315679a738931.png
[23:18:58.522] found thumb: /home/fehlix/.cache/thumbnails/normal/6c9441d1819fddc22e40070964724220.png
[23:18:58.523] found thumb: /home/fehlix/.cache/thumbnails/normal/225f1716541308a6d78b315f858a7cd4.png
[23:18:58.523] found thumb: /home/fehlix/.cache/thumbnails/normal/fea38c34117d800c326866038b508b7d.png
[23:18:58.527] MainWindow: save_session()
[23:18:58.696] MainWindow: save_session()
[23:18:58.803] MainWindow: save_session()
[23:18:58.983] MainWindow: save_session()
[23:18:59.143] MainWindow: save_session()
[23:18:59.316] MainWindow: save_session()
[23:18:59.486] MainWindow: save_session()
[23:18:59.670] MainWindow: save_session()
[23:18:59.841] MainWindow: save_session()
[23:19:00.010] MainWindow: save_session()
[23:19:00.026] session restored: ============================================================
[23:19:00.035] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:00.036] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:00.037] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:00.037] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:00.037] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:02.028] [MONITOR] G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT: /home/fehlix/.xsession-errors
[23:19:02.028] [MONITOR] G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT: /home/fehlix/.xsession-errors
[23:19:02.028] [MONITOR] G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT: /home/fehlix/.xsession-errors
[23:19:02.028] [MONITOR] G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT: /home/fehlix/.xsession-errors
[23:19:02.028] [MONITOR] G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT: /home/fehlix/.xsession-errors
[23:19:03.031] MainWindow: save_session()
[23:19:03.038] session saved: /home/fehlix/.config/polo/polo-last-session.json
[23:19:03.082] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:03.082] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:03.086] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:03.090] [MONITOR] G_FILE_MONITOR_EVENT_CHANGED: /home/fehlix/.xsession-errors
[23:19:03.098] Exiting Application

Posted: **Wed Nov 28, 2018 4:45 am**

Stevo wrote: Tue Nov 27, 2018 2:01 pm
Fornhamfred wrote: Tue Nov 27, 2018 1:35 pm I have polo installed from test on my two test machines but on my production machine it seemed to install OK with no error messages but is not in the menu and will not run from the terminal.
Are there any messages when you run "polo-gtk" in the terminal?

This is the terminal output:

Code: Select all

$ polo-gtk
[09:42:31.858] Architecture: 64-bit
[09:42:31.858] Host Name: master
[09:42:31.858] CPU Cores: 4
[09:42:31.859] RAM: 7960 MB
[09:42:32.696] E: Failed to open file '/usr/share/applications/libreoffice6.0-base.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-base.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-calc.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-calc.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-draw.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-draw.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-impress.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-impress.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-math.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-math.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-startcenter.desktop': No such file or directory
[09:42:32.697] E: Failed to read file: /usr/share/applications/libreoffice6.0-startcenter.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.697] E: Failed to open file '/usr/share/applications/libreoffice6.0-writer.desktop': No such file or directory
[09:42:32.698] E: Failed to read file: /usr/share/applications/libreoffice6.0-writer.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.698] E: Failed to open file '/usr/share/applications/libreoffice6.0-xsltfilter.desktop': No such file or directory
[09:42:32.698] E: Failed to read file: /usr/share/applications/libreoffice6.0-xsltfilter.desktop

(polo-gtk:7620): GLib-CRITICAL **: g_strsplit: assertion 'string != NULL' failed
[09:42:32.734] E: Trash: directories 'info' and 'files' not found: /home/wilf/.local/share/Trash
Segmentation fault

Posted: **Wed Nov 28, 2018 6:32 am**

Looks as if you installed a new liboffice6.1 and liboffice6.0 got removed?

Posted: **Wed Nov 28, 2018 11:56 am**

Richard wrote: Wed Nov 28, 2018 6: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?

Posted: **Wed Nov 28, 2018 2:30 pm**

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.

Posted: **Thu Nov 29, 2018 6:15 am**

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

Posted: **Thu Nov 29, 2018 1: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.

Posted: **Thu Nov 29, 2018 2:07 pm**

asqwerth wrote: Thu Nov 29, 2018 1: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.

Posted: **Thu Dec 05, 2019 9:26 am**

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.

Posted: **Thu Dec 05, 2019 9:37 am**

That is too bad. I had high hopes for it.

Posted: **Fri Aug 12, 2022 9:45 am**

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.

MX Linux Forum

Polo File Manager

Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager

Re: Polo File Manager