16.04 (Xenial Xerus) Known bugs and work-a-rounds

[stepheny]

I used

dpkg -i google-chrome-stable_current_amd64.deb

But that's not the point, a LTS shouldn't have such issues! And if it does they should be quickly recognised and fixed.

The nVidia issue is a major problem for many.

[QIII]

stepheny:

Please keep your posts strictly to known issues and work-arounds. This thread is intended neither for editorials nor for critiques. You are welcome to make those posts elsewhere in appropriate sub-forums.

[stepheny]

QIII:

I have identified two issues and offered workarounds for both of them. This reply to your critique is my first post here without workaround information! So where is the problem?

[howefield]

Instead of using the Software Centre to install downloaded debs, use gdebi instead, it's in the repositories.

Just to add that apt now installs third party .deb packages (which I am quite enthused with). My preference previously was to install gdebi and set deb packages to use it by default but not needed anymore.

sudo apt install pathtodebpackage

[jeremy31]

Seems there is a bug in network-manager package that detects wireless devices as LAN

nmcli -f all device show | sed '/^GENERAL.DEVICE:[ ]\+lo$/,/^$/d; /^AP\[[0-9]\+\]\./d'

Command is part of the wireless-info script will show similar to the snipped results from a recent poster

GENERAL.DEVICE:                         wlp4s0
GENERAL.TYPE:                           ethernet
GENERAL.NM-TYPE:                        NMDeviceEthernet
GENERAL.VENDOR:                         Intel Corporation
GENERAL.PRODUCT:                        Wireless 8260
GENERAL.DRIVER:                         iwlwifi

The workaround for now is to

systemctl restart NetworkManager.service

after every reboot. A similar bug report

[BJones007]

Found this useful for a GNS3 problem I was having here and here

It seem that upgrading to 16.04 broke GNS3 if GNS3 is installed from source and not from the package. This is due to major Python version change in Xenial requiring you to reinstall. Clean install from source will work, but we recommend to use the ubuntu package made by the GNS3 team.

First you need to uninstall gns3:

pip3 uninstall gns3-gui
pip3 uninstall gns3-server

Even if the previous command doesn't work, continue.

Make sure you don't have gns3, gns3server, dynamips, vpcs and ubridge in /usr/local/bin. If something is still here delete it.

After that follow the instruction to install the package


Ubuntu-based distributions (64-bit only)


Run the following commands in a terminal window

sudo add-apt-repository ppa:gns3/ppa 
sudo apt-get update 
sudo apt-get install gns3-gui

If you want IOU support:

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install gns3-iou

Hope this helps. Cheers

[insane9]

Adding HandleLidSwitchDocked=suspend

to /etc/systemd/logind.conf seems to have fixed the problem on my HP or at lease removing #.

Can confirm this works. Thanks! Was a very frustrating issue.

[stepheny]

I don't want to appear rude but what is the point of of this thread? Are we to just list workarounds for failings in 16.04 or is somebody actually looking into fixing these problems?

[PaulW2U]

I don't want to appear rude but what is the point of of this thread? Are we to just list workarounds for failings in 16.04 or is somebody actually looking into fixing these problems?

For anything I've posted here a bug report has also been raised. A workaround is often required before a fix is released.

[QIII]

I don't want to appear rude but what is the point of of this thread? Are we to just list workarounds for failings in 16.04 or is somebody actually looking into fixing these problems?

This thread is for just what it says: known bugs and work-arounds.

This forum is populated by users such as yourself. For bugs to be brought to the attention of Ubuntu developers (who don't hang out here) they must be reported. The Ubuntu Forums do not act as a bug report mechanism.