You are not logged in.
Hi all && a Happy fantastic 2021! ;D
Well, since the recent major update a couple of days ago thunar (stand-alone) has been lagging as hell~
Also its side-pane now shows many subfolders of / under "devices".
Probably that's because it's pretty outdated – on my p4 pacman tells me it's v1.8, while @x86_64 that's already v4.16!
So it would be very cool to have it modernized...
Last edited by cx (2021-02-19 18:25:53)
Offline
Besides ... while contemporarily switching to pcmanfm
Also its side-pane now shows many subfolders of / under "devices".
– that's the same issue here.
Offline
Thunar is not that outdated, they just have very wierd version numbers. After the version we have, 1.8.16, they directly jumped to 4.15 and 4.16. And 4.15 came out in Oct 2020.
That led to your confusion.
So yes, it is out of date, but not as much as the numbers suggest.
Offline
"Many subfolders of / under "devices" " is probably due to you having some stuff mounted at that time.
On my system, while not having anything plugged into my laptop, thunar shows Filesystem and Filesystem root, which is basically just /. No idea why they have two links to the same location. Maybe unmount some of the drives connected to your machine if you don't need them?
As for laggy, I don't know what might be causing that. You must be doing something memory and cpu intensive at the time, or accessing folders which have a lot of stuff in them.
Not really anything to be done there.
Last edited by mistersmee (2021-01-22 16:24:51)
Offline
Hi & thx for the input!
Thanks for noticing that funny thunar versioning.
However, the problems are persistent. At least pcmanfm still starts without delay, while thunar currently takes up to 30secs; same thing when invoking file operation dialogues like "Safe as" etc. And that kinda sucks...
But meanwhile I've seen this annoying issue for other programs as well, such as xed. So it rather looks like an underlying problem to me. Maybe just another missing update of gtk3 or dbus?
With that extra folders in both thunar and pcmanfm side panes: No, I don't have any other drives or devices plugged in! Then you wouldn't really recommend to unmount e. g. "home" or "tmp", right? – Besides, if I remember correctly, the same happened on my desktop box (which is on Manjaro64) about 2 weeks ago – but only for a session, or maximum a day. Then it disappeared and was never seen again.
Yet I can ssh into Arch32 from my desktop box as a workaround for now.
Last edited by cx (2021-01-27 10:30:10)
Offline
Hi & thx for the input!
Thanks for noticing that funny thunar versioning.
However, the problems are persistent. At least pcmanfm still starts without delay, while thunar currently takes up to 30secs; same thing when invoking file operation dialogues like "Safe as" etc. And that kinda sucks...
But meanwhile I've seen this annoying issue for other programs as well, such as xed. So it rather looks like an underlying problem to me. Maybe just another missing update of gtk3 or dbus?
With that extra folders in both thunar and pcmanfm side panes: No, I don't have any other drives or devices plugged in! Then you wouldn't really recommend to unmount e. g. "home" or "tmp", right? – Besides, if I remember correctly, the same happened on my desktop box (which is on Manjaro64) about 2 weeks ago – but only for a session, or maximum a day. Then it disappeared and was never seen again.
Yet I can ssh into Arch32 from my desktop box as a workaround for now.
Maybe start thunar through the terminal and check the error messages there?
I doubt it's gtk3 or dbus, because pcmanfm depends on both of them as well, and that's fine, as you say. Must be something up with thunar specifically, or something with it's dependencies. Xed tho... That's such a small program, with almost no dependencies. Again, opening through the terminal will better identify what the issue is,
Yeah, of course don't unmount /home or /tmp. What are the names of those extra folders? If they are "/home" and "/tmp", then you must be mounting /home separately. /tmp is different from /, it is mounted as a tmpfs, tho no idea why thunar is picking that up.
You wouldn't have btrfs as your filesystem, would you? Maybe thunar is picking up the subvolumes.
Last edited by mistersmee (2021-01-27 12:21:26)
Offline
You're welcome.
And yes, I do have btrfs, but that hasn't ever been a problem!
Here you are: The extra side pane entries literally are "Filesystem root", ".snapshots", "home" and "tmp", and they're specified in /etc/fstab.
For the logs, here they are:
$ LANG=C thunar &
(thunar:8870): Gtk-WARNING **: 22:23:14.632: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name
(thunar:8870): Gtk-WARNING **: 22:23:14.634: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name
(thunar:8870): Gtk-WARNING **: 22:23:14.635: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name
(thunar:8870): Gtk-WARNING **: 22:23:14.640: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name
(thunar:8870): Gtk-WARNING **: 22:23:14.643: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
ThunarThumbnailer: got 0 handle (Queue)
ThunarThumbnailer: got 0 handle (Error or Ready)
ThunarThumbnailer: got 0 handle (Finished)
$ LANG=C xed &
(xed:8927): Gtk-WARNING **: 22:25:20.030: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name
(xed:8927): Gtk-WARNING **: 22:25:20.033: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name
(xed:8927): Gtk-WARNING **: 22:25:20.033: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name
(xed:8927): Gtk-WARNING **: 22:25:20.039: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name
(xed:8927): Gtk-WARNING **: 22:25:20.041: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class
(xed:8927): libpeas-WARNING **: 22:25:20.861: Failed to load module 'python3loader': libpython3.8.so.1.0: cannot open shared object file: No such file or directory
(xed:8927): libpeas-WARNING **: 22:25:20.862: Could not load plugin loader 'python3'
** (xed:8927): WARNING **: 22:25:20.862: Failed to load builtin plugin: Text Size
** (xed:8927): WARNING **: 22:25:20.863: Failed to load builtin plugin: Join Lines
** (xed:8927): WARNING **: 22:25:20.863: Failed to load builtin plugin: Open URI
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
** (xed:8927): WARNING **: 22:25:48.921: Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory
** (xed:8927): WARNING **: 22:25:48.929: Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory
One might think: well, then there must be something wrong with thunar-volman! – Nope, as I said, it's the same erroneous side pane in instantly starting pcmanfm! – For the record, here is its log, too:
$ LANG=C pcmanfm &
Gtk-Message: 22:39:52.013: Failed to load module "xapp-gtk3-module"
Job 3, 'LANG=C pcmanfm &' has ended
All I see is a bunch of Gtk issues! And the python3 one, while python seems up-to-date; same version for 64bit. – Same is for udisks2, or the Gtk themes I use, while changing themes doesn't make a difference!
And believe me, pcmanfm is fast here, because it runs on Gtk2. So for the slowliness, it must be a Gtk3 problem!
Besides, while python is currently v3.9, the thunar log shows it can't find v3.8! Additionally, xed's two of its many dependencies "libpeas" and "xapp" for instance use both python3 and Gtk3! – So it's very likely both going wrong since the last couple of weeks.
Last edited by cx (2021-01-28 17:40:26)
Offline
Yes, sorry. Bugs in top-notch Gnome, KDE and friends is accumulating, as the devs are not using any of this bloatware on old machines
(disclaimer: I count myself as dev). :-)
The testing effort is just huge as it involves spinning up VMs and starting all display/window managers and hunting down bugs.
Currently webkit2gtk could be a major blocker for several packages not having been rebuilt.
The other one is icu 68 which has not been rebuilt most likely everywhere, there is a shim package
'icu67' in case you get funny 'icu*.so' loading errors.
Offline
You're welcome.
And yes, I do have btrfs, but that hasn't ever been a problem!
Here you are: The extra side pane entries literally are "Filesystem root", ".snapshots", "home" and "tmp", as they're specified in /etc/fstab. – But these also haven't never been a problem!
For the logs, here they are:
$ LANG=C thunar & (thunar:8870): Gtk-WARNING **: 22:23:14.632: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name (thunar:8870): Gtk-WARNING **: 22:23:14.634: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name (thunar:8870): Gtk-WARNING **: 22:23:14.635: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name (thunar:8870): Gtk-WARNING **: 22:23:14.640: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name (thunar:8870): Gtk-WARNING **: 22:23:14.643: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) ThunarThumbnailer: got 0 handle (Queue) ThunarThumbnailer: got 0 handle (Error or Ready) ThunarThumbnailer: got 0 handle (Finished) $ LANG=C xed & (xed:8927): Gtk-WARNING **: 22:25:20.030: Theme parsing error: gtk-main.css:2475:53: 'bg_color' is not a valid color name (xed:8927): Gtk-WARNING **: 22:25:20.033: Theme parsing error: gtk-main.css:2586:42: 'base_color' is not a valid color name (xed:8927): Gtk-WARNING **: 22:25:20.033: Theme parsing error: gtk-main.css:2595:34: 'bg_color' is not a valid color name (xed:8927): Gtk-WARNING **: 22:25:20.039: Theme parsing error: gtk-main.css:3083:34: 'bg_color' is not a valid color name (xed:8927): Gtk-WARNING **: 22:25:20.041: Theme parsing error: gtk-main.css:3431:66: Invalid name of pseudo-class (xed:8927): libpeas-WARNING **: 22:25:20.861: Failed to load module 'python3loader': libpython3.8.so.1.0: cannot open shared object file: No such file or directory (xed:8927): libpeas-WARNING **: 22:25:20.862: Could not load plugin loader 'python3' ** (xed:8927): WARNING **: 22:25:20.862: Failed to load builtin plugin: Text Size ** (xed:8927): WARNING **: 22:25:20.863: Failed to load builtin plugin: Join Lines ** (xed:8927): WARNING **: 22:25:20.863: Failed to load builtin plugin: Open URI Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) ** (xed:8927): WARNING **: 22:25:48.921: Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory ** (xed:8927): WARNING **: 22:25:48.929: Error loading plugin: libnuspell.so.4: cannot open shared object file: No such file or directory
One might think: well, then there must be something wrong with thunar-volman! – Nope, as I said, it's the same erroneous side pane in instantly starting pcmanfm! – For the record, here is its log, too:
$ LANG=C pcmanfm & Gtk-Message: 22:39:52.013: Failed to load module "xapp-gtk3-module" Job 3, 'LANG=C pcmanfm &' has ended
All I see is a bunch of Gtk issues! And the python3 one, while python seems up-to-date; same version for 64bit. – Same is for udisks2, or the Gtk themes I use, while changing themes doesn't make a difference!
And believe me, pcmanfm is fast here, because it runs on Gtk2. So for the slowliness, it must be a Gtk3 problem!
Besides, while python is currently v3.9, the thunar log shows it can't find v3.8! Additionally, xed's two of its many dependencies "libpeas" and "xapp" for instance use both python3 and Gtk3! – So it's very likely both going wrong since the last couple of weeks.
Well, it is picking up the subvolumes. I fiddled with btrfs a few times, never really got the hang of it, sticked to what I know best, ext4. But I remember that snapshots, home, tmp and root are subvolumes of btrfs.
No idea why it's doing that, or whether it even should be doing that, as I said, I don't have a lot of experience with btrfs, and what little I have, I never used a GUI file manager then.
Hmm, those gtk warnings are harmless, nothing there.
But this
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
is promising. You have gvfs and all its dependencies, including the optional dependencies installed, I presume? It's an optional dependency for thunar. That error seems to point to an error with gvfs.
Pcmanfm also optdepends upon gvfs, so that solves why both of them are misbehaving.
I see. Libpeas must not have been rebuilt against python3.9.
Checking the repos, I see that there is a version of libpeas in testing that has been rebuilt against python3.9. I guess, wait a bit, for it to come to stable. Or, download it, I never had a problem running packages from testing, they never were unstable for me.
Last edited by mistersmee (2021-01-28 07:42:56)
Offline
Hey, how about you check the web for the error I mentioned. There were quite a few solutions that I found, but all were specific problems, that I'm not sure on whether they apply to you.
Offline
Yes, sorry. Bugs in top-notch Gnome, KDE and friends is accumulating, as the devs are not using any of this bloatware on old machines
Sure, but I have to disappoint you ...
It's not affecting me, as I don't use any of them. No DE, just Xmonad via a plain startx.
Also I wouldn't call xed or thunar killer apps really. – Besides, these have shown the same symptoms in Sway, my spare WM. Yet I just can't post the logs from there, since sway is out of order lately, too, and does not start at all anymore, just throwing me back to tty login.
Currently webkit2gtk could be a major blocker for several packages not having been rebuilt.
The other one is icu 68 which has not been rebuilt most likely everywhere, there is a shim package
'icu67' in case you get funny 'icu*.so' loading errors.
So far not experiencing these.
But this
Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
is promising. You have gvfs and all its dependencies, including the optional dependencies installed, I presume? It's an optional dependency for thunar. That error seems to point to an error with gvfs.
Pcmanfm also optdepends upon gvfs, so that solves why both of them are misbehaving.
Good point. Also xed makes use of it for handling URI stuff, I guess:
$ LANG=C thunar & ... Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) ... $ LANG=C xed & ... Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) ...
This would explain why it also takes ages when attempting to open or save files.
Hey, how about you check the web for the error I mentioned. There were quite a few solutions that I found, but all were specific problems, that I'm not sure on whether they apply to you.
Yeah, I'm going to look for them.
Well, it is picking up the subvolumes. I fiddled with btrfs a few times, never really got the hang of it, sticked to what I know best, ext4. But I remember that snapshots, home, tmp and root are subvolumes of btrfs.
No idea why it's doing that, or whether it even should be doing that, as I said, I don't have a lot of experience with btrfs, and what little I have, I never used a GUI file manager then.
No, "tmp" is not a subvolume:
$ btrfs subvolume list /
ID 257 gen 142027 top level 5 path @
ID 258 gen 34 top level 5 path @boot
ID 259 gen 142027 top level 5 path @home
ID 260 gen 65476 top level 5 path @snapshots
ID 263 gen 22 top level 257 path var/lib/portables
ID 264 gen 23 top level 257 path var/lib/machines
So it's still not a btrfs problem. The filesystem doesn't matter here.
Just in case it's the inter process communication within a session currently having a hick-up, dbus is yet not completely out for me; wouldn't be the first time it would have caused trouble ...
Anyway it must be something basic.
Hmm, those gtk warnings are harmless, nothing there.
Maybe so, they're just warnings, and the GUI gets drawn eventually; except for
Gtk-Message: 12:50:25.443: Failed to load module "xapp-gtk3-module"
I see. Libpeas must not have been rebuilt against python3.9.
Checking the repos, I see that there is a version of libpeas in testing that has been rebuilt against python3.9. I guess, wait a bit, for it to come to stable. Or, download it, I never had a problem running packages from testing, they never were unstable for me.
Thanks for the hint. I should give that a try, though until now I haven't used the testing repo at all (as far as I remember).
Last edited by cx (2021-01-31 12:11:09)
Offline
Thanks for the updates of libpeas, thunar etc., guys!
However, thunar now does not start at all anymore:
$ thunar &
thunar: symbol lookup error: thunar: undefined symbol: xfce_gtk_get_action_entry_by_id
No changes with xed and pcmanfm (for reference); will continue checking "org.gtk.vfs.UDisks2VolumeMonitor" (see above) when I've time.
Last edited by cx (2021-01-31 12:17:42)
Offline
What is the output of
ldd /usr/bin/thunar
?
After a quick search on the net, I got some results relating to dependencies libraries not getting updated, usually exo.
The appropriate version for exo, i.e 4.16.something is in the testing repo.
Thunar was able to launch fine on my system, no problems whatsoever.
Offline
OK – back to normal now after updating the system almost daily!!
No more start up delays or file managers showing weird paths. Yet I can't actually figure out which package/s were responsible since there were so many...
Offline
Yeah, there where a lot of stuck packages, webkit2gtk was a major one. Turns out, that making Gnome work fixes all other window managers too, as
they rely on similar or Gnome libraries directly..
Offline