Addendum to Robert Bamler's install procedure in post #82: You can skip
the Raring step and install Saucy directly if you have an external
monitor connected. This bug only affects the internal monitor. Then
install the fixed kernel packages and reboot.
Also, like Mr. Bamler, I'm interested in know
I don't know why this is considered of medium importance, since it's a
duplicate of a bug with importance level High.
https://bugs.launchpad.net/ubuntu/saucy/+source/linux/+bug/1195483
Anyway, this affects the internal monitor only, and there's a new test
kernel posted that works (post 72 of the o
Cool! Now that this is fixed, will it be a part of a kernel update with
simple apt-get dist-upgrade? I assume now that stable 13.10 is out, this
didn't arrive in time for that. I assume the best strategy for a n00b
end user like me wanting to upgrade to Saucy would be installing stable
13.10 with e
Thanks for your response. I haven't tried every kernel, but it was
definitely fine on Ubuntu-Gnome 13.04, and in the report linked above
another user says this: "I booted with kernel 3.11.0 which is the
earliest I found that exhibits this problem." A Fedora user -
https://ask.fedoraproject.org/ques
Public bug reported:
Duplicate of this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195483
I`ve tried every version of Saucy and daily builds of Fedora, and all
newer Linux kernels seem to cause this problem on the Asus UX31a laptop.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Pac
Problem still persists on daily 13.10 Saucy mini.iso. I have a slightly
different computer (Shuttle XS35GSV3 with AMD GPU), but same network
hardware. No point in posting logs or details, as problem is exactly as
described here by several people over the last two years, and in other
threads around
