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 Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2081943 Title: Application time out monitor does not work correctly Status in linux package in Ubuntu: Opinion Bug description: Ubuntu 24.04.01 System resources near by 100% in use. Never had a problem in this case with Ubuntu 22.04.03. E,g.: firefox open with 10Tabs, visible in the panel. Get the application in foreground,open a new Tab, e.g.: with youtube as address, got immediately the message Box with two Buttons "Wait for response" "Kill the process" of the respective application, in this case firefox. I did check wait during the youtube page will appear, get again the message Box, again check "wait", going to fill out the youtube "search txt box" and will be 15 times interrupted by the message box and have to check the "wait" button. Obviously the application firefox works as expected, but the application time out monitor does not recognize it (same with nautilus). After a call of the resources monitor application, I could switch off the senseless time out monitor message box with two Buttons "Wait for response" "Kill the process" A workaround would help : How to switch off this senseless monitor or to set the time out to 1h ? ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-45-generic 6.8.0-45.45 ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12 Uname: Linux 6.8.0-45-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: richard 2036 F.... pipewire /dev/snd/controlC0: richard 2041 F.... wireplumber /dev/snd/controlC1: richard 2041 F.... wireplumber CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 25 07:26:51 2024 InstallationDate: Installed on 2024-01-24 (245 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X515DA_M515DA ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=fd8b1656-bd1b-411b-b6bd-7cbf3bc18cdb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-45-generic N/A linux-backports-modules-6.8.0-45-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.3 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-08-31 (25 days ago) dmi.bios.date: 10/19/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X515DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X515DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX515DA.302:bd10/19/2020:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX515DA_M515DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX515DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUSLaptop dmi.product.name: VivoBook_ASUSLaptop X515DA_M515DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.init.d.apport: 2024-07-22T16:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
