Comment 55 for bug 625239

@Carl: I'm sorry to say that your suggested changes to /etc/default/grub did not work for me. I noticed that 1920x1080 was not listed when I tried the vbeinfo command from a GRUB command prompt, as suggested in GRUB2 docs/help. I also tried a resolution that *is* listed as supported for me, 1280x800. This one made the splash look pretty, but I still had an error on VT7 and ended up on VT2. I logged out and back in to get on VT8 again, and quickly had another reset occur when simply clicking a button in Chrome. Shortly after this, I tried combining the GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX settings with the vga=799 on the linux line, but I then received very erratic behavior. I think I was booted to VT8, but had a GDM crash then bump me to VT9, and I also ended up getting bounced back to VT8 from VT9 with another GDM crash at some point. So, as it remains, it's still just adding vga=799 to GRUB_CMDLINE_LINUX_DEFAULT (or GRUB_CMDLINE_LINUX) that seems to be the one mysterious workaround for me.

@dino99: I presume you're referring to my comments #43 and #46? I do apologize, as they got off topic, but I was convinced that a file disappeared due to testing workarounds for this bug. Unfortunately, I'd jumped to conclusions and it was merely a silly oversight on my part. Back to the bug ;-)