[Bug 1134881] Re: Crash in LibreOffice Impress when using formulas
Hi Björn, Thanks for taking a look. I upgraded to raring and cannot reproduce the issue under LibureOffice 4.0.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134881 Title: Crash in LibreOffice Impress when using formulas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1134881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1134881] Re: Crash in LibreOffice Impress when using formulas
Ah, I see. I would have set it as Fix Released myself, but I thought perhaps there would be some slight degree of interest in back porting the fix to people not running the beta version of Ubuntu. Sorry to waste your time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1134881 Title: Crash in LibreOffice Impress when using formulas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1134881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 704232] Re: can´t resize side pane
I have also ran into the bug on Precise 12.04 LTS, which is really a shame for an LTS release. However, I have found a work around that resets the side pane for an afflicted PDF file. If you can not longer make the size pane smaller: [1] Close the offending PDF if it is currently opened in evince [2] At the command line: $ gvfs-set-attribute afflicted_file.pdf metadata::evince::sidebar_size 100 [3] Reopen PDF and enjoy. Hopefully this helps somebody a bit until a solution can be reached with regards to hscrollpolicy that finds its way into the official repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/704232 Title: can´t resize side pane To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/704232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
** Changed in: ubiquity (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Richard, thank you for your contributions. Good to know I was not the only person with this bug. I agree. Setting this bug back to invalid. ** Changed in: ubiquity (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 860821] Re: gcalctool crashed with signal 5 in g_simple_async_result_complete()
Encountered when switching from financial to programming mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/860821 Title: gcalctool crashed with signal 5 in g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/gcalctool/+bug/860821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
I have performed some more work towards this issue and I have found that it is an issue not with the kernel but with the generation of initrd.img. Ubuntu-3.2.0-20-generic is the kernel I received upon initial install via CD-ROM. This kernel came with the proper initrd.img-3.2.0-20-generic image. update-grub detects both kernel and ramdisk image correctly, and the system boots fine. Ubuntu-3.2.0-21-generic and Ubuntu-3.2.0-22-generic will installed via repository (normal system update). initrd.img does not exist for either of these kernels. Consequently, update-grub does not generate initrd lines for these kernels and they fail to mount the system partition due to lack of necessary modules. I built Ubuntu-3.2.0-23 from the Ubuntu kernel git repository via: $ fakeroot debian/rules clean $ fakeroot debian/rules binary-headers binary-generic and installed the resulting debs: * linux-headers-3.2.0-23_3.2.0-23.36_all.deb * linux-headers-3.2.0-23-generic_3.2.0-23.36_amd64.deb * linux-image-3.2.0-23-generic_3.2.0-23.36_amd64.deb Again, initrd.img-3.2.0-23-generic was never generated for some reason. So, naturally, booting this also failed. I was able to get Ubuntu-3.2.0-23-generic to boot by: 1) making a copy of my working initrd.img-3.2.0-20-generic 2) unpacking it 3) rename lib/modules/3.2.0-20-generic to lib/modules/3.2.0-23-generic 4) repacking 5) moving to /boot/initrd.img-3.2.0-23-generic I know this is a terrible hack, but I am not sure how to generate a proper initrd.img by hand. In short, initrd.img is not being generated after kernel installation by initramfs-tools on my system for some reason. I am not familiar enough with the generation of initrd.img to know where the failure could be. Help is, of course, appreciated in tracking the source of the error. Regardless, this is no longer really a kernel bug and should probably be reassigned or closed/re-opened as appropriate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Yes, I can confirm that on my system the problem is with update- initramfs. After kernel installation, update-initramfs is invoked via /etc/kernel/postinst.d/initramfs-tools. However, initrd.img is not created. In fact, update-initramfs seems to do nothing. Running update-initramfs manually via: $ sudo update-initramfs -c -t -k 3.2.0-21-generic -v Produces no output. Running: $ update-initramfs also produces no output. Not even the usage as in 10.04 LTS. However, I am able to use /usr/sbin/update-initramfs from my working 10.04 LTS partition to generate the initrd.img images. So, it looks like a problem with update-initramfs I tried: $ sudo apt-get clean $ sudo apt-get autoclean $ sudo apt-get --reinstall install initramfs-tools but this did not seem to change anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Final update. After further investigation, it seems that update-initramfs on my 12.04 LTS partition was merely a symlink to /bin/true The real update-initramfs was diverted to /usr/sbin/update- initramfs.distrib I am guessing there was just a hiccup in ubiquity during the install, perhaps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Final-Final update. No guessing. It was ubiquity: $ sudo dpkg-divert --list . . . diversion of /usr/sbin/update-initramfs to /usr/sbin/update-initramfs.distrib by ubiquity . . . ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
For reference, I will post my solution as well. First, I undid the divert performed by ubiquity via: $ sudo rm /usr/sbin/update-initramfs $ sudo dpkg-divert --rename --remove /usr/sbin/update-initramfs Then I was able to generate initrd images for all kernels via: $ sudo update-initramfs -c -t -k all And then updated grub as usual: $ sudo update-grub I have since pulled down a kernel via Update Manager and update- initramfs is now being triggered as intended by /etc/kernel/postinst.d /initramfs-tools, which now generates working boot configurations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
I am removing the 'needs-bisect' tag. It should be noted that in Post #10 I only mentioned building 3.2.0-23, but I also built 3.2.0-9, 3.2.0-20, 3.2.0-21, and 3.2.0-22. All of these build failed to boot due to lack of initrd.img. Naturally, the bisection failed because I could not find a good version since the problem was related to update-initranfs and initrd.img generation... not the kernel. Somebody more knowledgeable than myself should probably move this bug somewhere more appropriate (ubiquity, perhaps?) since it has been shown that this is not a kernel issue, despite being kernel related. ** Tags removed: needs-bisect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Here are the results of the debugging kernel boot. Due to the nature of the issue, the best I could do is camera shots. If there is a trick in this situation for obtaining a full boot log, I would be interested to hear. --- Case 1: (default as per https://wiki.ubuntu.com/DebuggingKernelBoot) recordfail gfxmode text insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos3)' search --no-floppy --fs-uuid --set=root 862bcf01-fc44-4c29-8d08-f8be78763567 linux /boot/vmlinuz-3.2.0-22-generic root=/dev/sda3 ro http://www.tshack.net/tmp/debug.jpg [158 KB] --- Case 2: (case 1 with raid=noautodetect) recordfail gfxmode text insmod gzio insmod part_msdos insmod ext2 set root='(hd0,msdos3)' search --no-floppy --fs-uuid --set=root 862bcf01-fc44-4c29-8d08-f8be78763567 linux /boot/vmlinuz-3.2.0-22-generic raid=noautodetect root=/dev/sda3 ro http://www.tshack.net/tmp/debug_noraidauto.jpg [187 KB] --- Note that using root=UUID=378367a0-4aac-4e08-b078-e708b24ac4d9 does not work either. For kernel 3.2.0-20, update-grub still generates root= using UUID on the kernel line. For 3.2.0.21+ update, root= is more explicitly specified using /dev/xxxyy entries for some reason. Neither specification works for kernels = 3.2.0.21 on my system. I will perform an upstream kernel build as soon as time permits. ** Attachment added: debug_noraidauto.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+attachment/3017093/+files/debug_noraidauto.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
** Attachment added: debug.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+attachment/3017094/+files/debug.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Sorry, the note at the bottom of #4 accidentally included the wrong UUID, but you get the idea. Corrected post reads as follows: Note that using root=UUID=862bcf01-fc44-4c29-8d08-f8be78763567 does not work either. For kernel 3.2.0-20, update-grub still generates root= using UUID on the kernel line. For 3.2.0.21+ update, root= is more explicitly specified using /dev/xxxyy entries for some reason. Neither specification works for kernels = 3.2.0.21 on my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Tried the pre-compiled mainline daily for April 6th 3.4.0 : (from: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/) * linux-headers-3.4.0-999_3.4.0-999.201204060408_all.deb * linux-headers-3.4.0-999-generic_3.4.0-999.201204060408_amd64.deb * linux-image-3.4.0-999-generic_3.4.0-999.201204060408_amd64.deb The results are similar. (See attachment) ** Attachment added: kernel-3.4.0-999-april_6th_2012.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+attachment/3017383/+files/kernel-3.4.0-999-april_6th_2012.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Hi Christopher. No problem. However, I am currently traveling so I will not be able to perform the kernel bisection until I return on Tuesday. I apologize for this delay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] [NEW] Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
Public bug reported: Since 3.2.0-21 the kernel does not locate my hard drive. Consequently, the kernel cannot locate the system partition, which results in a kernel panic -- unable to mount root filesystem. The suggested valid boot devices following this error include only my CD-ROM drive (sr0). Kernel 3.2.0-20 boots fine. Kernel 3.2.0-22 suffers the same problem as 3.2.0-21. Please let me know if I can supply any further/more specific information. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-generic 3.2.0.22.24 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Apr 5 20:44:16 2012 HibernationDevice: RESUME=UUID=35553fcd-9ae3-4e61-8142-e496f4d885d4 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. Precision WorkStation T7500 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=862bcf01-fc44-4c29-8d08-f8be78763567 ro quiet splash RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06FW8P dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd04/20/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T7500 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kernel-request-3.2.0-22.35 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974765] Re: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs
** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974765 Title: Drive not found since 3.2.0-21... kernel panic, unable to mount root fs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972968] Re: Spurious delayed command line output when using gvim and gnome-shell
Confirmed. Precise 12.04 beta2 with latest updates. As a developer who uses Vim everyday - this bug would make 12.04 unusable for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972968 Title: Spurious delayed command line output when using gvim and gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/972968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
+1 Bug needs fixing or checkbox needs to be removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
