February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208198] Tumbleweed from 20230213 (glibc 2.37) has stack protector triggering in libdl of libGLX_nvidia.so.0
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208198 http://bugzilla.opensuse.org/show_bug.cgi?id=1208198#c19 patrick shanahan <paka(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #19 from patrick shanahan <paka(a)opensuse.org> --- doesn't fix for me added /etc/ld.so.conf.d/nvidia.conf w/contents: /usr/lib64/tls /usr/lib/tls rebooted also Tumbleweed: move the latest libnvidia-tls.so (previously installed to /usr/lib{,64}/tls) to /usr/lib{,64} rebooted Xorg.0.log [ 183.767] X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 [ 184.005] Current Operating System: Linux crash.wahoo.no-ip.org 6.1.10-1-default #1 SMP PREEMPT_DYNAMIC Mon Feb 6 07:27:26 UTC 2023 (2a$ [ 184.006] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.1.10-1-default root=UUID=94757ae2-29cb-44c5-a9eb-5c2c42f93189 splash=verbose p$ [ 184.261] [ 184.347] Current version of pixman: 0.42.2 [ 184.523] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 184.523] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 184.881] (==) Log file: "/home/paka/.local/share/xorg/Xorg.0.log", Time: Sat Feb 11 11:35:45 2023 [ 184.973] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 185.066] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 185.066] (==) No Layout section. Using the first Screen section. [ 185.066] (==) No screen section available. Using defaults. [ 185.066] (**) |-->Screen "Default Screen Section" (0) [ 185.066] (**) | |-->Monitor "<default monitor>" [ 185.066] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 185.066] (**) Option "IgnoreABI" "true" [ 185.066] (**) Ignoring ABI Version [ 185.066] (==) Automatically adding devices [ 185.066] (==) Automatically enabling devices [ 185.066] (==) Automatically adding GPU devices [ 185.066] (==) Automatically binding GPU devices [ 185.066] (==) Max clients allowed: 512, resource mask: 0xfffff [ 185.066] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 185.066] Entry deleted from font path. [ 185.066] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/truetype/, built-ins [ 185.066] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 185.066] (WW) Ignoring unrecognized extension "XFree86-DGA" [ 185.066] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 185.066] (II) Loader magic: 0x5636bdf49ac0 [ 185.066] (II) Module ABI versions: [ 185.066] X.Org ANSI C Emulation: 0.4 [ 185.066] X.Org Video Driver: 25.2 [ 185.066] X.Org XInput driver : 24.4 [ 185.066] X.Org Server Extension : 10.0 [ 185.067] (--) using VT number 3 [ 185.067] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 185.068] (II) xfree86: Adding drm device (/dev/dri/card0) [ 185.068] (II) Platform probe for /sys/devices/pci0000:00/0000:00:03.0/0000:03:00.0/drm/card0 [ 185.073] (--) PCI:*(3@0:0:0) 10de:0dc4:196e:085a rev 161, Mem @ 0xd0000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0$ [ 185.073] (II) LoadModule: "glx" [ 185.074] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 185.077] (II) Module glx: vendor="NVIDIA Corporation" [ 185.077] compiled for 4.0.2, module version = 1.0.0 [ 185.077] Module class: X.Org Server Extension [ 185.077] (II) NVIDIA GLX Module 390.157 Wed Oct 12 09:19:15 UTC 2022 [ 185.078] (II) Scanning /usr/share/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers [ 185.078] (II) Scanning /usr/share/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers [ 185.078] (==) Matched nvidia as autoconfigured driver 0 [ 185.078] (==) Matched nouveau as autoconfigured driver 1 [ 185.078] (==) Matched nv as autoconfigured driver 2 [ 185.078] (==) Matched modesetting as autoconfigured driver 3 [ 185.078] (==) Matched fbdev as autoconfigured driver 4 [ 185.078] (==) Matched vesa as autoconfigured driver 5 [ 185.078] (==) Assigned the driver to the xf86ConfigLayout [ 185.078] (II) LoadModule: "nvidia" [ 185.078] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 185.078] (II) Module nvidia: vendor="NVIDIA Corporation" [ 185.078] compiled for 4.0.2, module version = 1.0.0 [ 185.078] Module class: X.Org Video Driver [ 185.078] (II) LoadModule: "nouveau" [ 185.078] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 185.078] (II) Module nouveau: vendor="X.Org Foundation" [ 185.078] compiled for 1.21.1.4, module version = 1.0.17 [ 185.078] Module class: X.Org Video Driver [ 185.078] ABI class: X.Org Video Driver, version 25.2 [ 185.078] (II) LoadModule: "nv" [ 185.079] (II) Loading /usr/lib64/xorg/modules/drivers/nv_drv.so [ 185.079] (EE) Failed to load /usr/lib64/xorg/modules/drivers/nv_drv.so: /usr/lib64/xorg/modules/drivers/nv_drv.so: undefined symbol: fb$ [ 185.079] (EE) Failed to load module "nv" (loader failed, 0) [ 185.079] (II) LoadModule: "modesetting" [ 185.079] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 185.079] (II) Module modesetting: vendor="X.Org Foundation" [ 185.079] compiled for 1.21.1.7, module version = 1.21.1 [ 185.079] Module class: X.Org Video Driver [ 185.079] ABI class: X.Org Video Driver, version 25.2 [ 185.079] (II) LoadModule: "fbdev" [ 185.079] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 185.079] (II) Module fbdev: vendor="X.Org Foundation" [ 185.079] compiled for 1.21.1.4, module version = 0.5.0 [ 185.079] Module class: X.Org Video Driver [ 185.079] ABI class: X.Org Video Driver, version 25.2 [ 185.079] (II) LoadModule: "vesa" [ 185.079] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 185.079] (II) Module vesa: vendor="X.Org Foundation" [ 185.079] compiled for 1.21.1.6, module version = 2.6.0 [ 185.079] Module class: X.Org Video Driver [ 185.079] ABI class: X.Org Video Driver, version 25.2 [ 185.079] (II) NVIDIA dlloader X Driver 390.157 Wed Oct 12 09:21:41 UTC 2022 [ 185.079] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 185.079] (II) NOUVEAU driver [ 185.079] (II) NOUVEAU driver for NVIDIA chipset families : [ 185.079] RIVA TNT (NV04) [ 185.079] RIVA TNT2 (NV05) [ 185.079] GeForce 256 (NV10) [ 185.079] GeForce 2 (NV11, NV15) [ 185.079] GeForce 4MX (NV17, NV18) [ 185.079] GeForce 3 (NV20) [ 185.079] GeForce 4Ti (NV25, NV28) [ 185.079] GeForce FX (NV3x) [ 185.079] GeForce 6 (NV4x) [ 185.079] GeForce 7 (G7x) [ 185.079] GeForce 8 (G8x) [ 185.079] GeForce 9 (G9x) [ 185.079] GeForce GTX 2xx/3xx (GT2xx) [ 185.079] GeForce GTX 4xx/5xx (GFxxx) [ 185.079] GeForce GTX 6xx/7xx (GKxxx) [ 185.079] GeForce GTX 9xx (GMxxx) [ 185.079] GeForce GTX 10xx (GPxxx) [ 185.079] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 185.079] (II) FBDEV: driver for framebuffer: fbdev [ 185.079] (II) VESA: driver for VESA chipsets: vesa [ 185.080] (EE) Fatal server error: [ 185.265] (EE) xf86OpenConsole: Cannot open virtual console 3 (Permission denied) [ 185.359] (EE) [ 185.454] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 185.835] (EE) Please also check the log file at "/home/paka/.local/share/xorg/Xorg.0.log" for additional information. [ 185.935] (EE) [ 186.136] (WW) xf86CloseConsole: KDSETMODE failed: Bad file descriptor [ 186.136] (WW) xf86CloseConsole: VT_GETMODE failed: Bad file descriptor [ 186.136] (EE) Server terminated with error (1). Closing log file. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208069] Leap 15.5 & Gecko rolling plasma does not revive video from suspend?
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208069 https://bugzilla.suse.com/show_bug.cgi?id=1208069#c6 --- Comment #6 from Fritz Hudnut <non.space.1(a)gmail.com> --- I just found a bug report I filed on Leap 15.5 GUI freezing back in Nov '22, doesn't seem like it was "solved" via the bug report, but it might show "line of inquiry" . . . other similarity is the "XFCE" component. https://bugzilla.suse.com/show_bug.cgi?id=1205452 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c19 --- Comment #19 from Jiri Slaby <jslaby(a)suse.com> --- If -next doesn't help, it might help to see debugging messages from mhi. It's very weird that it didn't time out as Takashi noted (the timeout_ms config). Adding mhi.dyndbg=+p to the kernel commandline will do the job. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197063] New: VUL-0: CVE-2022-24128: timescaledb: allow privilege escalation during extension installation
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197063 Bug ID: 1197063 Summary: VUL-0: CVE-2022-24128: timescaledb: allow privilege escalation during extension installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/326113/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bruno(a)ioda-net.ch Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2022-24128 Timescale TimescaleDB 1.x and 2.x before 2.5.2 may allow privilege escalation during extension installation. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-24128 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24128 http://www.cvedetails.com/cve/CVE-2022-24128/ https://docs.timescale.com/timescaledb/latest/overview/release-notes/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1207387] New: mdam : monitoring detected DeviceDisappeared
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207387 Bug ID: 1207387 Summary: mdam : monitoring detected DeviceDisappeared Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: holgerbruenjes(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello it ist the package mdadm-4.2-5.1.src.rpm from tumbleweed I use the mdadm tool also in the past my mdadm.conf cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md1 UUID=6c9f3d38:ada07516:3d186b3c:53958f34 ARRAY /dev/md/2 metadata=1.2 UUID=6bb43ca5:fab488e0:590a1132:6d893542 name=(none):2 ARRAY /dev/md/3 metadata=1.2 UUID=af96a8a7:8355bc0e:7e877926:835dd720 name=(none):3 PROGRAM /usr/libexec/mdadm/mdadm-event-handler.sh eis-5351:/ # eis-5351:/ # cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] md3 : active raid1 sdb3[0] sda3[1] 312198464 blocks super 1.2 [2/2] [UU] bitmap: 2/3 pages [8KB], 65536KB chunk md2 : active raid1 sdb2[0] sda2[1] 130048 blocks super 1.2 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md1 : active raid1 sdb1[0] sda1[1] 98240 blocks [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: <none> eis-5351:/ # ll /dev/md* brw-rw---- 1 root disk 9, 1 2023-01-23 09:38 /dev/md1 brw-rw---- 1 root disk 9, 2 2023-01-23 09:38 /dev/md2 brw-rw---- 1 root disk 9, 3 2023-01-23 09:38 /dev/md3 /dev/md: total 0 lrwxrwxrwx 1 root root 6 2023-01-23 09:38 2 -> ../md2 lrwxrwxrwx 1 root root 6 2023-01-23 09:38 3 -> ../md3 eis-5351:/ # blkid /dev/sda1: UUID="6c9f3d38-ada0-7516-3d18-6b3c53958f34" TYPE="linux_raid_member" PARTLABEL="boot" PARTUUID="30c4a077-5317-452e-9790-38907f0e2c23" /dev/sda2: UUID="6bb43ca5-fab4-88e0-590a-11326d893542" UUID_SUB="433c3917-8a67-201f-9cc6-488bc3cd40e5" LABEL="(none):2" TYPE="linux_raid_member" PARTLABEL="swap" PARTUUID="e29917a8-1adb-468d-bd89-45881e64e68f" /dev/sda3: UUID="af96a8a7-8355-bc0e-7e87-7926835dd720" UUID_SUB="d92de6c9-7df5-007a-cf88-4cbb7ca9a315" LABEL="(none):3" TYPE="linux_raid_member" PARTLABEL="root" PARTUUID="6bc85123-3938-4e6e-b8b2-1fa47786b66a" /dev/sdb1: UUID="6c9f3d38-ada0-7516-3d18-6b3c53958f34" TYPE="linux_raid_member" PARTLABEL="boot" PARTUUID="5c3f7a62-f9ad-4500-9ef3-3f736249b0e5" /dev/sdb2: UUID="6bb43ca5-fab4-88e0-590a-11326d893542" UUID_SUB="0b6cc352-863b-e379-5808-43b9e578c451" LABEL="(none):2" TYPE="linux_raid_member" PARTLABEL="swap" PARTUUID="9d942155-db32-4e57-ad42-4b331c76ac06" /dev/sdb3: UUID="af96a8a7-8355-bc0e-7e87-7926835dd720" UUID_SUB="bd272b7c-b5b6-efea-9375-e5d830899a38" LABEL="(none):3" TYPE="linux_raid_member" PARTLABEL="root" PARTUUID="3f876df5-8321-4e80-8de2-fd9101e1e620" /dev/md1: UUID="30b5bb75-d24e-4da1-ac44-982964ce4249" BLOCK_SIZE="1024" TYPE="ext4" /dev/md2: UUID="9b09c4e7-14ea-4800-a4b2-8074b59c8de2" TYPE="swap" /dev/md3: UUID="efd4a549-d390-4146-9125-546edd68cf60" BLOCK_SIZE="4096" TYPE="ext4" I use this test cmd mdadm --monitor --oneshot --scan --test and now it triggered 6 mail ------------------- Dispatched from mdadm Agent on Server 'eis-5351' Current Date: 2023-01-21 Time: 21:40:45 Host : eis-5351 MD Device : /dev/md/3 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/2 Event : TestMessage ... this device never existed and it cannot have disappeared as a result. Host : eis-5351 MD Device : /dev/md/md1 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/md1 Event : DeviceDisappeared ... Host : eis-5351 MD Device : /dev/md1 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md1 Event : NewArray -------------------------- and after boot it triggerd 1 mail Host : eis-5351 MD Device : /dev/md1 Event : NewArray -------------------- in the past with mdadm 4.1-13.2 it triggered 3 mail --------------- Dispatched from mdadm Agent on Server 'eis-5351' Current Date: 2023-01-21 Time: 16:38:13 Host : eis-5351 MD Device : /dev/md/3 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md/2 Event : TestMessage ... Host : eis-5351 MD Device : /dev/md1 Event : TestMessage ---------------------------------- it this now a feature or a bug I detected his patch for the problem 0029-Monitor-use-snprintf-to-fill-device-name.patch it contained your vote Signed-off-by: Coly Li <colyli(a)suse.de> and drop adding this patch, as a result the patches 0046 and 0051 cannot be added, but i can't tell if the patches were just a consequence problem Thanks Holger -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1208243] New: openssh/sshd creates duplicates entries in wtmp
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208243 Bug ID: 1208243 Summary: openssh/sshd creates duplicates entries in wtmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- sshd creates at minimum duplicate entries in wtmp: kukuk pts/0 fd21:4d9a:50d0:b Fri Feb 10 12:44 - 14:14 (01:30) kukuk ssh fd21:4d9a:50d0:b Fri Feb 10 12:44 - 14:14 (01:30) That's because sshd writes itself to the same files as pam_lastlog is doing. Solution is to remove pam_lastlog from PAM config for sshd. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1208217] [Build 20230213] LXQt not installable on snapshot 0213
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208217 https://bugzilla.suse.com/show_bug.cgi?id=1208217#c1 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Michael Vetter <mvetter(a)suse.com> --- Upstream: https://github.com/lxqt/lxqt-config/issues/903 lxqt-build-tools: SR#1065746 lxqt-config: SR#1065747 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203982] tcl FTBFS in 2038
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1203982 https://bugzilla.suse.com/show_bug.cgi?id=1203982#c5 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Reinhard Max <max(a)suse.com> --- Thanks, closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207150] New: jhead autorot broken
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207150 Bug ID: 1207150 Summary: jhead autorot broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: tuxuser(a)quantentunnel.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864125 --> http://bugzilla.opensuse.org/attachment.cgi?id=864125&action=edit example file for jhead autorot bug OS: openSUSE Leap 15.4, all updates installed Kernel: 5.14.21-150400.38-default Problem: jhead -autorot breaks exif info The bug occurs with the patched version 3.06.0.1-bp154.2.3.1 and the latest version ...-bp154.261. There is no problem with the original version ...-bp154.1.20 Put the attached photo into a new directory and run jhead -autorot * This will rotate the photo as expected but will kill every exif info such as camera, exposure gps,... There is also an error message "Nonfatal Error : 'DSC08058.JPG' Command has invalid characters." -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1207150] jhead autorot broken
by bugzilla_noreply＠suse.com 14 Feb '23

14 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207150 https://bugzilla.suse.com/show_bug.cgi?id=1207150#c8 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Petr Gajdos <pgajdos(a)suse.com> --- Packages submitted: TW,b15sp4/jhead. I believe all fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0