November 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192291] 389-DS crash related to compactdb operation
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192291 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |william.brown(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192306] New: General YaST control center is hard to find by default in GNOME Shell
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192306 Bug ID: 1192306 Summary: General YaST control center is hard to find by default in GNOME Shell Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: nekohayo(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- YaST modules being split in a bunch of launchable apps is a bit of a problem when combined with GNOME Shell specifically, because when you search for "yast" (expecting to find the main unified YaST control center app), there is a huge amount of search results but GNOME Shell only shows the first line (max 6 items) of results, of which the general YaST app isn't part of by default because of recency sorting and you never used it, so you hit a catch-22 situation. Additionally, GNOME Shell truncates the app names in the search results (it can expand names in the app picker, but not in search results), making it very difficult to find what you're looking for via search, even if it's not the main YaST app. As I couldn't find it, initially the only workaround I found was to activate the "Applications menu" extension, go to Applications > Other > Yast, and then, finally, found the unified Yast application! Only days later did I realize that, it turns out, "YaST" _is_ in the GNOME Shell apps picker... but it's the very last app on the 3rd page. So, combined with the impossibility of finding it via search in a fresh installation, this harms the first-time user experience of OpenSUSE Tumbleweed, at least as tested with GNOME 41. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c8 --- Comment #8 from Olav Reinert <seroton10(a)gmail.com> --- Using the suggested kernel does not fix the problem - I still get "Error: F0 not found" 24 times in the journal. # uname -a Linux blackbox 5.3.18-218.gebb75ee-default #1 SMP Tue Nov 2 07:01:22 UTC 2021 (ebb75ee) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189267] New: installation-images fails to build with updated source sans fonts
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1189267 Bug ID: 1189267 Summary: installation-images fails to build with updated source sans fonts 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: fvogt(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- With the update to version 3, the "Source Sans/Code" fonts dropped the "Pro" suffix in their name. While a fontconfig file to still match the old family name was introduced (https://build.opensuse.org/request/show/910248), installation-images still fails to build: [ 588s] running "unused_mos --domains --dir usr/share/YaST2 >/yast2-trans.domains" [ 588s] running "cp /bin/check_fonts /usr/bin/fc-match ." [ 588s] running "/check_fonts usr/share/YaST2/theme" [ 588s] Error: font "Source Sans Pro" not found; closest match(es): "Roboto" [ 588s] Error: font "Source Sans Pro Light" not found; closest match(es): "Roboto" [ 588s] Error: font "Source Sans Pro Semibold" not found; closest match(es): "Roboto" [ 588s] mk_image: execution of "/check_fonts usr/share/YaST2/theme" failed at lib/AddFiles.pm line 800 in data/root/root.file_list line 759. [ 588s] make: *** [Makefile:169: root] Error 2 [ 588s] error: Bad exit status from /var/tmp/rpm-tmp.OtDIU7 (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c7 --- Comment #7 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Borislav Petkov from comment #6) > (In reply to Takashi Iwai from comment #5) > > I don't recommend > > What would you recommend then instead? The updated suse-module-tools package (15.3.13-3.11.1) is already provided and published from the official Leap 15.3 update online repo. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c6 --- Comment #6 from Borislav Petkov <bpetkov(a)suse.com> --- (In reply to Takashi Iwai from comment #5) > I don't recommend What would you recommend then instead? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 https://bugzilla.suse.com/show_bug.cgi?id=1192278#c5 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #5 from Lubos Kocman <lubos.kocman(a)suse.com> --- I'm now running sync to prod. I'll have to most likely fix -Current symlinks afterwards. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- I don't recommend to mix up TW package on Leap for now, as TW packages have been changed significantly due to UsrMerge even if it's built from the similar source. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c4 --- Comment #4 from Borislav Petkov <bpetkov(a)suse.com> --- (In reply to Olav Reinert from comment #3) > The instructions on that web page seem to be outdated: Hmm, that has changed in the meantime. This should add your repo correctly: zypper ar -f https://download.opensuse.org/repositories/Kernel:/SLE15-SP3/pool Kernel:SLE15-SP3 notice the "pool" instead of "standard" in the file path. If it complains about missing suse-module-tools package, you can install it from here: http://download.opensuse.org/tumbleweed/repo/oss/ HTH. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192011] Build service dependency resolution generates ambiguity
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192011 https://bugzilla.suse.com/show_bug.cgi?id=1192011#c5 Raymund Will <rw(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo? --- Comment #5 from Raymund Will <rw(a)suse.com> --- Actually #1 is implemented in `shim` since Jan 2019 (at least in the development project) for FATE#326960 -- so this case was actually "fixed" early on! Robert, *where* did you find a `shim`-package, that still has that deprecated `grub2-efi` requirement? -- You are receiving this mail because: You are on the CC list for the bug.

1 0