July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201387] touch: cannot touch '/run/regenerate-initrd//usr/lib/modules/5.18.9-2-default/vmlinuz-5.18.9-2-default': No such file or directory
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201387 https://bugzilla.suse.com/show_bug.cgi?id=1201387#c1 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo(a)suse.com Assignee|screening-team-bugs(a)suse.de |dracut-maintainers(a)suse.de --- Comment #1 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- Could you attach the dracut generation log? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200547] New: Hang on boot
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1200547 Bug ID: 1200547 Summary: Hang on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hr.denzler(a)bluewin.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Nvidia twinview, GeForce GTX 1060 6GB nvidia-computeG05-470.129.06-lp153.54.1.x86 kernel-default-5.3.18-150300.59.71.2.x86_64 Leap 15.3 on front slot SSD-Drive Since 15.3, after 1-10 times of normal booting I get a hang on boot. Then hard shutdown, boot again. If I see many "kvm: disabled by bios" messages like 3 or more, then this is a good sign for correct booting later. A bad sign is the turning wheel never ending. var/log/messages doesn't give me a clue where it hangs. The bad sign from "last | more": reboot system boot 5.3.18-150300.59 Wed Jun 15 09:47 still running reboot system boot 5.3.18-150300.59 Wed Jun 15 09:46 - 07:46 (-1:59) The good sign: hrd pts/1 :0 Tue Jun 14 23:04 - 23:05 (00:00) hrd pts/0 :0 Tue Jun 14 22:34 - down (00:47) hrd tty7 :0 Tue Jun 14 22:34 - down (00:47) The bad sign after just one normal boot: reboot system boot 5.3.18-150300.59 Wed Jun 15 00:34 - 23:22 (-1:11) reboot system boot 5.3.18-150300.59 Wed Jun 15 00:33 - 22:33 (-1:59) Somewhere is a logic to prevent hanging all the time, unable to start Leap 15.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 28

[Bug 1200744] MD-RAID1 refuses to assemble while "mdadm -E" says the disks are fine (v1.2 superblock)
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200744 https://bugzilla.suse.com/show_bug.cgi?id=1200744#c4 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #4 from Neil Brown <nfbrown(a)suse.com> --- I could reproduce this problem easily (create some virtual devices, then truncate them), so I could confirm the "Unused Space:" does what I thought. I've created a patch to provide better diagnostics and submitted it upstream. I'll submit it to Base:System and Factory later this week if upstream is happy with it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198457] systemd[1]: Failed to start One time configuration for iscsid.service
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1198457 https://bugzilla.suse.com/show_bug.cgi?id=1198457#c33 --- Comment #33 from Jose Lausuch <jalausuch(a)suse.com> --- (In reply to Lee Duncan from comment #32) > Marking as resolved. Yes, the bug was gone 2 months ago: https://openqa.opensuse.org/tests/2338800#next_previous Sorry for late reply. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201383] New: Background transparency lost
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201383 Bug ID: 1201383 Summary: Background transparency lost 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: ub22(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since KDE/Plasma updated to 5.25.*, I miss at X11 the background transparency. If I look in Profil Settings "Erscheinungsbild" there is the red marked text visible: "Dieses Farbschema verwendet einen transparenten Hintergrund, der von Ihrem System scheinbar nicht unterst�tzt wird." But why the Color Porfile don't support the transparency anymore :-( I use transparency not only due to nice design reasons. Also to read an article in the background and code or test the new readed stuff in the konsole. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196547] MicroOS Desktop GNOME system role doesn't preinstall language subpackages
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196547 http://bugzilla.opensuse.org/show_bug.cgi?id=1196547#c14 --- Comment #14 from Richard Brown <rbrown(a)suse.com> --- (In reply to Ludwig Nussel from comment #13) > (In reply to Alois Wohlschlager from comment #12) > > [...] Some concrete examples > > TW/MicroOS experience: > > * enhanced_base -> plymouth: This is a Recommends, so it's not installed on > > MicroOS today. The system works without a boot splash, but it looks nicer > > with one. > > Plymouth needs to be made a requirement for graphical desktops > unfortunately. If someone desperately doesn't want it installed, the pattern > dragging plymouth in would have to be uninstalled. It's also worth considering on most systems plymouth starts slower than GDM/SDDM, so the only real-world effect of installing plymouth is often the addition of a flicker between grub and the login prompt, a flicker which is noticibly absent on MicroOS. Personally I'd rather have no flicker rather than an ugly flicker that doesn't have time for the human brain to register the fact there could have been an image there. > > > * microos_desktop_common -> hplip-hpijs, OpenPrintingPPDs: This is in fact a > > Requires today. A desktop system can work without printing if so desired, > > but a significant part of the userbase appreciates their printer working. > > That should neither be required nor recommended. If one plugs a USB printer, > hardware supplements are supposed to pull in required packages. I wouldn't > be surprised if that's broken (again) on openSUSE though. Also any > assumptions about whether or not users with local printers constitute a > significant part of the user base are based on pure guessing related to > personal bias :-) It is a clear design requirement of the MicroOS Desktop that it must be " small, but not at the expense of functionality. Printing, Gaming, Media Production and much more should all work." And such things should work "out of the box" https://en.opensuse.org/Portal:MicroOS/Desktop Therefore your 'concrete example' here is invalid and antithetical to the goals of the MicroOS Desktop Project -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198457] systemd[1]: Failed to start One time configuration for iscsid.service
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1198457 https://bugzilla.suse.com/show_bug.cgi?id=1198457#c32 Lee Duncan <lduncan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #32 from Lee Duncan <lduncan(a)suse.com> --- Marking as resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200583] FreeCAD Segfaults Opening Any Example (libc.so.6)
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200583 https://bugzilla.suse.com/show_bug.cgi?id=1200583#c13 Stephan Hemeier <Sauerlandlinux(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Sauerlandlinux(a)gmx.de --- Comment #13 from Stephan Hemeier <Sauerlandlinux(a)gmx.de> --- Here on Leap 15.3 it is working: https://build.opensuse.org/package/show/home:Sauerland/FreeCAD I build it with Coin3and a newer netgen. Maybe the 15.4 package is working for you. Stephan -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160066] python-certbot update to 1.0.0
by bugzilla_noreply＠suse.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1160066 http://bugzilla.opensuse.org/show_bug.cgi?id=1160066#c5 --- Comment #5 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1160066) was mentioned in https://build.opensuse.org/request/show/988418 Backports:SLE-15-SP4 / python-certbot https://build.opensuse.org/request/show/988419 Backports:SLE-15-SP4 / python-certbot-apache https://build.opensuse.org/request/show/988431 Backports:SLE-15-SP4 / python-certbot-nginx -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1141928] New: python-acme will break on November 1st
by bugzilla_noreply＠novell.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1141928 Bug ID: 1141928 Summary: python-acme will break on November 1st Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bmw(a)eff.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This bug affects the python*-acme packages in Leap 15.0 and 15.1. If there is already a version of python*-acme frozen in Leap 15.2, it is affected if it is not version 0.34.0 or greater. The python*-acme packages will no longer work with Let’s Encrypt’s “ACMEv2” endpoint which is their RFC 8555 compliant endpoint starting November 1st. See https://community.letsencrypt.org/t/acme-v2-scheduled-deprecation-of-unauth… for more details about this change. As one of the upstream maintainers of this library, I would recommend backporting python-acme 0.34.0 or greater to all supported versions of openSUSE. There are no breaking changes to the Python API and no dependencies should have to be updated. If you do this, to flag a couple changes for you that you may want to know about: * Some of the code in the library has been deprecated in recent versions and while it still works just fine it is causing Python DeprecationWarnings. See https://docs.python.org/3/library/warnings.html if you're not familiar with this. * There is an extremely minor change in the requests sent by the library. The previous versions were not RFC 8555 compliant and there are no known ACME CAs that rely on this non-standard behavior, but it's something you may want to know about. More details about this change are at https://github.com/certbot/certbot/pull/6975. If either of these changes are especially worrisome to you, I could tell you the changes that need to be backported to an earlier version of python-acme, however, I do not recommend this as it will result packages that have been less thoroughly tested. -- You are receiving this mail because: You are on the CC list for the bug.

2 3