Package: inadyn
Version: 2.10.0-1
$ sudo aptitude install inadyn
[sudo] Passwort für username:
Die folgenden NEUEN Pakete werden zusätzlich installiert:
inadyn libconfuse-common{a} libconfuse2{a}
0 Pakete aktualisiert, 3 zusätzlich installiert, 0 werden entfernt und 4 nicht
aktualisiert.
126 kB
Package: diffutils
Version: 1:3.8-4
Create two directories: empty A and B containing 'e9'$'\033''[H' . Then, from
an xterm:
$ ls A B
A:
B:
'e9'$'\033''[H'
$ diff -r A B
Nur in B: e9
After this prefix of the file name, the cursor jumps to the second line of the
used console from above and the
Package: djview-plugin
Version: 4.11-1
On the current debian 12 stable „bookworm“ with firefox-esr
115.9.1esr-1~deb12u1, we get
$ sudo aptitude install djview-plugin
The following NEW packages will be installed:
djview-plugin iceweasel{a}
Iceweasel 115.9.1esr-1~deb10u1 is a transitional package
Package: firefox-esr
Version: 115.9.0esr-1~deb12u1
Severity: wishlist
In the upstream issue report on this,
https://bugzilla.mozilla.org/show_bug.cgi?id=680385
https://bugzilla.mozilla.org/show_bug.cgi?id=680385, the last statement 38
contains “webp probably compresses just as well if not
Package: fontconfig
Version: 2.14.1-4
Control: affects -1 font-manager
For the purpose of this bug report, let's assume you have two versions of the
same font, say, Courier New (the real name is probably irrelevant, as we only
need the same name):
/usr/share/fonts/truetype/msttcorefonts/cour.ttf
Dear Hilmar,
Thank you for a quick answer. Note that the version of the package NewTX (most
likely, 1.726 (cf. https://ctan.org/pkg/newtx), since all the mentioned bugs
are repaired, whereas it was not the case for a few immediately preceeding
versions) deviates from the version of the file
Thank you! Now all the mentioned bugs seem to be repaired.
How to find out the NewTX version shipped with Debian texlive-fonts-extra?
Running locate newtx | xargs grep -r "1\.726" returns nothing from the
system-wide directories.
(Running tlmgr info newtx as a normal user yields no results, and
ontrol: tags -1 + pending On 08.09.2023 19:43, Al Ma wrote: Hi Al, > Please
upgrade NewTX to 1.726 (dated 2023-08-25). The following two > problems are
resolved there /simultenaously/: > There is no need to send package update
requests. I'm doing package updates on a regulars basis. I
Even three problems are solved there. The third positive aspect of this version
is that now ≗, ≖, blackboard bold (e.g., 픹), ⊛, Hebrew (say, ד) , and ✓ appear
properly; cf. http://tex.stackexchange.com/questions/693396 .
Package: texlive-fonts-extra
Version: 2023.20230613-2
Please upgrade NewTX to 1.726 (dated 2023-08-25). The following two problems
are resolved there simultenaously:
Two letters ij are not combined into the digraph ij; cf.
http://tex.stackexchange.com/questions/652108 . No excessive right-side
retitle 1041494 diffpdf: changes to zoom for small documents (⩽ 19 pages in at
least one file) don't take effect on ↩
thanks
You have to take small documents to reproduce this CLEANLY. Presumably at
least one of the two compared PDF files must have at most 19 pages to reproduce
this cleanly.
Please keep open because the issue is NOT fully resolved; some coloring (bold,
blue) remains unexplained or ill-explained.
Cf. http://github.com/systemd/systemd/issues/28953
http://github.com/systemd/systemd/issues/28953.
However, in the meantime, there has been an update of
https://www.freedesktop.org/software/systemd/man/journalctl.html
https://www.freedesktop.org/software/systemd/man/journalctl.html in this
regard. The update does not fully resolve the issue but is better than nothing.
Package: texlive-plain-generic
Version: 2022.20230122-4
Severity: wishlist
As of now, the following input produces wrong formatting (cf.
http://tex.stackexchange.com/questions/48501
http://tex.stackexchange.com/questions/48501 ) when fed to pdflatex:
\documentclass{standalone}
After having run
System Update (which upgraded IME Software) made by Lenovo and Windows Update
(which upgraded Windows 11 including its drivers) made by Microsoft, I still
see the error messages in the Debian journal. (Some ACPI-related stuff also
appears on the screen during boot, but it's a
Thanks for looking into this. The solid-state–memory device in question is
Samsung SSD 970 EVO 1TB, S/N:…, FW:2B2QEXE7, 1.00 TB. It's no longer sold on
samsung.com but still sold as new on amazon (ASIN B07CGJNLBB; the Web site says
it has been sold there since April 24, 2018). So yes, given the
Package: tracker-extract
Version: 3.4.3-1
Control: affects -1 tracker-miner-fs
In the journal of the currently stable Debian 12 we find a yellow warning
“tracker-extract[…]: Failed to create location for error reports: Keine
Berechtigung”, where “Keine Berechtigung” is German for “no permission”
As for Lenovo T14s I manage, it's of type 20T1 (in particular, not the one you
linked); its BIOS version is 1.26, released 12/14/2022. The firmware revision
is 1.14. No further BIOS upgrade is available for this very laptop as of now.
(A new Intel Management Engine Software for Windows has
I now checked the last machine I manage and saw similar messages having
occurred when unattended-upgrades upgraded linux-image-6.1.0-10-amd64:amd64 and
linux-image-amd64:amd64 from version 6.1.38-1 to version 6.1.38-2. The prefix
of /var/log/kern.log up to the BPF-related messages and slightly
Package: libhpmud0
Version: 3.22.10+dfsg0-2
Control: affects -1 hplip hplip-data colord
In my journal I discovered an error
colord-sane[1000]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
The part “io/hpmud/musb.c 2101: Invalid usb_open: Permission denied” is red.
The message appears
By the way, here's the contents of /etc/resolv.conf (which is a symlink to
/run/NetworkManager/resolv.conf):
# Generated by NetworkManager
search AnonymizedRouterName
nameserver 192.168.2.1
nameserver fe80::1%wlp3s0
wlp3s0 is the logical name of the wireless interface provided by the wireless
Package: avahi-daemon
Version: 0.8-10
In my journal.conf, we see this:
Jul 29 00:10:33 AnonymizedMachineName avahi-daemon[712]: Found user 'avahi'
(UID 107) and group 'avahi' (GID 117).
Jul 29 00:10:33 AnonymizedMachineName avahi-daemon[712]: Successfully dropped
root privileges.
Jul 29 00:10:33
severity 1017988 normal
found 1017988 5.66-1
thanks
Raising severity as this warning concerns more than one user. My journal has
this:
Jul 29 00:10:33 AnonymizedMachineName kernel: Bluetooth: hci0: BCM: firmware
Patch file not found, tried:
Jul 29 00:10:33 AnonymizedMachineName kernel:
Ben, I wonder why you merged #1042237 and #1003965. The BPF messages coincide
in the almost empty lines “[…] BPF:” and coincide up to spacing in “[…] BPF:
Invalid name”. The coincidences seem to end here. Some of the remaining “[…]
BPF: …” lines are similar but, strictly speaking, different.
Package: gdm3
Version: 43.0-3
The machine in question has two graphic chips:
- ASPEED AST2500 64MB built into the motherboard and
- NVIDIA GeForce GTX 1660 Ti PCIe graphics card.
The ASPEED chip (/dev/dri/card0) has only a VGA port; nothing is connected to
this D-SUB port. The NVIDIA card
In the meantime, systemd and udev have been upgraded to version
252.12-1~deb12u1 on a similar (but not identical) computer running Debian 12
stable. There, this message seems to be unconnected to printers (because no
printer is physically attached, and the only network printer is off). The
Dear iwlwifi developers,
I get a yellow warning in the journal: “iwlwifi :b3:00.0: api flags index 2
larger than supported by driver”.
The card:
AX3000 Dual Band PCE-AX3000 Wi-Fi 6 PCI-E Adapter
The preceding journal entries:
Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0:
Ben, thank you for a quick reply! Issue created:
https://gitlab.freedesktop.org/drm/nouveau/-/issues/246
https://gitlab.freedesktop.org/drm/nouveau/-/issues/246. There I wonder: if the
message is purely informational, it probably better really not be yellow (and
thus warn the user because
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Control: affects -1 src:linux smartmontools
In the journal I see a red error message of the form “smartd[…]: Device:
/dev/nvme0, number of Error Log entries increased from 푛 to 푛+1”. I think the
number 푛 increases on each boot. The relevant
Package: linux-image-6.1.0-10-amd64 Version: 6.1.38-1 Control: affects -1
src:linux
In the journal of a computer with motherboard ASUS WS C422 PRO/SE and Intel®
Xeon® W-2235 CPU @ 3.80GHz, 32 GB RAM, ASPEED AST2500 64MB built-in graphics
chip, and NVIDIA GeForce GTX 1660 Ti PCIe graphics card,
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Control: affects -1 src:linux
In the journal I discover the yellow warning “MXM: GUID detected in BIOS”. Is
this a software, a firmware, or a hardware problem? In plain English, what are
we really warned about? What to do to avoid
The warning is still there after upgrading the kernel to
linux-image-6.1.0-10-amd64 version 6.1.38-1. The logs are attached.
Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: enabling
device (0100 -> 0102)
Jul 22 22:35:22 AnonymizedMachineName kernel: [drm] Initialized ast
found 966218 src:linux/6.1.0-10
found 966218 linux/6.1.0-10
found 966218 linux-image-6.1.0-10-amd64/6.1.38-1
found 966218 firmware-iwlwifi/20230210-5
thanks
The errors in the journal still occur by default (i.e., without any options)
with ASUS AX3000 Dual Band PCE-AX3000 Wi-Fi PCI-E Adapter. The
Package: linux-image-6.1.0-10-amd64
Version: 6.1.38-1
Control: affects -1 scr:linux
On an ASUS WS C422 PRO/SE with a Samsung SSD 970 EVO 1TB, I get a yellow kernel
warning in the journal: “nvme nvme0: missing or invalid SUBNQN field.” The
relevant parts of the logs are attached. A software
found 1041503 linux-image-6.1.0-10-amd64/6.1.38-1
thanks
Same warning after kernel upgrade on a different machine (motherboard ASUS WS
C422 PRO/SE):
Jul 22 22:35:22 AnonymizedMachineName kernel: hub 1-0:1.0: USB hub found
Jul 22 22:35:22 AnonymizedMachineName kernel: hub 1-0:1.0: 16 ports
severity 1001286 important
found 1001286 linux/6.1.0-10
found 1001286 linux-image-6.1.0-10-amd64/6.1.38-1
thanks
Same restriction here, namely for two stationary computers with Asus WS C422
PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz (motherboard specification:
severity 1001286 important
thanks
Same restriction here, namely for two stationary computers with Asus WS C422
PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz (motherboard specification:
https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/techspec
I stand corrected – the very last message as of a few minutes ago concerned a
different machine: WS C422 PRO/SE with Intel® Xeon® W-2235 CPU @ 3.80GHz, 32 GB
RAM, ASPEED AST2500 64MB built-in graphics chip, and NVIDIA GeForce GTX 1660 Ti
PCIe graphics card.
found 1041141 6.1.38-1
thanks
After the kernel upgrade, I got a slightly different message in the same vein:
Jul 22 22:35:22 AnonymizedMachineName kernel: Registering PCC driver as Mailbox
controller
Jul 22 22:35:22 AnonymizedMachineName kernel: acpiphp: ACPI Hot Plug PCI
Controller Driver
Michael, thanks for taking a look. Last time I started
/lib/systemd/systemd-timesyncd directly as root from the command line was
several days ago, way before the today upload of the new versions of systemd
and systemd-timesyncd to stable. Back then, /lib/systemd/systemd-timesyncd did
start,
Package: aptitude
Version: 0.8.13-5
Severity: wishlist
Today I wanted to upgrade the pacakge sudo but made a typo:
# aptitude upgrade suo
Couldn't find any package whose name is "suo", but there are 4 packages which
contain "suo" in their name:
golang-github-bmatsuo-lmdb-go-dev festvox-suopuhe-lj
Package: gnome-settings-daemon
Version: 43.0-4
In my journal I see the following warnings:
Jul 20 04:44:36 AnonymizedMachineName gsd-media-keys[1263]: Unable to get
default sink
Jul 20 04:44:36 AnonymizedMachineName gsd-media-keys[1263]: Unable to get
default source
The (hopefully, relevant)
found 1038981 linux-image-6.1.0-10-amd64/6.1.37-1
found 1038981 linux/6.1.0-10
thanks
The same problem exists after the recent kernel upgrade to
linux-image-6.1.0-10-amd64 version 6.1.37-1.
$ uname -r
6.1.0-10-amd64
$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
40
40
40
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
During boot the warning “kernel: usb: port power management may be unreliable”
is printed yellow into the journal (see the attachment). I tried to plug in and
unplug a mouse into all USB-A ports and an iPhone into all USB-C ports of the
In my recollection of Debian 11, even changing a single digit in the Zoom field
led to an immediate redraw, i.e., even before pressing ⏎. So the current
situation is double worse.
As of how it _should_ be, I think that whenever a keyboard is attached, only
hitting [Enter] or moving the cursor
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
In the journal of a laptop Lenovo ThinkPad T14s Gen1, connected to a docking
station ThinkPad Thunderbolt 3 Dock Gen 2/Workstation Dock Gen 2 Type 40 AN
(which is powered by a 135 W AC Adapter ADL135NCC3A) and to a monitor Philips
275B1 via
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
In the journal of a laptop Lenovo ThinkPad T14s Gen1, connected to a docking
station ThinkPad Thunderbolt 3 Dock Gen 2/Workstation Dock Gen 2 Type 40 AN
(which is powered by a 135 W AC Adapter ADL135NCC3A) and to a monitor Philips
275B1 via
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
In the journal I see red lines
firmware_class: See https://wiki.debian.org/Firmware
https://wiki.debian.org/Firmware for information about missing firmware
bluetooth hci0: firmware: failed to load brcm/BCM20702A1-413c-8197.hcd (-2)
bluetooth
Package: systemd-timesyncd
Version: 252.6-1
`systemctl restart systemd-timesyncd` says that the control process exited with
error code. Status says, "Failed at step EXEC spawning
/lib/systemd/systemd-timesyncd: Permission denied".
In the `output of journal -xeu systemd-timesyncd.service` we see
Package: linux-image-6.1.0-9-amd64
Version: 6.1.27-1
Below, I try to cap the frequency for each of my processor cores, but some
cores resists:
# for i in `seq 0 7`; do echo "40">
/sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq && cat
Package: grub2-common
Version: 2.06-13
Severity: wishlist
The file /etc/default/grub contains, among many lines, the following one:
#GRUB_DISABLE_OS_PROBER=false
Both “disable” and “false” contain a negation—we have a double negation here.
For a human brain, a negation (let alone a double one)
Simon, thanks for the extensive reply. > If this isn't implicated in any
user-visible problem, then it's almost > certainly harmless, and definitely not
Severity: important. The main user-visible problem on my computer these days is
that X11 is used instead of Wayland, and the only big action
Package: gnome-shell-extension-pixelsaver
Version: 1.30-1
Severity: grave
Installing and then activating gnome-shell-extension-pixelsaver has no effect.
When the lowest buttom in the attached screenshot is clicked, no visible effect
is observed. In the journallog I see this (up to the anonymized
Package: colord
Version: 1.4.6-2.2
Taking a look at the bootlog obtained from journalctl -b, I discovered a report
of the following failure:
Jun 12 21:41:41 AnonymizedComputerName dbus-daemon[885]: [system] Activating
via systemd: service name='org.freedesktop.ColorManager' unit='colord.service'
Package: wireplumber
Version: 0.4.13-1
While examining the output of journalctl -b, I found the message “Can't find
org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?” first bold and
then yellow:
Jun 12 21:41:41 AnonymizedComputerName systemd[1]: Started user@119.service -
User
Package: gnome-shell
Version: 42.3.1-2
Severity: important
In the journal I've discovered a disturbing segfault:
Mai 25 23:43:55 AnonymizedComputerName dbus-daemon[820]: [system] Successfully
activated service 'org.freedesktop.realmd'
Mai 25 23:43:55 AnonymizedComputerName systemd[1]: Started
Package: tre-agrep
Version: 0.8.0-6+b1
How to reproduce:
1) Download a Windows 11 installation .iso for test purposes
2) run `tre-agrep --color -i -1 Maschineneigenschaft` on this file
3) Observe “Out of memory” although plenty of swap is present.
Log:
$ free -h
total used free
Package: gnome-shell
Version: 42.3.1-2
I discovered (among many others) a “No entry for geolocation” error in the
journal:
Mai 21 22:36:47 AnonymizedComputerName gnome-shell[1063]: Will monitor session
c1 Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Activating
via systemd:
Thanks! First, if the arguments `-' and `--' are absolutely equivalent, there's
no need for parens (which make the stuff inside the parens, well, parenthetic).
Second, pay attention to the consistency of the quotation marks, whichever you
choose. Therefore:
A single argument `--' or `-' stops
Package: bash
Version: 5.1-2+deb11u1
In the man page for bash we see the line,
“-- A -- signals the end of options and disables further option processing. Any
arguments after the -- are treated as filenames and arguments. An argument of -
is equivalent to --.”
I claim that the sentence “Any
Package: gdm3
Version: 3.38.2.1-1
In my journal log I see that an activated service org.freedesktop.systemd1
failed:
Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1164]:
SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mai 17 20:37:18
Package: gnome-shell
Version: 42.3.1-2
In my journal I discovered a message that a saved session file could not be
parsed:
Mai 17 20:03:28 AnonymizedComputerName org.gnome.Shell.desktop[1157]: glamor:
No eglstream capable devices found Mai 17 20:03:28 AnonymizedComputerName
gnome-shell[1049]:
Updating xwayland to version 2:21.1.3-1 removes this particular bug (and
introduces others). So the package containing the program that issues the call
with -initfd must depend on xwayland version ≥ 2:21.1.3-1. I have no idea which
program it is or whether this has been already done upstream.
Package: okular
Version: 4:20.12.3-2
Severity: important
Open a nonempty Postscript file (probably, any would do) with okular. For
example, take the file mwe.ps in the attachment produced by latex mwe && dvips
mwe from mwe.tex containing
Package: evince
Version: 3.38.2-1
Severity: important
Open a nonempty Postscript file (probably, any would do) with evince. For
example, take the file mwe.ps in the attachment produced by latex mwe && dvips
mwe from mwe.tex containing
\documentclass{article}\begin{document}Test\end{document}.
Package: gv
Version: 1:3.7.4-2+b1
Let's create mwe.tex containing
\documentclass{article}
\usepackage[paperwidth=1cm,paperheight=1.25cm,margin=0cm]{geometry}
\pagestyle{empty}
\usepackage{tikz}
\begin{document}\noindent \begin{tikzpicture}
\node[draw](A){};
\node[draw,below of=A]{};
retitle 1017466 Datei … ist ein symbolische Verknüpfung, während Datei … ein
normale leere Datei ist.
severity 1017466 important
thanks
I confirm the bug. The German message when comparing a symlink with a regular
file contains grammatical errors. To reproduce:
$ echo $LANG
de_DE.UTF-8
$ touch f
I noticed now that I had unintentionally omitted the name of a package in my
version list in my original post. It should read: “Here are the versions of
some relevant installed packages: xorg 1:7.7+23, […].”
Simon,
Thank you for a reply. I understand. On the machine in question, libmutter-10-0
in version 42.3-2 is installed. The package libmutter-7-0 is not installed, and
no other libmutters are known to aptitude. At the moment, I cannot risk a full
upgrade from Debian stable to Debian testing
Pardon me; the first line in my previous message should have been a quotation:
“There is no such driver.” It's not my claim but a claim of Timo.
There is no such driver.
If such a driver doesn't exist in the world, then either the message is bogus
and should be changed, or the vendor should be asked to produce the driver.
Package: pipewire
Version: 0.3.56-1
In my journal I get an error message about an inappropriate IOCTL for a device:
Mai 10 22:44:01 AnonymizedComputerName kernel: cx23885: cx23885[0]: registered
device video0 [v4l2]
Mai 10 22:44:01 AnonymizedComputerName kernel: cx23885: cx23885[0]: registered
Package: gnome-shell
Version: 42.3.1-2
In my journal log I see, among other weird stuff, the information that the
option -initfd has not been recognized:
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Boot VGA GPU
/dev/dri/card1 selected as primary
Mai 10 21:01:21
Package: libgl1-mesa-dri
Version: 20.3.5-1
My journal log shows, among other weird stuff, the following error message:
Mai 10 21:01:20 AnonymizedComputerName gnome-shell[1026]: Running GNOME Shell
(using mutter 42.3) as a Wayland display server
Mai 10 21:01:21 AnonymizedComputerName
Package: pulseaudio
Version: 14.2-2
My machine runs Debian stable with several upgraded packages but has no sound
ouput. It's a software issue (because in another operating system in dual boot
mode I get sound output). Here's a (hopefully, relevant) part of the journal
log:
Mai 10 21:01:20
Package: network-manager
Version: 1.30.6-1+deb11u1
While going though the journal log, I found, amoing other weird stuff, that
P2P, whatever it might be, has failed:
Mai 10 21:01:20 AnonymizedComputerName gnome-session[973]:
gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion
You are right, tlp-rdw was removed but not purged, as it turned out. After
puring tlp-rdw, the two error messages are gone. Thanks!
Alma
Package: network-manager
Version: 1.30.6-1+deb11u1
In my journal jog I find, among other weird stuff, this:
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3651] hostname: hostname: using hostnamed
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
Package: gnome-session-bin
Version: 42.0-1
In the journal log I discovered (among other crazy stuff) this:
Mai 10 16:47:36 AnonymizedComputerName tracker-miner-f[1232]: Unable to get XDG
user directory path for special directory Ignoring this location.
Mai 10 16:47:36 AnonymizedComputerName
Package: firmware-iwlwifi
Version: 20210315-3
In the journal log of a machine with the card
AX3000 Dual Band
PCE-AX3000
Wi-Fi 6 PCI-E Adapter
I see this:
Mai 10 16:47:33 AnonymizedMachineName kernel: RAPL PMU: API unit is 2^-32
Joules, 1 fixed counters, 655360 ms ovfl timer
Mai 10 16:47:33
Package: foot
Version: 1.6.4-1
How to reproduce:
1) Create a symlink to an existing file.
2) Create a symlink to a nonexistent file.
3) Issue `ls -lA` or simply `ls` and observe that the two links have the same
color.
We wish that broken symbolic links be represented in a different color, for
Package: texlive-pstricks
Version: 2022.20221123-1
Control: affects -1 ghostscript
Feed mwe.tex containing
\documentclass{article}
\usepackage{pstricks}
\begin{document}
Test
\end{document}
to `latex`, then issue `xdvi mwe` from an xterm under X11+gnome, and finally
observe the visual output
Package: emacs
Version: 1:27.1+1-3.1+deb11u2
1. In gnome, open gnome-characters and emacs.
2. In gnome-characters, find ⋢ (U+22E2) and copy it.
3. Paste it via Ctrl+y to the emacs scratch buffer.
4. Observe that the charater misses a lower bar.
In the attached screenshot, on the right you see the
Package: systemd
Version: 247.3-7+deb11u2
Control: affects -1 + udev
In the output of journalctl -b we see
…
Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-10: new low-speed USB
device number 4 using xhci_hcd
Apr 23 22:30:59 AnonymizedMachineName kernel: sr 5:0:0:0: Attached scsi CD-ROM
sr1
Package: linux-image-5.10.0-21-amd64
Version: 5.10.162-1
Severity: wishlist
In the output of journalctl -b we see this:
…
Apr 23 22:30:59 AnonymizedMachineName kernel: efifb: Truecolor: size=8:8:8:8,
shift=24:16:8:0
Apr 23 22:30:59 AnonymizedMachineName kernel: Console: switching to colour
frame
Thanks. I understand. As packages generally depend on each other on a large
scale, I posted the version of systemd simply to indicate that the bug is not
as old as it might seem from the prior report of Anonimno.
If the bug re-emerges (I don't wish to roll back my last update unless
necessary
Another user here with the same old bug on a different machine (stationary WS
C422 PRO SE with Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz). The journal log
entries just before the offending one:
Apr 23 00:34:25 AnonymousMachineName systemd-udevd[397]: Using default
interface naming scheme 'v247'.
reassign 1034462 pipewire-media-session 0.4.1-3
thanks
I use snapshots rather than backports (for unrelated reasons). After replacing
pipewire-media-session with wireplumber 0.4.2-1, the particular ioctl error
message is gone (but there are others instead). Therefore, bug report
reassigned to
Package: pipewire
Version: 0.3.56-1
I have very broken mic input in audacity. While looking into log, I saw the
following lines:
Apr 15 22:36:59 AnonymizedComputerName pipewire[1235]: spa.v4l2: '/dev/video0'
VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät
Apr 15 22:36:59
found 799603 1.30.6-1+deb11u1
quit
Affects me. In the journal log I see “NetworkManager[885]:
[1681591017.6980] Error: failed to open /run/network/ifstate”. As this is not
only a warning but also an error, who has done what wrong? (I have 184
occurrences of “error” in the output of
Thank you, Hilmar, the result looks good: your packages resolve the issue
http://tex.stackexchange.com/questions/680690
http://tex.stackexchange.com/questions/680690. While installing your packages,
I had to use dpkg -i -B (rather than the usual dpkg -i ); if this is how the
installation is
Package: texlive-latex-base
Version: 2022.20230122-2
Severity: wishlist
Please push the changes in babel.dtx due to commit cd59ff0 (cf.
https://github.com/latex3/babel/commit/cd59ff0,
https://github.com/latex3/babel/commit/cd59ff0, changes in line 15797-15798)
into Debian. This amounts to
93 matches
Mail list logo
