Bug#1068339: gnome-terminal: Regression - long running process will eventually block when terminal is not visible
Hi, I am not sure why I did not receive the followup e-mail from 2024-04-04. Shouldn't it automatically have been sent to me as the original reporter? Just today I eventually found the answer by accident and indeed, it seems to be the same bug. I can also confirm that the problem does not appear anymore with this package: ii libvte-2.91-0:amd64 0.75.92-1amd64Terminal emulator widget for GTK+ 3.0 - runtime files So the bug can be closed. Thanks! Detlev
Bug#1068339: gnome-terminal: Regression - long running process will eventually block when terminal is not visible
Package: gnome-terminal Version: 3.51.90-1 Severity: normal Occasionally I run ffmpeg to transcode videos and this can take up to an hour. With the latest gnome-terminal, this long-running process gets stopped when the terminal is not visible. This can be because the frame shows another tab or because the window is minimized and thus not visible. Using strace I found that ffmpeg is blocked on outputting its progress report. These are the final lines of strace output (filtered for write), before ffmpeg is suspended: write(2, "frame=44221 fps= 12 q=31.5 size= 358656kB time=00:30:45.83 bitrate=1591.8kbits/s speed=0.503x\r", 99) = 99 write(2, "frame=44228 fps= 12 q=31.2 size= 358656kB time=00:30:46.13 bitrate=1591.5kbits/s speed=0.503x\r", 99) = 99 write(2, "frame=44235 fps= 12 q=29.0 size= 358656kB time=00:30:46.43 bitrate=1591.2kbits/s speed=0.503x\r", 99) = 99 write(2, "frame=44243 fps= 12 q=29.1 size= 358656kB time=00:30:46.75 bitrate=1591.0kbits/s speed=0.503x\r", 99 As can be seen, the write call blocks (it does not finish) and ffmpeg is suspended. Bringing the tab to the foreground will resume processing and the output. Trying to reproduce this without ffmpeg, I came up with this little bash one- liner: i=0 ; while true ; do echo -e "Some counter $i" ; sleep .5 ; i=$(expr $i + 1) ; if [ $(( $i % 10 )) == 0 ] ; then echo -ne "\a" ; fi ; done This will beep every 5 seconds, so we know when the loop is still running fine. Just start it in the terminal and then minimize the terminal (switching to other tabs seem not to be a problem for this recipe). The beeps will stop immediately. After waiting a little while and refocusing the window, I see that the counter catches up to the correct value in regard to its start time, but that the output was not consumed anymore. Probably in this case, one needs to wait longer until a buffer fills up and then finally stops the shell loop. I guess this is what is happening with the ffmpeg process. But the test case should be good enough, as xterm running this one-liner continues to beep all the time, no matter if the terminal is minimized or not. As I did not have this problem previously, I believe it is a regression that has entered Debian Trixie in the last few weeks / months. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-terminal depends on: ii dbus-user-session [default-dbus-session-bus] 1.14.10-4 ii dbus-x11 [dbus-session-bus] 1.14.10-4 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b1 ii gnome-terminal-data 3.51.90-1 ii gsettings-desktop-schemas 46.0-1 ii libatk1.0-0 2.50.0-1+b1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libglib2.0-0 2.78.4-1 ii libgtk-3-03.24.41-1 ii libhandy-1-0 1.8.3-1 ii libpango-1.0-01.52.0+ds-1 ii libstdc++614-20240201-3 ii libuuid1 2.39.3-6 ii libvte-2.91-0 0.75.91-2 ii libx11-6 2:1.8.7-1 Versions of packages gnome-terminal recommends: ii gvfs 1.53.90-2 ii nautilus-extension-gnome-terminal 3.51.90-1 ii yelp 42.2-1+b1 gnome-terminal suggests no packages. -- no debconf information
Bug#1028329: padsp: LD_PRELOAD not set correctly
Package: pulseaudio-utils Version: 16.1+dfsg1-2+b1 Severity: important Hi, the /usr/bin/padsp script does not correctly set LD_PRELOAD because the script looks broken. Lines 76-80: if [ x"$LD_PRELOAD" = x ] ; then LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" else LD_PRELOAD="$LD_PRELOAD /usr/\\$$LIB/pulseaudio/libpulsedsp.so" fi The "\\$$LIB" evaluates in sh to a backslash followed by the pid of the shell. This of course does not work: dzu@krikkit:~$ padsp scratch ERROR: ld.so: object '/usr/\80625LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/usr/\80625LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/usr/\80625LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. Executing: /usr/lib/squeak/4.10.2.2614+20120917~dfsg/squeakvm -encoding UTF-8 -vm-display-x11 -plugins /usr/lib/scratch/plugins/:/usr/lib/squeak/4.10.2.2614+20120917~dfsg/ /usr/share/scratch/Scratch.image ERROR: ld.so: object '/usr/\80625LIB/pulseaudio/libpulsedsp.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. dzu@krikkit:~$ -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pulseaudio-utils depends on: ii libc62.36-7 ii libpulse016.1+dfsg1-2+b1 ii libpulsedsp 16.1+dfsg1-2+b1 ii libsndfile1 1.2.0-1 ii libx11-6 2:1.8.3-3 ii libx11-xcb1 2:1.8.3-3 ii libxcb1 1.15-1 pulseaudio-utils recommends no packages. Versions of packages pulseaudio-utils suggests: ii avahi-daemon 0.8-6+b1 ii pulseaudio16.1+dfsg1-2+b1 -- no debconf information
Bug#1007255: khal: Emits warnings about deprecated localize tz method
Package: khal Version: 1:0.10.4~ds-4 Followup-For: Bug #1007255 So I finally also ran into this problem. Upstream has a lot of issues around the timezone warnings, but I especially looked at this one: https://github.com/pimutils/khal/issues/1092 So it seems upstream has fixed the problem and indeed installing khal via pip gives me a version 0.10.6.dev105+g5191ee8 running without problems: dzu@krikkit:/opt/src/git/khal (master)$ pip install git+https://github.com/pimutils/khal Defaulting to user installation because normal site-packages is not writeable Collecting git+https://github.com/pimutils/khal Cloning https://github.com/pimutils/khal to /tmp/pip-req-build-sthm81rz Running command git clone --filter=blob:none --quiet https://github.com/pimutils/khal /tmp/pip-req-build-sthm81rz Resolved https://github.com/pimutils/khal to commit 5191ee88456b004d1d9d415045d57259ac6c03c8 [] Successfully built khal Installing collected packages: khal Successfully installed khal-0.10.6.dev105+g5191ee8 dzu@krikkit:/opt/src/git/khal (master)$ So very likely an updated Debian package will also solve this problem. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages khal depends on: ii python33.10.6-1 ii python3-atomicwrites 1.4.1-1 ii python3-click 8.0.3-1 ii python3-click-log 0.3.2-1 ii python3-configobj 5.0.6-5 ii python3-dateutil 2.8.2-1 ii python3-icalendar 4.0.3-5 ii python3-packaging 21.3-1.1 ii python3-pkg-resources 65.5.0-1 ii python3-tz 2022.6-1 ii python3-tzlocal4.2-1 ii python3-urwid 2.1.2-2+b2 ii python3-xdg0.27-3 Versions of packages khal recommends: ii python3-setproctitle 1.3.1-1+b1 Versions of packages khal suggests: pn khal-doc -- no debconf information
Bug#1024146: ocrmypdf: incompatible with ghostscript 10
Package: ocrmypdf Version: 13.7.0+dfsg-1 Followup-For: Bug #1023273 I also see that ocrmypdf does not work correctly with ghostscript 10.0. From the github page, it became clear that this little patch works around the problem, so you ocrmypdf can be used after applying the patch as is. This is of course only a stop gap solution but until newer ocrmypdf versions arise it may help people looking for a way to quickly make ocrmypdf work again. Best wishes Detlev -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ocrmypdf depends on: ii ghostscript 10.0.0~dfsg-6 ii icc-profiles-free 2.0.1+dfsg-1.1 ii python3 3.10.6-1 ii python3-coloredlogs 15.0.1-1 ii python3-img2pdf 0.4.4-3 ii python3-importlib-metadata 4.12.0-1 ii python3-packaging 21.3-1.1 ii python3-pdfminer20220319+dfsg-1 ii python3-pikepdf 6.0.0+dfsg-1 ii python3-pil 9.2.0-1.1+b1 ii python3-pkg-resources 65.5.0-1 ii python3-pluggy 1.0.0+repack-1 ii python3-reportlab 3.6.11-1 ii python3-tqdm4.64.0-2 ii python3-typing-extensions 4.3.0-2 ii tesseract-ocr 5.1.0-2+b1 ii zlib1g 1:1.2.11.dfsg-4.1 Versions of packages ocrmypdf recommends: ii pngquant 2.13.1-1 ii unpaper 7.0.0-0.1 Versions of packages ocrmypdf suggests: pn img2pdf pn ocrmypdf-doc pn python-watchdog -- no debconf information --- /usr/lib/python3/dist-packages/ocrmypdf/_exec/ghostscript.py.ORIG 2022-11-15 15:44:52.999056901 +0100 +++ /usr/lib/python3/dist-packages/ocrmypdf/_exec/ghostscript.py 2022-11-15 15:51:05.349598489 +0100 @@ -229,7 +229,7 @@ "-dCompatibilityLevel=" + str(pdf_version), "-sDEVICE=pdfwrite", "-dAutoRotatePages=/None", -"-sColorConversionStrategy=" + strategy, +"-dColorConversionStrategy=" + strategy, ] + compression_args + [
Bug#1000498: segfaults in libst-1.0.so with "vertical overview" plugin enabled
Hi, [...] >> Can you get a backtrace from this crash? systemd-coredump is usually the >> easiest way to achieve this. See: https://wiki.debian.org/HowToGetABacktrace > > I installed systemd-coredump and will report after the next occurrence. Ok, it did not take long this time. Relevant info from the log is attached as plain file. Best wishes Detlev Nov 24 23:27:49 krikkit gnome-shell[8849]: [VERTICAL-OVERVIEW] resetting overrides Nov 24 23:27:49 krikkit gnome-shell[8849]: [VERTICAL-OVERVIEW] disabled Nov 24 23:27:50 krikkit gnome-shell[8849]: ../../../gobject/gsignal.c:2732: instance '0x55c5ddf3b7a0' has no handler with id '11187' Nov 24 23:27:50 krikkit gnome-shell[8849]: ../../../gobject/gsignal.c:2732: instance '0x55c5ddf3b7a0' has no handler with id '152621' Nov 24 23:27:50 krikkit gnome-shell[8849]: ../../../gobject/gsignal.c:2732: instance '0x55c5ddf3b7a0' has no handler with id '210464' Nov 24 23:27:50 krikkit gnome-shell[8849]: ../../../gobject/gsignal.c:2732: instance '0x55c5ddf3b7a0' has no handler with id '241740' Nov 24 23:27:50 krikkit gnome-shell[8849]: ../../../gobject/gsignal.c:2732: instance '0x55c5ddf3b7a0' has no handler with id '358176' Nov 24 23:27:50 krikkit kernel: gnome-shell[8849]: segfault at 55c080245279 ip 7fd82aae5b29 sp 7ffddaa67fc0 error 4 in libst-1.0.so[7fd82aac3000+4b000] Nov 24 23:27:50 krikkit kernel: Code: eb 16 0f 1f 80 00 00 00 00 48 83 ed 08 48 39 6c 24 08 0f 84 7f 02 00 00 49 8b 84 24 28 01 00 00 4c 89 ee 4c 8b 3c 28 49 8b 07 <48> 8b 00 48 8b 38 e8 fc 01 fe ff 89 c3 85 c0 75 ce 4d 8b 7f 08 c7 Nov 24 23:27:50 krikkit systemd[1]: Created slice Slice /system/systemd-coredump. Nov 24 23:27:50 krikkit systemd[1]: Started Process Core Dump (PID 48932/UID 0). Nov 24 23:27:54 krikkit systemd-coredump[48933]: Process 8849 (gnome-shell) of user 1000 dumped core. Found module linux-vdso.so.1 with build-id: 091a444eee04263f7c695be0b5daf3cfefd69e97 Found module libcanberra-pulse.so with build-id: d5ec366020185d4f0a1fef2dc1f011eb5ad23a49 Found module libpixbufloader-xpm.so with build-id: b90ec749c16cc7c75e5ae330eaa7700ebbc3a738 Found module libcanberra-gtk-module.so with build-id: db2ee2b1573456b5975d71da980ecd66f47b571a Found module ISO8859-1.so with build-id: 7fdf0bac49ec033f8775bd720f00b50a08e324e6 Found module libgiognutls.so with build-id: 3f57f0b2efa5bf5a79b3d42677585f2459ff4f1a Found module libgiognomeproxy.so with build-id: 326177be2eb39230d3bf6ba69043749f76da1894 Found module libgnome-menu-3.so.0 with build-id: 303c22fd5fe12056f8497c92e18d9c2f15919041 Found module libgioremote-volume-monitor.so with build-id: c2d32acffbc1b017ce8e7a4126bdadb6e044a16b Found module libcrypt.so.1 with build-id: 7c145c0b7c666def24eefa0f87a8086d9a5040c1 Found module libaccountsservice.so.0 with build-id: fa55673675e3934b3a49318ffa924764db4da9d8 Found module libtirpc.so.3 with build-id: d102dc735601c274b7f9f1a10119113201a31621 Found module libnsl.so.2 with build-id: d7e4e187c5d3d36dc8386646d8d02910f2664a85 Found module libopus.so.0 with build-id: b1d12149ecfa4da848f8d65e0c5030d92719efae Found module libvorbisenc.so.2 with build-id: 15116f34e1cc88f88c13d4e6ce5aab9a05c2ad55 Found module libFLAC.so.8 with build-id: 40a64de55001157af9400854429cca51710ee571 Found module libwrap.so.0 with build-id: 7d8e1fb1fcb296405159bce34a01e39141261f4e Found module libasyncns.so.0 with build-id: c90de2251e2576e54fba59aae7af6334c4899939 Found module libsndfile.so.1 with build-id: d9c760d5e9fb778f7b03a199d024ab496e9771a1 Found module libpulsecommon-15.0.so with build-id: 4c6a0c253842fcfd74638fda9ca04111c2d4e87f Found module libpulse-mainloop-glib.so.0 with build-id: 0a11a3d83aec7346717298cec6e9d4bc8b0f25f2 Found module libpulse.so.0 with build-id: d2c00698dd7d8990dbb80d29cc12c00a883d298a Found module
Bug#1000498: segfaults in libst-1.0.so with "vertical overview" plugin enabled
Hi Simon, thanks for the quick reply! > On Wed, 24 Nov 2021 at 10:50:29 +0100, Detlev Zundel wrote: >> Having installed the "vertical overview" package, I experience segfaults in >> gnome-shell killing the whole session. I do think the addon is related as >> log >> messages precede the segfaults. > > Is this reproducible if you disable the extension? The crashes are not that frequent - sometimes it takes multiple days before another crash so I only started seeing this relation while collecting the data for the bug report. But now that I think of it, I did not experience segfaults before enabling the addon. So I am pretty sure but not 100%... > Did you get this extension from Debian or from extensions.gnome.org? I installed it from extensions.gnome.org and just checked that I do not see it packaged for Debian bookworm. > If an extension is causing a crash, there is usually not much that > gnome-shell can do about it. Extensions work by "monkey-patching" > the gnome-shell code, and have just as much control over execution as > gnome-shell does. > >> Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: >> instance '0x55db198ddf00' has no handler with id '10990' > > This suggests that something (presumably the vertical overview extension) > is not keeping track of its signal handler IDs correctly. > >> Nov 17 17:42:40 krikkit kernel: gnome-shell[2918]: segfault at 55de45d1f627 >> ip >> 7f39f4900b29 sp 7ffd73fdd360 error 4 in >> libst-1.0.so[7f39f48de000+4b000] > > Can you get a backtrace from this crash? systemd-coredump is usually the > easiest way to achieve this. See: https://wiki.debian.org/HowToGetABacktrace I installed systemd-coredump and will report after the next occurrence. Thanks Detlev
Bug#1000498: segfaults in libst-1.0.so with "vertical overview" plugin enabled
Package: gnome-shell Version: 41.1-1 Severity: important Having installed the "vertical overview" package, I experience segfaults in gnome-shell killing the whole session. I do think the addon is related as log messages precede the segfaults. Here are three logs for such incidents: Nov 17 17:42:40 krikkit gnome-shell[2918]: [VERTICAL-OVERVIEW] resetting overrides Nov 17 17:42:40 krikkit gnome-shell[2918]: [VERTICAL-OVERVIEW] disabled Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '10990' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '198347' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '461460' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '535503' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '570133' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '709185' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '880062' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '955234' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '1192322' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '1320914' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '1376170' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '2204841' Nov 17 17:42:40 krikkit gnome-shell[2918]: ../../../gobject/gsignal.c:2732: instance '0x55db198ddf00' has no handler with id '2232787' Nov 17 17:42:40 krikkit kernel: gnome-shell[2918]: segfault at 55de45d1f627 ip 7f39f4900b29 sp 7ffd73fdd360 error 4 in libst-1.0.so[7f39f48de000+4b000] Nov 24 02:13:47 krikkit gnome-shell[1310949]: [VERTICAL-OVERVIEW] resetting overrides Nov 24 02:13:47 krikkit gnome-shell[1310949]: [VERTICAL-OVERVIEW] disabled Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '11170' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '61914' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '186568' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '474494' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '532482' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '557261' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '759423' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '785118' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '977619' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '1149827' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '1358899' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '1449481' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '1968145' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '2031854' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '2091418' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '2266819' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '2487659' Nov 24 02:13:47 krikkit gnome-shell[1310949]: ../../../gobject/gsignal.c:2732: instance '0x563600b6ab00' has no handler with id '2655840' Nov 24
Bug#998799: linux-image-5.14.0-4-amd64: Regression causing graphics slowness (`amdgpu: failed to write reg`)
Package: src:linux Version: 5.14.16-1 Followup-For: Bug #998799 Just tested the new kernel image on my AMD Ryzen 5 2400G and I see the same problem. Initially I thought the system was dead due to the long delays introduced in the boot process. Here are the relevant lines from the kernel log: dzu@krikkit:~$ journalctl -b-1 | grep amdgpu | tail -8 Nov 16 09:24:22 krikkit gnome-shell[1454]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting. Nov 16 09:24:43 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6 Nov 16 09:25:03 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706 Nov 16 09:25:23 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6 Nov 16 09:25:43 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706 Nov 16 09:25:43 krikkit gnome-shell[1454]: Disabling DMA buffer screen sharing for driver 'amdgpu'. Nov 16 09:26:05 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 28b4 wait reg 28c6 Nov 16 09:26:25 krikkit kernel: amdgpu :08:00.0: amdgpu: failed to write reg 1a6f4 wait reg 1a706 dzu@krikkit:~$ Best wishes Detlev -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 5603 board_vendor: ASUSTeK COMPUTER INC. board_name: PRIME B350M-A board_version: Rev X.0x ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex [1022:15d0] Subsystem: ASUSTeK Computer Inc. PRIME B450M-A Motherboard [1043:876b] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge [1022:1452] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus B [1022:15dc] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 01:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset SATA Controller [1022:43b7] (rev 02) (prog-if 01 [AHCI 1.0]) Subsystem: ASMedia Technology Inc. 300 Series Chipset SATA Controller [1b21:1062] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 01:00.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:43b2] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in
Bug#992581: vdirsyncer: Bug in systemd unit file results in continuous restarts when encountering problems in the run
Package: vdirsyncer Version: 0.16.8-2 Severity: normal Hi, I have acticated the provided systemd config to run vdirsyncer as a user systemd timer: dzu@krikkit:~$ systemctl --user cat vdirsyncer.timer # /usr/lib/systemd/user/vdirsyncer.timer [Unit] Description=Synchronize vdirs [Timer] OnBootSec=5m OnUnitActiveSec=15m AccuracySec=5m [Install] WantedBy=timers.target dzu@krikkit:~$ This uses the vdirsyncer.service file in /usr/lib/systemd/user/vdirsyncer.service provided by the package without any overrides. The setup ran fine until the Nextcloud server it syncs against went into maintenance mode. Vsync then reports 503 errors that the server cannot be reached. In the systemd logs I then see that the process exits with status=1/FAILURE and is immediately restarted. This log excerpt shows the good case of running every 20 minutes and then the immediate restarts upon the problem: Aug 10 15:15:10 krikkit systemd[3173042]: vdirsyncer.service: Consumed 2.244s CPU time. Aug 10 15:35:09 krikkit systemd[3173042]: vdirsyncer.service: Succeeded. Aug 10 15:35:09 krikkit systemd[3173042]: vdirsyncer.service: Consumed 2.163s CPU time. Aug 10 15:55:10 krikkit systemd[3173042]: vdirsyncer.service: Succeeded. Aug 10 15:55:10 krikkit systemd[3173042]: vdirsyncer.service: Consumed 2.469s CPU time. Aug 10 16:15:07 krikkit systemd[3173042]: vdirsyncer.service: Main process exited, code=exited, status=1/FAILURE Aug 10 16:15:07 krikkit systemd[3173042]: vdirsyncer.service: Failed with result 'exit-code'. Aug 10 16:15:07 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.744s CPU time. Aug 10 16:15:07 krikkit systemd[3173042]: vdirsyncer.service: Scheduled restart job, restart counter is at 1. Aug 10 16:15:07 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.744s CPU time. Aug 10 16:15:09 krikkit systemd[3173042]: vdirsyncer.service: Main process exited, code=exited, status=1/FAILURE Aug 10 16:15:09 krikkit systemd[3173042]: vdirsyncer.service: Failed with result 'exit-code'. Aug 10 16:15:09 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.674s CPU time. Aug 10 16:15:09 krikkit systemd[3173042]: vdirsyncer.service: Scheduled restart job, restart counter is at 2. Aug 10 16:15:09 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.674s CPU time. Aug 10 16:15:11 krikkit systemd[3173042]: vdirsyncer.service: Main process exited, code=exited, status=1/FAILURE Aug 10 16:15:11 krikkit systemd[3173042]: vdirsyncer.service: Failed with result 'exit-code'. Aug 10 16:15:11 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.550s CPU time. Aug 10 16:15:11 krikkit systemd[3173042]: vdirsyncer.service: Scheduled restart job, restart counter is at 3. Aug 10 16:15:11 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.550s CPU time. Aug 10 16:15:13 krikkit systemd[3173042]: vdirsyncer.service: Main process exited, code=exited, status=1/FAILURE Aug 10 16:15:13 krikkit systemd[3173042]: vdirsyncer.service: Failed with result 'exit-code'. Aug 10 16:15:13 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.473s CPU time. Aug 10 16:15:13 krikkit systemd[3173042]: vdirsyncer.service: Scheduled restart job, restart counter is at 4. Aug 10 16:15:13 krikkit systemd[3173042]: vdirsyncer.service: Consumed 1.473s CPU time. I believe that the "Restart=on-failure" in the unit file is responsible for that behavior. I actually do not understand the intention of this statement for vdirsyncer at all. In the case I showed above, the reruns were "harmless" because the target host was not reachable but I also encountered a situation where vdirsyncer exited after syncing all the sources like this: Aug 10 22:34:09 krikkit vdirsyncer[2202152]: Syncing dzu_contacts/z-app- generated--contactsinteraction--recent Aug 10 22:34:10 krikkit vdirsyncer[2202152]: error: dzu_contacts/z-app- generated--contactsinteraction--recent: Storage "dzu_contacts_remote/z-app- generated--contactsinteraction--recent" was completely emptied. If you want to delete ALL entries on BOTH sides, then use> Aug 10 22:34:13 krikkit vdirsyncer[2202152]: error: 1 out of 14 tasks failed. Aug 10 22:34:13 krikkit systemd[3173042]: vdirsyncer.service: Main process exited, code=exited, status=1/FAILURE Aug 10 22:34:13 krikkit systemd[3173042]: vdirsyncer.service: Failed with result 'exit-code'. Aug 10 22:34:13 krikkit systemd[3173042]: vdirsyncer.service: Consumed 2.244s CPU time. Aug 10 22:34:13 krikkit systemd[3173042]: vdirsyncer.service: Scheduled restart job, restart counter is at 2. Aug 10 22:34:13 krikkit systemd[3173042]: Stopped Synchronize calendars and contacts. Aug 10 22:34:13 krikkit systemd[3173042]: vdirsyncer.service: Consumed 2.244s CPU time. Aug 10 22:34:13 krikkit systemd[3173042]: Started Synchronize calendars and contacts. In this case vdirsyncer was running continuously and produced a lot of network traffic. I was actually only finding this problem because my network provider sent me a traffic warning as vdirsyncer produced ~4GB
Bug#984917: feedgnuplot: dynamic plots (--stream) do not work
Hi Dima, > Hi. Yeah, wayland is almost certainly the cuplrit. If you can talk to > the gnuplot upstream to get it resolved, that'd be awesome. Ok, I'll see what I can do. And thanks for the awesome tool and the outstanding support! Cheers Detlev -- Warning: this comic occasionally contains strong language (which may be unsuit- able for children), unusual humor (which may be unsuitable for adults), and ad- vanced mathematics (which may be unsuitable for liberal-arts majors). /xkcd.org
Bug#984917: feedgnuplot: dynamic plots (--stream) do not work
Hi, [...] > I should have mentioned I only recently switched from GNOME on Xorg to > GNOME on Wayland. I hope it does not make a difference but I wanted to > mention it. Having written this paragraph I just reran the test once again and noticed that the graph gets redrawn when I move the mouse on the desktop so it enters and exits different windows. At those moments in time, the graph gets refreshed. So I can get an updating graph by continuously moving the mouse between my terminal window that I started the command in and the gnuplot window. With this in mind I switched back to GNOME on Xorg and sure enough everything works as expected... So the bug only shows in gnuplot under GNOME on Wayland. It is therefore likely a gnuplot bug instead of a problem in feedgnuplot. Does this make sense? Should I open a bug with gnuplot? Thanks! Detlev -- The 82558 B-step and later generation devices do not maintain a link in D3 if PME is disabled or if the device does not have power. -- Intel documentation
Bug#984917: feedgnuplot: dynamic plots (--stream) do not work
Hi Dima,
> Hi. Notes inline.
Thanks for your quick reply!
>> I cannot get dynamic plots to work on my system.
>
> OK. I suspect this is something on your end, but let's run some
> experiments.
I am 100% sure it is something on my end. The question is if it is my
fault or reproducible on other machines as well ;)
>> while true; do sleep 1; cat /proc/net/dev; done |
>> gawk '/enp6s0/ {if(b) {print $2-b; fflush()} b=$2}' |
>> feedgnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
>>
>> This opens up a gnuplot window but it is not updating every second as
>> it should. The lower left corner seems to be showing a coordinate and
>> this indeed updates every second, but the plot itself does not. From
>> time to time the plot gets redrawn but then again stays fixed.
>
> I can think of several potential causes. First off, let's eliminate X
> issues. Can you please add '--terminal "dumb 80 40"' to the feedgnuplot
> command? If that works properly, you'll see an ascii plot printed onto
> your console every second. Do you see that?
Works like a charm.
>> Doing more diagnosing, I used the --dump switch to see what is being fed into
>> gnuplot and when I manually run gnuplot and paste the fragments into it, it
>> works just fine. It seems to be related with the fact that gnuplot reads the
>> input from the pipe.
>
> Right. The second theory is that it's something related to buffering.
> That command should handle it, but let's see. Try this:
>
> 1. apt install mawk
>
> 2. while true; do sleep 1; cat /proc/net/dev; done |
> mawk -Winteractive '/enp6s0/ {if(b) {print $2-b} b=$2}' |
> feedgnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
> --terminal 'dumb 80 40'
>
> So use "mawk -Winteractive" instead of "gawk", and remove the fflush().
> Does that make any difference?
Nope. Same behaviour. Position in lower left corner updates, graph
does not. Only one update after approximately 8 seconds then again
fixed.
>> Maybe this is related to the gnuplot version in Bullseye?
>
> Maybe, but I doubt it. Please run the two experiments above, and we can
> go from there.
I should have mentioned I only recently switched from GNOME on Xorg to
GNOME on Wayland. I hope it does not make a difference but I wanted to
mention it.
Any other ideas?
Thanks in advance!
Detlev
--
Any fool can write code that a computer can understand. Good
programmers write code that humans can understand.
-- Martin Fowler
Bug#984917: feedgnuplot: dynamic plots (--stream) do not work
Package: feedgnuplot
Version: 1.57-1
Severity: important
Tags: upstream
I cannot get dynamic plots to work on my system. To rule out a user error on
my end,
I quickly limited myself to the example from the manpage (adjusted to my
network interface enp6s0):
while true; do sleep 1; cat /proc/net/dev; done |
gawk '/enp6s0/ {if(b) {print $2-b; fflush()} b=$2}' |
feedgnuplot --lines --stream --xlen 10 --ylabel 'Bytes/sec' --xlabel seconds
This opens up a gnuplot window but it is not updating every second as it
should. The lower left
corner seems to be showing a coordinate and this indeed updates every second,
but the plot itself
does not. From time to time the plot gets redrawn but then again stays fixed.
In order to get more information on the possible culprit, I checked this script
on Ubuntu 18.04 and Debian Buster and on both systems it works fine. Of course
the gnuplot and feedgnuplot versions are different.
I also cloned feedgnuplot from git without any effect, but sure enough the
Bullseye package is only a single commit behind git main and that commit is a
documentation change.
Doing more diagnosing, I used the --dump switch to see what is being fed into
gnuplot and when I manually run gnuplot and paste the fragments into it, it
works just fine. It seems to be related with the fact that gnuplot reads the
input from the pipe.
Maybe this is related to the gnuplot version in Bullseye?
Thanks in advance
Detlev
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages feedgnuplot depends on:
ii gnuplot-x11 [gnuplot-nox] 5.4.1+dfsg1-1
ii liblist-moreutils-perl 0.430-2
ii perl 5.32.1-3
feedgnuplot recommends no packages.
Versions of packages feedgnuplot suggests:
pn vnlog
Bug#960941: ofono-phonesim: Re-add ofono-phonesim as it is updated to use qt5
Hi, so I would also need this package to get my headset working on Debian bullseye, but obviously the installation fails: dzu@krikkit:~$ sudo apt install ofono-phonesim Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libqt5core5a : Breaks: libqtcore4 (< 4:4.8.7+dfsg-20~) but 4:4.8.7+dfsg-18+deb10u1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. dzu@krikkit:~$ So I would really also like to see an updated package to get this working. Thanks in advance Detlev -- Quantum physicists can either know how fast they do it, or where they do it, but not both.
Bug#897975: gdm3: System fails to boot due to GDM restarting constantly.
Package: gdm3 Version: 3.22.3-3+deb9u1 Followup-For: Bug #897975 Dear Maintainer, after recent upgrade, gdm3 also fails to start as for the other reportes. It doesn't even switch to graphical mode and so the few text boot messages stay visible. In contrast to previous reporters, I do not see the "ICELockAuthFile fail" error in my logs. To narrow down problems I enabled debug mode in /etc/gdm3/daemon.conf (as attached) and then gdm3 simply starts. Disabling debug mode makes gdm3 fail again. Funnily enough, the last packages upgraded before the failing boot were pretty innocent: Start-Date: 2018-05-07 14:29:16 Commandline: apt dist-upgrade Requested-By: dzu (1000) Upgrade: linux-libc-dev:amd64 (4.9.82-1+deb9u3, 4.9.88-1), openjdk-8-jre:amd64 (8u162-b12-1~deb9u1, 8u171-b11-1~deb9u1), linux-image-4.9.0-6-amd64:amd64 (4.9.82-1+deb9u3, 4.9.88-1), libmad0:amd64 (0.15.1b-8, 0.15.1b-8+deb9u1), openjdk-8-jre-headless:amd64 (8u162-b12-1~deb9u1, 8u171-b11-1~deb9u1), libsdl- image1.2:amd64 (1.2.12-5+b8, 1.2.12-5+deb9u1), tzdata:amd64 (2018d-0+deb9u1, 2018e-0+deb9u1) End-Date: 2018-05-07 14:30:23 Cheers Detlev -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.43-1 ii adduser 3.115 ii dconf-cli0.26.0-2+b1 ii dconf-gsettings-backend 0.26.0-2+b1 ii debconf [debconf-2.0]1.5.61 ii gir1.2-gdm-1.0 3.22.3-3+deb9u1 ii gnome-session [x-session-manager]3.22.3-1 ii gnome-session-bin3.22.3-1 ii gnome-session-flashback [x-session-manager] 3.22.0-3 ii gnome-settings-daemon3.22.2-2+deb9u2 ii gnome-shell 3.22.3-3 ii gnome-terminal [x-terminal-emulator] 3.22.2-1 ii gsettings-desktop-schemas3.22.0-1 ii libaccountsservice0 0.6.43-1 ii libaudit11:2.6.7-2 ii libc62.24-11+deb9u3 ii libcanberra-gtk3-0 0.30-3 ii libcanberra0 0.30-3 ii libgdk-pixbuf2.0-0 2.36.5-2+deb9u2 ii libgdm1 3.22.3-3+deb9u1 ii libglib2.0-0 2.50.3-2 ii libglib2.0-bin 2.50.3-2 ii libgtk-3-0 3.22.11-1 ii libkeyutils1 1.5.9-9 ii libpam-modules 1.1.8-3.6 ii libpam-runtime 1.1.8-3.6 ii libpam-systemd 232-25+deb9u3 ii libpam0g 1.1.8-3.6 ii librsvg2-common 2.40.16-1+b1 ii libselinux1 2.6-3+b3 ii libsystemd0 232-25+deb9u3 ii libwrap0 7.6.q-26 ii libx11-6 2:1.6.4-3 ii libxau6 1:1.0.8-1 ii libxcb1 1.12-1 ii libxdmcp61:1.1.2-3 ii lsb-base 9.20161125 ii metacity [x-window-manager] 1:3.22.1-1 ii mutter [x-window-manager]3.22.3-2 ii policykit-1 0.105-18 ii ucf 3.0036 ii x11-common 1:7.7+19 ii x11-xserver-utils7.7+7+b1 ii xterm [x-terminal-emulator] 327-2 Versions of packages gdm3 recommends: ii at-spi2-core2.22.0-6+deb9u1 ii desktop-base9.0.2+deb9u1 ii x11-xkb-utils 7.7+3+b1 ii xserver-xephyr 2:1.19.2-1+deb9u2 ii xserver-xorg1:7.7+19 ii zenity 3.22.0-1+b1 Versions of packages gdm3 suggests: ii gnome-orca3.22.2-3 ii libpam-gnome-keyring 3.20.0-3 -- Configuration Files: /etc/gdm3/daemon.conf changed: [daemon] [security] [xdmcp] [chooser] [debug] Enable=true -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: gdm3
Bug#723085: icedove: Fails to start with GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
Detlev Zundel d...@akk.org writes: Package: icedove Version: 10.0.12-1 Severity: important Icedove fails to start up at all after a system upgrade to Jessie: [dzu@deepthought ~][0]$ icedove (process:28515): GLib-CRITICAL **: g_slice_set_config: assertion sys_page_size == 0' failed [dzu@deepthought ~][0]$ Doing a websearch it seems to indicate this to be connected to glib alas there is no other version in Jessie or unstable to try. A proposed workaround of exporting G_SLICE=always-malloc also doesn't help. The problem is also present with icedove 17.0.8-1 from unstable. I cannot reproduce this anymore after a system reboot, so the bug can be closed. Icedove from testing and unstable work again. Sorry for the noise. Detlev -- Deutsches Grundgesetz Artikel 21 Absatz 1: Die Parteien wirken bei der politischen Willensbildung des Volkes mit. Ihre Gründung ist frei. Ihre innere Ordnung muß demokratischen Grundsätzen ent- sprechen. Sie müssen über die Herkunft und Verwendung ihrer Mittel sowie über ihr Vermögen öffentlich Rechenschaft geben. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#723085: icedove: Fails to start with GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
Package: icedove Version: 10.0.12-1 Severity: important Icedove fails to start up at all after a system upgrade to Jessie: [dzu@deepthought ~][0]$ icedove (process:28515): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed [dzu@deepthought ~][0]$ Doing a websearch it seems to indicate this to be connected to glib alas there is no other version in Jessie or unstable to try. A proposed workaround of exporting G_SLICE=always-malloc also doesn't help. The problem is also present with icedove 17.0.8-1 from unstable. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages icedove depends on: ii debianutils 4.4 ii fontconfig2.10.2-2 ii libasound21.0.27.1-2 ii libatk1.0-0 2.8.0-2 ii libc6 2.17-92+b1 ii libcairo2 1.12.14-4 ii libdbus-1-3 1.6.14-1 ii libdbus-glib-1-2 0.100.2-1 ii libevent-2.0-52.0.21-stable-1 ii libffi5 3.0.10-3 ii libfontconfig12.10.2-2 ii libfreetype6 2.4.9-1.1 ii libgcc1 1:4.8.1-2 ii libgdk-pixbuf2.0-02.28.2-1 ii libglib2.0-0 2.36.4-1 ii libgtk2.0-0 2.24.20-1 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8d-1 ii libnspr4 2:4.10-1 ii libnspr4-0d 2:4.10-1 ii libnss3 2:3.15.1-2 ii libnss3-1d2:3.15.1-2 ii libpango1.0-0 1.32.5-5+b1 ii libpixman-1-0 0.30.2-1 ii libsqlite3-0 3.8.0.2-1 ii libstartup-notification0 0.12-3 ii libstdc++64.8.1-2 ii libvpx1 1.2.0-2 ii libx11-6 2:1.6.1-1 ii libxext6 2:1.3.2-1 ii libxrender1 1:0.9.8-1 ii libxt61:1.1.4-1 ii psmisc22.20-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages icedove recommends: ii hunspell-sv-se [hunspell-dictionary] 1.51-1 ii myspell-bg [myspell-dictionary] 4.1-3 ii myspell-ca [myspell-dictionary] 0.20111230b-4 ii myspell-cs [myspell-dictionary] 20040229-5.1 ii myspell-da [myspell-dictionary] 1.6.25-1.1 ii myspell-de-de [myspell-dictionary]20120607-1 ii myspell-en-us [myspell-dictionary]1:3.3.0-4 ii myspell-eo [myspell-dictionary] 2.1.2000.02.25-45 ii myspell-es [myspell-dictionary] 1.11-4 ii myspell-et [myspell-dictionary] 1:20030606-20 ii myspell-fr [myspell-dictionary] 1.4-26 ii myspell-he [myspell-dictionary] 1.2-2 ii myspell-hu [myspell-dictionary] 1.2+repack-2 ii myspell-it [myspell-dictionary] 1:3.3.0-4 ii myspell-ku [myspell-dictionary] 0.20.0-2 ii myspell-lt [myspell-dictionary] 1.2.1-4 ii myspell-lv [myspell-dictionary] 0.9.4-5 ii myspell-nb [myspell-dictionary] 2.0.10-5.1 ii myspell-nl [myspell-dictionary] 1:2.10-1 ii myspell-nn [myspell-dictionary] 2.0.10-5.1 ii myspell-pl [myspell-dictionary] 20130519-1 ii myspell-pt-br [myspell-dictionary]20130317-1 ii myspell-pt-pt [myspell-dictionary]20091013-4 ii myspell-ru [myspell-dictionary] 0.99g5-18 ii myspell-sk [myspell-dictionary] 0.5.5a-2.3 ii myspell-sl [myspell-dictionary] 1.0-5 ii myspell-uk [myspell-dictionary] 1.6.5-2 Versions of packages icedove suggests: ii fonts-lyx 2.0.6-1 ii gconf-service 3.2.6-1 ii libgconf-2-4 3.2.6-1 ii libgssapi-krb5-2 1.11.3+dfsg-3 ii libnotify40.7.6-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703882: at not usable as regular (non-root) user
Package: at Version: 3.1.13-2 Severity: important Dear Maintainer, 'at' currently is not usable as a regular user contradicting the man page. In the regular installation, only /etc/at.deny exists and thus from the man page a user not listed in that file should be able to use at (my user is not listed there). Currently, this does not work however: bash[2]$ atq You do not have permission to use atq. bash[2]$ I started debugging at and it turns out that 'at' cannot even read /etc/at.deny and thus concludes that no user except root should be allowed to use it (seen easily also in strace): bash[2]$ strace -e open atq open(/etc/ld.so.cache, O_RDONLY) = 4 open(/lib/x86_64-linux-gnu/libc.so.6, O_RDONLY) = 4 open(/etc/nsswitch.conf, O_RDONLY)= 4 open(/etc/ld.so.cache, O_RDONLY) = 4 open(/lib/x86_64-linux-gnu/libnss_compat.so.2, O_RDONLY) = 4 open(/lib/x86_64-linux-gnu/libnsl.so.1, O_RDONLY) = 4 open(/etc/ld.so.cache, O_RDONLY) = 4 open(/lib/x86_64-linux-gnu/libnss_nis.so.2, O_RDONLY) = 4 open(/lib/x86_64-linux-gnu/libnss_files.so.2, O_RDONLY) = 4 open(/etc/passwd, O_RDONLY|O_CLOEXEC) = 4 open(/etc/group, O_RDONLY|O_CLOEXEC) = 4 open(/etc/passwd, O_RDONLY|O_CLOEXEC) = 4 open(/etc/at.allow, O_RDONLY) = -1 ENOENT (No such file or directory) open(/etc/at.deny, O_RDONLY) = -1 EACCES (Permission denied) You do not have permission to use atq. bash[2]$ The installed rights confirm this: bash[2]$ ls -l /etc/at.deny -rw-r-. 1 root bin 144 Nov 30 2009 /etc/at.deny bash[2]$ As a quick test, I added read rights for all other users, but also with no success: bash[2]$ sudo chmod o+r /etc/at.deny bash[2]$ atq Cannot change to /var/spool/cron/atjobs: Permission denied bash[2]$ At this point I stop as I'm not sure how this is supposed to work in the first place. I would really appreciate if we can fix things up. Let me know if I can test something. Thanks Detlev -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages at depends on: ii libc6 2.13-37 ii libpam-runtime 1.1.3-7.1 ii libpam0g1.1.3-7.1 ii lsb-base4.1+Debian8 Versions of packages at recommends: ii exim4-daemon-light [mail-transport-agent] 4.80-7 at suggests no packages. -- Configuration Files: /etc/at.deny [Errno 13] Permission denied: u'/etc/at.deny' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703882: at not usable as regular (non-root) user
Hello Ansgar, On 03/25/2013 11:19, Detlev Zundel wrote: I started debugging at and it turns out that 'at' cannot even read /etc/at.deny and thus concludes that no user except root should be allowed to use it (seen easily also in strace): bash[2]$ strace -e open atq [...] open(/etc/at.deny, O_RDONLY) = -1 EACCES (Permission denied) You do not have permission to use atq. I wouldn't expect strace to work on suid binaries. Ah, you're right there of course. The first instance was seen with gdb on a local build at however. Reproducing it with strace was only meant to be easier to show than copying a gdb transcript... The installed rights confirm this: bash[2]$ ls -l /etc/at.deny -rw-r-. 1 root bin 144 Nov 30 2009 /etc/at.deny Why does the file belong to the bin group on your system? It should belong to daemon. To be honest, I have no clue. To this day I cannot remember meddling with at at all, so I cannot answer this question. It does so in the binary package: $ dpkg-deb -c at_3.1.13-2_amd64.deb | grep /etc/at.deny -rw-r- root/daemon 144 2012-06-09 13:46 ./etc/at.deny Please also include the permissions of /var/spool/cron/at* and /usr/bin/at if there are still problems. Ah, your indication that there maybe consistency issues prompted me to purge and reinstall 'at' and everything now works for me. Unfortunately this also means that I do not know where the original problems came from but very likely this would have been very hard to reconstruct anyway. So thanks for the quick help and please go ahead and close the bug. Best wishes Detlev -- Oh, didn't you know, the Lord did the original programming of the universe in COBOL. - That's why the world is the evil work of Satan. A true divine being would have used Scheme. - And, if so, Jesus would have been crucified on a big lambda symbol. -- K. Chafin, K. Schilling D. Hanley, on comp.lang.lisp -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703882: at not usable as regular (non-root) user
Hi Steve, On Mon, Mar 25, 2013 at 11:19:16AM +0100, Detlev Zundel wrote: I started debugging at and it turns out that 'at' cannot even read /etc/at.deny and thus concludes that no user except root should be allowed to use it (seen easily also in strace): bash[2]$ strace -e open atq Hi Detlev, atq is setuid and setguid, but those flags are ignored when running under strace or gdb. Thanks for also pointing out my user error ;) As I wrote in my answer to Ansgar already, the strace output was only meant to demonstrate what I perceived as the problem more concisely. The transcript of the changed behaviour after adding read rights should be enough to prove that it was a real problem during regular runs also - obviously it wasn't the only problem. strace's -u flag documents how to get an accurate trace. Thanks for the tip - I wasn't aware of this option before. Thanks Detlev -- The Speedo3 is very similar to other Intel network chips, that is to say apparently designed on a different planet. -- drivers/net/eepro100.c in Linux source -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: d...@denx.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665832: gnuplot: Crashes with Segmentation fault on every command
Package: gnuplot Version: 4.6.0-1 Followup-For: Bug #665832 Hi, as an additional data point, I see exactly the same behaviour. Cheers Detlev -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnuplot depends on: ii gnuplot-nox 4.6.0-1 ii gnuplot-x11 4.6.0-1 gnuplot recommends no packages. Versions of packages gnuplot suggests: pn gnuplot-doc none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627453: Problem still persists
Hi, as an additional data point, I experienced the same problem, but due to the report of Ulrik, I was also able to rebuild the library locally and proceed with actually using QLandkarteGT. Can this problem please be fixed in Debian itself? Can I help in any way to make this happen? Thanks! Detlev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#479096: [xbattbar-acpi] No battery detected with kernel 2.6.25
Hi,
suffering from the same problems, I hacked up a working combination of
libacpi + yacpi (which I use) for 2.6.25. Unfortunately the patch
needs to change the API as I really needed to get to the
global-sysstyle.
So when applying these patches, the so-number needs to be bumped. In
the README I see that there is another change outstanding
neccessitating such an increment, namely exporting the acpi version in
the structure. Maybe this can be done together?
Also the new version is not backwards compatible, i.e. it simply
replaces the file names by the new versions. It should be easy
however to add probes for both versions so that we are backward
compatible. I was simply not sure how to do that in a suiting elegant
way ;)
Cheers
Detlev
diff -ur orig/libacpi-0.2/libacpi.c libacpi-0.2/libacpi.c
--- orig/libacpi-0.2/libacpi.c 2008-06-09 18:56:56.0 +0200
+++ libacpi-0.2/libacpi.c 2008-06-08 18:23:33.0 +0200
@@ -17,7 +17,7 @@
static int read_acpi_battinfo(const int num, const int sysstyle);
static int read_acpi_battalarm(const int num, const int sysstyle);
-static int read_acpi_battstate(const int num);
+static int read_acpi_battstate(const int num, const int sysstyle);
static void read_acpi_thermalzones(global_t *globals);
typedef struct {
@@ -195,6 +195,7 @@
snprintf(binfo-alarm_file, MAX_NAME, PROC_ACPI battery/%s/alarm, names[i]);
}
read_acpi_battinfo(i, globals-sysstyle);
+ read_acpi_battstate(i, globals-sysstyle);
read_acpi_battalarm(i, globals-sysstyle);
free(names[i]);
}
@@ -536,17 +537,17 @@
return NOT_PRESENT;
}
- snprintf(sysfile, MAX_NAME, %s/charge_full_design, info-info_file);
+ snprintf(sysfile, MAX_NAME, %s/energy_full_design, info-info_file);
if((buf = get_acpi_content(sysfile)) == NULL)
return NOT_SUPPORTED;
info-design_cap = strtol(buf, NULL, 10);
- snprintf(sysfile, MAX_NAME, %s/charge_full, info-info_file);
+ snprintf(sysfile, MAX_NAME, %s/energy_full, info-info_file);
if((buf = get_acpi_content(sysfile)) == NULL)
return NOT_SUPPORTED;
info-last_full_cap = strtol(buf, NULL, 10);
- snprintf(sysfile, MAX_NAME, %s/charge_now, info-info_file);
+ snprintf(sysfile, MAX_NAME, %s/energy_now, info-info_file);
if((buf = get_acpi_content(sysfile)) == NULL)
return NOT_SUPPORTED;
info-remaining_cap = strtol(buf, NULL, 10);
@@ -610,11 +611,29 @@
/* read information for battery num, return 0 on success or negative values on error */
static int
-read_acpi_battstate(const int num){
+read_acpi_battstate(const int num, const int sysstyle){
char *buf = NULL;
char *tmp = NULL;
battery_t *info = batteries[num];
unsigned int i = 0;
+ char sysfile[MAX_NAME];
+
+ if(sysstyle)
+ {
+ snprintf(sysfile, MAX_NAME, %s/status, info-info_file);
+ if((buf = get_acpi_content(sysfile)) == NULL)
+ return NOT_SUPPORTED;
+ if(!strcmp(buf, Discharging))
+ info-charge_state = C_DISCHARGE;
+ else if(!strcmp(buf, Charging))
+ info-charge_state = C_CHARGE;
+ else if(!strcmp(buf, Full))
+ info-charge_state = C_CHARGED;
+ else
+ info-charge_state = C_NOINFO;
+
+ return SUCCESS;
+ }
if((buf = get_acpi_content(info-state_file)) == NULL)
return NOT_SUPPORTED;
@@ -700,10 +719,10 @@
/* read/refresh information about a given battery num
* returns 0 on SUCCESS, negative values on errors */
int
-read_acpi_batt(const int num){
+read_acpi_batt(const int num, global_t *globals){
if(num MAX_ITEMS) return ITEM_EXCEED;
- read_acpi_battstate(num);
- read_acpi_battalarm(num, 0);
+ read_acpi_battstate(num, globals-sysstyle);
+ read_acpi_battalarm(num, globals-sysstyle);
calc_remain_perc(num);
calc_remain_chargetime(num);
calc_remain_time(num);
diff -ur orig/libacpi-0.2/libacpi.h libacpi-0.2/libacpi.h
--- orig/libacpi-0.2/libacpi.h 2008-06-09 18:56:56.0 +0200
+++ libacpi-0.2/libacpi.h 2008-06-08 15:19:58.0 +0200
@@ -237,7 +237,7 @@
* a struct with it
* @param num number of battery
*/
-int read_acpi_batt(const int num);
+int read_acpi_batt(const int num, global_t *globals);
/**
* Looks up if the ac adapter is plugged in or not
* and sets the values in a struct
diff -ur orig/libacpi-0.2/test-libacpi.c libacpi-0.2/test-libacpi.c
--- orig/libacpi-0.2/test-libacpi.c 2008-06-09 18:56:56.0 +0200
+++ libacpi-0.2/test-libacpi.c 2008-06-08 15:21:44.0 +0200
@@ -43,7 +43,7 @@
for(i=0;iglobal-batt_count;i++){
binfo = batteries[i];
/* read current battery values */
- read_acpi_batt(i);
+ read_acpi_batt(i, global);
if(binfo-present)
{
diff -ur orig/yacpi-3.0/yacpi.c yacpi-3.0/yacpi.c
--- orig/yacpi-3.0/yacpi.c 2007-08-09 18:47:47.0 +0200
+++ yacpi-3.0/yacpi.c 2008-06-08 17:52:27.0 +0200
@@ -362,7 +363,7 @@
binfo = batteries[i];
if(!binfo) return;
/* read current battery values */
- read_acpi_batt(i);
+ read_acpi_batt(i, global);
if(binfo binfo-present){
if(t) printf(| %s = %d%%, binfo-name, binfo-percentage);
