Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.os.linux.misc > #16659 > unrolled thread

Why suffer the *UPDATE* setback & Hardware view ?

Started byno.top.post@gmail.com
First post2016-01-04 02:17 +0000
Last post2016-01-04 04:41 +0000
Articles 2 — 2 participants

Back to article view | Back to comp.os.linux.misc


Contents

  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

#16659 — Why suffer the *UPDATE* setback & Hardware view ?

Fromno.top.post@gmail.com
Date2016-01-04 02:17 +0000
SubjectWhy suffer the *UPDATE* setback & Hardware view ?
Message-ID<n6ckne$g2$1@dont-email.me>
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.

[toc] | [next] | [standalone]


#16660

FromJohnF <john@please.see.sig.for.email.com>
Date2016-01-04 04:41 +0000
Message-ID<n6ct5q$9n6$1@reader1.panix.com>
In reply to#16659
In alt.os.linux.slackware no.top.post@gmail.com wrote:
<<snip>>
> While running old Slak12.x I noticed that mouse slowing was possible
> by: xset m <Arg1 Arg2> . But not in Slak13 ?!

Don't know about 12 or 13, but that works in 14.1. (Mouse was okay
with wired keyboard/mouse, but way oversensitive with a wireless
pair until I slowed it down.)
-- 
John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )

[toc] | [prev] | [standalone]


Back to top | Article view | comp.os.linux.misc


csiph-web