May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1224819] New: Please update Kicad to version 8.0
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224819 Bug ID: 1224819 Summary: Please update Kicad to version 8.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The included Kicad is stuck at version 6 where it is now at version 8. The version included in the engineering repository is broken (and stuck somewhere between 6 and 7. Note that Kicad 8 requires Python > 3.6, i.e. Python 3.11, with wxWidget and wxPython support for Python 3.11. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222919] criterion fails to build on Leap 15.6 - ImportError: cannot import name 'builder'
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222919 https://bugzilla.suse.com/show_bug.cgi?id=1222919#c7 --- Comment #7 from Max Lin <mlin(a)suse.com> --- Not changed to 3.11 by default, but 3.11 is 2nd option available other than 3.6. And protobuf 4.25 from SLE15 has built with python 3.11. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160672] mingw*-runtime + winpthreads does not build reproducibly
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1160672 https://bugzilla.suse.com/show_bug.cgi?id=1160672#c2 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- OK, it seems, Factory had its first 'unchanged' entry 2023-06-15 in osc jobhistory windows:mingw:win32 mingw32-runtime openSUSE_Factory x86_64 and now there are just variations in .a file metadata left that are ignored by build-compare. Let's count the original issue as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1062303] trackerbug: packages do not build reproducibly from randomness
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1062303 Bug 1062303 depends on bug 1160672, which changed state. Bug 1160672 Summary: mingw*-runtime + winpthreads does not build reproducibly https://bugzilla.suse.com/show_bug.cgi?id=1160672 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224199] [Build 20240512] Unlock Users setting will end up in changing Root user settings.
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224199 https://bugzilla.suse.com/show_bug.cgi?id=1224199#c1 --- Comment #1 from xiaoguang wang <xiaoguang.wang(a)suse.com> --- Create an issue on upstream. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3066 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224066] DistroBox does not start; after fresh install on SUSE TumbleWeed [ISSUE]
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224066 https://bugzilla.suse.com/show_bug.cgi?id=1224066#c6 Martin von Reichenberg <martin.von.reichenberg(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #6 from Martin von Reichenberg <martin.von.reichenberg(a)protonmail.com> --- (In reply to Aleksa Sarai from comment #5) > (In reply to Alexandre Vicenzi from comment #3) > > There is official documentation that describes manual steps post-install on > > Linux, see https://docs.docker.com/engine/install/linux-postinstall/. > > > > I don't classify this as a bug, but rather well-known behavior. Changes to > > the Docker package would be a feature request. > > > > Aleksa, should we add users to groups in %post/%posttrans scripts? > > Access to the docker group gives you admin privileges to the machine (it is > trivial to get root host access using Docker) and so automatically adding > users seems like a bad idea in general. We also don't know which users we > should add to the group at install time anyway. > > (In reply to Martin von Reichenberg from comment #2) > > So the point is that there is no mention (the one similar to VirtualBox) > > about the current user is supposed to be part of the Docker group which > > could easily be set in %post / %posttrans script as: `usermod -aG $USER > > docker` (or equivalent...). > > (In reply to Martin von Reichenberg from comment #4) > > But it is a formerly missing information by those who maintain it - As a > > post installation step / notification about what needs to be done in order > > to use the software. > > I don't see anything in the VirtualBox spec file which would tell users > about the vboxusers group at install time. If you want, we can add a line in > the package documentation about the docker group, but the fact that you need > to be part of the docker group to administer Docker is incredibly common > knowledge for users of Docker. As mentioned above, this is mentioned already > by the upstream documentation. VirtualBox shows the notification window at the initial runtime. In case of DistroBox it is not clear at the very first usage that it's all bound to Docker (- services/groups). Probably an echo/printf message could be enough, but it should be told after install or initial startup somehow - more likely a request to upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224066] DistroBox does not start; after fresh install on SUSE TumbleWeed [ISSUE]
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224066 https://bugzilla.suse.com/show_bug.cgi?id=1224066#c5 Aleksa Sarai <asarai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(asarai(a)suse.com) | --- Comment #5 from Aleksa Sarai <asarai(a)suse.com> --- (In reply to Alexandre Vicenzi from comment #3) > There is official documentation that describes manual steps post-install on > Linux, see https://docs.docker.com/engine/install/linux-postinstall/. > > I don't classify this as a bug, but rather well-known behavior. Changes to > the Docker package would be a feature request. > > Aleksa, should we add users to groups in %post/%posttrans scripts? Access to the docker group gives you admin privileges to the machine (it is trivial to get root host access using Docker) and so automatically adding users seems like a bad idea in general. We also don't know which users we should add to the group at install time anyway. (In reply to Martin von Reichenberg from comment #2) > So the point is that there is no mention (the one similar to VirtualBox) > about the current user is supposed to be part of the Docker group which > could easily be set in %post / %posttrans script as: `usermod -aG $USER > docker` (or equivalent...). (In reply to Martin von Reichenberg from comment #4) > But it is a formerly missing information by those who maintain it - As a > post installation step / notification about what needs to be done in order > to use the software. I don't see anything in the VirtualBox spec file which would tell users about the vboxusers group at install time. If you want, we can add a line in the package documentation about the docker group, but the fact that you need to be part of the docker group to administer Docker is incredibly common knowledge for users of Docker. As mentioned above, this is mentioned already by the upstream documentation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224940] New: network:im:signal/signal-desktop: it is not possible to save attached files or attach files to messages
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224940 Bug ID: 1224940 Summary: network:im:signal/signal-desktop: it is not possible to save attached files or attach files to messages Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Fedora Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: res-1(a)communicate.at QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- In the current revision ("300") it is not possible to save attached files or attach files to messages on Fedora/KDE. Since the problem doesn't seem to exist on other systems, I suspect the problem lies in the compilation done here. If I'm wrong, please let me know and I'll open a bug report on GitHub! -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1224455] New: inkscape open error
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224455 Bug ID: 1224455 Summary: inkscape open error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ivo.grimaldi(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When I try to open Inkscape <pre> 0# Inkscape::Application::crash_handler(int) in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 1# 0x00007FE528441240 in /lib64/libc.so.6 2# 0x00007FE527D06069 in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 3# 0x00007FE527D0694D in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 4# g_dbus_connection_register_object in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 5# g_dbus_connection_export_menu_model in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 6# 0x00007FE523384D93 in /usr/lib64/gtk-3.0/modules/libappmenu-gtk-module.so 7# Gtk::Widget_Class::realize_callback(_GtkWidget*) in /usr/bin/../lib64/inkscape/../libgtkmm-3.0.so.1 8# g_closure_invoke in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 9# 0x00007FE528163028 in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 10# 0x00007FE528164901 in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 11# g_signal_emit_valist in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 12# g_signal_emit in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 13# gtk_widget_realize in /usr/bin/../lib64/inkscape/../libgtk-3.so.0 14# InkscapeWindow::setup_view() in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 15# InkscapeWindow::InkscapeWindow(SPDocument*) in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 16# InkscapeApplication::window_open(SPDocument*) in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 17# InkscapeApplication::create_window(SPDocument*, bool) in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 18# InkscapeApplication::process_document(SPDocument*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 19# InkscapeApplication::on_activate() in /usr/bin/../lib64/inkscape/libinkscape_base.so.1.3.2.0 20# Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) in /lib64/libglibmm-2.4.so.1 21# g_closure_invoke in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 22# 0x00007FE528163265 in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 23# 0x00007FE528164901 in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 24# g_signal_emit_valist in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 25# g_signal_emit in /usr/bin/../lib64/inkscape/../libgobject-2.0.so.0 26# 0x00007FE527CFA840 in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 27# g_application_run in /usr/bin/../lib64/inkscape/../libgio-2.0.so.0 28# main in /usr/bin/inkscape 29# 0x00007FE52842A1F0 in /lib64/libc.so.6 30# __libc_start_main in /lib64/libc.so.6 31# _start in /usr/bin/inkscape </pre> <details><summary>System info</summary> Inkscape 1.3.2 (091e20ef0f, 2023-11-25) GLib version: 2.80.2 GTK version: 3.24.41 glibmm version: 2.66.6 gtkmm version: 3.24.9 libxml2 version: 2.12.6 libxslt version: 1.1.39 Cairo version: 1.18.0 Pango version: 1.52.0 HarfBuzz version: 8.4.0 OS version: openSUSE Tumbleweed </details> -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1221644] pipewire-pulse stops working when monitor powers off/on again
by bugzilla_noreply＠suse.com 22 May '24

22 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221644 https://bugzilla.suse.com/show_bug.cgi?id=1221644#c11 --- Comment #11 from Jim Henderson <hendersj(a)gmail.com> --- Something that maybe is useful - I noticed that the wireplumber user service unit shows the following today: --- May 22 11:30:56 TheEarth wireplumber[3647]: [string "alsa.lua"]:178: table index is nil stack traceback: [string "alsa.lua"]:178: in function <[string "alsa.lua"]:172> --- -- You are receiving this mail because: You are on the CC list for the bug.

1 0