I'm sorry you didn't agree with my analysis of the situation. If you look at the dmesg file, or the syslog file, the minidlna is having issues as it is throwing segmentation faults.
Sep 21 01:54:38 Laptop2 kernel: minidlnad[93836]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 4 (core 2, socket 0) Sep 21 02:14:39 Laptop2 kernel: minidlnad[95522]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 4 (core 2, socket 0) Sep 21 08:15:16 Laptop2 kernel: minidlnad[108956]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 1 (core 0, socket 0) Sep 21 20:46:20 Laptop2 kernel: vivictpp[145335]: segfault at 7ecb98ea9d6d ip 000061b04f6fb869 sp 00007ecc7a9ff980 error 6 in vivictpp[61b04e53d000+155c000] likely on CPU 0 (core 0, socket 0) Sep 22 08:16:42 Laptop2 kernel: minidlnad[176849]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 6 (core 3, socket 0) Sep 22 14:44:27 Laptop2 kernel: minidlnad[201339]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 0 (core 0, socket 0) Sep 22 14:44:27 Laptop2 kernel: minidlnad[201353]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 1 (core 0, socket 0) Sep 22 15:52:06 Laptop2 kernel: minidlnad[204933]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 3 (core 1, socket 0) Sep 22 15:52:06 Laptop2 kernel: minidlnad[204935]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 0 (core 0, socket 0) Sep 25 01:16:23 Laptop2 kernel: minidlnad[347458]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 7 (core 3, socket 0) Sep 25 01:26:37 Laptop2 kernel: minidlnad[348092]: segfault at 20 ip 00005c8984058dd2 sp 00007ffd03f8aac0 error 4 in minidlnad[5c898403a000+2e000] likely on CPU 1 (core 0, socket 0) I also know that there are reported memory leaks with minidlnad which I suspect was leading to the reduced performance. Also, when a major upgrade is done, as happens when moving from 22.04 to 24.04, even though the application you are running remains "unchanged", a lot of the underlying infrastructure changes, which can cause the application to fail in new/different ways. The upgrade to 24.04 changed many of the shared libraries, and the kernel, so even though minidlnad is the same version, it doesn't mean that because it used to be error-free that it still is. Either way, the prompt and timeout addition that you are asking about is not a kernel issue. I was just trying to help point you to a possible root cause. This issue is probably better to be opened against gnome-desktop (https://bugs.launchpad.net/ubuntu/+source/gnome-desktop) or gnome-shell (https://bugs.launchpad.net/ubuntu/+source/gnome-shell). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081943 Title: Application time out monitor does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081943/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
