February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1041742] transfiletriggerin and transfiletriggerpostun are not executed by libzypp
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1041742 https://bugzilla.suse.com/show_bug.cgi?id=1041742#c32 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com --- Comment #32 from Martin Wilck <martin.wilck(a)suse.com> --- I was hoping to be able to use %transfiletriggerun to solve bug 1195291 (on SLE/Leap). This bug here would prevent that solution. (In reply to Michael Andres from comment #7) > Most packages solve this via %posttrans. Libzypp uses '--noposttrans' as we > manually collect the posttrans scripts and execute them after _all_ packages > were installed. But we can't do this for filetriggers. Why not? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|guillaume.gardet(a)arm.com |screening-team-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207562] U-Boot: Raspberry Pi 4 booting from USB stopped booting
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207562 https://bugzilla.suse.com/show_bug.cgi?id=1207562#c20 --- Comment #20 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- Here, it works just fine with a Raspberry Pi 4 - 8GB with openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.aarch64-2023.01.09-Snapshot20230130.raw 'bdinfo' output: boot_params = 0x0000000000000100 DRAM bank = 0x0000000000000000 -> start = 0x0000000000000000 -> size = 0x000000003df00000 DRAM bank = 0x0000000000000001 -> start = 0x0000000040000000 -> size = 0x00000000bc000000 flashstart = 0x0000000000000000 flashsize = 0x0000000000000000 flashoffset = 0x0000000000000000 baudrate = 115200 bps relocaddr = 0x000000003dc3c000 reloc off = 0x000000003dbbc000 Build = 64-bit current eth = ethernet@7d580000 ethaddr = dc:a6:32:fb:c1:bd IP addr = <NULL> fdt_blob = 0x000000003d82a830 new_fdt = 0x000000003d82a830 fdt_size = 0x000000000000d540 Video = hdmi@7ef00700 inactive lmb_dump_all: memory.cnt = 0x2 memory[0] [0x0-0x3defffff], 0x3df00000 bytes flags: 0 memory[1] [0x40000000-0xfbffffff], 0xbc000000 bytes flags: 0 reserved.cnt = 0x5 reserved[0] [0x0-0xfff], 0x00001000 bytes flags: 0 reserved[1] [0x3c81e000-0x3defffff], 0x016e2000 bytes flags: 0 reserved[2] [0x3d826390-0x3dcfffff], 0x004d9c70 bytes flags: 0 reserved[3] [0x3ee62aa0-0x3ee62ae7], 0x00000048 bytes flags: 4 reserved[4] [0x40000000-0xfbffffff], 0xbc000000 bytes flags: 0 devicetree = board arch_number = 0x0000000000000000 TLB addr = 0x000000003dcf0000 irq_sp = 0x000000003d82a820 sp start = 0x000000003d82a820 Early malloc usage: 920 / 2000 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207847] New: Unable to run salt commands
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207847 Bug ID: 1207847 Summary: Unable to run salt commands Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Salt Assignee: salt-maintainers(a)suse.de Reporter: rdouman(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I get the following stack trace when running "salt '*' state.apply" : The minion function caused an exception: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/salt/minion.py", line 1939, in _thread_return return_data = minion_instance._execute_job_function( File "/usr/lib/python3.10/site-packages/salt/minion.py", line 1898, in _execute_job_function return_data = self.executors[fname](opts, data, func, args, kwargs) File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 149, in __call__ return self.loader.run(run_func, *args, **kwargs) File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 1230, in run return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs) File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 1245, in _run_as return _func_or_method(*args, **kwargs) File "/usr/lib/python3.10/site-packages/salt/executors/transactional_update.py", line 123, in execute opts, data, __salt__[DELEGATION_MAP[fun]], args, kwargs File "/usr/lib/python3.10/site-packages/salt/loader/context.py", line 78, in __getitem__ return self.value()[item] File "/usr/lib/python3.10/site-packages/salt/loader/lazy.py", line 336, in __getitem__ super().__getitem__(item) # try to get the item from the dictionary File "/usr/lib/python3.10/site-packages/salt/utils/lazy.py", line 105, in __getitem__ raise KeyError(key) KeyError: 'transactional_update.apply' -- Versions report: Salt Version: Salt: 3005.1 Dependency Versions: cffi: 1.15.1 cherrypy: Not Installed dateutil: 2.8.2 docker-py: Not Installed gitdb: Not Installed gitpython: Not Installed Jinja2: 3.1.2 libgit2: 1.5.0 M2Crypto: 0.38.0 Mako: Not Installed msgpack: 1.0.4 msgpack-pure: Not Installed mysql-python: Not Installed pycparser: 2.21 pycrypto: Not Installed pycryptodome: Not Installed pygit2: 1.11.1 Python: 3.10.9 (main, Dec 08 2022, 14:49:06) [GCC] python-gnupg: Not Installed PyYAML: 6.0 PyZMQ: 24.0.1 smmap: Not Installed timelib: Not Installed Tornado: 4.5.3 ZMQ: 4.3.4 System Versions: dist: opensuse-microos 20230131 locale: utf-8 machine: x86_64 release: 6.1.8-1-default system: Linux version: openSUSE MicroOS 20230131 OS Version NAME="openSUSE MicroOS" # VERSION="20230131" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed" VERSION_ID="20230131" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20230131" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" Everything worked before the upgrade on version 3004. I've also done a fresh install of the OS on a test server, installed salt-master and salt-minion, but the issue still occurs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207840] Mesa/intel: xterm cursor is missing 1 pixel (2D Accel/GLamor issue)
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207840 https://bugzilla.suse.com/show_bug.cgi?id=1207840#c10 --- Comment #10 from Stefan Dirsch <sndirsch(a)suse.com> --- https://gitlab.freedesktop.org/xorg/xserver/-/issues -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207840] Mesa/intel: xterm cursor is missing 1 pixel (2D Accel/GLamor issue)
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207840 https://bugzilla.suse.com/show_bug.cgi?id=1207840#c9 --- Comment #9 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. But with that this no longer looks driver related and probably needs to be discussed upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207840] Mesa/intel: xterm cursor is missing 1 pixel (2D Accel/GLamor issue)
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207840 https://bugzilla.suse.com/show_bug.cgi?id=1207840#c8 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jengelh(a)inai.de) | --- Comment #8 from Jan Engelhardt <jengelh(a)inai.de> --- Created attachment 864684 --> https://bugzilla.suse.com/attachment.cgi?id=864684&action=edit demo prog 00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01) 00:02.0 0300: 8086:9a49 (rev 01) But I think I figured it out. GL drawing does butt caps, whereas programs exercising bitmap drawing functionality expect square caps. ( https://archive.flossmanuals.net/inkscape/_booki/inkscape/static/Inkscape-S… ) A demo program is attached for your viewing pleasure. Butt caps have the issue that they terminate in the middle of a pixel, so there's always an unfortunate rounding decision made. The fix for glamor should be easy, let me experiment a bit more�� -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207840] New: xterm cursor is missing 1 pixel
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207840 Bug ID: 1207840 Summary: xterm cursor is missing 1 pixel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: jengelh(a)inai.de QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864675 --> http://bugzilla.opensuse.org/attachment.cgi?id=864675&action=edit Observed cursor where the lower right pixel is missing Observed ======== When I execute `xterm -uc`, the text cursor is missing 1 pixel in the lower right corner. Expected ======== Draw a complete rectangle. Implementation detail ===================== The cursor is an X11 polyline primitive consisting of 5 points, the first which is the starting point (relative to the X window), and the remaining 4 coordinates are relative movements. The VTbox array looks something like {{540,300},{16,0},{0,1},{-16,0},{0,-1}} so that's an origin, a move to the right as wide as the character cell is, one pixel row down, same move back to the left, and one up, completing the rectangle. The xterm underline cursor is always therefore 2 pixels thick. https://salsa.debian.org/xorg-team/app/xterm/-/blob/debian-unstable/fontuti… is the place where the relative movements are initially set (they stay the same during program execution obviously). https://salsa.debian.org/xorg-team/app/xterm/-/blob/debian-unstable/charpro… is the place where the origin coordinate is updated as the cursor is moved. The {-16,0} instruction seems to be misbehaving. See first attachment of this report for a screenshot. Debugging so far ================ * Leap 15.4 on real hw: FINE * openSUSE-Tumbleweed-XFCE-Live-x86_64-Snapshot20230131-Media.iso on real hw: BROKEN * same XFCE-Live inside Virtualbox: FINE -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1207840] xterm cursor is missing 1 pixel
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207840 https://bugzilla.suse.com/show_bug.cgi?id=1207840#c4 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |sndirsch(a)suse.de --- Comment #4 from Jan Engelhardt <jengelh(a)inai.de> --- rm -f /usr/lib64/xorg/modules/libglamoregl.so this fixes the issue on TW. Allow me to re-assign this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207763] New: Since 5.14.21-150400.24.41-default, machine fails to recover from hibernation.
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207763 Bug ID: 1207763 Summary: Since 5.14.21-150400.24.41-default, machine fails to recover from hibernation. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the last update, the machine fails on recovery from hibernation. It goes to boot instead. I will attach "journalctl -b0" and "journalctl --boot=-1", editing the central part out for privacy (emails and such). Core: Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 80% Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 90% Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 100% Jan 30 11:30:35 Telcontar kernel: PM: Image loading done Jan 30 11:30:35 Telcontar kernel: PM: hibernation: PM: secret key is invalid Jan 30 11:30:35 Telcontar kernel: PM: hibernation: PM: Hibernation trampoline page prepared Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Read 17090332 kbytes in 16.95 seconds (1008.27 MB/s) Jan 30 11:30:35 Telcontar kernel: PM: Image successfully loaded Jan 30 11:30:35 Telcontar kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 30 11:30:35 Telcontar kernel: serial 00:05: disabled Jan 30 11:30:35 Telcontar kernel: PM: pci_pm_freeze(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 Jan 30 11:30:35 Telcontar kernel: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xd0 returns -16 Jan 30 11:30:35 Telcontar kernel: xhci_hcd 0000:29:00.3: PM: failed to quiesce async: error -16 Jan 30 11:30:35 Telcontar kernel: xhci_hcd 0000:03:00.0: xHC error in resume, USBSTS 0x401, Reinit Jan 30 11:30:35 Telcontar kernel: usb usb1: root hub lost power or was reset Jan 30 11:30:35 Telcontar kernel: usb usb2: root hub lost power or was reset Jan 30 11:30:35 Telcontar kernel: serial 00:05: activated Jan 30 11:30:35 Telcontar kernel: nvme nvme0: Shutdown timeout set to 8 seconds Jan 30 11:30:35 Telcontar kernel: nvme nvme0: 32/0/0 default/read/poll queues Jan 30 11:30:35 Telcontar kernel: ata9: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata5: SATA link down (SStatus 0 SControl 330) Jan 30 11:30:35 Telcontar kernel: ata10: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata7: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata6: SATA link down (SStatus 0 SControl 330) Jan 30 11:30:35 Telcontar kernel: usb 1-13: reset low-speed USB device number 2 using xhci_hcd Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Failed to load image, recovering. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Basic memory bitmaps freed Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) -- You are receiving this mail because: You are on the CC list for the bug.

1 13