January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193397 https://bugzilla.suse.com/show_bug.cgi?id=1193397#c33 --- Comment #33 from Takashi Iwai <tiwai(a)suse.com> --- The kernel in OBS Kernel:stable:Backport is equivalent with TW kernel (can be even newer), just built for Leap file hierarchy without UsrMerge. Checking with that kernel would make clearer whether it's fixed solely in kernel or not. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194419] New: X11:common:Factory/fltk: Passing '-pie' in LDFLAGS breaks any shared lib build using fltk-config
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194419 Bug ID: 1194419 Summary: X11:common:Factory/fltk: Passing '-pie' in LDFLAGS breaks any shared lib build using fltk-config Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pgajdos(a)suse.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: screening-team-bugs(a)suse.de CC: dmueller(a)suse.com Found By: --- Blocker: --- With fltk 1.3.8, the LDFLAGS used to build libfltk are pulled into the LDFLAGS returned from `fltk-config --ldflags`. This breaks build of any shared library linking with libfltk, as `gcc -shared ... -pie ...` negates the `-shared`, i.e. GCC tries to built an executable instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1194506] New: GDM is started inappropriately
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194506 Bug ID: 1194506 Summary: GDM is started inappropriately Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: nwr10cst-oslnx(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Build Identifier: The problem occurred during an update. I think it happened both for the update to 20220106 and to 20220107. I booted up. Instead of a graphic login, I used CTRL-ALT-F1 to get a virtual console, and I logged in there as root. Before updating, I used telinit 3 to switch to multi-user mode. That was to be sure that GDM should not even be running. When updating, I normally start with zypper up libsolv-tools libzypp zypper rpm NetworkManager wicked autofs systemd and I follow that with "zypper dup". On this occasion, when it finished the preliminary update, a GDM screen showed up, even though GDM should not have been running. I think that was started by the install script for "systemd", but I cannot be sure of that. The system went into an unresponsive state. It did not respond to keyboard or to mouse. An attempt to do CTRL-ALT-F1 had no effect at all. From a different computer, I was able to ssh into this one, and again run: telinit 3 That killed GDM, and got my session back where I could continue the update (i.e. run "zypper dup". It seems to me that there are two bugs here: (1) GDM should not have been started at that time. I assume that's a "systemd" issue. (2) Given that GDM was started, it should have responded to the keyboard and allowed me to use CTRL-ALT-F1 to get back to my update session. Note1: On a computer using SDDM and another using lightdm, I did not see any problems. I actually updated those via an xterm run from the graphic interface. I am only seeing problems where GDM is the displaymanager. Note2: On another computer, I appended "3" to the kernel command line for booting, to get to multi-user mode. I did not have any problems updating that system, and GDM was never started there. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193397] amdgpu: Monitor NO signal if it hasn't been on since system boot
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1193397 https://bugzilla.suse.com/show_bug.cgi?id=1193397#c32 --- Comment #32 from Kourosh P. <kourosh(a)pourdanandeh.com> --- (In reply to Takashi Iwai from comment #31) > Could you check whether the issue is seen with the latest kernel in OBS > Kernel:stable:Backport? (without AMDGPU pro.) > > If the problem is still present with the latest kernel, we need to report to > the upstream devs, gitlab.freedesktop.org Issues. Thank you for your follow-up. Is it possible to install TW on my test SSD and test it? I believe TW runs the latest kernel, right? My daily driver has been Leap since 2016. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185444] New: Stellarium: cannot toggle full screen mode on GNOME 40
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1185444 Bug ID: 1185444 Summary: Stellarium: cannot toggle full screen mode on GNOME 40 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: pstivanin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've opened an issue upstream (https://github.com/Stellarium/stellarium/issues/1625), because since the update to GNOME 40 full screen mode cannot be toggled anymore. It works fine on KDE, and it was working fine on GNOME 3.38, so the issue is definitely due to GNOME 40. How to reproduce: * install openSUSE Tumbleweed with GNOME 40.x * install Stellarium 0.21.0 * Stellarium starts in full screen mode. Press F11 and watch the window disappear, but with ps aux we can see that the process is still alive in bg. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1074057] qemu can't properly capture some keys in libreoffice under GNOME wayland
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1074057 https://bugzilla.suse.com/show_bug.cgi?id=1074057#c90 --- Comment #90 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: qam-regression-gnome@64bit-virtio-vga https://openqa.suse.de/tests/7955409 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191425] [Build 20211005] openQA test fails in salt_master
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1191425 https://bugzilla.suse.com/show_bug.cgi?id=1191425#c6 --- Comment #6 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: salt-master https://openqa.opensuse.org/tests/2129836 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192140] [Build 20211027] openQA test fails in cifs
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1192140 https://bugzilla.suse.com/show_bug.cgi?id=1192140#c6 --- Comment #6 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_filesystem https://openqa.opensuse.org/tests/2126618 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194156] iputils: setting /usr/bin/ping to root:root 0755 "= cap_net_raw+ep". (wrong missing capabilities)
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194156 https://bugzilla.suse.com/show_bug.cgi?id=1194156#c8 --- Comment #8 from Petr Vorel <petr.vorel(a)suse.com> --- Can you actually use ping as user? $ ping -c1 ::1; echo $? PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.057 ms --- ::1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.057/0.057/0.057/0.000 ms 0 Also, due #1174504 you should not need any capability: $ getcap `which ping` # nothing -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194156] iputils: setting /usr/bin/ping to root:root 0755 "= cap_net_raw+ep". (wrong missing capabilities)
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194156 https://bugzilla.suse.com/show_bug.cgi?id=1194156#c7 Petr Vorel <petr.vorel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |petr.vorel(a)suse.com See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1174504 --- Comment #7 from Petr Vorel <petr.vorel(a)suse.com> --- Can you use pin -- You are receiving this mail because: You are on the CC list for the bug.

1 0