May 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1185513] ACPI BIOS Error after upgrade to 5.12.0-1-default
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185513 https://bugzilla.suse.com/show_bug.cgi?id=1185513#c6 Joey Lee <jlee(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(iqgrande(a)gmail.co | |m) --- Comment #6 from Joey Lee <jlee(a)suse.com> --- Hi Anthony, Hans de Jong, Could you please provide acpidump result? Please use this command: # acpidump > acpidump.raw Please attached acpidump.raw result file on bugzilla. I want to check the acpi table for the _CPC. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185542] 32 bit Tumbleweed failing to boot with the 5.12.0-1-pae kernel must revert to 5.11.16-1-pae kernel.
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185542 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pj.world(a)gmx.com Flags| |needinfo?(pj.world(a)gmx.com) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185542] 32 bit Tumbleweed failing to boot with the 5.12.0-1-pae kernel must revert to 5.11.16-1-pae kernel.
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185542 https://bugzilla.suse.com/show_bug.cgi?id=1185542#c4 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- Could you try to install kernel-default-5.12 and check whether it boots or not, as asked in comment 1? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185531] virt-viewer 10.0 second display handling
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185531 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |carnold(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185048] Install on hi res laptop impossible to read
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185048 https://bugzilla.suse.com/show_bug.cgi?id=1185048#c12 --- Comment #12 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Eric Benton from comment #11) > ok, what is icewm? On the login screen, select "IceWM" as session. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185048] Install on hi res laptop impossible to read
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185048 https://bugzilla.suse.com/show_bug.cgi?id=1185048#c11 --- Comment #11 from Eric Benton <erbenton(a)comcast.net> --- ok, what is icewm? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184088] New: frequent usb resets starting with 5.11-rc7, 5.11-rc6 was fine
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1184088 Bug ID: 1184088 Summary: frequent usb resets starting with 5.11-rc7, 5.11-rc6 was fine 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: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some change between 5.11-rc6 and 5.11-rc7 is causing frequently storms of usb resets, significantly eating cpu power: [Sa M�r 27 20:17:47 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:17:52 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:17:58 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:18:03 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:18:09 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:18:15 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd [Sa M�r 27 20:18:20 2021] usb 3-1.1.3: reset high-speed USB device number 6 using xhci_hcd it stops usually after turning off/on the monitor (the usb hub this is connected to is builtin to my display), but sometimes it just stops by itself, and then at some later point in time resumes again. No idea what exactly triggers it, but I've never seen this with 5.11-rc6 or below. lsusb -t -v for this sub tree is: /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 18, If 0, Class=Hub, Driver=hub/6p, 480M ID 0451:8442 Texas Instruments, Inc. |__ Port 6: Dev 25, If 0, Class=, Driver=, 480M ID 0451:82ee Texas Instruments, Inc. |__ Port 2: Dev 21, If 3, Class=Human Interface Device, Driver=usbhid, 12M ID 047f:c025 Plantronics, Inc. |__ Port 2: Dev 21, If 1, Class=Audio, Driver=snd-usb-audio, 12M ID 047f:c025 Plantronics, Inc. |__ Port 2: Dev 21, If 2, Class=Audio, Driver=snd-usb-audio, 12M ID 047f:c025 Plantronics, Inc. |__ Port 2: Dev 21, If 0, Class=Audio, Driver=snd-usb-audio, 12M ID 047f:c025 Plantronics, Inc. |__ Port 5: Dev 24, If 0, Class=Human Interface Device, Driver=usbhid, 480M ID 0451:82ff Texas Instruments, Inc. |__ Port 1: Dev 19, If 0, Class=Hub, Driver=hub/4p, 480M ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub |__ Port 3: Dev 23, If 2, Class=Audio, Driver=snd-usb-audio, 480M ID 046d:0825 Logitech, Inc. Webcam C270 |__ Port 3: Dev 23, If 0, Class=Video, Driver=uvcvideo, 480M ID 046d:0825 Logitech, Inc. Webcam C270 |__ Port 3: Dev 23, If 3, Class=Audio, Driver=snd-usb-audio, 480M ID 046d:0825 Logitech, Inc. Webcam C270 |__ Port 3: Dev 23, If 1, Class=Video, Driver=uvcvideo, 480M ID 046d:0825 Logitech, Inc. Webcam C270 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1185561] Ruby error in installation after partitioning
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185561 https://bugzilla.suse.com/show_bug.cgi?id=1185561#c4 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium URL| |https://trello.com/c/Kq990Q | |ba Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de --- Comment #4 from Steffen Winterfeldt <snwint(a)suse.com> --- Possibly introduced here: https://github.com/yast/yast-yast2/pull/1143 Tracking in YaST Scrum board. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185048] Install on hi res laptop impossible to read
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185048 https://bugzilla.suse.com/show_bug.cgi?id=1185048#c10 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(erbenton@comcast. | |net) --- Comment #10 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Eric Benton from comment #9) > Here is the info: > $ QT_LOGGING_RULES=qt.qpa.screen.debug=true dolphin > qt.qpa.screen: EDID data for output "eDP-1": identifier 'NE156QUM-N67-', > manufacturer 'BOE',model '', serial '', physical size: 340.00x190.00 > qt.qpa.screen: EDID data for output "HDMI-1": identifier '', manufacturer > 'Toshiba America Info Systems Inc',model 'ScreenXpert--', serial > '2290649088', physical size: 60.00x130.00 > qt.qpa.screen: Output DP-1-0 is not connected > qt.qpa.screen: Output DP-1-1 is not connected > qt.qpa.screen: Output HDMI-1-0 is not connected > qt.qpa.screen: adding QXcbScreen(0x55e4ff8fa9a0, name="eDP-1", > geometry=3840x2160+0+0, availableGeometry=3840x2160+0+0, > devicePixelRatio=1.0, logicalDpi=QPair(192.0,192.0), > physicalSize=344.0x194.0mm, screenNumber=0, virtualSize=4920x2160 > (4920.0x2160.0mm), orientation=Qt::LandscapeOrientation, depth=24, > refreshRate=60.0, root=376, windowManagerName="KWin") (Primary: true ) > qt.qpa.screen: adding QXcbScreen(0x55e4ff9299d0, name="HDMI-1", > geometry=1080x2160+3840+0, availableGeometry=1080x2160+3840+0, > devicePixelRatio=1.0, logicalDpi=QPair(192.0,192.0), > physicalSize=66.0x134.0mm, screenNumber=0, virtualSize=4920x2160 > (4920.0x2160.0mm), orientation=Qt::LandscapeOrientation, depth=24, > refreshRate=50.0, root=376, windowManagerName="KWin") (Primary: false ) > qt.qpa.screen: primary output is "eDP-1" eDP-1: geometry=3840x2160+0+0 + physicalSize=344.0x194.0mm -> 283x282 dpi -> ~2.9*96dpi HDMI-1: geometry=1080x2160+3840+0 + physicalSize=66.0x134.0mm -> 415x409 dpi -> ~4.3*96dpi So eDP-1 has almost 3 times the "regular" DPI, which Qt rounds down to a 2x scale (192dpi). That's almost your preferred scaling of 2.25x though, so the installer should look alright. HDMI-1 looks a bit weird, having a resolution of 1080x2160 on a 6.0x13.4cm display is unusual. Let's focus on the installer. If you login to icewm, the panel should be pretty tiny (a ~third of its normal size). Then run the following: /usr/lib/YaST2/bin/y2controlcenter QT_AUTO_SCREEN_SCALE_FACTOR=1 /usr/lib/YaST2/bin/y2controlcenter QT_SCREEN_SCALE_FACTORS=eDP-1=2 /usr/lib/YaST2/bin/y2controlcenter Which one of those is scaled and by how much? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185561] Ruby error in installation after partitioning
by bugzilla_noreply＠suse.com 03 May '21

03 May '21

https://bugzilla.suse.com/show_bug.cgi?id=1185561 https://bugzilla.suse.com/show_bug.cgi?id=1185561#c3 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |comrad(a)posteo.de Flags| |needinfo?(comrad(a)posteo.de) --- Comment #3 from Steffen Winterfeldt <snwint(a)suse.com> --- Thanks! But we will need yast logs to debug this further. To collect log files run 'save_y2logs' and attach the log file archive this command creates (usually named /tmp/y2log-SOMETHING.tar.xz). You can collect the logs from the installation environment: there's a shell running on consoles 5 and 6 during installation. Switch there with Ctrl-Alt-F5 (or -F6). If you're unsure what to do, please have a look at https://en.opensuse.org/openSUSE:Report_a_YaST_bug#logfiles *** Important *** When done, please remove the 'needinfo' flag. Otherwise the attachment might not be noticed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0