Ubuntu HowTo: lxde desktop non-functional in ubuntu 20.04 but works in 19.10

Original Source Link

I’m trying to install lxde desktop on a remote Ubuntu 20.04 server and VNC in.

When I use a ubuntu 19.10 server I have no problem:

#USING 19.10

sudo apt-get install -y lxde xorg lxdm  --no-install-recommends 
sudo apt-get install -y lxde xorg lxdm

sudo reboot

Using VNC it works just fine to access the GUI in 19.10

enter image description here

#USING 20.04

sudo apt-get install -y lxde xorg lxdm  --no-install-recommends 
sudo apt-get install -y lxde xorg lxdm
sudo reboot

Hangs here and retries in infinite loop in 20.04:

enter image description here

Can someone tell me what the difference is and help me solve this?

I had this problem when trying out LXQT on a virtual machine. The problem turned out to be I was missing the driver for the display.

I installed LXQT

apt-get install --no-install-recommends lxqt lubuntu-desktop

After a reboot, the terminal hung at the same spot as you. Accessing via a terminal (either ctrl-alt-f2 or use SSH) showed that SDDM was running, but there weren’t any logs indicating why the graphics were not appearing. The lshw command helped me narrow down the issue by showing the display was UNCLAIMED

# lshw -C display
  *-display UNCLAIMED
       description: VGA compatible controller
       product: SVGA II Adapter
       vendor: VMware

In order to fix

apt-get install linux-modules-extra-$(uname -r)

Normally this package is already installed, but it is not installed when using the linux-virtual kernel package (as I am using). Other solutions I saw indicated other video driver issues can cause it

I had a similar issue with gdm3 when switched between operating system version, then I found this cool stuff for solving the problem
Solution .

For resolve this Problem :
1. Editing the Configuration file of gdm
    1.vi /etc/gdm/custom.conf or nano or gedit (Any editor is fine)
    2.You will find a line this line #WaylandEnable=false
    3.Uncomment that line

Whole Configuration file looks like this.




2.Installing lubuntu-desktop

sudo apt install -y lubuntu-desktop
sudo reboot

3.Editing Grub

Step 1: Editing Grub

When you boot your system, just stop at the Grub screen like the one below. If you don’t see this screen, keep holding Shift key at the boot time.

At this screen, press ‘E’ key to go into the editing mode.
Edit Grub Menu to fix Ubuntu freezing at loginPress ‘E’ key

You should see some sort of code like the one below. You should focus on the line that starts with Linux.
Editing grub to fix frozen boot issue with Ubuntu LinuxGo to line starting with Linux
Step 2: Temporarily Modifying Linux kernel parameters in Grub

Remember, our problem is with the NVIDIA Graphics drivers. This incompatibility with open source version of NVIDIA drivers caused the issue so what we can do here is to disable these drivers.

Now, there are several ways you can try to disable these drivers. My favorite way is to disable all video/graphics card using nomodeset.

Just add the following text at the end of the line starting with Linux. You should be able to type normally. Just make sure that you are adding it at the end of the line.


Now your screen should look like this:
Disabling NVIDIA Open Source graphics driversDisable graphics drivers by adding nomodeset to the kernel

Press Ctrl+X or F10 to save and exit. Now you’ll boot with the newly modified kernel parameters here.
Explanation of what we did here (click to expand)
Step 3: Make permanent changes in Grub


In some cases, not using the graphics driver at all or switching to the open source driver may result in poor looking resolution. If that’s the case with you, try switching to proprietary driver as explained in alternate step 3 (next section).

Don’t be too happy yet just because you are able to login to your system now. What you did was temporary and the next time you boot into your system, your system will still freeze because it will still try to load the graphics drivers.

Does this mean you’ll always have to edit Kernel from the grub screen? Thankfully, the answer is no.

What you can do here to change the grub configuration so that the Linux kernel will not try to load the graphics driver before the display server.

To do that, open the terminal (use Ctrl+Alt+T shortcut) and then use the following command to open the grub configuration file in Gedit editor:

sudo gedit /etc/default/grub

You’ll have to use your password to open this file. Once you have the text file opened, look for the line that contains: GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”.

Change this line to: GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset”

It should look something like this:
Edit Grub To Fix Ubuntu Boot FreezeEdit Grub To Fix Ubuntu Boot Freeze

Save the file and update grub so that changes are taken into effect. Use this command:

sudo update-grub

Once it is complete, reboot your system and it should not freeze anymore.

4.Changing Default Driver Manager
    Try installing lightdm or reinstalling gdm3

sudo apt-get install lightdm

or Xfce 4

sudo apt-get install xubuntu-desktop.

try reinstall ubuntu desktop manager

sudo apt install --reinstall ubuntu-gnome-desktop

for reference:

Tagged : / / /

Ubuntu HowTo: Can’t Uninstall “asciidoc” Package

Original Source Link

I was building from source a package which needed asciidoc on Ubuntu 19.10. Now I want to uninstall it but I get the following

Package 'asciidoc' is not installed, so not removed

while it is clearly installed. Why is that happening? How can I uninstall it?

The main asciidoc executable in 18.04 LTS and newer versions is located in asciidoc-base package.

You have to remove it:

sudo apt-get purge asciidoc-base

For source code installations, here are the install/uninstall commands…

Installing asciidoc for all users

Create configure using autoconf(1); use configure to create the Makefile; run make(1); build the man pages; install:

$ autoconf
$ ./configure
$ make
$ sudo make install

To uninstall:

$ sudo make uninstall

Source: http://asciidoc.org/INSTALL.html

Update #1

For binary installations…

dpkg -l *ascii* | grep ii

un asciidoc <none> <none> (no description available) 
ii asciidoc-base 8.6.10-3 all Minimal version of asciidoc not suitable for pdf 
ii asciidoc-common 8.6.10-3 all Basic data and configuration files for asciidoc un asciidoc-doc <none> <none> (no description available)

To completely uninstall asciidoc, you’ll need to run all of these commands…

sudo apt-get purge asciidoc # already done

sudo apt-get purge asciidoc-base

sudo apt-get purge asciidoc-common

Tagged : / /

Ubuntu HowTo: 19.10 freezes at blank purple screen

Original Source Link

I upgraded to Ubuntu 19.10 yesterday while going to bed and might have fallen asleep while installing. I don’t recall if I interrupted or succesfully installed it.

I dual boot Ubuntu and windows should it be relevant.

When I boot Ubuntu up it does not show the loading bar and logo. It just goes plain blank purple and does not get any further.

Is there a way I can troubleshoot?
If not, Is is possible to reinstall ubuntu keeping my data?
If not, should I nuke it and install fresh with USB?

If you have a dedicated GPU, the most common reason for getting the purple screen is the graphics driver needs to be reinstalled. To fix this see Fixing Ubuntu Freezing at Boot Time.

To summarize steps in link:

  1. Editing Grub
  2. Temporarily Modifying Linux kernel parameters in Grub
  3. Make permanent changes in Grub
  4. [Alternate for NVIDIA Graphics] Update your system and install proprietary NVIDIA drivers
  5. Enjoy Ubuntu Linux

sharing solution from this post
To edit Grub2 during the boot process try the following:

  1. Immediately after the BIOS splash screen during boot, press and hold the SHIFT button. This will display you grub containing a list of kernels and recovery options

    enter image description here

  2. Press e to edit the first kernel displayed

    enter image description here

  3. Find the line ending with quiet splash. Add your boot option before these key words – i.e. so the line looks like […]nomodeset quiet splash

  4. Press CTRL + X to boot

Follow the steps in Coldfish’s answer on how to fix the nomodeset boot option permanently so that you don’t have to go through this manual procedure again.

Tagged : /

Ubuntu HowTo: How to remove snap completely without losing the Chromium browser?

Original Source Link

I am wondering whether or not there is a way to completely remove snap from Ubuntu 19.10 without losing the ability to install important applications like Chromium.

When I just recently updated to the newest Ubuntu release I realized that the installer programmatically reinstalled snap, although I had manually removed it before. Additionally the installer removed Chromium, which was installed via the repositories, and reinstalled it via snap.

As I don’t want snap to be installed on my machines for various reasons my question is if anybody knows a safe way to remove it, and to get the Chromium DEB back to the sources?

Is there a PPA? Could I use a source of an Ubuntu flavor additionally, which didn’t remove the Chromium Deb from its sources?

Debian Repo Saves the Day!

Debian still maintains Chromium as a regular package in their APT repository. We can configure Ubuntu to get it from there, and continue to receive timely security updates along with all of our other OS updates. This makes sense from a security perspective, since Debian is a very well known high-profile project, and is already where Ubuntu gets most of its packages. There is no need to risk installing mystery browser builds from some random source or fringe PPA.

Warning: This is entirely unsupported and could conceivably cause problems either immediately or in the future. If you break something, it’s your own fault.

Here’s what I did on Ubuntu 19.10:

sudo apt update && sudo apt upgrade

That brings all my already-installed Ubuntu packages up to date, so it will be easier to see how upgrades are affected after I make my changes.

snap remove chromium

Bye bye, annoying snap.

sudo apt purge chromium-browser chromium-chromedriver

Bye bye, fake Chromium packages. (You can leave out the chromium-chromedriver part if that package isn’t installed on your system.)

umask 22

That just makes sure that the files I create will be readable by everyone, including the system.

Create an /etc/apt/sources.list.d/debian-stable.list file containing:

deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://ftp.us.debian.org/debian/ stable main
deb-src [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://ftp.us.debian.org/debian/ stable main

deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://security.debian.org/ stable/updates main
deb-src [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://security.debian.org/ stable/updates main

# stable-updates, previously known as 'volatile'
deb [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://ftp.us.debian.org/debian/ stable-updates main
deb-src [signed-by=/usr/share/keyrings/debian-archive-keyring.gpg] http://ftp.us.debian.org/debian/ stable-updates main

That tells apt to look for packages not only in the Ubuntu archives, but also in the Debian stable archives. This is ordinarily a bad idea, because you don’t want hundreds of random Ubuntu packages being replaced with Debian versions; that would very likely break your system. However, we’re going to add some rules to prevent this from happening.

(Note: The /usr/share/keyrings/debian-archive-keyring.gpg file referenced above, along with several other Debian keyring files, are already present on my Ubuntu system thanks to the debian-archive-keyring package. It’s probably on your system already, too, but if not, you should install it: sudo apt install debian-archive-keyring)

Create an /etc/apt/preferences.d/debian-chromium file containing:

Explanation: Prevent installing from debian repo.
Package: *
Pin: origin "*.debian.org"
Pin-Priority: 1

Explanation: Allow installing chromium from debian repo.
Package: chromium*
Pin: origin "*.debian.org"
Pin-Priority: 100

The first stanza assigns a very low priority to all packages from the Debian archives, so they will not override anything in the Ubuntu archives. The second stanza assigns a somewhat higher priority to Debian Chromium packages. This is called apt pinning, and is described in the apt_preferences manual.

(I suppose I could have assigned a much higher priority to Debian’s Chromium packages if I needed them to override Ubuntu’s, but since they use different package names, no overriding is necessary.)

sudo apt update

That refreshes the package database, so my Ubuntu system now knows about everything in the Debian archives that I added.

apt upgrade --simulate

That shows me what a system-wide package upgrade would do, without actually doing it. Since I already did an upgrade before making any changes, I don’t expect to see any upgradable packages listed here.

If one or two upgradable packages were listed, it could mean that Ubuntu happened to release some updates while I was working, which is normal. I would ask apt where each of those updates come from before proceeding, with apt-cache policy package-name. If any of them were from the Debian archives, I would consider reverting my changes, by removing the files I created and running sudo apt update again.

If many upgradable packages were listed, it would probably mean that apt now thinks Debian’s packages are valid replacements for Ubuntu’s packages, which I do not want. This would happen if I made a mistake in those files I created. I would revert my changes, by removing the files I created and running sudo apt update again. I might then consider starting over and typing more carefully.

All was well at this point (no upgradable packages were listed), so I proceeded.

sudo apt install chromium

The package manager then asked me to confirm, listing chromium and a small handful of dependency packages needed by Chromium. Once again, if many packages were listed here, I would investigate and consider reverting my changes. (I investigated each dependency anyway, because I’m careful, and found that only one of the dependencies was coming from the Debian archive: libjpeg62-turbo, and it doesn’t conflict with anything I have installed.) All looked well, so I told the package manager to proceed.

When it finished, Chromium was finally installed as an apt package. Thanks, Debian maintainers!

I don’t use any snaps, so the next thing I did was to look in the snap directory in my home dir, make sure there was nothing in there that I needed, and then drop it in the trash. If you want to do the same, consider first that any user data that you created/modified/saved in Chromium since the snap was first installed lives somewhere under that snap folder. (Probably under snap/chromium/current/.config which is hidden by default in most file managers.) You might want to back it up or move it to chromium’s usual data directory: $HOME/.config/chromium. In my case, the Chromium data that I wanted to keep was still in its old/usual place, since I had only used the snap for about five minutes.

That’s it. I hope it helps someone. If it damages your system, steals your bike, runs off with your boyfriend, or does something else that you don’t like, then I’m sorry, but it’s still your own responsibility.

Good luck!

This PPA seems to work great for this purpose: https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev It’s the dev branch, but besides that, it’s perfect.

sudo snap remove chromium    
sudo apt purge snapd    
rm -rf ~/snap

add repo

sudo add-apt-repository ppa:chromium-team/dev

change eoan to disco in /etc/apt/sources.list.d/chromium-team-dev.list

if file not exist or empty then paste that:

deb http://ppa.launchpad.net/chromium-team/dev/ubuntu disco main
deb-src http://ppa.launchpad.net/chromium-team/dev/ubuntu disco main

then update

sudo apt update


apt policy chromium-browser


sudo apt install chromium-browser

Manually copy the required packages from the 19.04 distribution and install them with dpkg.

apt purge snapd
curl -OO http://ftp.ubuntu.com/ubuntu/ubuntu/pool/universe/c/chromium-browser/{chromium-browser_79.0.3945.79-0ubuntu0.19.04.3_amd64.deb,chromium-codecs-ffmpeg-extra_79.0.3945.79-0ubuntu0.19.04.3_amd64.deb}
dpkg -i chromium-codecs-ffmpeg-extra_79.0.3945.79-0ubuntu0.19.04.3_amd64.deb chromium-browser_79.0.3945.79-0ubuntu0.19.04.3_amd64.deb
apt-mark hold chromium-browser chromium-codecs-ffmpeg-extra snapd

Edit: I just realized that I could use Pinning to which ʇsәɹoɈ referred above in relation to the debian repo. I will get back to this when I have time to experiment.

I have nothing against snap in theory, but spamming my mounts, processes, and filesystem is just too darn much. I only used it for one thing (the micro editor) before chromium was pushed on me as well. (And not needed for micro anymore either.)

Remove snap*, and prevent its return:

sudo apt remove --purge snapd -y    # may take a while
killall snap snapd                  # probably not necessary

sudo rm -rf /snap /var/cache/snapd/ # buh-bye
sudo apt-mark hold snap snapd       # prevent reinstall

Install chromium, dev or beta:

# sudo add-apt-repository ppa:chromium-team/dev
sudo add-apt-repository ppa:saiarcot895/chromium-beta
# sudo apt update                   # if it didn't already
sudo apt install chromium-browser

Micro editor – before < 20.04 Focal

# install it from snap beforehand or compile, then copy locally:
cp micro ~/bin

Micro editor – after >= 20.04 Focal

sudo apt install micro

Similar to forest’s example above i did the following:

# first add the beta repo, the stable isn't possible as it doesn't get updated
sudo add-apt-repository ppa:chromium-team/beta

# now edit the file, changing the reference to disco, instead of eoan:
sudo nano /etc/apt/sources.list.d/chromium-team-ubuntu-stable-eoan.list
    deb http://ppa.launchpad.net/chromium-team/beta/ubuntu disco main

# Now update the repos:
sudo apt update

Now pin the repository order:
sudo nano /etc/apt/preferences.d/chromium

    Explanation: Disallow installing chromium from ubuntu repo.
    Package: chromium*
    Pin: origin "*.ubuntu.com"
    Pin-Priority: 1
    Explanation: Allow installing chromium from launchpad repo.
    Package: chromium*
    Pin: origin "ppa.launchpad.net"
    Pin-Priority: 100

# Check which version is to be installed:
apt policy chromium-browser

# Now we can install chromium (the extra codecs resolve playback issues):
sudo apt install chromium-browser chromium-codecs-ffmpeg-extra

  • Download Google Chrome

  • Compile Google Chromium from source

  • Find a PPA or deb package file that a third party has provided.

Google releases a new major version of Chromium every six weeks, with typically several minor versions to address security vulnerabilities in between. Every new stable version has to be built for each supported Ubuntu release − 16.04, 18.04, 19.04 and the upcoming 19.10 − and for all supported architectures (amd64, i386, armhf, arm64).

Additionally, ensuring Chromium even builds (let alone runs) on older releases such as 16.04 can be challenging, as the upstream project often uses new compiler features that are not available on older releases.

In contrast, a snap needs to be built only once per architecture, and will run on all systems that support snapd. This covers all supported Ubuntu releases including 14.04 with Extended Security Maintenance (ESM), as well as other distributions like Debian, Fedora, Mint, and Manjaro.


You can use APT to add the repository for Chromium. Then you won’t need snapd at all.

sudo add-apt-repository ppa:chromium-team/stable
sudo apt-get update
sudo apt install chromium

Tagged : / /

Ubuntu HowTo: Filtered audio from OBS as a virtual audio input for video conference

Original Source Link

I am trying to make conference calls with filtered obs video and audio as inputs. The video part I could do with v4l2loopback and obs-v4l2sink. How can I make the filtered audio from OBS as an input to video conferences in platforms such as Bigbluebutton, Jitsi, Google meet, etc. I saw virtual audio cable as a solution in windows and a forum post explains adding virtual audio devices using jack in Ubuntu. Please help me out here.

Tagged : / / / /

Ubuntu HowTo: 19.10 – Wifi – Linksys AE2500-RM not recognized by system

Original Source Link

I see this has been asked before, but not for 19.10, and not for FIVE years.

Linksys AE2500-RM wi fi adapter not even popping up on my Wi Fi Settings when I plug it in.

In five years, has there been a better solution than XP drivers to make this work?

EDIT: lsusb output:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver 
Bus 002 Device 002: ID 2516:0004 Cooler Master Co., Ltd. Storm QuickFire Rapid Mechanical Keyboard 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub  

EDIT 2: removed the devide from it’s USB port and plugged it into a different port, reran the command and got the following:

Bus 001 Device 008: ID 13b1:003a Linksys AE2500 802.11abgn Wireless Adapter [Broadcom BCM43236]

There is no known native Linux driver for your 13b1:003a device.

Drivers are typically developed either directly by or in conjuntion with the device chipset manufacturer, in this case, Broadcom. They have provided no driver for this device nor any of the very few other Broadcom USB devices.

The alternative used to be to use Windows XP driver files and the ndiswrapper mechanism. However, ndiswrapper is poorly supported and hasn’t worked properly on any recent Ubuntu version for many years.

The direct answer to your question, “In five years, has there been a better solution than XP drivers to make this work?” is that there is no solution at all, including ndiswrapper, to make this work.

I suggest that you purchase another fully supported USB wireless device.

Tagged : / / /

Ubuntu HowTo: How can I install the package python-uniconverter under ubuntu 19.10?

Original Source Link

I’m trying to do a plot with inkscape and if I copy the image with ctrl + c to another program, I get the error message that python-uniconverter is missing.

Further, I’m unable to install it with apt-get install python-uniconverter because it seems that the package is missing.

Do you know the procedure to install this missing package?

Thank you!

You can download this package manually from https://packages.ubuntu.com/xenial/python-uniconvertor and install with following commands:

cd ~/Downloads
wget http://security.ubuntu.com/ubuntu/pool/universe/p/pillow/python-imaging_3.1.2-0ubuntu1.3_all.deb 
sudo apt install ./python-imaging_3.1.2-0ubuntu1.3_all.deb 

Installing on Ubuntu 20.04

To install uniconvertor 1.1.5-4 you have to install additional the python-report-accel package. These packages are also necessary to build inkscape 1.0 with

wget http://launchpadlibrarian.net/306203180/python-uniconvertor_1.1.5-4_amd64.deb  http://launchpadlibrarian.net/303745119/python-imaging_4.0.0-4_all.deb  http://launchpadlibrarian.net/469960854/python3-reportlab_3.5.34-1ubuntu1_all.deb   http://launchpadlibrarian.net/469960848/python-reportlab-doc_3.5.34-1ubuntu1_all.deb

and install with

sudo apt install ./python-uniconvertor_1.1.5-4_amd64.deb ./python-imaging_4.0.0-4_all.deb ./python3-reportlab_3.5.34-1ubuntu1_all.deb ./python-reportlab-doc_3.5.34-1ubuntu1_all.deb

The package python-reportlab-doc provides pdf/html docus.

Tagged : / / /

Ubuntu HowTo: Ubuntu 19.10 / 20.04 webcam crashing

Original Source Link

This is a follow up of this question: Merlin U740 USB 2.0 camera not working

Basically I have Merlin U740 USB 2.0 camera. I managed to make it work on Ubuntu 18.04 and it was working well until I upgraded to 19.10. A subsequent upgrade to 20.04 didn’t make any difference and now the camera doesn’t work.

It’s recognised by the system and starts in Zoom, Slack and Cheese only to fail a few seconds later, causing Zoom to freeze / become unresponsive for a moment (up to 30s, other apps seem to handle it better). I tried all the USB ports available on my PC and it made no difference.

I ran the usual commands and here are the results:

lsmod | grep video

uvcvideo               98304  0
videobuf2_vmalloc      20480  1 uvcvideo
videobuf2_memops       20480  1 videobuf2_vmalloc
videobuf2_v4l2         24576  1 uvcvideo
videobuf2_common       49152  2 videobuf2_v4l2,uvcvideo
videodev              225280  3 videobuf2_v4l2,uvcvideo,videobuf2_common
mc                     53248  5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 010: ID 1410:1410 Novatel Wireless Merlin U740 (non-Vodafone)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dmesg -H

[May26 08:07] usb 3-4: USB disconnect, device number 2
[  +0.001971] uvcvideo: Failed to resubmit video URB (-19).
[  +0.003994] uvcvideo: Failed to resubmit video URB (-19).
[  +0.004001] uvcvideo: Failed to resubmit video URB (-19).
[  +0.003998] uvcvideo: Failed to resubmit video URB (-19).
[  +0.004001] uvcvideo: Failed to resubmit video URB (-19).
[  +0.334387] usb 3-4: new high-speed USB device number 9 using xhci_hcd
[  +0.113622] usb 3-4: New USB device found, idVendor=1410, idProduct=1410, bcdDevice= 0.00
[  +0.000003] usb 3-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[  +0.000001] usb 3-4: Product: USB 2.0 Camera
[  +0.000001] usb 3-4: Manufacturer: Sonix Technology Co., Ltd.
[  +0.010509] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (1410:1410)
[  +0.025696] uvcvideo 3-4:1.0: Entity type for entity Extension 4 was not initialized!
[  +0.000002] uvcvideo 3-4:1.0: Entity type for entity Processing 3 was not initialized!
[  +0.000001] uvcvideo 3-4:1.0: Entity type for entity Camera 1 was not initialized!
[  +0.000059] input: USB 2.0 Camera: SD webcam 5160 as /devices/pci0000:00/0000:00:08.1/0000:09:00.3/usb3/3-4/3-4:1.0/input/input31
[  +0.013231] usb 3-4: 3:1: cannot get freq at ep 0x84
[  +0.022373] usb 3-4: USB disconnect, device number 9
[  +0.342659] usb 3-4: new high-speed USB device number 10 using xhci_hcd
[  +0.118345] usb 3-4: New USB device found, idVendor=1410, idProduct=1410, bcdDevice= 0.00
[  +0.000002] usb 3-4: New USB device strings: Mfr=2, Product=1, SerialNumber=0
[  +0.000001] usb 3-4: Product: USB 2.0 Camera
[  +0.000002] usb 3-4: Manufacturer: Sonix Technology Co., Ltd.
[  +0.009629] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (1410:1410)
[  +0.025813] uvcvideo 3-4:1.0: Entity type for entity Extension 4 was not initialized!
[  +0.000002] uvcvideo 3-4:1.0: Entity type for entity Processing 3 was not initialized!
[  +0.000001] uvcvideo 3-4:1.0: Entity type for entity Camera 1 was not initialized!
[  +0.000058] input: USB 2.0 Camera: SD webcam 5160 as /devices/pci0000:00/0000:00:08.1/0000:09:00.3/usb3/3-4/3-4:1.0/input/input32
[  +0.013238] usb 3-4: 3:1: cannot get freq at ep 0x84
[  +0.203878] usb 3-4: 3:1: cannot get freq at ep 0x84
[  +0.012130] usb 3-4: 3:1: cannot get freq at ep 0x84

The camera doesn’t seem damaged in any way, but maybe there’s something wrong with the hardware itself?

I have Ubuntu 19.10 and faced this issue several days ago too. The reason is updating from 5.3.0-53 kernel to 5.3.0-55. As a workaround, you can choose 53 version in GRUB.
For 20.04 kernel version 5.6.15 should work: Webcam stopped working after recent kernel update

Tagged : / / /

Ubuntu HowTo: AC1200 Wireless adapter in Ubuntu 19.10

Original Source Link

I did the following in a terminal to get a AC1200 Linksys Wireless adapter to work on my Ubuntu 19.10 install:

sudo apt-get install linux-headers-$(uname -r) linux-headers-generic build-essential git
git clone https://github.com/abperiasamy/rtl8812AU_8821AU_linux
cd rtl8812AU_8821AU_linux
sudo make install

This process went through without errors and install was completed. However, my wireless USB adapter still doesn’t work. I ran lsusb in terminal and my wireless adapter was listed as

Bus 002 Device 004: ID 13b1:003f Linksys WUSB6300 802.11a/b/g/n/ac Wireless Adapter [Realtek RTL8812AU]

I then ran the following, and it simply returned the command line prompt

modinfo 8812au | egrep -i 'versi|filen|003f'
sudo modprobe -v 8812au
iwlist chan

When I opened my network setting for WiFi, I received the following:

No WiFi Adapter found
Make sure you have a wifi adapter plugged in and turned on

I also tried to get it to work by installing ndiswrapper, but that didn’t work either. I have researched this and have tried numerous things I found, but nothing seems to work. I know this has been answered before, but the answers all indicate the above procedure. Any help is appreciated as I am new to Ubuntu, but have run Red Hat linux prior to its shifting to Fedora.

For Linksys WUSB6300 do this:

Make sure USB wireless device not inserted

  1. Update the system:
    $ sudo apt update

  2. Install required packages:
    $ sudo apt install git && build-essential

  3. Download the driver:
    $ sudo git clone https://github.com/gnab/rtl8812au

  4. Go to the directory:
    $ cd rtl8812au

  5. Do the next commands consecutively:
    $ sudo make clean
    $ sudo make
    $ sudo make uninstall
    $ sudo make install

Reboot and insert USB wireless stick

-Persists reboots
-Works with dlink dwa-182 and linksys WUSB6300

Tagged : / /

Ubuntu HowTo: WUSB6300 wireless not working

Original Source Link

I’ve been unsuccessful getting the WUSB6300 to work on Ubuntu 19.10. I’ve executed the instructions at this website

My output from lsusb is
Bus 002 Device 009: ID 13b1:003f Linksys WUSB6300 802.11a/b/g/n/ac Wireless Adapter [Realtek RTL8812AU]

My output from lsmod shows the 8812au listed. My output from lshw -C network doesn’t show the WSUSB6300, 8812au, or any type of wireless adapter, only the Realtek PCI Express Gigabit Ethernet Controller that’s integral to the motherboard.

What am I missing? I can’t help thinking that there’s something I’m not doing that would enable this dongle to be recognized and used.

Thanks in advance!

modinfo 8812au |grep 003F


dmesg | grep -i rtl

[ 1.504926] r8169 0000:07:00.0 eth0: RTL8168evl/8111evl, 50:e5:49:b8:a6:98, XID 2c9, IRQ 34
[ 6.978205] RTL871X: module init start
[ 6.978206] RTL871X: rtl8812au v4.3.8_12175.20140902
[ 6.978206] RTL871X: build time: Apr 13 2020 13:46:32
[ 7.094661] usbcore: registered new interface driver rtl8812au
[ 7.094662] RTL871X: module init ret=0
[ 7.190684] RTL871X: module init start
[ 7.190685] RTL871X: rtl8812au v4.3.14_13455.20150212_BTCOEX20150128-51
[ 7.190685] RTL871X: rtl8812au BT-Coex version = BTCOEX20150128-51
[ 7.190693] Error: Driver ‘rtl8812au’ is already registered, aborting…
[ 7.190697] RTL871X: module init ret=-16
[ 17.308006] RTL8211E Gigabit Ethernet r8169-700:00: attached PHY driver
[RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-700:00, irq=IGNORE)

sudo updatedb && locate 8812au.ko

/usr/bin/find: ‘/run/user/1000/doc’: Permission denied
/usr/bin/find: ‘/run/user/1000/gvfs’: Permission denied

sudo dkms status

rtl8812au,, 5.3.0-46-generic, x86_64: installed
rtl8812AU_8821AU_linux, 1.0, 5.3.0-46-generic, x86_64: installed

sudo modprobe -r 8812au && sudo modprobe rtl8812au

Module Size Used by
rtl8812au 1347584 0

Disconnected wired connection, removed/reinserted usb dongle, no change to network behavior, i.e. no wireless connection to local wireless router.

sudo modprobe -r rtl8812au && sudo modprobe 88au

Module Size Used by
8812au 1290240 0
cfg80211 712704 1 8812au


lo no wireless extensions.
enp7s0 no wireless extensions.

sudo dkms status

rtl8812au,, 5.3.0-46-generic, x86_64: installed
rtl8812AU_8821AU_linux, 1.0, 5.3.0-46-generic, x86_64: installed

Apologies, I should clarify..this “radio button” is selectable for enable & disable. I’ve done both, with no difference in connection, i.e. no wireless established after either enabling or disabling

I had the same problem with 18.04 and Linksys WUSB6300.

These are the steps I used to get up and persist reboots:

Install the tools:
# sudo apt install wireless-tools && sudo apt install wpasupplicant

Install the driver:
# sudo apt install rtl8812au-dkms

Now open.yamlfile in netplan for editing:
# sudo vi /etc/netplan/50-cloud-init.yaml

Replace wlan0 with the name of your adapter, do ifconfig to find it.

Neplan file should look similar to this:

version: 2
renderer: networkd
            addresses: []
            dhcp4: true
            optional: true
            addresses: []
            dhcp4: true
            dhcp6: true
                    password: "my_password"

Now generate and debug:
# sudo netplan --debug generate

Apply the configuration:
# sudo netplan apply

Now remove ethernet wire and reboot:
# sudo reboot

My sudo dkms status output:
rtl8812au,, 4.15.0-96-generic, x86_64: installed
And your output has 2 versions of drivers installed. You must uninstall rtl8812AU_8821AU.

Connection and ip established after netplan generate. Omitting optional: true for ethernets will prevent persistence upon reboots.


Above was for Ubuntu Server, here is Ubuntu Desktop 18.04 thru 20.04:

Update the system:
sudo apt update

Install required packages:
sudo apt install git && build-essential

Download the driver:
sudo git clone https://github.com/gnab/rtl8812au

Go to the directory:
cd rtl8812au

Do the next commands consecutively:
sudo make clean
sudo make
sudo make uninstall
sudo install

Reboot and insert USB wireless stick

-Persists reboots
-Works for WUSB6300

Tagged : / / /