Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2023-08-05 Thread Albert Nash
noowner 1026965
thanks
I don't have the laptop at my disposal any longer. Please someone else take 
ownership of the bug.
Albert.


Bug#1032974: initial-window-size-chars=80x25 in foot.ini doesn't take the data from the current monitor but from the primary one if the monitors have different resolution

2023-03-14 Thread Albert Nash
Package: foot
Version: 1.6.4-1
How to reproduce:
1. Make sure that two different-resolution monitors are connected.
2. Start gnome with wayland  from gdm3 and ensure that the high-resolution 
monitor is the primary one.
3. Open a uxterm window on the high-resolution monitor.
4. Put  initial-window-size-chars=80x25 into ~/.config/foot/foot.ini .
5. Make xterm the current window (on the hi-res monitor) and then move the 
mouse pointer away from it (on the low-res monitor) without any mouse clicks.
6. Using your keyboard, start foot from the uxterm window.
7. Notice that the foot window automatically opens on the low-resolution 
monitor (because the mouse cursor is there).
8.  Observe that 93 columns fit into the new foot window (see the screeshot).
We expect the width to be, on the contrary, 80 columns upon start. (To be fair, 
we do get 80 when you move the foot window to the hi-res monitor.)
Debug output in the uxterm window:
$ foot &
$ info: main.c:356: version: 1.6.4 +ime
info: main.c:363: arch: x86_64/64-bit
info: main.c:367: locale: de_DE.UTF-8
info: config.c:2117: loading configuration from 
/home/malkis/.config/foot/foot.ini
info: wayland.c:1169: DP-1: 2560x1440+0x0@60Hz DELL U2715H 27.15" scale=1 
PPI=111x110 (physical) PPI=111x110 (logical), DPI=108.18
info: wayland.c:1169: DP-4: 1920x1200+2560x0@60Hz SyncMaster 24.04" scale=1 
PPI=96x100 (physical) PPI=96x100 (logical), DPI=94.19
info: wayland.c:1169: DP-7: 1920x1200+4480x0@60Hz SM2443DW 24.04" scale=1 
PPI=96x100 (physical) PPI=96x100 (logical), DPI=94.19
warn: wayland.c:1330: no decoration manager available - using CSDs 
unconditionally
info: fcft.c:245: fcft: 2.3.1
info: fcft.c:255: fontconfig: 2.13.1
info: fcft.c:261: freetype: 2.10.4
info: fcft.c:671: info: 
/usr/share/fonts/truetype/dejavu/DejaVuSansMono-BoldOblique.ttf: 
size=8.00pt/12px, dpi=108.18
fcft.c:671: /usr/share/fonts/truetype/dejavu/DejaVuSansMono-Bold.ttf: 
size=8.00pt/12px, dpi=108.18
info: fcft.c:671: /usr/share/fonts/truetype/dejavu/DejaVuSansMono-Oblique.ttf: 
size=8.00pt/12px, dpi=108.18
info: fcft.c:671: /usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf: 
size=8.00pt/12px, dpi=108.18
info: terminal.c:631: cell width=7, height=15
info: terminal.c:569: using 8 rendering threads
We think that some system packages might hypothetically be involved (because 
other applications such as firefox also show strange behaviour when getting 
moved between different-resolution screens) but are unsure who exactly is the 
culprit. (Speculating, the interface could also be a problem.)


Bug#1030691: Evince crashes on an unreadable nonempty postscript file owned by root

2023-02-06 Thread Albert Nash
Package: evince
Version: 3.38.2-1
I run an up-to-date Debian GNU/Linux 11 “bullseye” with wayland.
This is how to reproduce the crash from a terminal emulator (I tried xterm, 
gnome-terminal, and foot):
root@host:/tmp# rm mwe.ps
root@host:/tmp# echo "test" > mwe.ps
root@host:/tmp# chmod g-rwx,o-rwx mwe.ps
root@host:/tmp# exit
logout
user@host:/tmp$ evince mwe.ps
Segmentation fault
An expected outcome would be a meaningful error message instead of a segfault. 
The same bug on Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421 
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910421.
Thanks in advance for repairing this bug.


Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2022-12-25 Thread Albert Nash
Btw., the number after “found [Package]” in the dmesg output might 
change depending on the boot (now the date and time are different and 
the docking station is not attached).  Now this number is 10f955a8.




Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2022-12-25 Thread Albert Nash
Below you find a portion of the output of system information from Windows 11 
concerning the hardware of the laptop (in German; please feel free to ask for 
translation into English if needed):
Systemhersteller LENOVO
Systemmodell 20T1S8EJ00
Systemtyp x64-basierter PC
System-SKU LENOVO_MT_20T1_BU_Think_FM_ThinkPad T14s Gen 1
Prozessor Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz, 2304 MHz, 4 Kern(e), 8 
logische(r) Prozessor(en)
BIOS-Version/-Datum LENOVO N2YET35W (1.24 ), 09.07.2022
SMBIOS-Version 3.2
Version des eingebetteten Controllers 1.14
BIOS-Modus UEFI
BaseBoard-Hersteller LENOVO
BaseBoard-Produkt 20T1S8EJ00
BaseBoard-Version SDK0R32862 WIN
Plattformrolle Mobil
Sicherer Startzustand Ein
PCR7-Konfiguration Erweiterung zum Anzeigen erforderlich


Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2022-12-25 Thread Albert Nash

Typo:


…  As many updates have been installed in the past, …


As many updates were installed in the past, …



Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2022-12-25 Thread Albert Nash
tags 1026965 - moreinfo
thanks
--
Thanks for a quick reaction!
The kernel.org report you've mentioned concerns a somewhat different error 
message.
As of the submission time and right now, no updates are available for my 
computer in Windows.  Both "System Update" of Lenovo (cf. the screenshot in the 
attachment) and built-in "Windows Update" (including "Optional Updates") have 
been checked.  As many updates have been installed in the past, my 
interpretation is that the system is up to date now.
Albert.
These might indicate a firmware issue, cf. eg. the older 
https://bugzilla.kernel.org/show_bug.cgi?id=199983 
https://bugzilla.kernel.org/show_bug.cgi?id=199983. Can you please check if 
there are further firwmare updates available for your device from Lenovo?


Bug#1026965: ACPI Error: Needed [Integer/String/Buffer], found [Package]

2022-12-24 Thread Albert Nash
Package: linux-image-5.10.0-20-amd64
Version: 5.10.158-2
How to reproduce:
1) Boot Debian GNU/Linux 11 (bullseye), which is „stable“ now, on Lenovo 
ThinkPad T14s Gen 1 with Intel Core i7-10610U.
2) Search for „Error“ in the output of dmesg.
3) Find
ACPI Error: Needed [Integer/String/Buffer], found [Package] 0b621212 
(20200925/exresop-469)
[ 4.387053] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for 
[OpcodeName unavailable] (20200925/dswexec-431)
[ 4.387198] ACPI Error: Aborting method \ADBG due to previous error 
(AE_AML_OPERAND_TYPE) (20200925/psparse-529)
[ 4.387346] ACPI Error: Aborting method \_SB.HIDD._DSM due to previous error 
(AE_AML_OPERAND_TYPE) (20200925/psparse-529)
[ 4.387486] ACPI: \_SB_.HIDD: failed to evaluate _DSM (0x3003)
The anonymized prefix of the dmesg output till this error is attached.
Now, since we see an “error”, we wonder what exactly goes wrong.  How do we 
translate this into plain English?  What exactly should we worry about?
Thanks in advance,
Albert
[0.00] Linux version 5.10.0-20-amd64 (debian-ker...@lists.debian.org) 
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
2.35.2) #1 SMP Debian 5.10.158-2 (2022-12-13)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-20-amd64 
root=UUID=994be375-5bdc-4b91-b60b-00f80de5f90b ro quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
[0.00] x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
[0.00] x86/fpu: Enabled xstate features 0x1f, context size is 960 
bytes, using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x9a681fff] usable
[0.00] BIOS-e820: [mem 0x9a682000-0x9e85] reserved
[0.00] BIOS-e820: [mem 0x9e86-0x9fbe9fff] ACPI NVS
[0.00] BIOS-e820: [mem 0x9fbea000-0x9fc4efff] ACPI data
[0.00] BIOS-e820: [mem 0x9fc4f000-0x9fc4] usable
[0.00] BIOS-e820: [mem 0x9fc5-0xa7ff] reserved
[0.00] BIOS-e820: [mem 0xa800-0xa8bf] usable
[0.00] BIOS-e820: [mem 0xa8c0-0xae7f] reserved
[0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00084d7f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] e820: update [mem 0x77e46018-0x77e56057] usable ==> usable
[0.00] e820: update [mem 0x77e46018-0x77e56057] usable ==> usable
[0.00] extended physical RAM map:
[0.00] reserve setup_data: [mem 0x-0x0009efff] 
usable
[0.00] reserve setup_data: [mem 0x0009f000-0x000f] 
reserved
[0.00] reserve setup_data: [mem 0x0010-0x77e46017] 
usable
[0.00] reserve setup_data: [mem 0x77e46018-0x77e56057] 
usable
[0.00] reserve setup_data: [mem 0x77e56058-0x9a681fff] 
usable
[0.00] reserve setup_data: [mem 0x9a682000-0x9e85] 
reserved
[0.00] reserve setup_data: [mem 0x9e86-0x9fbe9fff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x9fbea000-0x9fc4efff] 
ACPI data
[0.00] reserve setup_data: [mem 0x9fc4f000-0x9fc4] 
usable
[0.00] reserve setup_data: [mem 0x9fc5-0xa7ff] 
reserved
[0.00] reserve setup_data: [mem 0xa800-0xa8bf] 
usable
[0.00] reserve setup_data: [mem 0xa8c0-0xae7f] 
reserved
[0.00] reserve setup_data: [mem 0xfed2-0xfed7] 
reserved
[0.00] reserve setup_data: [mem 0x0001-0x00084d7f] 
usable
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: TPMFinalLog=0x9fbe2000 SMBIOS=0x9cc83000 SMBIOS 
3.0=0x9cc76000 ACPI=0x9fc4e000 ACPI 2.0=0x9fc4e014 MEMATTR=0x9602d018 
ESRT=0x9b107000 MOKvar=0x9601d000 RNG=0x9fc4d018 TPMEventLog=0x77e57018 
[0.00] efi: seeding entropy pool
[0.00] random: crng init done
[0.00] Kernel is locked down from EFI Secure Boot; see man 
kernel_lockdown.7
[0.00] secureboot: Secure boot enabled
[0.00] SMBIOS 3.2.

Bug#1025333: Notification with connection failure pops up despite Internet

2022-12-02 Thread Albert Nash
Package: gnome
Version: 1:3.38+3
My laptop is connected to the Internet via an Ethernet cable, which is what I 
currently want.  Connections via WiFi are in general possible but today, they 
fail  (probably because too many clients try to connect to a public wireless 
network), cf. the screenshot in the attachment. This failure doesn't hurt me.  
Still, despite already having Internet access via cable, the latop apparently 
tries to connect via WiFi and fails, displaying the notification with title 
“Verbindung gescheitert”  (German for “connection failed”) and smaller text 
“Aktivierung der Netzverbindung ist gescheitert” (German for “activation of a 
network connection has failed”) every few minutes. This popup alone alone 
hurts. How to turn it off (without turning off the WiFi)? Moreover, it is 
probably useless or even harmful in general to _automatically_ try to establish 
another Internet connection when there's one already.
More data:
$ sudo cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
Thx in advance
Albert


Bug#1021371: gnome-control-center doesn't start, saying libsamdb-common.so.0 requires version `LDB_2.2.4'

2022-10-07 Thread Albert Nash
Simon, thanks, this worked for me:
Workaround: also upgrade samba-libs to the version from testing …
It pulled, I think, also a new version of libc6. Now I finally have control 
:-). And also thanks for cleaning up the “Package:” mess I inadvertently 
created.
Cheers!
Albert


Bug#1021371: (no subject)

2022-10-06 Thread Albert Nash
severity 1021371 important
affects 1021371 - control:
affects 1021371 - severity:
affects 1021371 - important
affects 1021371 - affects
affects 1021371 - version:
affects 1021371 - -1
affects 1021371 - 1:3.38.4-1
thanks
Some more data:
$ sudo aptitude show libsmbclient | grep Version
Version: 2:4.13.13+dfsg-1~deb11u5
$ sudo aptitude show samba-libs | grep Version
Version: 2:4.13.13+dfsg-1~deb11u5
(Sorry for the mess with the header: I tried my best to say that exactly two 
packages are affected: gnome-control-center and samba-libs. Something went 
wrong with the header 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1021371;msg=5 
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1021371;msg=5; I don't 
know what.)


Bug#1021371: gnome-control-center doesn't start, saying libsamdb-common.so.0 requires version `LDB_2.2.4'

2022-10-06 Thread Albert Nash
Package: gnome-control-center Version: 1:3.38.4-1 Severity: important Control: 
affects -1 samba-libs
The control center starts neither from gnome (Alt+F1 > Settings) nor from an 
xterm. In the last case, we get some (hopefully, useful) output:
$ gnome-control-center
gnome-control-center: /lib/x86_64-linux-gnu/libldb.so.2: version `LDB_2.2.4' 
not found (required by /usr/lib/x86_64-linux-gnu/samba/libsamdb-common.so.0)
$
(I presume that some dependencies of samba-libs or gnome-control-center are 
outdated or simply wrong.) The system is Debian stable 11 “bullseye” with a few 
updated packages from Debian testing. I'd be happy if this bug report finds 
attention soon because the package, as of now, is useless to me: the control 
center won't start (e.g., I have no means to adjust printers or screens).
Thanks in advance, Albert