#StackBounty: #18.04 #docker #routing #ifconfig Routing Docker in ubuntu

Bounty: 100

In my routing table on Ubuntu 18.04 I have these entries:

172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-9f3f970041e3
172.18.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-66d1d4ca46a2
172.19.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0

The docker0 entry I managed to move to a different IP range by creating a /etc/docker/daemon.json file and adding {"bip": "172.19.0.1/16"} to it.

I’m not sure where the br-* entries come from but I know that if I remove them that Docker stops working so they are used by Docker.

I need to have Docker assign these br-* addresses at 172.20.0.0 and 172.21.0.0 because the corp network uses the ones that they are currently occupying.

Questions:

  1. What part of Docker is creating these br-* entries?
  2. How does Docker use these entries?
  3. How can I configure Docker to assign them to other ranges?


Get this bounty!!!

#StackBounty: #networking #18.04 #iptables #firewall iptables match error "No chain/target/match by that name"

Bounty: 100

This is a fresh copy of ubuntu on my nVidia Jetson Nano, and I am trying to add the following rule to block network access for user 1001.

sudo iptables -A OUTPUT ! -o lo -m owner --uid-owner 1001 -j DROP

I get the following error:

iptables: No chain/target/match by that name.

Here is what I tried that works(YES) and does not work(NOT)

  1. YES – Remove the match criteria and replace with some other condition like source or target
  2. YES – On another similar installation on raspberry pi
  3. NOT – Change chain or target to INPUT or ACCEPT etc..
  4. NOT – Use a different user
  5. NOT – Try using user names instead of user ID
  6. NOT – Try a different match like –gid-owner
  7. NOT – Flushing the tables, restarting the PC etc
  8. NOT – Removed the ! -o lo from the command above

This is beyond me, I really have tried a lot of things and read through a number of posts with the same error – most of the times they are trying to do something complex – yet this is simple (and works on my other installation!). Any thoughts on how to understand this would be appreciated. Thanks!

EDIT: Based on comment below, here are the outputs:

grep CONFIG_NETFILTER_XT_MATCH /boot/config-$(uname -r)

grep: /boot/config-4.9.140-tegra: No such file or directory

I manually checked for the file and there’s no file that starts with config-XX in the boot folder. Additionally:

iptables -m owner --help

Could not determine whether revision 1 is supported, assuming it is.

….

owner match options:

[!] –uid-owner userid[-userid] Match local UID

[!] –gid-owner groupid[-groupid] Match local GID

[!] –socket-exists Match if socket exists


Get this bounty!!!

#StackBounty: #drivers #18.04 #nvidia #kernel #multiple-monitors Internal laptop screen stuck on Ubuntu loading screen, secondary monit…

Bounty: 100

I have a laptop with a gtx 1060 currently running on NVIDIA’s 418.39 driver. My secondary screen is working just fine, but my laptop screen is just stuck on the loading Ubuntu screen with the 5 dots.

If i do a sudo prime-select intel and rebootmy laptop screen works just fine but is stuck in 800×600 resolution without me being able to change it. when I do sudo prime-select nvidia I am stuck in the situation explained.

I have spend so much time trying to fix this, I am at a loss now, hopefully someone here can point me in the right direction. It would be nice to be able to use my laptop without a secondary screen.

Update: After trying to fix this issue my laptop screen now dosen’t work at all when loading Ubuntu, I have never been able to successfully install the Nvidia drivers either.


Get this bounty!!!

#StackBounty: #boot #18.04 AMD-VI : ubuntu 18.04.2 not booting

Bounty: 50

Since yesterday, my computer won’t boot on ubuntu. I did some system updates and tried to install a software (vscodium via .deb file), apt failed giving me a message about my cpu (don’t remember exactly what) so I restarted my computer, or at least tried to restart it.
Windows 10 (dual boot) is working fine.
I downloaded ubuntu 19.04 to boot on liveusb but it won’t boot either.
While trying to boot I encounter AMD-VI: Completion-Wait loop timed out
message along with iommu ivhd0 IOTLB_INV_TIMEOUT or something.

I already had issues installing ubuntu and upgrade linux kernel but managed to workaround with iommu=soft stuff (Impossible to install Ubuntu 18.04 on a new computer). I didn’t have any issues for several months so I thought it was behind me.

Computer specs :

  • Motherboard: b350 PC MATE
  • CPU: Ryzen 5 3600X
  • GPU: radeon RX 570
  • Ubuntu 18.04.2

At this point I really don’t know what to do…
I can’t even launch recovery mode.


Get this bounty!!!

#StackBounty: #apt #18.04 #kernel #lubuntu #udev Overriding a kernel module blacklisting that's reinstated during apt full-upgrade

Bounty: 200

On an old laptop with Lubuntu 18.04, I have sisfb working properly. It’s not blacklisted at all and loads on boot.

The problem is that sisfb is normally blacklisted in /lib/modprobe.d/fbdev-blacklist.conf. While I can comment that line out, whenever the udev package is updated using the weekly GUI update reminder, /lib/modprobe.d/fbdev-blacklist.conf is overwritten. While I can use chattr +i /lib/modprobe.d/fbdev-blacklist.conf to block the update from overwriting the file, that causes udev updates to fail, which causes apt full-upgrade to fail. Since the laptop is for the use of someone new to computers, this isn’t a workable method.

How can I load sisfb properly during boot?


Get this bounty!!!

#StackBounty: #18.04 #freeze #youtube #macbook-pro YouTube random crash, audio keeps repeating a given sound. Unable to do anything exc…

Bounty: 50

Update 23/04/2019 :
Upgrading to 18.10 did not solve the issue. The freezing happened again several times in both Firefox and Google Chrome, as well as in Opera. The last time it happened, I was on the Google Maps website. Strangely, the freezing seems to occur even more than before. It became so disturbing that I only use Ubuntu for offline work, and OS X for the rest.

Any suggestion would be appreciated.

Update 31/03/2019 :
Unfortunately it happened again yesterday and today, even after I disabled hardware acceleration and installed the Nvidia graphic driver. For now, it happened only in Firefox, but that is maybe because I mostly used Firefox. And I cannot open the terminal through the shortcut (Alt+Ctrl+T) during the freezing, even though it otherwise works.

I made a video showing the problem: https://www.youtube.com/watch?v=YZrK1bsnHCo
Yesterday, the freezing in Firefox even happened while I was not watching a video at all, but simply scrolling through the browser search results.



I installed Ubuntu 18.04.2 LTS on my MacBookPro two weeks ago. From time to time (at least once a day generally), while watching a YouTube video, the entire screen freezes, except the audio which keeps looping the sound being played at the time of the crash (like “shshshshshshshsh” or “stustustu” or “vidvidvidvid” I hope you see what I mean). The only thing I can do is force shut down the computer by pressing and holding down the power button for a few seconds.

I have absolutely no idea where this comes from. It happens both on Firefox and Chrome.

Do you have any idea what it could be, how I could prevent that or if there is at least another way to simply force quit YouTube/ Firefox / Chrome (without shutting down the entire computer by pressing the power button a few seconds) and simply restart the browser even though all shortcuts I tried as well as mouse movements did not respond during the crash?

Thanks for your help !


For Aravind:

$ hwinfo --gfxcard
14: PCI 100.0: 0300 VGA compatible controller (VGA)         
  [Created at pci.378]
  Unique ID: VCu0.9RMFrOT84MB
  Parent ID: vSkL.jPq0IMUQb1A
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GK107M [GeForce GT 650M Mac Edition]"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0fd5 "GK107M [GeForce GT 650M Mac Edition]"
  SubVendor: pci 0x106b "Apple Inc."
  SubDevice: pci 0x00fc 
  Revision: 0xa1
  Driver: "nouveau"
  Driver Modules: "nouveau"
  Memory Range: 0xc0000000-0xc0ffffff (rw,non-prefetchable)
  Memory Range: 0x90000000-0x9fffffff (ro,non-prefetchable)
  Memory Range: 0xa0000000-0xa1ffffff (ro,non-prefetchable)
  I/O Ports: 0x2000-0x207f (rw)
  Memory Range: 0xc1000000-0xc107ffff (ro,non-prefetchable,disabled)
  IRQ: 47 (557954 events)
  Module Alias: "pci:v000010DEd00000FD5sv0000106Bsd000000FCbc03sc00i00"
  Driver Info #0:
    Driver Status: nvidiafb is not active
    Driver Activation Cmd: "modprobe nvidiafb"
  Driver Info #1:
    Driver Status: nouveau is active
    Driver Activation Cmd: "modprobe nouveau"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (PCI bridge)

31: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: _Znp.RpDAoKcUWbF
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel 3rd Gen Core processor Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0166 "3rd Gen Core processor Graphics Controller"
  SubVendor: pci 0x106b "Apple Inc."
  SubDevice: pci 0x00fb
  Revision: 0x09
  Driver: "i915"
  Driver Modules: "i915"
  Memory Range: 0xc1400000-0xc17fffff (rw,non-prefetchable)
  Memory Range: 0xb0000000-0xbfffffff (ro,non-prefetchable)
  I/O Ports: 0x3000-0x303f (rw)
  IRQ: 46 (243 events)
  Module Alias: "pci:v00008086d00000166sv0000106Bsd000000FBbc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #14

$ sudo journalctl -r -p err
-- Logs begin at Fri 2019-03-15 00:04:59 CET, end at Fri 2019-03-29 15:09:01 CET
Mär 29 13:19:35 frieder-MacBookPro kernel: nouveau 0000:01:00.0: msvld: init fai
Mär 29 13:19:35 frieder-MacBookPro kernel: nouveau 0000:01:00.0: msvld: unable t
Mär 29 13:18:17 frieder-MacBookPro bluetoothd[885]: Failed to set mode: Blocked 
Mär 29 13:18:17 frieder-MacBookPro spice-vdagent[1650]: Cannot access vdagent vi
Mär 29 13:18:16 frieder-MacBookPro pulseaudio[1502]: [pulseaudio] backend-ofono.
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
lines 1-23

dmesg gives really a lot of text. Much of it is DATA_ERROR but it’s way too much to copy-paste it here.


Get this bounty!!!

#StackBounty: #18.04 #sound #freeze #youtube #macbook-pro YouTube random crash, audio keeps repeating a given sound. Unable to do anyth…

Bounty: 50

Update 23/04/2019 :
Upgrating to 18.10 did not solve the issue. The freezing happened again several times in both Firefox and Google Chrome, as well as in Opera. The last time it happened, I was on the Google Maps website. Strangely, the freezing seems to occur even more than before. It became so disturbing that I only use Ubuntu for offline work, and OS X for the rest.

Any suggestion would be appreciated.

Update 31/03/2019 :
Unfortunately it happened again yesterday and today, even after I disabled hardware acceleration and installed the Nvidia graphic driver. For now, it happened only in Firefox, but that is maybe because I mostly used Firefox. And I cannot open the terminal through the shortcut (Alt+Ctrl+T) during the freeezing, even though it otherwise works.

I made a video showing the problem: https://www.youtube.com/watch?v=YZrK1bsnHCo
Yesterday, the freezing in Firefox even happened while I was not watching a video at all, but simply scrolling through the browser search results.



I installed Ubuntu 18.04.2 LTS on my MacBookPro two weeks ago. From time to time (at least once a day generally), while watching a YouTube video, the entire screen freezes, except the audio that keeps repeating the sound being said at the time of the crash (like “shshshshshshshsh” or “stustustu” or “vidvidvidvid” I hope you see what I mean). The only thing I can do is force shut down the computer by pressing on the power button a few second and then restart.

I have absolutely no idea where this comes from. It happens both on Firefox and Chrome.

Do you have any idea what it could be, how I could prevent that or if there is at least another way to simply force quit YouTube/ Firefox / Chrome (without shutting down the entire computer by pressing the power button a few seconds) and simply restart the browser even though all shortcuts I tried did not respond during the crash including the mouse?

Thanks for your help !


For Aravind :

$ hwinfo --gfxcard
14: PCI 100.0: 0300 VGA compatible controller (VGA)         
  [Created at pci.378]
  Unique ID: VCu0.9RMFrOT84MB
  Parent ID: vSkL.jPq0IMUQb1A
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia GK107M [GeForce GT 650M Mac Edition]"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0fd5 "GK107M [GeForce GT 650M Mac Edition]"
  SubVendor: pci 0x106b "Apple Inc."
  SubDevice: pci 0x00fc 
  Revision: 0xa1
  Driver: "nouveau"
  Driver Modules: "nouveau"
  Memory Range: 0xc0000000-0xc0ffffff (rw,non-prefetchable)
  Memory Range: 0x90000000-0x9fffffff (ro,non-prefetchable)
  Memory Range: 0xa0000000-0xa1ffffff (ro,non-prefetchable)
  I/O Ports: 0x2000-0x207f (rw)
  Memory Range: 0xc1000000-0xc107ffff (ro,non-prefetchable,disabled)
  IRQ: 47 (557954 events)
  Module Alias: "pci:v000010DEd00000FD5sv0000106Bsd000000FCbc03sc00i00"
  Driver Info #0:
    Driver Status: nvidiafb is not active
    Driver Activation Cmd: "modprobe nvidiafb"
  Driver Info #1:
    Driver Status: nouveau is active
    Driver Activation Cmd: "modprobe nouveau"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (PCI bridge)

31: PCI 02.0: 0300 VGA compatible controller (VGA)
  [Created at pci.378]
  Unique ID: _Znp.RpDAoKcUWbF
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel 3rd Gen Core processor Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0166 "3rd Gen Core processor Graphics Controller"
  SubVendor: pci 0x106b "Apple Inc."
  SubDevice: pci 0x00fb
  Revision: 0x09
  Driver: "i915"
  Driver Modules: "i915"
  Memory Range: 0xc1400000-0xc17fffff (rw,non-prefetchable)
  Memory Range: 0xb0000000-0xbfffffff (ro,non-prefetchable)
  I/O Ports: 0x3000-0x303f (rw)
  IRQ: 46 (243 events)
  Module Alias: "pci:v00008086d00000166sv0000106Bsd000000FBbc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #14

$ sudo journalctl -r -p err
-- Logs begin at Fri 2019-03-15 00:04:59 CET, end at Fri 2019-03-29 15:09:01 CET
Mär 29 13:19:35 frieder-MacBookPro kernel: nouveau 0000:01:00.0: msvld: init fai
Mär 29 13:19:35 frieder-MacBookPro kernel: nouveau 0000:01:00.0: msvld: unable t
Mär 29 13:18:17 frieder-MacBookPro bluetoothd[885]: Failed to set mode: Blocked 
Mär 29 13:18:17 frieder-MacBookPro spice-vdagent[1650]: Cannot access vdagent vi
Mär 29 13:18:16 frieder-MacBookPro pulseaudio[1502]: [pulseaudio] backend-ofono.
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
Mär 29 13:18:10 frieder-MacBookPro kernel: nouveau 0000:01:00.0: gr: DATA_ERROR 
lines 1-23

“dmesg” gives really a lot of text. Much of it is DATA_ERROR but its way too much to copy paste it here


Get this bounty!!!

#StackBounty: #networking #18.04 #proxy Set Ubuntu Desktop Network Proxy Settings programmatically on 18.04

Bounty: 50

I try to create a fully automated desktop setup using preseed et al. The desktops will be running behind a “corporate proxy” (I know, I don’t like that either) and therefore need to be configured accordingly.

To get the proxy configured theres a fair amount of documentation such as https://www.serverlab.ca/tutorials/linux/administration-linux/how-to-configure-proxy-on-ubuntu-18-04/.

Most of the tasks are easy to automate, but I do not quite understand where the Network Manager persists its proxy settings (refering to the first section of the documentation linked above). Any hints on how to achieve this?


Get this bounty!!!

#StackBounty: #18.04 #sound #pulseaudio #alsa pulseaudio not loading properly

Bounty: 50

My Ubuntu 18.04 PC has decided that pulseaudio is nothing good in the world, and therefore pulseaudio suddenly will stop seeing literally any audio devices– quite literally, too, as aplay -l isn’t returning with anything nice to say.

I’ve found that I keep getting that dreaded E: [pulseaudio] main.c: Daemon startup failed. error, which spells no good news. pulseaudio -v, however, doesn’t report the inotify issue, but instead pushes;

E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.

pulseaudio -D reported with the startup error, and running pulseaudio -k and --start consecutively do not work either.

I attempted to restart alsa with sudo alsa force-reload, though that did not help. Running pacmd responded with Daemon not responding, and not much else. rm -r ~/.config/pulse; pulseaudio -k didn’t help, either.

For a tl;dr, pulseaudio isn’t loading my sound devices and no fixes I’ve seen are working.

Edit for clarity as of 4/20/19: I’d forgotten about this question, but I would like to point out some information I had missed that should be noted. Restarting the computer does in fact fix the problem. It only happens occasionally when the Facebook Messenger call applet window is open on Firefox. Every once in a while, you will get a split second of audio from whatever was playing in the background when it happened.


Get this bounty!!!

#StackBounty: #drivers #18.04 #graphics #intel-graphics Screen flickering as I type

Bounty: 50

I have laptop with 18.04 installed, this problem also occurred when I use 16.04 before.

My screen seems to blinked when I start typing, it blinked instantly that I could not capture the moment of it, anyhow the blinking also happens randomly, there is no pattern at all.

I have tried the suggestion from various source, this includes.

  1. Updating the kernel, Iam using kernel 4.19 now, before this Im using kernel 4.5 or 4.6 but does not work also.
  2. Updating graphics driver, running command from https://askubuntu.com/a/215967. Doesn’t seem to work, the flickering still happens.

How do I stop this from happening, it is not really distracting because it’s only fraction of second, but if I can stop it I rather do so.

I don’t have dedicated video graphics card, using Intel graphics at the moment. I think it’s Intel HD 3000.

sudo lshw -C video | grep product result.

sudo lshw -C video | grep product
product: 3rd Gen Core processor Graphics Controller

uname -r result.

$ uname -r
4.19.20-041920-generic

If you want further command, I’d love to include them.

Ridgwell


Get this bounty!!!