Bug 26063 - Since a recent update, Ethernet won't run on startup. The "Create new interface" is corrupted as well.
Summary: Since a recent update, Ethernet won't run on startup. The "Create new interf...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-13 08:44 CET by Doug Laidlaw
Modified: 2020-01-16 14:28 CET (History)
2 users (show)

See Also:
Source RPM: drakx-net-2.42-2
CVE:
Status comment:


Attachments

Description Doug Laidlaw 2020-01-13 08:44:25 CET
Description of problem:
On booting into Cauldron, the normal Ethernet channel (enp0s31f6) shows that it is present but not connected.  It can be brought up by "sudo ifup enp0s31f6,"
then runs without any problem

For a while, I was deleting and reinstating the connection.  During that operation, the Configuration screen would go to "Accept" before any detail could be entered.

Version-Release number of selected component (if applicable):

drakx-net 2.42-2


How reproducible:

On every bootup.


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2020-01-13 20:25:32 CET
> Since a recent update
This is something we see often. It would help if you could identify the updates which preceded the problem.
 $ rpm -qa --last | less
shows them in date order. Clearly if you can recall the date when the problem appeared - or note it at once - it would help to identify likely suspect updates.

You have the right SRPM, which provides 'drakx-net-text' which includes:
drakconnect: LAN/Internet connection configuration. It handles ethernet, ISDN, DSL, cable, modem.

Assigning globally as this SRPM has variable maintainers.

Source RPM: Mga Networking applet: not sure of exact RPM. => drakx-net-2.42-2
Assignee: bugsquad => pkg-bugs

Comment 2 Frank Griffin 2020-01-13 20:31:35 CET
Try the procedure in comment#3 of bug#26035.

CC: (none) => ftg

Comment 3 Doug Laidlaw 2020-01-13 21:18:17 CET
Frank, do you mean replacing drakx-net with NM?  I am used to seeing icons for both in the system tray, but this time, there is only drakx-net.

Lewis, thanks for the search command. The only likely RPMs are a group of 4 for glib-networking-2.62.3-1. They came down on Jan 4 last. It would be no later, and I can't see anything earlier.
Comment 4 Frank Griffin 2020-01-13 22:21:32 CET
@Doug Yep, bug#26035 involved some sort of conflict between drakx-net and NM, but cutting out drakx-net and letting NM take over seemed to fix it.

You need to be sure that NM is installed as well as plasma-applet-nm if you're using plasma.  The stuff in the comment I referenced makes sure that (a) NM isn't trying to use any of the drakx-net (ifcfg-rh) stuff, and (b) all of the drakx-net stuff is deleted (via MCC/drakconnect) just to make sure.

Note that this solution doesn't address what's wrong with drakx-net or whether there is a problem with glib-networking, but it may get you working.
Comment 5 Doug Laidlaw 2020-01-14 00:04:04 CET
The NM packages for Cauldron are in the repos, but not in rpmdrake.  Apparently networkmanager depends on networkmanager-wifi, which in turn depends on a library that is missing from the repos.
Comment 6 Doug Laidlaw 2020-01-14 03:27:24 CET
The Mga8 installation that I have been using as my default system has a few problems.  I am about to go back to 7.1. I still have another "Cauldron" installation that shows this bug as well.
Comment 7 Maurice Batey 2020-01-16 12:36:54 CET
My fully-updated Plasma 64-bit Cauldron install fails to connect to ethernet during booting.

Pro-tem, I then just invoke net_applet and hit Connect.

CC: (none) => maurice

Comment 8 Doug Laidlaw 2020-01-16 14:28:12 CET
So apart from the DE, you have what I had when I mentioned the bug on the ng.  I couldn't switch to NM because a required library was missing.  It doesn't happen under 7.1, but my Cups failure still does.

Note You need to log in before you can comment on or make changes to this bug.