February 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1208248] libopenblas-pthreads0 missing a file?
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208248 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208336] New: The Nextcloud installer does not create the users necessary to correct install Nextcloud.
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208336 Bug ID: 1208336 Summary: The Nextcloud installer does not create the users necessary to correct install Nextcloud. Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software Assignee: screening-team-bugs(a)suse.de Reporter: rokejulianlockhart+1674683091(a)outlook.com QA Contact: screening-team-bugs(a)suse.de Found By: --- Blocker: --- https://github.com/nextcloud/server/issues/36460#issue-1564866420 explains the problem. I won't duplicate the explanation because it's solely one click away and is reliant upon Markdown, which this does not appear to support. -- https://github.com/nextcloud/server/issues/36460#issuecomment-1419952140 states that somewhere in bugzilla.opensuse.org should be the correct place for this report. However, please note that I had no more idea than that of where to file this report, per https://unix.stackexchange.com/a/735651/386242. Selecting the correct component is significantly less intuitive than redhat.bugzilla.org's organization (there, components are packages). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1208198] Tumbleweed from 20230213 (glibc 2.37) has stack protector triggering in libdl of libGLX_nvidia.so.0
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208198 http://bugzilla.opensuse.org/show_bug.cgi?id=1208198#c38 --- Comment #38 from patrick shanahan <paka(a)opensuse.org> --- rebooted with upddated nvidia tw packages and glibc 2.37-1. have X but using nouveau, not nvidia attaching Xorg.0.log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208198] Tumbleweed from 20230213 (glibc 2.37) has stack protector triggering in libdl of libGLX_nvidia.so.0
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208198 http://bugzilla.opensuse.org/show_bug.cgi?id=1208198#c37 --- Comment #37 from patrick shanahan <paka(a)opensuse.org> --- Created attachment 864918 --> http://bugzilla.opensuse.org/attachment.cgi?id=864918&action=edit Xorg log -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175850] New: MicroOS Desktop can't reboot?
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1175850 Bug ID: 1175850 Summary: MicroOS Desktop can't reboot? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: mike(a)flingtoad.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a default install of MicroOS Desktop (KDE) (ALPHA) 20200824-0, there is no obvious way to reboot the machine after install packaged with transactional-update. Here's what I've tried. 1. 'transactional-update reboot' (notifies rebootmgrctl that a reboot is requested, but 'rebootmgrctl status' seems to be waiting for the scheduled maintenance time. 2. 'rebootmgrctl reboot now' does not seem to do anything. 3. 'rebootmgrctl reboot fast' does not seem to do anything. 4. Click "Leave" -> "Restart" from KDE menu does not seem to do anything. 5. Click "Leave" -> "Shutdown" from KDE menu does not seem to do anything. 6. Click "Leave" -> "Shutdown" from KDE menu does not seem to do anything. 7. 'systemctl reboot' drops to a non-graphical target with login prompt, but doesn't continue with a reboot. 8. 'shutdown -r now' drops to a non-graphical target with login prompt, but doesn't continue with a reboot. 9. 'shutdown -h now' complains about not being able to unmount /etc, but eventually does halt. 10. 'systemctl reboot' to drop to term and the ctrl-alt-delete several times does eventually reboot >From what I can tell, 4-6 only happen when running the X session for KDE. If you run the Wayland session, 4-6 work but the others still don't. I haven't tried Wayland (Full). Other notes and observations: 1. I don't think the X session is starting the org.kde.ksmserver, but it does get started for Wayland. 2. I'm using full-disk encryption. 3. No matter how I exit the KDE session, it never saved my display configuration. I have to reconfigure the displays each time. Perhaps another bug report for this one. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1208262] New: TigerVNC 1.13.0 available (new version)
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208262 Bug ID: 1208262 Summary: TigerVNC 1.13.0 available (new version) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All URL: https://github.com/TigerVNC/tigervnc/releases/tag/v1.1 3.0 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: jayjayjazz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- TigerVNC 1.13.0 is now available. The most prominent changes in this release are: The servers and native viewer now support RealVNC's RSA-AES authentication methods and encryption The native viewer is now translated to Romanian and Georgian The native viewer now (optionally) supports PiKVM's H.264 encoding The display settings for the native viewer have been overhauled to make them easier to understand The native viewer now supports adding exceptions for expired certificates Resolved an issue where full-screen mode didn't work in the native viewer on macOS 13 Lock key synchronization has been re-enabled in the native viewer after being accidentally disabled in 1.11.0 Xvnc/libvnc.so can now be built with Xorg 1.21 x0vncserver is a bit better at handling differing server and client keyboard layout x0vncserver now correctly handles zaphod mode Added Ubuntu 22.04 and RHEL 9 packages Binaries are available from SourceForge: https://sourceforge.net/projects/tigervnc/files/stable/1.13.0 Release Notes: https://github.com/TigerVNC/tigervnc/releases/tag/v1.13.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1208258] [Build 399.1] yast2_ntpclient - in/cp: cannot stat '/mnt/boot/vmlinuz': No such file or directory
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208258 https://bugzilla.suse.com/show_bug.cgi?id=1208258#c6 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #6 from Stefan Hundhammer <shundhammer(a)suse.com> --- So, in summary, the part that made the OpenQA test fail is the changed path that needs to be adapted in the test, and the other part is just a log message that is too noisy. The need to adapt the test is tracked at https://progress.opensuse.org/issues/124640. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1208258] [Build 399.1] yast2_ntpclient - in/cp: cannot stat '/mnt/boot/vmlinuz': No such file or directory
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1208258 https://bugzilla.suse.com/show_bug.cgi?id=1208258#c5 --- Comment #5 from Stefan Hundhammer <shundhammer(a)suse.com> --- That other message is probably harmless: 22023-02-12 17:08:06 <1> install(3533) [Ruby] bin/y2start(<main>):22 y2base called with ["installation", "--arg", "initial", "qt", "--noborder", "--auto-fonts", "--fullscreen"] ... ... 023-02-12 12:22:02 <3> ip-10-0-2-15(3533) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat '/mnt/boot/vmlinuz': No such file or directory 2023-02-12 12:22:02 <1> ip-10-0-2-15(3533) [Ruby] bootloader/kexec.rb(copy_kernel):110 Command for copy: /bin/cp -L /mnt/boot/vmlinuz /mnt/boot/initrd /var/lib/YaST2 and result {"exit"=>1, "stderr"=> "/bin/cp: cannot stat '/mnt/boot/vmlinuz': No such file or directory\n", "stdout"=>""} 2023-02-12 12:22:02 <3> ip-10-0-2-15(3533) [Ruby] bootloader/kexec.rb(copy_kernel):112 Copy kernel and initrd failed, output: {"exit"=>1, "stderr"=> "/bin/cp: cannot stat '/mnt/boot/vmlinuz': No such file or directory\n", "stdout"=>""} /boot/vmlinuz (or like here in the inst-sys, /mnt/boot/vmlinuz) is normally a symlink to the current default kernel. It looks like at that point that link does not (yet) exist. But a kernel with the full name obviously exists because the system booted successfully. Why we are trying to copy (as a symlink (-L), if possible) the current kernel and the initrd to /var/lib/YaST2 is not clear to me; possibly to use "kexec" instead of a real boot. But anyway, this is nothing to worry about AFAICS. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207949] Nautilus: the toggle to set file executable permissions is missing (via NFS)
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207949 https://bugzilla.suse.com/show_bug.cgi?id=1207949#c6 --- Comment #6 from C J <c.j(a)tuta.io> --- (In reply to Alynx Zhou from comment #5) > That depends on MIME types, I have the toggle for a script without extension. Ah ok, so we now have to set this manually with the mime types. Thanks for the feedback! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202526] QT6 apps don't get Adwaita styling applied under GNOME
by bugzilla_noreply＠suse.com 15 Feb '23

15 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1202526 https://bugzilla.suse.com/show_bug.cgi?id=1202526#c41 C J <c.j(a)tuta.io> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #41 from C J <c.j(a)tuta.io> --- (In reply to Alynx Zhou from comment #40) I'm not sure it's the same issue, as in your link the theme isn't applied at all. Here, the theme is applied but the dark colors are missing (see screenshot). But: this was now fixed again after an update (it seems to break every 1 or 2 months and then is fixed again, so I have reopened and closed this bug several times already). -> closing again, (hope this time its definitive). -- You are receiving this mail because: You are on the CC list for the bug.

1 0