No network at all after upgrade/reboot

[Snowhog]

Added 12:26 pm October 26th

The process took a fairly long time. No issues until after I rebooted. NO NETWORK, EITHER WIRED OR WIRELESS!!

That is completely unacceptable under any situation. I believe I know why this happened, but I blame the developers/kernel maintainers for having permitted it to occur at all.

My HP 64-bit laptop has the following:

02:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)

Now, I 'might' have accepted the wireless connection not being there after the upgrade, as Broadcom support is problematic. However, not having the wired network is, as I said, not acceptable at all!

I restored my pre do-release-upgrade backup and I'm here again, running 14.04.1 LTS.

Added 10-30-2014:

Backed up again and the ran sudo do-release-upgrade -d

Once again, after completing and rebooting, NO NETWORK; WIRED OR WIRELESS!!

I made note of what I thought might be relevant as the process proceded, and present that here:

(gtk-update-icon-cache-3.0:25949): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.


Preparing to unpack .../bcmwl-kernel-source_6.30.223.248+bdcom-0ubuntu1_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu1) over (6.30.223.141+bdcom-0ubuntu2) ...


Configuration file '/etc/gnome/defaults.list'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** defaults.list (Y/I/N/O/D/Z) [default=N] ? Y


wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.13.0-39-generic/updates/dkms/

depmod....

DKMS: install completed.
Building initial module for 3.16.0-24-generic
Done.

wl:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.16.0-24-generic/updates/dkms/

depmod....

DKMS: install completed.


WARNING: /lib/systemd/system/kdm.service is the selected default display manager but does not exist

Remove obsolete packages?


71 packages are going to be removed. 1 new package is going to be
installed.

Continue [yN] Details [d]d

Remove: akonadi-facebook audiocd-kio conky-all
kubuntu-default-settings kubuntu-netbook-default-settings
libcolord1 libgnutls28 libparted0debian1 libplist1 libplymouth2
libpoppler44 libreoffice-emailmerge libwpd-0.9-9 libwpg-0.2-2
libwps-0.2-2 nepomuk-core nepomuk-core-dev
nepomuk-core-ffmpegextractor python-gnupginterface

Remove (was auto installed) docbook-to-man g++-4.8 gcc-4.8-base:i386
libavfilter3 libavresample1 libboost-iostreams1.54.0
libboost-system1.54.0 libboost-thread1.54.0 libcdr-0.0-0
libcolorhug1 libdvbpsi8 libept1.4.12 libfreetype6-dev
libgnutls26:i386 libgssglue1 libicu48:i386 libidl-common libidl0
libkwineffects1abi4 libllvm3.4 libllvm3.4:i386 libmikmod2:i386
libmspub-0.0-0 libnepomukcleaner4 libnepomukcore4abi1 liboil0.3
libopenconnect2 liborbit2 liborcus-0.6-0 libpoppler-private-dev
libqmi-glib0 librtmp0:i386 libruby1.9.1 libssh2-1 libstdc++-4.8-dev
libtar0 libvisio-0.0-0 libwxbase2.8-0 libwxgtk2.8-0
linux-headers-3.13.0-38 linux-headers-3.13.0-38-generic
linux-headers-3.13.0-39 linux-headers-3.13.0-39-generic
linux-image-3.13.0-38-generic linux-image-extra-3.13.0-38-generic
nepomuk-core-data nepomuk-core-runtime pkg-config ruby1.9.1 sp
syslinux-themes-debian syslinux-themes-debian-wheezy


Install: opensp
y


Error in function:


A fatal error occurred

Please report this as a bug and include the files
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.

SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1)



Error during commit

A problem occurred during the clean-up. Please see the below message
for more information.

installArchives() failed


System upgrade is complete.

Restart required

To finish the upgrade, a restart is required.
If you select 'y' the system will be restarted.

Waiting for Steve to see this before I opt to restore my backup -- again.

SOLVED!!
For what ever reason, networkmanager service was not restarted. The fix: sudo service network-manager start

Added:
But, it doesn't survive a shutdown/reboot. Hmm.

Added:
I think I resolved this. A reboot will tell.

Added:
Nope. The network service is not being started when the system is booted. I have to start it manually. What's up with that? What do I need to tweek so the network comes up when the system is booted?

Added:
Editing /etc/NetworkManager/NetworkManager.conf and changing managed=true to managed=false also didn't solve this.

[NickStone]

You've logged this as solved but have not mentioned in your post if you had actually resolved the issue.

Does Kubuntu 14.10 now use systemd?

If it does you might want to use the following command to enable and start network-manager

sudo systemctl enable network-manager.service

then

sudo systemctl start network-manager.service

Only use the above command if systemd has been installed.

[Snowhog]

systemd isn't implemented in Ubuntu -- yet. Parts of systemd are installed with 14.10, but it isn't the default and doesn't run at boot.

My 32-bit 14.10 isn't suffering from this problem; only my 64-bit 14.10.

[Snowhog]

Well, I'm back to 14.04.1 LTS on my 64-bit HP. Until someone can tell me why network-manager won't start after booting so I don't have to start it manually when I'm logged in to my Desktop, I'll stay with 14.04.1 LTS on the HP.

[Snowhog]

This has been solved. See https://www.kubuntuforums.net/showth...l=1#post361748