[Bug 1928984] [NEW] keyboard layout return back to US during the install process
Public bug reported: When installing the 21.04 version on an Oracle VirtualBox, you can choose the keyboard setting following your country. What is expected: the chosen settings will remain during the whole install process. What happened: At the moment you are entering the login_name and the login_password, the keyboard revert discreetly back to US layout and will once again revert to chosen country setting after the reboot. Resulting problem: you will type the login/password with a different keyboard layout that the one you had when you entered it during the install process. IMPORTANT: This is a regression as the exact same problem was already known with 20.04 and was solved. See : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928984 Title: keyboard layout return back to US during the install process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899135] [NEW] Checkbox not visible when install Dutch (Nederlands) on 800*600 Oracle virtual Box
Public bug reported: Hi, If you try to install Ubuntu on an Oracle VirtualBox machine in Dutch (Nederlands), the checkboxes (quit) (back) (continue) cannot be seen (=out of visible screen) witch is 800*600. The check boxes are on a usable/seen place in French and English, same default screen 800*600. I didn't check other languages so far. I noticed the same problem with guest in Ubuntu versions 18.04.5 LTS, 20.04 and in groovy-desktop-amd64 as of Oct 8, 2020. So, it is not a regression. N.B.: in VirtualBox, the OS installation screen is 800*600. I suspect that the problem will be the same with an install on a bare machine where the screen is 800*600 only but I have no way to test it now. Host : Ubuntu 18.04 with daily updates as of Oct 8, 2020 8 Gb Ram Oracle VirtualBox Version 6.1.12 r139181 (Qt5.9.5) The VM is "vanilla" but for the RAM I upgrade from 1 to 3 or 4 Gb Ram and the size of the virtual disk upgraded from 10 to 20 Gb. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899135 Title: Checkbox not visible when install Dutch (Nederlands) on 800*600 Oracle virtual Box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1899135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 975803] Re: ubuntu-defaults-builder: setting language automatically results in non-standard keyboard layout
Hi, I think it is solved. See https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062 I made an install in Dutch (Nederlands) with the current groovy-desktop amd64 and didn't find the problem anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/975803 Title: ubuntu-defaults-builder: setting language automatically results in non-standard keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/975803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
Hi Lukasz I checked also in Dutch (Nederlands) and it is also solved. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
@sil2100 Problem solved :-) I check the daily-live I download from the indicated address and made exactly the same install (Oracle VM running on a Ubuntu 18.04, vanilla config of the VM) that failed since 2020-04-27 and this time, at the moment of introducing the new login and password, the keyboard was in Azerty Belgian aka Belgian Keyboard as asked. To be sure, I'll check with some other languages and if it failed, I'll write it here but I'm 99% confident that all will be OK. You are welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
I checked with the last Groovy I found 45 minutes ago and the bug is still there in French-Belgian language/keyboard layout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
And still ther in German (Deutsch) also -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
@gunnarhj @dag-e @xnox gave the adress for ISO "Groovy images are available from http://cdimage.ubuntu.com/daily-live/pending/ " -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
This bug is a regression: with older version of Ubuntu, such as 18.04 LTS, during the install process, you get your selected keyboard layout all along during the install process. As I said before, this bug makes that, if you don't realize that the keyboard layout fell to US, it might happen that at the place where you choose your password, where the letters appears as "*", you use one or more characters where US and your selected keyboard layouts differs without realizing it. In that case, at the reboot (where your keyboard selection is correctly activated), you will receive the message "invalid password" on and on. If you don't realize where the bug is, it is possible that you choose to reinstall Ubuntu again and again until you choose a password where the 2 keyboard layout don't differ. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
@xnox Okay, I double check on base of your remarks and I got deeper in the tests and eliminate the other bugs in this report. Thank you for helping to reformulate and motivate me to goes on :-) I am more precise now and I think I may say it is exactly the same bug in all 3 languages I checked. The selected keyboard layout is NOT recognize at any point during the install process, period. I check 3 keyboards layout (and languages): Norwegian, French and Deutsch (aka German) on my VM. In other words: at no point of the install but the moment of the selection itself, you get the keyboard layout you selected. You got a 82 US layout in the first version of 20.04, with "Groovie" it's a 102 US layout (with numeric keypad). A little progress, so. The original bug description said: "During a fresh install of Ubuntu 20.04, selecting Norwegian keyboard is provided and keys are responding correctly at that stage. But later when entering user information the keyboard setting is wrong." Word for word, the same remark applies except, as I said before, that the problem appears sooner, too. It may help to trace the bug that some problem exist in US layout too: the keyboard layout fall to 88 touch during the install process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
Worse : in an english speaking install with a AZERTY Belgian keyboard, we are back to the 88 touch US design (no numeric pad) at the same moment : introduction of name+password. I insist : 88 US Keyb. It is different in a french speaking install were the Keyboard is a 102 touch US Keyb (numeric pad work). And for the third time, it still cannot install the boot loader. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
Another problem appears while installing Groovy as of now, FR speaking version, on an Oracle VM machine, the installer cannot install the bootloader (FR: "chargeur d'amorçage") with the following message (in french) "Désolé, une erreur s'est produite. Il n'a pas été possible d'installer le chargeur d'amorçage à l'emplacement indiqué." and propose to install it on another media. I tried it twice on 2 different virtual disks but on the same physical Solid-State Disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
I checked the Groovy version proposed by @Dimitri John Ledkov (xnox) ab NO progress: still a US in place of the chosen localized keyboard at the introduction of the name+password. Progress: 102 touch in place of 88 touch keyboard (numeric keyboard worked) at that moment I checked the Groovy version proposed by @Dimitri John Ledkov with the same configuration : VM Oracle. I went directly to the minimal install, without trying the OS before as described by @coeur-noir, and the "AZERTY Belgian Keyb" configuration is recognize as such but at the moment of the introduction of name+password. There, it is still a 102 US Keyboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: Incorrect keyboard layout for selecting username and password during install of 20.04
I installed a fresh Ubuntu 20.04 LTS on an Oracle VM. During the installation, I choosed “french language” and “Belgian keyboard”. Later, the installer asked me to type my name and password and THERE the keyboard is in Qwerty with no support of the numeric pad (Qwerty 88) I checked it with two different install to be sure of the bug. And with a German keyboard, same problem. After reboot, it returns back in Keyb BE as defined. Potential login problem : If your name doesn’t contain any letter as “z-q-a-w or m” nor a numeric AND neither does your password, you are fine. But if only your password does, you’re fried because you cannot detect the problem during the install and at the next restart : bam ! “your password is invalid”. The work around is to type the password with the “Qwerty 88” design in your head, a design easy to find on internet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: Incorrect keyboard layout for selecting username and password during install of 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
To be closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
Problem does NOT appear any more : tests use new version of snap or using Ubuntu 18.10 STABLE in place of "pre version" used 15 month ago. Case can be closed from my point of view. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
Bug doesn't appear on new version of Ubuntu. I don't use the 18.10 in my test. I will make a new/fresh install with this peculiar version (18.10) in a few minutes and see if it still happen when installing the package via "sudo apt install snapd" as described 14 month ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
** Changed in: snapd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
Due to a manipulation error, I losted the original faulty french- speaking install. I repeated twice an English-speaking install with the same error message while updating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781692] Re: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
journalctl -xe -- Subject: Unit NetworkManager-dispatcher.service has finished start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit NetworkManager-dispatcher.service has finished starting up. -- -- The start-up result is RESULT. Jul 15 19:21:10 VB-Ubu-64-Alpha dbus-daemon[723]: [session uid=1000 pid=723] Act Jul 15 19:21:10 VB-Ubu-64-Alpha dbus-daemon[723]: [session uid=1000 pid=723] Act Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-DISKIO-MIB Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-EXTEN Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in NET-SNMP-AGENT Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha colord[1201]: Cannot adopt OID in UCD-SNMP-MIB: Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) config/ud Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) VirtualBo Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) Using inp Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) systemd-l Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) VirtualBo Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) Option "D Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) Option "_ Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) event5 - Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) event5 - Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) event5 - Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) Option "c Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) XINPUT: A Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) Option "A Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) VirtualBo Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) VirtualBo Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (**) VirtualBo Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) event5 - Jul 15 19:20:42 VB-Ubu-64-Alpha /usr/lib/gdm3/gdm-x-session[695]: (II) event5 - Jul 15 19:20:45 VB-Ubu-64-Alpha
[Bug 1781692] [NEW] Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB
Public bug reported: sudo apt install snapd [sudo] Mot de passe de jdv : Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les NOUVEAUX paquets suivants seront installés : snapd 0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour. Il est nécessaire de prendre 12,4 Mo dans les archives. Après cette opération, 57,8 Mo d'espace disque supplémentaires seront utilisés. Réception de:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 snapd amd64 2.34~pre1+18.10.2 [12,4 MB] 12,4 Mo réceptionnés en 5s (2.507 ko/s) Sélection du paquet snapd précédemment désélectionné. (Lecture de la base de données... 116074 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../snapd_2.34~pre1+18.10.2_amd64.deb ... Dépaquetage de snapd (2.34~pre1+18.10.2) ... Paramétrage de snapd (2.34~pre1+18.10.2) ... Installation de la nouvelle version du fichier de configuration /etc/apparmor.d/usr.lib.snapd.snap-confine.real ... Installation de la nouvelle version du fichier de configuration /etc/profile.d/apps-bin-path.sh ... Created symlink /etc/systemd/system/multi-user.target.wants/snapd.apparmor.service → /lib/systemd/system/snapd.apparmor.service. snapd.snap-repair.service is a disabled or a static unit, not starting it. A dependency job for snapd.apparmor.service failed. See 'journalctl -xe' for details. Progression : [ 67%] [###...] 1.1) Description: Ubuntu Cosmic Cuttlefish (development branch) Release:18.10 1.2) Running on Oracle VM VirtualBox 5.2.12 (122591) Qt 5.6.1 2) snapd_2.34~pre1+18.10.2_amd64.deb 3) I expected a snapd install 4) The installation is locked + Corruption of install means no more install of any new program or updates. Have to reinstall the whole Ubuntu. N.B. I repeated the problem twice, each on new installations. If needed to help resolving by collecting extra : a) an image of the present situation is still on my VB b) I can make a fresh install with suggestions to work around in minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.34~pre1+18.10.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 14 07:47:53 2018 InstallationDate: Installed on 2018-07-07 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180630) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781692 Title: Ubuntu corrupted by installing snapd - complete Ubuntu re-installation needed on VB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1781692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
