This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1998490 - first connection of modem is somehow unintuitive
Summary: first connection of modem is somehow unintuitive
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-control-center
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Felipe Borges
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-27 11:25 UTC by Vladimir Benes
Modified: 2023-09-15 19:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-15 19:14:33 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4183 0 None Migrated None 2023-09-15 19:14:29 UTC
Red Hat Issue Tracker RHELPLAN-95422 0 None None None 2021-08-27 11:26:55 UTC

Description Vladimir Benes 2021-08-27 11:25:28 UTC 
Description of problem:
I'll describe my workflow. 
1. plug in a new modem
2. when we see it in GS menu, click connect
3. what should I do now in the control center? ah ok, click Mobile Data
4. now I see empty Access Points page, what does this mean? Should I click +?
5. after clicking + I see Name, APN, User, and Password, I do miss hints on what that means. 

Profile name really does mean nothing and it's just a connection for NM, ok, but one should now. In wired networks there is prefilled Profile 1, let's do this too. So let's add GSM Profile 1. APN what does that mean? Let's prefill it too with the widely used internet. If you don't have it from your operator you just have no idea what to fill in.


Version-Release number of selected component (if applicable):
ModemManager-1.14.10-6.el9.x86_64
gnome-shell-40.4-2.el9.x86_64
gnome-control-center-40.0-14.el9.x86_64

How reproducible:


Actual results:


Expected results:
I think after clicking connect in GS, you should be directly to AP even maybe after + is clicked. You obviously want to connect so why clicking Mobile Data first?

Additional info:
Comment 2 Allan Day 2023-03-28 12:26:30 UTC 
I'm finding it hard to understand this issue report and, without having a 3G dongle, I'm unable to see what's being described. Could you provide screenshots?

It would also help if you could describe what you are attempting to achieve. Why do you need to use the settings? Why would expect them to be shown when you click connect?
Comment 3 RHEL Program Management 2023-09-15 19:13:11 UTC 
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.
Comment 4 RHEL Program Management 2023-09-15 19:14:33 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.