Errors in Ubuntu 18.04 on Windows 10

Question

Hello,

I tried to migrate from WSL Ubuntu 16.04 to Ubuntu 18.04 but it did'nt work.

Then I tried to uninstall Ubuntu 16.04 but I got error 0x80070002

I finally succedeed in installing Ubuntu 18.04 but 

I couldn't choose the same username as before, the majuscule in first position caused an error

adduser: Please enter a username matching the regular expression configured

via the NAME_REGEX[_SYSTEM} configuration variable. Use the `--force-badname'

option to relax this check or reconfigure NAME_REGEX.

Now, I have errors in Ubuntu 18.04.

Example :

command sudo apt-get upgrade

Result

[code]Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

The following package was automatically installed and is no longer required:

  libfreetype6

Use 'sudo apt autoremove' to remove it.

The following packages will be upgraded:

  ebtables

1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

22 not fully installed or removed.

Need to get 0 B/79.9 kB of archives.

After this operation, 0 B of additional disk space will be used.

Do you want to continue? [Y/n] y

(Reading database ... 28478 files and directories currently installed.)

Preparing to unpack .../ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb ...

invoke-rc.d: could not determine current runlevel

 * Error: insufficient privileges to access the ebtables rulesets.

invoke-rc.d: initscript ebtables, action "stop" failed.

dpkg: warning: old ebtables package pre-removal script subprocess returned error exit status 1

dpkg: trying script from the new package instead ...

invoke-rc.d: could not determine current runlevel

 * Error: insufficient privileges to access the ebtables rulesets.

invoke-rc.d: initscript ebtables, action "stop" failed.

dpkg: error processing archive /var/cache/apt/archives/ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb (--unpack):

 new ebtables package pre-removal script subprocess returned error exit status 1

update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults

invoke-rc.d: could not determine current runlevel

Errors were encountered while processing:

 /var/cache/apt/archives/ebtables_2.0.10.4-3.5ubuntu2.18.04.1_amd64.deb

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

I have several PC to migrate from Ubuntu 16.04 tu Ubunto 18.04.

Questions :

How can I get rid of these errors ?

Why couldn't I choose a user name beginning with a capital letter as I did with Ubuntu 16.04 ?

How can I start fresh after removing everything from Ubuntu, code and data ?

How can I upgrade from Ubuntu 16.04 tu Ubuntu 18.04 and keep my user data ?

Thanks for your help.

Answer 1

Hi Patricia, 

I had the same problem, after upgrading to 18.04.   The problem is that there's a bug in the one of the ebtables support script, causing you to get the "insufficient privileges" script. 

Rather than edit the scripts that cause this problem, simply remove /sbin/ebtables and replace with a program that exits with a success error code, and prints nothing (ie.  /bin/true):

sudo cp -p  /bin/true /sbin/ebtables

sudo apt update -y

sudo apt upgrade -y

Notes: 

1. The trick is to install a "fake" /sbin/ebtables  that does nothing and exits with a success code value of 0 (zero).  That's what /bin/true does.
2. The "upgrade" does an uninstall of the old and install of the new, so your "fake" /sbin/ebtables will be installed with a real /sbin/ebtables.
3. The new ebtables is STILL broken, so you'll have to do the same thing when you

need to update ebtables again. 4. If you have absolutely no use for ebtables, remove it by doing:

    sudo apt remove ebtables -y ****before doing the "sudo apt upgrade -y"

Answer 2

Hello,

The problem is now solved.

No need for special commands.

Answer 3

Hi Patricia  - 

Just out of curiosity, how did you resolve the issue?

Answer 4

Hello,

The issue was resolved by developers, I had Nothing to do.

https://forum.ubuntu-fr.org/viewtopic.php?pid=21925258

I just have still got the problem of capital letters forbidden in usernames

https://github.com/Microsoft/WSL/issues/3273

Hope it helps.

Answer 5

I did not understand the French site, but the problem still exists on my WSL running 18.04.

--Rasit