** Summary changed:
- friendly-recovery: failsafeX dialog is completely unusable
+ friendly-recovery: failsafeX dialog is keyboard-hostile (sometimes completely
unusable)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
http
Sorry for the delay. Here are the requested log files in a tarball:
lp1169004-logs/normal/dmesg
lp1169004-logs/normal/Xorg.0.log
-> logs from a normal boot, where X works just fine
lp1169004-logs/failsafe/dmesg
lp1169004-logs/failsafe/Xorg.failsafe.log
-> logs from a recovery boot with failsa
> I've recently installed 13.04 on my laptop, so I'll try it there next.
Good: failsafe-x is no longer completely broken in 13.04. It can now be
controlled with the mouse and keyboard. Hooray!
It still has several bugs, though, which I'll report separately.
--
You received this bug notification
Update on 12.10: it's not just keyboard-unusable, it's also mouse-
unusable. I just tried failsafe-x on my desktop system running 12.10,
and it is completely unusable. X works perfectly on this system, my
mouse is hooked up and working fine, everything is good. Details...
Steps to reproduce:
1) lo
Workaround #1:
> I guess I'll repartition and try installing raring in the new
partition.
success! the bug has been fixed in Ubuntu 13.04. This is still an update
regression with 12.10; my ThinkPad T500 worked just fine on March 31 and
video stopped working on April 13. But at least the next vers
This is starting to look very much like a kernel bug, although I'm still
confused about several things. My main evidence is that I'm having
similar problems with System Rescue CD, a Gentoo-based rescue distro
that boots from CD or USB stick.
In particular, System Rescue CD 3.4.1 (kernel 3.4.32) wo
** Tags added: regression-update
** Summary changed:
- no video after upgrading kernel, mesa, libc, and several other packages
+ regression: no video after upgrading kernel, mesa, libc, and several other
packages (ThinkPad T500)
--
You received this bug notification because you are a member of
Public bug reported:
Steps to reproduce:
1) on 2013-03-31, shutdown laptop for a 2-week vacation
2) on 2013-04-13, return from vacation, boot laptop, and apply pending updates
with update-manager
3) reboot laptop
Expected result: Ubuntu boots just as it did before the update (it
worked fine on 2
8 matches
Mail list logo
