Bug 518777
Summary: | Network in menu is to Network Configuration dialog (related to another mismenuing) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nick Levinson <Nick_Levinson> |
Component: | system-config-network | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 10 | CC: | christoph.wickert, fedora, harald, jmoskovc, jpopelka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-08-25 16:04:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nick Levinson
2009-08-22 18:17:13 UTC
(In reply to comment #0) > Description of problem: > A dialog appears to be at the wrong menu command. > > Version-Release number of selected component (if applicable): > Component and component version are unknown. One hypothesis (not mine) is that > the problem is with an ambiguous .desktop file in Fedora. Correct component is system-config-network, explained in bug 518780 comment 1. > Actual results: > The Network Configuration dialog appears. > > Expected results: > I guess the Network Connections dialog should appear, because another Main Menu > command offers the Network Configuration dialog. Your guess is wrong, explained in bug 518775 comment 1. > See Bug 518775, that Network > Configuration in Main Menu > System menu > Preferences > Network Configuration > menu is to the Network Connections dialog. This is on purpose because it's a different network stack. Also explained in bug 518775 comment 1. > Additional info: > --- I've enabled GUI root access. Please don't, see bug 518780 comment 1. > --- Three other network-related commands appear to operate as they should, but > are cited here because of their topical relationship: > --- --- Main Menu > Places > Network is to a Network folder, which lists > Windows Network. > --- --- Main Menu > System > Preferences > Internet and Network > Network Proxy > is to the Network Proxy Preferences dialog. Sorry, but what does this have to do with this 'bug'? > --- --- In the root account, Main Menu > System > Administration > Network > Device Control operates correctly. (In a nonroot account, nothing responds to > the menu command; I don't know why it doesn't request root authorization, but I > plan to file a separate bug report on that momentarily.) Not a bug, explained in bug 518780 comment 1. The only thing that really could be a bug would be here is if system-config-network (not system-control-network) wouldn't show a authentication dialog for non-root users. If so, this should be tracked in bug 518780. There is nothing left to track here, so I'm closing this one, too. Sorry to close 2 of your 3 bug reports, but everything is working as it should. If not, feel free to reopen. *** This bug has been marked as a duplicate of bug 518780 *** I'm effectively folding this bug report into 518775 (reopened) instead of 518780 and leaving this one closed. On enabling GUI root access, besides what I wrote at Bug 518780: Because RHEL and Fedora are increasingly geared to large and medium-size organizations, where technical amateurs ruin the innards and then blame someone else and make RHEL look bad, RH is separating sysadmin and user functions and doing more to discourage even users with root passwords from tackling root problems without asking the sysadmin. I, however, perform both functions for myself. A full-time sysadmin with specialized tools, like a list of command equivalents, would be nice. That's not available, so I need GUI root. For safety, I have three accounts on my Fedora laptop: root, my usual user account, and a guest account in case I let someone else use my machine, and I do almost everything in my usual nonroot account. The first time I upgraded from FC4 to F10 and discovered I couldn't get into root GUI, I promptly did a clean reinstall of FC4 and researched what I'd have to do to get GUI root access when I'd need it, because I wasn't reinstalling F10 until I had fixed that, notwithstanding that I had paid something like $50 for F10 and the accompanying book, which in 1000-plus pages didn't mention that problem (I emailed the author). I found the hack and reinstalled F10 when FC4 crashed irretrievably again. I understand RH's problem but I also understand mine. I assume anything that should be run only by root but that is being accessed via a nonroot account should request root authorization rather than simply not respond to a menu. That's usability. Thanks. -- Nick *** This bug has been marked as a duplicate of bug 518775 *** |