3.19.0-49 updates breaks login screen & network connections

Asked by Galen Thurber

2 major breaks
1st
updates breaks login screen,
login does not come to foreground.
User has to switch to another TTY then back to TTY7 in order to get login screen

2nd
updates breaks ALL network connections,
ALL direct and wifi config are wiped out.
network-connections are no longer editable
can not add connections.

my Ubuntu is dead

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
Last query:
Last reply:
Revision history for this message
Manfred Hampl (m-hampl) said :
#1

The network issue probably is Bug #1511735

Do you have the trusty-proposed repository enabled?

see also https://answers.launchpad.net/ubuntu/+question/284147

Revision history for this message
Galen Thurber (godfree2) said :
#2

expunge those those whom have double sabotaged Linux

Revision history for this message
Galen Thurber (godfree2) said :
#3

Who in the fuck authourized this sabotage of working systems?

Revision history for this message
Galen Thurber (godfree2) said :
#4

who will stand against this sabotage?

Revision history for this message
Manfred Hampl (m-hampl) said :
#5

The software in the -proposed repositories is still in its testing phase.
It is not sabotage if software turns out to be buggy while in testing. Only after a period of successful use in -testing it will be made available for everyone in the -updates repositories.

Yes, this case is a bit more complicated, because it disables networking functionality, and it is tricky to repair a system that is broken with this bug.

In https://answers.launchpad.net/ubuntu/+question/284147 I described a way to re-install the previous version of the packages, and another user has already successful done that.

Revision history for this message
Best Manfred Hampl (m-hampl) said :
#6

Corrected instructions from question 284147

1. Boot your system normally from the hard disk (with broken network) and issue the command
dpkg --print-architecture
What do you get? Is it i386 or is it amd64?

2. Boot your system with a live DVD or an Ubuntu installer on an USB stick in the "Try Ubuntu without installing" mode.
Alternatively you can download the files in the following steps by using any computer and any operating system.

3. Insert an USB stick into the system.

4. If the information in step 1 was amd64, then browse to https://launchpad.net/ubuntu/+source/libnl3/3.2.21-1/+build/5320735 and download the files
libnl-3-200_3.2.21-1_amd64.deb
libnl-genl-3-200_3.2.21-1_amd64.deb
libnl-route-3-200_3.2.21-1_amd64.deb
and save them on the USB stick.
Eject the USB stick (right click on the USB stick icon on the left and select eject)

5. Boot your system normally from the hard disk (with broken network)

6. insert the USB stick

7. open nautilus and identify the name of the USB stick (probably something like /media/1A2B-3C4D)

8. open a terminal window

9. Issue the command
cd /media/xxxx-xxxx
(replace xxxx-xxxx by the name of the USB stick identified in the previous step)

10. Issue the command
dpkg -i --force-downgrade libnl-3-200_3.2.21-1_amd64.deb libnl-genl-3-200_3.2.21-1_amd64.deb libnl-route-3-200_3.2.21-1_amd64.deb

11. reboot

XXXXX

If in step 1 you see i386 then you have to do replace two of the steps above:

4. If the information in step 1 was i386, then browse to https://launchpad.net/ubuntu/+source/libnl3/3.2.21-1/+build/5320738 and download the files
libnl-3-200_3.2.21-1_i386.deb
libnl-genl-3-200_3.2.21-1_i386.deb
libnl-route-3-200_3.2.21-1_i386.deb
and save them on the USB stick.
Eject the USB stick (right click on the USB stick icon on the left and select eject)

and

10. Issue the command
dpkg -i --force-downgrade libnl-3-200_3.2.21-1_i386.deb libnl-genl-3-200_3.2.21-1_i386.deb libnl-route-3-200_3.2.21-1_i386.deb

XXXXX

In case that anything is not yet clear to you, or if you get error messages, please do not hesitate to ask again.

Revision history for this message
Galen Thurber (godfree2) said :
#7

Thanks Manfred Hampl, that solved my question.