[Bug 1914053] Re: US intl. Deadkeys not working in some programs
Hi I'm experimenting a very analog trouble. I designed my own keyboard layout and my own .XCompose file to produce ancien greek characters such as α ά ὰ ὰ ᾴ ᾳ ἁ ᾁ ἀ ᾀ, … (I'm using 18.04 to type the present text). Ι've been using these keyboard and .XCompose file for several years now and they worked fine until I installed Ubuntu 20.04 on a new PC a few weaks ago. When I hit a dead key, a little circle may get displayed on the screen, however not systematically. This little circle disappears when I hit the desired key, and the cursor returns to its previous location. I'm very disapointed and ready to return to Ubuntu 18.04. Arbiel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914053 Title: US intl. Deadkeys not working in some programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1914053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] Re: [18.04] update-initramfs fails to generate correct initrd
This trouble arises when trying to update initramfs from the isofile (ubuntu-18.04.1-desktop-amd64.iso) as soon as ubiquity terminates the installation. update-initramfs succeeds when run from an installed instance of Ubuntu and after a chroot command, or, afterwards, from a running 18.04 system. This seems to point the bug to the isofile. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220724/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220726/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220714/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220720/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220715/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220723/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220725/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220718/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220722/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220719/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220716/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220717/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] Re: [18.04] update-initramfs fails to generate correct initrd
apport information ** Tags added: apport-collected ** Description changed: Hi I get many trouble in trying to generate a correct initrd.img for the following configuration clear lvm on /dev/sd4 partition (msdos) several logical volumes, some clear and some luks-encrypted / et /home on encrypted logical volumes, each with its own 512 byte binary key-file on removable device (USB stick) /boot et /usr on clear logical volumes I am still running 14.04 due to trouble with 16.04, maybe because I missed the introduction of the "initramfs" crypttab option. I dropped any investigation hoping for the trouble being solved with 18.04. This is not the case. I run into trouble as soon as I tried to update initrd.img with update- initramfs. victor-odos goes to /, victor-oikia goes to /home I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev 1/ with crypttab referencing my binary key-files victor-odos /dev/mapper/victor-odos_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs victor-oikia /dev/mapper/victor-oikia_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs I join two files : /dev/stdout sent to .log and /dev/stderr to .err 2/ with no key-files victor-odos /dev/mapper/victor-odos_l none luks,initramfs victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs I don't know how to bypass this issue When this has been solved, I intend to detach luks headers. How to code crypttab as I don't know the operational file hierarchy inside initrd ? + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu 2114 F pulseaudio + CasperVersion: 1.394 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: Dell Inc. Vostro 3550 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper iso-scan/filename=/amorces/username-18.04.1-desktop-amd64.iso quiet splash --- + ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-29-generic N/A + linux-backports-modules-4.15.0-29-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-29-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/18/2014 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A12 + dmi.board.vendor: Dell Inc. + dmi.board.version: A12 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: + dmi.product.name: Vostro 3550 + dmi.product.version: Not Specified + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220713/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1806914/+attachment/5220721/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806914] [NEW] [18.04] update-initramfs fails to generate correct initrd
Public bug reported: Hi I get many trouble in trying to generate a correct initrd.img for the following configuration clear lvm on /dev/sd4 partition (msdos) several logical volumes, some clear and some luks-encrypted / et /home on encrypted logical volumes, each with its own 512 byte binary key-file on removable device (USB stick) /boot et /usr on clear logical volumes I am still running 14.04 due to trouble with 16.04, maybe because I missed the introduction of the "initramfs" crypttab option. I dropped any investigation hoping for the trouble being solved with 18.04. This is not the case. I run into trouble as soon as I tried to update initrd.img with update- initramfs. victor-odos goes to /, victor-oikia goes to /home I rewrote passdev and stored it in /lib/cryptsetup/bash/passdev 1/ with crypttab referencing my binary key-files victor-odos /dev/mapper/victor-odos_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-odos:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs victor-oikia /dev/mapper/victor-oikia_l /dev/disk/by-uuid/4146dfad-26f0-4aec-99c3-8ab00c3e4297:/.ckf/victor-oikia:1 luks,keyscript=/lib/cryptsetup/bash/passdev,initramfs I join two files : /dev/stdout sent to .log and /dev/stderr to .err 2/ with no key-files victor-odos /dev/mapper/victor-odos_l none luks,initramfs victor-oikia /dev/mapper/victor-oikia_l none luks,initramfs I don't know how to bypass this issue When this has been solved, I intend to detach luks headers. How to code crypttab as I don't know the operational file hierarchy inside initrd ? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic cryptsetup crypttab update-initramfs ** Attachment added: "key-files.updt.err" https://bugs.launchpad.net/bugs/1806914/+attachment/5219452/+files/key-files.updt.err -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806914 Title: [18.04] update-initramfs fails to generate correct initrd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734430] Re: isodevice unable to unmount when using loopback
In my previous post, change "add a terminal" by "open a terminal" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734430 Title: isodevice unable to unmount when using loopback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1734430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734430] Re: isodevice unable to unmount when using loopback
This bug affects previous Ubuntu releases. To circumvent this issue, choose "Try Ubuntu", add a terminal and unmount /isodevice sudo umount -lfd /isodevice -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734430 Title: isodevice unable to unmount when using loopback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1734430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759674] Re: Xenial fails to boot because of cryptsetup keyfiles.
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+attachment/5094027/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759674 Title: Xenial fails to boot because of cryptsetup keyfiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759674] Re: Xenial fails to boot because of cryptsetup keyfiles.
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+attachment/5094026/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759674 Title: Xenial fails to boot because of cryptsetup keyfiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759674] Re: Xenial fails to boot because of cryptsetup keyfiles.
** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+attachment/5094028/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759674 Title: Xenial fails to boot because of cryptsetup keyfiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759674] [NEW] Xenial fails to boot because of cryptsetup keyfiles.
Public bug reported: I always install fresh configurations apart from my working system, on logical volumes of my "victor" logical group. I always use four logical volumes per distribution : boot (clear), root (crypted), home (crypted) and usr (clear), naming them differently from a distribution to another one. Xenial logical volumes are archos (boot), odos (root), oikia (home) and trophe (usr). Only odos and oikia are concerned. To avoid typing cryptsetup keys, I rely on keyfiles. It turns out that, for reasons outside of this report, I did install grub on removable USB keys, and did not alter Windows booting procedure on my hard disk. I also record my key-files on that same device. This means that my USB key is always connected to my PC when I boot Ubuntu. My working system is Ubuntu Trusty with the 3.13.0.106-generic kernel. It does not suffer the bug I'm reporting (I discarted 3.13.0.108-generic for a reason I forgot, but it also works, as regards to the present report). Xenial does not boot, apparently because it hangs waiting for the USB device. The present bug is then a regression bug. I attached the output of "journalctl -xb" in which one can read (I translated french sentences in brakets[]) ### -- L'unité (unit) boot.mount a commencé à démarrer. [unit boot.mount started] mars 25 12:22:37 remi-Vostro-3550 systemd-udevd[666]: Process '/sbin/crda' failed with exit code 249. mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounting ext2 file system using the ext4 subsystem mars 25 12:22:37 remi-Vostro-3550 kernel: EXT4-fs (dm-12): mounted filesystem without journal. Opts: (null) mars 25 12:22:37 remi-Vostro-3550 systemd[1]: Mounted /boot. -- Subject: L'unité (unit) boot.mount a terminé son démarrage [unit boot.mount has finished] -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) boot.mount a terminé son démarrage, avec le résultat done.[unit boot.mount has finished and reported done] mars 25 12:23:58 remi-Vostro-3550 systemd[1]: dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device: Job dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device/start timed out. mars 25 12:23:58 remi-Vostro-3550 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device. -- Subject: L'unité (unit) dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-.ckf-victor\x2dodos:1.device a échoué [unit dev-disk…-victor\x2dodos:1.device failed] -- Defined-By: systemd For testing purposes, I also installed a Xenial-B on a clear logical volume. I have being able, after boot of Xenial-B, to "cryptdisks_start" crypted logical volumes defined with the crypttab's "noauto" option. Removing the "noauto" option, without mounting the corresponding volumes with fstab, did not prevent Xenial-B to boot, but the same message as the one I mentionned ealier, appeared into the "journalctl -xb" output. I also discovered that cryptdisks_start fails if the USB key happens to be mounted. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-106-generic 3.13.0-106.153 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remi 3564 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 28 22:15:20 2018 InstallationDate: Installed on 2014-05-30 (1397 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3550 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-106-generic root=/dev/mapper/victor-root ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-106-generic N/A linux-backports-modules-3.13.0-106-generic N/A linux-firmware 1.127.23 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht
[Bug 1758853] [NEW] ubiquity crashed when unable to run grub-install, which I don't want to run anyway
Public bug reported: When I install a new system, I do not want the boot process to be modified. So I generally ask grub to be installed in a location where it cannot be installed, to avoid my specific boot sequence to be modified. I run grub-mkconfig to update grub menu in the way I want it to be modified. Please, insert an option in ubiquity to dismiss grub's installation. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.6 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon Mar 26 10:54:29 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/amorce/ubuntu-16.04.4-desktop-amd64.iso quiet splash --- LiveMediaBuild: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.6 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758853 Title: ubiquity crashed when unable to run grub-install, which I don't want to run anyway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1758853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742145] [NEW] installation crashed when I went back due to /isodevice still mounted
Public bug reported: I always install from an iso file. Ubiquity doesn't know how to unmount this file, mounted on /isodevice. I forgot to do it by hand before asking for the imstallation after I input all necessary data. The crash occurred whem I clicked on the "back" botton". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Tue Jan 9 14:07:44 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/xubuntu.seed boot=casper iso-scan/filename=/amorces/xubuntu-16.04.3-desktop-amd64.iso quiet splash --- LiveMediaBuild: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 xenial xubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742145 Title: installation crashed when I went back due to /isodevice still mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1742145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737846] Re: bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command
Don't consider this as a bash bug. It's a misunderstanding by myself of the pipeline operation. Maybe a comment should be included in the reference manual to cleary explain that the last command may try to open for writing the file still open for reading by the first command, and that such a situation obviously fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737846 Title: bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1737846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737846] [NEW] bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command
Public bug reported: In a non-interactive bash session, redirecting the standard output to the file read by the pipeline's first command leads to random resuts : the redirection sometimes works, but generally the file is overwriten by an empty file. In an interactive session, the redirection works, which leads the user to look somewhere else to find a bug. However, when the last command is a user-writen function which simulates "cat", the resulting file is correct, as in an interactive session. Bash documentation does not prohibit such processing. Arbiel ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 23:51:22 2017 InstallationDate: Installed on 2014-05-30 (1292 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "error-report" https://bugs.launchpad.net/bugs/1737846/+attachment/5021868/+files/error-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737846 Title: bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1737846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658331] [NEW] virtual machines get damaged in a MultiAttach context
Public bug reported: Hi I first wrongly reported this bug under OpenStack, due to a misunderstanding of the bug reporting procedure. It received there # 1657726. I'm running VirtualBox Version 4.3.12 r93733. The Windows application I run accesses a single file, and is not able to handle concurrently the two files I have to manage. So I decided to create two VirtualBox virtual machines, one for each file. To be able to run the two virtual machines concurrently when I need access to both files, and to save disk space, I decided to use the multiattach option, as it fits my needs. In this context, the last virtual machine to be closed gets damaged after closure : hard disks description in the vbox file are removed. Instead of reading hard disk description gets The same damage keeps occurring until next reboot even if the relaunched machine remains the only running machine. I consider this to be a bug as section "5.4 Special image write modes" of the "Oracle VM VitualBox® User Manual version 5.1.14" (https://www.virtualbox.org/manual/UserManual.html) reads as follows §5 An image in multiattach mode can be attached to more than one virtual machine at the same time, even if these machines are running simultaneously. For each virtual machine to which such an image is attached, a differencing image is created. As a result, data that is written to such a virtual disk by one machine is not seen by the other machines to which the image is attached; each machine creates its own write history of the multiattach image. As long I'm concerned, I wrote a script to bypass this issue, so that there is no hurry for me for this issue to be fixed. However, other users may be in great difficulty to use the multiattach option. Arbiel ** Affects: virtualbox (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/1658331 Title: virtual machines get damaged in a MultiAttach context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1658331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652173] [NEW] wrong sha512 hash for boot-info-script_0.61-2.debian.tar.gz
Public bug reported: To my opinion, the right sha512 hash for boot-info- script_0.61-2.debian.tar.gz is 36e9876f c235-19fbcb53-529378ad-eb8c915d-52108f98-7a734f7d-31d8dcbd900a and not 36e9876f 00 c235 … ** Affects: boot-info-script (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/1652173 Title: wrong sha512 hash for boot-info-script_0.61-2.debian.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boot-info-script/+bug/1652173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525724] Re: boot hangs with more than 1 luks device in crypttab
I am using 14.04 with / and /home (both logical volumes) crypted and USB sticks holding my key files. In this configuration, the system boots. I intend to move to Xenial and installed it on other lv's with the same type of configuration. Boot hangs, and gets to the situation Karl Kastner wrote about. It turns out that the journal lists timeout for both lv's root : Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-lkf-victor-odos:1.device. and home : Timed out waiting for device dev-disk-by\x2duuid-4146dfad\x2d26f0\x2d4aec\x2d99c3\x2d8ab00c3e4297:-lkf-victor-oikia:1.device. The listed device is my usb stick. No way moving to Xenial if no solution to this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525724 Title: boot hangs with more than 1 luks device in crypttab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1525724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604595] [NEW] Ubiquity crashed after informing me grub could not been installed on a GPT device
Public bug reported: No further information ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Tue Jul 19 23:32:02 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/ubuntu-16.04-desktop-amd64.iso quiet splash --- LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604595 Title: Ubiquity crashed after informing me grub could not been installed on a GPT device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1604595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594903] [NEW] Ubuntu does not reset grubenv's recordfail
Public bug reported: This is a conceptual bug in the way it aims at the interface between grub2 and ubuntu. This situation arises when Ubuntu's /boot/grub/grubenv does not point to the same grubenv file as the one that is used by grub at booting time. To say it another way, let's suppose grub has been installed on a removable device with --boot-directory referring to a directory on the same removable device. As the contents of the /boot directory have no reason to remain in the file tree on a running system, the user is well entitled to include a line in /etc/fstab to mount any other partition on /boot, so as to free the port on which the booting device is connected. In which case, the system reset recordfail in an environment which is not the right one. At booting time, recordfail is then always true. ** Affects: grub2 (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/1594903 Title: Ubuntu does not reset grubenv's recordfail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1594903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561618] [NEW] package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symb
Public bug reported: My fstab file contains the mounting with the bind option of a /home/…/filename on the corresponding xkb/symbols/filename. I tried a reinstalling of the xkb packets and got the present error message. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Mar 24 16:15:07 2016 Dependencies: DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:xkb-data:2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr]:impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien croisé de périphéque invalide ErrorMessage: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien croisé de périphéque invalide InstallationDate: Installed on 2014-05-30 (663 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Vostro 3550 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-77-generic root=/dev/mapper/victor-root ro quiet splash nomdmonddf nomdmonisw RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: xkeyboard-config Title: package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien croisé de périphéque invalide UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/18/2014:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Mar 24 17:11:02 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. Error loading keymap /var/lib/xkb/server-17ADDC480211589580CCE86EE8D14EA1392425A2.xkm Error loading keymap /var/lib/xkb/server-59AA3993CA9ABEC7ED9221D97990DF3246549A14.xkm Error loading keymap /var/lib/xkb/server-17ADDC480211589580CCE86EE8D14EA1392425A2.xkm xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5539 vendor CMO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561618 Title: package xkb-data 2.10.1-1ubuntu1 [modified: usr/share/X11/xkb/symbols/gr] failed to install/upgrade: impossible de créer un lien symbolique de secours de « ./usr/share/X11/xkb/symbols/gr » avant d'installer une nouvelle version: Lien croisé de périphéque invalide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1561618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180685] Re: update-grub makes grub2 point on an incorrect UUID
Hi I run additional tests to find out that the issue is the sharing of the /boot partition with the two systems, Ubuntu and XUbuntu. This sharing mixes up all things as both systems rely on vmlinuz and initrd.img files whose names may be the same, but with different contents. So, please, drop this bug. The /boot partition, where separated from its root (/), should never be shared with several systems. This is my mistake. Arbiel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180685 Title: update-grub makes grub2 point on an incorrect UUID To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1180685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180685] [NEW] update-grub makes grub2 point on an incorrect UUID
Public bug reported:
Hi
'lsb_release -rd'
Description:Ubuntu 12.04.2 LTS
Release:12.04
'apt-cache policy pkgname'
N: Impossible de trouver le paquet pkgname
The bug I want to report is very similar to bug #442631, maybe even the
same bug. I however report the present bug as, to my understanding, bug
#442631 has not been cleared.
Here is my partitions block id's
remi@remi-Vostro-3550:~$ sudo blkid
[sudo] password for remi:
/dev/sda10: LABEL="PASSERELLEM-t" UUID="6272-45BA" TYPE="vfat"
/dev/sda11: LABEL="maisonnette" UUID="dea2a123-c985-4a5c-bc98-975c6bd8386b"
TYPE="ext4"
/dev/sda2: LABEL="OS" UUID="AC7C4EC27C4E86D4" TYPE="ntfs"
/dev/sda5: LABEL="xubuntu" UUID="5193ea50-93a3-41f0-9e40-acd7c80a0877"
TYPE="ext4"
/dev/sda6: LABEL="ciel_remi" UUID="498F2C6F49CED050" TYPE="ntfs"
/dev/sda9: LABEL="Archives" UUID="5ecd6806-5db8-4670-a2fd-079df82cf0d6"
TYPE="ext4"
/dev/sda1: LABEL="Data" UUID="3ee2811f-d984-4ff4-9698-36f083fecda1" TYPE="ext4"
/dev/sda4: LABEL="swap" UUID="857dda1a-4d1f-4e71-bd5d-d6c96e8032c6" TYPE="swap"
/dev/sda7: LABEL="Pingolin" UUID="bedf892b-d69d-45ba-a16c-59b32a8e031c"
TYPE="ext4"
/dev/sda8: LABEL="Multimedia" UUID="3b5a9083-e27a-4f2f-917d-56945ff7fd4e"
TYPE="ext4"
/dev/sda12: LABEL="boot" UUID="1022a339-49dc-41fd-bc26-a8cb207dcb82"
TYPE="ext2"
remi@remi-Vostro-3550:~$
I've got a boot partition on /dev/sda12, nammed "boot
Here is a regular menuentry to boot to Ubuntu 12.04 Precise Pingolin on
/dev/sda7
menuentry 'Ubuntu, avec Linux 3.2.0-41-generic-pae' --class ubuntu --class
gnu-linux --class gnu --class os {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='(hd0,msdos12)'
search --no-floppy --fs-uuid --set=root
1022a339-49dc-41fd-bc26-a8cb207dcb82
linux /vmlinuz-3.2.0-41-generic-pae
root=UUID=bedf892b-d69d-45ba-a16c-59b32a8e031c ro quiet splash $vt_handoff
initrd /initrd.img-3.2.0-41-generic-pae
}
It appears that root is set to /dev/sda12 for looking for the vmlinuz
and initrd.img files, and that the linux line refers to Pingolin's UUID
to pass the root partition to the kernel.
Here is the wrong menu entry, to boot to xubuntu (also a 12.04 version)
on /dev/sda5
menuentry "Ubuntu, avec Linux 3.2.0-41-generic-pae (on /dev/sda5)" --class
gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos12)'
search --no-floppy --fs-uuid --set=root
1022a339-49dc-41fd-bc26-a8cb207dcb82
linux /vmlinuz-3.2.0-41-generic-pae
root=UUID=bedf892b-d69d-45ba-a16c-59b32a8e031c ro quiet splash $vt_handoff
initrd /initrd.img-3.2.0-41-generic-pae
}
It appears that root is still correctly set, by the linux line still
refers to Pingolin's UUID as the root partition, instead of the xubutu's
UUID (5193ea50-93a3-41f0-9e40-acd7c80a0877)
You can find the boot report as it has been created by boot-report at
http://paste.ubuntu.com/5669945/
Beware that the grub.cfg file to be considered is located at line 491
Regards
Arbiel
** Affects: grub2 (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/1180685
Title:
update-grub makes grub2 point on an incorrect UUID
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1180685/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155216] [NEW] Unable to umount isodevice
Public bug reported: When installing from an iso file, with grub's loopback option, Ubiquity displays a message stating the isodevice cannot be unmounted, even when the isofile is not located on the same harddrive as the installation target. sudo umount -l -r -f /isodevice solves this problem, so Ubiquity should be able to issue this command by itself, without any user action. Arbiel ** 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/1155216 Title: Unable to umount isodevice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155201] Re: Remove default value for grub install
*** This bug is a duplicate of bug 1152496 *** https://bugs.launchpad.net/bugs/1152496 ** This bug has been marked a duplicate of bug 1152496 Remove default value for where to install grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155201 Title: Remove default value for grub install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155207] [NEW] Erroneous behaviour regarding partition table
Public bug reported: Even when choosing "Other choice" when installing Ubuntu, it is apparently impossible to install from an iso file located on the same disk as the destination partition. A message states that the partition table is to be accessed and modified, even if no such modification is necessary, as all partitions have been properly set. And even if some partitions have to be reformatted with a file system different from the current ones, this reformating does not concern the other partitions on the same drive. So Ubiquity should be able to properly install a distribution, even if some partition on the destination drive remain mounted. Arbiel ** 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/1155207 Title: Erroneous behaviour regarding partition table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155201] [NEW] Remove default value for grub install
Public bug reported:
When using the third option for installing Ubuntu ("Autre choix" in
french), Ubiquity displays a screen with a control and a default value
for the drive where to install grub. This control is ill located, at the
bottom of the screen, and may easily be inadvertendly left unchanged by
the user, even if the default value may lead to a undesirable result
(installing on an external drive taken away before the installing PC has
been reboot).
Instead, the value should be set by the user, to make sure the choice is
what he really wants to be done.
It is even reasonable to install no grub when installing a distribution,
so a unset value could be take as a decision by the user not to install
grub.
Anyway, confirmation of the to be install configuration should be asked
for before launching the installation.
Arbiel
** 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/1155201
Title:
Remove default value for grub install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1155201/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152496] [NEW] Remove default value for where to install grub
Public bug reported: Hi This is not really a bug report, but rather a improvement request. The subject is close to the subject of #461085 No default value should be used for the location where to install grub, as, inadvertently, the user may omit to specify where he really wants to install grub, and the /dev/sda value may be a great inconvenience for the user. The point that he made a mistake seems to me less relevant than avoiding him to make that mistake. He may even want no grub to be installed. For the least, showup a confirmation request, but rather remove any default value and, if the user did not specify any location, ask him to confirm he does not want any grub to be installed. Arbiel ** 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/1152496 Title: Remove default value for where to install grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1152496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] Re: Wine under Natty fails to run Money 2002
Hi I've switched to running Money with VirtualBox, which solution I am happy with. My project now is to switch to GNU Cash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] Re: Natty boots randomly, 1 every 10 to 20 tries
Can someone tell me when this bug will be assigned to somebody. It's really becoming very cumbersome to boot Ubuntu 11.04. Thank you for any information you can provide me with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] Re: Natty boots randomly, 1 every 10 to 20 tries
and my /boot/grub/grub.cfg configuration file ** Attachment added: "Grub configuration file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+attachment/2462381/+files/grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] Re: Natty boots randomly, 1 every 10 to 20 tries
Here is my /etc/default/grub file ** Attachment added: "Grub parameter file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+attachment/2462379/+files/grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] Re: Wine under Natty fails to run Money 2002
For the moment, I'm in very deep trouble with my GNU/Linux systems : the booting procedure (Natty) very frequently leads to a black screen, I cannot run Money under Wine/Natty, I had to reinstall Maverick also because of a Dell-update of my PC to repair faulty hardware, and my Maverick lacks some drivers (no time to look for appropriate ones). Do not expect me to be very active for Natty/Wine testing in the near future, as I will have to boot Windows to go forward in my daily work. I'll take contact again, when I have been able to be up-to-date with my regular duties. Sorry for the delay -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] Re: Wine under Natty fails to run Money 2002
remi@remi-Vostro-3550:~$ wine --version wine-1.3.15 remi@remi-Vostro-3550:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] Re: Natty boots randomly, 1 every 10 to 20 tries
Here is the second attachment ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+attachment/2447527/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] Re: Natty boots randomly, 1 every 10 to 20 tries
** Attachment added: "version.log" https://bugs.launchpad.net/bugs/857444/+attachment/2447505/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857444] [NEW] Natty boots randomly, 1 every 10 to 20 tries
Public bug reported: This may be a duplicate of bug #683775. In this case, there has been a regression in the Natty distribution. But this may be a new bug, as bug #683775 was reported here in late 2010, and apparently fixed. After I migrated from Maverick to Natty last May (2011) , I experienced some difficulties at boot time. For example, I installed a second Natty on my hard drive, but never have I been able to boot it (at the time, I used to try only a few times).I concluded that I could not have two Natties on the same disk, without understanding why. Since two or three months, the situation has turned highly unbearable. As I did know what was wrong, I installed Natty over and over again, with no significant result, until I found bug #683775. I applied the modification suggested by Andy, with no results. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-11-generic 2.6.38-11.48 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remi 1407 F pulseaudio CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 54' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:111d76d1,102804b3,00100205 HDA:80862805,80860101,0010' Controls : 18 Simple ctrls : 10 Date: Fri Sep 23 16:10:18 2011 HibernationDevice: RESUME=UUID=8f2885cb-39ad-4ce3-9799-6fd77a8df4e7 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. Vostro 3550 ProcEnviron: LANGUAGE=fr:en LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=a0cf8484-de2c-4269-9cab-77eab5fee0ec ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-11-generic N/A linux-backports-modules-2.6.38-11-generic N/A linux-firmware 1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 053PX4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/02/2011:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn053PX4:rvrA02:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug natty running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857444 Title: Natty boots randomly, 1 every 10 to 20 tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/857444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] Re: Wine under Natty fails to run Money 2002
People at Wine say that, as I did not change the version of WIne, this is a distribution bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683775] Re: Natty Alpha 1, i915 has blank screen after boot
I have 3 distros : 1 Natty and 1 Maverick on my internal disk and 1 Natty on an external Usb disk, all 64 bits. Andy's modification helped to boot both Natty, however with better results for my internal Natty (roughly 50% success for warm boots, and 25% for cold ones) than for my external one (maybe 20% for warm boots, and 10% for cold one). Each Natyy has its own swap. A few days ago, I had to boot Maverick (no problem booting), and this then both Natties refuse to boot (I may have since run up to 20 tries on each one). Internal Natty's kernel : Linux 2.6.38-11-generic USB Natty's kernel : Linux 2.6.38-8-generic Maverik's kernel : Linux 2.6.35-22-generic The situation is getting very frustrating, as my Maverik is not complete : does not run WIfi and has no sound. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683775 Title: Natty Alpha 1, i915 has blank screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/683775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] Re: Wine under Natty fails to run Money 2002
** Bug watch added: Wine Bugzilla #28300 http://bugs.winehq.org/show_bug.cgi?id=28300 ** Also affects: wine via http://bugs.winehq.org/show_bug.cgi?id=28300 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843327] [NEW] Wine under Natty fails to run Money 2002
Public bug reported: Wine used to run 2002 under Maverick. Since I upgraded Ubuntu to Natty, Wine is unable to run Money. At start, it open a window stating "Microsoft Money a rencontré un problème et doit fermer. Nous vous prions de nous excuser pour le désagrément encouru", in other words that Microsoft Money has crashed and must close down. ** Affects: unity-2d Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Also 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/843327 Title: Wine under Natty fails to run Money 2002 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/843327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683775] Re: Natty Alpha 1, i915 has blank screen after boot
The bug seems to me not to have been fixed. It takes me up to 6 to 8 tries before any successfull cold boot. I made the modification suggested by Andy in comment #10. Maybe 1 success for every 8 to 10 tries. I don't know whether it still makes sense to test the kernel linked at in comment #14. If it makes sense, can somebody explain me how to do ? ** Attachment added: "boot_info_05_09_2011.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683775/+attachment/2356336/+files/boot_info_05_09_2011.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683775 Title: Natty Alpha 1, i915 has blank screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/683775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800563] [NEW] Accord des adjectifs attributs
Public bug reported: remi@remi-Vostro-3550:~$ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 remi@remi-Vostro-3550:~$ LibreOffice 3.3.2 OOO330m19 (Build:202) tag libreoffice-3.3.2.2, Ubuntu package 1:3.3.2-1ubuntu5 The french spelling checker erroneously accepts wrong spellings of adjectives as in Il nous faut être capable et inventif Both adjectives "capable" and "inventif" report to "nous" (pluriel, complément indirect de "faut") and not to "il" (singulier, sujet de "faut") The correct spelling is Il nous faut être capables et inventifs. However, the checker accepts the correct spelling. Other wrongly accepted erroneous spellings Il nous plaît d'être capable et inventif. Il nous donne l'illusion d'être inventive Pitfall : both hereunder sentences are correctly spelled (and accepted by the checker) Il nous donne l'illusion d'être capables et inventifs Il nous donne l'illusion d'être capable et inventif. Ubuntu Natty 64 bits ** Affects: libreoffice (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/800563 Title: Accord des adjectifs attributs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/800563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
