October 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1177133] No microphone support on HP ZBook laptop
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177133 https://bugzilla.suse.com/show_bug.cgi?id=1177133#c15 --- Comment #15 from Takashi Iwai <tiwai(a)suse.com> --- Then check the capture tab (Eingabegeraete). There should be multiple items including the microphone. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176474] AUDIT-0: powerdevil5 (suse-dbus-unauthorized-service, polkit-untracked-privilege)
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1176474 https://bugzilla.suse.com/show_bug.cgi?id=1176474#c4 --- Comment #4 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- The new helper is okay. It only accepts integer parameters in D-Bus methods and they control the battery charging threshold. Only getting is allowed for locally logged in users, setting requires admin privileges. That's okay. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177177] Resuming from suspend locks up Plasma, requiring a reboot
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177177 https://bugzilla.suse.com/show_bug.cgi?id=1177177#c6 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |IN_PROGRESS Flags| |needinfo?(psychonaut@nothin | |gisreal.com) --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- This driver is only meant for older Intel GPUs. Could you please add the output when runnning hwinfo --gfxcard as root? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177177] Resuming from suspend locks up Plasma, requiring a reboot
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1177177 https://bugzilla.suse.com/show_bug.cgi?id=1177177#c5 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Workspace (Plasma) |X.Org Assignee|opensuse-kde-bugs@opensuse. |gfx-bugs(a)suse.de |org | QA Contact|qa-bugs(a)suse.de |gfx-bugs(a)suse.de --- Comment #5 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Tristan Miller from comment #4) > Yes, I had xf86-video-intel-2.99.917+git8674.25c9a2fcc-lp152.3.7 installed. > I removed it and rebooted, and then suspended and resumed by computer 30 > times without encountering the bug. So you are probably right about the > problem being linked to the video driver. The xf86-video-intel driver is deprecated and won't work with newer hardware, so that's probably just a symptom of that. Reassigning. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175119] while doing the autoyast an internal error occurs it says: undefined method `product_package'
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1175119 https://bugzilla.suse.com/show_bug.cgi?id=1175119#c15 --- Comment #15 from Nicolas Nattermann <opensuse-bugs(a)yalwa.com> --- sorry that was imprecise. I don't have anything of our own / related to our yalwa-client repository there. we do have, from the openSUSE install itself patrick@desk45:~> ls -l /etc/products.d/ total 4 lrwxrwxrwx 1 root root 13 Jun 26 2019 baseproduct -> openSUSE.prod -rw-r--r-- 1 root root 3491 Jun 24 17:27 openSUSE.prod patrick@desk45:~> rpm -qa|fgrep -- -release openSUSE-release-15.2-lp152.575.1.x86_64 openSUSE-release-ftp-15.2-lp152.575.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1175119] while doing the autoyast an internal error occurs it says: undefined method `product_package'
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1175119 https://bugzilla.suse.com/show_bug.cgi?id=1175119#c14 Nicolas Nattermann <opensuse-bugs(a)yalwa.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(opensuse-bugs@yal | |wa.com) | --- Comment #14 from Nicolas Nattermann <opensuse-bugs(a)yalwa.com> --- Looks like we are going to learn something new... I don't have anything in /etc/products.d, and no *-release page. Would you have some link where I can get a quick readup on what they are supposed to look like? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176793] New: [Build 20200921] openQA test fails in system_role y2start core dumped ppc64 (BE)
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176793 Bug ID: 1176793 Summary: [Build 20200921] openQA test fails in system_role y2start core dumped ppc64 (BE) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC URL: https://openqa.opensuse.org/tests/1400814/modules/syst em_role/steps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: jsrain(a)suse.com Found By: openQA Blocker: --- Created attachment 841821 --> http://bugzilla.opensuse.org/attachment.cgi?id=841821&action=edit yast_core_dump_ppc64_tw_20200921_console.log ## Observation [Build 20200921] openQA test fails in system_role y2start core dumped ppc64 (BE) in "Installation Settings" menu when depressing the "Software" headline. in attachment the console log with bunch of backstraces. openQA test in scenario opensuse-Tumbleweed-DVD-ppc64-RAID0@ppc64 fails in [system_role](https://openqa.opensuse.org/tests/1400814/modules/system_role/… ## Test suite description ## Reproducible Fails since (at least) Build [20200921](https://openqa.opensuse.org/tests/1400814) (current job) ## Expected result Last good: [20200918](https://openqa.opensuse.org/tests/1398622) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1174593] pam_xauth(.so) module is extremly slow on Leap 15.2
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1174593 https://bugzilla.suse.com/show_bug.cgi?id=1174593#c17 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndirsch(a)suse.com |needinfo?(josef.moellers@su |) |se.com) --- Comment #17 from Stefan Dirsch <sndirsch(a)suse.com> --- (In reply to Dr. Werner Fink from comment #15) > This is what I see as root even with option `-i` > > boole:~ # XAUTHORITY=/suse/werner/.Xauthority xauth -vi nlist > xauth: /suse/werner/.Xauthority not writable, changes will be ignored > > that means that even for read action (and `nlist` seems to be a read action) > xauth tries to lock. Nevertheless as root even can not read the Xauthority > file > > ll /suse/werner/.Xauthority > -rw------- 1 werner suse 363 Oct 1 08:12 /suse/werner/.Xauthority > > the correct solution is to do the xauth call as user and not as root hence > this bug belongs IMHO to the maintainer of pam(_xauth) I fully agree with Werner. (In reply to Josef Möllers from comment #16) > (In reply to Dr. Werner Fink from comment #15) > > This is what I see as root even with option `-i` > > > > boole:~ # XAUTHORITY=/suse/werner/.Xauthority xauth -vi nlist > > xauth: /suse/werner/.Xauthority not writable, changes will be ignored > > > > that means that even for read action (and `nlist` seems to be a read action) > > xauth tries to lock. Nevertheless as root even can not read the Xauthority > > file > > I straced the xauth invocation and found that it tries to create a file in > ~user: > openat(AT_FDCWD, "/suse/jmoellers/.Xauthority-c", O_WRONLY|O_CREAT|O_EXCL, > 0600) > but as it does not have permission, this fails (EACCES (Permission denied)). > Xauth (or XauLockAuth()) then hopes that this will go away by itself, so it > sleeps for 2s: > nanosleep({tv_sec=2, tv_nsec=0}, 0x7ffe5d5194f0) > and tries again. After 10 tries it gives up. So what would help it to create this somewhere else, where root has access to, if root cannot read the /suse/jmoellers/.Xauthority file anyway to get the information it needs? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1174593] pam_xauth(.so) module is extremly slow on Leap 15.2
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

https://bugzilla.suse.com/show_bug.cgi?id=1174593 https://bugzilla.suse.com/show_bug.cgi?id=1174593#c16 --- Comment #16 from Josef Möllers <josef.moellers(a)suse.com> --- (In reply to Dr. Werner Fink from comment #15) > This is what I see as root even with option `-i` > > boole:~ # XAUTHORITY=/suse/werner/.Xauthority xauth -vi nlist > xauth: /suse/werner/.Xauthority not writable, changes will be ignored > > that means that even for read action (and `nlist` seems to be a read action) > xauth tries to lock. Nevertheless as root even can not read the Xauthority > file I straced the xauth invocation and found that it tries to create a file in ~user: openat(AT_FDCWD, "/suse/jmoellers/.Xauthority-c", O_WRONLY|O_CREAT|O_EXCL, 0600) but as it does not have permission, this fails (EACCES (Permission denied)). Xauth (or XauLockAuth()) then hopes that this will go away by itself, so it sleeps for 2s: nanosleep({tv_sec=2, tv_nsec=0}, 0x7ffe5d5194f0) and tries again. After 10 tries it gives up. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1176626] New: problem with flatpak and QT_QPA_PLATFORM on Wayland
by bugzilla_noreply＠suse.com 01 Oct '20

01 Oct '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1176626 Bug ID: 1176626 Summary: problem with flatpak and QT_QPA_PLATFORM on Wayland Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the Telegram flatpak does not start, if within a GNOME Wayland session. Trying to start it manually, this is the output: flatpak run org.telegram.desktop (process:2): Telegram-WARNING **: 16:39:07.608: Unfortunately, GTK integration conflicts with qgtk2 platformtheme and style. Therefore, QT_QPA_PLATFORMTHEME and QT_STYLE_OVERRIDE will be unset. Telegram-Message: 16:39:07.609: This can be ignored by setting TDESKTOP_I_KNOW_ABOUT_GTK_INCOMPATIBILITY environment variable to any value, however, if qgtk2 theme or style is used, this will lead to a crash. Telegram-Message: 16:39:07.609: GTK integration can be disabled by setting TDESKTOP_DISABLE_GTK_INTEGRATION to any value. Keep in mind that this will lead to clipboard issues and tdesktop will be unable to get settings from GTK (such as decoration layout, dark mode & more). qt.qpa.xcb: could not connect to display qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Trying to run it like this: QT_QPA_PLATFORM=wayland-egl flatpak run org.telegram.desktop it does start. On an Xorg session, it starts without issues. I'm reporting this here instead than to Telegram or flathub directly, is that installing exactly the same flatpak on, e.g., Fedora or Ubuntu works flawlessly while inside a Wayland session. So it feels like it's something specific to openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

1 4