October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191381] New: gnu-compilers-hpc: Move rpm macros to %_rpmmacrodir
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1191381 Bug ID: 1191381 Summary: gnu-compilers-hpc: Move rpm macros to %_rpmmacrodir Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: eich(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1191379 Found By: --- Blocker: --- rpm macros aren't config files for the administrator, as such they should be installed into %_rpmmacrodir (ie /usr/lib/rpm/macros.d) instead of /etc/rpm. Please consider adjusting gnu-compilers-hpc -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1203594] New: xscreensaver v 6.03 GL Slideshow fails
by bugzilla_noreply＠suse.com 16 Mar '23

16 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203594 Bug ID: 1203594 Summary: xscreensaver v 6.03 GL Slideshow fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: suse(a)stanmiller.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to run the GL Slideshow screensaver v 6.03 fails with this message. X error in glslideshow: glslideshow: Failed request: 158 glslideshow: Major opcode: 151 () glslideshow: Resource id: 0x0 glslideshow: Serial number: 117 / 117 It appears (quick test) that all other savers work. Manually installing xscreensaver v 5.44, from Open Suse 15.3 on 15.4 works with no problems. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1175587] New: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Deprecated external dependency generator is used
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1175587 Bug ID: 1175587 Summary: windows:mingw:win{32|64}/mingw{32|64}-filesystem: Deprecated external dependency generator is used Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, idonmez(a)suse.com, mkbosmans(a)gmail.com Found By: --- Blocker: --- On building packages there is always a message printed that a 'Deprecated external dependency generator is used'. The reason for this message is located in macros.mingw32 (https://build.opensuse.org/package/view_file/windows:mingw:win32/mingw32-fi…) %_mingw32_package_header \ %global __strip %{_mingw32_strip} \ %global __objdump %{_mingw32_objdump} \ %global _use_internal_dependency_generator 0 \ %global __find_requires %{_mingw32_findrequires} \ %global __find_provides %{_mingw32_findprovides} \ %global __os_install_post %{_mingw32_install_post} by specifing '_use_internal_dependency_generator 0' and overriding the __find_requires and __find_provides. Recent obs dependency support uses *.attr file as shown below: cat /usr/lib/rpm/fileattrs/cmake.attr %__cmake_provides %{_rpmconfigdir}/cmake.prov %__cmake_path ^/usr/lib(64)?/cmake/.*/.*(Config\.cmake|-config\.cmake) where the mentioned file cmake.prov does the work of generating a list of packages that are provided by cmake configuration files. Similar files exists for debuginfo cat /usr/lib/rpm/fileattrs/debuginfo.attr %__debuginfo_provides %{_rpmconfigdir}/debuginfo.prov %__debuginfo_path ^/usr/lib/debug/ for pkgconfig files cat /usr/lib/rpm/fileattrs/pkgconfig.attr %__pkgconfig_provides %{_rpmconfigdir}/pkgconfigdeps.sh --provides %__pkgconfig_requires %{_rpmconfigdir}/pkgconfigdeps.sh --requires %__pkgconfig_path ^((%{_libdir}|%{_datadir})/pkgconfig/.*\.pc|%{_bindir}/pkg-config)$ for executables cat /usr/lib/rpm/fileattrs/elf.attr %__elf_provides %{_rpmconfigdir}/elfdeps --provides %{?__filter_GLIBC_PRIVATE:--filter-private} %__elf_requires %{_rpmconfigdir}/elfdeps --requires %{?__filter_GLIBC_PRIVATE:--filter-private} %__elf_magic ^(setuid,? )?(setgid,? )?(sticky )?ELF (32|64)-bit.*executable %__elf_flags exeonly %__elf_exclude_path ^/usr/lib/debug/ for shared libraries cat /usr/lib/rpm/fileattrs/elflib.attr %__elflib_provides %{_rpmconfigdir}/elfdeps --assume-exec --provides %{?__filter_GLIBC_PRIVATE:--filter-private} %__elflib_requires %{_rpmconfigdir}/elfdeps --assume-exec --requires %{?__filter_GLIBC_PRIVATE:--filter-private} %__elflib_magic ^(setuid )?(setgid )?(sticky )?ELF (32|64)-bit.*shared object %__elflib_exclude_path ^/usr/lib/debug/ and others. To take advantage of this type of support, the currently used files mingw32-find-provides.sh and mingw32-find-requres.sh must be split into implementations that handle a single category of corresponding files. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1166537] New: osc rq accept - forwarding request causes backtrace
by bugzilla_noreply＠novell.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1166537 Bug ID: 1166537 Summary: osc rq accept - forwarding request causes backtrace Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: marco.strigl(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de CC: suse-tux(a)gmx.de Found By: --- Blocker: --- When accepting a SR to a devel project, osc asks if I want to forward the SR to Factory. I answered "y", but got this nice backtrace instead of a SR to Factory: # osc rq accept 784420 Result of change request state: ok openSUSE:Factory Forward this submit to it? ([y]/n)y Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python3.8/site-packages/osc/babysitter.py", line 64, in run return prg.main(argv) File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python3.8/site-packages/osc/commandline.py", line 2652, in do_request project, package, html.escape(msg, quote=False)) NameError: name 'html' is not defined Wild guess: missing "import html"? Note: commandline.py has an "import html" in do_submitrequest(), but this import isn't visible to do_request(). Also note that there are more functions in this file that call html.escape() without importing html before and will probably break in a similar way. Doing the "import html" in the file header instead of inside the functions might be a good idea. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1195395] New: hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195395 Bug ID: 1195395 Summary: hardware/wpa_supplicant: Not able to connect to WLAN after wpa_supplicant update to version 2.10 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: karol(a)babioch.de Reporter: reiokorn(a)tutanota.com QA Contact: screening-team-bugs(a)suse.de CC: cfamullaconrad(a)suse.com Found By: --- Blocker: --- Created attachment 855766 --> http://bugzilla.opensuse.org/attachment.cgi?id=855766&action=edit log file of wpa_supplicant Hello, after the recent update to Tumbleweed, and the wpa_supplicant to version 2.10, I'm no longer able to connect to my home WLAN with my laptop. I've included the wpa_supplicant.log file for diagnosis. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1195634] New: Base Report does not work
by bugzilla_noreply＠suse.com 15 Mar '23

15 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1195634 Bug ID: 1195634 Summary: Base Report does not work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: hd(a)swiateck.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 855943 --> http://bugzilla.opensuse.org/attachment.cgi?id=855943&action=edit Error after open to start a report the error message appears See attachment -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1199618] New: [Build 20220516] openQA test fails in fanotify16 (LTP)
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199618 Bug ID: 1199618 Summary: [Build 20220516] openQA test fails in fanotify16 (LTP) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2353240/modules/fano tify16/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-ltp-syscalls@aarch64-HD24G fails in [fanotify16](https://openqa.opensuse.org/tests/2353240/modules/fanotify16/st… Error log: fanotify.h:336: TBROK: fanotify_mark (3, FAN_MARK_ADD, ..., AT_FDCWD, ".") failed: EXDEV (18) Test process returned unkown none zero value (2). Test took approximately 0.581575272008195 seconds Some test output could not be parsed: 9 lines were ignored. ## Test suite description ## Reproducible Fails since (at least) Build [20220302](https://openqa.opensuse.org/tests/2224057) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1203100] New: Disable fingerprint login doesn't work.
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203100 Bug ID: 1203100 Summary: Disable fingerprint login doesn't work. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: alynx.zhou(a)suse.com, yfjiang(a)suse.com, zcjia(a)suse.com Found By: --- Blocker: --- Env: openSUSE Leap 15.4 GNOME 41.2 gdm 41.3 fprintd 1.94.1 hardware: Thinkpad P15 Gen1 Steps: 1. Boot to desktop and login 2. Disable the fingerprint login in gnome-control-center -> Users 3. Logout or even restart 4. Try to login, stay on the input password screen and observe the warning message below the input field. Actual Result: The "Sorry, fingerprint authentication didn't work. Please try again." message keeps appearing every ~2 sec no matter whether I use the fingerprint scanner or not. From the journal log we can see the Fingerprint Authentication Daemon is started even we already disable it in gnome-control-center. ============================================================================== Sep 05 11:12:25 MiWiFi-R3600-srv dbus-daemon[1022]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested b> Sep 05 11:12:25 MiWiFi-R3600-srv systemd[1]: Starting Fingerprint Authentication Daemon... Sep 05 11:12:26 MiWiFi-R3600-srv dbus-daemon[1022]: [system] Successfully activated service 'net.reactivated.Fprint' Sep 05 11:12:26 MiWiFi-R3600-srv systemd[1]: Started Fingerprint Authentication Daemon. Sep 05 11:12:26 MiWiFi-R3600-srv gdm-fingerprint][828]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] term> Sep 05 11:12:29 MiWiFi-R3600-srv gdm-fingerprint][837]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] term> ============================================================================= Related issue: https://bugzilla.suse.com/show_bug.cgi?id=1203099 -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1203099] New: Cannot unblock GNOME desktop using the fingerprint scanner
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203099 Bug ID: 1203099 Summary: Cannot unblock GNOME desktop using the fingerprint scanner Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: grace.wang(a)suse.com QA Contact: qa-bugs(a)suse.de CC: alynx.zhou(a)suse.com, mail(a)vsv.dev, yfjiang(a)suse.com, zcjia(a)suse.com Depends on: 1189621 Found By: Community User Blocker: --- Env: openSUSE Leap 15.4 GNOME 41.2 gdm 41.3 fprintd 1.94.1 hardware: Thinkpad P15 Gen1 +++ This bug was initially created as a clone of Bug #1189621 +++ Despite the fact that `fprintd` is installed, the fingerprints are configured and `fprintd-verify` recognizes them, I still cannot use the fingerprint scanner in order to unlock my GNOME session. Reproducible: Always Steps to Reproduce: 1. Install fprintd via `sudo zypper in fprintd` 2. Enable 'Fingerprint Login' in 'Gnome Settings > Users' GUI application and add a fingerprint 3. Verify that it works when invoking `fprintd-verify` from the command line: fprintd-verify Using device /net/reactivated/Fprint/Device/0 Listing enrolled fingers: - #0: right-index-finger Verify started! Verifying: right-index-finger Verify result: verify-match (done) 3. Lock the screen in GNOME 4. Try to unlock the screen Actual Results: Unlocking via the fingerprint scanner doesn't work. "Sorry, that didn't work. Please try again." message keeps appearing every ~2 sec no matter whether I use the fingerprint scanner or not. The session can be unlocked only by entering the password. Expected Results: Both password and fingerprint scan should unlock the GNOME session. ~> zypper info gnome-shell | grep Version Version : 40.3-4.1 ~> zypper info gdm | grep Version Version : 3.38.2-2.6 ~> zypper info fprintd | grep Version Version : 1.90.9-2.3 ~> cat /etc/os-release | grep VERSION_ID VERSION_ID="20210817" ~> sudo journalctl --since "10 min ago" | grep fingerprint Aug 19 19:58:55 vsv-thinkpad gdm-fingerprint][5155]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:58:58 vsv-thinkpad gdm-fingerprint][5162]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:59:00 vsv-thinkpad gdm-fingerprint][5168]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] Aug 19 19:59:03 vsv-thinkpad gdm-fingerprint][5171]: pam_warn(gdm-fingerprint:auth): function=[pam_sm_authenticate] flags=0 service=[gdm-fingerprint] terminal=[/dev/tty7] user=[vsv] ruser=[<unknown>] rhost=[<unknown>] ~> sudo fwupdmgr get-devices ... ��Prometheus: �� Device ID: 50efef912094e784a03628350441f6927c4920b0 �� Summary: Fingerprint reader �� Current version: 10.01.3273255 �� Vendor: Synaptics (USB:0x06CB) �� Install Duration: 2 seconds �� Serial Number: 60900456185485 �� GUIDs: 09e8bf16-3e69-50f5-bb66-c7a040248352 �� USB\VID_06CB&PID_00BD&REV_0000 �� 8088f861-6318-5b1e-9ce4-fbddbedb09ac �� USB\VID_06CB&PID_00BD �� Device Flags: �� Updatable �� Supported on remote server �� Cryptographic hash verification is available ~> uname -a Linux vsv-thinkpad 5.13.8-1-default #1 SMP Thu Aug 5 08:56:22 UTC 2021 (967c6a8) x86_64 x86_64 x86_64 GNU/Linux Hardware Model: Lenovo ThinkPad T14 Gen 1 (AMD) Windowing System: Wayland -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1197556] New: gnome42 completely unusable on Lenovo P15
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1197556 Bug ID: 1197556 Summary: gnome42 completely unusable on Lenovo P15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: donald.vosburg(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Logging into GNOME on Lenovo P15 with DockStation results in hung system unable to launch applications. Keyboard and mouse become unresponsive, networking on dock gets disabled, and the only alternative is hard power-off. Using plasma on the same OS on the same hardware works perfectly. -- You are receiving this mail because: You are on the CC list for the bug.

1 20