November 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1233149] New: System got stuck in "setting up" screen on first boot
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233149 Bug ID: 1233149 Summary: System got stuck in "setting up" screen on first boot Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: lzcoder(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878470 --> https://bugzilla.suse.com/attachment.cgi?id=878470&action=edit journalctl -p crit After installing the system with 20241106 image, it got stuck at the “setting up” screen on first boot. In my case I waited more than 30 minutes (in previous installations I didn't have to wait that long) and after waiting I restarted my system and everything seems to work correctly. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1233665] New: No thumbnails for some video formats files in Nautilus
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233665 Bug ID: 1233665 Summary: No thumbnails for some video formats files in Nautilus Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: kisskovacsattila(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Nautilus not generating thumbnails for mp4/mkv/mov... video files. I've installed ffmpegthumbnailer and totem-video-thumbnailer, but it doesn't resolve the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1233781] New: Installation stops with 'encrypted partition not found' (after it created it as seen in logs)
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233781 Bug ID: 1233781 Summary: Installation stops with 'encrypted partition not found' (after it created it as seen in logs) Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: igor.lautar(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878723 --> https://bugzilla.suse.com/attachment.cgi?id=878723&action=edit tik log file produced by install attempts I'm trying to install Aeon on my desktop PC (B650, 7800X3D, NVidia, 2x SSD, 192GB RAM). Using image: Aeon-Installer.x86_64-0.1.0-Snapshot20241124.raw.xz Created USB using xzcat and also Impression (same result). For debugging purposes, I did experiment with different HW configs, most notably pulling out NVidia card and moving SSDs to different slots. This is why there will be multiple 'installation attempts' in tik.log file. Let me know what else is needed, or I can also debug the process if instructions are provided. Apparently, the partitions were created, it seems like encrypted one 'is already mounted' and script gets confused at that point. I really want to try Aeon... Is there an older image I can try and install? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1233875] New: "Emergency mode" during install
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233875 Bug ID: 1233875 Summary: "Emergency mode" during install Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: main.text2175(a)fastmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 878756 --> https://bugzilla.suse.com/attachment.cgi?id=878756&action=edit emergency screen Occurred based on the latest image from https://aeondesktop.github.io on 11/28/24 (M/D/Y). The OpenSUSE Aeon installer boots and then enters some sort of error mode, I think it is dracut mode based on what I saw from troubleshooting. After restarting the error occurs again, and if you follow the instructions (Press Control-D to continue) you do reach the installer. However, the installer always fails after this error occurs. This error occurred many times, and then randomly didn't after a reboot and the installation finally worked, after ~10 reboots. This same error occurred a few months ago when I tried to install Aeon as well. I would love to have provided the full logs but I am unsure exactly how to at the moment as I currently only have one computer (with a USB-A port) which means I cannot extract data from the thumb drive. My only guess is maybe trying from the "live-environment" but that sounds too painful for me to do currently. I can get the full logs when I return home in a few weeks time. In lieu of that, I have attached pictures of anything notable I saw in the logs. Hopefully that will be helpful. This error may be similar or related to https://bugzilla.opensuse.org/show_bug.cgi?id=1232815 but I can't tell so I'm here. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1233824] New: [s390x] gnome-remote-desktop RDP-server does not start on s390x
by bugzilla_noreply＠suse.com 03 Jan '25

03 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233824 Bug ID: 1233824 Summary: [s390x] gnome-remote-desktop RDP-server does not start on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: martin.sirringhaus(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I can't get RDP to work on s390x, so I tried the same steps on a x86_64 VM and on s390x: ``` sudo zypper in -y gnome-remote-desktop freerdp-server # You probably have to do `su -` here first for this one: sudo -u gnome-remote-desktop winpr-makecert \ -silent -rdp -path ~gnome-remote-desktop rdp-tls # Set RDP_USER and RDP_PASS to whatever you want sudo grdctl --system rdp set-credentials "$RDP_USER" "$RDP_PASS" sudo grdctl --system rdp set-tls-key /var/lib/gnome-remote-desktop/rdp-tls.key sudo grdctl --system rdp set-tls-cert /var/lib/gnome-remote-desktop/rdp-tls.crt sudo grdctl --system rdp enable sudo systemctl --now enable gnome-remote-desktop.service ``` On both systems I get basically the same output for this: ``` # grdctl --system status Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Overall: Unit status: active RDP: Status: enabled Port: 3389 TLS certificate: /var/lib/gnome-remote-desktop/rdp-tls.crt TLS fingerprint: 1f:76:bb:d3:bd:42:fd:51:af:e7:89:64:e1:00:c2:78:d9:16:20:63:2b:08:84:ac:38:4e:79:48:c9:4a:07:db TLS key: /var/lib/gnome-remote-desktop/rdp-tls.key Username: (hidden) ``` `systemctl start gnome-remote-desktop` works fine on both systems, telling me that the service is up and running. On my VM, however, I get ``` Nov 27 14:04:03 localhost.localdomain systemd[1]: Starting GNOME Remote Desktop... Nov 27 14:04:03 localhost.localdomain gnome-remote-de[4244]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 14:04:03 localhost.localdomain systemd[1]: Started GNOME Remote Desktop. Nov 27 14:04:04 localhost.localdomain gnome-remote-de[4244]: RDP server started localhost:~ # ss -punta | grep gnome tcp LISTEN 0 10 *:3389 *:* users:(("gnome-remote-de",pid=4244,fd=9)) ``` whereas on s390x, I get: ``` Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Starting GNOME Remote Desktop... Nov 27 12:47:41 firefox.prg2.suse.org gnome-remote-de[15170]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback Nov 27 12:47:41 firefox.prg2.suse.org systemd[1]: Started GNOME Remote Desktop. firefox:~ # ss -punta | grep gnome firefox:~ # ``` Setting G_MESSAGES_DEBUG=all didn't reveal anything, either. Basically, all RDP-related output is missing on s390x. No additional info (that is not also logged on x86_64 with this env-variable). The RDP-server simply doesn't start up on s390x without any errors or logging. -- You are receiving this mail because: You are on the CC list for the bug.

1 35

[Bug 1229281] New: [Package: teleport] Webassets outdated
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1229281 Bug ID: 1229281 Summary: [Package: teleport] Webassets outdated 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: jankmann(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hope this is the right place to post this. The teleport package (https://build.opensuse.org/package/show/openSUSE:Factory/teleport) include outdated webassets which break the Web-GUI with version 16.X. The currently packaged Web-GUI still has the 15.X look and will not connect to any resource starting with 16.0.0. My current workaround is to replace the package binary with the official binary, which obviously breaks with each upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1233887] New: Have installer not set enforcing=1 in grub config, so /etc/selinux/config is ignored
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1233887 Bug ID: 1233887 Summary: Have installer not set enforcing=1 in grub config, so /etc/selinux/config is ignored Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jsegitz(a)suse.com QA Contact: jsrain(a)suse.com CC: cathy.hu(a)suse.com, mmeisters(a)suse.com, security-team(a)suse.de Depends on: 1232496 Target Milestone: --- Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1232496 +++ sl micro 5.5 has enforcing=1 in grub config, so /etc/selinux/config is ignored should be removed, otherwise it is confusing for users why changing /etc/selinux/config does not do anything -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1227749] New: Orange PI 5 Plus limited functionality
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1227749 Bug ID: 1227749 Summary: Orange PI 5 Plus limited functionality Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876046 --> https://bugzilla.suse.com/attachment.cgi?id=876046&action=edit idbloader for Orange PI 5 Plus I managed to get U-Boot running on the Orange PI 5 Plus with a couple of key SUSE patches to the point where it is booting into OpenSUSE AARCH64 Rockchip version. Currently only the following are working: - PCIe - NVME - eMMC/SD - Serial port The following are not working: - USB - Realtek RTL8125 2.5G Ethernet drivers (seen on PCIe bus) - Realtek RTL8852BE (seen on PCIe bus, not driver seems to be available) Note that in U-Boot that USB also does not work and the network cards are not supported (as of 7/15). I am attaching my U-Boot and idbloader for this board which should allow it to boot, use the usual offset 64 for the idbloader and offset 16384 for U-Boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1222902] New: Monitor detection fails after hard reset
by bugzilla_noreply＠suse.com 02 Jan '25

02 Jan '25

https://bugzilla.suse.com/show_bug.cgi?id=1222902 Bug ID: 1222902 Summary: Monitor detection fails after hard reset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: david.mulder(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a hard reset (laptop locked up when I tried to suspend it), my external monitors are no longer detected. I've seen this happen 3 times in as many weeks (on several recent versions of TW), and the only solution I've found is reinstalling TW. > sudo hwinfo --monitor 45: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.iVNqLoWlvi7 Parent ID: _Znp.TcrQYGYoBS2 Hardware Class: monitor Model: "BOE CQ LCD Monitor" Vendor: BOE "BOE CQ" Device: eisa 0x0a7d Serial ID: "0" Resolution: 1920x1200@60Hz Size: 345x215 mm Year of Manufacture: 2021 Week of Manufacture: 27 Detailed Timings #0: Resolution: 1920x1200 Horizontal: 1920 1968 2000 2140 (+48 +80 +220) -hsync Vertical: 1200 1203 1209 1260 (+3 +9 +60) +vsync Frequencies: 161.79 MHz, 75.60 kHz, 60.00 Hz Driver Info #0: Max. Resolution: 1920x1200 Vert. Sync Range: 40-60 Hz Hor. Sync Range: 76-76 kHz Bandwidth: 161 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #39 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1232668] New: displaylink driver uses wrong ethernet module cdc_ncm instead of r8152
by bugzilla_noreply＠suse.com 30 Dec '24

30 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1232668 Bug ID: 1232668 Summary: displaylink driver uses wrong ethernet module cdc_ncm instead of r8152 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: cookie170(a)web.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The Lenovo USB-C Hybrid Dock (40AF) comes with a Realtek chip for the ethernet connection: r8152 and as far as I can see the displaylink.rules assume, the correct driver for ethernet were cdc_ncm. But no: There is a special r8152 driver, which seems to be included in the kernel. cdc_ncm does not work well with this chip. Suspend leads to crash which causes strange network effects in LAN. See this file: https://build.opensuse.org/projects/X11:XOrg/packages/displaylink-driver/fi… Discussion see here: https://forums.opensuse.org/t/realtek-r8152-build-with-dkms-fails/179813 The displaylink driver is provided by X11:Xorg repo https://download.opensuse.org/repositories/X11:/XOrg/ Workaround: - Download r8152 from github, make, sudo depmod -a, sudo make install. Copy the udev-rules file from downloaded archive to /etc/udev/rules.d. The ethernet connection will work, until the next kernel update. I've no idea why dkms fails with r8152, I've described my efforts in the openSUSE forum, as linked above. I'm a user. It's simply my assumption that the rules file were the culprit. -- You are receiving this mail because: You are on the CC list for the bug.

1 6