[Bug 1575813] Re: Dual boot does not work after upgrade to 16.04
Thanks. As I said, I installed ubuntu 12.10 long time ago and, yes, I used boot-repair at that point. I haven't used it since then and the configuration has been fine through all the previous upgrades (6 of them) until now. It is in this sense that it might be an Ubuntu bug: It used to be fine and the upgrade has broken things. As I mention in a comment above, uncommenting one of the lines in the fstab allowed me to finish the upgrade but not to be able to boot the windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575813 Title: Dual boot does not work after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575813] Re: Dual boot does not work after upgrade to 16.04
Thanks for the help. My laptop came with windows pre-installed. The first ubuntu I installed was 12.10 I do not remember how I did it (I followed a tutorial of the time). I just have been updating the system since then, and everything has worked fine until now. The output from blkid is as follows: /dev/sda1: LABEL="ESP" UUID="5251-F902" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b032ab5d-1a06-4b52-afcb-14954b4b6ab8" /dev/sda2: LABEL="DIAGS" UUID="D8B9-CFAA" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="894a2bd8-619f-406f-9d3a-89583bce90c1" /dev/sda4: LABEL="WINRETOOLS" UUID="D210BAE110BACC2B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="ca0006ab-9fa9-4990-af37-b2979183716d" /dev/sda5: LABEL="OS" UUID="FC48BE7B48BE33EC" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fe43cb74-06a7-4cea-bfb9-eec6d0c8c77d" /dev/sda7: LABEL="PBR Image" UUID="04CEF99BCEF98568" TYPE="ntfs" PARTLABEL="Microsoft recovery partition" PARTUUID="ed4ceb90-ddb0-48f0-a50a-494fa7bc7d06" /dev/sda9: UUID="b22addc5-b969-47bf-a154-f91b6a137dd6" TYPE="ext4" PARTUUID="c294885b-877a-44f8-8ee4-ac06e95db88e" /dev/sda10: UUID="5cc07bc2-7247-40b6-8290-7edef8b4a39d" TYPE="ext4" PARTUUID="2dc51211-b2f4-4f35-9ec8-24f406045e3b" /dev/sda11: UUID="0aa517c8-aed2-446f-91c2-ecb573598a6d" TYPE="ext4" PARTUUID="6cda9a49-4e81-4c03-b267-fc4aefbe8755" /dev/mapper/cryptswap1: UUID="fc121bf9-d660-4721-b51e-d8e13cc14e70" TYPE="swap" /dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="c81f37b4-4bfd-418a-ab28-d79d1b668607" /dev/sda6: PARTUUID="675c3706-0cbd-4878-b725-9e3c1b4c83a5" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575813 Title: Dual boot does not work after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575813] Re: Dual boot does not work after upgrade to 16.04
Nop. Until today I had never touched the fstab file. So Ubuntu has broken things, not me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575813 Title: Dual boot does not work after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575813] Re: Dual boot does not work after upgrade to 16.04
Not so fast. Before filing the bug report I had already checked that. Here is the deal. If I uncomment the second UEFI entry in my fstab and I try to mount /boot/efi it does not work at all. If I uncomment the first it mounts the partition. However, in neither case I can boot the windows. In both cases it complains about not finding b032ab5d-1a06-4b52-afcb-14954b4b6ab8 So, there is definitely something wrong here. I do not understand why there are two UEFI entries in my fstab, by the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575813 Title: Dual boot does not work after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575813] [NEW] Dual boot does not work after upgrade to 16.04
Public bug reported: I upgraded from 15.10 to 16.04. The process was not completed apparently due a problem with shim-signed. I now find the following message every time I try to update the system: Setting up shim-signed (1.12+0.8-0ubuntu2) ... Installing for x86_64-efi platform. grub-install: error: cannot find EFI directory. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: shim-signed E: Sub-process /usr/bin/dpkg returned an error code (1) Furthermore, I have a dual boot system with Windows and Ubuntu but only the latter works. Something seems to have gone south with UEFI. I attach the efibootmgr output. My /etc/fstab looks as follows # # / was on /dev/sda10 during installation UUID=5cc07bc2-7247-40b6-8290-7edef8b4a39d / ext4 errors=remount-ro 0 1 # /boot was on /dev/sda9 during installation #UUID=b22addc5-b969-47bf-a154-f91b6a137dd6 /boot ext4defaults 0 2 # /home was on /dev/sda11 during installation UUID=0aa517c8-aed2-446f-91c2-ecb573598a6d /home ext4defaults 0 2 # swap was on /dev/sda8 during installation #UUID=64342e46-54ea-46bf-826e-5667367e2301 noneswapsw 0 0 /dev/mapper/cryptswap1 none swap sw 0 0 UUID=b22addc5-b969-47bf-a154-f91b6a137dd6 /boot ext4defaults 0 2 #UUID=5251-F902 /boot/efi vfatdefaults0 1 #UUID=b032ab5d-1a06-4b52-afcb-14954b4b6ab8 /boot/efi /dev/sda1: PARTLABEL= defaults0 1 ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Attachment added: "efibootmgr output" https://bugs.launchpad.net/bugs/1575813/+attachment/4649315/+files/efibootmgr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575813 Title: Dual boot does not work after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1575813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943195] Re: xpdf.real crashed with SIGSEGV in GooHash::hash()
The debian package also seems to work for me. I had to install libopenjpeg2 manually, though. BTW, xpdf is essential, for example, if you want to use whizzytex (http://cristal.inria.fr/whizzytex/), since AFAIK it does not support evince. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943195 Title: xpdf.real crashed with SIGSEGV in GooHash::hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/943195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874207] Re: After the upgrade to 10.10 tomboy crashes at start
I fixed it! There was a problem with a couple of packages: I have re- installed liblaunchpad-integration1.0-cil and libgmime2.4-cil. After that it works just fine. Something went wrong during the update... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874207 Title: After the upgrade to 10.10 tomboy crashes at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/874207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874207] Re: After the upgrade to 10.10 tomboy crashes at start
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874207 Title: After the upgrade to 10.10 tomboy crashes at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/874207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 874207] [NEW] After the upgrade to 10.10 tomboy crashes at start
Public bug reported: Every time I run tomboy it crashes. Here is the message I receive when I start it from the command line (I have removed the publickeytoken just in case it was sensitive information...): Missing method SetSourcePackageName in assembly /usr/lib/tomboy/Tomboy.exe, type LaunchpadIntegration.LaunchpadIntegration Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'launchpad-integration-sharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=' or one of its dependencies. File name: 'launchpad-integration-sharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=' at Tomboy.Application.Initialize (System.String locale_dir, System.String display_name, System.String process_name, System.String[] args) [0x0] in :0 at Tomboy.Tomboy.Main (System.String[] args) [0x0] in :0 [ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not load file or assembly 'launchpad-integration-sharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=' or one of its dependencies. File name: 'launchpad-integration-sharp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=' at Tomboy.Application.Initialize (System.String locale_dir, System.String display_name, System.String process_name, System.String[] args) [0x0] in :0 at Tomboy.Tomboy.Main (System.String[] args) [0x0] in :0 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: tomboy 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 15:18:50 2011 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.3) SourcePackage: tomboy UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) ** Affects: tomboy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874207 Title: After the upgrade to 10.10 tomboy crashes at start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/874207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 815055] [NEW] Samsung Galaxy SII not detected
Public bug reported: I use Natty 64 bit. When I connect a Samsung Galaxy SII phone (using the mtp mode, the only one available as far as I know), lsusb detects it: Bus 002 Device 004: ID 2001:f111 D-Link Corp. DBT-122 Bluetooth adapter Bus 002 Device 003: ID 046e:5522 Behavior Tech. Computer Corp. Bus 002 Device 002: ID 058f:9254 Alcor Micro Corp. Hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 007: ID 04e8:6860 Samsung Electronics Co., Ltd Bus 001 Device 005: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader Bus 001 Device 003: ID 0bda:2831 Realtek Semiconductor Corp. RTL2831U DVB-T Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub but according to mtp-detect it is not there: libmtp version: 1.0.6 Listing raw device(s) No raw devices found. Nautilus, however detects it as a camera (standard mtp behavior I guess) but it simply shows folders that are empty... I guess this is the reason why I cannot sync music with Banshee, etc... ** Affects: libmtp (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/815055 Title: Samsung Galaxy SII not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/815055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
