Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.os.linux.slackware > #26054
| From | no.top.post@gmail.com |
|---|---|
| Newsgroups | alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian |
| Subject | Why suffer the *UPDATE* setback & Hardware view ? |
| Date | 2016-01-04 02:17 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <n6ckne$g2$1@dont-email.me> (permalink) |
Cross-posted to 3 groups.
Reading these bank-clerk mentality opinions of 'get the latest' [rubber wheels & shoe soles wear out], reminds one of the problem that the original light bulb manufacturers had when they realised that their product lasted too long, and they couldn't sell fresh-milk every day. 2009: Slak13 had a subtle/painfull problem: after non-use, when the display shuts-down, xpdf & others show 'fuzzy' - related to gamma. An older Slak12.x based liveCD has no such problem. After much pain & wasted effort, advice to: xset s off xset -dpms solves the problem. Some year/S later, Slak13's partition 'overflows' & causes CRASH! TextToSpeech generates *BIG* files. Attempts to reinstall Slak13 from the same CD, to other partition/S fail with xorg errors?! BLINDLY copying the /etc/X11/xorg.conf* files from old Slak12.x solves the problem. Has there been a change in the hardware? Did that cup of water spilled over the running MOBO, which took-out the power, cause permanent change, and relate to DebWheezy losing kybrd & mouse when going X? But it's running OK now. While running old Slak12.x I noticed that mouse slowing was possible by: xset m <Arg1 Arg2> . But not in Slak13 ?! But xset is confirmed by xset s off + xset -dpms; being effective, in Slak13 ?! Who would want to *upgrade* with all this punishment? Don't name it an "issue" when it's a PROBLEM.
Back to alt.os.linux.slackware | Previous | Next — Next in thread | Find similar | Unroll thread
Why suffer the *UPDATE* setback & Hardware view ? no.top.post@gmail.com - 2016-01-04 02:17 +0000 Re: Why suffer the *UPDATE* setback & Hardware view ? JohnF <john@please.see.sig.for.email.com> - 2016-01-04 04:41 +0000 Re: Why suffer the *UPDATE* setback & Hardware view ? Doug713705 <doug.letough@free.fr> - 2016-01-04 09:35 +0000
csiph-web