| Summary: | Ethernet and WiFi connections not visible in GNOME | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Friedel Wolff <friedel> |
| Component: | RPM Packages | Assignee: | GNOME maintainers <gnome> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, nic, olav, thierry.vignaud |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gnome-control-center-3.14.2-1.mga5 | CVE: | |
| Status comment: | |||
|
Description
Friedel Wolff
2016-01-21 07:05:22 CET
There's no maintainer for gnome-control-center, so assigning to all packagers collectively. I'm very much puzzled by this report, though, I think an issue like this one would have affected many of our iso testers and Mga5 wouldn't have been released like that. Can anyone reproduce it? CC:
(none) =>
marja11 Hi Friedel What do you mean by disabled net_applet? What did you actually do. Nic CC:
(none) =>
nic Please ignore the previous comment. I can reproduce this and net_applet appears to have nothing to do with it. I think the reason it hasn't been reported before is that people use mcc instead of the gnome network app. I'll check upstream for a report. I have just checked in Ubuntu 14.04 with Gnome3 DE and it works as expected. Is it possible this is a MCC bug? Network settings changed so Gnome can't read them? (In reply to Nic Baxter from comment #4) > I have just checked in Ubuntu 14.04 with Gnome3 DE and it works as expected. > Is it possible this is a MCC bug? Network settings changed so Gnome can't > read them? s/MCC/drakx-net/ CC'ing tv and ovitters, who might just know :-) CC:
(none) =>
olav, thierry.vignaud Re-assigning to the Gnome maintainers group. Is this bug still valid in a completely updated system? Keywords:
(none) =>
NEEDINFO Hi Marja. Yes, this is still this way today. Hi Friedel, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja @ Friedel: No reply, so closing as OLD since Mageia 5 is no longer maintained. ==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <== Status:
NEW =>
RESOLVED |