I haven't used that machine in a while, but I don't recall it being a
problem last time I did. I'll close this bug.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is
As of Natty, the Asus EeePC 1201T touchpad has real multitouch support.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/554980
Title:
Two finger scroll not working on all
I have observed this problem with a HP dv2500t running Natty (latest
updates). Manually changing
/desktop/gnome/peripherals/touchpad/touchpad_enabled to true fixed it.
Seriously, what's going on here?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
This bug is still present in Ubuntu 10.10.
--
two-finger scrolling does not work on Asus EeePC 1201T
https://bugs.launchpad.net/bugs/591921
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in ubuntu.
Public bug reported:
Binary package hint: xserver-xorg-video-ati
It appears that MythTV was configured to use XvMC for HD video. After changing
to plain Xv, X does not crash.
Furthermore, it looks like I get [drm:drm_mode_getfb] *ERROR* invalid
framebuffer id in dmesg when the crash occurs.
--
X crashes when attempting to watch HD TV in mythtv
https://bugs.launchpad.net/bugs/666054
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
___
Mailing list:
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
According to reviews on Newegg, this notebook has two-finger scrolling
under Windows. However, I cannot enable two-finger scrolling on Kubuntu
10.04. I have tried loading psmouse with different protocols, but none
have had
** Attachment added: XInput properties for the touchpad
http://launchpadlibrarian.net/50034734/xinput-list-props.txt
--
two-finger scrolling does not work on Asus EeePC 1201T
https://bugs.launchpad.net/bugs/591921
You received this bug notification because you are a member of Ubuntu-X,
which
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50034243/Dependencies.txt
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/50034244/RelatedPackageVersions.txt
--
two-finger scrolling does not work on Asus EeePC 1201T
This bug is still present in Kubuntu Lucid. Does GNOME work around it?
If so, it that documented anywhere? Really, though, if the devices have
to disappear and reappear across the suspend-resume cycle, then the
settings should be saved in the X server. I don't see an upstream bug
about this. I
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: x11-xserver-utils
Running
xrandr --output NO_SUCH_THING --mode NOT_A_MODE
gives an exit code of 0. There is no output called NO_SUCH_THING, so it
should give a non-zero exit code
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/47624862/CurrentDmesg.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47624865/Dependencies.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/47624867/Lspci.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/47624870/Lsusb.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in
apport information
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/47624871/PciDisplay.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/47624876/ProcCpuinfo.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/47624877/ProcInterrupts.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/47624885/UdevDb.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/47624878/ProcModules.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/47624886/UdevLog.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/47624882/RelatedPackageVersions.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is
apport information
** Attachment added: XorgLog.txt
http://launchpadlibrarian.net/47624887/XorgLog.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils
apport information
** Attachment added: XorgLogOld.txt
http://launchpadlibrarian.net/47624888/XorgLogOld.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: Xrandr.txt
http://launchpadlibrarian.net/47624897/Xrandr.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils in
As I said before, this bug is definitely still present in Lucid, but it
doesn't seem to be as much of a problem now that the KDE and GNOME
display tools have improved.
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a
apport information
** Attachment added: monitors.xml.txt
http://launchpadlibrarian.net/47624941/monitors.xml.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: setxkbmap.txt
http://launchpadlibrarian.net/47624944/setxkbmap.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: xdpyinfo.txt
http://launchpadlibrarian.net/47624945/xdpyinfo.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
apport information
** Attachment added: glxinfo.txt
http://launchpadlibrarian.net/47624940/glxinfo.txt
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x11-xserver-utils
It looks like this issue has been addressed, so I am closing this bug.
** Changed in: gsynaptics (Ubuntu)
Status: New = Fix Released
--
configuration of synaptics touchpads should be possible by default, and
gsynaptics should be installed by default on laptops
This bug is still present in Lucid, although there doesn't seem to be
much of a reason to use xrandr for anything other than debugging these
days.
--
xrandr gives incorrect exit code
https://bugs.launchpad.net/bugs/453247
You received this bug notification because you are a member of Ubuntu-X,
Appears to be fixed as of linux-image-11-generic 2.6.32-11.16.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Fix Released
--
[i965gm] screen flickers whenever anything is drawn under KMS
https://bugs.launchpad.net/bugs/499632
You received this bug notification because
This bug does not occur when using 2.6.33-rc4 from the Ubuntu mainline
kernel repository.
--
[i965gm] screen flickers whenever anything is drawn under KMS
https://bugs.launchpad.net/bugs/499632
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Binary package hint: xserver-xorg-video-intel
When using KMS, the screen flickers whenever anything is updated. So,
if there is an animated progress bar, the whole screen flickers like mad
until the progress bar goes away. Also, the screen will turn completely
white after
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37104455/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37104456/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37104457/Dependencies.txt
**
I have obtained another machine with the same hardware as the original
machine, and the problem seems to be solved.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Fix Released
--
DRI fails to initialize when KMS is enabled with radeon driver
I no longer have access to the machine that had this problem, so I
cannot do any further tests. Given Fedora's push for KMS, I suspect
this problem has been fixed upstream.
--
DRI fails to initialize when KMS is enabled with radeon driver
https://bugs.launchpad.net/bugs/399746
You received this
Does anyone know why jcwinnie's workaround works? I use KDE, so I can't
use that workaround.
--
synaptics driver forgets user settings on resume
https://bugs.launchpad.net/bugs/399902
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
Binary package hint: x11-xserver-utils
Running
xrandr --output NO_SUCH_THING --mode NOT_A_MODE
gives an exit code of 0. There is no output called NO_SUCH_THING, so it
should give a non-zero exit code to indicate an error. I would report
this upstream, but
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33791164/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33791165/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33791166/Dependencies.txt
**
I don't understand why it loses the settings. Aren't they stored in
RAM? If not, I think the synaptics driver should cache them and restore
them when coming back from suspend-to-RAM.
Please note that I am NOT asking for it to remember settings across a
shutdown. I have a script that runs on
** Attachment added: X log showing version mismatch error
http://launchpadlibrarian.net/29299922/Xorg.0.log
--
DRI fails to initialize when KMS is enabled with radeon driver
https://bugs.launchpad.net/bugs/399746
You received this bug notification because you are a member of Ubuntu-X,
which
** Attachment added: lspci from affected system
http://launchpadlibrarian.net/29299925/lspci.log
--
DRI fails to initialize when KMS is enabled with radeon driver
https://bugs.launchpad.net/bugs/399746
You received this bug notification because you are a member of Ubuntu-X,
which is
I just now realized that the lspci was run as lspci -vnn, not -vvnn. I
think the information that is present is sufficient, though. If not,
let me know and I will redo it.
--
DRI fails to initialize when KMS is enabled with radeon driver
https://bugs.launchpad.net/bugs/399746
You received this
Public bug reported:
Binary package hint: xserver-xorg-video-radeon
When booting with radeon.modeset=1, KMS works, but X refuses to use DRI due to
a version mismatch:
[dri] radeon.o kernel module version is 2.0.0 but version 1.17.0 or newer is
needed.
When not using KMS, DRI (not DRI2)
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
I use synclient to set my ALPS touchpad to use fake two-finger scrolling
and disable tap-to-click. When I suspend to RAM and resume, two-finger
scrolling does not work, and tap-to-click is enabled. Running synclient
again
47 matches
Mail list logo
