July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1225965] New: Improve KDE Discover bug reporting button
by bugzilla_noreply＠suse.com 11 Jan '25

11 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1225965 Bug ID: 1225965 Summary: Improve KDE Discover bug reporting button Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de CC: shundhammer(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Whenever we have a generic package issues that affects multiple users like (bug 1225174), we get a whole to of bug reports and duplicates. All that users seem to be doing is copy the text "<html>Dependency resolution failed:<br/><br/>[...] </html>", report a bug in a random component. Bonus: If the component is YaST, Huha gets angry like in bug 1225949. We do not see the bugs that were not reported due to bugzilla pointing out the possible duplicate, but in the example above we got 14 reports. These users may or may not have read through the duplicated bug, or read the recommendation there. https://github.com/KDE/discover/blob/d644b2a1000c04f084d39a4ef8a3402abf6417… Let's improve user experience here. Some ideas: 0. Direct the user to zypper/YaST for self-service resolution of the conflict. 1. Direct the user to a landing page with instructions for #0. 2. Direct the user to bugzilla search first 3. Take the message - extract package names only, strip arch/installed version, sort, and make a hash from it. Use that as the bug alias for automatic reduplication. 4. or even a fuzzy hash 5. Use a bugzilla whiteboard field with self-service fix instructions -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1227477] New: eglinfo tool is required but could not be ofund
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227477 Bug ID: 1227477 Summary: eglinfo tool is required but could not be ofund Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: tom.gossler(a)sigmanetworking.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875924 --> https://bugzilla.suse.com/attachment.cgi?id=875924&action=edit Screenshot of the Info Center message While running the Info Center application, clicking on OpenGl (EGL) in the menu under Graphics, the application reports "The eglinfo tool is required to display this page, but could not be found". I then attempted to install the tool manually via YaST, but the module was not found in the repositories. Details of my system are: Operating System: openSUSE Leap 15.5 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.4-lp154.5-default (64-bit) Graphics Platform: X11 Processors: 2 × Intel® Pentium® CPU G630 @ 2.70GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 2000 Manufacturer: Dell Inc. Product Name: Inspiron One 2320 System Version: 00 I believe this is simply a packaging issue, but could be considered installation as well. The same message was displayed within Info Center for the clinfo module, however I was able to install that manually as it was included in the repositories I have. Potentially this was fixed under bug 1195695 in Leap 15.3, but the fix may have been lost. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1223838] New: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau)
by bugzilla_noreply＠suse.com 10 Jan '25

10 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1223838 Bug ID: 1223838 Summary: Nonfunctional brightness keys on Apple Macbook 5.1 (mcp79,nouveau) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: ilgaz(a)ilgaz.gen.tr QA Contact: qa-bugs(a)suse.de CC: kernel-bugs(a)suse.de, qa-bugs(a)suse.de, tiwai(a)suse.com, variable_valuables761(a)simplelogin.com Depends on: 1217750, 1217716 Target Milestone: --- Found By: --- Blocker: --- Created attachment 874641 --> https://bugzilla.suse.com/attachment.cgi?id=874641&action=edit current dmesg output +++ This bug was initially created as a clone of Bug #1217750 +++ It seems the brightness keys (Fn+F1,Fn+F2) do not work in Tumbleweed with current 6.8 kernel series. This should have been reported rather long time ago. This has started happening in ~6.5 series I've attached the output of "brightnessctl -l",> which only shows keyboard (caps lock) key and several non-existent LEDs on keyboard. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1220086] New: xfce4-terminal does not honor --geometry parameter under wayland
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1220086 Bug ID: 1220086 Summary: xfce4-terminal does not honor --geometry parameter under wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I decided to play around with wayland instead of x11 to find out, if everything works as expected for me. On thing I found, is that xfce4-terminal does not honor --geometry parameter under wayland. It is always started centered, it seems to use the size parameters, though. Operating System: openSUSE Tumbleweed 20240216 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.4-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222194] New: kubo ipfs tries to start before the network appears and fails with an error
by bugzilla_noreply＠suse.com 09 Jan '25

09 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222194 Bug ID: 1222194 Summary: kubo ipfs tries to start before the network appears and fails with an error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: werwolf131313(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- kubo ipfs tries to start before the network appears and fails with an error > [werwolf@power] ~ > ❯ sudo LANG=c zypper info kubo > Refreshing service 'openSUSE'. > Loading repository data... > Reading installed packages... > > > Information for package kubo: > ----------------------------- > Repository : filesystems > Name : kubo > Version : 0.26.0-16.17 > Arch : x86_64 > Vendor : obs://build.opensuse.org/filesystems > Installed Size : 79.2 MiB > Installed : Yes > Status : up-to-date > Source package : kubo-0.26.0-16.17.src > Upstream URL : https://github.com/ipfs/kubo > Summary : IPFS implementation in Go > Description : > IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single bittorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence > built in. You can also mount the world at /ipfs. As far as I understand, the problem can be solved by simply adding one line to the systemd service file > Wants=network-online.target > After=network-online.target -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1228016] New: VNC login results in black screen on KDE
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1228016 Bug ID: 1228016 Summary: VNC login results in black screen on KDE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: devguy.ca(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On KDE, I have enabled VNC server from Yast > Network Services > Remore Admin (VNC), on the PC I wish to remote into. However using both RealVNC viewer as well as TigerVNC viewer I end up getting a black screen. With KDE I am using X11. FYI: I havc used both x11vnc as well as x0vncserver both with success starting them up manually. System Infom Operating System: openSUSE Tumbleweed 20240715 KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.9.9-1-default (64-bit) Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A38 System Version: 8.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218653] New: Gimp 3 scheduled for May - Lets start the preparations
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1218653 Bug ID: 1218653 Summary: Gimp 3 scheduled for May - Lets start the preparations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- - https://www.phoronix.com/news/GIMP-3.0-May-2024-Schedule - https://librearts.org/2023/11/gimp-3-0-roadmap/ current test packages are in: https://build.opensuse.org/project/show/graphics:gimp:master i dropped a mail to Jehan to find out if the master snapshots of gegl and babl are still needed or not. if we want to have parallel buildable packages it would be easy to rename the master gimp package to gimp3 and apply this patch: ``` Index: gimp.spec =================================================================== --- gimp.spec (revision 1878) +++ gimp.spec (working copy) @@ -67,14 +67,16 @@ %global abiver 5 %global apiver 3.0 -Name: gimp +%define pkg_name gimp + +Name: gimp3 Version: 3.0 Release: 0 Summary: The GNU Image Manipulation Program License: GPL-3.0-or-later Group: Productivity/Graphics/Bitmap Editors URL: https://www.gimp.org/ -Source: %{name}-%{version}.tar.zst +Source: %{pkg_name}-%{version}.tar.zst Source1: macros.gimp # openSUSE palette file Source2: openSUSE.gpl @@ -184,6 +186,7 @@ Provides: gimp-2.0 = %{version} Provides: gimp(abi) = %{abiver} Provides: gimp(api) = %{apiver} +Conflicts: gimp %description The GIMP is an image composition and editing program, which can be @@ -296,7 +299,7 @@ %endif %prep -%autosetup -p1 +%autosetup -p1 -n %{pkg_name}-%{version} %build #define _lto_cflags %{nil} ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1218455] New: kernel: NOHZ tick-stop error: local softirq work is pending
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1218455 Bug ID: 1218455 Summary: kernel: NOHZ tick-stop error: local softirq work is pending Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Starting with kernel 6.6.6 (and continuing with 6.6.7) I get kernel: NOHZ tick-stop error: local softirq work is pending, handler #08!!! a few times within one or two minutes and during this time performance is degraded heavily. This happens about every two days, so it is not that much of a problem, but a bit annoying. system is: Operating System: openSUSE Tumbleweed 20231226 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Dell Inc. Product Name: XPS 13 9310 2-in-1 -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1219817] New: GNOME 45.3 session crashed when changing sound output
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1219817 Bug ID: 1219817 Summary: GNOME 45.3 session crashed when changing sound output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: db(a)mail25.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872650 --> https://bugzilla.suse.com/attachment.cgi?id=872650&action=edit journal.txt OS: Tumbleweed 20240209 gnome-shell version: 45.3-2.2 System: Dell Latitude 5440 laptop Had Bluetooth headphones connected, in the top-right GNOME "tray" area I changed the sound output to the Handsfree option of my headphones and my session immediately crashed, I was returned to the GDM login screen. Logged back in, everything seemed to be working again, changed the sound output without crashes. First time I've had this happen. There are some errors about code being reached that shouldn't be, stack traces and core dumps in the journal (attached file). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227591] New: eclipse-jdt upgrade
by bugzilla_noreply＠suse.com 08 Jan '25

08 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227591 Bug ID: 1227591 Summary: eclipse-jdt upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: elatllat(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- eclipse-jdt is from 2020-03 when it should be 2024-06 -- You are receiving this mail because: You are on the CC list for the bug.

1 2