Bug#1070780: adduser: Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /run/inadyn kann nicht zugegriffen werden: No such file or directory
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 an Archiven müssen heruntergeladen werden. Nach dem Entpacken werden 338
kB zusätzlich belegt sein.
Möchten Sie fortsetzen? [Y/n/?] Y
Holen: 1 http://debian.mirror.lrz.de/debian stable/main amd64 libconfuse-common
all 3.3-3 [13,4 kB]
Holen: 2 http://debian.mirror.lrz.de/debian stable/main amd64 libconfuse2 amd64
3.3-3 [33,3 kB]
Holen: 3 http://debian.mirror.lrz.de/debian stable/main amd64 inadyn amd64
2.10.0-1 [79,0 kB]
126 kB wurden in 0 s heruntergeladen (328 kB/s)
Vormals nicht ausgewähltes Paket libconfuse-common wird gewählt.
(Lese Datenbank ... 516782 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von .../libconfuse-common_3.3-3_all.deb ...
Entpacken von libconfuse-common (3.3-3) ...
Vormals nicht ausgewähltes Paket libconfuse2:amd64 wird gewählt.
Vorbereitung zum Entpacken von .../libconfuse2_3.3-3_amd64.deb ...
Entpacken von libconfuse2:amd64 (3.3-3) ...
Vormals nicht ausgewähltes Paket inadyn wird gewählt.
Vorbereitung zum Entpacken von .../inadyn_2.10.0-1_amd64.deb ...
Entpacken von inadyn (2.10.0-1) ...
libconfuse-common (3.3-3) wird eingerichtet ...
libconfuse2:amd64 (3.3-3) wird eingerichtet ...
inadyn (2.10.0-1) wird eingerichtet ...
adduser: Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /run/inadyn
kann nicht zugegriffen werden: No such file or directory
Trigger für man-db (2.11.2-2) werden verarbeitet ...
Trigger für libc-bin (2.36-9+deb12u7) werden verarbeitet ...
$ sudo ls /run/inadyn
ls: Zugriff auf '/run/inadyn' nicht möglich: Datei oder Verzeichnis nicht
gefunden
«No such file or directory» doesn't sound good. Any error anywhere?
Bug#1069235: diff -r cannot properly display a filename containing an escape sequence and garbles the screen
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 output continues from there. Instead, we expect the file name to be dispayed fully and the cursor go to the next line after the file name.
Bug#1068567: intalling djview-plugin pulls in the transitional package iceweasel though firefox-esr is installed
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 these days that pulls
in firefox-esr.
Is djview-plugin still functional with the relatively new firefox-esr, or does
djview-plugin indeed require a browser from the times of the real iceweasel,
before June 2016? In the first case, adapt the dependencies. In the second,
remove the defunct djview-plugin from Debian.
Bug#1067549: Support arithmetic-encoded JPEGs
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 better”. This is extremely wrong in my tests for a file of mine. As I don't have sufficient rights in bugzilla, I ask someone who has sufficient rights to comment there and, if possible, reopen the upstream issue report. Here's my test. My original file, a nonpublic (sorry about that) portrait photograph, is of size 1483651 bytes. The goal was to compress it as much as possible with GIMP in 1 pass such that the face is still recognizable; we allow color artifacts and a heavily rasterized image. Here are the test results (the first column is the size in bytes, the second column is the format and the settings used for saving): 35623 JPEG, 4:2:0 subsampling, integers 35619 JPEG, 4:2:0 subsampling, float-point numbers 35618 JPEG, 4:2:0 subsampling, fast integers 35254 JPEG, 4:2:0 subsampling, full aliasing, integers 35252 JPEG, 4:2:0 subsampling, full aliasing, float-point numbers 35248 JPEG, 4:2:0 subsampling, full aliasing, fast integers 25656 WEBP, Photo 25484 WEBP, Picture 25364 WEBP, Default 25342 WEBP, Drawing 20720 WEBP, Icon 20720 WEBP, Text 7892 JPEG, arithmetic encoding, 4:2:0 subsampling, full aliasing, integers 7891 JPEG, arithmetic encoding, 4:2:0 subsampling, full aliasing, floating-point numbers 7879 JPEG, arithmetic encoding, 4:2:0 subsampling, full aliasing, fast integers Of course, we used quality 0 in all places. As we see, the smallest JPEG file created with the arithmetic encoding blows - the smallest file created with a WEBP encoding by a factor of around 2.6 and - the smallest JPEG file created without the arithmetic encoding by a factor of around 4.5. Also, both epiphany-browser and chromium do show this smallest file created with the arithmetic encoding (and the face on the compressed image is still recognizable). In my view, both news together (astonishing file-size ratios and support in other browsers) is sufficient at least to reopen the issue report closed 4 years ago (regardless of how to resolve this and who would do this).
Bug#1064068: font-manager shows the older version of two versions of the same font and prints “Fontconfig error: No writable cache directories” on the console
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 /usr/local/share/fonts/link_to_a_directory_on_a_nonroot_drive/cour.ttf The tool gnome-font-viewer reports v2.82 for the first font file and a larger version for the second font file. The tool font-manager reports also v2.82 for Courier New. So a file with a larger version is ignored. This is not good and should be improved: whenever two versions of the same font are available, the larger one should be taken. Upon starting the font-manager, we see 4 equal lines “Fontconfig error: No writable cache directories” on the console without further information. Running # fc-cache -r && fc-cache -fv && dpkg-reconfigure fontconfig fontconfig-cache font-manager didn't help, and /var/log/syslog and dmesg show, subjectively, nothing of interest for this bug report.
Bug#1051497: closed by Debian FTP Masters (reply to Hilmar Preusse ) (Bug#1051497: fixed in texlive-extra 2023.20231007-1)
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 newtx.sty (namely, still 1.724). My question concerns the version of the whole NewTX package and not the versions of the constituent files. (Since you wrote that the present bug report 1051497 is repaired, I highly believe you that you put 1.726 into texlive-fonts-extra, and what I'd like to know is how to check this in the future.) Cheers, AlMa.
Bug#1051497: closed by Debian FTP Masters (reply to Hilmar Preusse ) (Bug#1051497: fixed in texlive-extra 2023.20231007-1)
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 I don't know whether running this command as root would break anything.)
Bug#1051497: Please upgrade NewTX to 1.726 2023-08-25
Alright, got it. Thanks! I simply wanted to make you aware that there's a need for an upgrade of specifically NewTX to a specific version (as compared to upgrades of other LaTeX packages or to an upgrade of NewTX to prior or yet-to-appear versions) because, as fas as I tested so far (around 1000 pages through `pdflatex` and `latex`), this version of NewTX is probably relatively free of issues (as compared to other versions of NewTX or other LaTeX packages you might wish to upgrade). Gratefully, AlMa 09.09.2023, 00:51, Preuße, Hilmar < mailto:hill...@web.de hill...@web.de > Control: 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 tag that issue pending and will close it in one of the next uploads. H. -- sigfault
Bug#1051497: Acknowledgement (Please upgrade NewTX to 1.726 2023-08-25)
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 .
Bug#1051497: Please upgrade NewTX to 1.726 2023-08-25
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 bearings of the double-struck Latin capital letters; cf. http://tex.stackexchange.com/questions/693633 . This upgrade is not urgent, and I personally do not care whether the upgraded package would land in unstable or experimental. Gratefully, Alma
Bug#1041494: diffpdf: changes to zoom for small documents (⩽ 19 pages in at least one file) don't take effect on ↩
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. E.g., run pdflatex on one file containing
\documentclass[ngerman]{article} \usepackage{babel}
\usepackage[bible]{blindtext} \begin{document} \Blindtext[87] \end{document}
and then run pdflatex on another file containing
\documentclass[ngerman]{article} \usepackage{babel}
\usepackage[random]{blindtext} \begin{document} \Blindtext[49] \end{document}
and diffpdf the results.
If each of the compared PDF files has at least 20 pages, another bug kicks in,
namely, http://bugs.debian.org/1051422 http://bugs.debian.org/1051422. In
short, the function of the zoom field is very broken; please repair this.
Gratefully,
Alma
Bug#1037960: The manpages of journalctl should explain bold (or semi-bold), yellow, and blue highlighting/emphasis
Please keep open because the issue is NOT fully resolved; some coloring (bold, blue) remains unexplained or ill-explained.
Bug#1037960: Info received (The manpages of journalctl should explain bold (or semi-bold), yellow, and blue highlighting/emphasis)
Cf. http://github.com/systemd/systemd/issues/28953 http://github.com/systemd/systemd/issues/28953.
Bug#1037960: The manpages of journalctl should explain bold (or semi-bold), yellow, and blue highlighting/emphasis
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.
Bug#1049912: FWD: Please upgrade soul to v3.0 or higher
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} \usepackage{xcolor} \selectcolormodel{rgb}
\usepackage{soul} \begin{document} Please, highlight \hl{this small text}.
\end{document}
Output attached: mwe_48501.png.
The following input doesn't run though pdflatex (a cleaned-up version of the
example from http://tex.stackexchange.com/questions/160220):
\documentclass{standalone} \usepackage[T1]{fontenc} \usepackage[french]{babel}
\usepackage[utf8]{inputenc} \usepackage{soul} \usepackage{color}
\definecolor{y}{RGB}{245, 255, 189} \sethlcolor{y} \begin{document} \hl{é}
\end{document}
T he following error is printed:
! Argument of \UTFviii@two@octets@combine has an extra }. \par
l.10 \hl{é}?
Both issues have been solved upstream; I've just tested soul 2023-06-14 v3.1.
According to my old log files, even soul v3.0 might work. We kindly ask for an
upgrade of the soul package, preferrably into Debian 12.2. Though this is not
urgent, I'd personally welcome an upgrade very much (because these issues
prevent recompilation of my old sources with TeX Live from Debian stable, and
recompiling my old sources with the current upstream TeXLive 2023 doesn't work
properly for different reasons (NewTX is partially broken; cf.
https://tex.stackexchange.com/questions/693396)).
Gratefully,
AlMa
Bug#1026965: Error messages still there despite a full system upgrade in Windows
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 bit hard to see because this vanishes quickly.)
Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to …
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 dates in https://en.wikipedia.org/wiki/NVM_Express#Specifications https://en.wikipedia.org/wiki/NVM_Express#Specifications, the drive might be aware of the NVMe 1.2 or 1.3 specification but, again hypothetically, not 1.4 or even 2.0. I wouldn't know how to check this, and firmware upgrades seem unavailable ( https://semiconductor.samsung.com/consumer-storage/support/tools/ http://semiconductor.samsung.com/consumer-storage/support/tools/ mentions the same version 2B2QEXE7). Just in case this helps, the motherboard is Asus WS C422 PRO/SE. Here is some debugging data: $ sudo nvme error-log -e 2 /dev/nvme0 Error Log Entries for device:nvme0 entries:2 . Entry[ 0] . error_count : 1885 sqid : 0 cmdid : 0x14 status_field : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field) phase_tag : 0 parm_err_loc : 0x lba : 0 nsid : 0 vs : 0 trtype : The transport type is not indicated or the error is not transport related. cs : 0 trtype_spec_info: 0 . Entry[ 1] . error_count : 0 sqid : 0 cmdid : 0 status_field : 0(Successful Completion: The command completed without error) phase_tag : 0 parm_err_loc : 0 lba : 0 nsid : 0 vs : 0 trtype : The transport type is not indicated or the error is not transport related. cs : 0 trtype_spec_info: 0 . $ sudo nvme list Node Generic SN Model Namespace Usage Format FW Rev - - - -- /dev/nvme0n1 /dev/ng0n1 Anonymized S.N. Samsung SSD 970 EVO 1TB 1 135,04 GB / 1,00 TB 512 B + 0 B 2B2QEXE7 $ sudo nvme error-log -e 2 /dev/nvme0 Error Log Entries for device:nvme0 entries:2 . Entry[ 0] . error_count : 1885 sqid : 0 cmdid : 0x14 status_field : 0x2002(Invalid Field in Command: A reserved coded value or an unsupported value in a defined field) phase_tag : 0 parm_err_loc : 0x lba : 0 nsid : 0 vs : 0 trtype : The transport type is not indicated or the error is not transport related. cs : 0 trtype_spec_info: 0 . Entry[ 1] . error_count : 0 sqid : 0 cmdid : 0 status_field : 0(Successful Completion: The command completed without error) phase_tag : 0 parm_err_loc : 0 lba : 0 nsid : 0 vs : 0 trtype : The transport type is not indicated or the error is not transport related. cs : 0 trtype_spec_info: 0 . As you see, the output is slightly different from that in https://github.com/linux-nvme/libnvme/issues/550 https://github.com/linux-nvme/libnvme/issues/550, and `nvme list` does not increase error_count (or at least not directly). If there's anything else I can help with, please let me know. Gratefully, AlMa
Bug#1042793: tracker-…: Failed to create location for error reports: Keine Berechtigung
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” or “no rights”. A bit later, the same wording is reproduced by tracker-miner-fs: “tracker-miner-f[…]: Failed to create location for error reports: Keine Berechtigung”. See the attached excerpt from the journal. These warnings are produced at boot time, and “Failed to create location for error reports: Keine Berechtigung” are yellow in the output of journalctl -b. There are some high-level problems that the computer faces which may or may not be related (e.g., #1040497, evince no longer saves the prior searches, really last-used files do not always show up in the list of the last used files, …; I plan to report the new issues separately). If, for each occurrence of the offending message, the location that allegedly can't be created is so standard that it can be made public, we'd like to see it in the journal so that we can manually check whether it should be created at all (and if it should, whether the permissions are indeed insufficient). So as for now we simply wish for a more verbose error message if possible. (Later, other, higher-level bug reports may follow.) I run gdm3+gnome. (I manually anonymize the stuff I post, so the attached data are terse. If anyone asks for (more) lines of a particular log or file, I'll try to do my best.) Gratefully, AlMa Jul 31 14:29:14 AnonymousPC systemd[1]: systemd-localed.service: Deactivated successfully. Jul 31 14:29:15 AnonymousPC systemd[1]: systemd-hostnamed.service: Deactivated successfully. Jul 31 14:29:45 AnonymousPC geoclue[1212]: Service not used for 60 seconds. Shutting down.. Jul 31 14:29:45 AnonymousPC systemd[1]: geoclue.service: Deactivated successfully. Jul 31 14:29:47 AnonymousPC realmd[1628]: quitting realmd service after timeout Jul 31 14:29:47 AnonymousPC realmd[1628]: stopping service Jul 31 14:29:47 AnonymousPC systemd[1]: realmd.service: Deactivated successfully. Jul 31 14:30:02 AnonymousPC CRON[1923]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jul 31 14:30:02 AnonymousPC CRON[1924]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi) Jul 31 14:30:02 AnonymousPC CRON[1923]: pam_unix(cron:session): session closed for user root Jul 31 14:33:40 AnonymousPC anacron[802]: Job `cron.daily' started Jul 31 14:33:40 AnonymousPC anacron[1930]: Updated timestamp for job `cron.daily' to 2023-07-31 Jul 31 14:33:40 AnonymousPC su[1954]: (to nobody) root on none Jul 31 14:33:40 AnonymousPC su[1954]: pam_unix(su:session): session opened for user nobody(uid=65534) by (uid=0) Jul 31 14:33:40 AnonymousPC systemd[1]: Created slice user-65534.slice - User Slice of UID 65534. Jul 31 14:33:40 AnonymousPC systemd[1]: Starting user-runtime-dir@65534.service - User Runtime Directory /run/user/65534... Jul 31 14:33:40 AnonymousPC systemd[1]: Finished user-runtime-dir@65534.service - User Runtime Directory /run/user/65534. Jul 31 14:33:40 AnonymousPC systemd[1]: Starting user@65534.service - User Manager for UID 65534... Jul 31 14:33:40 AnonymousPC (systemd)[1962]: pam_unix(systemd-user:session): session opened for user nobody(uid=65534) by (uid=0) Jul 31 14:33:40 AnonymousPC systemd[1962]: Queued start job for default target default.target. Jul 31 14:33:40 AnonymousPC systemd[1962]: Created slice app.slice - User Application Slice. Jul 31 14:33:40 AnonymousPC systemd[1962]: Created slice session.slice - User Core Session Slice. Jul 31 14:33:40 AnonymousPC systemd[1962]: Created slice background.slice - User Background Tasks Slice. Jul 31 14:33:40 AnonymousPC systemd[1962]: Reached target paths.target - Paths. Jul 31 14:33:40 AnonymousPC systemd[1962]: Reached target timers.target - Timers. Jul 31 14:33:40 AnonymousPC systemd[1962]: Starting dbus.socket - D-Bus User Message Bus Socket... Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on dirmngr.socket - GnuPG network certificate management daemon. Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gcr-ssh-agent.socket - GCR ssh-agent wrapper. Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gnome-keyring-daemon.socket - GNOME Keyring daemon. Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers). Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted). Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation). Jul 31 14:33:40 AnonymousPC systemd[1962]: Listening on gpg-agent.socket - GnuPG cryptographic
Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package] … (0x3003)
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 been released three days ago; I'm planning to install it next month and report here if anything changes.) If you wish to know user-visible problems (rather than the journal-visible problems), there are many; I'm going to report them, too. (One step at a time.) As of today, the errors and warnings are a tiny bit different: ACPI Error: Needed [Integer/String/Buffer], found [Package] e1607619 (20220331/exresop-469) ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20220331/dswexec-431) ACPI Error: Aborting method \ADBG due to previous error (AE_AML_OPERAND_TYPE) (20220331/psparse-529) ACPI Error: Aborting method \_SB.HIDD._DSM due to previous error (AE_AML_OPERAND_TYPE) (20220331/psparse-529) (the four lines above are red) ACPI: \_SB_.HIDD: failed to evaluate _DSM b356ecee-4244-8f40-a792-4edd4d758054 (0x3003) (the line above is orange) Thanks for the URL https://github.com/fwupd/firmware-lenovo https://github.com/fwupd/firmware-lenovo; I plan to yell there if the next update/upgrade from Lenovo brings no change. Gratefully, AlMa
Bug#1042237: “BPF: Invalid name” occurs on all machines I looked into
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 beyond them is attached. (I cannot attach full-length journals because I'd have to anonymize them, and anonymizing means, as a partial step, taking a look at each line. As the logs generally contain many thousands of lines, I am unable to look through all of them carefully; I can attach only a portion I am able to scroll through as long as I am able to maintain full concentration.) Gratefully, Alma 2023-07-30T03:38:47.609735+02:00 Anonymized_PC kernel: [48300.691272] ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x000a3f, prod_id: 0x0f83, dev_id: 0x20) 2023-07-30T05:53:53.397722+02:00 Anonymized_PC kernel: [56406.550965] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 2023-07-30T05:53:53.441723+02:00 Anonymized_PC kernel: [56406.597140] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 2023-07-30T05:53:53.573718+02:00 Anonymized_PC kernel: [56406.727862] wlp179s0: deauthenticating from Anonymized_MAC_Address by local choice (Reason: 3=DEAUTH_LEAVING) 2023-07-30T05:53:54.648477+02:00 Anonymized_PC kernel: [56407.799608] PM: suspend entry (deep) 2023-07-30T05:53:54.697822+02:00 Anonymized_PC kernel: [56407.851386] Filesystems sync: 0.051 seconds 2023-07-30T05:53:54.697849+02:00 Anonymized_PC kernel: [56407.852130] (NULL device *): firmware: direct-loading firmware nvidia/tu116/nvdec/scrubber.bin 2023-07-30T05:53:54.697852+02:00 Anonymized_PC kernel: [56407.852135] (NULL device *): firmware: direct-loading firmware nvidia/tu116/acr/bl.bin 2023-07-30T05:53:54.697854+02:00 Anonymized_PC kernel: [56407.852272] (NULL device *): firmware: direct-loading firmware nvidia/tu116/acr/ucode_ahesasc.bin 2023-07-30T05:53:54.697856+02:00 Anonymized_PC kernel: [56407.852321] (NULL device *): firmware: direct-loading firmware nvidia/tu116/acr/unload_bl.bin 2023-07-30T05:53:54.697858+02:00 Anonymized_PC kernel: [56407.852325] (NULL device *): firmware: direct-loading firmware nvidia/tu116/acr/ucode_unload.bin 2023-07-30T05:53:54.697860+02:00 Anonymized_PC kernel: [56407.852362] (NULL device *): firmware: direct-loading firmware nvidia/tu116/acr/ucode_asb.bin 2023-07-30T05:53:54.697862+02:00 Anonymized_PC kernel: [56407.852442] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/fecs_bl.bin 2023-07-30T05:53:54.697863+02:00 Anonymized_PC kernel: [56407.852485] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/fecs_data.bin 2023-07-30T05:53:54.697866+02:00 Anonymized_PC kernel: [56407.852511] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/fecs_sig.bin 2023-07-30T05:53:54.697868+02:00 Anonymized_PC kernel: [56407.852589] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/fecs_inst.bin 2023-07-30T05:53:54.697869+02:00 Anonymized_PC kernel: [56407.852650] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/gpccs_bl.bin 2023-07-30T05:53:54.697871+02:00 Anonymized_PC kernel: [56407.852671] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/gpccs_inst.bin 2023-07-30T05:53:54.697873+02:00 Anonymized_PC kernel: [56407.852735] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/gpccs_data.bin 2023-07-30T05:53:54.697875+02:00 Anonymized_PC kernel: [56407.852745] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/gpccs_sig.bin 2023-07-30T05:53:54.697876+02:00 Anonymized_PC kernel: [56407.852824] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/sw_nonctx.bin 2023-07-30T05:53:54.697878+02:00 Anonymized_PC kernel: [56407.852841] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/sw_ctx.bin 2023-07-30T05:53:54.697880+02:00 Anonymized_PC kernel: [56407.852911] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/sw_bundle_init.bin 2023-07-30T05:53:54.697881+02:00 Anonymized_PC kernel: [56407.852977] (NULL device *): firmware: direct-loading firmware nvidia/tu116/gr/sw_method_init.bin 2023-07-30T05:53:54.697884+02:00 Anonymized_PC kernel: [56407.853038] (NULL device *): firmware: direct-loading firmware nvidia/tu116/sec2/sig.bin 2023-07-30T05:53:54.697885+02:00 Anonymized_PC kernel: [56407.853117] (NULL device *): firmware: direct-loading firmware nvidia/tu116/sec2/desc.bin 2023-07-30T05:53:54.697887+02:00 Anonymized_PC kernel: [56407.853153] (NULL device *): firmware: direct-loading firmware nvidia/tu116/sec2/image.bin 2023-07-30T05:53:54.697888+02:00 Anonymized_PC kernel: [56407.853195] (NULL device *): firmware: direct-loading firmware regulatory.db 2023-07-30T05:53:54.697890+02:00 Anonymized_PC kernel: [56407.853246] (NULL device *): firmware: direct-loading
Bug#1042719: “colord-sane[…]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied” is missing the description of the USB port
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 during boot; a hopefully relevant part of the journal is attached. The computer has many USB-A ports, and by default lots of stuff is connected to them (a mouse, a keyboard, an HP printer, an HP all-in-one (used only as a scanner), and sometimes an external USB thumb drive; the printer and the scanner usually sleep or are off at boot). It would be great if we could see an indication of which port was tried to get opened (the identifier of the USB port is unlikely to be a privacy concern) because connecting and disconnecting stuff and rebooting for the purpose of debugging may be difficult. (In my special case, plugging/unplugging the cables on the particular computer is physically tedious, and rebooting takes lots of time. Other folks might find rebooting difficult, e.g., in case of highly available servers.) Further, the red message is unlikely to be a hardware bug because all devices seem to work to the extent of my knowledge with Windows (the printer and the scanner seem to work once you awake them from sleep or turn them on). The fact that certain devices are connected to the computer and are simply asleep does not constitute a user error warranting red color but is normal behavior and should be treated as such. Of course, also the permissions of the USB device in the file system might be wrong for whatever reason. So I speculate that the red message is likely to be a software issue. I can't speculate further without better error reporting. The package colord in version 1.4.6-2.2 is installed. Nitpickung for hard-boiled purists: `if (hd == NULL)` in musb.c should be simplified to `if(!hd)`. Gratefully, AlMa Jul 30 23:39:45 AnonymizedMachineName dbus-daemon[871]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.14' (uid=0 pid=957 comm="/usr/sbin/cupsd -l") Jul 30 23:39:45 AnonymizedMachineName sshd[975]: Server listening on 0.0.0.0 port 22. Jul 30 23:39:45 AnonymizedMachineName sshd[975]: Server listening on :: port 22. Jul 30 23:39:45 AnonymizedMachineName systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles... Jul 30 23:39:45 AnonymizedMachineName systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Jul 30 23:39:45 AnonymizedMachineName systemd[1]: Started ModemManager.service - Modem Manager. Jul 30 23:39:45 AnonymizedMachineName kernel: NET: Registered PF_QIPCRTR protocol family Jul 30 23:39:45 AnonymizedMachineName udev-configure-printer[869]: device devpath is /devices/pci:00/:00:14.0/usb1/1-11 Jul 30 23:39:45 AnonymizedMachineName udev-configure-printer[869]: MFG:hp MDL:deskjet 5600 SERN:AnonymizedSerialNumber serial:AnonymizedSerialNumber Jul 30 23:39:45 AnonymizedMachineName colord[976]: failed to get edid data: EDID length is too small Jul 30 23:39:45 AnonymizedMachineName dbus-daemon[871]: [system] Successfully activated service 'org.freedesktop.ColorManager' Jul 30 23:39:45 AnonymizedMachineName systemd[1]: Started colord.service - Manage, Install and Generate Color Profiles. Jul 30 23:39:45 AnonymizedMachineName dbus-daemon[871]: [system] Successfully activated service 'org.freedesktop.hostname1' Jul 30 23:39:45 AnonymizedMachineName systemd[1]: Started systemd-hostnamed.service - Hostname Service. Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5362] hostname: hostname: using hostnamed Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5363] hostname: static hostname changed from (none) to "AnonymizedMachineName" Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5365] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto) Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5370] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci:b2/:b2:00.0/:b3:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi) Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5371] manager[0x5591bef93000]: rfkill: Wi-Fi hardware radio set enabled Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5371] manager[0x5591bef93000]: rfkill: WWAN hardware radio set enabled Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5405] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wwan.so) Jul 30 23:39:45 AnonymizedMachineName NetworkManager[901]: [1690753185.5420] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-team.so) Jul 30 23:39:45 AnonymizedMachineName
Bug#1042479: Acknowledgement (avahi-daemon[…]: chroot.c: open() failed: No such file or directory)
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 card Intel Centrino Ultimate-N 6300 built into the laptop. The wireless-card driver is iwlwifi.
Bug#1042479: avahi-daemon[…]: chroot.c: open() failed: No such file or directory
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 AnonymizedMachineName avahi-daemon[712]: avahi-daemon 0.8 starting up. Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Starting lm-sensors.service - Initialize hardware monitoring sensors... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Started low-memory-monitor.service - Low Memory Monitor. Jul 29 00:10:34 AnonymizedMachineName /usr/sbin/gpm[721]: *** info [daemon/startup.c(131)]: Jul 29 00:10:34 AnonymizedMachineName /usr/sbin/gpm[721]: Started gpm successfully. Entered daemon mode. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting polkit.service - Authorization Manager... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting power-profiles-daemon.service - Power Profiles daemon... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting rsyslog.service - System Logging Service... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting rtkit-daemon.service - RealtimeKit Scheduling Policy Service... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting smartmontools.service - Self Monitoring and Reporting Technology (SMART) Daemon... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting sysfsutils.service - LSB: Set sysfs variables from /etc/sysfs.conf... Jul 29 00:10:34 AnonymizedMachineName polkitd[723]: Started polkitd version 122 Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting systemd-logind.service - User Login Management... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting udisks2.service - Disk Manager... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Mounted run-rpc_pipefs.mount - RPC Pipe File System. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Reached target rpc_pipefs.target. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: rpc-gssd.service - RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Reached target nfs-client.target - NFS client services. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Reached target remote-fs.target - Remote File Systems. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Starting atd.service - Deferred execution scheduler... Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Started cron.service - Regular background program processing daemon. Jul 29 00:10:34 AnonymizedMachineName systemd[1]: systemd-pcrphase.service - TPM2 PCR Barrier (User) was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-SomeLongUUID). Jul 29 00:10:34 AnonymizedMachineName rsyslogd[726]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2302.0] Jul 29 00:10:34 AnonymizedMachineName rsyslogd[726]: [origin software="rsyslogd" swVersion="8.2302.0" x-pid="726" x-info="https://www.rsyslog.com;] start Jul 29 00:10:34 AnonymizedMachineName systemd[1]: Started rsyslog.service - System Logging Service. Jul 29 00:10:34 AnonymizedMachineName sensors[741]: coretemp-isa- Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Adapter: ISA adapter Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Package id 0: +78.0°C (high = +87.0°C, crit = +105.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Core 0: +75.0°C (high = +87.0°C, crit = +105.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Core 1: +77.0°C (high = +87.0°C, crit = +105.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Core 2: +78.0°C (high = +87.0°C, crit = +105.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Core 3: +75.0°C (high = +87.0°C, crit = +105.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: radeon-pci-0100 Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Adapter: PCI adapter Jul 29 00:10:34 AnonymizedMachineName sensors[741]: temp1: +58.0°C (crit = +120.0°C, hyst = +90.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: acpitz-acpi-0 Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Adapter: ACPI interface Jul 29 00:10:34 AnonymizedMachineName sensors[741]: temp1: +61.5°C (crit = +107.0°C) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: dell_smm-isa- Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Adapter: ISA adapter Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Processor Fan: 0 RPM (min = 0 RPM, max = 4900 RPM) Jul 29 00:10:34 AnonymizedMachineName sensors[741]: Video Fan: 0 RPM (min = 0 RPM, max = 4900 RPM) Jul 29 00:10:34 AnonymizedMachineName
Bug#1017988: (uetoothd)[…]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
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: Bluetooth: hci0: BCM:
'brcm/BCM20702A1-413c-8197.hcd'
Jul 29 00:10:33 AnonymizedMachineName kernel: Bluetooth: hci0: BCM:
'brcm/BCM-413c-8197.hcd'
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Starting
accounts-daemon.service - Accounts Service...
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Started acpi-fakekey.service
- ACPI fakekey daemon.
Jul 29 00:10:33 AnonymizedMachineName kernel: ACPI: AC: AC Adapter [AC]
(off-line)
Jul 29 00:10:33 AnonymizedMachineName kernel: input: ACPI Virtual Keyboard
Device as /devices/virtual/input/input23
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Started acpi-support.service
- ACPI support daemon.
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Started acpid.service - ACPI
event daemon.
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: anacron.service - Run anacron
jobs was skipped because of an unmet condition check (ConditionACPower=true).
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Starting avahi-daemon.service
- Avahi mDNS/DNS-SD Stack...
Jul 29 00:10:33 AnonymizedMachineName systemd[1]: Starting bluetooth.service -
Bluetooth service...
Jul 29 00:10:33 AnonymizedMachineName (uetoothd)[713]: ConfigurationDirectory
'bluetooth' already exists but the mode is different. (File system: 755
ConfigurationDirectoryMode: 555)
Let's take a look at various bluetooth-related directories:
# find / -type d -iname \*blue\* -exec ls -lad {} \;
…
find: ‘/run/user/1000/doc’: Keine Berechtigung
find: ‘/run/user/1000/gvfs’: Keine Berechtigung
drw--- 2 root root 40 29. Jul 00:10 /run/systemd/propagate/bluetooth.service
drwx-- 3 root root 4096 3. Okt 2012 /var/lib/bluetooth
drwxr-xr-x 2 root root 4096 27. Apr 2015
/var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants
drwx-- 3 root root 4096 29. Jul 00:10
/var/tmp/systemd-private-1b81fdf5b8874508bc9eae082c60fc15-bluetooth.service-HCJpfF
drwxr-xr-x 2 root root 4096 13. Jul 16:43 /etc/bluetooth
drwxr-xr-x 2 root root 4096 27. Apr 2015
/etc/systemd/system/bluetooth.target.wants
…
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/libexec/bluetooth
drwxr-xr-x 3 root root 4096 28. Apr 2015 /usr/lib/x86_64-linux-gnu/bluetooth
drwxr-xr-x 2 root root 4096 13. Jul 22:54
/usr/lib/x86_64-linux-gnu/spa-0.2/bluez5
drwxr-xr-x 2 root root 4096 14. Jul 03:08
/usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/bluezqt
drwxr-xr-x 6 root root 4096 22. Jul 17:25
/usr/lib/modules/6.1.0-10-amd64/kernel/net/bluetooth
drwxr-xr-x 2 root root 4096 22. Jul 17:25
/usr/lib/modules/6.1.0-10-amd64/kernel/drivers/bluetooth
drwxr-xr-x 2 root root 4096 13. Jul 22:44 /usr/share/wireplumber/bluetooth.lua.d
…
drwxr-xr-x 2 root root 4096 13. Jul 22:44
/usr/share/doc/gir1.2-gnomebluetooth-3.0
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/share/doc/bluez-cups
drwxr-xr-x 2 root root 4096 14. Jul 03:08 /usr/share/doc/libkf5bluezqt-data
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/share/doc/bluez-obexd
drwxr-xr-x 2 root root 4096 13. Jul 22:54 /usr/share/doc/libspa-0.2-bluetooth
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/share/doc/bluetooth
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/share/doc/libbluetooth3
drwxr-xr-x 2 root root 4096 13. Jul 22:44
/usr/share/doc/libgnome-bluetooth-ui-3.0-13
drwxr-xr-x 2 root root 4096 14. Jul 03:08 /usr/share/doc/libkf5bluezqt6
drwxr-xr-x 2 root root 4096 13. Jul 16:42 /usr/share/doc/bluez
drwxr-xr-x 2 root root 4096 13. Jul 22:39
/usr/share/doc/libgnome-bluetooth-3.0-13
…
drwxr-xr-x 2 root root 4096 13. Jul 22:39
/usr/share/doc/gnome-bluetooth-3-common
drwxr-xr-x 2 root root 4096 13. Jul 22:44 /usr/share/doc/gnome-bluetooth-sendto
drwxr-xr-x 2 root root 4096 14. Jul 03:08
/usr/share/doc/qml-module-org-kde-bluezqt
drwxr-xr-x 2 root root 4096 13. Jul 22:54 /usr/share/spa-0.2/bluez5
drwxr-xr-x 2 root root 4096 13. Jul 22:39 /usr/share/gnome-bluetooth-3.0
drwx-- 3 root root 60 29. Jul 00:10
/tmp/systemd-private-1b81fdf5b8874508bc9eae082c60fc15-bluetooth.service-Y0ZhEd
drwxr-xr-x 3 root root 0 29. Jul 00:10 /sys/kernel/debug/bluetooth
drwxr-xr-x 2 root root 0 29. Jul 00:10 /sys/class/bluetooth
drwxr-xr-x 3 root root 0 29. Jul 00:10
/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.4/3-1.4:1.0/bluetooth
drwxr-xr-x 2 root root 0 29. Jul 00:10
/sys/fs/cgroup/system.slice/bluetooth.service
drwxr-xr-x 6 root root 0 29. Jul 00:10 /sys/module/bluetooth
These are many directories. Running
# find / -type d -iname \*blue\* -exec dpkg -S {} \;
yields /etc/bluetooth, /usr/libexec/bluetooth,
/usr/lib/x86_64-linux-gnu/bluetooth, /usr/share/doc/bluez as belonging to the
package bluez, so (regardless of which permissions of which directories should
be set differently, why, and how) the warning better
Bug#1003965: Processed: upgrading linux-image-6.1.0-10-amd64 leads to “BPF: Invalid name”
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. Moreover, in #1042237 these mesages have been read from the console, whereas in #1003965, they have been taken from the kernel log. Further, in #1042237 no information about any modules is printed, whereas in #1003965, a bunch of modules seems to get not validated and not being able to load. Finally, #1042237 occured during kernel upgrade only once (and has NOT re-occurred so far AFAIK during boot), which might indicate a problem at kernel upgrades, whereas #1003965 occured during boot. Gratefully, AlMa
Bug#1041749: “/usr/libexec/gdm-x-session[…]: (WW) Warning, couldn't open module ast” followed by “/usr/libexec/gdm-x-session[968]: (EE) Failed to load module "ast" (module does not exist, 0)”
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 (/dev/dri/card1) has lots of ports; a properly functioning monitor Philips 275B1 is connected to the DisplayPort of the card, and the other ports are empty. In the journal we see a warning and an error written there during boot: /usr/libexec/gdm-x-session[…]: (WW) Warning, couldn't open module ast /usr/libexec/gdm-x-session[…]: (EE) Failed to load module "ast" (module does not exist, 0) >From a user's viewpoint, there's probably no error here and nothing to warn >about here, since the absence of anything connected to the VGA D-SUB port is >fine as long as a functioning monitor is connected elsewhere (in our case, to >the graphics card). I tried to specify the monitor as a command-line argument >“video=DP-1:2560x1440R”; does this help or can this even be improved? If the (WW) and (EE) lines occur for a different reason than the absense of anything connected to the VGA D-SUB port, the reason should be visible in the journal (but it's not)! The machine has other, related issues (cf. #1040497), which, hypothetically, may (or may not) interplay with this one. The relevant parts of the journal and of the lshw and lspci outputs are attached. By the way, after boot and after gdm3+gnome started, the module ast turns out to be even loaded (probably, for no good reason!): # lsmod | grep ast ast 61440 1 drm_vram_helper 20480 1 ast drm_ttm_helper 16384 3 drm_vram_helper,ast,nouveau drm_kms_helper 204800 5 drm_vram_helper,ast,drm_display_helper,nouveau drm 614400 18 drm_kms_helper,drm_vram_helper,ast,drm_display_helper,drm_ttm_helper,ttm,nouveau i2c_algo_bit 16384 3 igb,ast,nouveau Gratefully, AlMa Part of the journal: Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (--) Log file renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-968.log" to "/var/lib/gdm3/.local/share/xorg/Xorg.0.log" Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: X.Org X Server 1.21.1.7 Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: X Protocol Version 11, Revision 0 Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Current Operating System: Linux AnonymizedMachineName 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64 Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=794e56b5-1d18-4d73-849e-6d52f2eacce5 ro video=DP-1:2560x1440R Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: xorg-server 2:21.1.7-3 (https://www.debian.org/support) Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Current version of pixman: 0.42.2 Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Before reporting problems, check http://wiki.x.org Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: to make sure that you have the latest version. Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Markers: (--) probed, (**) from config file, (==) default setting, Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (++) from command line, (!!) notice, (II) informational, Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) Log file: "/var/lib/gdm3/.local/share/xorg/Xorg.0.log", Time: Sat Jul 22 22:35:25 2023 Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) No Layout section. Using the first Screen section. Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) No screen section available. Using defaults. Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (**) |-->Screen "Default Screen Section" (0) Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (**) | |-->Monitor "" Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) No monitor specified for screen "Default Screen Section". Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: Using a default monitor configuration. Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) Automatically adding devices Jul 22 22:35:25 AnonymizedMachineName /usr/libexec/gdm-x-session[968]: (==) Automatically enabling devices Jul 22 22:35:25
Bug#1037449: colord[…]: failed to get edid data: EDID length is too small
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 relevant portion of the log is attached. I have not noticed any color issues so far. (Exception: my network printer – usually and now it's turned off – runs out of ink from time to time, but Linux knows nothing about this.) Gratefully, AlMa Jul 22 22:35:24 AnonymizedMachineName systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles... Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/sda [SAT], state read from /var/lib/smartmontools/smartd.AnonymizedSerialOne.ata.state Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, opened Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, Samsung SSD 970 EVO 1TB, S/N:AnonymizedSerialTwo, FW:2B2QEXE7, 1.00 TB Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list. Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.Samsung_SSD_970_EVO_1TB-AnonymizedSerialTwo.nvme.state Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Initial device: auto Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Initial device: auto Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Info: lircd: Opening log, level: Info Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: driver: devinput Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: Using systemd fd Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Warning: Running as root Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: output: /var/run/lirc/lircd Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: nodaemon: 1 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: plugindir: /usr/lib/x86_64-linux-gnu/lirc/plugins Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: logfile: syslog Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: immediate-init: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: permission: 666 Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Info: Using remote: devinput-64. Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: driver-options: Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: pidfile: /var/run/lirc/lircd.pid Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: listen: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: connect: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: userelease: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: effective_user: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: release_suffix: _EVUP Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: allow_simulate: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: repeat_max: 600 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: configfile: /etc/lirc/lircd.conf Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: dynamic_codes: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Current driver: devinput Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver API version: 4 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver version: 0.10.0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver info: See file:///usr/share/doc/lirc/plugindocs/devinput.html Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: lircd: Opening log, level: Info Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Using systemd fd Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Warning: Running as root Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Using remote: devinput-64. Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_MISC Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_MISC Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code:
Bug#1035885: iwlwifi: api flags index 2 larger than supported by driver
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: enabling device (0100 -> 0102) Jul 22 22:35:22 AnonymizedMachineName kernel: [drm] Initialized ast 0.1.0 20120228 for :04:00.0 on minor 0 Jul 22 22:35:22 AnonymizedMachineName kernel: AVX2 version of gcm_enc/dec engaged. Jul 22 22:35:22 AnonymizedMachineName kernel: ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x000a3f, prod_id: 0x0f83, dev_id: 0x20) Jul 22 22:35:22 AnonymizedMachineName kernel: AES CTR mode by8 optimization enabled Jul 22 22:35:22 AnonymizedMachineName kernel: asus_wmi: ASUS WMI generic driver loaded Jul 22 22:35:22 AnonymizedMachineName kernel: Console: switching to colour frame buffer device 128x48 Jul 22 22:35:22 AnonymizedMachineName kernel: ast :04:00.0: [drm] fb0: astdrmfb frame buffer device Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: api flags index 2 larger than supported by driver The relevant lshw portion: *-pci:2 description: PCI bridge product: Sky Lake-E PCI Express Root Port A vendor: Intel Corporation physical id: 0 bus info: pci@:b2:00.0 version: 07 width: 32 bits clock: 33MHz capabilities: pci msi pciexpress pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:35 memory:fbe0-fbef *-network description: Wireless interface product: Wi-Fi 6 AX200 vendor: Intel Corporation physical id: 0 bus info: pci@:b3:00.0 logical name: wlp179s0 version: 1a serial: AnonymizedSerial width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=6.1.0-10-amd64 firmware=72.daa05125.0 cc-a0-72.ucode ip=192.168.1.49 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:94 memory:fbe0-fbe03fff The relevant lspci portion: b3:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) Subsystem: Intel Corporation Wi-Fi 6 AX200NGW Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- http://bugs.debian.org/1035885 that the firmware probably advertises some features that the driver doesn't know how to use. Perhaps, it's time to upgrade the driver? Or is the aforementioned yellow message a real warning for me as an admin or a user, and I should take some action? Gratefully, AlMa
Bug#1041743: Thx!
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 yellow means, AFAIK, a warning) but light-gray–white as usual. Gratefully, AlMa
Bug#1041745: smartd[…]: Device: /dev/nvme0, number of Error Log entries increased from … to …
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 portion of the log is attached. Is this a problem of software, firmware, or hardware? In plain English, what is the real error? What to do to avoid whichever havoc might occur? Gratefully, AlMa Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, opened Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, Samsung SSD 970 EVO 1TB, S/N:AnonymizedSerialOne, FW:2B2QEXE7, 1.00 TB Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list. Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Device: /dev/nvme0, state read from /var/lib/smartmontools/smartd.Samsung_SSD_970_EVO_1TB-AnonymizedSerialOne.nvme.state Jul 22 22:35:24 AnonymizedMachineName smartd[815]: Monitoring 1 ATA/SATA, 0 SCSI/SAS and 1 NVMe devices Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Initial device: auto Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Initial device: auto Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Info: lircd: Opening log, level: Info Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: driver: devinput Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: Using systemd fd Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Warning: Running as root Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: output: /var/run/lirc/lircd Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: nodaemon: 1 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: plugindir: /usr/lib/x86_64-linux-gnu/lirc/plugins Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: logfile: syslog Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: immediate-init: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: permission: 666 Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Info: Using remote: devinput-64. Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: driver-options: Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: pidfile: /var/run/lirc/lircd.pid Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: listen: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: connect: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: userelease: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: effective_user: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: release_suffix: _EVUP Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: allow_simulate: 0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: repeat_max: 600 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: configfile: /etc/lirc/lircd.conf Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Options: dynamic_codes: (null) Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Current driver: devinput Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver API version: 4 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver version: 0.10.0 Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Driver info: See file:///usr/share/doc/lirc/plugindocs/devinput.html Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: lircd: Opening log, level: Info Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: Using systemd fd Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Warning: Running as root Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Info: Using remote: devinput-64. Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_MISC Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_MISC Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_MOUSE Jul 22 22:35:24 AnonymizedMachineName lircd[884]: lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple values for same code: BTN_SOUTH Jul 22 22:35:24 AnonymizedMachineName lircd-0.10.1[884]: Notice: /etc/lirc/lircd.conf.d/devinput.lircd.conf: devinput-64: Multiple
Bug#1041744: kernel: thermal thermal_zone0: failed to read out thermal zone (-61)
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, we see the yellow warning “thermal thermal_zone0: failed to read out thermal zone (-61)”. Is this a problem of software, firmware, or hardware? In plain English, what are we really warned about? What to do to avoid whichever havoc might occur? The probably relevant portions of the journal, lshw, and lspci are attached. Gratefully, AlMa In journal: Jul 22 22:35:23 AnonymizedMachineName kernel: nouveau :65:00.0: vgaarb: deactivate vga console Jul 22 22:35:23 AnonymizedMachineName kernel: nouveau :65:00.0: NVIDIA TU116 (168000a1) Jul 22 22:35:23 AnonymizedMachineName kernel: ipmi_si IPI0001:00: IPMI kcs interface initialized Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounting boot-efi.mount - /boot/efi... Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounting home.mount - /home... Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounting media-AnonymizedLabelOne.mount - /media/AnonymizedLabelOne... Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounting media-AnonymizedLabelTwo.mount - /media/AnonymizedLabelTwo... Jul 22 22:35:23 AnonymizedMachineName systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounting tmp.mount - /tmp... Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounted tmp.mount - /tmp. Jul 22 22:35:23 AnonymizedMachineName kernel: ipmi_ssif: IPMI SSIF Interface driver Jul 22 22:35:23 AnonymizedMachineName ntfs-3g[698]: Version 2022.10.3 integrated FUSE 28 Jul 22 22:35:23 AnonymizedMachineName ntfs-3g[698]: Mounted /dev/nvme0n1p5 (Read-Write, label "", NTFS 3.1) Jul 22 22:35:23 AnonymizedMachineName systemd[1]: Mounted media-AnonymizedLabelTwo.mount - /media/AnonymizedLabelTwo. Jul 22 22:35:23 AnonymizedMachineName ntfs-3g[698]: Cmdline options: rw,noatime,discard,commit=120 Jul 22 22:35:23 AnonymizedMachineName ntfs-3g[698]: Mount options: discard,commit=120,allow_other,nonempty,noatime,rw,fsname=/dev/nvme0n1p5,blkdev,blksize=4096 Jul 22 22:35:23 AnonymizedMachineName ntfs-3g[698]: Ownership and permissions disabled, configuration type 7 Jul 22 22:35:23 AnonymizedMachineName kernel: iwlwifi :b3:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 Jul 22 22:35:23 AnonymizedMachineName kernel: thermal thermal_zone0: failed to read out thermal zone (-61) Jul 22 22:35:23 AnonymizedMachineName kernel: nouveau :65:00.0: bios: version 90.16.29.00.a9 # journalctl -b | grep -i -C 1 thermal Jul 22 22:35:22 AnonymizedMachineName kernel: Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear) Jul 22 22:35:22 AnonymizedMachineName kernel: CPU0: Thermal monitoring enabled (TM1) Jul 22 22:35:22 AnonymizedMachineName kernel: process: using mwait in idle threads -- Jul 22 22:35:22 AnonymizedMachineName kernel: audit: type=2000 audit(1690058117.100:1): state=initialized audit_enabled=0 res=1 Jul 22 22:35:22 AnonymizedMachineName kernel: thermal_sys: Registered thermal governor 'fair_share' Jul 22 22:35:22 AnonymizedMachineName kernel: thermal_sys: Registered thermal governor 'bang_bang' Jul 22 22:35:22 AnonymizedMachineName kernel: thermal_sys: Registered thermal governor 'step_wise' Jul 22 22:35:22 AnonymizedMachineName kernel: thermal_sys: Registered thermal governor 'user_space' Jul 22 22:35:22 AnonymizedMachineName kernel: thermal_sys: Registered thermal governor 'power_allocator' Jul 22 22:35:22 AnonymizedMachineName kernel: cpuidle: using governor ladder -- Jul 22 22:35:23 AnonymizedMachineName kernel: iwlwifi :b3:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 Jul 22 22:35:23 AnonymizedMachineName kernel: thermal thermal_zone0: failed to read out thermal zone (-61) Jul 22 22:35:23 AnonymizedMachineName kernel: nouveau :65:00.0: bios: version 90.16.29.00.a9 Part of the output of lshw (searched for “thermal”): *-generic:14 UNCLAIMED description: Signal processing controller product: 200 Series PCH Thermal Subsystem vendor: Intel Corporation physical id: 14.2 bus info: pci@:00:14.2 version: 00 width: 64 bits clock: 33MHz capabilities: pm msi cap_list configuration: latency=0 resources: memory:9094e000-9094efff Part of the output of lspci (searched for “thermal”): 00:14.2 Signal processing controller: Intel Corporation 200 Series PCH Thermal Subsystem DeviceName: Onboard - Other Subsystem: ASUSTeK Computer Inc. 200 Series PCH Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Bug#1041743: kernel: MXM: GUID detected in BIOS
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 whichever havoc might occur? The relevant portion of the journal: Jul 22 22:35:22 AnonymizedMachineName kernel: asus_wmi: Initialization: 0x0 Jul 22 22:35:22 AnonymizedMachineName kernel: asus_wmi: BIOS WMI version: 0.9 Jul 22 22:35:22 AnonymizedMachineName kernel: asus_wmi: SFUN value: 0x0 Jul 22 22:35:22 AnonymizedMachineName kernel: eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS Jul 22 22:35:22 AnonymizedMachineName kernel: input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input7 Jul 22 22:35:22 AnonymizedMachineName kernel: usb 1-11.4.2: Found UVC 1.50 device USB2.0 FHD UVC WebCam (04f2:b612) Jul 22 22:35:23 AnonymizedMachineName kernel: input: USB2.0 FHD UVC WebCam: USB2.0 F as /devices/pci:00/:00:14.0/usb1/1-11/1-11.4/1-11.4.2/1-11.4.2:1.0/input/input8 Jul 22 22:35:23 AnonymizedMachineName kernel: usb 1-11.4.2: Found UVC 1.50 device USB2.0 FHD UVC WebCam (04f2:b612) Jul 22 22:35:23 AnonymizedMachineName kernel: input: USB2.0 FHD UVC WebCam: IR Camer as /devices/pci:00/:00:14.0/usb1/1-11/1-11.4/1-11.4.2/1-11.4.2:1.2/input/input9 Jul 22 22:35:23 AnonymizedMachineName kernel: usbcore: registered new interface driver uvcvideo Jul 22 22:35:23 AnonymizedMachineName kernel: MXM: GUID detected in BIOS Gratefully, AlMa
Bug#1035885: kernel: iwlwifi 0000:b3:00.0: api flags index 2 larger than supported by driver
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 0.1.0 20120228 for :04:00.0 on minor 0 Jul 22 22:35:22 AnonymizedMachineName kernel: AVX2 version of gcm_enc/dec engaged. Jul 22 22:35:22 AnonymizedMachineName kernel: ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x000a3f, prod_id: 0x0f83, dev_id: 0x20) Jul 22 22:35:22 AnonymizedMachineName kernel: AES CTR mode by8 optimization enabled Jul 22 22:35:22 AnonymizedMachineName kernel: asus_wmi: ASUS WMI generic driver loaded Jul 22 22:35:22 AnonymizedMachineName kernel: Console: switching to colour frame buffer device 128x48 Jul 22 22:35:22 AnonymizedMachineName kernel: ast :04:00.0: [drm] fb0: astdrmfb frame buffer device Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: api flags index 2 larger than supported by driver *-pci:2 description: PCI bridge product: Sky Lake-E PCI Express Root Port A vendor: Intel Corporation physical id: 0 bus info: pci@:b2:00.0 version: 07 width: 32 bits clock: 33MHz capabilities: pci msi pciexpress pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:35 memory:fbe0-fbef *-network description: Wireless interface product: Wi-Fi 6 AX200 vendor: Intel Corporation physical id: 0 bus info: pci@:b3:00.0 logical name: wlp179s0 version: 1a serial: AnonymizedSerial width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=6.1.0-10-amd64 firmware=72.daa05125.0 cc-a0-72.ucode ip=192.168.1.49 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:94 memory:fbe0-fbe03fff
Bug#966218: iwlwifi 0000:b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
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 relevant portions of the journal and lshw are attached. The line portions iwlwifi :b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware iwlwifi :b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) are red. As for creating /etc/modprobe.d/iwlwifi.conf with a single line options iwlwifi enable_ini=N : is the type still boolean? In https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220304131517.4929e4b14956.I1bdffa4c37d4ee349aa0001978b716b96e38b090@changeid/ https://patchwork.kernel.org/project/linux-wireless/patch/iwlwifi.20220304131517.4929e4b14956.I1bdffa4c37d4ee349aa0001978b716b96e38b090@changeid/ they tried to change it to integer, but I might be looking in a wrong place. Further, I'm feeling very uncomfortable about changing something I don't really understand (the option is not really documented) that should be done by the system itself (kernel or firmware). Whoever is responsible for the mess should also resolve it! Gratefully, AlMa Jul 22 22:35:22 AnonymizedMachineName kernel: ast :04:00.0: [drm] fb0: astdrmfb frame buffer device Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-72.ucode Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: api flags index 2 larger than supported by driver Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) Jul 22 22:35:22 AnonymizedMachineName kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) Jul 22 22:35:22 AnonymizedMachineName kernel: iwlwifi :b3:00.0: loaded firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm *-pci:2 description: PCI bridge product: Sky Lake-E PCI Express Root Port A vendor: Intel Corporation physical id: 0 bus info: pci@:b2:00.0 version: 07 width: 32 bits clock: 33MHz capabilities: pci msi pciexpress pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:35 memory:fbe0-fbef *-network description: Wireless interface product: Wi-Fi 6 AX200 vendor: Intel Corporation physical id: 0 bus info: pci@:b3:00.0 logical name: wlp179s0 version: 1a serial: AnonymizedSerial width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=6.1.0-10-amd64 firmware=72.daa05125.0 cc-a0-72.ucode ip=192.168.1.49 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:94 memory:fbe0-fbe03fff
Bug#1041741: kernel: nvme nvme0: missing or invalid SUBNQN field.
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 issue in the kernel or a firmware/hardware issue of the NVMe SSD? Anything to upgrade? I could run the software from https://www.samsung.com/de/support/model/MZ-V7E1T0BW , but the drivers there seem old, from year 2000, so I'm not sure whether they are of any help or would make things worse (and whether they upgrade the firmware at all or concern just Windows). Gratefully, AlMa excerpt from the journal: Jul 22 22:35:22 AnonymizedMachineName kernel: nvme nvme0: pci function :09:00.0 Jul 22 22:35:22 AnonymizedMachineName kernel: xhci_hcd :05:00.0: hcc params 0x0200ef80 hci version 0x110 quirks 0x00800010 Jul 22 22:35:22 AnonymizedMachineName kernel: xhci_hcd :05:00.0: xHCI Host Controller Jul 22 22:35:22 AnonymizedMachineName kernel: xhci_hcd :05:00.0: new USB bus registered, assigned bus number 6 Jul 22 22:35:22 AnonymizedMachineName kernel: xhci_hcd :05:00.0: Host supports USB 3.1 Enhanced SuperSpeed Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01 Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb5: Product: xHCI Host Controller Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb5: Manufacturer: Linux 6.1.0-10-amd64 xhci-hcd Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb5: SerialNumber: :05:00.0 Jul 22 22:35:22 AnonymizedMachineName kernel: hub 5-0:1.0: USB hub found Jul 22 22:35:22 AnonymizedMachineName kernel: hub 5-0:1.0: 2 ports detected Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb6: We don't know the algorithms for LPM for this host, disabling LPM. Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 Jul 22 22:35:22 AnonymizedMachineName kernel: nvme nvme0: missing or invalid SUBNQN field. excerpt from lshw: *-pci:7 description: PCI bridge product: 200 Series PCH PCI Express Root Port #9 vendor: Intel Corporation physical id: 1d bus info: pci@:00:1d.0 version: f0 width: 32 bits clock: 33MHz capabilities: pci pciexpress msi pm normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:32 memory:9040-904f *-nvme description: NVMe device product: Samsung SSD 970 EVO 1TB vendor: Samsung Electronics Co Ltd physical id: 0 bus info: pci@:09:00.0 logical name: /dev/nvme0 version: 2B2QEXE7 serial: AnonymizedSerial width: 64 bits clock: 33MHz capabilities: nvme pm msi pciexpress msix nvm_express bus_master cap_list configuration: driver=nvme latency=0 nqn=nqn.2014.08.org.nvmexpress:144d144dAnonymizedSerial Samsung SSD 970 EVO 1TB state=live resources: irq:16 memory:9040-90403fff
Bug#1041503: (no subject)
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 detected Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01 Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb2: Product: xHCI Host Controller Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb2: Manufacturer: Linux 6.1.0-10-amd64 xhci-hcd Jul 22 22:35:22 AnonymizedMachineName kernel: usb usb2: SerialNumber: :00:14.0 Jul 22 22:35:22 AnonymizedMachineName kernel: hub 2-0:1.0: USB hub found Jul 22 22:35:22 AnonymizedMachineName kernel: hub 2-0:1.0: 10 ports detected Jul 22 22:35:22 AnonymizedMachineName kernel: usb: port power management may be unreliable To debug this further, I could try to plug in a USB-A mouse and USB-C charging cable into various ports and observe the journal, but I'd like to know, while doing so, what I should watch for, i.e., what I should and shouldn't see. Gratefully, AlMa
Bug#1001286: kernel: i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD
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: https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/techspec https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/techspec ). Journal messages: Jul 22 22:35:22 AnonymizedMachineName kernel: i801_smbus :00:1f.4: SPD Write Disable is set Jul 22 22:35:22 AnonymizedMachineName kernel: i801_smbus :00:1f.4: SMBus using PCI interrupt Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: [8086:a2a0] type 00 class 0x058000 Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: reg 0x10: [mem 0xfd00-0xfdff 64bit] Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: Adding to iommu group 86 Jul 22 22:35:22 AnonymizedMachineName kernel: dca service started, version 1.12.1 Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: Removing from iommu group 86 Jul 22 22:35:22 AnonymizedMachineName kernel: i2c i2c-0: 2/8 memory slots populated (from DMI) Jul 22 22:35:22 AnonymizedMachineName kernel: i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD Raising severity because more than two machines are concerned. Though it's not urgent (or at least not urgent for me in any sense of the word) because currently I don't have that much RAM to populate all the slots, it's important to eventually remove the restriction because I'm quite sure that I am going to add RAM in the future. All my computers so far ended their lives with the maximal amount of RAM. Gratefully, AlMa
Bug#1001286: kernel: i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD
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 https://www.asus.com/de/motherboards-components/motherboards/workstation/ws-c422-pro-se/techspec ). Journal messages: Jul 22 22:35:22 AnonymizedMachineName kernel: i801_smbus :00:1f.4: SPD Write Disable is set Jul 22 22:35:22 AnonymizedMachineName kernel: i801_smbus :00:1f.4: SMBus using PCI interrupt Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: [8086:a2a0] type 00 class 0x058000 Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: reg 0x10: [mem 0xfd00-0xfdff 64bit] Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: Adding to iommu group 86 Jul 22 22:35:22 AnonymizedMachineName kernel: dca service started, version 1.12.1 Jul 22 22:35:22 AnonymizedMachineName kernel: pci :00:1f.1: Removing from iommu group 86 Jul 22 22:35:22 AnonymizedMachineName kernel: i2c i2c-0: 2/8 memory slots populated (from DMI) Jul 22 22:35:22 AnonymizedMachineName kernel: i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD Raising severity because more than two machines are concerned. Though it's not urgent (or at least not urgent for me in any sense of the word) because currently I don't have that much RAM to populate all the slots, it's important to eventually remove the restriction because I'm quite sure that I am going to add RAM in the future. All my computers so far ended their lives with the maximal amount of RAM. Gratefully, AlMa
Bug#1041141: kernel: pmd_set_huge: Cannot satisfy [mem 0x…-0x…] with a huge-page mapping due to MTRR override.
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.
Bug#1041141: kernel: pmd_set_huge: Cannot satisfy [mem 0x…-0x…] with a huge-page mapping due to MTRR override.
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 version: 0.5 Jul 22 22:35:22 AnonymizedMachineName kernel: PCI: MMCONFIG for domain [bus 00-ff] at [mem 0x6000-0x6fff] (base 0x6000) Jul 22 22:35:22 AnonymizedMachineName kernel: PCI: MMCONFIG at [mem 0x6000-0x6fff] reserved in E820 Jul 22 22:35:22 AnonymizedMachineName kernel: pmd_set_huge: Cannot satisfy [mem 0x6000-0x6020] with a huge-page mapping due to MTRR override. Gratefully, AlMa
Bug#1041014: systemd-timesyncd: data collected by reportbug, new journal
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, did not print anything and also did not terminate by itself. Hitting
Ctrl+C killed/terminated it, leading me back to the usual bash prompt. Is this
the expected behavior? If this behavior is still the same after the today
upgrade, should I still run strace on the process and post the logs or do
something else? (I'm going to check in a few days because I don't always have
the laptop on which the bug occurs at my disposal.)
(Wild guess: Presumably, during the upgrade from Debian 11 to Debian 12 some
important packages that should be installed in their amd64 versions could have
hypothetically been installed, for whatever reason, in i386. This is something
I observed today on a different machine during an otherwise uneventful, routine
upgrade of dbus. I can try to check via `sudo dpkg -l | awk '/^ii/ && $4 ==
"i386" { print }'`.)
Gratefully,
AlMa
Bug#1041736: aptitude: if package to be upgraded is not found, please search for the correct package name approximately
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 festvox-suopuhe-mv festvox-suopuhe-common Unable to apply some actions, aborting Clearly, neither of the suggestions of aptitude is anywhere close to my intention. I propose that aptitude searches approximately, akin to what tre-agrep does, and suggests first packages whose names deviate by 1 character from the asked one, then by two characters, then by three, …, and stops after it has listed all the packages with the current number of deviations (and increases the admissible number of deviations if less than 4 packages have been found so far) or until the list of the known packages is exhausted, whichever comes first. Gratefully, AlMa
Bug#1041558: gsd-media-keys[…]: Unable to get default sink/source
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) segment of the log is attached. What do these warnings tell us? Any bugs here? The computer has no source and no sink, at least not in their everyday meanings. Still, the computer exhibits other issues at boot, so I wonder what are we warned about here, which consequences do these warnings have, and how to avoid whichever trouble might be invited. Gratefully, AlMa Jul 20 04:44:12 AnonymizedMachineName gsd-media-keys[1263]: Failed to grab accelerator for keybinding settings:rotate-video-lock Jul 20 04:44:12 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: dbus-daemon[1085]: [session uid=119 pid=1085] Successfully activated service 'org.gnome.ScreenSaver' Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.0631] dhcp4 (wlp179s0): state changed new lease, address=IPv4AddressOne Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.0639] policy: set 'AnonymizedWiFiName' (wlp179s0) as default for IPv4 routing and DNS Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.0645] dns-mgr: Writing DNS information to /sbin/resolvconf Jul 20 04:44:13 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: dbus-daemon[1085]: [session uid=119 pid=1085] Activating service name='org.freedesktop.systemd1' requested by ':1.10' (uid=119 pid=1232 comm="/usr/libexec/gsd-sharing") Jul 20 04:44:13 AnonymizedMachineName /usr/libexec/gdm-x-session[1085]: dbus-daemon[1085]: [session uid=119 pid=1085] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Jul 20 04:44:13 AnonymizedMachineName gsd-sharing[1232]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Jul 20 04:44:13 AnonymizedMachineName gsd-sharing[1232]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: Joining mDNS multicast group on interface wlp179s0.IPv4 with address IPv4AddressOne. Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: New relevant interface wlp179s0.IPv4 for mDNS. Jul 20 04:44:13 AnonymizedMachineName avahi-daemon[795]: Registering new address record for IPv4AddressOne on wlp179s0.IPv4. Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1200] device (wlp179s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1244] device (wlp179s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1248] device (wlp179s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1256] manager: NetworkManager state is now CONNECTED_SITE Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1271] device (wlp179s0): Activation: successful, device activated. Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.1282] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 20 04:44:13 AnonymizedMachineName NetworkManager[844]: [1689821053.3941] agent-manager: agent[d1470084c37e1102,:1.37/org.gnome.Shell.NetworkAgent/119]: agent registered Jul 20 04:44:14 AnonymizedMachineName dbus-daemon[797]: [system] Activating via systemd: service name='org.freedesktop.realmd' unit='realmd.service' requested by ':1.37' (uid=119 pid=1141 comm="/usr/bin/gnome-shell") Jul 20 04:44:14 AnonymizedMachineName systemd[1]: Starting realmd.service - Realm and Domain Configuration... Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: holding daemon: startup Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: starting service Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: connected to bus Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: GLib-GIO: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’ Jul 20 04:44:14 AnonymizedMachineName realmd[1611]: released daemon: startup Jul 20 04:44:14 AnonymizedMachineName dbus-daemon[797]: [system] Successfully activated service 'org.freedesktop.realmd' Jul 20
Bug#1038981: scaling_cur_freq ≰ scaling_max_freq
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 40 40 40 40 40 $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq 400016 399983 400012 48 400015 35 400016 230 $ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq 40 40 40 40 40 40 40 40 As we see, the value 230 is too high! I'd expect around 40. As the fun is running, the reported elevated values (here, 2.4 GHz) are probably real. Gratefully, AlMa
Bug#1041503: kernel: usb: port power management may be unreliable
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 laptop and the docking station; each time I observed the output in the journal and found nothing power-related (see tried_empty_ports.log). A bunch of error messages occurred when I unplugged and plugged in the docking station itself. The first time I did this, I saw upowerd[1000]: energy 52,50 bigger than full 52,02 in the journal. However, the second time I did this, the message has not reappeared (see tried_unplugging_and_plugging_in_the_docking_station.log). My wish would be that for the computer at hand (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 a HMDI cable), the kernel would be able to manage power reliably (and if it happens already now, the warning should be considered bogus and should not appear). Gratefully, AlMa Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: Run /init as init process Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: with arguments: Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: /init Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: with environment: Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: HOME=/ Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: TERM=linux Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: button: Sleep Button [SLPB] Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: button: Lid Switch [LID] Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: button: Power Button [PWRF] Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: tsc: Refined TSC clocksource calibration: 2303.998 MHz Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: clocksource: tsc: mask: 0x max_cycles: 0x2135f5e6f15, max_idle_ns: 440795231538 ns Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: clocksource: Switched to clocksource tsc Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pps_core: LinuxPPS API ver. 1 registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: battery: Slot [BAT0] (battery present) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: bus type drm_connector registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: bus type USB registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: usbcore: registered new interface driver usbfs Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: usbcore: registered new interface driver hub Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: usbcore: registered new device driver usb Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: bus type thunderbolt registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: thunderbolt :05:00.0: enabling device ( -> 0002) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: i801_smbus :00:1f.4: SPD Write Disable is set Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: i801_smbus :00:1f.4: SMBus using PCI interrupt Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: i2c i2c-0: 2/2 memory slots populated (from DMI) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: PTP clock support registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: sdhci: Secure Digital Host Controller Interface driver Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: sdhci: Copyright(c) Pierre Ossman Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: e1000e: Intel(R) PRO/1000 Network Driver Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: e1000e :00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: xhci_hcd :00:14.0: xHCI Host Controller Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: xhci_hcd :00:14.0: hcc params
Bug#1041494: diffpdf: changes in a single digit in zoom don't take immediate effect
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 (or, perhaps, the focus) elsewhere should incur a change in the view. If no real or virtual keyboard is attached (which is hard to imagine, but the world is huge), also changing a single digit should incur a change in the view. Gratefully, AlMa
Bug#1041484: kernel: hpet_acpi_add: no address or irqs in _CRS
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 a HMDI cable, we discovered the following warning (last line is yellow) generated at boot: Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: Freeing initrd memory: 78744K Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: alg: self-tests for CTR-KDF (hmac(sha256)) passed Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: io scheduler mq-deadline registered Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1c.0: PME: Signaling with IRQ 122 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1c.4: PME: Signaling with IRQ 123 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1c.4: pciehp: Slot #4 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1d.0: PME: Signaling with IRQ 124 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1d.0: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :00:1d.4: PME: Signaling with IRQ 125 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pcieport :04:01.0: pciehp: Slot #1 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+ Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: thermal LNXTHERM:00: registered as thermal_zone0 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: thermal: Thermal Zone [THM0] (72 C) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: serial :00:16.3: enabling device ( -> 0003) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: :00:16.3: ttyS0 at I/O 0x4060 (irq = 19, base_baud = 115200) is a 16550A Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: hpet_acpi_add: no address or irqs in _CRS As the laptop has some issues later (e.g., the contents of the external and internal screens do not fully match in tty text mode: the output to the external monitor is cut below), we'd like to know the extent and consequences of the above warning “hpet_acpi_add: no address or irqs in _CRS”. I plain English, what does it tell us? What does it warn us about, and which actions should we undertake to avoid whichever havoc it might promise? Here is some more data: # journalctl -b| grep -i -C1 hpet Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: BOOT 0x9CB2F000 28 (v01 LENOVO TP-N2Y 1260 PTEC 0002) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: HPET 0x9CB2A000 38 (v01 LENOVO TP-N2Y 1260 PTEC 0002) Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: APIC 0x9CB29000 000164 (v04 LENOVO TP-N2Y 1260 PTEC 0002) -- Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: Reserving BOOT table memory at [mem 0x9cb2f000-0x9cb2f027] Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: Reserving HPET table memory at [mem 0x9cb2a000-0x9cb2a037] Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: Reserving APIC table memory at [mem 0x9cb29000-0x9cb29163] -- Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: Using ACPI (MADT) for SMP configuration information Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: HPET id: 0x8086a201 base: 0xfed0 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: e820: update [mem 0x94e5b000-0x9509bfff] usable ==> reserved -- Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: ACPI: Core revision 20220331 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: hpet: HPET dysfunctional in PC10. Force disabled. Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: APIC: Switch to symmetric I/O mode setup -- Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: DMAR-IR: HPET id 0 under DRHD base 0xfed91000 Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. -- Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: :00:16.3: ttyS0 at I/O 0x4060 (irq = 19, base_baud = 115200) is a 16550A Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel:
Bug#1041482: kernel: pnp 00:0a: disabling [mem …-…] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
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 a HMDI cable, we discovered the following four warnings (last four lines are yellow) generated at boot: Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pnp: PnP ACPI init Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [io 0x1800-0x18fe] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xfd00-0xfd69] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xfd6b-0xfd6c] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xfd6f-0xfdff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xfe00-0xfe01] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xfe20-0xfe7f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:00: [mem 0xff00-0x] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:01: [io 0x2000-0x20fe] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:02: [io 0x0680-0x069f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:02: [io 0x164e-0x164f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:04: [io 0x1854-0x1857] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x1800-0x189f] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0800-0x087f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0880-0x08ff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0900-0x097f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0980-0x09ff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0a00-0x0a7f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0a80-0x0aff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0b00-0x0b7f] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x0b80-0x0bff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x15e0-0x15ef] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x1600-0x167f] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [io 0x1640-0x165f] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xf000-0xf7ff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfed1-0xfed13fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfed18000-0xfed18fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfed19000-0xfed19fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfeb0-0xfebf] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfed2-0xfed3] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:07: [mem 0xfed9-0xfed93fff] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed1-0xfed17fff] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed18000-0xfed18fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed19000-0xfed19fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xf000-0xf7ff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed2-0xfed3] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed9-0xfed93fff] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfed45000-0xfed8] could not be reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:08: [mem 0xfee0-0xfeef] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: system 00:09: [mem 0xfe038000-0xfe038fff] has been reserved Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: pnp 00:0a: disabling [mem 0x000c-0x000c3fff] because it overlaps :00:02.0 BAR 6 [mem
Bug#1041015: Drivers for Dell Wireless 380 Bluetooth Card wanted
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 hci0: firmware: failed to load brcm/BCM-413c-8197.hcd (-2) bluetooth hci0: firmware: failed to load brcm/BCM-413c-8197.hcd (-2) Bluetooth: hci0: BCM: firmware Patch file not found, tried: Bluetooth: hci0: BCM: 'brcm/BCM20702A1-413c-8197.hcd' Bluetooth: hci0: BCM: 'brcm/BCM-413c-8197.hcd' More errors/warnings concerning bluetooth follow later. The card is a built-in “Dell Wireless 380 Bluetooth Card” on a Dell Mobile Precision M6700. I failed to find the requested files myself. Any help/remedy/fix? (As opposed to #1013895, no USB dongles are plugged into our machine; all the USB ports are free.) Gratefully, AlMa
Bug#1041014: systemd-timesyncd.service: Failed to execute /lib/systemd/systemd-timesyncd: Permission dienied
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 systemd-timesyncd.service: Failed to execute /lib/systemd/systemd-timesyncd: Permission dienied systemd-timesyncd.service: Failed at step EXEC spawning /lib/systemd/systemd-timesyncd: Permission dienied … The error number returned by this process is ERRNO. However, -rwxr-xr-x 1 root root 55520 28. Feb 12:15 /lib/systemd/system-timesyncd The error appeared after upgrading from Debian 11 to Debian 12.
Bug#1038981: capping maximum frequency no longer works in kernel 6.1
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 /sys/devices/system/cpu/cpu$i/cpufreq/scaling_cur_freq; done 42 44 399989 230 230 230 400013 399519 Moreover, the cores that resist changes each time; e.g., the next run yields this: # for i in `seq 0 7`; do echo "40"> /sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq && cat /sys/devices/system/cpu/cpu$i/cpufreq/scaling_cur_freq; done 400024 230 42 400020 230 40 399930 48 I tried to read the frequency via /proc/cpuinfo: # for i in `seq 0 7`; do echo "40"> /sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done && cat /proc/cpuinfo | grep MHz cpu MHz : 400.001 cpu MHz : 399.989 cpu MHz : 2300.000 cpu MHz : 400.107 cpu MHz : 1028.210 cpu MHz : 399.942 cpu MHz : 400.001 cpu MHz : 400.004 I also tried to use tlp (yes, I said TLP_DEFAULT_MODE=BAT, TLP_PERSISTENT_DEFAULT=1, CPU_BOOST_ON_BAT=0, and CPU_HWP_DYN_BOOST_ON_BAT=0) and sysfs packages; all methods yield the similar results: capping the frequency of all cores doesn't work. I tried to cap all at, say, 800 MHz, 1.2 GHz, and 2 GHz instead, but the result is often (but not always!) the same: a few cores often (but not always!) resist and run at higher frequencies up to 2.4 GHz. Only seldom I see the expected: # for i in `seq 0 7`; do echo "40"> /sys/devices/system/cpu/cpu$i/cpufreq/scaling_max_freq; done && cat /proc/cpuinfo | grep MHz cpu MHz : 400.004 cpu MHz : 399.988 cpu MHz : 399.999 cpu MHz : 400.011 cpu MHz : 399.980 cpu MHz : 400.048 cpu MHz : 400.002 cpu MHz : 400.008 But running cat /proc/cpuinfo | grep MHz a few seconds later yields again a few lines with 2300.000. The governor is powersave everywhere. For kernel 5 with Debian 11 (which I can no longer test), everything worked like a charm (or at least I always observed all-400-MHz back then). So either the new kernel is erroneous or my processor broke somehow (perhaps, during the upgrade). It has Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz. Who is the culprit? What to do? Gratefully, AlMa
Bug#1038914: GRUB_DISABLE_OS_PROBER=false is a double negation; replace it with GRUB_ENABLE_OS_PROBER=true
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) is more difficult to understand than a positive claim. I had to look at this setting a bit before understanding what is really meant. Suggestion: replace the above line with a straighforward # GRUB_ENABLE_OS_PROBER=true Moreover, I suggest that the default setting, whichever it may be, gets documented in a comment in the configuration file itself. Off-topic: Personally, I prefer to run the os-prober because all my computers are (and should be) able to boot both Windows and Linux. Each time grub is seriously upgraded, I need to take manual action in /etc/default/grub. I'd prefer NOT to undertake this manual action during upgrades. So, I prefer GRUB_DISABLE_OS_PROBER=false or, respectively, GRUB_ENABLE_OS_PROBER=true to be default. Perhaps, os-prober could also be made cleverer in choosing (and looking into) the operating systems that can be booted (the file says, “if your computer is a host for guest OSes installed via LVM or raw disk devices”). After all, nobody prevents a computer from having both: at least two installed operating systems and hosting guest OSes installed via LVM or raw disk devices. Gratefully, AlMa
Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
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 of mine was upgrading to Debian 12 from Debian 11 (with a few packages from Debian 12). Before we get to the first Wayland-related message in the log in some yet-to-be-written bug report, we better deal with all the visible warnings, errors, and failures, one by one, that happen earlier because an issue happening at time 푡 may potentially be (and sometimes is) a consequence of failures happening at times < 푡. Dealing with issues one by one, starting with the earliest, is usually the technically most _proper_ way to deal with software. (Ideally, we'd better start even with the high-level architecture of the GUI, but it's too far from the specific topic here.) > The gdm display manager runs gnome-shell in a special mode to provide > its "greeter" (login prompt) user interface, but there isn't really > any state in that session that would be useful to save, so the fact that > gdm can't load a saved state is not doing anyone any harm. If my memory serves me right, at least the state of the Num Lock was saved in certain older Debian versions. I'm going to double check on this. > Arguably the fact that it tries to load a saved session file and logs a > message while in this special mode is a minor bug, but gnome-shell is a > large, user-facing component with many more users than developers, and > as a result, a very large number of bug reports that are more serious > than this one. > > If this offends you, then you could do the research into why this is > appearing and send a merge request upstream to silence it; but please > bear in mind that even if you take the time to do that, the time needed > for a developer to review whether that contribution is correct would be > time that they cannot spend on something with a higher impact, like for > example diagnosing and fixing a crash. A crash is sometimes (of course, not always) a consequence of an accumulation of issues which happened earlier. (What I personally learned by looking into the documentation of failures of safety-critical or security-critical applications is that for such applications, a hard failure can _always_, to the extent of my knowledge, be contributed to a combination of issues, and that these hidden issues are very difficult to figure out only from the user-visible symptoms; sometimes the root causes are never found.) What you said, essentially, means that resources (here, time) might lack to develop a system the proper way. I fully and completely understand; no argument here. At the same time, this lack of resources is more an organizational problem and less a technical one. (The question of how to organize software development, in particular open-source software development, in such a way that the technically ideal path will be followed with little resources available is both extremely important and difficult. In my view, the sheer multitude of > 80K bugs on www.debian.org/Bugs is not only due to the size of Debian but also a result of the inability to find and follow the technically ideal path. This is not specific to Debian; other software projects suffer similarly. In short, the situation is already bad, and it will get only worse if the current method of software development continues. I'm not going to discuss this question here further, as this would lead us too far away from the topic.) Practically and pragmatically, given the fact that some folks develop a piece of software (here: Gnome) mainly because this is what they want to do (and not only because they have to do it, e.g., to get paid), I hope that I'm providing these folks with feedback. Given that I'm dealing with tons of issues myself, I'm probably doing already more than the majority of Gnome users. It's impossible for me to do more now (otherwise I simply run out of time, sleep, health, and money); even reporting all the red-colored failures in the journal is highly likely to be out of my reach. I hope that if at any point a developer decides to look into any particular issue or a combination of issues, he/she gets the logs he/she needs. In this case, the corresponding bug report(s) will be of help. I apologize if my bug reports sound too harsh (I guess, I have felt simply overwhelmed and extremely helpless; I promise to express myself more professionally). > This is unlikely to be fixed as a Debian-specific change. Any change has a > risk of causing regressions, so we have to weigh up that risk against the > benefit of fixing a bug. If the bug is minor, then the maximum possible > benefit is very small, so any risk at all would be a problem. I get it. At the same time, in my understanding, this is what Debian
Bug#1037523: gnome-shell-extension-pixelsaver doesn't work at all
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 user name and machine name): Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: [pixel-saver]: 'appmenu' is not a valid button. Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: Usage of object.actor is deprecated for AppMenuButton get@resource:///org/gnome/shell/ui/environment.js:387:29 enable@/usr/share/gnome-shell/extensions/pixel-sa...@deadalnix.me/app_menu.js:212:2 enable@/usr/share/gnome-shell/extensions/pixel-sa...@deadalnix.me/extension.js:62:10 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:184:32 _onEnabledExtensionsChanged/<@resource:///org/gnome/shell/ui/extensionSystem.js:529:35 _onEnabledExtensionsChanged@resource:///org/gnome/shell/ui/extensionSystem.js:529:14 createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:686:46 enableExtension@resource:///org/gnome/shell/ui/extensionSystem.js:211:29 EnableExtension@resource:///org/gnome/shell/ui/shellDBus.js:447:38 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:324:38 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:401:34 Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: Jun 13 20:08:56 AnonymizedMachineName gnome-shell[2573]: [pixel-saver]: Can't find original state for AnonymizedUserName@AnonymizedMachineName: ~ with id 0x2800020 The package is useless (on my machine, it fails to work in a visible way), hence the raised severity. I use Debian stable 12 “bookworm”, gnome 1:42+1 with X11. The package should be repaired or removed from Debian altogether. Gratefully, AlMa
Bug#1037449: colord[…]: failed to get edid data: EDID length is too small
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' requested by ':1.14' (uid=0 pid=960 comm="/usr/sbin/cupsd -l") Jun 12 21:41:41 AnonymizedComputerName systemd[1]: Starting colord.service - Manage, Install and Generate Color Profiles... Jun 12 21:41:41 AnonymizedComputerName systemd[1]: Started ModemManager.service - Modem Manager. Jun 12 21:41:41 AnonymizedComputerName kernel: NET: Registered PF_QIPCRTR protocol family Jun 12 21:41:41 AnonymizedComputerName sshd[988]: Server listening on 0.0.0.0 port 22. Jun 12 21:41:41 AnonymizedComputerName sshd[988]: Server listening on :: port 22. Jun 12 21:41:41 AnonymizedComputerName systemd[1]: Started ssh.service - OpenBSD Secure Shell server. Jun 12 21:41:41 AnonymizedComputerName udev-configure-printer[883]: device devpath is /devices/pci:00/:00:14.0/usb1/1-11 Jun 12 21:41:41 AnonymizedComputerName udev-configure-printer[883]: MFG:hp MDL:deskjet 5600 SERN:AnonymizedPrinterSerialNumber serial:AnonymizedPrinterSerialNumber Jun 12 21:41:41 AnonymizedComputerName colord[990]: failed to get edid data: EDID length is too small What is EDID? Why is it too small and how big should it be, whatever it is? Is there a programming error anywhere? The printer itself is powered, connected to the computer via a USB cable, and in a deep sleep with all LEDs off (but if you send a there document, it wakes up). I use Debian stable “bookworm” with udev 252.6-1 and systemd 252.6-1. Gratefully, AlMa
Bug#1037447: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?
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 Manager for UID 119. Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Started pipewire.service - PipeWire Multimedia Service. Jun 12 21:41:41 AnonymizedComputerName systemd[1]: Started session-c1.scope - Session c1 of User Debian-gdm. Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Starting tracker-extract-3.service - Tracker metadata extractor... Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Started wireplumber.service - Multimedia Service Session Manager. Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Started pipewire-pulse.service - PipeWire PulseAudio. Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Starting dbus.service - D-Bus User Message Bus... Jun 12 21:41:41 AnonymizedComputerName systemd[1024]: Started dbus.service - D-Bus User Message Bus. Jun 12 21:41:41 AnonymizedComputerName wireplumber[1045]: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jun 12 21:41:41 AnonymizedComputerName wireplumber[1045]: found session bus but no portal Jun 12 21:41:41 AnonymizedComputerName pipewire-pulse[1046]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jun 12 21:41:41 AnonymizedComputerName pipewire-pulse[1046]: mod.rt: found session bus but no portal Jun 12 21:41:41 AnonymizedComputerName pipewire[1043]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running? Jun 12 21:41:41 AnonymizedComputerName pipewire[1043]: mod.rt: found session bus but no portal The boot log contains no prior mentioning of xdg-desktop-portal, but the package xdg-desktop-portal itself is installed in version 1.16.0-2. Either the error message is bogus, or something is really not found thought it should be there. In any case, the situation should be repaired. I use an up-to-date Debian stable “bookworm”. Gratefully, AlMa
Bug#1036781: gnome-shell segfaults on boot shortly after realmd starts working
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 Realm and Domain Configuration. Mai 25 23:43:55 AnonymizedComputerName realmd[1322]: claimed name on bus: org.freedesktop.realmd Mai 25 23:43:55 AnonymizedComputerName kernel: show_signal_msg: 14 callbacks suppressed Mai 25 23:43:55 AnonymizedComputerName kernel: gnome-shell[1068]: segfault at 0 ip sp 7fffc9a8c8a8 error 14 Mai 25 23:43:55 AnonymizedComputerName kernel: Code: Unable to access opcode bytes at RIP 0xffd6. Unfortunately, dmesg and syslog contain no additional information from the last moments before the segfault. In my understanding, this failure leads to the inability to start Wayland (and xorg kicks in instead). Who is the real culprit and what to do? Any remedy or bugfix? Any (as small as possible) set of packages to upgrade? I run Debian stable, kernel 5.10.0-23-amd64, with a few updated packages from testing. Probably related packages: linux-image-amd64 5.10.179-1, realmd 0.16.3-3, systemd 247.3-7+deb11u2, dbus 1.12.24-0+deb11u1. The severity is raised because the bug is (in my understanding) a major reason for why Wayland is unusable on my machine. Gratefully, AlMa
Bug#1036736: tre-agrep reports out of memory despite plenty of swap
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 shared buff/cache available Mem: 31Gi 3.8Gi 3.5Gi 540Mi 23Gi 26Gi Swap: 14Gi 0B 14Gi $ ls -lh Win10_21H1_German_x64_2021-06-25.iso … 5.5G Apr 14 2021 Win10_21H1_German_x64_2021-06-25.iso $ tre-agrep --color -i -1 Maschineneigenschaft Win10_21H1_German_x64_2021-06-25.iso tre-agrep: Out of memory
Bug#1036555: gnome-shell[…]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
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: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.37' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Starting Locale Service... Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Successfully activated service 'org.freedesktop.locale1' Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Started Locale Service. Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.37' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Starting Location Lookup Service... Mai 21 22:36:47 AnonymizedComputerName polkitd(authority=local)[809]: Registered Authentication Agent for unix-session:c1 (system bus name :1.37 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale de_DE.UTF-8) Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.37' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Starting PackageKit Daemon... Mai 21 22:36:47 AnonymizedComputerName PackageKit[1191]: daemon start Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Successfully activated service 'org.freedesktop.GeoClue2' Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Started Location Lookup Service. Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1171]: dbus-daemon[1171]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=119 pid=1063 comm="/usr/bin/gnome-shell ") Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1171]: dbus-daemon[1171]: Successfully activated service 'org.a11y.atspi.Registry' Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1201]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Mai 21 22:36:47 AnonymizedComputerName org.gnome.Shell.desktop[1063]: Window manager warning: Failed to parse saved session file: Datei »/var/lib/gdm3/.config/mutter/sessions/1065b6e83232cb60411684701404911355001015.ms« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Mai 21 22:36:47 AnonymizedComputerName dbus-daemon[801]: [system] Successfully activated service 'org.freedesktop.PackageKit' Mai 21 22:36:47 AnonymizedComputerName systemd[1]: Started PackageKit Daemon. Mai 21 22:36:47 AnonymizedComputerName kernel: rfkill: input handler disabled Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=119 pid=1213 comm="/usr/libexec/gsd-sharing ") Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Mai 21 22:36:47 AnonymizedComputerName gsd-sharing[1213]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mai 21 22:36:47 AnonymizedComputerName gsd-sharing[1213]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119 pid=1009] Activating service name='org.gtk.vfs.Daemon' requested by ':1.24' (uid=119 pid=1258 comm="ibus-daemon --panel disable ") Mai 21 22:36:47 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1009]: dbus-daemon[1009]: [session uid=119
Bug#1036245: “Any arguments after the -- are treated as filenames and arguments.” in the bash man page makes no sense the way stated
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 bash interpreting further arguments as its own options. Any arguments after the `--' or `-' are treated as a new command line that bash will run. For example, `bash -- ls --help' passes the `--help' to `ls' rather than bash. However, there's a problem: $ bash -- ls --help /usr/bin/ls: /usr/bin/ls: cannot execute binary file AlMa
Bug#1036245: “Any arguments after the -- are treated as filenames and arguments.” in the bash man page makes no sense the way stated
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 arguments after the -- are treated as filenames and arguments.” is strange and should be rewritten or dropped. I see two main logical interpretations of this sentence: (1) *For each argument 푥 after --, 푥 is treated as a filename and an argument simultaneously.* This can be expressed more succinctly without any loss of information: *For each argument 푥 after --, 푥 is treated as a filename.* This implies the original formulation as follows. Take any 푥 after --. By the succinct formulation, 푥 is treated as a filename. By assumption, 푥 is an argument. By default (as this has not been stated otherwise for the option --), arguments are also treated as arguments, so 푥 is also treated as an argument. Together, 푥 is treated as a filename and an argument. Q.E.D. (2) *For each argument 푥 after --, 푥 is treated as a filename, or 푥 is treated as an argument.* This is a tautology, which you see as follows. Take any 푥 after --. By default (as this has not been stated otherwise for the option --), arguments are also treated as arguments, so 푥 is treated as an argument. Therefore, 〈any claim〉 or 푥 is treated as an or argument. The term 〈any claim〉 can be arbitrary; in particular, *푥 is treated as a filename* would do. Q.E.D. Summarizing, in case (1) the sentence can be shortened and in case (2) the sentence can be dropped, both without loss of information. Of course, assuming that the authors of the document really wish to say what they are saying. We ask for the description of `--` to be rewritten clearly and succinctly. Gratefully, AlMa
Bug#1036233: /usr/libexec/gdm-wayland-session[…]: dbus-daemon[…]: [session uid=… pid=…] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
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 AnonymizedComputerName org.gnome.Shell.desktop[1038]: Window manager warning: Failed to parse saved session file: Datei »/var/lib/gdm3/.config/mutter/sessions/10b3c2ff926492598a1684348635677448000995.ms« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden Mai 17 20:37:18 AnonymizedComputerName dbus-daemon[772]: [system] Successfully activated service 'org.freedesktop.PackageKit' Mai 17 20:37:18 AnonymizedComputerName systemd[1]: Started PackageKit Daemon. Mai 17 20:37:18 AnonymizedComputerName kernel: rfkill: input handler disabled Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[983]: dbus-daemon[983]: [session uid=119 pid=983] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=119 pid=1176 comm="/usr/libexec/gsd-sharing ") Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[983]: dbus-daemon[983]: [session uid=119 pid=983] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Failures are not good in general and make me worry (especially since my log shows many of them). How bad is this particular failure? Who is the culprit and what to do? The machine runs systemd 247.3-7+deb11u2, dbus 1.12.24-0+deb11u1, and gnome-settings-daemon 42.2-1 (which contains /usr/libexec/gsd-sharing). Gratefully, AlMa
Bug#1036232: org.gnome.Shell.desktop[…]: Window manager warning: Failed to parse saved session file:
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]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. Mai 17 20:03:28 AnonymizedComputerName gnome-shell[1049]: Will monitor session c1 Mai 17 20:03:28 AnonymizedComputerName dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.35' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:28 AnonymizedComputerName systemd[1]: Starting Locale Service... Mai 17 20:03:29 AnonymizedComputerName dbus-daemon[793]: [system] Successfully activated service 'org.freedesktop.locale1' Mai 17 20:03:29 AnonymizedComputerName wpa_supplicant[812]: wlp179s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE Mai 17 20:03:29 AnonymizedComputerName systemd[1]: Started Locale Service. Mai 17 20:03:29 AnonymizedComputerName /usr/libexec/gdm-wayland-session[998]: dbus-daemon[998]: [session uid=119 pid=998] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1113] policy: auto-activating connection 'AnonymizedWiFiName' (AnonymizedHexID) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1121] device (wlp179s0): Activation: starting connection 'AnonymizedWiFiName' (AnonymizedHexID) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1123] device (wlp179s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName /usr/libexec/gdm-wayland-session[998]: dbus-daemon[998]: [session uid=119 pid=998] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1146] device (wlp179s0): set-hw-addr: reset MAC address to AnonymizedMACAddress (preserve) Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1155] device (wlp179s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1160] device (wlp179s0): Activation: (wifi) access point 'AnonymizedWiFiName' has security, but secrets are required. Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1161] device (wlp179s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1164] sup-iface[db9ea4b039e47a74,0,wlp179s0]: wps: type pbc start... Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1289] device (wlp179s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1296] device (wlp179s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1301] device (wlp179s0): Activation: (wifi) connection 'AnonymizedWiFiName' has security, and secrets exist. No new secrets needed. Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'ssid' value 'AnonymizedWiFiName' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'scan_ssid' value '1' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1302] Config: added 'bgscan' value 'simple:30:-70:86400' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'auth_alg' value 'OPEN' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1303] Config: added 'psk' value '' Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1795] device (wlp179s0): supplicant interface state: disconnected -> scanning Mai 17 20:03:29 AnonymizedComputerName NetworkManager[796]: [1684346609.1795] device (p2p-dev-wlp179s0): supplicant management interface state: disconnected -> scanning Mai 17 20:03:29 AnonymizedComputerName dbus-daemon[793]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.35' (uid=119 pid=1049 comm="/usr/bin/gnome-shell ") Mai 17 20:03:29 AnonymizedComputerName systemd[1]: Starting Location Lookup Service... Mai 17 20:03:29 AnonymizedComputerName polkitd(authority=local)[800]:
Bug#1035899: (no subject)
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.
Bug#1036120: Okular draws the pages of Postscript files with black vertical bars (sometimes with colored dots on it) on the left
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
\documentclass{article}\begin{document}Test\end{document}. Scroll completely to
the left. Observe a vertical bar on the left of the page. If the bar doesn't
appear immediately, zoom out (and in) a few times with Ctrl++ and Ctrl+-. At
some (seemingly random) magnifications, the bar sometimes appears (and
sometimes disappears) fully or partially. Sometimes, colored dots are scattered
on the otherwise black bar. Two screenshots of okular mwe.pdf with a bar are
attached: one at 33%, another at full page for the same small window size.
The severity is raised because the bar distracts the reader and gets
increasingly annoying in the long run. I run Debian bullseye with a few updated
packages from bookworm.
The black vertical bar shouldn't be there. I kindly ask for a fix.
Gratefully,
AlMa
mwe.ps
Description: PostScript document
Bug#1036115: Evince draws the pages of Postscript files with black vertical bars on the left
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}. Observe two black
vertical bars on the left of the page: one in the main view and another in the
thumbnails. If the bars don't appear immediately, play with evince a bit:
change the zoom or reload with Ctrl+R a few times. Upon some reloads, the bars
appear, and upon other reloads, the bars disappear (not necessarily
simultaneously). A screenshot of evince mwe.pdf with two bars is attached.
The severity is raised because the bars distract the reader, and in the long
run (and the bug has been there quite long, probably over a year), they get
increasingly annoying. (If my memory doesn't fail me, the bars might have even
appeared once in a printout, though it's a long time ago, and I wouldn't vouch
for it today because it was seldom and might have been specific to a file,
ergo, not necessarily related to the bug here.) I run Debian bullseye with a
few updated packages from bookworm.
The black vertical bars shouldn't be there. I kindly ask for a fix.
Gratefully,
AlMa
mwe.ps
Description: PostScript document
Bug#1036112: views of the PDF outputs of pdflatex, latex+dvipdf, and latex+ps2pdf are slightly shifted upwards compared to the view of the Postscript output of latex+dvips
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]{};
\end{tikzpicture}% \end{document} and run latex mwe && pdflatex mwe && dvips -o
mwe.ps mwe.dvi && dvipdf mwe.dvi mwe.dvi.pdf && ps2pdf mwe.ps mwe.ps.pdf.
In https://i.stack.imgur.com/DSm4L.png https://i.stack.imgur.com/DSm4L.png
(attached screenshot_2_nodes.png), we see the generated mwe.ps, mwe.pdf,
mwe.dvi.pdf, and mwe.ps.pdf (from left to right), as shown by the viewer gv.
Notice that in the view of the PostScript file, the upper box is fully visible,
whereas in views of the PDF files, the upper line of the upper box is cut off.
If we remove the lower \node… command from the input, the upper box becomes
fully visible, but the views of the Postscript and PDF outputs are still
different, as shown in https://i.stack.imgur.com/5CS8n.png
https://i.stack.imgur.com/5CS8n.png (attached screenshot_1_node.png). In the
view of the Postscript file, the remaining box is lower than in the view of the
PDF file.
Clearly, cutting off stuff is bad as well as the discrepancies between the
views of the Postscript and PDF files that should depict the same stuff.
According to
https://tex.stackexchange.com/questions/685761/gv-the-outputs-of-pdflatex-latexdvipdf-and-latexps2pdf-are-slightly-shifted#comment1701532_685761
https://tex.stackexchange.com/questions/685761/gv-the-outputs-of-pdflatex-latexdvipdf-and-latexps2pdf-are-slightly-shifted#comment1701532_685761,
the viewers Adobe Reader, sumatra, and the pdf viewer from winedt show the
boxes exactly in the corner, and the problem here is probably due to gv.
On the machine in question, ghostscript 9.55.0~dfsg-3 on Debian stable with a
few updated packages from testing is installed. I kindly ask to check the issue
and fix it.
Gratefully,
AlMa
Bug#1017466: Datei … ist ein symbolische Verknüpfung, während Datei … ein normale leere Datei ist.
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 g $ ln -s f fl $ diff --no-dereference fl g Datei fl ist ein symbolische Verknüpfung, während Datei g ein normale leere Datei ist. The grammatically correct message should be this: Datei fl ist eine symbolische Verknüpfung, während Datei g eine normale leere Datei ist. Alternatively, if you prefer to have the definite article: Die Datei fl ist eine symbolische Verknüpfung, während die Datei g eine normale leere Datei ist. Raising the severity because the errors annoy me as a corrector each time I see them. Gratefully, Alma
Bug#1035899: (no subject)
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, […].”
Bug#1035899: org.gnome.Shell.desktop[…]: Unrecognized option: -initfd
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 (it's a production machine), but I can certainly try to upgrade a package or two. To get rid of the particular error message, the solution would be to upgrade xwayland, wouldn't it? Any hint on which version would do, at least roughly? Gratefully, Alma
Bug#1035895: Info received (Bug#1035895: Please add ast_dri.so)
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.
Bug#1035895: Please add ast_dri.so
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.
Bug#1035901: Pipewire & wireplumber: Inappropriate IOCTL for device
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 device vbi0 Mai 10 22:44:01 AnonymizedComputerName kernel: cx23885: cx23885[0]: alsa: registered ALSA audio device Mai 10 22:44:01 AnonymizedComputerName kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s) Mai 10 22:44:01 AnonymizedComputerName kernel: cx23885: cx23885[0]: cx23885 based dvb card … Mai 10 22:44:01 AnonymizedComputerName systemd[936]: Listening on PipeWire Multimedia System Socket. … Mai 10 22:44:01 AnonymizedComputerName systemd[936]: Started PipeWire Multimedia Service. … Mai 10 22:44:01 AnonymizedComputerName dbus-daemon[781]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=119 pid=967 comm="/usr/bin/pipewire ") … Mai 10 22:44:01 AnonymizedComputerName wireplumber[971]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? Mai 10 22:44:01 AnonymizedComputerName wireplumber[971]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. … Mai 10 22:44:02 AnonymizedComputerName pulseaudio[968]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 22:44:02 AnonymizedComputerName dbus-daemon[781]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.39' (uid=119 pid=968 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Mai 10 22:44:02 AnonymizedComputerName systemd[1]: Condition check resulted in Bluetooth service being skipped. Mai 10 22:44:02 AnonymizedComputerName rtkit-daemon[1003]: Supervising 4 threads of 2 processes of 1 users. Mai 10 22:44:02 AnonymizedComputerName rtkit-daemon[1003]: Successfully made thread 1132 of process 968 owned by '119' RT at priority 5. Mai 10 22:44:02 AnonymizedComputerName rtkit-daemon[1003]: Supervising 5 threads of 2 processes of 1 users. Mai 10 22:44:02 AnonymizedComputerName systemd[936]: Started Sound Service. Mai 10 22:44:02 AnonymizedComputerName systemd[936]: Reached target Main User Target. Mai 10 22:44:02 AnonymizedComputerName systemd[936]: Startup finished in 1.324s. Mai 10 22:44:02 AnonymizedComputerName pulseaudio[968]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 22:44:02 AnonymizedComputerName pulseaudio[968]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 22:44:02 AnonymizedComputerName pulseaudio[968]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 22:44:02 AnonymizedComputerName pipewire[967]: spa.v4l2: '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät The last lines above are all shown red, so I excercise, ergo, caution. In plain English, how should this message about wrong control worry me (besides from other issues with the computer which may be related or not)? The package wireplumber 0.4.2-5 is installed. The package pipewire-media-session has been uninstalled a long time ago and purged a boot ago. I run $ uname -a Linux AnonymizedComputerName 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux Any remedy? Any bugfix? Gratefully, Alma
Bug#1035899: org.gnome.Shell.desktop[…]: Unrecognized option: -initfd
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 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[778]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.39' (uid=119 pid=953 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Mai 10 21:01:21 AnonymizedComputerName rtkit-daemon[972]: Supervising 4 threads of 2 processes of 1 users. Mai 10 21:01:21 AnonymizedComputerName rtkit-daemon[972]: Successfully made thread 1123 of process 953 owned by '119' RT at priority 5. Mai 10 21:01:21 AnonymizedComputerName rtkit-daemon[972]: Supervising 5 threads of 2 processes of 1 users. Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Started Sound Service. Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Reached target Main User Target. Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Startup finished in 1.360s. Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pipewire[952]: spa.v4l2: '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pipewire[952]: spa.v4l2: '/dev/video0' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-_00_1f.3" card_name="alsa_card.pci-_00_1f.3" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName pulseaudio[953]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_65_00.1" card_name="alsa_card.pci-_65_00.1" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. Mai 10 21:01:21 AnonymizedComputerName /usr/libexec/gdm-wayland-session[969]: dbus-daemon[969]: [session uid=119 pid=969] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=119 pid=1026 comm="/usr/bin/gnome-shell ") Mai 10 21:01:21 AnonymizedComputerName /usr/libexec/gdm-wayland-session[969]: dbus-daemon[969]: [session uid=119 pid=969] Successfully activated service 'org.a11y.Bus' Mai 10 21:01:22 AnonymizedComputerName gnome-shell[1026]: Using public X11 display :1024, (using :1025 for
Bug#1035895: Please add ast_dri.so
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 gnome-shell[1026]: Device
'/dev/dri/card0' prefers shadow buffer
Mai 10 21:01:21 AnonymizedComputerName goa-daemon[1048]: goa-daemon version
3.38.0 starting
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Added device
'/dev/dri/card0' (ast) using atomic mode setting.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Activating service name='org.gnome.Identity' requested by ':1.15'
(uid=119 pid=1048 comm="/usr/libexec/goa-daemon ")
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Device
'/dev/dri/card1' prefers shadow buffer
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Successfully activated service 'org.gnome.OnlineAccounts'
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Successfully activated service 'org.gnome.Identity'
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Started Virtual filesystem
service - GNOME Online Accounts monitor.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Activating via systemd: service
name='org.gtk.vfs.GPhoto2VolumeMonitor'
unit='gvfs-gphoto2-volume-monitor.service' requested by ':1.3' (uid=119 pid=955
comm="/usr/libexec/tracker-miner-fs ")
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Starting Virtual
filesystem service - digital camera monitor...
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[962]: [session uid=119
pid=962] Successfully activated service 'org.gtk.vfs.GPhoto2VolumeMonitor'
Mai 10 21:01:21 AnonymizedComputerName systemd[920]: Started Virtual filesystem
service - digital camera monitor.
Mai 10 21:01:21 AnonymizedComputerName dbus-daemon[778]: [system] Activating
via systemd: service name='org.freedesktop.UPower' unit='upower.service'
requested by ':1.37' (uid=119 pid=955 comm="/usr/libexec/tracker-miner-fs ")
Mai 10 21:01:21 AnonymizedComputerName systemd[1]: Starting Daemon for power
management...
Mai 10 21:01:21 AnonymizedComputerName systemd[1]: Started Console Mouse
manager.
Mai 10 21:01:21 AnonymizedComputerName gnome-shell[1026]: Added device
'/dev/dri/card1' (nouveau) using non-atomic mode setting.
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]: pci id
for fd 9: 1a03:2000, driver (null)
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]:
MESA-LOADER: failed to open ast: /usr/lib/dri/ast_dri.so: Kann die
Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden (search
paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
Mai 10 21:01:21 AnonymizedComputerName org.gnome.Shell.desktop[1026]: failed to
load driver: ast
So MESA-LOADER complains that /usr/lib/dri/ast_dri.so is not found. This is
correct because on my machine, /usr/lib/dri doesn't exist and ast_dri.so
doesn't exist elsewhere. Does my Aspeed chip have no driver? Should I ever
need it a VGA output, don't I get it? My request is to deal with this error
message, ideally, by introducing ast_dri.so into to Debian (or making
MESA-LOADER work without it).
Bug#1035893: No sound and «pulseaudio[…]: Failed to load module "module-alsa-card"»
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 AnonymizedComputerName kernel: cx23885: cx23885[0]: alsa: registered ALSA audio device Mai 10 21:01:20 AnonymizedComputerName kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s) Mai 10 21:01:20 AnonymizedComputerName kernel: cx23885: cx23885[0]: cx23885 based dvb card Mai 10 21:01:20 AnonymizedComputerName kernel: i2c i2c-20: Added multiplexed i2c bus 23 Mai 10 21:01:20 AnonymizedComputerName kernel: a8293 20-000b: Allegro A8293 SEC successfully attached Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Started Disk Manager. Mai 10 21:01:20 AnonymizedComputerName udisksd[798]: Acquired the name org.freedesktop.UDisks2 on the system message bus Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.5666] device (wlp179s0): set-hw-addr: set MAC address to AnonymizedMACAddress (scanning) Mai 10 21:01:20 AnonymizedComputerName audit[874]: AVC apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=874 comm="cupsd" capability=12 capname="net_admin" Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Started CUPS Scheduler. Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Reached target Printer. Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Started Make remote CUPS printers available locally. Mai 10 21:01:20 AnonymizedComputerName kernel: m88rs6000t 23-0021: chip_id=64 Mai 10 21:01:20 AnonymizedComputerName colord-sane[940]: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Queued start job for default target Main User Target. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Created slice User Application Slice. Mai 10 21:01:20 AnonymizedComputerName kernel: m88rs6000t 23-0021: Montage M88RS6000 internal tuner successfully identified Mai 10 21:01:20 AnonymizedComputerName kernel: dvbdev: DVB: registering new adapter (cx23885[0]) Mai 10 21:01:20 AnonymizedComputerName kernel: cx23885 :08:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88RS6000)... Mai 10 21:01:20 AnonymizedComputerName kernel: cx23885: cx23885_dvb_register() allocating 1 frontend(s) Mai 10 21:01:20 AnonymizedComputerName kernel: cx23885: cx23885[0]: cx23885 based dvb card Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Created slice User Core Session Slice. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Reached target Paths. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Reached target Timers. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting D-Bus User Message Bus Socket. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GnuPG network certificate management daemon. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GNOME Keyring daemon. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on GnuPG cryptographic agent and passphrase cache. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on PipeWire Multimedia System Socket. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on debconf communication socket. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on Sound System. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Listening on D-Bus User Message Bus Socket. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Reached target Sockets. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Reached target Basic System. Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Started User Manager for UID 119. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Started PipeWire Multimedia Service. Mai 10 21:01:20 AnonymizedComputerName systemd[1]: Started Session c1 of user Debian-gdm. Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting Sound Service... Mai 10 21:01:20 AnonymizedComputerName kernel: i2c i2c-20: Added multiplexed i2c bus 24 Mai 10 21:01:20 AnonymizedComputerName kernel: si2168 20-0064: Silicon Labs Si2168-B40 successfully identified Mai 10 21:01:20 AnonymizedComputerName kernel: si2168 20-0064: firmware version: B 4.0.2 Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting Tracker metadata extractor... Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting Tracker file system data miner... Mai 10 21:01:20 AnonymizedComputerName kernel: si2157
Bug#1035890: NetworkManager[…]: […] sup-iface[…,0,wlp179s0]: call-p2p-cancel: failed with P2P cancel failed
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 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session[973]: gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName gnome-session-binary[973]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 21:01:20 AnonymizedComputerName wireplumber[956]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? Mai 10 21:01:20 AnonymizedComputerName wireplumber[956]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. Mai 10 21:01:20 AnonymizedComputerName dbus-daemon[962]: [session uid=119 pid=962] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor' Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Started Virtual filesystem service - disk device monitor. Mai 10 21:01:20 AnonymizedComputerName dbus-daemon[962]: [session uid=119 pid=962] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.3' (uid=119 pid=955 comm="/usr/libexec/tracker-miner-fs ") Mai 10 21:01:20 AnonymizedComputerName systemd[920]: Starting Virtual filesystem service - Apple File Conduit monitor... Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.8952] device (wlp179s0): supplicant interface state: internal-starting -> disconnected Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.8954] Wi-Fi P2P device controlled by interface wlp179s0 created Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.8962] manager: (p2p-dev-wlp179s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.8970] device (p2p-dev-wlp179s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.8985] device (wlp179s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.9002] device (p2p-dev-wlp179s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Mai 10 21:01:20 AnonymizedComputerName NetworkManager[779]: [1683745280.9007] sup-iface[64aeaff5d52037a3,0,wlp179s0]: call-p2p-cancel: failed with P2P cancel failed The last line is yellow. The output of nmcli says, in red: p2p-dev-wlp179s0: nicht verbunden "p2p-dev-wlp179s0" wifi-p2p, hw As this is a warning I feel, ergo, warned. What is it, in plain English, that I am warned about? I use Wi-Fi on wlp179s0 (the connection had its issues, but they seem to be mitigated now, so that I can send and receive e-mails such as this one) but hate to be warned about non-issues. Or, if the warning shows a real issue (about the stuff I'm not using or not knowing to be using), it should be fixed. Any remedy? Any bugfix? Gratefully, AlMa
Bug#1035889: [Pkg-utopia-maintainers] Bug#1035889: nm-dispatcher[…]: /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm: 14: .: cannot open /usr/share/tlp/tlp-func-base: No such file
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
Bug#1035889: nm-dispatcher[…]: /etc/NetworkManager/dispatcher.d/99tlp-rdw-nm: 14: .: cannot open /usr/share/tlp/tlp-func-base: No such file
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]:
[1683743307.3651] hostname: hostname changed from (none) to
"AnonymizedMachineName"
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3658] dns-mgr[0x55c99fe0b170]: init: dns=default,systemd-resolved
rc-manager=symlink (auto)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3670] rfkill0: found Wi-Fi radio killswitch (at
/sys/devices/pci:b2/:b2:00.0/:b3:00.0/ieee80211/phy0/rfkill0)
(driver iwlwifi)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3672] manager[0x55c99fe1a030]: rfkill: Wi-Fi hardware radio set
enabled
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3672] manager[0x55c99fe1a030]: rfkill: WWAN hardware radio set
enabled
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3731] Loaded device plugin: NMWwanFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wwan.so)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3755] Loaded device plugin: NMTeamFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-team.so)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3768] Loaded device plugin: NMWifiFactory
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-wifi.so)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3789] Loaded device plugin: NMBluezManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-bluetooth.so)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3797] Loaded device plugin: NMAtmManager
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-device-plugin-adsl.so)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3803] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled
by state file
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3806] manager: rfkill: WWAN enabled by radio killswitch; enabled by
state file
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3808] manager: Networking is enabled by state file
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3811] dhcp-init: Using DHCP client 'internal'
Mai 10 20:28:27 AnonymizedMachineName dbus-daemon[780]: [system] Activating via
systemd: service name='org.freedesktop.nm_dispatcher'
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0
pid=784 comm="/usr/sbin/NetworkManager --no-daemon ")
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3821] settings: Loaded settings plugin: ifupdown
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.30.6/libnm-settings-plugin-ifupdown.so")
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3822] settings: Loaded settings plugin: keyfile (internal)
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3822] ifupdown: management mode: unmanaged
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3822] ifupdown: interface-parser: parsing file
/etc/network/interfaces
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3823] ifupdown: interface-parser: source line includes interfaces
file(s) /etc/network/interfaces.d/*
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3824] ifupdown: interface-parser: parsing file
/etc/network/interfaces.d/setup
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3824] ifupdown: interface-parser: finished parsing file
/etc/network/interfaces.d/setup
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3825] ifupdown: interface-parser: finished parsing file
/etc/network/interfaces
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3832] ifupdown: guessed connection type (enp6s0) = 802-3-ethernet
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3844] ifupdown: guessed connection type (enp7s0) = 802-3-ethernet
Mai 10 20:28:27 AnonymizedMachineName systemd[1]: Starting Network Manager
Script Dispatcher Service...
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3949] device (lo): carrier: link connected
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3956] manager: (lo): new Generic device
(/org/freedesktop/NetworkManager/Devices/1)
Mai 10 20:28:27 AnonymizedMachineName dbus-daemon[780]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'
Mai 10 20:28:27 AnonymizedMachineName NetworkManager[784]:
[1683743307.3984] manager: (enp6s0): new Ethernet device
Bug#1035887: gnome-session-binary[…]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
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 tracker-miner-f[1232]: Unable to get XDG user directory path for special directory Ignoring this location. 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 tracker-miner-f[1232]: Unable to get XDG user directory path for special directory Ignoring this location. 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 tracker-miner-f[1232]: Unable to get XDG user directory path for special directory Ignoring this location. 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 tracker-miner-f[1232]: Unable to get XDG user directory path for special directory Ignoring this location. 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 rtkit-daemon[1267]: Successfully made thread 1229 of process 1229 owned by '119' high priority at nice level -11. Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Supervising 1 threads of 1 processes of 1 users. Mai 10 16:47:36 AnonymizedComputerName dbus-daemon[1236]: [session uid=119 pid=1236] Activating via systemd: service name='org.gtk.vfs.UDisks2VolumeMonitor' unit='gvfs-udisks2-volume-monitor.service' requested by ':1.2' (uid=119 pid=1232 comm="/usr/libexec/tracker-miner-fs ") Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Successfully made thread 1230 of process 1230 owned by '119' high priority at nice level -11. Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Supervising 2 threads of 2 processes of 1 users. Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Supervising 2 threads of 2 processes of 1 users. Mai 10 16:47:36 AnonymizedComputerName systemd[1206]: Starting Virtual filesystem service - disk device monitor... Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Supervising 2 threads of 2 processes of 1 users. Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Successfully made thread 1279 of process 1229 owned by '119' RT at priority 20. Mai 10 16:47:36 AnonymizedComputerName rtkit-daemon[1267]: Supervising 3 threads of 2 processes of 1 users. Mai 10 16:47:36 AnonymizedComputerName wireplumber[1233]: SPA handle 'api.bluez5.enum.dbus' could not be loaded; is it installed? Mai 10 16:47:36 AnonymizedComputerName wireplumber[1233]: PipeWire's BlueZ SPA missing or broken. Bluetooth not supported. Mai 10 16:47:36 AnonymizedComputerName gnome-session-binary[1248]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 16:47:36 AnonymizedComputerName gnome-session[1248]: gnome-session-binary[1248]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 16:47:36 AnonymizedComputerName gnome-session[1248]: gnome-session-binary[1248]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Mai 10 16:47:36 AnonymizedComputerName gnome-session-binary[1248]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed In general, failing assertions are not good. Besides this and in plain English, what does the message “GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed” tell us? Who is the culprit and what to do? Versions of the packages outputting into the log just before the error occurred: tracker-miner-fs 2.3.5-2.1, rtkit 0.13-4, dbus 1.12.24-0+deb11u1, systemd 247.3-7+deb11u2, wireplumber 0.4.2-5, gnome-session-bin 42.0-1, gnome-session 42.0-1. (The machine has many issues, which might or might not be related to this. Among them, e.g., no sound output in gnome through loudspeakers connected via a standard 3-pole 3.5 mm audio jack.) Gratefully, AlMa
Bug#1035885: iwlwifi: api flags index 2 larger than supported by driver
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 AnonymizedMachineName kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Mai 10 16:47:33 AnonymizedMachineName kernel: Intel(R) Wireless WiFi driver for Linux Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: enabling device (0100 -> 0102) Mai 10 16:47:33 AnonymizedMachineName kernel: cryptd: max_cpu_qlen set to 1000 Mai 10 16:47:33 AnonymizedMachineName kernel: AVX2 version of gcm_enc/dec engaged. Mai 10 16:47:33 AnonymizedMachineName kernel: AES CTR mode by8 optimization enabled Mai 10 16:47:33 AnonymizedMachineName kernel: cx23885: cx23885 driver version 0.0.4 loaded Mai 10 16:47:33 AnonymizedMachineName kernel: cx23885 :08:00.0: enabling device ( -> 0002) Mai 10 16:47:33 AnonymizedMachineName kernel: cx23885: CORE cx23885[0]: subsystem: 0070:f038, board: Hauppauge WinTV-HVR5525 [card=52,autodetected] Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: direct-loading firmware iwlwifi-cc-a0-59.ucode Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: api flags index 2 larger than supported by driver Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22 Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: loaded firmware version 59.601f3a66.0 cc-a0-59.ucode op_mode iwlmvm Mai 10 16:47:33 AnonymizedMachineName kernel: iwlwifi :b3:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) Mai 10 16:47:33 AnonymizedMachineName kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware What does “api flags index 2 larger than supported by driver” tell us? Is this something I should be worried about? If so, what to do? I had WiFi-connectivity issues in the past, so I wonder whether this could be a source of these issues or at least contribute to them.
Bug#1035660: Foot should display broken symbolic links in a different color than intact symlinks
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 example, in red as in xterm. For the test, see the screenshot (xterm on the left, foot on the right).
Bug#1035313: pstricks causes gray output of xdvi
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 https://i.stack.imgur.com/UYZKG.png
https://i.stack.imgur.com/UYZKG.png.
On the console,
gs:
gs: WARNING: Transparency operations ignored - need to use
-dALLOWPSTRANSPARENCY
gs:
gs:
is printed.
This is strange. The input file has no transparency whatsoever. In fact,
pstricks is not even used. Further, there's IMHO no way for xdvi to pass the
option `-dALLOWPSTRANSPARENCY` to gs. Finally, the graphical output should be
black, and not gray.
Presumably, updating texlive-pstricks or ghostscript might solve the problem,
but which versions of which packages would be the smallest to have the fix?
Versions used in this question:
• Debian package texlive 2022.20221123-1,
• Debian package texlive-binaries 2022.20220321.62855-4+b1,
• Debian package ghostscript 9.53.3~dfsg-7+deb11u4,
• `latex` has version `pdfTeX 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian)`,
• `xdvi` has version 22.87.06,
• `pstricks.sty` has version 2022/19/23 v0.72, and
• `gs` has version 9.53.3.
I don't wish to update the machine in this very bug report myself without being
advised because this might trigger newer bugs, and rollbacks sometimes failed
in the past.
Bug#1035114: The lower horizontal bar of ⋢ (U+22E2) is missing by default.
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 correct representation in gnome-characters, and on the left the wrong one in emacs. What you see on the left is the negation of ⊏, whereas you expect the negation of ⊑. In case it's a font issue, please feel free to reassign the bug report appropriately. Gratefully, Alma
Bug#1034766: systemd-udevd[…]: Failed to call EVIOCSKEYCODE with scan code 0xc022d/0xc022e, and key code 103/108: Invalid argument
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 Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-10: New USB device found, idVendor=045e, idProduct=00db, bcdDevice= 1.73 Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-10: Product: Natural® Ergonomic Keyboard 4000 Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-10: Manufacturer: Microsoft Apr 23 22:30:59 AnonymizedMachineName kernel: input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:045E:00DB.0003/input/input1 Apr 23 22:30:59 AnonymizedMachineName kernel: microsoft 0003:045E:00DB.0003: input,hidraw2: USB HID v1.11 Keyboard [Microsoft Natural® Ergonomic Keyboard 4000] on usb-:00:14.0-10/input0 Apr 23 22:30:59 AnonymizedMachineName kernel: input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:045E:00DB.0004/input/input2 Apr 23 22:30:59 AnonymizedMachineName kernel: usb 1-11: new high-speed USB device number 5 using xhci_hcd Apr 23 22:30:59 AnonymizedMachineName kernel: microsoft 0003:045E:00DB.0004: input,hidraw3: USB HID v1.11 Device [Microsoft Natural® Ergonomic Keyboard 4000] on usb-:00:14.0-10/input1 … Apr 23 22:30:59 AnonymizedMachineName systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 22:30:59 AnonymizedMachineName kernel: input: USB2.0 FHD UVC WebCam: USB2.0 F as /devices/pci:00/:00:14.0/usb1/1-11/1-11.4/1-11.4.2/1-11.4.2:1.0/input/input8 Apr 23 22:30:59 AnonymizedMachineName kernel: uvcvideo: Found UVC 1.50 device USB2.0 FHD UVC WebCam (04f2:b612) Apr 23 22:30:59 AnonymizedMachineName systemd-udevd[408]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Apr 23 22:30:59 AnonymizedMachineName kernel: input: USB2.0 FHD UVC WebCam: IR Camer as /devices/pci:00/:00:14.0/usb1/1-11/1-11.4/1-11.4.2/1-11.4.2:1.2/input/input9 Apr 23 22:30:59 AnonymizedMachineName kernel: usbcore: registered new interface driver uvcvideo Apr 23 22:30:59 AnonymizedMachineName kernel: USB Video Class driver (1.1.1) Apr 23 22:30:59 AnonymizedMachineName systemd-udevd[397]: event1: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Apr 23 22:30:59 AnonymizedMachineName systemd-udevd[397]: event1: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument The keyboard “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0” is attached to the machine in question. As for the scan codes, we indeed see ### # Microsoft ### # Microsoft Natural Ergonomic Keyboard 4000 evdev:input:b0003v045Ep00DB* KEYBOARD_KEY_c022d=up # zoomin KEYBOARD_KEY_c022e=down # zoomout in /lib/udev/hwdb.d/60-keyboard.hwdb . In plain English, what do the two messages „systemd-udevd[…]: Failed to call EVIOCSKEYCODE with scan code …, and key code …: Invalid argument“ tell us, and how should this worry us? (By the way, the way I zoom in or out using keyboard, say, in Mozilla Firefox, is via Ctrl++ and Ctrl+-. The middle slide key of the keyboard moves the contents of the window or the cursor up and down.)
Bug#1034765: [Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]
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 buffer device 128x48 Apr 23 22:30:59 AnonymizedMachineName kernel: fb0: EFI VGA frame buffer device Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: MWAIT substates: 0x2020 Apr 23 22:30:59 AnonymizedMachineName kernel: Monitor-Mwait will be used to enter C-1 state Apr 23 22:30:59 AnonymizedMachineName kernel: Monitor-Mwait will be used to enter C-2 state Apr 23 22:30:59 AnonymizedMachineName kernel: ACPI: \_SB_.SCK0.CP00: Found 2 idle states Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: v0.5.1 model 0x55 Apr 23 22:30:59 AnonymizedMachineName kernel: intel_idle: Local APIC timer is reliable in all C-states Apr 23 22:30:59 AnonymizedMachineName kernel: [Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0] What does the last message “[Firmware Bug]: APEI: Invalid physical address in GAR [0x0/64/0/4/0]” tell us in plain English, except that there's a firmware bug? Which firmware exactly is involved? Is there a real fault anywhere? The machine is stationary, has WS C422 PRO SE motherboard with Intel(R) Xeon(R) W-2235 CPU @ 3.80GHz, and runs Debian stable with a few updated packages from snapshots. Cheers, Alma
Bug#985150: systemd-udevd[…]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
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 for other reasons), I'll reopen the report. Cheers, Alma
Bug#985150: systemd-udevd[…]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
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'. Apr 23 00:34:25 AnonymousMachineName systemd-udevd[397]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Apr 23 00:34:25 AnonymousMachineName kernel: iwlwifi :b3:00.0 wlp179s0: renamed from wlan0 Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 00:34:25 AnonymousMachineName systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 00:34:25 AnonymousMachineName kernel: EDAC MC0: Giving out device to module skx_edac controller Skylake Socket#0 IMC#0: DEV :64:0a.0 (INTERRUPT) Apr 23 00:34:25 AnonymousMachineName kernel: EDAC MC1: Giving out device to module skx_edac controller Skylake Socket#0 IMC#1: DEV :64:0c.0 (INTERRUPT) Apr 23 00:34:25 AnonymousMachineName systemd-udevd[406]: Using default interface naming scheme 'v247'. Apr 23 00:34:25 AnonymousMachineName systemd-udevd[406]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Apr 23 00:34:25 AnonymousMachineName systemd-udevd[410]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device Indeed, the file and even the containing directory is absent: $ ls /sys/module/acpi_cpufreq ls: Zugriff auf '/sys/module/acpi_cpufreq' nicht möglich: Datei oder Verzeichnis nicht gefunden My nondefault lines in /etc/tlp.conf: $ egrep -v "(^$)|(^#)" /etc/tlp.conf CPU_SCALING_GOVERNOR_ON_AC=powersave CPU_SCALING_GOVERNOR_ON_BAT=powersave CPU_SCALING_MAX_FREQ_ON_AC=120 CPU_SCALING_MAX_FREQ_ON_BAT=120 DISK_SPINDOWN_TIMEOUT_ON_AC="0 241" DISK_SPINDOWN_TIMEOUT_ON_BAT="0 241" SATA_LINKPWR_ON_AC="med_power_with_dipm medium_power" SATA_LINKPWR_ON_BAT="med_power_with_dipm min_power" Still, either tlp or sysfsutils do their frequency-setting job satisfactorily: $ cat /proc/cpuinfo | grep MHz cpu MHz : 1201.105 cpu MHz : 1200.942 cpu MHz : 1200.752 cpu MHz : 1200.079 cpu MHz : 1199.669 cpu MHz : 1199.822 cpu MHz : 1200.053 cpu MHz : 1200.007 cpu MHz : 1200.144 cpu MHz : 1200.040 cpu MHz : 1199.999 cpu MHz : 1200.186 I don't wish to uninstall tlp (my version: 1.4.0-1) because otherwise the machine might run too hot for its fully passive cooling. I have no idea whether the bug is tlp-related; please feel free to reassing or retag this report if necessary. The bug might be plymouth-related though, because the offending message disappeared when I updated a few packages to their versions from snapshots, among them plymouth from 0.9.5 to 0.9.5+git20211018-1.
Bug#1034462: Pipewire: Inappropriate ioctl for device
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 the (dying) pipewire-media-session.
Bug#1034462: Pipewire: Inappropriate ioctl for device
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 AnonymizedComputerName pipewire-media-session[1236]: ms.core: error id:35 seq:256 res:-25 (Inappropriate ioctl for device): enum params id:3 (Spa:Enum:ParamId:EnumFormat) failed As the error concerns a multimedia-related piece of software (and as I have no mic-input at the moment for an unknown reason), I wonder what this error tells us? Who has done what wrong and how? By the way, as /dev/video0 is mentioned, the only way a video could be captured on my machine would be via a TV card. The TV card is connected to the antenna, and the TV tuner was not started on boot. More info: $ uname -a Linux AnonymizedComputerName 5.10.0-21-amd64 #1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux $ sudo aptitude show pipewire| grep Version Version: 0.3.56-1 $ sudo aptitude show pipewire-media-session | grep Version Version: 0.4.1-3 $ sudo lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
Bug#799603: NetworkManager: Error: failed to open /run/network/ifstate
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 `journalctl -b`; I'd really wish to know which one is no more than a printf resulting from sloppy, careless programming and which one also leads to the end-user problems at hand, whichever they may be.)
Bug#1034038: Please push babel.sty v3.87 or later into the upcoming distribution
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 supposed to succeed, please feel free to push them to Debian. (Caveat: I have not tested xetex and I have not installed texlive-full, so I can say nothing about these two packages.)
Bug#1034038: Please push babel.sty v3.87 or later into the upcoming distribution
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 babel v3.87 or later and solves https://tex.stackexchange.com/questions/680690 https://tex.stackexchange.com/questions/680690. Ideally, the update should have a chance to propagate to the upcoming stable before the final freeze. Gratefully, Alma
