[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT
Additional to the last - Just noticed, like the OP, I also have windows installed on a separate drive - not sure if this is important or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924605 Title: Grub2 menu not loading - could not create MokListXRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1924605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924605] Re: Grub2 menu not loading - could not create MokListXRT
Also a Lenovo T430 owner receiving the same error message having just updated from 20.10 to 21.04. The file system is ext4 with LVS encryption. I didn't see this message prior to the update to 21.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924605 Title: Grub2 menu not loading - could not create MokListXRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1924605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915760] [NEW] crashed on install - used zfs - notsurprised as an experiment
Public bug reported: Old acer 590 notebook - could be hardware error ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.4 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.456 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 16 09:37:10 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) ProcEnviron: LANGUAGE=en_NZ.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.4 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915760 Title: crashed on install - used zfs - notsurprised as an experiment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1915760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896316] Re: tracker-extract crashed with signal 31 in statx()
Hi Sebastien Thanks for the notification. I'll send any more bugs if they occur, but so far, pre-release Ubuntu 20.10 appears to be surprisingly stable. Ian On Sat, Oct 10, 2020 at 12:30 PM Apport retracing service < 1896...@bugs.launchpad.net> wrote: > ** Tags added: need-amd64-retrace > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896316 > > Title: > tracker-extract crashed with signal 31 in statx() > > Status in tracker-miners package in Ubuntu: > Fix Released > > Bug description: > Ubuntu 20.10 > > ProblemType: Crash > DistroRelease: Ubuntu 20.10 > Package: tracker-extract 2.3.3-2build1 > ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 > Uname: Linux 5.8.0-18-generic x86_64 > ApportVersion: 2.20.11-0ubuntu45 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: KDE > Date: Sat Sep 19 10:36:18 2020 > ExecutablePath: /usr/libexec/tracker-extract > InstallationDate: Installed on 2020-05-21 (120 days ago) > InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 > (20200521) > ProcCmdline: /usr/libexec/tracker-extract > ProcEnviron: >LANG=de_CH.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >XDG_RUNTIME_DIR= > Signal: 31 > SourcePackage: tracker-miners > StacktraceTop: >statx (fd=-100, path=0x7fd6b401cd10 "/home/username/Downloads/Jenevieve > - Baby Powder (Official Video).mp3", flags=2304, mask=4095, > buf=0x7fd6c9727580) at ../sysdeps/unix/sysv/linux/statx.c:29 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 >tracker_file_get_size () from > /usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-mp3.so >tracker_extract_get_metadata () from > /usr/lib/x86_64-linux-gnu/tracker-miners-2.0/extract-modules/libextract-mp3.so > Title: tracker-extract crashed with signal 31 in statx() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1896316/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896316 Title: tracker-extract crashed with signal 31 in statx() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1896316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896316] Re: tracker-extract crashed with signal 31 in statx()
Unexpected crash but not unexpected for a pre-release Ubuntu 20.10. Otherwise it has been working fine. I also note that Scilab works on this version, running as a VM using Virtualbox on windows 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896316 Title: tracker-extract crashed with signal 31 in statx() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1896316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875491] [NEW] boot fail
Public bug reported: on hp envy- suspect the notebook ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 08:48:10 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_NZ.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875491 Title: boot fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1875491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875311] [NEW] Boot failure on HP Envy notebook
Public bug reported: Failed on Ubuntu 20.04 recent download, full production OS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 20:31:27 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_NZ.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875311 Title: Boot failure on HP Envy notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1875311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875311] Re: Boot failure on HP Envy notebook
Tried dual boot alongside Zorin OS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875311 Title: Boot failure on HP Envy notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1875311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875311] Re: Boot failure on HP Envy notebook
Will try boot repair from Zorin OS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875311 Title: Boot failure on HP Envy notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1875311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875130] [NEW] some crashes afer ubuntu reinstall - probably minor
Public bug reported: dual boot on HP Pavilion dv6 notebook ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 18:08:53 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_NZ.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875130 Title: some crashes afer ubuntu reinstall - probably minor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875130] Re: some crashes afer ubuntu reinstall - probably minor
will try complete reinstall if many programs are missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875130 Title: some crashes afer ubuntu reinstall - probably minor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Sri Thanks for the information. The HP Envy does not come with an optical drive as with many notebooks these days, so therefore none should show in BIOS. It does have 4 USB ports and all are working. I use one for a wireless mouse, another for a WiFi dongle (its internal WiFi card is dodgy, as seems to happen prematurely with HP notebooks). The other two I use for USB drives, external USB HD, external USB optical drives and and external USB 16 bit sound card etc - no problems. *The only issue is boot failure*. Interestingly, the same boot failure always occurs on another HP Pavilion notebook for any OS based on Ubuntu 18.04. On my HP Envy notebook I just installed the Debian version LDME for Mint Cinnamon that is based on Debian rather than Ubuntu - seems to be going fine, but dual boots Zorin OS, based on Ubuntu 18.04 and had therefore, I guess, needed the boot repair utility. Also of interest, Mint Cinnamon 18.3 now also comes shipped with a boot repair utility in its installation ISO. *It seems odd that both Zorin OS and Mint 18.3, both based on Ubuntu 18.04, would develop a boot repair utility unless they were aware of a need for one*. Further, I had attempted to install Ubuntu 20.04 previously - zero boot repair success, but it runs fine as a virtual machine in VirtualBox on any notebook with any OS installed. Ian On Wed, Jan 29, 2020 at 6:16 AM Sri <1851...@bugs.launchpad.net> wrote: > And, just to note an observation fwiw, in response to comment #10, the > non-existant boot order variables probably corresponded to a USB drive > and an optical drive that were set in the BIOS Boot Order, but are > physically not present (the actual CD/DVD and a bootable USB stick). I > do see them set in the BIOS. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in efivar package in Ubuntu: > New > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve, Sri Of course I want to help. *My notebook is available as it is.* I have time and intent. Iaan On Sat, Jan 11, 2020 at 4:41 AM Sri <1851...@bugs.launchpad.net> wrote: > Steve, > I downloaded (downgraded) libefiboot1 and libefivar1 per your suggestion > in comment #14, and here is the output (no change from previous results). > > $ sudo dpkg -i libefiboot1_34-1_amd64.deb > dpkg: warning: downgrading libefiboot1:amd64 from 37-2ubuntu2 to 34-1 > (Reading database ... 398727 files and directories currently installed.) > Preparing to unpack libefiboot1_34-1_amd64.deb ... > Unpacking libefiboot1:amd64 (34-1) over (37-2ubuntu2) ... > Setting up libefiboot1:amd64 (34-1) ... > Processing triggers for libc-bin (2.30-0ubuntu2) ... > $ > $ sudo dpkg -i libefivar1_34-1_amd64.deb > dpkg: warning: downgrading libefivar1:amd64 from 37-2ubuntu2 to 34-1 > (Reading database ... 398727 files and directories currently installed.) > Preparing to unpack libefivar1_34-1_amd64.deb ... > Unpacking libefivar1:amd64 (34-1) over (37-2ubuntu2) ... > Setting up libefivar1:amd64 (34-1) ... > Processing triggers for libc-bin (2.30-0ubuntu2) ... > $ > $ sudo efibootmgr -o ,0003,0004,0001; echo $? > Invalid BootOrder order entry value,0003,0004 >^ > efibootmgr: entry 0004 does not exist > 8 > $ > $ sudo efibootmgr -o ,0003,0001; echo $? > Could not set BootOrder: Invalid argument > 8 > $ > > Please let me know if you want me to run any more tests. > > Regards, > Sri > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in efivar package in Ubuntu: > New > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve I can of course only reply on a notebook running an OS *that works*. How could I reply on a notebook that doesn't work? *I have been clear and exact on all I have replied*. I have tried to assist. I cannot do the impossible Steve. Ubuntu definitely has a problem here. Can you solve this problem or not? Whether you can acknowledge and address this Ubuntu problem that it definitely is now or not matters to me neither. I have tried within what I could possibly be able to do to help. Perhaps this isn't enough. In any case, maybe Ubuntu is in sunset now, bootless. Ian On Fri, Jan 10, 2020 at 1:30 PM Steve Langasek wrote: > On Wed, Jan 08, 2020 at 09:30:29PM -0000, Ian Scott wrote: > > I can install Ubuntu 20.04 on this notebook as I have an ISO for this - > > runs fine in Virtualbox. > > I'm sorry, are you running these commands on Ubuntu, or not? I assumed it > was clear that I was looking for the output of these commands from Ubuntu. > > In particular, > > > I downloaded both .deb files and ran using gdebi - it reports "same > > version already installed" so I reinstalled anyway and then ran > > efivar 34-1 is the version of this package in Ubuntu 18.04; so you should > not have seen this message if you were installing it on Ubuntu 19.10. > > > sudo efibootmgr -o ,3000,0001,0002,2001; echo $? > > > Output is > > > Invalid BootOrder order entry value,3000,0001,0002,2001,2002 > > > efibootmgr: entry 2002 does not exist > > 8 > > The command you've quoted above doesn't list 2002 but your output does. > Did > you run the right command? > > > As a thought Steve, is it possible for you to remotely access this > > notebook? > > We are not set up for secure remote access to arbitrary users' computers, > no. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in efivar package in Ubuntu: > New > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve Some more information if it is of any help I added another OS to dual boot with Zorin OS on this notebook. At first I tried to dual boot with Ubuntu 20.04. It installed but with grub boot failure. I tried several times to repair this using the Zorin USB repair boot utility - all attempts consistently failed to repair and let this notebook boot. I then installed Mint 19.3 and this also reported grub boot failure. This time the Zorin USB fix boot utility is working (so far). However Mint consistently reports an error each time I install new software or use the update manager. I installed Clementine, for example and here is the error message output, installArchives() failed: Selecting previously unselected package libmng2:amd64. (Reading database ... (Reading database ... 5%% (Reading database ... 10%% (Reading database ... 15%% (Reading database ... 20%% (Reading database ... 25%% (Reading database ... 30%% (Reading database ... 35%% (Reading database ... 40%% (Reading database ... 45%% (Reading database ... 50%% (Reading database ... 55%% (Reading database ... 60%% (Reading database ... 65%% (Reading database ... 70%% (Reading database ... 75%% (Reading database ... 80%% (Reading database ... 85%% (Reading database ... 90%% (Reading database ... 95%% (Reading database ... 100%% (Reading database ... 289950 files and directories currently installed.) Preparing to unpack .../00-libmng2_2.0.2-0ubuntu3_amd64.deb ... Unpacking libmng2:amd64 (2.0.2-0ubuntu3) ... Selecting previously unselected package qtcore4-l10n. Preparing to unpack .../01-qtcore4-l10n_4%%3a4.8.7+dfsg-7ubuntu1_all.deb ... Unpacking qtcore4-l10n (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqtcore4:amd64. Preparing to unpack .../02-libqtcore4_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqtcore4:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqjson0:amd64. Preparing to unpack .../03-libqjson0_0.8.1-3_amd64.deb ... Unpacking libqjson0:amd64 (0.8.1-3) ... Selecting previously unselected package libcrypto++6. Preparing to unpack .../04-libcrypto++6_5.6.4-8_amd64.deb ... Unpacking libcrypto++6 (5.6.4-8) ... Selecting previously unselected package libqt4-xml:amd64. Preparing to unpack .../05-libqt4-xml_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-xml:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqtdbus4:amd64. Preparing to unpack .../06-libqtdbus4_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqtdbus4:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package qtchooser. Preparing to unpack .../07-qtchooser_64-ga1b6736-5_amd64.deb ... Unpacking qtchooser (64-ga1b6736-5) ... Selecting previously unselected package qdbus. Preparing to unpack .../08-qdbus_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking qdbus (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqt4-dbus:amd64. Preparing to unpack .../09-libqt4-dbus_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-dbus:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqt4-network:amd64. Preparing to unpack .../10-libqt4-network_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-network:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package liblastfm1:amd64. Preparing to unpack .../11-liblastfm1_1.0.9-1_amd64.deb ... Unpacking liblastfm1:amd64 (1.0.9-1) ... Selecting previously unselected package libmygpo-qt1:amd64. Preparing to unpack .../12-libmygpo-qt1_1.0.9-2_amd64.deb ... Unpacking libmygpo-qt1:amd64 (1.0.9-2) ... Selecting previously unselected package projectm-data. Preparing to unpack .../13-projectm-data_2.1.0+dfsg-4build1_all.deb ... Unpacking projectm-data (2.1.0+dfsg-4build1) ... Selecting previously unselected package libftgl2:amd64. Preparing to unpack .../14-libftgl2_2.1.3~rc5-4+nmu1.2_amd64.deb ... Unpacking libftgl2:amd64 (2.1.3~rc5-4+nmu1.2) ... Selecting previously unselected package libglew2.0:amd64. Preparing to unpack .../15-libglew2.0_2.0.0-5_amd64.deb ... Unpacking libglew2.0:amd64 (2.0.0-5) ... Selecting previously unselected package libprojectm2v5. Preparing to unpack .../16-libprojectm2v5_2.1.0+dfsg-4build1_amd64.deb ... Unpacking libprojectm2v5 (2.1.0+dfsg-4build1) ... Selecting previously unselected package libqt4-script:amd64. Preparing to unpack .../17-libqt4-script_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-script:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqt4-sql:amd64. Preparing to unpack .../18-libqt4-sql_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-sql:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqt4-xmlpatterns:amd64. Preparing to unpack .../19-libqt4-xmlpatterns_4%%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Unpacking libqt4-xmlpatterns:amd64 (4:4.8.7+dfsg-7ubuntu1) ... Selecting previously unselected package libqt4-declarative:amd64. Preparing to unpack
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve I downloaded both .deb files and ran using gdebi - it reports "same version already installed" so I reinstalled anyway and then ran sudo efibootmgr -o ,3000,0001,0002,2001; echo $? Output is Invalid BootOrder order entry value,3000,0001,0002,2001,2002 ^ efibootmgr: entry 2002 does not exist 8 As a thought Steve, is it possible for you to remotely access this notebook? If so it might speed things up. Also I don't mind wiping it and trying new installs if that helps - currently it runs Zorin OS as this has a boot repair utility and otherwise Ubuntu won't boot by itself - it will with the Zorin repair but not perfectly as it appears to be optimised for Zorin OS, that it has worked for Ubuntu (and Mint 19.3)is probably an accident. I can install Ubuntu 20.04 on this notebook as I have an ISO for this - runs fine in Virtualbox. Ian On Thu, Jan 9, 2020 at 10:01 AM Steve Langasek wrote: > Thanks. Since this fails for you both with efibootmgr and with grub, > that suggests there might be a bug in the underlying efivar library. > Opening a task on that package. > > Can you try installing the libefiboot1 and libefivar1 packages from > https://launchpad.net/ubuntu/+source/efivar/34-1/+build/14347977 and > running the efibootmgr command again, to see if that changes the > behavior for you? > > ** Also affects: efivar (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in efivar package in Ubuntu: > New > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve Thanks - I remember the sudo dpkg --configure -a command and have had to use it before - didn't know what it was called though. I ran it but the terminal had no feedback to make. I then ran your new command and here is the output Could not set BootOrder: Invalid argument 8 Ian On Wed, Jan 8, 2020 at 1:00 PM Steve Langasek wrote: > On Tue, Jan 07, 2020 at 11:40:05PM -0000, Ian Scott wrote: > > I'm at the library at the moment on another notebook but I'll be back in > > an hour or so to try the new idea. However "And then, could you try > > finishing the configuration of the grub package?" > > > Unfortunately I have no idea at all how to do this. Can you provide some > > instructions Steve? I only use computers, mainly for math analysis and > > simulations, but I have very little understanding of what goes on inside > > the OS. > > >From a console, you should be able to run 'sudo dpkg --configure -a' and > watch it attempt to finish configuration of the grub packages that > previously failed to configure. > > > On Wed, Jan 8, 2020 at 11:50 AM Steve Langasek < > steve.langa...@canonical.com> > > wrote: > > > > > The error message appears to be correct, you have both 2002 and 2003 in > > > your BootOrder but neither is present in your list of boot options. I > > > don't think this is the cause of the grub failure. Could you try > > > instead running the command: > > > > > > sudo efibootmgr -o ,3000,0001,0002,2001; echo $? > > > > > > and see if that works better? And then, could you try finishing the > > > configuration of the grub package? > > > > > > Interestingly, I notice that Sri also has a BootOrder variable which > > > references a non-existent boot entry. So it's possible this is > related. > > > > > > -- > > > You received this bug notification because you are subscribed to the > bug > > > report. > > > https://bugs.launchpad.net/bugs/1851955 > > > > > > Title: > > > ubuntu 19.10 boot installer failed > > > > > > Status in grub2 package in Ubuntu: > > > New > > > Status in shim-signed package in Ubuntu: > > > Incomplete > > > > > > Bug description: > > > Installed on an ENVY notebook, installation afiled at the end with no > > > bootloader message > > > > > > ProblemType: Bug > > > DistroRelease: Ubuntu 19.10 > > > Package: ubiquity 19.10.21 > > > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > > > Uname: Linux 5.3.0-18-generic x86_64 > > > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > > > ApportVersion: 2.20.11-0ubuntu8 > > > Architecture: amd64 > > > CasperVersion: 1.427 > > > Date: Sun Nov 10 08:32:41 2019 > > > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > > > quiet splash --- maybe-ubiquity > > > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > > > SourcePackage: ubiquity > > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > > > To manage notifications about this bug go to: > > > > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions > > > > > > > -- > > You received this bug notification because you are subscribed to shim- > > signed in Ubuntu. > > https://bugs.launchpad.net/bugs/1851955 > > > > Title: > > ubuntu 19.10 boot installer failed > > > > To manage notifications about this bug go to: > > > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve I'm at the library at the moment on another notebook but I'll be back in an hour or so to try the new idea. However "nd then, could you try finishing the configuration of the grub package?" Unfortunately I have no idea at all how to do this. Can you provide some instructions Steve? I only use computers, mainly for math analysis and simulations, but I have very little understanding of what goes on inside the OS. Ian On Wed, Jan 8, 2020 at 11:50 AM Steve Langasek wrote: > The error message appears to be correct, you have both 2002 and 2003 in > your BootOrder but neither is present in your list of boot options. I > don't think this is the cause of the grub failure. Could you try > instead running the command: > > sudo efibootmgr -o ,3000,0001,0002,2001; echo $? > > and see if that works better? And then, could you try finishing the > configuration of the grub package? > > Interestingly, I notice that Sri also has a BootOrder variable which > references a non-existent boot entry. So it's possible this is related. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve Here's the output Invalid BootOrder order entry value,3000,0001,0002,2001,2002 ^ efibootmgr: entry 2002 does not exist 8 Ian On Wed, Jan 8, 2020 at 10:55 AM Steve Langasek wrote: > Ok. Ian, Sri, could you also both check whether running efibootmgr on > Ubuntu 19.10 succeeds? Probably the easiest check is a no-op rewrite of > the boot order variable. Ian, for you the command would be: > > sudo efibootmgr -o ,3000,0001,0002,2001,2002,2003; echo $? > > Sri, for you the command would be: > > sudo efibootmgr -o ,0003,0004,0001; echo $? > > Please post the complete output of this command. > > This will help us determine whether there is a bug in the grub > implementation of variable writing, or if there's a bug in the > underlying libraries used by both grub and efibootmgr. > > ** Also affects: grub2 (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in grub2 package in Ubuntu: > New > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Steve Thanks for your reply. Here are the outputs for this Envy notebook - now running Zorin OS as this installs and has a "Grub repair" feature on its USB install stick - usually fixes all HP shenanigans. BootCurrent: Timeout: 5 seconds BootOrder: ,3000,0001,0002,2001,2002,2003 Boot* ubuntu HD(1,GPT,ca9d4c6c-f90a-408b-9a27-1559c1619904,0x800,0x10)/File(\EFI\ubuntu\shimx64.efi)RC Boot0001* Network Adapter (IPv4 UEFI) PciRoot(0x0)/Pci(0x1c,0x6)/Pci(0x0,0x0)/MAC(a0481cc2def7,0)/IPv4(0.0.0.00.0.0.0,0,0)RC Boot0002* Network Adapter (IPv6 UEFI) PciRoot(0x0)/Pci(0x1c,0x6)/Pci(0x0,0x0)/MAC(a0481cc2def7,0)/IPv6([::]:<->[::]:,0,0)RC Boot2001* USB Drive (UEFI) RC Boot3000* Internal Hard Disk or Solid State Disk RC Boot3001* Internal Hard Disk or Solid State Disk RC Boot3002* Internal Hard Disk or Solid State Disk RC Boot3003* Internal Hard Disk or Solid State Disk RC Boot3004* Internal Hard Disk or Solid State Disk RC I ran your command on another HP Pavilion dv6 that also has grub failure using Ubuntu. It replied "EFI Variables are not installed on this system". I checked BIOS in detail on both notebooks - no mention of anything unusual. This second dv6 also had Grub install failure with Ubuntu and also Mint 19.3 - based on Ubuntu. It now dual boots Zorin OS and Mint 19.3. To accomplish this I installed Zorin OS first, used its Grub repair feature, installed Mint 19.3 for dual boot and Grub install failure occurred. I used Zorin OS Grub repair on its USB install pen drive to get Grub to work, now both OS are happy. *I agree that this is definitely intentional by HP to motivate consumers to buy another notebook - they hope one of theirs*. No way! Not Ever again Steve! Other anti-consumer behaviour - battery charge failures - proprietary 3-pin connection on this Envy. It is impossible to wire in any other 19 V supply - I tried this, it doesn't respond. I waited a week, it stopped playing silly games. I am quite certain given all this that HP Intentionally is motivating consumers to ditch older notebook and buy another. They especially target Ubuntu as I have described on several incidents, all based on Ubuntu. Thanks for your assistance Steve. Although I have a workaround there may be others who don't - If I can help others with HP shenanigans, no problem. Lastly, on an older Acer 5920 notebook - never a problem. I use this one to try lots of different OS, often. This behaviour is specific to HP. Ian On Tue, Jan 7, 2020 at 7:30 AM Steve Langasek wrote: > On Mon, Jan 06, 2020 at 05:46:14PM -, Sri wrote: > > Setting up grub-efi-amd64-signed (1.128.1+2.04-1ubuntu12.1) ... > > Installing for x86_64-efi platform. > > grub-install: warning: Cannot set EFI variable Boot. > > grub-install: warning: efivarfs_set_variable: writing to fd 7 failed: > Invalid argument. > > grub-install: warning: _efi_set_variable_mode: ops->set_variable() > failed: Invalid argument. > > grub-install: error: failed to register the EFI boot entry: Invalid > argument. > > > Any clue on where I should start looking? > > Look into reports of problems with your specific firmware for your specific > device. See if an update is available. See if there are options in the > BIOS menu that control whether these variables are locked. > > What is the output of 'efibootmgr -v' on this system? > > If Ubuntu can't control the boot variables, then it can't reliably boot on > the system; so the package install failure is intentional. > > However you also mention that this started happening to you on upgrade and > there has been a change in grub's implementation between 18.04 and 19.10, > where previously grub shelled out to efibootmgr and now it writes the > variables directly. So it's possible there is a bug in the grub > implementation. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1851955/+subscriptions > -- You received this bug notification because you are
Re: [Bug 1851955] Re: ubuntu 19.10 boot installer failed
Hi Jean-Baptiste and Steve I admit I am baffled but I appreciate your replies. I had thought it might be caused by a small hard drive error but that's just a guess. Interestingly Mint 18 installs OK Mint 12.2 doesn't and any Ubuntu version does not, although these used to. More curious, I made a Zorin OS boot USB on another notebook and ran this after the grub installer failed. This had a "repair boot" section so I ran this and now Ubuntu 19.10 boots on its own. Very odd. I checked Bios and it has EFI also I see an EFI partition from Ubuntu using disks. I like Linux but am just a novice but overall this behaviour just seems weird. Anyway I'll report back later if this approach turns out to be stable, for whatever reason. Also, is there any way you could remotely inspect and modify this notebook, even just as an experiment? Ian On Sun, Nov 10, 2019 at 4:35 PM Steve Langasek wrote: > The error in your logs is: > > Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning: Cannot set EFI > variable Boot. > Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning: > efivarfs_set_variable: writing to fd 7 failed: Invalid argument. > Nov 9 19:25:47 ubuntu ubiquity: grub-install: warning: > _efi_set_variable_mode: ops->set_variable() failed: Invalid argument. > Nov 9 19:25:47 ubuntu ubiquity: grub-install: error: failed to register > the EFI boot entry: Invalid argument. > > Do you know of a reason that Ubuntu would be unable to write to these > firmware variables, such as a BIOS security setting? > > ** Changed in: shim-signed (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851955 > > Title: > ubuntu 19.10 boot installer failed > > Status in shim-signed package in Ubuntu: > Incomplete > > Bug description: > Installed on an ENVY notebook, installation afiled at the end with no > bootloader message > > ProblemType: Bug > DistroRelease: Ubuntu 19.10 > Package: ubiquity 19.10.21 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu8 > Architecture: amd64 > CasperVersion: 1.427 > Date: Sun Nov 10 08:32:41 2019 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd > quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1851955/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851955] [NEW] ubuntu 19.10 boot installer failed
Public bug reported: Installed on an ENVY notebook, installation afiled at the end with no bootloader message ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Sun Nov 10 08:32:41 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851955 Title: ubuntu 19.10 boot installer failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1228383] Re: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text()
Hi Paul Ubuntu 18.10 runs fine - the only issue it has is to run SciLab - never opens, however on Mint no problem. I've reported this earlier. Ian On Wed, Dec 5, 2018 at 3:30 AM Paul White <1228...@bugs.launchpad.net> wrote: > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. > > Do you still see a problem related to the one that you reported in a > currently supported version of Ubuntu? > > Please let us know if you do. Alternatively, this bug report can be left > to expire in approximately 60 days time. > > Thank you for helping make Ubuntu better.related > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: gdebi (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1228383 > > Title: > gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() > > Status in gdebi package in Ubuntu: > Incomplete > > Bug description: > gdebi-gtk crashed on notebook turn-on (not used, but might have had > unfinished business with virtualbox?) > > ProblemType: Crash > DistroRelease: Ubuntu 13.10 > Package: gdebi 0.9.1ubuntu1 > ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 > Uname: Linux 3.11.0-8-generic x86_64 > ApportVersion: 2.12.4-0ubuntu1 > Architecture: amd64 > Date: Fri Sep 20 17:36:02 2013 > ExecutablePath: /usr/share/gdebi/gdebi-gtk > InterpreterPath: /usr/bin/python2.7 > MarkForUpload: True > PackageArchitecture: all > ProcCmdline: /usr/bin/python /usr/bin/gdebi-gtk --non-interactive > /media/ian/Nemesis1/Software/Internet\ Software/Virtualbox/For\ Ubuntu\ > 13.04/virtualbox-4.2_4.2.18-88780~Ubuntu~raring_amd64.deb > ProcEnviron: >LANGUAGE=en_NZ:en >PATH=(custom, no user) >LANG=en_NZ.UTF-8 >SHELL=/bin/bash >TERM=unknown > SegvAnalysis: >Segfault happened at: 0x7ffdb30fef8e : > cmp%rax,(%rdx) >PC (0x7ffdb30fef8e) ok >source "%rax" ok >destination "(%rdx)" (0x) not located in a known VMA > region (needed writable region)! > SegvReason: writing unknown VMA > Signal: 11 > SourcePackage: gdebi > StacktraceTop: >gtk_label_set_text () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 >g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_signal_emit_valist () from > /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 >g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 > Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228383 Title: gdebi-gtk crashed with SIGSEGV in gtk_label_set_text() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1228383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790811] [NEW] package mailman 1:2.1.26-1 failed to install/upgrade: installed mailman package post-installation script subprocess returned error exit status 1
Public bug reported: occured during upgrade from ubuntu 16.04.01 to 18.04.01. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: mailman 1:2.1.26-1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 4 20:34:33 2018 ErrorMessage: installed mailman package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-04-24 (498 days ago) InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: mailman Title: package mailman 1:2.1.26-1 failed to install/upgrade: installed mailman package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-09-05 (0 days ago) ** Affects: mailman (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790811 Title: package mailman 1:2.1.26-1 failed to install/upgrade: installed mailman package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1790811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1785554] Re: BUG: scheduling while atomic: Xorg/865/0x00000100
Hi Joseph I was interested in the upcoming version of Ubuntu and downloaded the latest version from CD image yesterday. I made a USB boot pen drive and used this to install Ubuntu on a HP dv6 notebook. It installed OK and ran. Then I ran the update option and this also completed OK. During installing some software from the repositories the notebook reported a cash. I rebooted the notebook but after waiting a long time, Ubuntu failed to run. I note that the update manager prior failed to update if all update options were selected - I deselected the last option - problem solved. I have installed Ubuntu 18.10 on Virtualbox running on another HP Envy notebook - no problems, but also failed to update if all options are selected. However the OS is stable as a VM on this Envy notebook. A few days previous, I tried an earlier version of Ubuntu 18.10 on a third Acer 5920 notebook - same behavior as first notebook. I am not upset of course and appreciate that Ubuntu is in an early stage - I am happy to try future versions out. Interestingly the latest experimental version of Mint LMDE 3 Cinnamon runs well on both notebooks, also in early days, but seems to have erratic desktop icon placement behavior and Wine / PlayOnLinux is not yet functional I also note that since Ubuntu 18.04. Scilab is no longer functional - will this be updated. I tend to prefer Scilab over Octave but this is not a big issue. In comparison, Scilab, Octave (and also Basic-256) all work perfectly in any version of Mint. Ian On Tue, Aug 7, 2018 at 4:11 AM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.18 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc8 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1785554 > > Title: > BUG: scheduling while atomic: Xorg/865/0x0100 > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > unexpected error > > ProblemType: KernelOops > DistroRelease: Ubuntu 18.10 > Package: linux-image-4.17.0-6-generic 4.17.0-6.7 > ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 > Uname: Linux 4.17.0-6-generic x86_64 > Annotation: Your system might become unstable now and might need to be > restarted. > ApportVersion: 2.20.10-0ubuntu7 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: ian1896 F pulseaudio >/dev/snd/controlC1: ian1896 F pulseaudio > Date: Mon Aug 6 18:02:20 2018 > Failure: oops > InstallationDate: Installed on 2018-08-06 (0 days ago) > InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 > (20180723) > MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC > ProcFB: > > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic > root=UUID=94d4a0a4-084d-4cfe-95ed-d689b51c557a ro recovery nomodeset > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: kerneloops-daemon N/A > RfKill: > > SourcePackage: linux > StagingDrivers: r8188eu > Title: BUG: scheduling while atomic: Xorg/865/0x0100 > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/07/2011 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.29 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 144A > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 65.38 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059B11243010010020100:rvnHewlett-Packard:rn144A:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A: > dmi.product.family: 103C_5335KV > dmi.product.name: HP Pavilion dv6 Notebook PC > dmi.product.version: 059B11243010010020100 > dmi.sys.vendor: Hewlett-Packard > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785554/+subscriptions > -- You received this bug notification because you are a member of Ubuntu
[Bug 1785554] [NEW] BUG: scheduling while atomic: Xorg/865/0x00000100
Public bug reported: unexpected error ProblemType: KernelOops DistroRelease: Ubuntu 18.10 Package: linux-image-4.17.0-6-generic 4.17.0-6.7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.17.0-6-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1896 F pulseaudio /dev/snd/controlC1: ian1896 F pulseaudio Date: Mon Aug 6 18:02:20 2018 Failure: oops InstallationDate: Installed on 2018-08-06 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=94d4a0a4-084d-4cfe-95ed-d689b51c557a ro recovery nomodeset PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux StagingDrivers: r8188eu Title: BUG: scheduling while atomic: Xorg/865/0x0100 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 144A dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.38 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr059B11243010010020100:rvnHewlett-Packard:rn144A:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 059B11243010010020100 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops cosmic kernel-oops staging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785554 Title: BUG: scheduling while atomic: Xorg/865/0x0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745255] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of pac
Public bug reported: random complain no obvious cause ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Thu Jan 25 11:09:58 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental3ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-vvtMT0/10-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-20 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha7 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745255 Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1745255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302342] Re: Ubuntu 1404 b2 - you don't have priviledges to install updates and any system modification is refused
This bug showed today on 2 VMs on Win 8.1 and one native OS on another notebook - after I used software updater. Will this bug allow repair as it prevents updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302342 Title: Ubuntu 1404 b2 - you don't have priviledges to install updates and any system modification is refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1302342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302342] [NEW] Ubuntu 1404 b2 - you don't have priviledges to install updates and any system modification is refused
Public bug reported: This is a serious bug as it stops all updates even corrections! It also stops logging out as this needs priveldges. The only solution is the power switch! Also, even as a VM, rather than as a native OS, this can mean host shutdown. ** Affects: update-manager (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/1302342 Title: Ubuntu 1404 b2 - you don't have priviledges to install updates and any system modification is refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1302342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794475] [NEW] package xemacs21-mule-canna-wnn (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
Public bug reported: Binary package hint: xemacs21 Xemacs package fails to install with synaptic. I've tried downloading the deb package from the Xemacs official site but gdebi has the same problem : package is xemacs21-mule-canna-wnn_21.4.22-3.1_i386.deb and gdebi reports: Error: Dependency is not satisfiable: xemacs21-support (= 21.4.22-3.1) I downloaded xemacs21-support_21.4.22-3.1_all.deb and tried to install with gdebi. I got the message: Error: Dependency is not satisfiable: xemacs21 (= 21.4.22-3.1) Which is a bit of a deadlock. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: xemacs21-mule-canna-wnn (not installed) ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16 Uname: Linux 2.6.32-32-generic i686 Architecture: i386 Date: Tue Jun 7 19:11:43 2011 ErrorMessage: subprocess installed post-installation script returned error exit status 255 InstallationMedia: Ubuntu 10.04.2 LTS Lucid Lynx - Release i386 (20110211.1) SourcePackage: xemacs21 Title: package xemacs21-mule-canna-wnn (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 ** Affects: xemacs21 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794475 Title: package xemacs21-mule-canna-wnn (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794475] Re: package xemacs21-mule-canna-wnn (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 255
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794475 Title: package xemacs21-mule-canna-wnn (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 255 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
