November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204695] [Build 20221024] openQA test fails in setitimer01
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204695 https://bugzilla.suse.com/show_bug.cgi?id=1204695#c1 Martin Doucha <martin.doucha(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.doucha(a)suse.com --- Comment #1 from Martin Doucha <martin.doucha(a)suse.com> --- The test was recently rewritten but it appears that it found a kernel bug. I've modified the test to print the wrong values returned by setitimer() in the third parameter and tried a few experiments with different timer values. The experiment works like this: new_timer = old_timer = {0}; new_timer.it_value.tv_usec = 9234; setitimer(type, &new_timer, NULL); new_timer.it_value.tv_usec = 10345; old_timer.it_value.tv_usec = 18456; setitimer(type, &new_timer, &old_timer); Here we check that old_timer.it_value.tv_usec < 18456 and fail because the kernel sets it to 19234. I've tried multiple value combinations and the kernel always set old_timer to 10000us more than it should be when the timer type is ITIMER_VIRTUAL or ITIMER_PROF. ITIMER_REAL appears to work correctly. The cloned job with modified test is here: https://openqa.opensuse.org/tests/2846894#step/setitimer01/8 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204931] New: sypder-lang should be recommended and not required by spyer
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204931 Bug ID: 1204931 Summary: sypder-lang should be recommended and not required by spyer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: wagner-thomas(a)gmx.at QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Most packages have their corresponding *-lang package as a recommended package. However, spyder on Tumbleweed 20221031 required spyder-lang. # rpm -q --whatrequires spyder-lang spyder-5.3.3-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204930] New: opencv: Segmentation fault
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204930 Bug ID: 1204930 Summary: opencv: Segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Current opencv (4.6.0) cant be imported in python because it throws a segmentation fault. As consequence, camera etc doe not work docb@X1E:~/buildservice> python3 Python 3.10.8 (main, Oct 19 2022, 07:46:20) [GCC] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import cv2 Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: /usr/lib64/libopencv_imgcodecs.so.406: undefined symbol: _ZN7Imf_3_114ChromaticitiesC1ERKN9Imath_3_14Vec2IfEES5_S5_S5_ >>> Information for package python3-opencv: --------------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : python3-opencv Version : 4.6.0-2.2 Arch : x86_64 Vendor : openSUSE Installed Size : 6.6 MiB Installed : Yes (automatically) Status : up-to-date Source package : opencv-4.6.0-2.2.src Upstream URL : https://opencv.org/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c14 --- Comment #14 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- (In reply to Thomas Zimmermann from comment #13) > Two simpledrms? I wonder where the second one comes from. Maybe one from > the DT and another one from the EFI framebuffer? But is that even possible? The bootloader, Broadcom one (not the U-Boot), is inserting simple-framebuffer compatible device into 'chosen' devicetree node at runtime. > > The logs indicate that one of the simpledrm instances created a framebuffer > device. So there should be a console on the screen. (?) Yes, there is graphical console, at least over HDMI, see comment#9. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204380] New: Swap usage going up until OOM killer kicks in
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204380 Bug ID: 1204380 Summary: Swap usage going up until OOM killer kicks in Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jgross(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my laptop running openSUSE Leap 15.4 swap usage keeps growing, until after several days processes are killed by the OOM killer. Swap usage isn't going down significantly even after stopping most use processes. After a reboot the same pattern is shown: swap usage is going up again. After 3 days running, I'm seeing 2.5GB swap used: # free total used free shared buff/cache available Mem: 32476508 28181440 749956 22399648 26361408 4295068 Swap: 33554428 2566144 30988284 # cat /proc/meminfo MemTotal: 32476508 kB MemFree: 764712 kB MemAvailable: 4309652 kB Buffers: 748 kB Cached: 25370992 kB SwapCached: 10000 kB Active: 3887988 kB Inactive: 25143556 kB Active(anon): 1726396 kB Inactive(anon): 24281868 kB Active(file): 2161592 kB Inactive(file): 861688 kB Unevictable: 778528 kB Mlocked: 13880 kB SwapTotal: 33554428 kB SwapFree: 30988284 kB Dirty: 6120 kB Writeback: 0 kB AnonPages: 4375308 kB Mapped: 536888 kB Shmem: 22399772 kB KReclaimable: 989620 kB Slab: 1231732 kB SReclaimable: 989620 kB SUnreclaim: 242112 kB KernelStack: 22832 kB PageTables: 99672 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 49792680 kB Committed_AS: 36645776 kB VmallocTotal: 34359738367 kB VmallocUsed: 67064 kB VmallocChunk: 0 kB Percpu: 7296 kB HardwareCorrupted: 0 kB AnonHugePages: 1413120 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 1328552 kB DirectMap2M: 30789632 kB DirectMap1G: 1048576 kB # uname -a Linux jglap 5.14.21-150400.24.21-default #1 SMP PREEMPT_DYNAMIC Wed Sep 7 06:51:18 UTC 2022 (974d0aa) x86_64 x86_64 x86_64 GNU/Linux # df -k | grep tmpfs devtmpfs 4096 0 4096 0% /dev tmpfs 16238252 11580 16226672 1% /dev/shm tmpfs 6495304 35264 6460040 1% /run tmpfs 4096 0 4096 0% /sys/fs/cgroup tmpfs 3247648 140 3247508 1% /run/user/1000 # ipcs -m ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x00000000 28 gross 600 393216 2 dest 0x00000000 31 gross 600 524288 2 dest 0x00000000 32 gross 600 393216 2 dest 0x00000000 35 gross 600 524288 2 dest 0x00000000 38 gross 600 524288 2 dest 0x00000000 41 gross 600 524288 2 dest Summing up different values of all processes from /proc/<pid>/smaps_rollup show much lower swap usage: Swap: 116900 KB Pss_Shmem: 51861 KB SwapPss: 96114 KB -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c13 --- Comment #13 from Thomas Zimmermann <tzimmermann(a)suse.com> --- (In reply to Ivan Ivanov from comment #12) > (In reply to Takashi Iwai from comment #11) > > > Could you check what conflicts in those memory area by looking at > > /proc/iomem? > > /proc/iomem don't show anything. > > Error starts in devm_aperture_acquire(), where simpledrm tries to > add new resource to the list of apertures, but finds that there is > already one which cover same memory region. And it looks like the > aperture was added by ... simpledrm module. Two simpledrms? I wonder where the second one comes from. Maybe one from the DT and another one from the EFI framebuffer? But is that even possible? The logs indicate that one of the simpledrm instances created a framebuffer device. So there should be a console on the screen. (?) > > simple-framebuffer simple-framebuffer.0: Conflicting range [mem > 0x3e402000-0x3ebeb000 flags 0x200] with simple-framebuffer: > 3e402000.framebuffer range: [mem 0x3e402000-0x3ebfa000 flags 0x200] > > I am not sure that is difference between simple-framebuffer.0 and > 3e402000.framebuffer devices. Above shows that when simple-framebuffer.0 > device > try to register 0x3e402000-0x3ebfa000 aperture it finds that the same was > already registred for 3e402000.framebuffer devices. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197723] New: GPG does not detect cards
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197723 Bug ID: 1197723 Summary: GPG does not detect cards Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After the last update gpg does not detect any of the 3 Yubikey cards I have. If I boot from a read only snapshot (28th), the gpg --card-status show the hw key. lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 005: ID 06cb:00da Synaptics, Inc. Bus 003 Device 004: ID 5986:212b Acer, Inc Integrated Camera Bus 003 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 003 Device 002: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID Bus 003 Device 006: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1204027] New: openSUSE Tumbleweed 20221001-0 -> 20221003-0 forcefully installed lots of KDE patterns
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204027 Bug ID: 1204027 Summary: openSUSE Tumbleweed 20221001-0 -> 20221003-0 forcefully installed lots of KDE patterns Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper dup ... and the KDE patterns that I manually disabled during the first OS installation are forcefully installed now (kde-pim, kde-games, kde-multimedia, libre-office) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1183962] New: System freeze when wake up from sleep
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183962 Bug ID: 1183962 Summary: System freeze when wake up from sleep Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Machine: Laptop E14 Gen2 When computer wakes up from sleep the whole system freeze. I tried adding snd_hda_codec_hdmi.enable_silent_stream=0 to kernel boot parameters as described in #1180651, but still no luck. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1180884] New: Powerdevil skipping reload action as profile has not changed
by bugzilla_noreply＠suse.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180884 Bug ID: 1180884 Summary: Powerdevil skipping reload action as profile has not changed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cosmin.tanczel(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have configured powerdevil to change brightness level while on battery. When I remove the power adapter, the battery icons becomes visible in Systray, meaning the system detected that the power cable was removed. But when I hover the mouse on the battery icon the info I got is that the power adapter is still plugged in. Also, I have no message in /var/log/message when I remove the power adapter. When I plug in the power adapter, the battery icon gets hidden, meaning the system recognized that the power adapter was plugged in and I also got the following messages in /var/log/messages: 2021-01-13T14:34:30.349152+02:00 localhost org_kde_powerdevil[2135]: powerdevil: Can't contact ck 2021-01-13T14:34:30.349227+02:00 localhost org_kde_powerdevil[2135]: powerdevil: Currently using activity "b1627b23-a919-40b9-8110-0dc6c8742ebd" 2021-01-13T14:34:30.349250+02:00 localhost org_kde_powerdevil[2135]: powerdevil: () () 2021-01-13T14:34:30.349268+02:00 localhost org_kde_powerdevil[2135]: powerdevil: () () 2021-01-13T14:34:30.349286+02:00 localhost org_kde_powerdevil[2135]: powerdevil: Loading profile for plugged AC 2021-01-13T14:34:30.349310+02:00 localhost org_kde_powerdevil[2135]: powerdevil: Activity is not forcing a profile 2021-01-13T14:34:30.349331+02:00 localhost org_kde_powerdevil[2135]: powerdevil: Skipping action reload routine as profile has not changed 2021-01-13T14:34:35.424074+02:00 localhost kernel: [ 3374.931800] ucsi_acpi USBC000:00: UCSI_GET_PDOS returned 0 bytes Machine: Lenovo ThinkPad E14 System: Kernel: 5.3.18-40-default x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-40-default root=UUID=c7a347e6-8c45-438a-a0b2-11eaaa6dd968 splash=silent quiet mitigations=off Desktop: KDE Plasma 5.18.6 tk: Qt 5.12.7 wm: kwin_x11 dm: SDDM Distro: openSUSE Leap 15.3 Alpha Machine: Type: Laptop System: LENOVO product: 20TA002GRI v: ThinkPad E14 Gen 2 serial: <filter> Chassis: type: 10 serial: <filter> Mobo: LENOVO model: 20TA002GRI serial: <filter> UEFI: LENOVO v: R1EET31W(1.31 ) date: 12/01/2020 Battery: ID-1: BAT0 charge: 45.6 Wh condition: 47.0/45.0 Wh (105%) volts: 12.4/11.1 model: Sunwoda 5B10X025 type: Li-poly serial: <filter> status: Unknown cycles: 4 Device-1: hidpp_battery_0 model: Logitech Marathon Mouse/Performance Plus M705 serial: <filter> charge: 55% (should be ignored) rechargeable: yes status: Discharging -- You are receiving this mail because: You are on the CC list for the bug.

1 1