June 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220574] New: [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now errors)
by bugzilla_noreply＠suse.com 29 Jul '24

29 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220574 Bug ID: 1220574 Summary: [META] GCC 14 package failures that cannot be worked around with -fpermissive (that are not results of warnings that are now errors) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mjambor(a)suse.com Reporter: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Meta issue that will track all packages that fail with gcc14 package except for those that are tracked in bug#1220571 - i.e. those that cannot be worked around by turning new errors back to warnings. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1225808] New: windows:mingw:win64/mingw64-openssl: No sources included in debug package
by bugzilla_noreply＠suse.com 29 Jul '24

29 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225808 Bug ID: 1225808 Summary: windows:mingw:win64/mingw64-openssl: No sources included in debug package Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The generated debug package does not include any source files, see https://build.opensuse.org/projects/windows:mingw:win64/packages/mingw64-op… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1225799] New: windows:mingw:win64/mingw64-kmymoney5: crashes on startup
by bugzilla_noreply＠suse.com 29 Jul '24

29 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225799 Bug ID: 1225799 Summary: windows:mingw:win64/mingw64-kmymoney5: crashes on startup Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- Running kmymoney5 from the binary package crashes - this has been reported at the KDE bug tracker. How to reproduce: 1. Download the portable package from https://build.opensuse.org/projects/windows:mingw:win64/packages/mingw64-km… 2. Unpack archive on Windows 3. In the root dir of the unpacked archive run start.bat or kmymoney.exe from the bin dir 4. follow new file wizard 5. save file After saving the file kmymoney crashes. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1225919] New: Package rrdtool does not build with gcc14 because of new errors
by bugzilla_noreply＠suse.com 29 Jul '24

29 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225919 Bug ID: 1225919 Summary: Package rrdtool does not build with gcc14 because of new errors 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: mjambor(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1220571 Target Milestone: --- Found By: --- Blocker: --- GCC 14 newly by default treats as errors a number of situations which before were only warnings. For more information see https://gcc.gnu.org/gcc-14/porting_to.html and meta bug #1220571. Because of this, package rrdtool fails to compile. This can be seen online at: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… It can be reproduced locally with command: osc build --clean --alternative-project home:rguenther:nextgcc We probably need patches listed at: https://gitlab.com/fweimer-rh/fedora-modernc/-/blob/main/pkg/r/rrdtool.md?r… The (first) error (that halts the build) is: [ 41s] rrd_tune.c: In function 'rrd_tune_r': [ 41s] rrd_tune.c:239:35: error: passing argument 3 of 'optparse_init' from incompatible pointer type [-Wincompatible-pointer-types] [ 41s] 239 | optparse_init(&options, argc, argv); /* re-initialize optparse */ [ 41s] | ^~~~ [ 41s] | | [ 41s] | const char ** [ 41s] In file included from rrd_tool.h:49, [ 41s] from rrd_tune.c:46: [ 41s] optparse.h:68:63: note: expected 'char **' but argument is of type 'const char **' [ 41s] 68 | void optparse_init(struct optparse *options, int argc, char **argv); [ 41s] | ~~~~~~~^~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219657] New: "airplane mode" does not survive reboot
by bugzilla_noreply＠suse.com 28 Jul '24

28 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219657 Bug ID: 1219657 Summary: "airplane mode" does not survive reboot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal 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 Target Milestone: --- Found By: --- Blocker: --- Time doesn't make bugs go away: It seems the issue has been reported before: https://bugzilla.opensuse.org/show_bug.cgi?id=925535 Anyway: When having enabled "airplane mode" (WiFi and Bluetooth OFF) on my Lenovo ThinkPad E15 Gen 2, airplane mode is disabled after reboot, and even before login I'm prompted for a WiFi password repeatedly (which I don't what to enter at that point). What makes matters worse is that the keyboard hotkey to toggle airplane mode does work only after having logged in to GNOME. Unsure whether it's base system or GNOME. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226517] New: After snapper rollback/restore marks packages as explicitly installed which were autoinstalled previously
by bugzilla_noreply＠suse.com 28 Jul '24

28 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226517 Bug ID: 1226517 Summary: After snapper rollback/restore marks packages as explicitly installed which were autoinstalled previously Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: ors0092(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Yesterday, I filed a bug report directly on Snapper's upstream GitHub, as I was advised to do so on the Matrix support chat (https://github.com/openSUSE/snapper/issues/916) However, the issue was closed and I was redirected here. Two days ago, I accidentally noticed something strange. I don't know if this is how Snapper is supposed to work, but here are my observations and steps to reproduce: 1. I installed `firewall-applet` manually, and zypper marked it with `i+` as explicitly installed. It also pulled `firewall-config` automatically as a dependency (marking it with `i` as auto-installed status) - so far, so good. 2. Then, I did a `sudo zypper rm --clean-deps firewall-applet`, and it perfectly caught `firewall-config` too, as it was installed automatically as a dependency. 3. Next, I did a reboot and told Snapper to use the `post` snapshot from the time when `firewall-applet` was installed. This reverted the removal process to the point where `firewall-applet` was installed instead, so chronologically we are at step 1. 4. In the read-only mode, I did a `zypper se -i firewall-`, and to my surprise, `firewall-config` was also marked with `i+`. 5. I made the `sudo snapper rollback` to see the changes live, and yes, `firewall-config` was still marked with `i+`. 6. When I did `sudo zypper rm --clean-deps firewall-applet`, it no longer recognized `firewall-config` to be auto-removed since it was marked as explicitly installed. 7. This can be also reproduced without rebooting when steps are done from the GUI YaST2 snapshot tool. 8. Since it was late yesterday, I thought I was too tired and maybe misunderstood something. So, I double-checked myself and simulated the steps I made yesterday, just to confirm my theory, and yepp - same results. No idea why, but snapper removes any affected packages during a snapper procedure within `/var/lib/zypp/AutoInstalled` but this step is nowhere logged. Also an additional question for us affected users: how do we trace back which packages were marked by these rollbacks? As you might guess, there could be plenty of unnecessary packages using extra drive space, now that are explicitly marked and thus never get removed via `sudo zypper dup --remove-orphaned` nor gets listed by `zypper pa --orphaned` or `zypper pa --unneeded` sadly. 4years ago it seems it got already uncovered under boo 1175304, but is also reported under Leap, this ticket is all about Tumbleweed experiences. Operating System: openSUSE Tumbleweed 20240617 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.4-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 Manufacturer: MSI Product Name: MS-7972 System Version: 2.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1226391] New: cockpit-machines missing dependency to libvirt
by bugzilla_noreply＠suse.com 27 Jul '24

27 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226391 Bug ID: 1226391 Summary: cockpit-machines missing dependency to libvirt Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: noah(a)simai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- i installed cockpit-machines using zypper started the module in my browser it told me hardware virtualization was disabled i clicked ignore it told me libvirt is not active i looked into my installed packages to notice libvirt wasnt installed i installed libvirt using zypper enabled and started the service with cockpit virtual machines module works now :D -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1227210] New: bash-git-prompt only works for login shells
by bugzilla_noreply＠suse.com 27 Jul '24

27 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227210 Bug ID: 1227210 Summary: bash-git-prompt only works for login shells Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: lassi.vaatamoinen(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There's a slight bug in the package, caused by the fact that /etc/profile.d/bash-git-prompt.sh is executed via /etc/profile. Now, the bash-git-prompt works properly when you login for example on a non-graphical TTY, or via SSH (even on localhost), as here we get a login shell. BUT when you enter to a desktop environment, and use a terminal application, bash-git-prompt __git_ps1 gets overridden by /etc/bash_completion.d/git-prompt that comes as part of git-core, as that script is executed for non-login shell by /etc/bash.bashrc So, the sequence of issues to the problem is here: User comes to a login screen (e.g. SDDM) LOGIN -> /etc/profile gets executed /etc/profile.d/bash-git-prompt.sh PROFILEREAD=true Open Konsole /etc/bash.bashrc (and ~/.bashrc) get executed /etc/bash_completion.d/git-prompt is executed -> overrides the previously set git prompt. -> bash-git-prompt is only usable for login shells (sudo -i, ssh, TTY), not in graphical desktop envs. NOTE: it does not matter if for Konsole, you set startup command as '/bin/bash --login' , since PROFILEREAD=true already (I assume), so the bash-git-prompt scripts won't get run. IMPROVEMENT: make bash-git-propmt run in the bashrc -sequence, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1226912] New: gnupg problem with socket connection
by bugzilla_noreply＠suse.com 27 Jul '24

27 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226912 Bug ID: 1226912 Summary: gnupg problem with socket connection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I want to verify a tarball using gnupg: docb@X1E:~/buildservice/Application:ERP:GNUHealth:Factory/mygnuhealth> gpg --default-key mygnuhealth.keyring --verify mygnuhealth-2.2.0.tar.gz.sig can't connect to 'socket:///home/docb/.gnupg/log-socket': No such file or directory The error message does not change if I create this file, I can work around it with the option --log-file=~/gnupg.log (even if it does not create a log, but thats probably a different story. I found https://forum.gnupg.org/t/problem-with-socket-connection-refused/4669 dealing with this problem, however it does not offer a solution -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226656] New: rsync --chown sets permissions to root:root after upgrade to Leap 15.6
by bugzilla_noreply＠suse.com 26 Jul '24

26 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226656 Bug ID: 1226656 Summary: rsync --chown sets permissions to root:root after upgrade to Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, On the client: ``` rsync -a --delete --super --owner --group --chown=477:479 --chmod='u=rwX,g=rX,o=' $PWD/ rsync://saltpush@witch1.infra.opensuse.org:873/salt-push/ ``` On the server, rsyncd.socket is listening with the following /etc/rsyncd.conf: ``` # Salt managed defaults address = :: gid = users log format = %h %o %f %l %b secrets file = /etc/rsyncd.secrets transfer logging = True use chroot = True # Salt managed modules [salt-push] path = /srv/salt-git/ comment = /srv/salt-git/ list = false uid = root gid = salt auth users = saltpush read only = False hosts allow = 2a07:de40:b27e:1203::126, 2a07:de40:b27e:1203::127 ``` With Leap 15.5, sync operations would keep the expected permissions and ownership on the directory /srv/salt-git and its contents. After the upgrade to Leap 15.6, which installed `rsync-3.2.7-150600.1.5.x86_64` on both the client and server side, the following happens: ``` root@witch1 ~# chown -R 477:479 /srv/salt-git root@witch1 ~# ls -dn /srv/salt-git drwxr-x--- 1 477 479 426 Jun 20 16:35 /srv/salt-git/ 8ec7287bf746:/srv/salt-git # rsync -a --delete --owner --group --chown=477:479 --chmod='u=rwX,g=rX,o=' $PWD/ rsync://saltpush@witch1.infra.opensuse.org:873/salt-push/ root@witch1 ~# ls -dn /srv/salt-git drwxr-x--- 1 0 0 426 Jun 20 16:35 /srv/salt-git/ ``` The directory gets recursively owned as root:root instead of keeping 477:479. -- You are receiving this mail because: You are on the CC list for the bug.

1 5