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.
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.
https://bugzilla.suse.com/show_bug.cgi?id=1200441
Bug ID: 1200441
Summary: go1.19 release tracking
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: screening-team-bugs(a)suse.de
Reporter: jkowalczyk(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
go1.19 (expected August 2022) is a major release of Go.
Minor releases of go1.19.x will be provided through August 2023.
This issue tracks go1.19.x releases packaged and submitted initially
to openSUSE:Factory and can be referenced in submissions to
additional repositories.
Go Release Cycle
https://github.com/golang/go/wiki/Go-Release-Cycle
Go Release history
https://golang.org/doc/devel/release.html
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
https://bugzilla.suse.com/show_bug.cgi?id=1202351
Bug ID: 1202351
Summary: dracut: remove mkinitrd wrapper
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: dracut-maintainers(a)suse.de
Reporter: antonio.feijoo(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Upstream support removed in March 2021
(https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation
announcement on factory mailing list in May 2021
(https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…).
ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in
Tumbleweed first.
Affected packages that need to be updated before (at least):
# zypper se --requires mkinitrd
Loading repository data...
Reading installed packages...
S | Name | Summary |
Type
---+---------------------+----------------------------------------------------+--------
| kernel-debug | A Debug Version of the Kernel |
package
i+ | kernel-default | The Standard Kernel |
package
| kernel-default-base | The Standard Kernel - base modules |
package
| kernel-kvmsmall | The Small Developer Kernel for KVM |
package
| kernel-pae | Kernel with PAE Support |
package
| kernel-vanilla | The Standard Kernel - without any SUSE patches |
package
i | mdadm | Utility for configuring "MD" software RAID devices |
package
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1202353
Bug ID: 1202353
Summary: kernel: replace mkinitrd wrapper with native dracut
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: antonio.feijoo(a)suse.com
QA Contact: qa-bugs(a)suse.de
Blocks: 1202351
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1202351 +++
Upstream support removed in March 2021
(https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation
announcement on factory mailing list in May 2021
(https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…).
ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in
Tumbleweed first.
Affected packages that need to be updated before (at least):
# zypper se --requires mkinitrd
Loading repository data...
Reading installed packages...
S | Name | Summary |
Type
---+---------------------+----------------------------------------------------+--------
| kernel-debug | A Debug Version of the Kernel |
package
i+ | kernel-default | The Standard Kernel |
package
| kernel-default-base | The Standard Kernel - base modules |
package
| kernel-kvmsmall | The Small Developer Kernel for KVM |
package
| kernel-pae | Kernel with PAE Support |
package
| kernel-vanilla | The Standard Kernel - without any SUSE patches |
package
i | mdadm | Utility for configuring "MD" software RAID devices |
package
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1193579
Bug ID: 1193579
Summary: Lifearea misses python3-cairo dependency
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 Applications
Assignee: screening-team-bugs(a)suse.de
Reporter: bluedzins(a)wp.pl
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Lifearea misses python3-cairo dependency, without using TrayIcon plugin is
impossible, and in turn it is not possible to close&stay Lifera window, which
for such type of the program is basically a must.
For the record -- my report in Lifearea github:
https://github.com/lwindolf/liferea/issues/1025
--
You are receiving this mail because:
You are on the CC list for the bug.
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.
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.
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.