#StackBounty: #18.04 #webcam webcam no longer detected after updating Ubuntu 18.04 LTS

Bounty: 100

For a while, my microphone wasn’t working, but my webcam was. Now I have the reverse problem. Evidently, trying solutions which worked for other users isn’t going to cut it, since I have already managed to make my Dell Precision M6800 worse by trying random solutions suggested on various threads (it no longer reliably wakes up from suspend, but reboots instead sometimes). Ubuntu 16.04 LTS was rock stable on my machine, but I have had numerous problems with 18.04 LTS since it was first released. My machine finally started working smoothly after about six months of updates and was stable for some time before things started to go wrong again about six months ago. Anyway, I am frustrated and could really use some more professional help to get things working again (if it is not some hardware failure, which I rather doubt). Since I am not that handy with Ubuntu, I would appreciate some context/explanation for whatever commands are suggested so that I may fare better with troubleshooting in the future. To my understanding, it should be a good start to provide the output of ls -ltrh /dev/video*:

ls: cannot access '/dev/video*': No such file or directory

the output of getfacl /dev/video:

getfacl: /dev/video: No such file or directory

the output of ls -ltrh /dev/video*:

ls: cannot access '/dev/video*': No such file or directory

the output of lsusb:

Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

the output of v4l2-ctl --list-devices:

Failed to open /dev/video0: No such file or directory

and, finally, the output of lspci:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1c.6 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #7 (rev d4)
00:1c.7 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #8 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM87 Express LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Saturn XT [FirePro M6100] (rev ff)
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM] (rev ff)
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)
11:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)

I have no idea what most of these commands are about in any detail, but I tried to look through all applicable threads for relevant diagnostic commands. Please let me know if I omitted anything potentially important.

EDIT: My microphone is detected by Ubuntu but actually isn’t working either.


Get this bounty!!!

#StackBounty: #18.04 #ssh #xorg #docker #x11-forwarding X11 over remote Docker container stops working after resetting VPN

Bounty: 50

I’m running on ubuntu 18.04, with a “operator” machine VPN’ed into a network that has the “Test” machine.

The test machine runs a Docker container that has a GUI application that I forward over X11. I use SSH on the operator machine to SSH into the test machine. Then, I run the Docker container. Normally, the GUI shows up on my “operator” machine when I run the Docker container.

However, I’ve noticed that as soon as I disconnect my VPN and reconnect,I get a “Could not connect to display $DISPLAY” error.

I would need to create a new container from the image to have the X11 working again.

Here is how I launch it:

SOCK=/tmp/.X11-unix
XAUTH=/tmp/.docker.xauth
xauth nlist $DISPLAY | sed -e 's/^..../ffff/' | xauth -f $XAUTH nmerge -
chmod 777 $XAUTH
sudo docker run  --gpus all -it --privileged --network=host -e DISPLAY=$DISPLAY -v $XSOCK:$XSOCK -v $XAUTH:$XAUTH -e XAUTHORITY=$XAUTH  image

Nothing changed on the “test” machine or docker container in this situation. Even if the VPN reconnect assigned me the same IP as prior, it would still have this issue.


Get this bounty!!!

#StackBounty: #drivers #18.04 #hp #webcam #camera HP Truevision HD built-in webcam not working in ubuntu 18.04

Bounty: 500

I have a HP Notebook-15-ac603tu and after shifting to ubuntu from windows, the camera stopped working.

I have run the following commands with output:

  • lsusb :
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 042: ID 0bda:57d6 Realtek Semiconductor Corp. 
Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 25a7:fa23  
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  • v4l2-ctl –list-devices :
HP Truevision HD: HP Truevision (usb-0000:00:14.0-5):
    /dev/video0
  • ls -ltr /dev/video* :
crw-rw----+ 1 root video 81, 0 Mar 22 11:59 /dev/video0
  • cheese :
(cheese:6397): Gtk-WARNING **: 12:11:18.227: Theme parsing error: cheese.css:7:35: The style property GtkScrollbar:min-slider-length is deprecated and shouldn't be used anymore. It will be removed in a future version

** (cheese:6397): CRITICAL **: 12:11:18.789: cheese_preferences_dialog_on_source_change: assertion '_tmp2_ > ((guint) 0)' failed

(cheese:6397): cheese-CRITICAL **: 12:11:18.789: cheese_camera_device_get_name: assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed

(cheese:6397): GLib-CRITICAL **: 12:11:18.790: g_variant_new_string: assertion 'string != NULL' failed

(cheese:6397): GLib-CRITICAL **: 12:11:18.790: g_variant_ref_sink: assertion 'value != NULL' failed

(cheese:6397): GLib-GIO-CRITICAL **: 12:11:18.790: g_settings_schema_key_type_check: assertion 'value != NULL' failed

(cheese:6397): GLib-CRITICAL **: 12:11:18.790: g_variant_get_type_string: assertion 'value != NULL' failed

(cheese:6397): GLib-GIO-CRITICAL **: 12:11:18.790: g_settings_set_value: key 'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of type '(null)' was given

(cheese:6397): GLib-CRITICAL **: 12:11:18.791: g_variant_unref: assertion 'value != NULL' failed

** (cheese:6397): CRITICAL **: 12:11:18.791: cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device != NULL' failed

** (cheese:6397): CRITICAL **: 12:11:20.317: cheese_preferences_dialog_on_source_change: assertion '_tmp2_ > ((guint) 0)' failed

(cheese:6397): cheese-CRITICAL **: 12:11:20.318: cheese_camera_device_get_name: assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed

screenshot of cheese displaying black screen

I tried almost everything and I don’t know how to proceed further (basically am a noob user). Please help me out in working my webcam.


Get this bounty!!!

#StackBounty: #networking #18.04 #ssl #openssl #kvm-switch Setting up barrier to run on startup

Bounty: 50

Barrier is a free popular KVM software that enables mouse/keyboard sharing across several devices.

I’ve been fiddling with it for a few hours and I can’t seem to get it right.

I have a barrier server running on my Windows machine.
I’ve downloaded the git repository and built the binaries. I’ve copied barrier, barrierc and barriers into /usr/bin.

If I run barrier GUI, specify the server IP and enable the server, it works. I can do it with and without SSL (as long as both the client and the server have the same setting set). I would prefer to use SSL though.

I’ve then tried running barrierc --enable-crypto <ip>. The server acknowledges the connection, but says it’s not secure and it doesn’t work. However, if I run the same command with the -f flag barrierc -f --enable-crypto <ip> which makes it run in the foreground, it all works dandy.

Since I’m on Ubuntu 18.04, I’ve setup a systemd service like so:

[Unit]
Description=Barrier mouse/keyboard share
Requires=display-manager.service
After=display-manager.service
StartLimitIntervalSec=0

[Service]
Type=simple
ExecStart=/usr/bin/barrierc -f --enable-crypto 192.168.12.96
Restart=always
RestartSec=1
User=karlovsky120

[Install]
WantedBy=multi-user.target

I’ve named it barrier.service and copied it into /etc/systemd/system/.

I’ve tried starting it manually, but it refuses to work. From what I can tell from systemctl status, it looks like systemd runs the client, but the client exits immediately and then it restarts it. I’ve tried with and without the -f flag, but the result is the same.

The server also complains that the client connection might not be secure, which is the same error you get when you try to connect with a non SSL client to an SSL server. It does so with and without the -f flag.

I know I have to enable the service to have it run on startup, but how do I get it to work at all?


Get this bounty!!!

#StackBounty: #networking #wireless #18.04 #atheros Weak Wifi Signal Ubuntu 18.04 Qualcomm Atheros QCA6174 802.11ac

Bounty: 50

I’ve been using Ubuntu 18.04 for a while, but a few days ago the wifi signal became weak to the point I can’t connect if I’m not really close to the router.
Other devices can connect in the same wireless from longer distances.
I already tried solutions from other posts, such as this one and this, nothing worked.
I suspect it started after an update.

lspci output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 930M] (rev a2)
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 07)

lshw -class network output:

*-network                 
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 32
       serial: 40:49:0f:fe:23:55
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=4.18.0-17-generic firmware=WLAN.RM.2.0-00180-QCARMSWPZ-1 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:127 memory:d5000000-d51fffff
  *-network
       description: Ethernet interface
       product: RTL810xE PCI Express Fast Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0
       version: 07
       serial: f4:8e:38:e4:53:89
       size: 10Mbit/s
       capacity: 100Mbit/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s
       resources: irq:17 ioport:d000(size=256) memory:d5204000-d5204fff memory:d5200000-d5203fff

Thanks in advance


Get this bounty!!!

#StackBounty: #18.04 #ssh #remote-desktop #remote #remmina Configure Remmina or other GUI control app through ssh without X forwarding

Bounty: 50

Due to the COVID-19 crisis, I only have access to my work computer through ssh (so no physical access). Since I connect to this computer through another one that does not allow X forwarding, I can not forward X.

I now need to control an app that does not allow me to do so by just using the terminal.

The best option that comes to my mind (I accept suggestions) is using Remmina, but I need to be able to start it and configure it remotely through ssh.

Whenever I try to start Remmina through ssh it throws an error due to unavailability of X forwarding.


Get this bounty!!!

#StackBounty: #18.04 #ssh #remote #remmina Configure Remmina or other GUI control app through ssh without X forwarding

Bounty: 50

Due to the COVID-19 crisis, I only have access to my work computer through ssh (so no physical access). Since I connect to this computer through another one that does not allow X forwarding, I can not forward X.

I now need to control an app that does not allow me to do so by just using the terminal.

The best option that comes to my mind (I accept suggestions) is using Remmina, but I need to be able to start it and configure it remotely through ssh.

Whenever I try to start Remmina through ssh it throws an error due to unavailability of X forwarding.


Get this bounty!!!