Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)
Hi, On 2023-07-02 17:37, Antonio wrote: > Debian/Sid > > Operating System: Debian GNU/Linux > KDE Plasma Version: 5.27.5 > KDE Frameworks Version: 5.107.0 > Qt Version: 5.15.8 > Kernel Version: 6.3.0-1-amd64 (64-bit) > Graphics Platform: Wayland > Processors: 24 × 12th Gen Intel® Core™ i9-12900T > Memory: 31.1 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 770 (integrated) > Manufacturer: ASUS ROG STRIX B660-I GAMING WIFI > > > dmesg: > [dom lug 2 17:28:34 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, > not enough memory for the allocation > [dom lug 2 17:28:34 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, > not enough memory for the allocation > [dom lug 2 17:28:35 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, > not enough memory for the allocation > [dom lug 2 17:28:36 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, > not enough memory for the allocation > [dom lug 2 17:28:37 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, > not enough memory for the allocation > > kernel debian sid: > - linux-image-amd64 > > Linux SAT 6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12) > x86_64 GNU/Linux > > Same problems Thanks for the infos. Unfortunately I have not been able to reproduce the problem locally, either on a laptop with an Intel Graphic card or with a Bookworm QEMU image upgraded to the latest sid. This means that things will have to be debug on your side. From what I understood you are still able to run applications, so could you please open a Konsole, and provide additional infos: - Please provide the output of the "ldd /usr/bin/plasmashell" command - Please try running plasmashell under strace in order to have more details about that failed memory allocation using "strace -o log /usr/bin/plasmashell". Then please send me the output "log" file, possibly privately without Cc to the Debian BTS. Thanks Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)
I carried out further tests, until I replicated the problem on a virtual machine. Then I compared the plasma configuration subdir with a functioning version (obtained experimentally, resetting the arrangement of the desktop and windows, from default breeze theme). The difference that determines the problem is in the "~/.config/plasma-org.kde.plasma.desktop-appletsrc", section "[Screenmapping]". I noticed that "itemsondisabledscreens" and "screenmapping" items have an excessive line length. LENGTH LINE BYTES FIRST 200 chars 82 --- ok-plasma-org.kde.plasma.desktop-appletsrc 2023-07-03 13:26:44.894 83 +++ bad-plasma-org.kde.plasma.desktop-appletsrc 2023-07-03 12:35:57.69 16 [ScreenMapping] 24 -itemsOnDisabledScreens= 392 -screenMapping=desktop:/4.png,0,71c04f84-b363-4dca-a9a8-671fbb033f34,d... 14110 +itemsOnDisabledScreens=2,19c9821c-6bd3-4d27-b17a-1e325203a1fc,1,deskt... 3994359 +screenMapping=desktop:/safekernel-bk110323.01-rel6.1.18/build/include... This was also noted from the file size: Bad: -rw--- 1 root root 37K Jul 3 13:43 ~/.config/plasma-org.kde.plasma.desktop-appletsrc Good: -rw--- 1 root root 12549 3 lug 13.47 ~/.config/plasma-org.kde.plasma.desktop-appletsrc If I remove the entire section, everything works well. I don't know why, but these lines have elongated dramatically. Perhaps the processes that manage them do not control the maximum length of the lines ... With the previous version of Libc this problem had never occurred, even in the presence of these lines; while with the new version he came out. However, now the problem seems to have solved.
Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)
I also reported the problem to the KDE team: https://bugs.kde.org/show_bug.cgi?id=471903
[Git][glibc-team/tzdata][sid] 2 commits: Update Romanian debconf translation
Benjamin Drung pushed to branch sid at GNU Libc Maintainers / tzdata Commits: 8f77595b by Benjamin Drung at 2023-07-03T16:58:23+02:00 Update Romanian debconf translation Closes: #1038905 Thanks: Remus-Gabriel CheluSigned-off-by: Benjamin Drung - - - - - 2fb15014 by Benjamin Drung at 2023-07-03T17:19:07+02:00 Release tzdata 2023c-7 Signed-off-by: Benjamin Drung - - - - - 2 changed files: - debian/changelog - debian/po/ro.po View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/compare/05eadbc1141a405fb88a19ab4efb0556b942bbab...2fb15014c44c32af623ba07da1465739a7e4caf2 -- View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/compare/05eadbc1141a405fb88a19ab4efb0556b942bbab...2fb15014c44c32af623ba07da1465739a7e4caf2 You're receiving this email because of your account on salsa.debian.org.
[Git][glibc-team/tzdata] Pushed new tag debian/2023c-7
Benjamin Drung pushed new tag debian/2023c-7 at GNU Libc Maintainers / tzdata -- View it on GitLab: https://salsa.debian.org/glibc-team/tzdata/-/tree/debian/2023c-7 You're receiving this email because of your account on salsa.debian.org.
Processed: Bug#1038905 marked as pending in tzdata
Processing control commands: > tag -1 pending Bug #1038905 [tzdata] Subject: [INTL:ro] Romanian debconf templates translation-revision of tzdata Added tag(s) pending. -- 1038905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of tzdata_2023c-7_source.changes
tzdata_2023c-7_source.changes uploaded successfully to localhost along with the files: tzdata_2023c-7.dsc tzdata_2023c-7.debian.tar.xz tzdata_2023c-7_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Bug#1038905: marked as done (Subject: [INTL:ro] Romanian debconf templates translation-revision of tzdata)
Your message dated Mon, 03 Jul 2023 16:12:10 + with message-id and subject line Bug#1038905: fixed in tzdata 2023c-7 has caused the Debian Bug report #1038905, regarding Subject: [INTL:ro] Romanian debconf templates translation-revision of tzdata to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1038905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tzdata Version: N/A Severity: wishlist Tags: l10n, patch Dear Maintainer, Please find attached the Romanian translation of the «ro.po» file. Thanks, Remus-Gabriel ro.po Description: Binary data --- End Message --- --- Begin Message --- Source: tzdata Source-Version: 2023c-7 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of tzdata, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated tzdata package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Jul 2023 17:18:18 +0200 Source: tzdata Built-For-Profiles: noudeb Architecture: source Version: 2023c-7 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Benjamin Drung Closes: 1038905 Changes: tzdata (2023c-7) unstable; urgency=medium . * Update Romanian debconf translation. Thanks to Remus-Gabriel Chelu (Closes: #1038905) Checksums-Sha1: 3835ec7e90676d2d4d565bc73d26e8ebc43f39ce 2429 tzdata_2023c-7.dsc 73bed819e742897640748d2f966e2d970aa25c76 120472 tzdata_2023c-7.debian.tar.xz 84221bbdc07a26396c563de920a8e935521052e8 6901 tzdata_2023c-7_source.buildinfo Checksums-Sha256: 2ad6a5899368119caea23c4929517baa8ad438146434c153ab240795604b434b 2429 tzdata_2023c-7.dsc ab8cc6a17b26909f5d97936bd1b7fababa9162d7194c9d6df6d03d4bb5fdb3a8 120472 tzdata_2023c-7.debian.tar.xz b0d9e1909eebaf27ab8a56a9916caec23ce4b4389aa2072696f1d1182144a2d7 6901 tzdata_2023c-7_source.buildinfo Files: 9666249ab647a1921a306943a909869c 2429 localization required tzdata_2023c-7.dsc 9b8923bb02f6881873ba6bbc36da8291 120472 localization required tzdata_2023c-7.debian.tar.xz c55f4ef5df64333eb723e4840bc72592 6901 localization required tzdata_2023c-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmSi6AAACgkQFZ61xO/I d0wPshAAkWtwXYWHalrQyNsnqfoUePksu682j/7vCbAUUZgnxUIqcv/YEW+jvVGh 2/vybu8ct7YqjbwY3PxOa2bn6uuJNIy516JvkmOYg7yhBCBUFd5T6W9l6+xP6JN5 1LMwQH0ddac4MsK+yG8NmE+rFTGGcXhFF23qfvgPwbzl5gPI/UFRV+795vFCK8ll 6I6hKCOEwXY5cYMuOXj7JOQrSZyJ9LrOXnkxyGxWyepBF64F1CCFdFxsmrGJIU2X Qr4bn5T/E4PaKF+Z/y0fiTp6/6vtRtGd0fQ6YP2VqI5ZDEZxStxiJyeV4ehMEyb/ T57KmAhNOfh0lSRVzLRVc9jgxHY6YPPwg7kz0eRvgjHsEERdEQ9YAhSR4WY4TVxM ZGpGgoSt6sN35F+xdSnGYtwCQP4SbwFX0U6ULUuq1SGWw0ILkzP9wkpxuN0zrnoO beFKunW/nV3cvs/opobzoKxW+UW/SltLiIvBFK0jZrRXOkK0DcSAwsXbbwwdviWB 1brm1pc553u4HUgBdYY/aI/wY9X7jpNMO/dKoMkUjhIqg1zhDeXnSgvFBdCRlhL6 /WuHRdnXI6zWekgPy67A7It+f4+3Vpf42zR8cX3yWtyv3MO3KLvsEj2Y0DQ5m4uI 1N7RPigHzlvMXjuhhi6qBc22zTeMlywt5lcLCO1/zGVwRO6HJD4= =WbHT -END PGP SIGNATURE End Message ---
tzdata_2023c-7_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Jul 2023 17:18:18 +0200 Source: tzdata Built-For-Profiles: noudeb Architecture: source Version: 2023c-7 Distribution: unstable Urgency: medium Maintainer: GNU Libc Maintainers Changed-By: Benjamin Drung Closes: 1038905 Changes: tzdata (2023c-7) unstable; urgency=medium . * Update Romanian debconf translation. Thanks to Remus-Gabriel Chelu (Closes: #1038905) Checksums-Sha1: 3835ec7e90676d2d4d565bc73d26e8ebc43f39ce 2429 tzdata_2023c-7.dsc 73bed819e742897640748d2f966e2d970aa25c76 120472 tzdata_2023c-7.debian.tar.xz 84221bbdc07a26396c563de920a8e935521052e8 6901 tzdata_2023c-7_source.buildinfo Checksums-Sha256: 2ad6a5899368119caea23c4929517baa8ad438146434c153ab240795604b434b 2429 tzdata_2023c-7.dsc ab8cc6a17b26909f5d97936bd1b7fababa9162d7194c9d6df6d03d4bb5fdb3a8 120472 tzdata_2023c-7.debian.tar.xz b0d9e1909eebaf27ab8a56a9916caec23ce4b4389aa2072696f1d1182144a2d7 6901 tzdata_2023c-7_source.buildinfo Files: 9666249ab647a1921a306943a909869c 2429 localization required tzdata_2023c-7.dsc 9b8923bb02f6881873ba6bbc36da8291 120472 localization required tzdata_2023c-7.debian.tar.xz c55f4ef5df64333eb723e4840bc72592 6901 localization required tzdata_2023c-7_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEpi0s+9ULm1vzYNVLFZ61xO/Id0wFAmSi6AAACgkQFZ61xO/I d0wPshAAkWtwXYWHalrQyNsnqfoUePksu682j/7vCbAUUZgnxUIqcv/YEW+jvVGh 2/vybu8ct7YqjbwY3PxOa2bn6uuJNIy516JvkmOYg7yhBCBUFd5T6W9l6+xP6JN5 1LMwQH0ddac4MsK+yG8NmE+rFTGGcXhFF23qfvgPwbzl5gPI/UFRV+795vFCK8ll 6I6hKCOEwXY5cYMuOXj7JOQrSZyJ9LrOXnkxyGxWyepBF64F1CCFdFxsmrGJIU2X Qr4bn5T/E4PaKF+Z/y0fiTp6/6vtRtGd0fQ6YP2VqI5ZDEZxStxiJyeV4ehMEyb/ T57KmAhNOfh0lSRVzLRVc9jgxHY6YPPwg7kz0eRvgjHsEERdEQ9YAhSR4WY4TVxM ZGpGgoSt6sN35F+xdSnGYtwCQP4SbwFX0U6ULUuq1SGWw0ILkzP9wkpxuN0zrnoO beFKunW/nV3cvs/opobzoKxW+UW/SltLiIvBFK0jZrRXOkK0DcSAwsXbbwwdviWB 1brm1pc553u4HUgBdYY/aI/wY9X7jpNMO/dKoMkUjhIqg1zhDeXnSgvFBdCRlhL6 /WuHRdnXI6zWekgPy67A7It+f4+3Vpf42zR8cX3yWtyv3MO3KLvsEj2Y0DQ5m4uI 1N7RPigHzlvMXjuhhi6qBc22zTeMlywt5lcLCO1/zGVwRO6HJD4= =WbHT -END PGP SIGNATURE-
Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)
Hi, On 2023-07-03 14:27, Antonio wrote: > I carried out further tests, until I replicated the problem on a virtual > machine. > > Then I compared the plasma configuration subdir with a functioning version > (obtained experimentally, resetting the arrangement of the desktop and > windows, from default breeze theme). > > The difference that determines the problem is in the > "~/.config/plasma-org.kde.plasma.desktop-appletsrc", section > "[Screenmapping]". > > I noticed that "itemsondisabledscreens" and "screenmapping" items have an > excessive line length. > > LENGTH LINE > BYTES FIRST 200 chars > 82 --- ok-plasma-org.kde.plasma.desktop-appletsrc 2023-07-03 > 13:26:44.894 > 83 +++ bad-plasma-org.kde.plasma.desktop-appletsrc 2023-07-03 > 12:35:57.69 > 16 [ScreenMapping] > 24 -itemsOnDisabledScreens= > 392 > -screenMapping=desktop:/4.png,0,71c04f84-b363-4dca-a9a8-671fbb033f34,d... > 14110 > +itemsOnDisabledScreens=2,19c9821c-6bd3-4d27-b17a-1e325203a1fc,1,deskt... > 3994359 > +screenMapping=desktop:/safekernel-bk110323.01-rel6.1.18/build/include... > > This was also noted from the file size: > > Bad: > -rw--- 1 root root 37K Jul 3 13:43 > ~/.config/plasma-org.kde.plasma.desktop-appletsrc > > Good: > -rw--- 1 root root 12549 3 lug 13.47 > ~/.config/plasma-org.kde.plasma.desktop-appletsrc > > If I remove the entire section, everything works well. Thanks a lot for investigating. With that details, I was able to reproduce the issue in a VM. > I don't know why, but these lines have elongated dramatically. Perhaps the > processes that manage them do not control the maximum length of the lines > ... > > With the previous version of Libc this problem had never occurred, even in > the presence of these lines; while with the new version he came out. It's not clear to me either what's the issue. So far I have just found that the virtual memory allocation of plasmashell is ~11GB with glibc 2.37 vs ~2GB with glibc 2.36. In both cases the resident memory is around 350MB. This higher virtual memory allocation seems to cause the clone syscall to fail with -ENOMEM. > However, now the problem seems to have solved. Yes, it's great that you have found a workaround. Given that, I don't think it warrants blocking the migration of glibc 2.37 to testing, but I'll continue investigating to better understand if it could have other side effects. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)
Hi, On 2023-07-03 22:15, Aurelien Jarno wrote: > It's not clear to me either what's the issue. So far I have just found > that the virtual memory allocation of plasmashell is ~11GB with glibc > 2.37 vs ~2GB with glibc 2.36. In both cases the resident memory is > around 350MB. This higher virtual memory allocation seems to cause the > clone syscall to fail with -ENOMEM. > > > However, now the problem seems to have solved. > > Yes, it's great that you have found a workaround. Given that, I don't > think it warrants blocking the migration of glibc 2.37 to testing, but > I'll continue investigating to better understand if it could have other > side effects. The issue is due to this upstream commit: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f4f2ca1509288f6f780af50659693a89949e7e46 Other possible workarounds are: - defining the GLIBC_TUNABLES environment variable to "glibc.malloc.trim_threshold=128" - changing the kernelvm.overcommit_memory parameter to 1 with "sysctl vm.overcommit_memory=1" Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net