Bug 1998484
| Summary: | control-center is not updated when modem connected via gnome-shell | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Vladimir Benes <vbenes> |
| Component: | gnome-control-center | Assignee: | Felipe Borges <feborges> |
| gnome-control-center sub component: | Network and Wi-Fi panels | QA Contact: | Filip Pokryvka <fpokryvk> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | cgarnach, fpokryvk, jadahl, jkoten, nm-team, tpelka, tpopela |
| Version: | 9.0 | Keywords: | MigratedToJIRA, Triaged |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-15 19:14:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vladimir Benes
2021-08-27 10:56:22 UTC
(In reply to Vladimir Benes from comment #0) > Steps to Reproduce: > 1. open gcc > 2. open GS menu and connect a modem Does the modem actually connect? If yes, then that's between ModemManager and control center. yes, I clicked GS menu and connected the modem, but control-center stayed the same, connected, should cc reads dbus about state change? If yes, could you switch the component to gcc? Yes, the only way gnome-shell interacts directly with gnome-control-center is when handling the various "... Settings" menu items. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |