April 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1165047] New: CD tray closed immediately after ejecting media
by bugzilla_noreply＠novell.com 04 Feb '22

04 Feb '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1165047 Bug ID: 1165047 Summary: CD tray closed immediately after ejecting media Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ml.heimburg(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, after updating aaa_base to the version aaa_base-84.87+git20180409.04c9dae-lp151.5.18.1.x86_64.rpm the CD tray closed immediately after ejecting a media. So it is not possible to take the media out of the CD tray, because the time is too short between the opening and closing of the CD tray. This behavior does not depend from any other programs. It is reproducible every time when a CD, DVD or BD is injected in the CD tray. With the version aaa_base-84.87+git20180409.04c9dae-lp151.5.15.1.x86_64.rpm all media will be ejected correctly. System opensuse Leap 15.1 -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1089938] New: yast-samba-client fails to join if /etc/samba/smb.conf or /etc/krb5.conf don't exist
by bugzilla_noreply＠novell.com 03 Feb '22

03 Feb '22

http://bugzilla.suse.com/show_bug.cgi?id=1089938 Bug ID: 1089938 Summary: yast-samba-client fails to join if /etc/samba/smb.conf or /etc/krb5.conf don't exist Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: david.mulder(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- # sudo rm /etc/samba/smb.conf /etc/krb5.conf Join fails with "Cannot use the Workgroup xxxx for linux authentication" # sudo touch /etc/samba/smb.conf Join begins, but fails with "Failed to join domain: failed to connect to AD: Included profile file could not be read" # sudo touch /etc/krb5.conf Join succeeds and stubs out the smb.conf and krb5.conf files. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 996088] New: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=996088 Bug ID: 996088 Summary: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: stuart(a)stella-maris.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After performing an update today, 29/08/16, I decided to run efibootmgr -v as I have had issues before. I then found it returned BootCurrent: 0003 Timeout: 1 seconds No BootOrder is set; firmware will attempt recovery Boot0000* opensuse HD(1,GPT,2eca2750-fed6-4e3f-887f-27f183020fda,0x800,0x61800)/File(\EFI\opensuse\grubx64.efi) Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* CD/DVD Drive BBS(CDROM,,0x0) After which I ran efibootmgr -o 0000,0001,0002 which returned efibootmgr: Could not set BootOrder: No space left on device I then tried both update-bootloader --reinit which failed, then grub2-install which failed as well. This ended up with no efi boot options at all. I had to resort to chrooting from TW rescue disk and re-install grub2 and recover my PC. So far I have not tried to run the update-bootloader --reinit or grub2-install again since recovering my system as I fear it will mess up the system once more. As part of the update various grub2 packages were updated all not at beta3-10 level, the zypper history shows dracut running but no apparent errors were reported there. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1111728] New: Out of date package: openSUSE:Factory/efibootmgr
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111728 Bug ID: 1111728 Summary: Out of date package: openSUSE:Factory/efibootmgr Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sean(a)suspend.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory/efibootmgr is out of date (14). Current upstream is https://github.com/rhinstaller/efibootmgr/releases/download/17/efibootmgr-1…. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1167730] New: python-pandas tests are failing on ThunderX1 machines
by bugzilla_noreply＠novell.com 25 Jan '22

25 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1167730 Bug ID: 1167730 Summary: python-pandas tests are failing on ThunderX1 machines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de CC: afaerber(a)suse.com, dmueller(a)suse.com Found By: --- Blocker: --- python-pandas 1.0.2 fails in %check tests when scheduled on ThunderX1 machines (obs-arm-{1,2,3,4}). See job history: https://build.opensuse.org/packages/python-pandas/job_history/devel:languag… -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1093071] New: YaST constantly steals focus
by bugzilla_noreply＠novell.com 24 Jan '22

24 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1093071 Bug ID: 1093071 Summary: YaST constantly steals focus Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: okurz(a)suse.com QA Contact: jsrain(a)suse.com CC: ben.kevan(a)bio-rad.com, casualprogrammer(a)opensuse.org, cyberorg(a)opensuse.org, diego.ercolani(a)gmail.com, ensonic(a)sonicpulse.de, federico(a)suse.com, francis(a)opensuse.org, gabriel(a)opensuse.org, jdsn(a)suse.com, jonas(a)jonasbjork.net, l_v_brienen(a)casema.nl, m.moeller(a)opensuse.org, Markus.Elfring(a)web.de, martin(a)oneiros.de, mmeeks(a)suse.com, ptomes(a)gmail.com, ric8cruz(a)gmail.com, Roland.Kletzing(a)dguv.de, sbrabec(a)suse.com, tilman(a)imap.cc, Ulrich.Windl(a)rz.uni-regensburg.de, volker_apelt(a)yahoo.de Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #326158 +++ ## Observation There are a lot of very old bugs already and at least in the current state seems like the behaviour described in these bugs is still present: YaST during some actions, especially package installation (but not in the "software management" module itself), opens many popup dialogs and steals the focus preventing to work with the system while yast does its actions ## Steps to reproduce * In an installed system, open the yast control center, open "Remote Administration (VNC)", enable any of the Remote Administration options and confirm * Confirm installation of necessary package and minimize or focus another application * Observe how the yast configuration dialog gains focus again (unminimized) ## Expected result * For minimised YaST progress dialogs should never popup * progress dialogs should not get focus for unfocussed foreground applications ## Further details Seems this has been reported already many times so it might be interesting to dig a bit into history here: * https://bugzilla.suse.com/show_bug.cgi?id=326158 * https://bugzilla.suse.com/show_bug.cgi?id=331835 * https://bugzilla.suse.com/show_bug.cgi?id=34759 * https://bugzilla.suse.com/show_bug.cgi?id=334631 * https://bugzilla.suse.com/show_bug.cgi?id=615927 * https://bugzilla.suse.com/show_bug.cgi?id=372319 * https://bugzilla.suse.com/show_bug.cgi?id=74073 * https://bugzilla.suse.com/show_bug.cgi?id=330649 * https://bugzilla.suse.com/show_bug.cgi?id=297642 * https://bugzilla.suse.com/show_bug.cgi?id=298071 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1146452] New: Broken lighttpd logrotate config
by bugzilla_noreply＠novell.com 22 Jan '22

22 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1146452 Bug ID: 1146452 Summary: Broken lighttpd logrotate config Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running openSUSE Leap 15.1 with lighttpd-1.4.49-lp151.2.3.x86_64 and I see the following postrotate in /etc/logrotate.d/lighttpd which is came from the package: postrotate /etc/init.d/lighttpd reload endscript However, there is no such file /etc/init.d/lighttpd -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1131437] New: dbench4 regression with 5.0 kernel on anderson and marvin7
by bugzilla_noreply＠novell.com 21 Jan '22

21 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1131437 Bug ID: 1131437 Summary: dbench4 regression with 5.0 kernel on anderson and marvin7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Our performance dashboard shows significant regressions (up to 20%) for dbench4 on anderson and marvin7 especially on XFS filesystem but to some extent also on ext4. This appears both with and without mitigations. -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1159205] New: KIWI: Wrong GRUB default entry when booting snapshot
by bugzilla_noreply＠novell.com 20 Jan '22

20 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1159205 Bug ID: 1159205 Summary: KIWI: Wrong GRUB default entry when booting snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: iforster(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With our KIWI images, when selecting an older snapshot in the GRUB menu ("Start bootloader from a read-only snapshot" -> any entry), then the first entry "Help on bootable snapshot #<num>" will be selected instead of the actual bootable entry. For regular users this will just be an inconvenience compared to systems installed with YaST, but on automated systems, e.g. when using health-checker to automatically select an older snapshot if the default kernel or initrd did not boot correctly, this will break the boot completely - the system will be stuck in the help text. On systems installed with YaST, https://github.com/yast/yast-bootloader/blob/53bed387ab933f635fa3c557716131… will set the default entry by using the entry's name (e.g. "openSUSE MicroOS" or "openSUSE Leap 15.1"). KIWI would need a similar mechanism to get this working. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1084804] New: Plasma + Wayland: input method does not start
by bugzilla_noreply＠novell.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084804 Bug ID: 1084804 Summary: Plasma + Wayland: input method does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Plasma + Wayland session, input method like IBus, Fcitx does not start anymore. This is simply because /etc/X11/xim, which has been a script to launch one of input methods, is not executed on a Wayland session. So we need to update our input method launcher script to support Wayland. How can we do that? What is the right way to set environment variables such as GTK_IM_MODULE and QT_IM_MODULE according to the current selected input method under on Wayland session? Workaround: Set GTK_IM_MODULE and QT_IM_MODULE in ~/.i18n and start ibus-daemon -xd or fcitx by using KDE auto start settings. However, both IBus and Fcitx will not work correctly due to other bugs and limitations related to Wayland. -- You are receiving this mail because: You are on the CC list for the bug.

2 9