https://bugs.kde.org/show_bug.cgi?id=517253
Bug ID: 517253
Summary: Crash in Solid::Device::udi()
Classification: Frameworks and Libraries
Product: frameworks-solid
Version First 6.20.0
Reported In:
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
SUMMARY
libkf6solid6:amd64-dependent KDE apps suddenly crash when performing
mount/unmount performing as root. I needed the raw `mount` command, and don't
know if `udisksctl` would avoid the crash.
STEPS TO REPRODUCE
1. `gdb --args kate -b ~/ext4benchmarks.txt`
2. I was running this as root:
```console
root@daniel-desktop3:~# systemctl stop containerd docker
root@daniel-desktop3:~# mkdir -p /run/downloadtmp /run/archives
root@daniel-desktop3:~# mount -o remount,size=8G /run
root@daniel-desktop3:~# mount --bind /run/downloadtmp /var/lib/containerd
root@daniel-desktop3:~# systemctl start containerd docker
root@daniel-desktop3:~# docker run --rm -itv
/run/archives:/var/cache/apt/archives ubuntu:24.04 bash -c 'apt update && apt
install -dy texlive-full'
[... 4417 MB and 755 packages ...]
root@daniel-desktop3:~# systemctl stop containerd docker
root@daniel-desktop3:~# umount /var/lib/containerd
root@daniel-desktop3:~# wipefs -a /dev/sdb2
root@daniel-desktop3:~# mkfs.ext4 /dev/sdb2
mke2fs 1.47.2 (1-Jan-2025)
64-bit filesystem support is not enabled. The larger fields afforded by this
feature enable full-strength checksumming. Pass -O 64bit to rectify.
Creating filesystem with 2097152 4k blocks and 262144 inodes
Filesystem UUID: d370114c-abe5-4b16-adba-e6b626b76f1d
Superblock backups stored on blocks:
Allocating group tables: done
Writing inode tables: done
Creating journal (16640 blocks): done
Writing superblocks and filesystem accounting information: done
root@daniel-desktop3:~# mount /dev/sdb2 /var/lib/containerd
root@daniel-desktop3:~# rm -rf /var/lib/containerd/* /run/containerd
root@daniel-desktop3:~# systemctl start containerd docker
root@daniel-desktop3:~# docker pull ubuntu:24.04
24.04: Pulling from library/ubuntu
01d7766a2e4a: Pull complete
fd8cda969ed2: Download complete
Digest: sha256:d1e2e92c075e5ca139d51a140fff46f84315c0fdce203eab2807c7e495eff4f9
Status: Downloaded newer image for ubuntu:24.04
docker.io/library/ubuntu:24.04
root@daniel-desktop3:~# sync
root@daniel-desktop3:~# sysctl -w vm.drop_caches=3
vm.drop_caches = 3
root@daniel-desktop3:~# time docker run --rm -v /run/archives:/mnt ubuntu:24.04
bash -c 'dpkg --force-all -i /mnt/*.deb ; sync'
```
3. Before running the last command, I saved the file in Kate
4. When attempting to reproduce this, I `rm -f`ed the Docker container before
it finished
5. I then dragged my mouse to select text, and repeatedly hovered and unhovered
the window
OBSERVED RESULT
Kate suddenly quit when run outside gdb. In gdb, I get:
```text
Thread 1 "kate" received signal SIGSEGV, Segmentation fault.
0x00007ffff38ab4b4 in Solid::Device::udi() const () from
/lib/x86_64-linux-gnu/libKF6Solid.so.6
(gdb) bt
#0 0x00007ffff38ab4b4 in Solid::Device::udi() const () at
/lib/x86_64-linux-gnu/libKF6Solid.so.6
#1 0x00007fffee0fa794 in ??? () at
/lib/x86_64-linux-gnu/libKF6KIOFileWidgets.so.6
#2 0x00007ffff5de4a95 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#3 0x00007ffff38a8ec2 in Solid::DeviceNotifier::deviceRemoved(QString const&)
() at /lib/x86_64-linux-gnu/libKF6Solid.so.6
#4 0x00007ffff5de4a95 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#5 0x00007ffff38c0482 in ??? () at /lib/x86_64-linux-gnu/libKF6Solid.so.6
#6 0x00007ffff38fbd2a in ??? () at /lib/x86_64-linux-gnu/libKF6Solid.so.6
#7 0x00007ffff5de4a95 in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#8 0x00007ffff391c3ad in ??? () at /lib/x86_64-linux-gnu/libKF6Solid.so.6
#9 0x00007ffff3924a1a in ??? () at /lib/x86_64-linux-gnu/libKF6Solid.so.6
#10 0x00007ffff7b2775d in ??? () at /lib/x86_64-linux-gnu/libQt6DBus.so.6
#11 0x00007ffff5dd61d4 in QObject::event(QEvent*) () at
/lib/x86_64-linux-gnu/libQt6Core.so.6
#12 0x00007ffff739d49f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Widgets.so.6
#13 0x00007ffff5d8add8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib/x86_64-linux-gnu/libQt6Core.so.6
#14 0x00007ffff5d8b04e in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#15 0x00007ffff5ff445f in ??? () at /lib/x86_64-linux-gnu/libQt6Core.so.6
#16 0x00007ffff478dc7b in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff478f2b7 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ffff478f4a3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007ffff5ff130d in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /lib/x86_64-linux-gnu/libQt6Core.so.6
#20 0x00007ffff5d944c3 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/lib/x86_64-linux-gnu/libQt6Core.so.6
#21 0x00007ffff5d8dc07 in QCoreApplication::exec() () at
/lib/x86_64-linux-gnu/libQt6Core.so.6
#22 0x000055555555fd3c in ??? ()
#23 0x00007ffff542a575 in __libc_start_call_main
(main=main@entry=0x55555555cf10, argc=argc@entry=3,
argv=argv@entry=0x7fffffffd898) at ../sysdeps/nptl/libc_start_call_main.h:58
#24 0x00007ffff542a628 in __libc_start_main_impl
(main=0x55555555cf10, argc=3, argv=0x7fffffffd898, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd888) at
../csu/libc-start.c:360
#25 0x00005555555619b5 in ??? ()
```
EXPECTED RESULT
It should not crash.
SOFTWARE/OS VERSIONS
Operating System: Ubuntu 25.10
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.17.0-14-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 32 GiB of RAM (31.3 GiB usable)
Graphics Processor: AMD Radeon RX 6650 XT
ADDITIONAL INFORMATION
I am using the latest
https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/backports on Ubuntu 25.10.
Fedora has a [similar
crash](https://retrace.fedoraproject.org/faf/reports/1382190/) with KDE Connect
instead of Kate
Unknown if related to https://bugs.kde.org/show_bug.cgi?id=494224 .
Plasmashell, KRunner, and Dolphin crashes are slightly tolerable. But Kate
crashes can cause data loss. I often write many paragraphs in Unnamed files
before finally managing to pick a filename with difficulty, so those Unnamed
files won't have swap files and will be lost.
--
You are receiving this mail because:
You are watching all bug changes.
