July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222496] New: ipv6 dies within a day (or faster) on leap 15.5
by bugzilla_noreply＠suse.com 10 Mar '25

10 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222496 Bug ID: 1222496 Summary: ipv6 dies within a day (or faster) on leap 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I just recently narrowed down or observed that on a rather new (fresh) leap system (15.5, all updated, default repos, very simple, single gigabit ethernet pcie interface (realtek, onboard, gigabyte GA-P55-UD3 mainboard) the system becomes rather sluggish and networking stuff (only ssh-ing into the machine, some very simple things) is very unresponsive. until i discovered that even simple things such as direkt ipv6 pings onto ipv6 addresses fail and all packets become lost or never get replied. ipv4 works normal. whole network is a simple LAN with a normal soho gateway/home-router (fritzbox, in germany, deutsche telekom fibre provider consumer grade). yast2 shows dhcp4 on the eth0, but i tried having both dhcp4 and dhcp6 enabled to acquire the machines ip settings / assignments. or via neighbor announcement or what this stuff is called for ip6. either way, after less than a day of uptime of this leap 15.5 machine, the ipv6 stack seems to become non-working. once the ipv6 layer is broken I have situations such as this: -------- ping 2001:4860:4860::8844 PING 2001:4860:4860::8844(2001:4860:4860::8844) 56 data bytes ^C --- 2001:4860:4860::8844 ping statistics --- 323 packets transmitted, 0 received, 100% packet loss, time 329725ms ------------- /sbin/lspci | grep -i net 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ------- i am not very fluent with systemd, so I used rcnetwork to reset the network stack or recycle it, and after this command, ipv6 works normal again as well. > sudo rcnetwork restart fixes the stuff. only to again fail after less than a day, I couldnt narrow this down to a more precise time span. maybe completely random. any ideas? thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1225296] New: Dual monitor not recognised after upgrade 15.5 to 15.6
by bugzilla_noreply＠suse.com 09 Mar '25

09 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1225296 Bug ID: 1225296 Summary: Dual monitor not recognised after upgrade 15.5 to 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: martin.schmidt(a)io-warnemuende.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Moin, moin, I am using openSUSE 15.5 on an old intel based x86 PC, equipped with a simple nvidia gforce and two monitors. The monitors are using a displayport connnection from the graphics card to the monitors via an Y-shaped cable. Both monitors are recognised correctly and can be configured to form a single graphical work space, when the system is up and running. After upgrading to openSUSE 15.6 this does not work any more. When booting, monitor 1 shows some firmware screen and the openSUSE boot screen, where the OS version (several subversions of 15.6 and frozen snapshots of 15.5) can be selected. Using the default option (15.6 from harddrive), the output of the boot process is moving to monitor 2, but monitor 1 is going to a "power saving sleep mode" and stays inactive frome here on. The boot process is finished correctly with monitor 2 as the only graphical device. Monitor 1 cannot be activated again. Switching off monitor 2 before booting, the system comes up without any valid output device. Monitor 1 goes to sleep after the system boot started. I did not check the system status with a remote ssh-connection yet. Switching off monitor 1 before booting, lets the system come up completely with monitor 2. Also the initial hardware screen is diplayerd there. In turn, booting from a read-only snapshot with openSUSE 15.5, both monitors are used as before. The nouveau-dri drivers are used, no propriatary nvidia driver is installed. Some upgrade history: - just to test, if the few graphic card cores could be used in a cuda environment, cuda was installed under 15.5. This failed and cuda was deinstalled. However, when upgrading later from 15.5 to 15.6 the cuda development environment was reinstalled automatically together with nvidia drivers. As a result the nvidia drivers allowed only for a single low resolution vga monitor. May be, this happened, since the nvidia repository was not deleted and there was some leftover from the cuda test. - with the ascii-yast the nvidia drivers (gforce003/004) and cuda could be removed and the nouveau-dri drivers where reinstalled - together with dependencies. This allows for a single monitor OS_15.6 system with high resolution, but the second monitor (monitor 1) is lost during the boot process as described above. Before I try to install from scratch just with the hope that the error goes away, I am reporting this strange behaviour here. May be, this helps to streamline the distribution. Any hints are very welcome - especially how to modify the bootloader options. Cheers, Martin Schmidt -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1221183] New: Upgrade problems with clang-cpp
by bugzilla_noreply＠suse.com 09 Mar '25

09 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1221183 Bug ID: 1221183 Summary: Upgrade problems with clang-cpp Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: franz.sirl-obs(a)lauterbach.com QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Hi, during a "zypper --releasever=15.6 dup" upgrade from a fully up-to-date 15.5 installation I got the following messages: Checking for file conflicts: ...................................................................................................................................................................[error] Detected 4 file conflicts: File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from install of clang13-13.0.1-bp156.7.42.x86_64 (Main Repository) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang11-11.0.1-150300.3.6.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang15-15.0.7-150500.4.4.1.x86_64 (@System) File /usr/bin/clang-cpp from install of clang17-17.0.6-150600.1.13.x86_64 (Main Repository) conflicts with file from package clang7-7.0.1-150100.3.22.2.x86_64 (@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. Continue? [yes/no] (no): yes Even though this is mostly harmless, it disturbs the upgrade experience and probably can be easily fixed by backporting the clang-cpp/update-alternatives change from clang17 to the other clang versions that are part of Leap. regards, Franz -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1218403] New: Qt Creator does not show qt6's examples after `zypper in qt6-*-examples`
by bugzilla_noreply＠suse.com 08 Mar '25

08 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1218403 Bug ID: 1218403 Summary: Qt Creator does not show qt6's examples after `zypper in qt6-*-examples` Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: sauntor(a)yeah.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- As the title says, after install qt 6 examples via zypper, reopen qtcreator, it will not show any qt6 example! But if you install qt5 examples, it shows. Is it a bug or can one fix it himself by some way? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1227625] New: in %post (core dumped) ZYPP_READONLY_HACK=1 zypper refresh-services
by bugzilla_noreply＠suse.com 08 Mar '25

08 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1227625 Bug ID: 1227625 Summary: in %post (core dumped) ZYPP_READONLY_HACK=1 zypper refresh-services Classification: openSUSE Product: openSUSE Distribution Version: Leap 16.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875993 --> https://bugzilla.suse.com/attachment.cgi?id=875993&action=edit zypper.log from leap16 Using zypper refresh-services in %post crashes the post-script See line 345 in https://build.opensuse.org/projects/Base:System/packages/openSUSE-repos/fil… Using the add-service with READONLY_HACK and is working, however not regen of repos that most people complain about (missing after initial install etc). %post /var/tmp/rpm-tmp.4eukQ3: line 25: 8351 Aborted (core dumped) ZYPP_READONLY_HACK=1 zypper refresh-services -- You are receiving this mail because: You are on the CC list for the bug.

1 12

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

07 Mar '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 31

[Bug 1224808] New: dracut incorrectly modify btrfs compression level for /
by bugzilla_noreply＠suse.com 07 Mar '25

07 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1224808 Bug ID: 1224808 Summary: dracut incorrectly modify btrfs compression level for / Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: fcrozat(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a MicroOS Desktop system, I'm trying to enable btrfs compression on root fs. The change is made at /etc/fstab level. The initial fstab relevant line was: UUID=no_interest_here / btrfs ro 0 0 Changed to: UUID=no_interest_here / btrfs ro,compress=zstd:1 0 0 and then running transaction-update initrd to ensure dracut is run in the transactional system. However, the stored kernel cmdline by dracut becomes: dracut[I]: root=UUID=980c03f5-35f5-405d-8686-d51ec67c17b4 rootfstype=btrfs rootflags=rw,relatime,seclabel,compress=,ssd,discard=async,space_cache=v2,subvolid=774,subvol=/@/.snapshots/619/snapshot,subvol=@/.snapshots/619/snapshot compress parameter is being stripped. This is with dracut-059+suse.588.g528264be-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1222815] New: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer
by bugzilla_noreply＠suse.com 06 Mar '25

06 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1222815 Bug ID: 1222815 Summary: Performance CoPilot 6 is not starting due to missing pmlogger_daily.timer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- just installing pcp and pmlogger leads to: # systemctl start pmlogger Failed to start pmlogger.service: Unit pmlogger_daily.timer not found. this unit is currently in pcp-zeroconf. however pmlogger.service is in pcp (main package). if zeroconf is supposed to be optional, then the pmlogger_daily.timer dependency is supposed to be made optional. otherwise the timer needs to be moved into the main package (like it appears to be upstream) -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1218120] New: jetty-artifact-remote-resources: reproducible builds issue
by bugzilla_noreply＠suse.com 06 Mar '25

06 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1218120 Bug ID: 1218120 Summary: jetty-artifact-remote-resources: reproducible builds issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: fstrba(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that our jetty-artifact-remote-resources varies from filesystem-readdir-order. It probably needs an extra sort somewhere. example diff is --- old//usr/share/java/jetty-artifact-remote-resources/jetty-artifact-remote-resources.jar/META-INF/maven/remote-resources.xml +++ new//usr/share/java/jetty-artifact-remote-resources/jetty-artifact-remote-resources.jar/META-INF/maven/remote-resources.xml @@ -3,9 +3,9 @@ xmlns="http://maven.apache.org/remote-resources/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <remoteResources> - <remoteResource>about.html</remoteResource> - <remoteResource>META-INF/LICENSE</remoteResource> <remoteResource>META-INF/NOTICE.txt</remoteResource> + <remoteResource>META-INF/LICENSE</remoteResource> + <remoteResource>about.html</remoteResource> </remoteResources> <sourceEncoding>UTF-8</sourceEncoding> </remoteResourcesBundle> jetty-distribution-remote-resources is also affected. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1228081] New: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated
by bugzilla_noreply＠suse.com 03 Mar '25

03 Mar '25

https://bugzilla.suse.com/show_bug.cgi?id=1228081 Bug ID: 1228081 Summary: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876103 --> https://bugzilla.suse.com/attachment.cgi?id=876103&action=edit selectively trimmed zypper up typescript session plus dmesg tail Initial summary: "systemd-cryptsetup-generator[2606]: Assertion 'i->idx > 0' failed at src/basic/hashmap.c" messages spewed on tty when systemd is updated The summary messages have occurred on the tty running zypper up on each recent zypper up of each of my 15.6 installations that included updates to systemd* packages. They are logged in dmesg tail attached, following typescript log of login/zypper up session. Running kernel for the attachment generation was 6.4.0-150600.21.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 3