Public bug reported:
I have a server machine with an ASPEED BMC (kernel driver `ast`) and a
Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE
Wayland session or a Gnome Wayland session, it crashes back to the login
screen, with the same innermost level in the traceback.
What I'd l
** Description changed:
- I'm testing out the git version of the fujitsu-tablet driver from here, and X
is crashing when I hit something with the rightmost two buttons (one marked
"fn", another marked "alt".
+ I'm testing out the git version of the fujitsu-tablet driver from the
following page,
On my workplace Thinkpad W530 (Quadro K1000M in discrete-only mode),
"EnableBrightnessControl=1" does in fact expose a working "Backlight" property
via xrandr.
Unfortunately, Gnome is looking for a property called "BACKLIGHT", and falls
back to /sys/class/backlight when it's not found.
See https
Now, why is this other bug, that's talking about getting REAL multitouch
on older touchpads, a duplicate of this bug?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/546697
If we could get real multi-finger, why should we spend any time getting
FAKE multi-finger?
--
er, we CAN get it... if somebody sniffs out what that Windows driver
does to the touchpad.
--
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
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
https://bugs.launchpad.net/bugs/589485
Title:
Ignores physical display size and calculates based on 96DPI
___
** This bug is no longer a duplicate of bug 554980
Two finger scroll not working on all old touchPads (emulation approach).
--
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
To be clear: this bug is not about getting multi-finger support on touchpads
that already claim to support it, but were not working properly.
This bug is also not about using width-based emulation to get fake multi-finger
detection.
This bug report is about sniffing out what, precisely, that mag
This is still true with the Radeon driver in Natty. There's no
BACKLIGHT property exposed on the LVDS interface.
Gnome Power Manager itself now works around it, with gnome-backlight-helper.
KDE also now somehow works around it, as well.
So, the user-facing portion is fixed, but the original prob
Would you mind doing the same sniffing for that special driver I linked
to? That driver really does enable multi-finger detection on touchpads
that have never supported it before, even in Windows!
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/30
No, I am quite absolutely sure that that IS enabling real multi-finger
detection read the comments! It seems to be patching the firmware
of the touchpad, somehow.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You received this bug no
No, I am quite absolutely sure that that IS enabling real multi-finger
detection read the comments! It seems to be patching the firmware
of the touchpad, somehow.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You received this bug no
Anyway, that's not the main issue being discussed on this bug... it's just that
the technique you used would be useful for that, too:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/546697
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.l
This is not a duplicate! The parent bug is about touchpads that already
had multi-finger capabilities in Windows; this bug is about using a hack
to get multi-finger capabilities on ALL touchpads.
Just in case anyone thinks the driver is only doing emulation, try this
in Windows: go to Mouse contr
"new bug"... there's this one I just linked to above!
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/546697
And with that, I am done with this thread here.
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpad.net/bugs/308191
You re
On my laptop, the keys that are handled by the hp_wmi give no scancodes
at all -- they're hardcoded to specific, too-high keycodes such as
KEY_INFO! You have to edit the module source to change them.
Some of the other keys' mappings are handled by udev, though. If the
keymap creators, as shown b
*** This bug is a duplicate of bug 554980 ***
https://bugs.launchpad.net/bugs/554980
Why does nobody believe that it could EVER be possible for a driver to patch
the firmware?
I've said it before, and I'll say it again: that special driver IS NOT FREAKING
EMULATION. IT IS REAL MULTI-FINGER!
*** This bug is a duplicate of bug 554980 ***
https://bugs.launchpad.net/bugs/554980
And before you go saying it IS emulation, try what I described in the
post above, in the debug window, on a real multi-finger touchpad. Then
try it on a "non-multifinger" touchpad with an ordinary driver. Th
I'd appreciate it if somebody would figure out the initialization
sequence for that "magic" driver mentioned in bug 546697 ... there's
absolutely zero activity there.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
The same is true of my HP EliteBook 8530w: the scroll area is literally
only 5mm wide, and the raised border around the touchpad pushes the
"center" of my finger outside that tiny area.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625?comments=all
-- that bug has info on how to trace PS/2 activity via VirtualBox.
Hopefully, it'll be enough to just do that trace with the "unlocking"
driver.
--
enable multitouch support on older touchpads, as supported by driver v15.0.9
Cool now we just need to do that with THIS driver, and we'll get
multi-finger on ALL Synaptics touchpads:
http://www.engadget.com/2010/03/19/synaptics-driver-enables-multitouch-gestures-on-older-trackpads/
--
Multitouch support not available for Synaptics touchpads v7.2
https://bugs.launchpa
This other driver is not emulation -- it adds native multitouch to ANY
touchpad, even ones that didn't originally do multitouch even in
Windows! We just need to sniff out the initialization sequence -- it
seems to be patching the firmware on the fly.
--
Multitouch support not available for Synap
See also: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/612591
It looks like the ClickPad support is to blame... it treats the middle button
as a left or a right, depending on where your finger is.
--
[Maverick] Middle buttons do the same as left buttons
https://bugs.launchpad.net/bugs/63
I've actually noticed that this "backfill" behavior itself seems to cause
glitches on my Intel netbook. When I use the "vacuum" animation for menu
creation, new menus grab bits of the window behind them and drag those bits
along, until the real content finishes appearing. That's exactly what X
Hmm, I seem to have the exact opposite problem: it detects a non-
ClickPad touchpad as a ClickPad, and thus breaks both my ability to use
my real middle button, and my ability to click and drag with the left
button.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/612591
--
TouchPad buttons
** Summary changed:
- [ubuntu 9.04 beta]slow unminimizing with ati card and desktop effects enabled
+ [ubuntu 9.04] slow unminimizing with ati card and desktop effects enabled
--
[ubuntu 9.04] slow unminimizing with ati card and desktop effects enabled
https://bugs.launchpad.net/bugs/351186
You
Hmm, the issue still happens for me with 8.620, on Karmic
(2.6.30-10-generic); I haven't yet tried it on Jaunty. the aticonfig
--acpi-services=off workaround still works.
--
[HD 3650] fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received
I've just discovered something interesting, after some time
experimenting in Karmic -- somehow, I managed to catch a line about
"failed to connect to acpid" just before the crash.
Apparently, the acpi-services part of the fglrx driver explicitly
depends on having acpid up and running by the time X
Another new discovery: with acpi-services on, I save more power than
with acpi-services off, even if both Battery and AC-Power are set to
"low power usage" in amdccle. However, in exchange, having acpi-
services enabled makes suspend fail -- system hangs even before going
into suspend.
--
[HD 36
Slightly better than that is the patch here:
http://www.phoronix.com/forums/showthread.php?t=17731&page=21
Aside from fixing 2.6.30 compatibility, ATI / AMD should replace all
their calls, as shown in Kano's patch; so far, that symbol removal seems
to be the only significant change from 2.6.30 to
hmm, I was mentioning the issue on IRC, and Kano told me to check in
/usr/share/initramfs-tools/scripts/init-top/framebuffer
... and lo and behold, it's hardcoded to load i915:
if modprobe -q intel_agp && modprobe -q i915; then
FB=kms
fi
;;
The so suggested
er, "the so" is me altering a sentence, and then getting sidetracked in
the middle of it. Should be "He".
--
[Mobility Radeon HD] fglrx DRI initialization failed
https://bugs.launchpad.net/bugs/392039
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [Mobility Radeon HD] fglrx DRI initialization failed
+ initramfs scripts hard-coded to load i915; blocks loading fglrx
--
initramfs scripts hard-coded to load i915; blocks loading fglrx
h
Something to consider trying to allow apport to catch Xorg crashes (at the
expense of not getting a stacktrace in xorg log): enable NoTrapSignals in
xorg.conf.
https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-November/006332.html
--
Xorg crashed with SIGSEGV in FatalError() when usin
Public bug reported:
Binary package hint: xorg
I have a Samsung N130 netbook with a multitouch-capable Synaptics 7.2
touchpad, but for some reason, Xorg doesn't see the multi-finger
capabilities that the touchpad offers. I shall attach a debug-info file
from the mouse control panel in Windows (p
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38383987/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38383988/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38383989/Dependencies.txt
** A
... on second thought, this may be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
synaptics/+bug/308191 . I shall attach my synaptics debug info there.
** Attachment added: "SynDiag2010-01-25_16-16-08.log"
http://launchpadlibrarian.net/38384187/SynDiag2010-01-25_
I just reported a bug:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/512589 -- but then realized
it's most likely a duplicate of this bug.
Handy hint for in Windows: go to the mouse control panel and press
"alt-shift-i", and it will give you a debug dialog. I have attached the saved
dia
I've attached a video of my touchpad spazzing out as I try moving around
with two or three fingers. Unfortunately, gtk-recordmydesktop can't
keep up with the desktop drawing under compiz, and I need compiz to get
the "showmouse" flame-ring. Observe how it leaves trails from movements
way too fast
An attempt at making the spazzing more visible: "Annotate" plugin.
I would imagine fixing the multi-finger detection should fix this spazzing
cursor issue.
** Attachment added: "dana_nocrash.profile"
http://launchpadlibrarian.net/38539487/dana_nocrash.profile
--
Multi fingers touch doesn't b
er, attached the wrong file... grr. Sorry about that.
** Attachment added: "out-2.ogv"
http://launchpadlibrarian.net/38539513/out-2.ogv
--
Multi fingers touch doesn't be correctly recognized
https://bugs.launchpad.net/bugs/308191
You received this bug notification because you are a member of
I noticed that, as quickly as the change to gdm fixed it, the next
upgrade of fglrx (not sure which version) re-broke it even after the
init tweak.
--
[HD 3650] fglrx versions newer than 8.543 cause system hang and panic
https://bugs.launchpad.net/bugs/314600
You received this bug notification be
Same issue happens for me with an NV17. I have attached the output of
gdb, with debug symbols installed.
** Attachment added: "nouveau_segfault.txt"
http://launchpadlibrarian.net/43870377/nouveau_segfault.txt
--
Starts in low graphic mode due to segmentation fault at 0xc4
https://bugs.launch
To be fair, I've noticed a similar lag and 100% CPU usage during resize
operations on the ATI open-source driver (hardware: RV635), the Intel
open-source driver (hardware: GMA950), and the nvidia binary driver
(hardware: GF6200 IGP on Athlon64). The ATI binary driver just lags
more severely than
It looks like radeontool fails silently, instead of telling the user to run it
under sudo. I also had to escape the asterisk to pass it to radeontool:
sudo radeontool match \*
Here's my radeontool output on 2.6.34-rc5 kernel from kernel-ppa -- this
is the "broken" case.
I can't seem to recall a
More correctly, I can't remember _whether_ it ever worked before.
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ub
It looks like something similar to option "C" is going on upstream now:
http://lists.x.org/archives/xorg-devel/2010-May/008085.html
--
[Lucid][Ubuntu 10.04][ATI cards] Slow/freeze windows management (resize,
maximise, .etc) with fglrx driver + compositing desktop.
https://bugs.launchpad.net/bugs
To clarify, there are two interacting bugs here: One is that Radeon
doesn't support BACKLIGHT, and the other is that the old HAL-based way
no longer works. The preferred action would be to fix the former,
rather than the latter.
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance: Unde
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/41238121/UdevDb.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
which is s
apport information
** Attachment added: "RelatedPackageVersions.txt"
http://launchpadlibrarian.net/41238115/RelatedPackageVersions.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are
apport information
** Attachment added: "gnome-power-bugreport.txt"
http://launchpadlibrarian.net/41238128/gnome-power-bugreport.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/41238112/ProcModules.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/41238123/UdevLog.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
which is
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/41238111/ProcInterrupts.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubun
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/41238109/Lsusb.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
which is sub
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/41238110/ProcCpuinfo.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/41238078/CurrentDmesg.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X
apport information
** Attachment added: "GConfNonDefault.txt"
http://launchpadlibrarian.net/41238084/GConfNonDefault.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ub
apport information
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41238081/Dependencies.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/41238090/Lspci.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
which is sub
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: gnome-power-manager
With the deprecation of hal, gnome-power-manager must rely on the
BACKLIGHT property in xrandr; however, the ATI open-source drivers seem
not to support this property (r
apport information
** Attachment added: "DevkitPower.txt"
http://launchpadlibrarian.net/41238083/DevkitPower.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu-X,
I've discovered something new (on another laptop):
By installing these drivers on my non-multi-finger-capable laptop, I've
obtained multi-finger support:
http://www.engadget.com/2010/03/19/synaptics-driver-enables-multitouch-gestures-on-older-trackpads/
I had initially thought it had upgraded my t
I can confirm... using the side of one finger, or three fingers
immediately adjacent, does give me just one contact area.
Also, I do still have the "spazzing" issue on the netbook.
--
Multi fingers touch doesn't be correctly recognized
https://bugs.launchpad.net/bugs/308191
You received this bug
Interestingly enough, I've found that the fglrx version in Lucid no
longer gets this panic, even without disabling acpi-services or
modifying GDM's upstart settings. However, the 8.720 driver also has
other regressions, in things such as suspend/resume support. If anyone
still DOES have the issue
66 matches
Mail list logo
