Polo File Manager

Forum rules
Post Reply
Message
Author
balarm
Posts: 160
Joined: Thu Dec 07, 2017 2:15 pm

Re: Polo File Manager

#21 Post by balarm »

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
mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
Distro: MX-19.3x64 patito feo October 21 2019
Machine: Type: Laptop System: LENOVO product: 1951A47 v: ThinkPad T60
Top
User avatar
Fornhamfred
Posts: 309
Joined: Sun May 02, 2010 12:49 pm

Re: Polo File Manager

#22 Post by Fornhamfred »

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.
Top
User avatar
Stevo
Developer
Posts: 14645
Joined: Fri Dec 15, 2006 7:07 pm

Re: Polo File Manager

#23 Post by Stevo »

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?
Top
User avatar
fehlix
Developer
Posts: 12740
Joined: Wed Apr 11, 2018 5:09 pm

Re: Polo File Manager

#24 Post by fehlix »

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.
Top
balarm
Posts: 160
Joined: Thu Dec 07, 2017 2:15 pm

Re: Polo File Manager

#25 Post by balarm »

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.
mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
Distro: MX-19.3x64 patito feo October 21 2019
Machine: Type: Laptop System: LENOVO product: 1951A47 v: ThinkPad T60
Top
User avatar
fehlix
Developer
Posts: 12740
Joined: Wed Apr 11, 2018 5:09 pm

Re: Polo File Manager

#26 Post by fehlix »

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.
Top
balarm
Posts: 160
Joined: Thu Dec 07, 2017 2:15 pm

Re: Polo File Manager

#27 Post by balarm »

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
mx Kernel: 4.19.0-6-amd64 x86_64 bits: 64 Desktop: Xfce 4.14.2
Distro: MX-19.3x64 patito feo October 21 2019
Machine: Type: Laptop System: LENOVO product: 1951A47 v: ThinkPad T60
Top
User avatar
fehlix
Developer
Posts: 12740
Joined: Wed Apr 11, 2018 5:09 pm

Re: Polo File Manager

#28 Post by fehlix »

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
:puppy:
Top
User avatar
Fornhamfred
Posts: 309
Joined: Sun May 02, 2010 12:49 pm

Re: Polo File Manager

#29 Post by Fornhamfred »

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
Top
User avatar
Richard
Posts: 1590
Joined: Fri Dec 12, 2008 9:31 am

Re: Polo File Manager

#30 Post by Richard »

Looks as if you installed a new liboffice6.1 and liboffice6.0 got removed?
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.
HP Ryzen 5 17-cp3xxx with MX23.4 AHS & Liquorix 6.10-12~mx23ahs amd64
Top
Post Reply

Return to “General”