August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1044803] New: Default online repositories not used even if installing with network connection by default
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1044803 Bug ID: 1044803 Summary: Default online repositories not used even if installing with network connection by default Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Depends on: 1044741 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1044741 +++ I did installation from openSUSE-Leap-42.3-DVD-x86_64-Build0279-Media.iso image and during installation there was internet connection and computer was ONLINE. But I found that it tried to use only DVD as repository... Though default online repositories (oss, non-oss, oss-updates, non-oss-updates) will be added only if I intentionally pressed to configure online repositories at dialog for computer role. If I remember good, in previous versions these four _default_ repos where enabled by default, and we had option to include _additional_ repositories. See yast2logs and screenshots in bug#1044741 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1172465] New: transactional-update.timer fires immediately at first boot
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1172465 Bug ID: 1172465 Summary: transactional-update.timer fires immediately at first boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE-MicroOS.armv7l-16.0.0-RaspberryPi2-Snapshot20200528.raw Booted and wondered why systemd-analyze wouldn't show me results. Turns out transactional-update.timer was started immediately at first boot. Maybe related to missing rtc on rpi? So the time warp caused by chrony catching up triggered it? # systemctl status transactional-update.timer * transactional-update.timer - Daily update of the system Loaded: loaded (/usr/lib/systemd/system/transactional-update.timer; enabled; vendor preset: enabled) Active: active (waiting) since Thu 2020-04-23 14:15:38 UTC; 1 months 10 days ago Trigger: Thu 2020-06-04 01:38:53 UTC; 11h left Triggers: * transactional-update.service Docs: man:transactional-update(8) If so why April 23rd rather than end of May when the image was created? # l /var/lib/chrony total 0 drwxr-x--- 1 chrony chrony 0 May 2 22:23 ./ drwxr-xr-x 1 root root 268 Jun 3 13:56 ../ Can and do we want to do something about this behavior or a matter of documentation again? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1195850] New: installation hooks are not working
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195850 Bug ID: 1195850 Summary: installation hooks are not working 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: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm trying to use hooks as described here: https://github.com/yast/yast-yast2/blob/master/library/general/doc/Hooks.md What I did is to create the file "before_copy_logs_finish_00_test_hook.sh" and put it in var/lib/YaST2/hooks/installation in the 'root' image that is used at installation time (to be clear like the one that is available in: download.opensuse.org/tumbleweed/repo/oss/boot/x86_64/root At the the end of the installation process, the script before_copy_logs_finish_00_test_hook.sh is supposed to be executed, but that doesn't happen. The log /var/log/YaST2/y2log-1.gz explains why: [Ruby] modules/Hooks.rb(find_hook_files):193 Found 1 hook files: before_copy_logs_finish_00_comes_hook.sh [Ruby] modules/Hooks.rb(execute):165 Executing hook 'before_copy_logs_finish' [Ruby] modules/Hooks.rb(execute):210 Executing hook file '/var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh' [bash] ShellCommand.cc(shellcommand):78 sh: /var/lib/YaST2/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory [Ruby] modules/Hooks.rb(execute):212 Hook file 'before_copy_logs_finish_00_comes_hook.sh' failed with stderr: sh: /var/lib/YaST/hooks/installation/before_copy_logs_finish_00_comes_hook.sh: No such file or directory The installer finds the script, but when it is executed it is not there. I suspected a chroot issue and to confirm my suspicion I did the following: After the installation process started, I moved to tty2 where a shell is available. The command 'ls /var/lib/YaST2/hooks/installation' shows that the hook script is there. then I did: mkdir -p /mnt/var/lib/YaST2/hooks/installation cp /var/lib/YaST2/hooks/installation/* /mnt/var/lib/YaST2/hooks/installation and let the installation process complete. This time the hook script got executed. The solution to the problem seemd to be: 1) do not execute the hook scripts in the chroot environment or 2) make the hook scripts visible in the chroot environment I guess the correct solution is number 2. For the record, the issue exists both in Leap 15.3 and tumbleweed. Using hooks was a possible solution to fix boo#1195118 bur I guess that's not an option right now. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1179849] New: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments
by bugzilla_noreply＠suse.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1179849 Bug ID: 1179849 Summary: plymouth rpm output: bad invocation of systemd-sysv-convert: too few arguments 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: mail(a)bernhard-voelker.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just saw this in the RPM output when doing 'zypper dup' today (openSUSE Tumbleweed 20201205-0 -> 20201207-0): (41/51) Installing: plymouth-0.9.5+git20200921+20778f2-4.1.x86_64 .......[done] Additional rpm output: usage: systemd-sysv-convert --apply <service> [<service> ...] Too few arguments. Please check to avoid this kind of worrying messages. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1170344] New: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output
by bugzilla_noreply＠novell.com 07 Mar '23

07 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1170344 Bug ID: 1170344 Summary: Btrfsprogs 5.6 bug: kernel booting stop at "BTRFS info" output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I Updated My PC and laptop to Tumbleweed 20200417, then these two systems could not boot, and there is not any error on screen. I tried to chroot to get the dmesg log, I got many BTRFS notices at the end. I find Btrfsprogs was updated before 10 days ago in Factory. I guess this is a bug for Btrfsprogs. -- You are receiving this mail because: You are on the CC list for the bug.

2 18

[Bug 1194784] New: Yast should use RSpec verifying doubles everywhere
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1194784 Bug ID: 1194784 Summary: Yast should use RSpec verifying doubles everywhere Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lslezak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This should avoid bugs in the unit tests. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1201815] New: Inconsistent Bluetooth status display
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201815 Bug ID: 1201815 Summary: Inconsistent Bluetooth status display Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 860354 --> http://bugzilla.opensuse.org/attachment.cgi?id=860354&action=edit Bluetooth status in GNOME Sometimes when the Bluetooth status is "disabled", the suggested action in the GNOME menu is "Turn Off" (instead of "Turn On"). So yo have to "Turn Off" even if it's off, just to be able to see (if at all) a "Turn On" again. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1197477] New: network port on monitor integrated usb hub never detects a link
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1197477 Bug ID: 1197477 Summary: network port on monitor integrated usb hub never detects a link Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: josua.m(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Greetings everybody! I recently got a new Monitor on my desk with an integrated USB-3.0 Hub and an integrated RJ45 network interface. But with openSUSE Leap (both 15.3 and 15.4-Beta), the system never detects a link - as shown by the ethtool output below: sudo ethtool usb0 [sudo] Passwort f�r root: Settings for usb0: Current message level: 0x00000007 (7) drv probe link Link detected: no I have tested this with two laptops: - An ASUS UX331UN (i7-8250U) running Leap 15.3 - An ROG G14 (Ryzen 5800) running Leap 15.4 Beta I have also tested 2 other operating systems - On Windows the interface works - On Ubuntu Focal the interface works Very rarely, a link is detected for a very short time, leading to networkmanager applet indicating connection attempt for a second or two. I caputres such a case in the dmesg below: [11867.152288] usb 1-3: new high-speed USB device number 15 using xhci_hcd [11867.302285] usb 1-3: New USB device found, idVendor=0424, idProduct=2806, bcdDevice= 2.10 [11867.302292] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.302295] usb 1-3: Product: USB2806 Smart Hub [11867.302298] usb 1-3: Manufacturer: Microchip [11867.304310] hub 1-3:1.0: USB hub found [11867.304698] hub 1-3:1.0: 6 ports detected [11867.432196] usb 2-4: new SuperSpeed Gen 1 USB device number 9 using xhci_hcd [11867.456449] usb 2-4: New USB device found, idVendor=0424, idProduct=5806, bcdDevice= 2.10 [11867.456457] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.456462] usb 2-4: Product: USB5806 Smart Hub [11867.456465] usb 2-4: Manufacturer: Microchip [11867.457681] hub 2-4:1.0: USB hub found [11867.457710] hub 2-4:1.0: 5 ports detected [11867.600165] usb 1-3.6: new high-speed USB device number 16 using xhci_hcd [11867.704259] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11867.704266] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11867.704269] usb 1-3.6: Product: Hub Feature Controller [11867.704272] usb 1-3.6: Manufacturer: Microchip [11867.708519] hid-generic 0003:0424:284C.0005: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 [11867.780407] usb 2-4.3: new SuperSpeed Gen 1 USB device number 10 using xhci_hcd [11867.800927] usb 2-4.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=33.00 [11867.800933] usb 2-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [11867.800936] usb 2-4.3: Product: USB 10/100/1000 LAN [11867.800939] usb 2-4.3: Manufacturer: Realtek [11867.800941] usb 2-4.3: SerialNumber: 0033000001 [11867.825408] cdc_ncm 2-4.3:2.0: MAC-Address: b0:4f:13:d7:59:ae [11867.825414] cdc_ncm 2-4.3:2.0: setting rx_max = 16384 [11867.825522] cdc_ncm 2-4.3:2.0: setting tx_max = 16384 [11867.826100] cdc_ncm 2-4.3:2.0 usb0: register 'cdc_ncm' at usb-0000:00:14.0-4.3, CDC NCM, b0:4f:13:d7:59:ae [11867.972746] usb 1-3.6: USB disconnect, device number 16 [11868.208085] usb 1-3.6: new high-speed USB device number 17 using xhci_hcd [11868.312781] usb 1-3.6: New USB device found, idVendor=0424, idProduct=2840, bcdDevice= 2.10 [11868.312788] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11868.312792] usb 1-3.6: Product: Hub Feature Controller [11868.312796] usb 1-3.6: Manufacturer: Microchip [11870.916715] cdc_ncm 2-4.3:2.0 usb0: 1000 mbit/s downlink 1000 mbit/s uplink [11871.172732] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready [11888.115889] usb 1-3.6: reset high-speed USB device number 17 using xhci_hcd [11888.221821] usb 1-3.6: device firmware changed [11888.221922] usb 1-3.6: USB disconnect, device number 17 [11888.303624] usb 1-3.6: new high-speed USB device number 18 using xhci_hcd [11888.407663] usb 1-3.6: New USB device found, idVendor=0424, idProduct=284c, bcdDevice= 2.00 [11888.407670] usb 1-3.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [11888.407674] usb 1-3.6: Product: Hub Feature Controller [11888.407677] usb 1-3.6: Manufacturer: Microchip [11888.411497] hid-generic 0003:0424:284C.0006: hiddev96,hidraw1: USB HID v1.10 Device [Microchip Hub Feature Controller] on usb-0000:00:14.0-3.6/input1 Also adding an lsusb: Bus 002 Device 010: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 009: ID 0424:5806 Microchip Technology, Inc. (formerly SMSC) USB5806 Smart Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 13d3:5a09 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 018: ID 0424:284c Microchip Technology, Inc. (formerly SMSC) Hub Feature Controller Bus 001 Device 015: ID 0424:2806 Microchip Technology, Inc. (formerly SMSC) USB2806 Smart Hub Bus 001 Device 006: ID 0781:55a1 SanDisk Corp. Cruzer Spark Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I'd be happy to do experiments if somebody can point me in a meaningful direction on how to approach this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1166296] New: Return of Yast2-fonts
by bugzilla_noreply＠novell.com 04 Mar '23

04 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1166296 Bug ID: 1166296 Summary: Return of Yast2-fonts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: cornelis(a)solcon.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- As yast2-fonts is back in TW again after a brief hiatus, would it be possible to add it again to Leap 15.2? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1200235] New: Multiple X sessions not possible with Plasma (Wayland)
by bugzilla_noreply＠suse.com 04 Mar '23

04 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200235 Bug ID: 1200235 Summary: Multiple X sessions not possible with Plasma (Wayland) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: simplyschinne(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- *steps to reproduce* (1) log in user1 with 'Desktop Session: Plasma (Wayland)' (2) lock screen (3) on lock screen, chose 'switch user' (4) log in user2 with 'Desktop Session: Plasma (Wayland)' (5) press ctrl-alt-f7 *expected behaviour* lock screen is displayed with prompt for user1's password, user1's session can be continued after keying in password *observed behaviour* lock screen is displayed but no key stroke, no mouse click is accepted. PC has to be rebooted. *notes* (1) Bug reproducible 100% with Desktop Session Plasma (Wayland) (2) Bug NOT reproducible with Desktop Session Plasma (X11) *environment* qqq@linux ~$ uname -a Linux linux.fritz.box 5.18.1-1-default #1 SMP PREEMPT_DYNAMIC Mon May 30 07:49:01 UTC 2022 (d00e88d) x86_64 x86_64 x86_64 GNU/Linux qqq@linux ~$ cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20220603" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20220603" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20220603" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed" LOGO="distributor-logo-Tumbleweed" -- You are receiving this mail because: You are on the CC list for the bug.

1 4