I just woke early with a question. Before I had chance to seek my own
answer my monitor died as the Flicker err bug #1520583 & Bug 1511158
took over.
my G-Partition Editor says the ext 2 file system is 62.65 MiB 26 % used
1) UUID on this 1 t-bit WD hard drive
Flicker err bug #1520583 & Bug 1511158 continues every few hours.
Sometimes PC must be powered off. Screen gets like a Venetian blind;
remains mangled. Depending on severity, I lose work under way.
Because I must turn out results, on 1.20.16, I must set this Mirus
P5GC-MX, BIOS 0314, bought
@ 4 pm cst 1-12-16, Flicker err bug #1520583 rose its head. The PC's
screen again looked like a Venetian blind mangled by a wind.
It self corrected.
My clone P5GC-MX, BIOS 0314, bought 5/27/2007 with 1 tbit WD HD running
15.10 Wily
Eric @ EMAX COMPUTERS tested my hardware saying your PC is
Robie I've gotta ask a higher power's intervention
thx/Seasons Greetings Robie. For now, I don't know which way to turn except
seeing months down the tubes
1. I acknowledge I'm the who lost a few very valuable work when a bug crashed
my PC, which I can't fix whatever has caused my fluttering
new install 1510Wily on 1 WD Tbit, Screen flips & crashes/takes over/dying
fluttering like a wind blown venetian blind
Bug #1520583 [& Bug 1511158] combine as an outflow of a WD 1 T HD that drives
3 other HDs including a 750g maxtor, an 80g seagate and 120 g Seagate.
Question, is the flutter
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
on Nov 24-27 I log in 15.10 Wily 1 T Western Digital produced the
following note, which hasn't been solvable; I don't see a way to restore
bug's behavior; amid this posting on 11-27th 8am cst, the flicker error
pest took over; it close the monitor then w/mouse clicks, the screen
achieved sanity,
being I'm totally unacquainted with bug #1520583, I ask is it a stranger
or a new form of Nvidia related trouble?
bug #1520583 is smacking me when I need freedom to write a missle. Help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
