September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1198547] New: power-profiles-daemon package is missing in Leap 15.4
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198547 Bug ID: 1198547 Summary: power-profiles-daemon package is missing in Leap 15.4 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: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of the main features of the new LTS Plasma was power profiles, but this package is missing in Leap 15.4. Is it possible to add it? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1176566] New: Installing ignition leads to unbootable system
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 Bug ID: 1176566 Summary: Installing ignition leads to unbootable system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've installed ignition locally on Tumbleweed, to be able to validate ignition files locally. After a reboot I was presented with an emergency shell, leading down a wild goose chase for disabling ignition permanently. It all went away after setting up a chroot and removing all traces of ignition, but it would be much much better if installing it would not lead to a broken system by default. I saw some errors related to the ignition generator, and the systemd unit file was broken, but could not save any logs unfortunately. But it should be easy enough to reproduce if anyone cares: # zypper in ignition # reboot (Might be related to #1172592) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200955] New: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint'
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200955 Bug ID: 1200955 Summary: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint' 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: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The ansible-lint package on Tumbleweed complains about the missing ansiblelint module: > phoenix@racetrack-7290:~/Projects/geekoops> ansible-lint > Traceback (most recent call last): > File "/usr/bin/ansible-lint", line 5, in <module> > from ansiblelint.__main__ import _run_cli_entrypoint > ModuleNotFoundError: No module named 'ansiblelint' -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1200542] New: Regional preferences error with "default" locale
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200542 Bug ID: 1200542 Summary: Regional preferences error with "default" locale 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: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859593 --> http://bugzilla.opensuse.org/attachment.cgi?id=859593&action=edit Screenshot with the solution When I configure in: Preferences > Formats > Region > es_PE (Per�) Result: Many of the details (Numbers, Date, Money) are in "Default" so if I save the config: $ locale locale: Cannot set LC_ALL to default locale: No existe el fichero o el directorio (Don't exist the file or directory) Also, some apps in python show error: locale.Error: unsupported locale setting BUT, if I config each detail with es_PE, all is OK. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200391] New: Add country flag to the calendar in digital clock
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200391 Bug ID: 1200391 Summary: Add country flag to the calendar in digital clock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859507 --> http://bugzilla.opensuse.org/attachment.cgi?id=859507&action=edit screenshot When I configure two or more calendars en the clock, the holidays of different countries are confusing BUT if flags are added it would be solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 1