[Bug 114441]
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/114441 Title: Gecko Engine does not support the XHTML 1.1 ruby tag To manage notifications about this bug go to: https://bugs.launchpad.net/epiphany-browser/+bug/114441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551949]
I got a question on chat about using SkiaPDF instead of cairo for this and I might as well add what info I have here. SkiaPDF does indeed [have functionality to annotate](https://github.com/google/skia/blob/c0bd9f9fe533a7b8644392240c1250195aaee537/include/core/SkAnnotation.h) the PDFs in generates. However, although we use Skia, we [only made an experimental start on integrating and using SkiaPDF](https://mzl.la/3iZiU7v) as a printing backend. Finishing that off is probably still a fair amount of work. For anyone looking into fixing this bug the expedient way forward is most likely to try porting the functionality from a newer version of cairo to our old, in-tree version, as suggested by Jeff in comment 20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551949 Title: Printing to PDF file loses URLs/links To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551949]
(In reply to kaz from comment #16) > If you're not going to make it work, the least you could do is not fake the > appearance, you know? Would it be difficult to pop up a dialog box or > something? I'm sympathetic to where you're coming from, but this bug is filed against the platform code and is about implementing the missing functionality in the platform code. Platform developers do not make decisions about adding/changing frontend UI such as opening dialog boxes, so you would need to file a new bug against the 'Firefox' component to get that attention. As for the rest of the discussion, from my perspective as a platform dev it adds a lot of text that we have to read through to check we're not missing anything once we get around to trying to fix this bug. The more bugs we have with conversations like that, the more unproductive time is used up reading through comments that don't help inform the development work involved. You're all welcome to comment, but please do keep that in mind and try to keep unnecessary comments to a minimum. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551949 Title: Printing to PDF file loses URLs/links To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889107] Re: Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed
The following shows that the contents of /efi/ubuntu/grub.cfg are broken, and shows my attempt to rerun the contents of that file with corrected values to try to boot. This gets me to a boot menu where I can choose Ubuntu, get the spinning throbber indicating that Ubuntu is loading, but then I get dumped into an '(initramfs)' prompt. grub> ls (crypto0) (proc) (lvm/vg-root) (hd0) (hd0,gpt2) (hd0,gpt1) # Examine first partitions contents: grub> ls (hd0,gpt1) Partition hd0,gpt1: Filesystem type fat, <...> grub> ls (hd0,gpt1)/ efi/ grub> ls (hd0,gpt1)/efi/ ubuntu/ boot/ grub> ls (hd0,gpt1)/efi/boot/ bootx64.efi fbx64.efi mmx64.efi grub> ls (hd0,gpt1)/efi/ubuntu/ grubx64.efi shimx64.efi mmx64.efi bootx64.csv grub.cfg # Examine /efi/ubuntu/grub.cfg grub> cat (hd0,gpt1)/efi/ubuntu/grub.cfg cryptomount -u search.fs_uuid root lvmid// set prefix=($root)'/@/boot/grub' configfile $prefix/grub.cfg # Examine second partition's contents: grub> ls (lvm/vg-root) Device lvm/vg-root: Filesystem type btrfs, UUID - ... grub> ls (lvm/vg-root)/ @/ @home/ grub> ls (lvm/vg-root)/@ dev/ run/ lib32 boot/ lib sbin cdrom/ srv/ media/ usr/ opt/ lib64 swapfile bin home/ etc/ swap/ var/ tmp/ libx32 sys/ mnt/ proc/ root/ # Fix $root # Note: I include parenthesis and append '/@' (since it's BTRFS) - is that okay? grub> echo $root hd0,gpt1 grub> set root=(lvm/vg-root)/@ # Fix $prefix # Note: Given the changes to $root, I don't include parenthesis or "/@" here. grub> echo $prefix (hd0,gpt1)/@/boot/grub grub> ls $prefix error: file '/@/boot/grub' not found. set prefix=$root'/boot/grub' # Now try to boot: configfile $prefix/grub.cfg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889107 Title: Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889107] Re: Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed
Running the following in Terminal early on during the installation gets rid of the 'grub-install' error and subsequent Ubuntu installer crash: sudo sh -c "echo GRUB_ENABLE_CRYPTODISK=y>> /target/etc/default/grub" On booting up the installed system the prompt to enter the password for the encrypted LUKS partition is presented, and the partition is decrypted successfully. However, grub almost immediately fails to boot and I end up at a 'grub>' prompt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889107 Title: Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889107] [NEW] Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed
Public bug reported: I tried to install 20.04, creating the following custom partition layout: nvme0n1259:00 1.9T 0 disk ├─nvme0n1p1259:30 512M 0 part /target/boot/efi └─nvme0n1p2259:40 1.9T 0 part └─cryptdata 253:00 1.9T 0 crypt ├─vg0-root 253:10 1.5T 0 lvm /target └─vg0-vms 253:20 371.2G 0 lvm Everything proceeded fine until I got a popup window with the message: Executing 'grub-install /dev/nvme0n1' failed. This is a fatal error. In the details part of the main installer window was: ubuntu grub-installer: grub-install: error: attempting to install to encrypted disk without cryptodisk enabled. Set 'GRUB_ENABLE_CRYPTODISK=y' in file /etc/default/grub The default install allows the disk to be encrypted with the default partition layout, so presumably it knows how to set up grub to work with encrypted root, and it could be made to be a bit smarter about detecting when a custom partition layout includes encryption and set up grub appropriately? In the meantime, if anyone has any tips on how to get the install to succeed I'd be very grateful to hear them. :) 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 Date: Mon Jul 27 17:19:19 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421) 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/1889107 Title: Installer failed to write grub to EFI, installing to root on logical volume inside LUKS wrapper, then later crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1889107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888065] Re: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling
> Does comment #2 mean the issue is gone for good? No, I just mean that it didn't reoccur after rebooting. Turning on fractional scaling broke things again. The `full-upgrade` thing does appear to have fixed things for good though. Thank you for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888065 Title: [nvidia] Screen dies/black after changing display orientation or enabling fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1888065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888065] Re: Screen dies/black after changing display orientation or enabling fractional scaling
The issue seems gone after a reboot. Theming and colors are back to normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888065 Title: Screen dies/black after changing display orientation or enabling fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1888065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888065] [NEW] Screen dies/black after changing display orientation or enabling fractional scaling
Public bug reported: I upgraded to 20.04 over a month ago and it's been working fine. I have one monitor (external). I tried turning on fractional scaling in the display settings and the screen immediately turned black. I waited, expecting the "confirm changes" prompt to timeout and restore the display. It never did. Next I hard rebooted, but as soon as I'd entered my password to login, the screen went black again. Tried this a few more times. I then booted to a root console and `apt update/upgrade` to get all updates. Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1 to get a virtual console, then back to F2, and a few other things. At some point I was able to log back in. Foolishly I assumed the issue was just with fractional scaling, and back in Display settings I for some reason decided to experiment further and flipped the display orientation to portrate. Immediately I got a black screen and ended back in the same reboot loop, always getting a black screen as soon as I tried to log back in. Searching online I couldn't seem to find a way to revert the display orientation. From another virtual console I was unable to run xrandr or start a wayland session to get to the settings panel. To do that I was trying to run: dbus-run-session -- gnome-shell --display-server --wayland But that's just something I found on the Web, I have no idea what I'm doing there. It just gave the error: (gnome-shell:) mutter-warning: **: Failed to open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted (gnome-shell:) mutter-warning: **: Failed to create backend: No GPUs found Eventually I found a suggestion on the Web to unplug the cable to the display, and after experimenting with that a bit and switching between virtual consoles, at some point it was logged in with a working display ... well, sort of. The colors and icons are weird like it's lost theming or something. Going into the Display settings it seems that the orientation has also been reset to landscape. I'm filing this bug before restarting the machine so I can report the system scan it has taken. At this point I've no idea whether I'll be able to log back in again after a reboot. I'll try that now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:21:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jul 18 17:21:56 2020 DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.4.0-37-generic, x86_64: installed nvidia, 435.21, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107GL [Quadro P400] [1028:11be] InstallationDate: Installed on 2019-11-03 (257 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Z4 G4 Workstation ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago) dmi.bios.date: 03/21/2019 dmi.bios.vendor: HP dmi.bios.version: P62 v01.75 dmi.board.name: 81C5 dmi.board.vendor: HP dmi.board.version: MVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53335X HP Workstation dmi.product.name: HP Z4 G4 Workstation dmi.product.sku: 5FN34US#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau:
[Bug 1065126]
An example of a PDF with Content-Disposition: attachment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551949]
FWIW cairo has [functionality for creating links](https://www.cairographics.org/manual/cairo-Tags-and-Links.html) as of v1.16, but it looks like the in-tree cairo is too old (v1.9.5). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1551949 Title: Printing to PDF file loses URLs/links To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1551949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 526482]
Possibly related is that nsPrintSettingsService::GetGlobalPrintSettings and nsPrintSettingsService::GetNewPrintSettings essentially do the same thing: https://searchfox.org/mozilla- central/rev/8b7aa8af652f87d39349067a5bc9c0256bf6dedc/widget/nsPrintSettingsService.cpp#927 That's probably not the whole story though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/526482 Title: Firefox don't save print settings To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/526482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25830]
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/25830 Title: Option to display file in browser, treat as text/plain To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/25830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237941]
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/237941 Title: Bookmarking Folder Location To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/237941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607643] Re: Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition))
As said in the bug description, it's present in http://cdimage.ubuntu.com/releases/maverick/alpha-2/maverick- dvd-i386.iso As stated in comment 5, the solution is known, and this seems like it's just a case of applying that fix again (I'm guessing somehow the fix got overwritten before Maverick was released). ** Changed in: ubuntu Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607643 Title: Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition)) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606756] Re: GUI setting needed to disable or enable wake from suspend via mouse (or keyboard)
The Power Manager window in 10.10 does not offer options to wake on USB, or as the original reporter (and I) would like, using finer grained device selection. ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Confirmed -- GUI setting needed to disable or enable wake from suspend via mouse (or keyboard) https://bugs.launchpad.net/bugs/606756 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 636711] Re: 10.10 can't mount squashfs file system
This also affects me on my Thinkpad T410. I'm using the 10.10 DVD. This bug has been reported for several major versions now. Given that it's a showstopper, shouldn't this be given high priority? -- 10.10 can't mount squashfs file system https://bugs.launchpad.net/bugs/636711 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 636711] Re: 10.10 can't mount squashfs file system
Ah! While the 10.10 DVD ISO doesn't work, the 10.10 CD ISO - burnt to the EXACT same blank media - does! -- 10.10 can't mount squashfs file system https://bugs.launchpad.net/bugs/636711 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 607643] Re: Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition))
I just discovered an old closed bug for 10.04 that seems to have a solution for my 10.10 install that I created by upgrading from 10.04, and gets me a little (not much) further with installing 10.10 directly (ie clean install) from the 10.10 DVD: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/546393?comments=all I need to add both nouveau.noaccel=1 and blacklist=vga16fb to the boot options. That seems to fix the 10.10 install that I created from the 10.04 upgrade. Adding these same options to the 10.10 installer DVD when it starts get's me past the black screen with the white cursor, and to a purple screen with the text ubuntu and five white dots underneath, with a highlight moving from dot to dot. That's where the 10.10 DVD install stops unfortunately, and in fact the moving highlight from dot to dot also stop eventually, leaving just five white dots. So I'm wondering whether the fix Andy Whitcroft mentions in comment 118 of bug 546393 have somehow been dropped...or stopped working: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/546393/comments/118 -- Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition)) https://bugs.launchpad.net/bugs/607643 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 607643] Re: Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?)
I just took delivery of a new HDD and tried 10.10 again, but this time by trying to go via an update to 10.04 rather than a clean 10.10 install from the 10.10 DVD iso. I managed to install and run 10.04 on my Macbook Pro just fine. Next I updated to 10.10 by running package-manager -d. On rebooting the screen just displayed some funky garbage. The same thing occurs on each reboot. Next I tried holding down 'alt' while booting to get to GRUB and got the following eight options: Ubuntu, with Linux 2.6.35-14-generic Ubuntu, with Linux 2.6.35-14-generic (recovery mode) Ubuntu, with Linux 2.6.32-24-generic Ubuntu, with Linux 2.6.32-24-generic (recovery mode) Memory test (memtest86+) Memory test (memtest86+, serial console 115200) Memory test (memtest86+, experimental multiboot) Memory test (memtest86+, serial console 115200, experimental multiboot) Selecting the first option gave the same problems (presumably because it's the default). The third option boots fine, but into what is apparently Ubuntu 10.04, not 10.10. -- Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?) https://bugs.launchpad.net/bugs/607643 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 607643] Re: Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?)
If I choose the second boot option Ubuntu, with Linux 2.6.35-14-generic (recovery mode) then I get a semi-garbled screen, but there seem to be four lines of output, which are more or less: /dev/sda2: clean, 144711/3055616 files, 982506/12207104 blocks /dev/sda2: recovering journal /dev/sda3: clean, 363/26984448 files, 1754779/107936256 blocks [5.206069] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver Above these lines is a thick (two or three text lines high) red/orange striped bar, and below it a thinner ( 1 line high) blue striped bar. Below the blue bar there are a bunch of different colored dots around the screen. The conflicting fb hw usage nouveaufb vs VESA VGA line led me to these links, but I'm not sure they really help in finding the underlying bug. http://lists.freedesktop.org/archives/nouveau/2010-April/thread.html#5477 http://ubuntuforums.org/showthread.php?p=9617681 ** Summary changed: - Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?) + Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition)) -- Maverick alpha 2 can't install or run on Macbook Pro (5.1 (late 2008 edition)) https://bugs.launchpad.net/bugs/607643 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 607643] Re: Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?)
Note that it is the installer that got stuck very early on for me, not booting. I didn't even get close to having an install I could try to boot. Regarding 10.04, Mac 10.5 wouldn't even burn the .iso to CD for some reason. At that point I pretty much gave up on Linux for this upgrade cycle and decided to stick with Mac for now. If you're interested in pursuing this bug I'd be happy to buy a new HDD and try harder to get 10.04 burn an install to it. I'd be happy to spend time doing other things too to if they're helpful in debugging this issue. I'm on vacation just now, so won't be able to follow up on any of this until early August. Let me know either way if there's something I can do that would be helpful though. -- Maverick alpha 2 can't install on late 2008 Macbook Pro (Plymouth fails to start?) https://bugs.launchpad.net/bugs/607643 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
