September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1199477] New: [Build 20220509] system_role is not fully visualized
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199477 Bug ID: 1199477 Summary: [Build 20220509] system_role is not fully visualized Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2337286/modules/syst em_role/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote_vnc_controller@64bit fails in [system_role](https://openqa.opensuse.org/tests/2337286/modules/system_role/… ## Test suite description Controller performs remote installation via vnc to the target It is missing the bottom part of the transactional system role. Could be a bug in X, the VNC layers or the client. When trying to click on the radiobutton the page is not ready and the radiobutton is not selected. I doubt it will be a YaST bug, after waiting a bit the screen is again ok to interact with it. ## Expected result Last good: [20220217](https://openqa.opensuse.org/tests/2195844) (or more recent) -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1197269] New: Failed to get GBM bo for flip to new front.... spamming forever on Xorg.0.log
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1197269 Bug ID: 1197269 Summary: Failed to get GBM bo for flip to new front.... spamming forever on Xorg.0.log Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: olivpass(a)web.de QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.51 Safari/537.36 Build Identifier: Desktop environment: xfce, with activated komposit ``` grep EE.*flip /var/log/Xorg.0.log | wc -l 405912 itnbltest154:/icpers/ms/home # grep EE.*flip /var/log/Xorg.0.log | tail [ 88161.296] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 88161.296] (EE) modeset(0): present flip failed [ 88161.308] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 88161.308] (EE) modeset(0): present flip failed [ 88161.372] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 88161.372] (EE) modeset(0): present flip failed [ 88161.524] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 88161.524] (EE) modeset(0): present flip failed [ 88162.133] (EE) modeset(0): Failed to get GBM bo for flip to new front. [ 88162.133] (EE) modeset(0): present flip failed itnbltest154:/icpers/ms/home # hwinfo --gfxcard 27: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.Hd7BnpKZdtA SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel VGA compatible controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x9a60 SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x0a67 Revision: 0x01 Driver: "i915" Driver Modules: "i915" Memory Range: 0x6052000000-0x6052ffffff (rw,non-prefetchable) Memory Range: 0x4000000000-0x400fffffff (ro,non-prefetchable) I/O Ports: 0x3000-0x303f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 166 (3901402 events) Module Alias: "pci:v00008086d00009A60sv00001028sd00000A67bc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Primary display adapter: #27 ``` with deaktivated komposit the massive output of this message stops. See also following: * https://dwaves.de/2019/08/14/debian-10-mate-gnome2-desktop-failed-to-get-gb… * https://bugzilla.redhat.com/show_bug.cgi?id=1645553 * https://community.parrotsec.org/t/self-reseting-to-loging-screen/3368 Reproducible: Always Steps to Reproduce: 1. gfx driver i915 2. X11 not wayland 3. use xfce desktop 4. default activated komposit Expected Results: no massive messages -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1194159] New: xorg-x11-server: Failed to open 'xbb.conf': No such file or directory
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194159 Bug ID: 1194159 Summary: xorg-x11-server: Failed to open 'xbb.conf': No such file or directory Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Upgrading from Leap 15.2 to 15.3 via "zypper dup" showed this error message: (3788/5706) Installing: xorg-x11-server-1.20.3-22.5.33.1.x86_64 .....[done] Additional rpm output: Failed to open 'xbb.conf': No such file or directory Updating /etc/sysconfig/displaymanager ... -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1188970] New: Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188970 Bug ID: 1188970 Summary: Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: marc(a)msys.ch QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 851469 --> http://bugzilla.opensuse.org/attachment.cgi?id=851469&action=edit Xorg.0.log showing the degmentation fault. When a USB DisplayLink display is connected to the system, Xorg segfaults while starting. lsusb lists the following display device: Bus 001 Device 019: ID 17e9:039a DisplayLink PA35 USB Display This is a regression, it worked without problems in openSUSE Leap 15.2. The hardware is an Aures Twist POS terminal with touchscreen. Xorg.0.log ais attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 62

[Bug 1186092] New: Invisible windows on clean Leap 15.3 beta install with gnome and wayland
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1186092 Bug ID: 1186092 Summary: Invisible windows on clean Leap 15.3 beta install with gnome and wayland Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: 64bit OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: alex.a(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 849362 --> http://bugzilla.opensuse.org/attachment.cgi?id=849362&action=edit Invisible opensuse welcome window Hi, I'm now testing Leap 15.3 beta on a clean install and many windows from new opened programs stay invisible or just have a shadow like in the attached picture. The programs itself are running as I can see them with ps and in the dash. Some windows are visible: e.g. Firefox, Thunderbird, Nautilus, Terminal. I've traced it down that removing gnome-session-wayland solves the issue. However without it other things don't work, e.g. my 2nd Monitor stays black, terminal takes long time to open. Before that I've upgraded from Leap 15.2 to 15.3 and gnome was crashing when opening same windows which stay invisible now (Firefox etc. worked fine). In journalctl I see a lot of "... gnome-shell[xxxx]: Modifiers specified, but DRI is too old" entries. Seems to be related to Mesa driver (?). The versions of Mesa and Mesa-dri do not match. Nothing interesting in dmesg. Have never seen such issue on Leap 15.2 and Tumbleweed before. Tried without success: use only one monitor, disable gnome extensions, install vendor GPU driver. Have seen some related issues with KDE plasma: https://forums.opensuse.org/showthread.php/539874-Wayland-Plasma-Applicatio… Can't use the workaround suggested there as there are no such options with gnome. package versions: gnome-session-wayland 3.34.2-6.3.1 Mesa 20.2.4-57.13 Mesa-dri 20.2.4-57.12 My specs: CPU: AMD Ryzen 5 3600, GPU: AMD Radeon RX 5700 OpenSUSE 15.3 beta Kernel: 5.3.18-57-default x86_6 from inxi -GxxSza: Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: Tul driver: amdgpu v: kernel bus ID: 28:00.0 chip ID: 1002:731f Display: wayland server: X.Org 1.20.3 compositor: gnome-shell driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa display ID: :0 screens: 1 OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.39.0 5.3.18-57-default LLVM 11.0.1) v: 4.6 Mesa 20.2.4 direct render: Yes -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1184906] New: gnome transparent window
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184906 Bug ID: 1184906 Summary: gnome transparent window Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: 8494(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 848459 --> http://bugzilla.opensuse.org/attachment.cgi?id=848459&action=edit screenclip of transparent welcome window directly after login Hello, After installing server, server-extra and server-wayland from: https://download.opensuse.org/repositories/home:/yudaike:/branches:/SUSE:/S… and logging into option Gnome, the welcome window is transparent. Filemanager, firefox, is not transparent. Please see attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1184543] New: wayand crashes when trying to display keyboard layout in GNOME live system
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184543 Bug ID: 1184543 Summary: wayand crashes when trying to display keyboard layout in GNOME live system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Whenever I try to display the keyboard layout in the GNOME live system (openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso), something odd happens: Suddenly there are a few text characters in the upper left corner of the screen, and the graphical background is all gone. It looks as if the system has crashed, while keys pressed are displayed. As it turned out from journal, wayland had crashed: pr 08 21:04:44 linux.fritz.box systemd[2492]: Started Application launched by gnome-shell. Apr 08 21:04:44 linux.fritz.box gnome-shell[4182]: syntax error: line 1 of stdin Apr 08 21:04:44 linux.fritz.box gnome-shell[4182]: Errors encountered in stdin; not compiled. Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: The XKEYBOARD keymap compiler (xkbcomp) reports: Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: > Internal error: Could not resolve keysym XF86WWAN Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: > Internal error: Could not resolve keysym XF86RFKill Apr 08 21:04:44 linux.fritz.box gnome-shell[4184]: Errors from xkbcomp are not fatal to the X server Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Modifiers specified, but DRI is too old Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Modifiers specified, but DRI is too old Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Backtrace: Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 0: /usr/bin/Xwayland (xorg_backtrace+0x65) [0x55f1d24fd375] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 1: /usr/bin/Xwayland (0x55f1d2361000+0x1a0049) [0x55f1d2501049] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 2: /lib64/libpthread.so.0 (0x7f00e9e8e000+0x13f80) [0x7f00e9ea1f80] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 3: /usr/bin/Xwayland (0x55f1d2361000+0x4faec) [0x55f1d23b0aec] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 4: /usr/bin/Xwayland (0x55f1d2361000+0x46188) [0x55f1d23a7188] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 5: /usr/bin/Xwayland (BlockHandler+0x3a) [0x55f1d24cf9ca] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 6: /usr/bin/Xwayland (WaitForSomething+0xd7) [0x55f1d24faa97] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 7: /usr/bin/Xwayland (0x55f1d2361000+0x169de3) [0x55f1d24cade3] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 8: /usr/bin/Xwayland (0x55f1d2361000+0x16e03c) [0x55f1d24cf03c] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f00e9aef34d] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) 10: /usr/bin/Xwayland (_start+0x2a) [0x55f1d23a623a] Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Segmentation fault at address 0x0 Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: Fatal server error: Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Caught signal 11 (Segmentation fault). Server aborting Apr 08 21:04:44 linux.fritz.box gnome-shell[2646]: (EE) Apr 08 21:04:44 linux.fritz.box gkbd-keyboard-d[4179]: gkbd-keyboard-display: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 08 21:04:44 linux.fritz.box gnome-shell[2593]: Connection to xwayland lost Apr 08 21:04:44 linux.fritz.box gsd-xsettings[2828]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Apr 08 21:04:44 linux.fritz.box systemd[2492]: gnome-launched-gkbd-keyboard-display-4179.scope: Succeeded. ... When waiting long enough, the display manager is started again (by systemd, I guess). However it's not obvious to the user what had happened (I also had reset the computer the first time). -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1184072] New: Gnome login failure
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184072 Bug ID: 1184072 Summary: Gnome login failure Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: 8494(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fresh install of 15.3 Beta. Using Thinkpad E595 AMD 3700u. Selecting Gnome login option. ( the X11 versions all work like classic etc ) The screens goes to black for a second or two after clicking login button, the mousepointer seems to freeze and then I'm back at the login screen. Anyone know of logs I should attach? -- You are receiving this mail because: You are on the CC list for the bug.

1 31

[Bug 1182510] New: broken formatting for man page: modesetting
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182510 Bug ID: 1182510 Summary: broken formatting for man page: modesetting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846331 --> http://bugzilla.opensuse.org/attachment.cgi?id=846331&action=edit fix for modesetting man page xorg-server < 1.20.6 On leap 15.2 the command man modesetting shows incorrect formatting (like: MODESETTING(@drivermansuffix@) instead of: MODESETTING(4)) This issue was fixed upstream in xorg-server-1.20.6 however since the upcoming leap 15.3 still comes with xorg-server-1.20.3 I suggest to apply the attached patch to the package xorg-x11-server in order to fix the issue in 15.2/15.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1199661] New: amd-pstate CPU Performance Scaling Driver
by bugzilla_noreply＠suse.com 07 Nov '22

07 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199661 Bug ID: 1199661 Summary: amd-pstate CPU Performance Scaling Driver Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, is there an easy way to activate the new amd-pstate driver on Tumbleweed? I've tried: kernel-parameters: amd_pstate.replace=1 and amd_pstate.shared_mem=1 additionally I created a file named /etc/modules-load.d/amd-pstate.conf inside: # Load amd pstate at boot amd_pstate However it still defaults to: cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq Anything I'm missing here? Thanks for your help -- You are receiving this mail because: You are on the CC list for the bug.

1 9