[Bug 1176553] New: [Build 20200914] NM_wpa2_enterprise: no auth dialog to connect
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 Bug ID: 1176553 Summary: [Build 20200914] NM_wpa2_enterprise: no auth dialog to connect Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1394333/modules/NM_w pa2_enterprise/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: openQA Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_on_gnome@64bit fails in [NM_wpa2_enterprise](https://openqa.opensuse.org/tests/1394333/modules/NM_wpa2_enterprise/steps/7) ## Test suite description Maintainer: asmorodskyi, okurz. Extra tests which were designed to run on gnome ## Reproducible Fails since (at least) Build [20200309](https://openqa.opensuse.org/tests/1199785) ## Expected result Last good: [20200307](https://openqa.opensuse.org/tests/1198559) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=extra_tests_on_gnome&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gnome-bugs@suse.de |songchuan.kang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c1 --- Comment #1 from Jonathan Kang <songchuan.kang@suse.com> ---
gnome-shell[1363]: Device state invalid, is 0 NetworkManager[3528]: <info> [1600161229.2581] NetworkManager (version 1.26.2) is starting... (after a restart)
It seems NetworkManager is still in the state of restarting when GNOME Shell is populating the wifi dialog. When the connect button is clicked, GNOME Shell tries to connect to an invalid connection, logging the following line:
gnome-shell[1363]: error: Execution of “gnome-control-center” failed:: Array element (type filename) may not be null
This might be caused by low performance of the test machine:
gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-19ms), your system is too slow gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-1ms), your system is too slow gnome-shell[1363]: libinput error: event3 - QEMU QEMU USB Tablet: client bug: event processing lagging behind by 38ms, your system is too slow gnome-shell[1363]: libinput error: client bug: timer event3 debounce: scheduled expiry is in the past (-17ms), your system is too slow
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 Guillaume GARDET <guillaume.gardet@arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaume.gardet@arm.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c3 Michel Normand <normand@linux.vnet.ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |normand@linux.vnet.ibm.com --- Comment #3 from Michel Normand <normand@linux.vnet.ibm.com> --- *** Bug 1178504 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c9 Deepthi Yadabettu Venkatachala <deepthi.venkatachala@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |deepthi.venkatachala@suse.c | |om, songchuan.kang@suse.com Flags| |needinfo?(songchuan.kang@su | |se.com) --- Comment #9 from Deepthi Yadabettu Venkatachala <deepthi.venkatachala@suse.com> --- Have tested manually and waited for till the Network Manager to start. then I have opened the wifi dialog to connect and but there were no action when I click the connect button. Below messages are observed in the "journalctl -b", could please let me if this is related to issue or not, Jun 21 05:24:49 susetest gnome-shell[998]: Window manager warning: Failed to create DRM buffer wrapper: drmModeAddFB does not support format 'AR24' (0x34325241) Jun 21 05:24:49 susetest gnome-shell[998]: JS ERROR: Error: Argument string may not be null _packVariant@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:87:29 _init/this.Variant._new_internal@resource:///org/gnome/gjs/modules/core/overrides/GLib.js:281:35 launchSettingsPanel/param<@resource:///org/gnome/shell/ui/status/network.js:89:31 launchSettingsPanel@resource:///org/gnome/shell/ui/status/network.js:89:22 _connect@resource:///org/gnome/shell/ui/status/network.js:966:36 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c11 --- Comment #11 from Dominique Leuenberger <dimstar@opensuse.org> --- Any update here? It's closing in to 1-year-without-fix -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c13 --- Comment #13 from Dominique Leuenberger <dimstar@opensuse.org> --- I dare to challenge the 'timing issue' :) For a test I changed the openQA code to wait 5 minutes before clicking connect in gnome-shell; 5 minutes ought to be enough for really about everything Test scheduled as https://openqa.opensuse.org/tests/1847618 The test failed - as it did before. The 5 minute gap can be observed between https://openqa.opensuse.org/tests/1847618#step/yast2_network_use_nm/7 and https://openqa.opensuse.org/tests/1847618#step/NM_wpa2_enterprise/1 (clock moved by 5 minutes) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 Yifan Jiang <yfjiang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com, | |qkzhu@suse.com, | |yfjiang@suse.com, | |yu.daike@suse.com Assignee|songchuan.kang@suse.com |xiaoguang.wang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c17 --- Comment #17 from xiaoguang wang <xiaoguang.wang@suse.com> --- I think this issue was from upstream commit https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/c9708b140ce046d8df95a069... gnome-shell uses the dbus way to replace the spawn way, when creating dbus message variables, the error happens. Because some argument is optional, so we need to consider the null argument. I create a patch, please try to test it. I can't reproduce this issue on my PC, I can't test. https://build.opensuse.org/packoptiontalage/show/home:xiaoguang_wang:branche... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c19 --- Comment #19 from xiaoguang wang <xiaoguang.wang@suse.com> --- (In reply to Jonathan Kang from comment #18)
gnome-control-center -v wifi connect-8021x-wifi /org/freedesktop/NetworkManager/Devices/5 /org/freedesktop/NetworkManager/AccessPoint/3
How to reproduce this issue on my PC, I need to do more investigation. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c21 --- Comment #21 from xiaoguang wang <xiaoguang.wang@suse.com> --- I update the patch to print more information. https://build.opensuse.org/packoptiontalage/show/home:xiaoguang_wang:branche... Filter the journal log by: grep "NNNN" Please try to get the log. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c23 --- Comment #23 from xiaoguang wang <xiaoguang.wang@suse.com> --- (In reply to Jonathan Kang from comment #22)
localhost:/home/suse # journalctl -f | grep "NNNN" Jul 28 14:45:00 localhost.localdomain gnome-shell[1459]: NNNN wifi connect-8021x-wifi this._device.get_path() accessPoints[0].get_path() Jul 28 14:45:00 localhost.localdomain gnome-shell[1459]: NNNN wifi connect-8021x-wifi null /org/freedesktop/NetworkManager/AccessPoint/1
Yes, here the _device.get_path() is null. I think it should not be null. the _device is NMDevice, _device.get_path() equals C function nm_device_get_path, so we need to know why nm_device_get_path returns null. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c28 --- Comment #28 from xiaoguang wang <xiaoguang.wang@suse.com> --- (In reply to Jonathan Kang from comment #27)
But later on NetworkManager implemented `NMDevice.get_path()` and it's designed to return the actual pci path for that device interface. So gnome-shell should call `nm_object_get_path()` on the NMDevice instead to get the expected value.
For C code we can use this way to get dbus path,
nm_object_get_path(NM_OBJECT(device)) But for JS code it's impossible to do it like that. NMDevice needs to support nm_device_get_parent or nm_device_get_object to get NMObject, then do NMObject.get_path() to get dbus path.
Maybe NMDevice can add a function nm_device_get_dbus_path to get dbus path directly. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c29 --- Comment #29 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to xiaoguang wang from comment #28)
(In reply to Jonathan Kang from comment #27)
But later on NetworkManager implemented `NMDevice.get_path()` and it's designed to return the actual pci path for that device interface. So gnome-shell should call `nm_object_get_path()` on the NMDevice instead to get the expected value.
For C code we can use this way to get dbus path,
nm_object_get_path(NM_OBJECT(device)) But for JS code it's impossible to do it like that. NMDevice needs to support nm_device_get_parent or nm_device_get_object to get NMObject, then do NMObject.get_path() to get dbus path.
Maybe NMDevice can add a function nm_device_get_dbus_path to get dbus path directly.
Personally, I don't think NM upstream will accept this solution. Since this is an issue specific to openSUSE. Maybe we can create an issue at gnome-shell's upstream and see what they suggest. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 http://bugzilla.opensuse.org/show_bug.cgi?id=1176553#c30 --- Comment #30 from xiaoguang wang <xiaoguang.wang@suse.com> --- Open an issue on upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4565 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176553 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com