[Bug 1609210] [NEW] package grub-pc-bin 2.02~beta2-36ubuntu3.1 failed to install/upgrade: package grub-pc-bin is already installed and configured
Public bug reported: The computer prompted me to report this issue which rose after upgrading from Ubuntu 14.04 to 16.04. The computer fails to boot unless via recovery mode. Error message bash: Cannot create temporary file from here-document:Read-only file system. Scrolling info includes Failed to create volatile files and Failed to synchronise time. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-pc-bin 2.02~beta2-36ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Wed Aug 3 14:40:29 2016 DuplicateSignature: package:grub-pc-bin:2.02~beta2-36ubuntu3.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package grub-common (--configure): package grub-common is already installed and configured ErrorMessage: package grub-pc-bin is already installed and configured InstallationDate: Installed on 2013-06-22 (1138 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=2ec12a4a-508b-4adb-8d05-721f58cad6b8 ro recovery nomodeset RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: dpkg Title: package grub-pc-bin 2.02~beta2-36ubuntu3.1 failed to install/upgrade: package grub-pc-bin is already installed and configured UpgradeStatus: Upgraded to xenial on 2016-07-31 (2 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609210 Title: package grub-pc-bin 2.02~beta2-36ubuntu3.1 failed to install/upgrade: package grub-pc-bin is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1609210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1142213] Re: emacs23/24 GUI does not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled
>> Olof Staffans (olof-staffans) wrote 22 minutes ago: >> Sorry for my ignorance, but how do I change the theme from oxygen to >> something else? Go into the KDE System settings. Then click "Application Appearance" under the "Common Appearance and Behavior" Then click GTK. I changed the GTK2 theme to Raleigh and the GTK3 to Emacs. I'm not sure which of the two was required but Emacs now works for me. BTW I noticed that emacs-snapshot didn't have this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1142213 Title: emacs23/24 GUI does not start when run in Kubuntu 13.04 with oxygen- gtk theme enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1142213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 475006] Re: can't connect
I had a similar problem. Fixed by running u1sync --authorize after removing the client computer from Ubuntu One via the web interface at https://one.ubuntu.com/account/machines/ -- can't connect https://bugs.launchpad.net/bugs/475006 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
