https://bugs.kde.org/show_bug.cgi?id=445549
jwag...@graffdeals.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jwag...@graffdeals.com
--- Comment #12 from jwag...@graffdeals.com ---
I've been plagued by this same flaw for a long time now, but really didn't have
anything substantive to contribute until now.
A system at work has Ubuntu 20.04 on it with Krusader 2.7.2-1. It does not
have this problem.
My home system has Ubuntu 22.04 on it with Krusader 2.7.2-1. It does have the
issue.
---
Here are the packages I have installed that match the pattern 'kio':
kio-extras-data/jammy,jammy,now 4:21.12.3-0ubuntu1 all [installed,automatic]
kio-extras/jammy,now 4:21.12.3-0ubuntu1 amd64 [installed,automatic]
kio/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
libkf5kiocore5/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
libkf5kiofilewidgets5/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
libkf5kiogui5/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
libkf5kiontlm5/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
libkf5kiowidgets5/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
On the unaffected system at work, these are the versions of the above packages:
kio-extras - 4.19.12.3a
kio-extras-data - 4.19.12.3a
kio - 5.68.6
libkf5kiocore5 - 5.68.0
libkf5kiofilewidgets5 - 5.68.0
libkf5kiogui5 - 5.68.0
libkf5kiontlm5 - 5.68.0
libkf5kiowidgets5 - 5.68.0
There is also a qml-module-org-kde-kio package at version 5.68.0 that is not
installed on my home machine.
---
Honestly, I do not know what most of these packages do or how they interact
with one another, but it at least narrows down things a bit. Unfortunately,
ubuntu does not like people installing old packages and so I cannot easily
install old versions on my home machine to isolate it further.
# apt list --all-versions kio
Listing... Done
kio/jammy,now 5.92.0-0ubuntu1 amd64 [installed,automatic]
Is there a repository of .deb files with older versions of these kio libraries?
If so, I'd be willing to play on my home laptop to figure out what version it
was introduced in, though only if there's a reasonable chance of getting it
fixed... this bug has been open for well over 2 years and there doesn't seem to
be any activity on it.
--
You are receiving this mail because:
You are watching all bug changes.
