** No longer affects: xserver-xorg-input-synaptics (Ubuntu Quantal)
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To
For me, now the touchpad work after S3 made by menu but it doesn't still
work when I close my MBA.
--
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/968845
Title:
bcm5974 touchpad doesn't
I'm still having issues where after opening my screen, the touch pad
detects single clicks as some kind of move window with handles event.
This is certainly not fixed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Changed in: xserver-xorg-input-synaptics
Status: In Progress = Fix Released
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3
Today scrolling works better (I havn't touched apt/dpkg since
yesterday). But sometimes it triggers a press on the Alt button and
shows the HUD. Quickly scrolling up and down continuously confirms the
bug. It shows and hide the HUD and sometimes enter the menus. You can
see the underlines
Yesterday I finally had time to test what's currently in precise-
proposed, but now the two-finger-scroll is almost unusable. The same
gesture both scroll up and down in Google Chrome. Sometimes it's
extremely sensitive too, which makes it hard just figuring whether it's
scrolling up or down.
I
Hi Steve,
There's actually a couple more fixes for the remainder of the issues.
Since this package resolves some of the issues, I think we should accept
it into precise-updates. Then we can create a new bug to track the
remaining issues.
** Tags removed: verification-failed
** Tags added:
Based on comment #59, I'm marking this SRU verification-failed. Chase,
if you think this is worth publishing as-is, feel free to change it from
verification-failed to verification-done instead.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug
Hi,
I have a Macbook 7,1 with a similar trackpad to the above mentioned Macbook
Air.
My trackpad uses the bcm5974 module, and in the original release of
Ubuntu 12.04, my trackpad stopped working after suspending my computer.
I've recently been looking at the Xorg.conf file and noticed that
The latest precise-propsed packages are an improvement. I'm no longer
seeing single clicks behaving like double-clicks after initiating S3 by
closing the lid. I am however seeing the following behavior: If I
depress the clickpad with one finger and tap a second finger at other
various locations on
Hi Seth, Luke,
I have another fix for when a touch is active and the device is
disabled. I have uploaded it to ppa:chasedouglas/jupiter. Please install
it and retest to see if it fixes your issues.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Chase: I no longer see the double clicks when using tap-to-click, but I
can still reproduce the pointer jumps as described in comment #59.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Hi Luke,
Did you log out or restart after installing the updates? The updates do
not take effect until the X server is restarted.
--
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/968845
Chase, I did both to confirm. The test I use is the network manager's
connect to hidden network and then the dropdown to select previously
connected to hidden networks. First boot it works just fine with
clicking the trackpad as well as tapping. After suspend, clicking always
acts as a double
I'm sorry I had that backwards: I connect to hidden wireless networks
after suspend and clicking works but tapping on the trackpad is like
double-clicking. Sorry for the confusion.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
I updated to the latest proposed xserver-xorg-input-synaptics and still
have the single-click interpreted as double-click problem. So this
does not work for me. Is it working for anyone else?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(SRU Note: due to a launchpad bug it's not possible to add a Precise
task to -synaptics. The current state would be fix-committed!)
--
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/968845
This bug was fixed in the package xserver-xorg-input-synaptics -
1.6.0-0ubuntu1
---
xserver-xorg-input-synaptics (1.6.0-0ubuntu1) quantal; urgency=low
* Update to upstream version 1.6.0
- Bug fixes only
- Fully fixes touchpad bugs on suspend/resume (LP: #968845)
* Drop
** Branch linked: lp:ubuntu/xserver-xorg-input-synaptics
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To manage
** No longer affects: xorg-server (Ubuntu Precise)
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To manage
** Description changed:
xorg-server SRU Justification
=
[Impact]
When a laptop is suspended, X disables the input devices. If X believes the
hardware has a button press when the device is disabled, it will not release
the button on resume and device enabling.
Hello Seth, or anyone else affected,
Accepted xorg-server into precise-proposed. The package will build now
and be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in
** Branch linked: lp:ubuntu/precise-proposed/xorg-server
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To manage
This bug was fixed in the package xorg-server - 2:1.11.4-0ubuntu11
---
xorg-server (2:1.11.4-0ubuntu11) quantal; urgency=low
* Release buttons when device is disabled on suspend (LP: #968845)
- Add temporary patch 508_device_off_release_buttons.patch from upstream
-- Chase
** Description changed:
- I started seeing this immediately after installing updates that included
- xserver-xorg-input-synaptics from 1.5.99.901-0ubuntu2 to
- 1.5.99.902-0ubuntu1 and rebooting.
+ xorg-server SRU Justification
+ =
+ [Impact]
+ When a laptop is
** Branch linked: lp:ubuntu/xorg-server
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To manage notifications about
This bug was fixed in the package xserver-xorg-input-synaptics -
1.5.99.902-0ubuntu5.1
---
xserver-xorg-input-synaptics (1.5.99.902-0ubuntu5.1) precise-proposed;
urgency=low
* debian/patches/204_monotonicise_hw_timestamp.patch:
- Cherry-pick patch from upstream to ensure the
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = Medium
--
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/968845
Title:
bcm5974 touchpad
This bug was partially fixed in xserver-xorg-input-synaptics
1.5.99.902-0ubuntu5.1. Most suspend/resume cycles will complete
successfully now. However, about 10-20% of the time the trackpad will
stop working properly. There are two more patches for xserver-xorg-
input-synaptics and one for
** Bug watch added: freedesktop.org Bugzilla #49161
https://bugs.freedesktop.org/show_bug.cgi?id=49161
** Also affects: xserver-xorg-input-synaptics via
https://bugs.freedesktop.org/show_bug.cgi?id=49161
Importance: Unknown
Status: Unknown
--
You received this bug notification
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=49161.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
I also have this problem though when it wakes from sleep all of the
multitouch gestures still work fine. It is almost as if when awaking
from sleep the touchpad is in a constant state of being pressed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I've indeed now seen this failure mode too. I'll try and get some time
over the next days to do some debugging.
My first thought is that the patch resets the state on suspend (when the
device is disabled). Perhaps there is a similar interaction when the lid
is opened and the device reenabled.
Is
Chase: I added the debug statements as you suggested. When I'm getting
the incorrect behavior the number of touches seen by x-x-i-s is still
correct.
Whether I get a left- or right-click behavior when I push down on the
clickpad definitely seems to correspond to where my finger is on the
Trying to install using with sudo apt-get install xserver-xorg-input-
synaptics/precise-proposed but am getting error E: Release 'precise-
proposed' for 'xserver-xorg-input-synaptics' was not found.
I'd be happy to test the fix so any advice on how to actually install it
from precise-proposed
Are someone up to a patch for this? Or should I create one using the
script from Ubuntu Forums?
--
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/968845
Title:
bcm5974
Hello Seth, or anyone else affected,
Accepted xserver-xorg-input-synaptics into precise-proposed. The package
will build now and be available in a few hours. Please test and give
feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed.
** Branch linked: lp:ubuntu/precise-proposed/xserver-xorg-input-
synaptics
--
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/968845
Title:
bcm5974 touchpad doesn't work
Just tried the new proposed update. The cursor now moves after S3 but
it's also trying to scroll while moving the cursor. The rmmod/modprobe
trick get rid of that problem. I've got two-finger-scroll enabled.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Tags removed: verification-needed
** Tags added: verification-failed
--
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/968845
Title:
bcm5974 touchpad doesn't work after
Did a few tests again and now it works. Not sure how to interpret this.
I guess I just keep testing for a while and if it keep working I'll just
forget about those first tests...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Hi Daniel,
After you upgraded, did you log out and back in, or restart your
computer? The changes would not take effect until you restarted the X
server. That would explain why it didn't fix things at first, and now it
is fixed.
--
You received this bug notification because you are a member of
Yes, I did a full reboot just to be sure. Very weird. I'll keep
testing...
--
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/968845
Title:
bcm5974 touchpad doesn't work
Ok, yet another suspend and touchpad works perfectly. Changed back to
verification-needed and hope for other folks to test it out.
** Tags removed: verification-failed
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Removed SUSPEND_MODULES hack, installed, rebooted and verified that it
all works correctly.
Thanks very much for the proper fix!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I've been having good luck with the proposed fix as well.
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on
3 out of 20 S3's failed here, it was stuck double clicking with a single
click until removing/reloading bcm5974 when it fails. definitely better
than it was.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
For those of us who hit this issue and are proficient programmers
(sarvatt, sforshee, laney, hint hint :), I suggest adding some debug
statements inside the src/eventcomm.c touch handling functions to see
exactly what is going on. The patch that RAOF added for this bug resets
the touch state when
Same problem here on thinkpad edge 13
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir
To manage
Same issue on 4,1 macbook air (11'' 2011) with up-to-date 12.04
installed from one of the daily builds. I haven't installed any
touchpad-related packages so the issue occurs with whatever module comes
by default.
--
You received this bug notification because you are a member of Ubuntu-X,
which
As there was a question on IRC: I really meant to say that for precise
it is okay to have a pm-utils *script* workaround, not that it actually
needs to live in the pm-utils package. It is equally fine to ship it in
x-x-i-s if people prefer. On second thought that actually makes more
sense, as the
** Also affects: xserver-xorg-input-synaptics (Ubuntu Precise)
Importance: High
Status: Triaged
--
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/968845
Title:
Yes, I think a pm-utils snippet is a good enough hack for precise and an
SRU, provided that (1) it has been verified that un/reloading the module
does not introduce more problems than it solves (there were modules
which caused kernel oopses on unloading, or freezes of X or other
processe), and (2)
Seth, thanks for the explanation. Reassigning back to x-x-i-s then.
** Package changed: linux (Ubuntu) = xserver-xorg-input-synaptics
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
Do we have any chance of seeing this fixed in Precise? It's not really
great to break suspend for these users. Can the package (what package is
it?) ship a pm-config.d snippet for the SUSPEND_MODULES workaround to at
least make the situation tenable? We could release note the fact that
it's just
The root cause is the hardware itself. The work around of adding a
SUSPEND_MODULES config file to /etc/pm/config.d should fix the issue for
broken input after resume.
The next question is: what package should this go into? I would suggest
pm-utils since it already has video quirks.
--
You
Same here, but with a particularity I have not seen above. If you click
(not tapping but pressing) and while holding, move the finger, the
cursor moves.
If you change session (to a different user), the cursor works fine
again. If you come back to the original user, the problem reappears.
--
You
@Gorka: That's the exact behavior here as well. Just forgot to mention.
--
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/968845
Title:
bcm5974 touchpad doesn't work after
Hi Gorka,
The cursor moving while the trackpad button is pressed is expected
behavior. It allows for operations like click + drag.
Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
** Summary changed:
- bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
+ bcm5974 touchpad doesn't work after S3 on MacBookAirX,X
** Summary changed:
- bcm5974 touchpad doesn't work after S3 on MacBookAirX,X
+ bcm5974 touchpad doesn't work after S3 on MacBookAir
--
You received this bug
The workaround works nicely to ensure that the touchpad always
functions, but it seems to result in the touchpad being reset so that,
for example, gestures don't emulate mouse clicks, even though I have
them set to; I have to unset and reset the preference in System Settings
to recover the
Also randomly happens on my Thinkpad.
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
To manage
As temporary workaround I recommend using next:
$ echo 'SUSPEND_MODULES=bcm5974' | sudo tee /etc/pm/config.d/mba4,x-touchpad
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
As Chase Douglas said, reloading the usbhid module will get it working.
You can put this into a script to be called by pm-utils. I've provided
the instructions on how to do so in this Ubuntu Forums thread:
http://ubuntuforums.org/showthread.php?t=1952532
You'll just need to edit the script so
I have this same problem on my Macbook Air 3,1 and would be more than
willing to help with testing/debugging. Probably the easiest way is to
apply patches to a PPA and let the community test.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This issue was discussed on irc the other day, and I'm going to attempt
to summarize the findings here.
The MBA has a magnet near the camera, and as the lid is closed this
magnet induces touchpad activity. The resulting stream of input events
from the driver show the start of a multitouch
I don't think asking xf86-input-synaptics to listen to unrelated events
is a good idea. However, there is functionality already present in
synaptics that we may be able to use: the Synaptics Off option.
Syndaemon already uses this to disable the trackpad when the user is
typing on the keyboard. We
** Summary changed:
- bcm5974 touchpad doesn't work after S3
+ bcm5974 touchpad doesn't work after S3 on MacBookAir4,1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided = High
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Assignee: (unassigned) = Chase Douglas (chasedouglas)
--
You
This affects me as well. MacBookPro 5,2.
The mouse cursor is still visible, and I can right-click and get a
context menu, but I am unable to move the mouse cursor around my screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is something that requires some physical testing to ensure it gets
done right. Unfortunately, my Macbook 5,1 laptop won't resume from
suspend, so I can't really develop a fix for this. I'm unassigning
myself.
A workaround is to unload and reload the bcm5974 kernel module:
$ sudo rmmod
Confirmed on 11 Macbook Air after Beta 2 update a few hours ago. Tried
it several times, inspecting xsession-errors each time. Frequently I
received GRAIL WARNING (v3/slice.cpp:GetValues:230): failed to get
touch from frame messages as described in Seth's xsession-errors. On
certain occassions,
--
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/968845
Title:
bcm5974 touchpad doesn't work after S3
To manage notifications about this bug go to:
Attaching xsession-errors from from a session with a non-functioning
touchpad. There are a lot of warnings and some errors.
** Attachment added: xsession-errors
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/968845/+attachment/2964847/+files/xsession-errors
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
75 matches
Mail list logo
