April 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1209436] New: I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1209436 Bug ID: 1209436 Summary: I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Got new kernel from zypper up. Rebooted and it hang on line switching from VGA to i915. Had to power off and select previous kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 68

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 02 Apr '23

02 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c76 --- Comment #76 from George Johnson <gjjohnson(a)fwsi.com> --- New Kernel 5.14.21-150400.24.55-default resolves the hang for me on Lenovo Thinkpad p50. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210028] New: When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210028 Bug ID: 1210028 Summary: When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: statusinformatica13(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hey guys When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open. Error message: edson@localhost:~> torbrowser-launcher Lan�ador do Navegador Tor Por Micah Lee, licenciado sob o MIT vers�o 0.3.6 https://github.com/micahflee/torbrowser-launcher Traceback (most recent call last): File "/usr/bin/torbrowser-launcher", line 30, in <module> torbrowser_launcher.main() File "/usr/lib/python3.10/site-packages/torbrowser_launcher/__init__.py", line 76, in main common = Common(tor_browser_launcher_version) File "/usr/lib/python3.10/site-packages/torbrowser_launcher/common.py", line 62, in __init__ self.torbrowser12_rename_old_tbb() File "/usr/lib/python3.10/site-packages/torbrowser_launcher/common.py", line 185, in torbrowser12_rename_old_tbb os.rename(abs_filename, self.paths["tbb"]["dir_tbb"]) FileExistsError: [Errno 17] File exists: '/home/edson/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US' -> '/home/edson/.local/share/torbrowser/tbb/x86_64/tor-browser' edson@localhost:~> -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1210026] New: Delay of portal service start on MicroOS Desktop KDE delays flatpak application startup.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1210026 Bug ID: 1210026 Summary: Delay of portal service start on MicroOS Desktop KDE delays flatpak application startup. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: touko.alasavikota(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running MicroOS Desktop KDE snapshot 20230330 (originally 20230212). Proprietary nvidia drivers and wayland. My install comes automatically with multiple xdg-desktop-portal backends: xdg-desktop-portal-gnome, xdg-desktop-portal-kde and xdg-desktop-portal-gtk. The problem is that the GNOME backend is started first and it times out and fails. I think that this delays the start of xdg-desktop-portal and flatpak applications like Firefox won't start during the delay. The portal service is able to start after the timeout and everything works normally after that. This github issue might be related: https://github.com/flatpak/xdg-desktop-portal/issues/656 I tested installing a fresh MicroOS Desktop 20230330 with both GNOME and KDE flavors. They only had the their respective backends installed with no flatpak application launch delays on startup. My other MicroOS Desktop KDE is originally from snapshot 20230212 so that might have had the GNOME implementation included from the start. I'm not sure if multiple xdg-desktop-portal implementations should even be installed in the first place but in this state the system will have a consistent timeout with every boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c75 --- Comment #75 from Rolf Breuning <Rolf.Breuning(a)t-online.de> --- Solved for me by the new kernel 5.14.21-150400.24.55, thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1209436] I915 hangs on Kernel vmlinuz-5.14.21-150400.24.49
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1209436 https://bugzilla.suse.com/show_bug.cgi?id=1209436#c74 --- Comment #74 from Volker Kuhlmann <bugz57(a)top.geek.nz> --- 5.14.21-150400.24.55-default works again and boots fine - thank you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210028] When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210028 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Other Assignee|yast2-maintainers(a)suse.de |screening-team-bugs(a)suse.de QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210028] When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210028 https://bugzilla.suse.com/show_bug.cgi?id=1210028#c1 --- Comment #1 from Stefan Hundhammer <shundhammer(a)suse.com> --- What makes you think that this would be an installer problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210028] When trying to open Torbrowser-launcher through the terminal, it displays an error message and does not open.
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210028 Stefan Hundhammer <shundhammer(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Normal -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202078] New: Plasma wayland cannot be set as default with autologin
by bugzilla_noreply＠suse.com 01 Apr '23

01 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202078 Bug ID: 1202078 Summary: Plasma wayland cannot be set as default with autologin Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Leap 15.4 with Plasma KDE 5.24.4 and all updates installed with autologin enabled. It works fine on X11. I tried to set Plasma Wayland as default via "System Settings-->Startup and Shutdown-->Login Screen (SDDM)-->Behavior-->choose Plasma Wayland", but then I will end in console instead in Plasma. Plasma Wayland itself works, if I keep old settings with autologin into X11 and then I just unlog to SDDM, change session and log with Wayland, it is ok. Just autologin will not boot. I can reproduce it both on my freshly installed Laptop with i5-11400H cpu with integrated graphics and in VirtualBox. I tested behavior in Fedora 36 without updates (similar components, Plasma 5.24.3, etc) and there autologin settings works fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 4