Bug#628089: modifying brightness with xbacklight result in fast anarchic brightness changes

2011-10-02 Thread ReportBug

Le 24/09/2011 19:25, Julien Cristau a écrit :

On Fri, May 27, 2011 at 06:12:48 +, Adrien Le Guillou wrote:


Package: xbacklight
Version: 1.1.2-1
Severity: grave
Justification: renders package unusable

when using xbacklight to modify brightness (-set, -inc or -dec ) the screen
brightness changes a lot a times and really quickly
(as if xbacklight were searching for the right value)


That's not a bug in xbacklight.  It may be a bug in the samsung
backlight kernel driver though.  Does the same sort of stuff happen if
you change brightness using /sys/class/backlight/samsung/brightness
directly?  Does it still happen with a newer kernel?

Cheers,
Julien

Sorry for my late answer,

I tried to change the brightness using 
/sys/class/backlight/samsung/brightness directly and it works fine, 
although if I install gnome-power-manager I can change the brightness 
without any problems.
About the kernel : I'm using the linux-image-686-pae package (actual 
version is 3.0.0-1) should I try with a more recent one? (I've never 
compile a kernel before).
Furthermore it works fine with xbacklight in squeeze with the 2.6.32-5 
686 kernel.


Cheers,
Adrien





--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e88387e.9040...@gmail.com



Bug#598834: xserver-xorg-input-synaptics: Several improvements to the package

2010-10-02 Thread reportbug
Package: xserver-xorg-input-synaptics
Version: 1.2.2-2
Severity: important
Tags: squeeze

Please add the package libxtst-dev to the package's build-dep list in order
that the syndaemon "-R" option will work, because with this package in the list
the XRecord code will find the way into the daemon binary.


In addition, on my ThinkPad Edge 13 (the Intel CPU configuration) I got
following Xorg error messages:

(II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/event8)
(**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
(**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.7.6.901, module version = 1.2.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(II) Synaptics touchpad driver version 1.2.2
(**) Option "Device" "/dev/input/event8"
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type:
TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/mouse2)
(**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
(II) Synaptics touchpad driver version 1.2.2
SynPS/2 Synaptics TouchPad no synaptics event device found
(**) Option "Device" "/dev/input/mouse2"
Query no Synaptics: 6003C8
(--) SynPS/2 Synaptics TouchPad: no supported touchpad found
(EE) SynPS/2 Synaptics TouchPad Unable to query/initialize Synaptics hardware.
(EE) PreInit failed for input device "SynPS/2 Synaptics TouchPad"
(II) UnloadModule: "synaptics"

After I added the line

MatchDevicePath "/dev/input/event*"

to the file /usr/share/X11/xorg.conf.d/50-synaptics.conf everything works
respectively no errors anymore and the touchpad works fine. Here are the Xorg
messages after my change:

(II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/event8)
(**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
(**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 1.7.6.901, module version = 1.2.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(II) Synaptics touchpad driver version 1.2.2
(**) Option "Device" "/dev/input/event8"
(II) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5472
(II) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4448
(II) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
(II) SynPS/2 Synaptics TouchPad: finger width range 0 - 0
(II) SynPS/2 Synaptics TouchPad: buttons: left right middle
(**) Option "SHMConfig" "on"
(--) SynPS/2 Synaptics TouchPad: touchpad found
(**) SynPS/2 Synaptics TouchPad: always reports core events
(II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type:
TOUCHPAD)
(**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 0
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
(**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
(--) SynPS/2 Synaptics TouchPad: touchpad found
(II) config/udev: Adding input device SynPS/2 Synaptics TouchPad
(/dev/input/mouse2)
(II) No input driver/identifier specified (ignoring)

While I was searching for a solution for this problem, I found a bunch of other
people with the same issue. It seems to be a known thing.



-- Package-specific info:
/var/lib/x11/X.roster does not exist.

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 Sep 26 05:34 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1881152 Sep 20 20:21 /usr/bin/Xorg

/var/lib/x11/xorg.conf.roster does not exist.

VGA-compatible devices on PCI bus:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

/etc/X11/xorg.conf does not exist.

Kernel version (/proc/version):
Linux version 2.6.32-5-amd64 (Debian 2.6.32-24) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Se

Bug#469936: xserver-xorg-input-mouse: mouse sluggish after upgrade (same as 461152? different?)

2008-03-07 Thread gambarimasu+reportbug
Package: xserver-xorg-input-mouse
Version: 1:1.2.3-2
Severity: normal


not sure if this is same or different from 461152.

shortly after i upgraded xserver-xorg-input-mouse to unstable, the
mouse started occasionally being very sluggish to the point of
near-unusability.  a few days before that, i upgraded
xserver-xorg-core and x11-common, so i do not know for sure that it is
the mouse driver.  but it is almost certainly one of those three.

new information:

1.  i use xset m 1/2 because the mouse is far too fast normally.  however,
this does not fix it.

2.  i have a tyan tiger motherboard with dual athlon mp.  this link
suggests that it might be relevant:
http://ubuntuforums.org/showthread.php?t=100165 .

3.  a busy system makes it worse.  i do not know if this is a cpu thing
or a bus thing, or what.

usb wireless mouse, fresh batteries, excellent reception, never any problem.

thanks.


p.s. previous reportbug claimed success, but it did not post?

-- Package-specific info:
Contents of /var/lib/x11/X.roster:

/var/lib/x11/X.md5sum does not exist.

X server symlink status:
lrwxrwxrwx 1 root root 13 2007-11-27 16:58 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 1673980 2008-01-31 21:06 /usr/bin/Xorg

Contents of /var/lib/x11/xorg.conf.roster:
xserver-xorg

VGA-compatible devices on PCI bus:
01:05.0 VGA compatible controller: Matrox Graphics, Inc. MGA G550 AGP (rev 01)

/etc/X11/xorg.conf does not exist.

Xorg X server log files on system:
-rw--- 1 root root 36628 2007-11-28 19:16 /var/log/Xorg.3.log
-rw--- 1 root root 25992 2008-01-27 23:28 /var/log/Xorg.2.log
-rw--- 1 root root 25987 2008-01-31 15:18 /var/log/Xorg.1.log
-rw--- 1 root root 27977 2008-02-25 16:25 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file
/var/log/Xorg.0.log:


-- System Information:
Debian Release: lenny/sid
Architecture: i386 (i686)

Kernel: Linux 2.6.24myver-2-first (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xserver-xorg-input-mouse depends on:
ii  libc6  2.7-6 GNU C Library: Shared libraries
ii  xserver-xorg-core  2:1.4.1~git20080131-1 Xorg X server - core server

xserver-xorg-input-mouse recommends no packages.

-- debconf-show failed



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#412287: xserver-xorg-input-joystick: Failed to load module "joystick" (out of memory[...])

2007-02-25 Thread reportbug
On Sun, Feb 25, 2007 at 11:22:06AM +0100, Brice Goglin wrote:
> 
> I see several reports like this one in google, but I didn't find any
> solution.

I know :)

> Are you sure /dev/input/js0 is the right device? Does reading from it
> (with "cat /dev/input/js0", maybe as root) while moving the joystick
> generate garbage chars in your terminal ?

I'm sure it's the right device in my case. The joystick works OK using for
instance the joy2key package



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#372079: xserver-xorg-video-mga: can i help?

2006-06-18 Thread gambarimasu+reportbug
Package: xserver-xorg-video-mga
Followup-For: Bug #372079


i have been using the linux console for a while now.  i tried
downgrading to xfree86, but that broke the package manager (signal 11,
baby).  i'm hoping i won't have to install sarge or even ubuntu (to
see if they have a solution for g550 dvi).

so is there anything i can do to provide information to help with
this?

i note that the severity was downgraded, but i don't know why.

it would help if i knew a little more about the status of this driver
so that i could decide whether to steal drivers from ubuntu, tweak a
few settings, etc.

thanks.

-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16myver
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#372079: xserver-xorg-video-mga: strange frequency behavior with dvi

2006-06-08 Thread gambarimasu+reportbug
Package: xserver-xorg-video-mga
Version: 1:1.2.1.3.dfsg.1-2
Severity: grave
Justification: renders package unusable


i just upgraded from xfree86 4.2 to xorg 7.0.  this driver seems to
output frequencies that are out of range for the monitor when the
monitor's documented ranges are entered in the horizsync line.

the documented ranges worked perfectly with 4.2, although that was
probably using matrox's proprietary driver.

when the horizsync line is reduced to a narrow range of frequencies,
there are strange -dpi and font behaviors.  everything is ugly and
many things are not resizable by -dpi and far too large.  for example,
gkrellm is too large and unaffected by the -dpi option to the x
server.  small fonts are impossible to read in most cases, even when
the font path is identical to 4.2.  strangely, i don't think i changed
xfs at all.  xorg.conf is the same as xf86config-4 was otherwise.
configuring via debconf and via mgapdesk result in the same behaviors.

it's possible that some of these are software changes in the way x
works since 4.2 and have nothing to do with the frequency issue or
even the driver.  i have no idea whether frequency changes or the
driver are the cause or not.

i arrived at the narrow range by trial and error.

card=g550
output=dvi
monitor=sony lcd

HorizSync35.0 - 38.0 #far narrower than the monitor supports
VertRefresh  52.0 - 60.0

i will provide xorg.conf, x server logs, monitor specs, or any other
data -- just ask.  i don't know which would be helpful and don't want
to clutter the bug report with non-useful data.

thanks.

p.s.  severity set to grave because i'm not sure which of the
following i should do.  i cannot use the driver as it is now.  if this
is incorrect, please reassign.

o downgrade to xfree86
o try to fix bugs
o reinstall etch
o try to install proprietary drivers
o replace card

all are undesirable, but if i can help fix the bug by working around it
and providing data to the people working on the driver, i will.

-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16myver
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xserver-xorg-video-mga depends on:
ii  libc6 2.3.6-13   GNU C Library: Shared libraries
ii  xserver-xorg-core 1:1.0.2-8  X.Org X server -- core server

xserver-xorg-video-mga recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#372067: xserver-xorg-video-mga: Please explicitly say in the package description and man page what the driver is capable of

2006-06-07 Thread gambarimasu+reportbug
Package: xserver-xorg-video-mga
Version: 1:1.2.1.3.dfsg.1-2
Severity: normal


I have not been able to determine whether this package is *supposed* to
work with DVI output on a Matrox G550 card.  Does regular single-head
DVI operation require special Matrox modules?

It would be splendid if the package description would say whether it is
supposed to provide basic DVI functionality or not.

The strategy of just trying it does not work in my case because xorg
is not working for me.  I get signal out of range even with correctly
specified frequency ranges, and even with a bizarre extremely narrow
range of frequencies, X launches but has strange non-resizing -dpi and
extremely ugly font behavior.  (Perhaps it should be obvious to me
whether this means the card is working.)

The man page is unclear.  It says "The second head of dual-head cards
is supported for the G450 and G550" which implies that DVI works
unless there are dual VGA versions of those cards.  But then it says
"[t]hat module ... may be necessary to use the DVI (digital) output on
the G550 " which implies that it might or might not work, and
doesn't say when it might and when it might not.  When might it?

The xorg web sites don't seem to say (there is a broken link), and the
Matrox forums are hideously complicated on the point due to various
versions of xorg and Matrox modules and people who are overclocking
and using special DRI thingies for gaming.

What's a person who just wants basic functionality to do?

So a package description that simply states whether it is supposed to
work or not (and thus whether the user needs to go on a wild goose
chase getting Matrox's unsupported proprietary closed-source black-box
obviously non-dfsg modules to work) would be great.

A hint on what to do if you need the proprietary driver would be
beyond great, somewhere in the fantastic to superlative range.

(I am unsure whether to downgrade to Sarge xfree86 or earlier, forge
ahead fixing xorg, figure out how to use the proprietary driver,
reinstall etch, or replace my card.  Guidance from the package
description and man page would simplify those choices.)

If the driver is slowly picking away at the closed-source, kind of
working and kind of not but expected to improve and would users please
report bugs -- that sort of thing -- that would be good to mention.

Thanks.

-- System Information:
Debian Release: testing/unstable
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16myver
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages xserver-xorg-video-mga depends on:
ii  libc6 2.3.6-13   GNU C Library: Shared libraries
ii  xserver-xorg-core 1:1.0.2-8  X.Org X server -- core server

xserver-xorg-video-mga recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]