July 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c4 --- Comment #4 from Alan Hughes <alanhants(a)gmail.com> --- Logs supplied as requested. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c3 --- Comment #3 from Alan Hughes <alanhants(a)gmail.com> --- Created attachment 860115 --> https://bugzilla.suse.com/attachment.cgi?id=860115&action=edit Xorg log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c2 --- Comment #2 from Alan Hughes <alanhants(a)gmail.com> --- Created attachment 860114 --> https://bugzilla.suse.com/attachment.cgi?id=860114&action=edit Boot log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200461] Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200461 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-bugs(a)suse.de Flags| |needinfo?(kernel-bugs@suse. | |de) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200461] Dracut locks computer, fails to generate initrd file
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200461 https://bugzilla.suse.com/show_bug.cgi?id=1200461#c36 Thomas Blume <thomas.blume(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mfdemicco(a)gmail.c | |om) | --- Comment #36 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Mike DeMicco from comment #35) > Created attachment 860107 [details] > strace Thanks, so it hang at reading file named config below: /sys/devices/pci0000:00/ IMO, that should not happen. Acessing a readable sysfs file should not hang the system. That might be a kernel bug. kernel-maintainers, could you please take a look? -- 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 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1200583 https://bugzilla.suse.com/show_bug.cgi?id=1200583#c14 --- Comment #14 from Adrian Schr�ter <adrian.schroeter(a)suse.com> --- Maintenance request 988549 to fix this is out there. This also provides a version update to 0.20 because we are on it anyway. Test packages can be found here until the submission enters the maintenance workflow: https://download.opensuse.org/repositories/home:/adrianSuSE:/branches:/open… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201392] KDE login screen not displayed after update to TW 20220710
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1201392 https://bugzilla.suse.com/show_bug.cgi?id=1201392#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alanhants(a)gmail.com, | |fvogt(a)suse.com Flags| |needinfo?(alanhants(a)gmail.c | |om) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Please attach the journal for the relevant boot as well as /var/log/Xorg.0.log. -- 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 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196547 http://bugzilla.opensuse.org/show_bug.cgi?id=1196547#c15 --- Comment #15 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Richard Brown from comment #14) > (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. Absolutely. The point is that if the OS needs plymouth because we fail to make it boot fast and need to paper over the ugly messages then plymouth must be required. Or we fix the broken boot time and render plymouth obsolete. Then it doesn't need to be listed at all. IOW if plymouth is "recommended" there's something worth fixing. > > > * 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" Again I agree. That cannot mean installing cups with all drivers and ppds for all printers ever manufactured on this planet by default though. Think out of the box to find a proper solution :-) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197911] firewalld Error when booting
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

https://bugzilla.suse.com/show_bug.cgi?id=1197911 https://bugzilla.suse.com/show_bug.cgi?id=1197911#c9 --- Comment #9 from M. Edwin Zakaria <medwin(a)opensuse.org> --- (In reply to Otto Hollmann from comment #8) > No, but changes were already submitted (private comment #6 that you probably > can't see) so new (fixed) version will be released soon. You right I cannot see it. Thank you for following this up. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1201393] New: systemd[1]: Configuration file /usr/lib/systemd/system/iscsi.service is marked executable.
by bugzilla_noreply＠suse.com 12 Jul '22

12 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201393 Bug ID: 1201393 Summary: systemd[1]: Configuration file /usr/lib/systemd/system/iscsi.service is marked executable. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Systemd complains about several iSCSI service files having executable bits set, like this: Jul 11 08:37:53 localhost systemd[1]: Configuration file /usr/lib/systemd/system/iscsi.service is marked executable. Please remove executable permission bits. Proceeding anyway. Jul 11 08:37:53 localhost systemd[1]: Configuration file /usr/lib/systemd/system/iscsi-init.service is marked executable. Please remove executable permission bits. Proceeding anyway. Jul 11 08:37:53 localhost systemd[1]: Configuration file /usr/lib/systemd/system/iscsid.socket is marked executable. Please remove executable permission bits. Proceeding anyway. Jul 11 08:37:53 localhost systemd[1]: Configuration file /usr/lib/systemd/system/iscsid.service is marked executable. Please remove executable permission bits. Proceeding anyway. Jul 11 08:37:53 localhost systemd[1]: Configuration file /usr/lib/systemd/system/iscsiuio.service is marked executable. Please remove executable permission bits. Proceeding anywa -- You are receiving this mail because: You are on the CC list for the bug.

1 1