[Bug 372695] Re: creating new user account silently fails when UID is already used
I can confirm the findings of "FernanAguero". The fix is: - delete the home dir - remove from /etc/group - remove from /etc/gshadow Now you can recreate a user you have deleted. Good starting point for the devs. Regards, OE -- creating new user account silently fails when UID is already used https://bugs.launchpad.net/bugs/372695 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771651] [NEW] The installation fails with a "GRUB installation failed" message.
Public bug reported: Release: Ubuntu 18.04 LTS (Bionic Beaver) Summary: The installation fails with a "GRUB installation failed" message. Workaround available, see below. Since 16.04 installed fine, you could see this as a regression... * System setup (relevant part only) - UEFI enabled - Secure Boot disabled - SSD with a pre-install MBR (msdos) partition layout /dev/sda /dev/sda1 ext4 / (format) /dev/sda2 ext4 /home (do NOT format) /dev/sda3 swap * During the install (relevant part only) - Installation type: select "Manual" - Prepare partitions: see layout above >>> What I expected to happen: installation success! >>> What happened instead: (see below) After the complete installation is done, an alert box pops up: Alert box: GRUB installation failed """ The 'grub-efi-amd64-signed' package failed to install into / target/. Without the GRUB boot loader, the installed system will not boot. """ Button: OK Side note: I think this alert box fails to fill in the "/target/" part... After clicking on [OK] an "Installer Crashed" window appears. Before I can read anything, the window disappears. (This also looks like a bug!). Then the installer flips back to the live desktop with the "Install" icon on the desktop. I reboot the system. The next error appears: """ error: file '/boot/grub/i386-pc/normal.mod' not found. Entering rescue mode... grub rescue> """ At this point I can't do anything because grub is missing files! I consider this also a bug, the installer should always install GRUB full because failures are unforeseen by their very nature. You should always have a full GRUB installation available when this happens, even when the installer assumes(!) it's doing the right thing... Do -not- assume Murphy's law doesn't apply to you, because then it will hit you even harder... My guess on what went wrong: The installer detected that UEFI was enabled, then (wrongly) assumed/detected that Secure Boot was also enabled. Then logic dictates (...) that the HDD/SSD should be a GPT disk with the appropriate layout and (wrongly) "thinks" MBR is not an option. Now GRUB fails because it encounters a MBR disk. == === The Workaround === == The simple workaround is; use a GPT disk with the appropriate partition layout. When using a GPT disk with the appropriate partition layout is not an option, then use this three step workaround: 1) Fix the wrong GRUB installation 2) Manual boot the system with GRUB 3) Run update-grub so the system will boot correctly * Step 1: Fix the wrong GRUB installation - Boot into the live desktop - Open a terminal - Find the boot disk... ...in this case it is: /dev/sda - Find the partition where /boot is installed... ...in this case it is: /dev/sda1 - Now run the commands: (replace /dev/sda1 and /dev/sda with the appropriate values) sudo mount /dev/sda1 /mnt sudo grub-install --boot-directory=/mnt/boot /dev/sda * Step 2: Manual boot the system with GRUB - Boot the system, the "grub>" prompt should appear. - Find the partition where /boot is installed... ...in this case it is: (hd0,msdos1) - Find the partition where / is installed... ...in this case it is: /dev/sda1 - Heads-up: pay attention to the "ls" commands, the vmlinuz and initrd filenames may differ! - Now run the commands: ls ls (hd0,msdos1)/boot set root=(hd0,msdos1) linux /boot/vmlinuz-4.15.0-20-generic root=/dev/sda1 initrd /boot/initrd.img-4.15.0-20-generic boot - The system should boot now... * Step 3: Run grub so the system will boot automatically - The system is now booted - Open a terminal - Now run the command: sudo update-grub - Now reboot the system - The system will boot normally now ... if everything went well... ** Affects: ubuntu Importance: Undecided Status: New ** Tags: grub grub-efi-amd64-signed installer normal.mod rescue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771651 Title: The installation fails with a "GRUB installation failed" message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1771651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
Can anybody confirm that the workaround in the bug report below works? https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651 If so, then it could be a duplicate... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
For the people who are looking for a workaround; I think you have three options: - Use a GPT partition table on the disk - Boot the installer in legacy mode - When both are not an option (or fail), use the workaround described in: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651 I hope this helps, regards, Onno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771675] Re: Ubuntu18.04 fail to install grub and destroy existing grub
Could you try the workaround found here: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771675 Title: Ubuntu18.04 fail to install grub and destroy existing grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771782] Re: The ubuntu 18.04 installer went through the installation process and then suddenly halted, said I cannot install the grub bootloader. Looks like I am cooked. My machine is useless wi
Although the bug is a bit different, the workaround in the bug below is quite generic. Maybe you could try it or adapt it to your needs: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651 I hope this helps, regards, Onno -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771782 Title: The ubuntu 18.04 installer went through the installation process and then suddenly halted, said I cannot install the grub bootloader. Looks like I am cooked. My machine is useless without an operating system. I did not even keep my older ubuntu 14.04 installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771651] Re: The installation fails with a "GRUB installation failed" message.
@oldfred; I understand your argument, but this doesn't take reality in account. I've looked for similar bugs (very likely duplicates of this one or visa versa) and there are more than 250 reports regarding grub failures at the end of the installation or upgrade. In theory you are right, in practice there are a lot of people who have troubles. The Linux kernel itself is full of "reality patches" that defy theory but work nevertheless. Also take into account that the previous LTS installed fine and GRUB behaved as expected, even when dual-booting Windows 7. It's really easy to argue that this is a regression and should be fixed accordingly. In conclusion; when a large portion of your user-base is experiencing trouble where they don't expect it and/or had none before, it should be fixed. Especially when a fix is (easily) feasible and expands the use of Ubuntu and it derivatives considerably. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771651 Title: The installation fails with a "GRUB installation failed" message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
> Is this really a bug? When the previous LTS had not problems in these situations, then it's not only a bug but a regression as well. When a large portion of your user-base is experiencing trouble where they don't expect it and/or had none before, it should be fixed. Especially when a fix is (easily) feasible and expands the use of Ubuntu and it derivatives considerably. Thus, it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767703] Re: Calling 'apt-install grub-efi-amd64-signed' failed
Is this a "grub-installer" bug -or- is the use of grub in "ubiquity" the problem ??? If the latter, then this bug should be assigned to the "ubiquity" package... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767703 Title: Calling 'apt-install grub-efi-amd64-signed' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771651] Re: The installation fails with a "GRUB installation failed" message.
@apt-ghetto Thanks for you're analysis. I have no option to boot in legacy mode... @apt-ghetto said: > ..you can install Ubuntu in BIOS mode simply by booting the installer in > the BIOS mode. > (Depending on the UEFI you have and how you created the USB stick, this is > not always a simple task) So this the real solution then; detect / make it easy to boot in legacy mode! But this a regression then, I had no problems while installing 16.04 via USB stick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771651 Title: The installation fails with a "GRUB installation failed" message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1771651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012058] Re: package mysql-server-5.5 5.5.24-0ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
It's apparmor. See /var/log/syslog Aug 1 22:37:19 magna kernel: [119350.467189] type=1400 audit(1343853439.594:46): apparmor="DENIED" operation="mknod" parent=15003 profile="/usr/sbin/mysqld" name="/run/tmp/ibQJ1cz5" pid=15094 comm="mysqld Note: I've symlinked /tmp to /run/tmp ... To fix, edit: /etc/apparmor.d/usr.sbin.mysqld, and add: /tmp/** rwk, /run/tmp/** rwk, Maybe I could do without the last or with fewer rights, but I'm in a hurry... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012058 Title: package mysql-server-5.5 5.5.24-0ubuntu0.12.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/1012058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441835]
Even if floppies are rare on the general desktop, I would sure like to see this fixed. Floppies still have a strong niche in specialty equipment. I have a bunch of machines here with floppy drives. Is there a work-around? Older version that works? Udisks2? Other? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441835 Title: Clicking on floppy gives "no device media found" To manage notifications about this bug go to: https://bugs.launchpad.net/devicekit/+bug/441835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
Bug also occurs with Mesa 9.2.2, in Ubuntu 14.04 pre-alpha: OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.2 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303086] Re: Pointer Speed Missing in Unity Settings for Mouse & Trackpad
*** This bug is a duplicate of bug 1132063 *** https://bugs.launchpad.net/bugs/1132063 A also experience the bug in Ubuntu 16.04 final beta. Using a Logitech wireless optical mouse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303086 Title: Pointer Speed Missing in Unity Settings for Mouse & Trackpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1303086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
I can hardly believe my eyes, but this bug appears to be FIXED under the current libraries in the Trusty beta. evil@clevo:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0-rc1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.1.0-rc1 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: evil@clevo:~$ uname -r 3.13.0-10-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
Problem still occurs with Mesa 9.2.1 evil@clevo:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.1 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.1 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
I can also recreate it at 9.2.0 (using Ubuntu 13.10 beta). Symptoms appear same as the original when using cairo-dock. - evil@clevo:~/src/clevokbledui$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.0 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.0 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282867]
I've been seeing the same glitches, starting when the updated mesa packages were pushed out on 2/20: http://ubuntuforums.org/showthread.php?t=2206883 At exactly the same time the glitches appeared, the primus bridge quit working for Bumblebee: https://github.com/amonakov/primus/issues/133 Backleveling mesa to the packages in the saucy repository causes the graphical glitches to disappear and everything looks normal again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282867 Title: Many bugs in rendering with lockups, likely caused by SNA To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1282867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
Excellent! It appears this bug is fixed in Mesa 10.1 and later, and can finally 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/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
I also tested with edgers 10.2 packages, like k3mist, and it is still working perfectly. I too rebooted and checked multiple times that everything is good. I found other bugs with the current 10.1 packages in trusty, but they're not related to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
Yes. :) I definitely made sure it was using OpenGL and that I was running it on my HD4000 and not the nVidia chipset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 521877]
Please add an option (command-line or config file) to make the X server stop lying about the physical DPI of the display device. I understand all the arguments for pegging DPI at 96, but *I* still want my X server to report the actual DPI as read from the EDID. Maybe add an -autodpi command-line option? Or support "-dpi auto" with 96 being the default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/521877 Title: [gm45] wrong screen size detected on X200s To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/521877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180646]
I've also been able to recreate this issue while running cairo-dock on a Clevo P150EM (Intel HD4000). I see the status is NEEDINFO. I've worked around the issue for myself by just using the cairo back end, but is there any info/testing I can provide to help resolve the issue when using OpenGL? evil@clevo:~$ lsmod|grep "^i" ... i915 610430 4 ... evil@clevo:~$ sudo lshw -C display [sudo] password for evil: *-display description: VGA compatible controller product: 3rd Gen Core processor Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:45 memory:f740-f77f memory:d000-dfff ioport:f000(size=64) evil@clevo:~$ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Ivybridge Mobile OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.1.4 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.1.4 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
