https://bugs.kde.org/show_bug.cgi?id=379516
--- Comment #18 from Méven Car <meve...@gmail.com> ---
I guess you have not reinstalled your system since you encountered the bug.
It may be beyond my knowledge.
Could do some digging ?
Find out what `ldd /usr/bin/solid-hardware5` returns.
On my kubuntu system (should be quite similar on kde-neon):
$ ldd /usr/bin/solid-hardware5
linux-vdso.so.1 (0x00007fff5bfcd000)
libKF5Solid.so.5 => /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
(0x00007fc86acd6000)
[...]
Then for where libKF5Solid.so, can use `apt-file -F search` to find the
packages this comes from (you may need to install apt-file)
For me the command would be :
$ apt-file -F search /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
libkf5solid5: /usr/lib/x86_64-linux-gnu/libKF5Solid.so.5
You can check the right one is used (the one from your 5.65 version package).
(apt show libkf5solid5 for instanec)
Another idea would be to run "ls -l `find /usr/lib -name libKF5Solid*`" to see
if you have multiple solid versions installed.
If this is inconclusive, it may be worthwhile looking into the sources of the
libkf5solid5 package and check the code is current and not lagging behind for
whatever reason: apt source libkf5solid5
then check in src/solid/devices/backends/udisks2/udisksstorageaccess.cpp that
104 correspond to the patch
https://cgit.kde.org/solid.git/commit/?id=1384f275ab2f1ad1841753ee163af6d1b0bb952b.
--
You are receiving this mail because:
You are watching all bug changes.
