[Bug 1179310] Re: Option to edit repositories missing in Synaptic
The header states that this bug affects 1 person (me). This is not srictly accurate as the bug will affect any user who wishes to use Synaptic with a *fresh* install of Kubuntu 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179310 Title: Option to edit repositories missing in Synaptic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1179310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1069049] Re: subprocess installed post-installation script returned error exit status 1
On 22/10/12 22:41, Brian Murray wrote: Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New = Incomplete Sorry, no can do. The bug left me with an unusable system - /boot was empty! - so I re-installed from scratch, including formatting all partitions. Peter HB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069049 Title: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1069049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069049] [NEW] subprocess installed post-installation script returned error exit status 1
Public bug reported: During dist-upgrade from 12.04 to 12.10 Could not install 'grub-pc' after choosing to retain a customised 05_debian_theme ** Affects: ubuntu-release-upgrader (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/1069049 Title: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1069049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501475] [NEW] device.map not correctly updated after update-grub
Public bug reported: Binary package hint: grub2 Adding a new, third SATA disk and installing Mythbuntu (but NOT GRUB) to complement Windows 7 on sda (with GRUB in the MBR) and Ubuntu 9.10 on sdb, followed by update-grub produced a device.map containing: (hd0) /dev/sda (hd1) /dev/sdb (hd2) /dev/sdg Naturally booting from the third drive failed. I have no idea where the 'g' came from, but editing device.map manually to the correct 'sdc' for hd2 restored the boot function. Obviously this action resolved my original problem, but others may encounter this bug hence this report. A secondary question is whether manual editing of device.map is a preferred method, or is there an alternative? ProblemType: Bug Architecture: amd64 Date: Tue Dec 29 20:51:30 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: grub-pc 1.97~beta4-1ubuntu4.1 ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: grub2 Uname: Linux 2.6.31-16-generic x86_64 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- device.map not correctly updated after update-grub https://bugs.launchpad.net/bugs/501475 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 501475] Re: device.map not correctly updated after update-grub
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37278566/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37278567/XsessionErrors.txt -- device.map not correctly updated after update-grub https://bugs.launchpad.net/bugs/501475 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 489926] [NEW] memtest86+ fails to boot when GRUB and the system filesystem are on separate disks
Public bug reported: Binary package hint: grub2 With GRUB in the MBR on /dev/sda and the complete Ubuntu 9.10 system installed on /dev/sdb, selection of memtest86+ in the GRUB menu fails with file not found GRUB version: 1.97~beta4 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- memtest86+ fails to boot when GRUB and the system filesystem are on separate disks https://bugs.launchpad.net/bugs/489926 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
Re: [Bug 489926] Re: memtest86+ fails to boot when GRUB and the system filesystem are on separate disks
Felix Zielcke wrote: just having GRUB in the MBR of a different disk then Linux is on doestn't cause this. Do you have a seperate /boot partition? Then this is a duplicate of 450351 which is already fixed in lucid. Yes, I do have a separate /boot partition, as I do on a single disk installation where memtest86+ loads correctly, leading to my allegedly incorrect diagnosis! -- memtest86+ fails to boot when GRUB and the system filesystem are on separate disks https://bugs.launchpad.net/bugs/489926 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
Re: [Bug 489926] Re: memtest86+ fails to boot when GRUB and the system filesystem are on separate disks
Peter Hillier-Brook wrote: Felix Zielcke wrote: just having GRUB in the MBR of a different disk then Linux is on doestn't cause this. Do you have a seperate /boot partition? Then this is a duplicate of 450351 which is already fixed in lucid. Yes, I do have a separate /boot partition, as I do on a single disk installation where memtest86+ loads correctly, leading to my allegedly incorrect diagnosis! Sincere apologies for the above. I had forgotten that the single disk system is the *only* one I have that doesn't keep /boot in a separate partition. Regards Peter HB -- memtest86+ fails to boot when GRUB and the system filesystem are on separate disks https://bugs.launchpad.net/bugs/489926 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
