October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are on the CC list for the bug.

1 27

[Bug 1202269] New: supportconfig does not include expected YaST logs
by bugzilla_noreply＠suse.com 20 Dec '22

20 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1202269 Bug ID: 1202269 Summary: supportconfig does not include expected YaST logs 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: dgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- We've notice that expected YaST logs aren't being (fully) included in recently attached supportconfig files. For example, we miss the content of the /var/log/YaST2/y2log. After taking a look at the code, we think it could be because of a recent change in `conf_files`. Please, have a look at the issue created in the supportconfig's Github project, https://github.com/openSUSE/supportutils/issues/134 -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1168405] New: adjust issue handling to new agetty
by bugzilla_noreply＠novell.com 20 Dec '22

20 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1168405 Bug ID: 1168405 Summary: adjust issue handling to new agetty 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- agetty from util-linux 2.35 (not yet packaged) supports reading issue files from /run and /usr in the following way: if /etc/issue exists: read /etc/issue and /etc/issue.d else if /run/issue exists or /run/issue.d has any files read those else read /usr/lib/issue read /usr/lib/issue.d Moreover, the \4 and \6 escape codes use the first configured interface to print the IP address. That means for the most useful default case we don't need to run the extra code of issue generator to enumerate network interfaces and merge issue files anymore. We can rely on agetty built-in features only. Those who need the extra features to print ssh keys or custom computed stuff could still install issue-generator. So I propose the following change: - don't hard require issue-generator in openSUSE-release - don't ship /etc/issue - ship /usr/lib/issue.d/10-openSUSE.issue with the following content: Welcome to \S{PRETTY_NAME} \S{VERSION_ID} - Kernel \r (\l). \4 \6 -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1189991] New: qt5 rcc error: No data signature found
by bugzilla_noreply＠suse.com 20 Dec '22

20 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189991 Bug ID: 1189991 Summary: qt5 rcc error: No data signature found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- build log: [ 104s] g++ -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type -flto=auto -DOPENSSL_LOAD_CONF -g -Wall -fprofile-arcs -ftest-coverage -fno-access-control -O0 -O2 -std=gnu++11 -pthread -Wall -Wextra -D_REENTRANT -fPIC -DVERSION=5.9.13 -DQT_NO_DEBUG_OUTPUT -DQT_DEPRECATED_WARNINGS -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_DBUS_LIB -DQT_TESTLIB_LIB -DQT_CORE_LIB -DQT_TESTCASE_BUILDDIR='"/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests"' -c ./qrc_files.cpp -o ./qrc_files.tmp.o [ 104s] /usr/lib64/qt5/bin/rcc -name files files.qrc -pass 2 -temp ./qrc_files.tmp.o -o qrc_files.o [ 104s] No data signature found [ 104s] make[1]: *** [Makefile:884: qrc_files.o] Error 1 [ 104s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests' [ 105s] make[1]: Entering directory '/home/abuild/rpmbuild/BUILD/deepin-reader-5.9.13/tests' Removing resources_big from .pro can workaround this issue. But it will be out of memory. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1177083] New: python-aliyun-python-sdk-core package ships a vendored python-requests package
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1177083 Bug ID: 1177083 Summary: python-aliyun-python-sdk-core package ships a vendored python-requests package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: adrian.glaubitz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The python-aliyun-python-sdk-core ships a vendored version of the python-requests package which should be removed in the next version update to avoid hidden vulnerabilities in the embedded version of python-requests as well as avoid code duplicity. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1185613] New: groff: .Os macro uses BSD as default
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1185613 Bug ID: 1185613 Summary: groff: .Os macro uses BSD as default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: sbrabec(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: werner(a)suse.com Found By: --- Blocker: --- The .Os macro in man pages when used without parameters produces "BSD". The built-in default for "doc-default-operating-system" in groff needs to be changed, ideally to read /etc/os-release. # man ssh|tail -1 BSD July 15, 2020 BSD # (. /etc/os-release; echo .ds doc-default-operating-system $PRETTY_NAME) >> /usr/share/groff/site-tmac/mdoc.local tw-systemd:/tmp # man ssh|tail -1 openSUSE Tumbleweed July 15, 2020 openSUSE Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1191244] New: USB speaker working when plugged while system is up but not on reboot
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191244 Bug ID: 1191244 Summary: USB speaker working when plugged while system is up but not on reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: aarch64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: peter.stark(a)storck.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have multiple raspberry PI 4Bs with openSUSE Leap 15.3 and some with raspbian 9. I got a USB speaker (e2b7:0811) which I connected to the 4Bs using Leap 15.3. This speaker works fine when I plug it in when the PI is already running: rpi15:~ # uname -a Linux rpi15 5.3.18-59.24-default #1 SMP Mon Sep 13 15:06:42 UTC 2021 (2f872ea) aarch64 aarch64 aarch64 GNU/Linux rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 007: ID e2b7:0811 Jie Li CD002 Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 [Sa Okt 2 10:56:09 2021] usb 1-1.2: USB disconnect, device number 4 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 6 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: device descriptor read/64, error -32 [Sa Okt 2 10:56:17 2021] usb 1-1.2: new full-speed USB device number 7 using xhci_hcd [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:56:17 2021] usb 1-1.2: config 1 has no interface number 0 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device found, idVendor=e2b7, idProduct=0811, bcdDevice= 1.00 [Sa Okt 2 10:56:17 2021] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Product: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: Manufacturer: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: SerialNumber: CD002 [Sa Okt 2 10:56:17 2021] usb 1-1.2: 9:1: bogus dB values (-12800/-12700), disabling dB reporting [Sa Okt 2 10:56:17 2021] input: CD002 CD002 as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.3/0003:E2B7:0811.0003/input/input1 However, after a reboot with the device still connected (no change) the kernel boots and does not even see the device. rpi15:~ # lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 03eb:2013 Atmel Corp. iAQ Stick Bus 001 Device 003: ID 044f:b351 ThrustMaster, Inc. F16 MFD 1 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub rpi15:~ # dmesg -T|grep 1-1.2 rpi15:~ # I have tried the same USB speaker on another PI4B with Leap 15.3 with the same result. So, it doesn't seem to be that PI. When I connect the speaker to a PI3 with raspbian 9, it works as expected. root@rpi13:~# dmesg -T |grep 1-1.3 [Sa Okt 2 10:33:08 2021] usb 1-1.3: new full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:33:08 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:33:08 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:33:08 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:33:08 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0001/input/input0 [Sa Okt 2 10:42:57 2021] usb 1-1.3: reset full-speed USB device number 4 using dwc_otg [Sa Okt 2 10:42:58 2021] usb 1-1.3: USB disconnect, device number 4 [Sa Okt 2 10:42:58 2021] usb 1-1.3: 9:1: cannot get min/max values for control 2 (id 9) [Sa Okt 2 10:43:04 2021] usb 1-1.3: new full-speed USB device number 6 using dwc_otg [Sa Okt 2 10:43:04 2021] usb 1-1.3: device descriptor read/64, error -32 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has an invalid interface number: 3 but max is 2 [Sa Okt 2 10:43:04 2021] usb 1-1.3: config 1 has no interface number 0 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device found, idVendor=e2b7, idProduct=0811 [Sa Okt 2 10:43:04 2021] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=1 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Product: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: Manufacturer: CD002 [Sa Okt 2 10:43:04 2021] usb 1-1.3: SerialNumber: CD002 [Sa Okt 2 10:43:04 2021] input: CD002 CD002 as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.3/0003:E2B7:0811.0002/input/input1 I noticed that the raspbian uses dwc_otg vs. xhci_hcd on Leap. However, dwc_otg doesn't seem to be a separate module in raspbian nor it is available on leap. As the speaker is working when I un-plug and plug it in again, I wonder what may causes this strange behavior. Especially as I do not see the device via lsusb after reboot, though it is still connected. Any ideas on how to fix it? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1199270] New: Chromium 100.0.4896.127 high GPU usage after resume (NVIDIA)
by bugzilla_noreply＠suse.com 19 Dec '22

19 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199270 Bug ID: 1199270 Summary: Chromium 100.0.4896.127 high GPU usage after resume (NVIDIA) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: denni.granata(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Chromium browser GPU escalation when resumed from suspend to RAM. How to duplicate: Open Chromium Browse the web Put the PC in susped to RAM Resume Wait for some seconds Open the Chromium task manager (Shift+Esc) Find the GPU process and observe it raises above 100% Kill the process or your GPU fan will go crazy. OpenSUSE Tumbleweed 20220503 Chromium 100.0.4896.127 Nvidia-GfxG06 510.68.02-7.1 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.4-1-default (64-bit) Graphics Platform: X11 Processors: 12 �� Intel�� Core�� i7-9750H CPU @ 2.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1198137] New: [Build 6.44] openQA test fails in sshd: busybox- packages in the repo
by bugzilla_noreply＠suse.com 18 Dec '22

18 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1198137 Bug ID: 1198137 Summary: [Build 6.44] openQA test fails in sshd: busybox- packages in the repo Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://openqa.opensuse.org/tests/2283453/modules/sshd /steps/24 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: lubos.kocman(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dcermak(a)suse.com, mlin(a)suse.com Found By: openQA Blocker: Yes busybox-foo packages are provided as alternatives to packages like e.g. coreutils and psmisc, but zypper picks them by default because they are earlier in the alphabet. This breaks installing packages which explicitly require the non-busybox variant and will also cause other issues. Like in SLE, the busybox- packages must not be visible to users, only inside OBS, because the distro is not prepared for that yet. ## Observation openQA test in scenario opensuse-15.4-JeOS-for-kvm-and-xen-x86_64-jeos@64bit_virtio-2G fails in [sshd](https://openqa.opensuse.org/tests/2283453/modules/sshd/steps/24) ## Test suite description Maintainer: fvogt, mnowak Start JeOS from the HDD image, configure it using the firstboot wizard and then run basic tests. console=tty0 added as needed for aarch64. ## Reproducible Fails since (at least) Build [6.28](https://openqa.opensuse.org/tests/2263801) ## Expected result Last good: [6.24](https://openqa.opensuse.org/tests/2258177) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1187951] New: Contacts synchronization not working for google
by bugzilla_noreply＠suse.com 17 Dec '22

17 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187951 Bug ID: 1187951 Summary: Contacts synchronization not working for google Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running latest TW with Contacts Version 5.17.2 (21.04.2) I noticed that around 25% of ma contacts on google is missing. Tried refreshing the collection, but that did not help. Finally I deleted the addressbook and created a new one. Some error messages occured: org.kde.pim.akonadiserver: New notification connection (registered as Akonadi::Server::NotificationSubscriber(0x7fbf4c1bb420) ) org.kde.pim.akonadiserver: Subscriber Akonadi::Server::NotificationSubscriber(0x7fbf4c1bb420) identified as "AgentBaseChangeRecorder - 94763683329824" kf.coreaddons: Trying to attach UI delegate: KIO::JobUiDelegate(0x564c71fc43b0) to job KJob(0x564c71ff4270) but this delegate is already attached to a different job KIO::OpenUrlJob(0x564c71fc9520) kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart (some more....) kf.calendarcore: Invalid dtStart kf.calendarcore: Invalid dtStart org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection akonadi_google_resource_1 (0x55b7f4780580) org.kde.pim.akonadicore: Deleting items from the akonadi database failed: "No items found" org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist (some more as well) org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Requested resource does not exist org.kde.kgapi: Bad request, Google replied ' "Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration." ' org.kde.pim.google: Got error: KGAPI2::ContactFetchPhotoJob(0x562fe53147d0) "Fehlerhafte Anfrage." The API change seems to be the issue..... Reported upstream https://bugs.kde.org/show_bug.cgi?id=439285 -- You are receiving this mail because: You are on the CC list for the bug.

1 8