[Bug 246364] Re: seahorse asks twice for gpg key password
I did some troubleshooting on this issue, because it affects me as well.
The previous comment mentions an upstream bug report, but I haven't been
able to find it, so I'll post this here.
The first time I send a signed message after restarting Thunderbird, I
get prompted twice for my gpg key password. Each subsequent time I send
a signed message within the same Thunderbird session, I am only prompted
once.
I should make it clear that I have my gpg-agent configured with "ignore-
cache-for-signing" enabled. Although upstream states this case is
working as intended, I can suggest a minor code change which would
eliminate the need for the extra password prompt.
As mentioned previously, there are two signing requests to gpg2 during
this first transaction. The first of these ("--clearsign") is signing
the message "Dummy Test" for the sole purpose of detecting which digest
algorithm gpg2 intends to use: it looks for a line such as "Hash:
SHA256" in the output.
One thing I noticed when testing gpg2 on the command line is gpg2
outputs the "Hash: SHA256" line *before* it prompts for the password.
So, the password prompt can be bypassed by adding the argument
"--pinentry-mode cancel" to the gpg2 command line:
$ /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --use-agent --batch
--no-tty --status-fd 2 -t --clearsign --pinentry-mode cancel -u
0xE19CF36DDF865D8405B1E4100B39535099304B41 <<< 'Dummy Test'
[GNUPG:] BEGIN_SIGNING H8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dummy Test
gpg: signing failed: Operation cancelled
[GNUPG:] FAILURE sign 67108963
gpg: [stdin]: clearsign failed: Operation cancelled
Enigmail can then parse the digest algorithm from the output without needing to
bother the user with an extra password prompt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/246364
Title:
seahorse asks twice for gpg key password
To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/246364/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen
I tested metacity version 1:3.18.5-0ubuntu0.1 from xenial-proposed, and confirmed the fix works correctly and with no regressions. Firefox and Thunderbird windows can now be dragged above the top of the screen. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509031 Title: can no longer alt-drag firefox/thunderbird windows above top of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509031] Re: can no longer alt-drag firefox/thunderbird windows above top of screen
I tested by applying the patch against the current Ubuntu Xenial release version of the metacity package (metacity_3.18.4-0ubuntu0.3). I can confirm the patch fixes the regression (it allows me to drag my Firefox and Thunderbird windows above the top of the screen.) So far, I have encountered no new regressions. I also tried building metacity git master, but ran into several unmet dependencies (newer versions of gtk+/glib than what I have installed), so I was unable to complete that test. Thanks for looking into this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509031 Title: can no longer alt-drag firefox/thunderbird windows above top of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509031] [NEW] can no longer alt-drag firefox/thunderbird windows above top of screen
Public bug reported: After upgrading to 15.10, I can no longer Alt-drag Firefox and Thunderbird windows above the top of the screen. When I attempt to do so, the window snaps downward along the y-axis so that the titlebar aligns with top of screen. Other applications such as gnome-terminal do not seem to be affected. I ran git-bisect on metacity, and narrowed the regression down to this commit: https://github.com/GNOME/metacity/commit/90b36abebdf69be0abaec4015d01e46296f6f5d6 commit 90b36abebdf69be0abaec4015d01e46296f6f5d6 Author: Alberts Muktupāvels Date: Fri Apr 3 23:30:20 2015 +0300 window: add a meta_window_get_titlebar_rect Based on mutter commits: https://git.gnome.org/browse/mutter/commit/?id=3a0af0faaebb1af75925c70ad98e73c61e57639b https://git.gnome.org/browse/mutter/commit/?id=ac099343dab7b5048ce242958c454c55d1924902 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: metacity 1:3.17.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Thu Oct 22 13:35:02 2015 InstallationDate: Installed on 2014-09-22 (394 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: metacity UpgradeStatus: Upgraded to wily on 2015-10-22 (0 days ago) ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509031 Title: can no longer alt-drag firefox/thunderbird windows above top of screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1509031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE
I found a decent workaround: use the main server "archive.ubuntu.com" instead of the mirror. Notice how it includes only the known-good addresses; security.ubuntu.com includes a mix of good and bad hosts, and us.archive.ubuntu.com includes only the bad ones. $ dig +short archive.ubuntu.com 2001:67c:1360:8c01::18 2001:67c:1360:8c01::19 $ dig +short security.ubuntu.com 2001:67c:1562::16 2001:67c:1562::13 2001:67c:1562::14 2001:67c:1562::15 2001:67c:1360:8c01::18 2001:67c:1360:8c01::19 2001:67c:1562::17 $ dig +short us.archive.ubuntu.com 2001:67c:1562::13 2001:67c:1562::14 2001:67c:1562::15 2001:67c:1562::16 2001:67c:1562::17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1412943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE
This affects all of the IPv6 addresses for us.archive.ubuntu.com as well (the addresses are mostly the same as security.ubuntu.com, excluding the two that actually work.) It would be less of a concern if apt automatically fell back on the IPv4 stack, but right now the only way for my machines to receive updates is to manually disable IPv6. This is cumbersome--and in the case of security updates, potentially dangerous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1412943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
The libwnck git master works perfectly. I can also confirm that specific commit (5f88636284154e76611012c8a7c7495b9d917bd7) constitues the fix: applying the diff to libwnck3_3.4.7-3.debian fixes the crash; conversely, reverting the diff on git master reintroduces the crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwnck3/+bug/1293252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
I still get the crash even after removing the window-list applet. I
actually just finished building libwnck3-3.4.7 with this line commented
out in libwnck/xutils.c in the try_pixmap_and_mask() function, and it
successfully prevents the crash. I haven't noticed any side-effects
other than some errors logged to my terminal:
if (mask_surface)
{
//XXX cairo_mask_surface (cr, mask_surface, 0, 0);
cairo_surface_destroy (mask_surface);
}
else
cairo_paint (cr);
*** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293252
Title:
gnome-panel crashed with signal 5 in _XReply()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293252] Re: gnome-panel crashed with signal 5 in _XReply()
Is there anything I can do to help troubleshoot this? I purchased Kerbal Space Program "early access" on Steam this morning, and gnome- panel crashes with this error whenever I try to run the game. This does not happen with the KSP demo, only the full version. A web search suggests this may affect any game that uses the Unity engine, not just KSP. While KSP is running, any attempt to start up gnome-panel results in an immediate crash with this error output: (gnome-panel:7495): Gdk-ERROR **: The program 'gnome-panel' received an X Window System error. This probably reflects a bug in the program. The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 2047 error_code 8 request_code 62 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap I use "gnome-session-flashback" as my desktop environment on Ubuntu 14.10. The default desktop environment does not seem to be affected by this (I tried in a Guest session), but even in the Guest session you can still reproduce the error by attempting to execute "gnome-panel" in a terminal window while KSP is running. If I install libcairo2-dbg and run gnome-panel with the GDK_SYNCHRONIZE environment variable, the crash occurs on line 905 of cairo-1.13.0~20140204/src/cairo-xlib-surface-shm.c when _cairo_xlib_surface_update_shm calls XCopyArea(). According to the XCopyArea docs at www.x.org, "The drawables must have the same root and depth, or a BadMatch error results." Unfortunately I am not versed in X programming, so I don't know what to try next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293252 Title: gnome-panel crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1293252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302736] Re: apt 0.9.15.4ubuntu4 uninstalls ppa:webupd8team/java oracle-java[78]-installer
I just sent an email to the maintainer of the webupd8 packages, asking for him to weigh in. While I agree that removing the sun-java6-jdk Provide from the webupd8 installers would indeed resolve the issue, I'm not familiar enough to know what the possible downside might be of doing so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302736 Title: apt 0.9.15.4ubuntu4 uninstalls ppa:webupd8team/java oracle- java[78]-installer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1302736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302736] [NEW] apt 0.9.15.4ubuntu4 uninstalls ppa:webupd8team/java oracle-java[78]-installer
Public bug reported:
This morning's update to the "apt" package (0.9.15.4ubuntu4) adds sun-
java6-jdk to the Breaks/Replaces list for apt. This unfortunately
creates a conflict with oracle-java7-installer / oracle-java8-installer
from ppa:webupd8team/java, both of which "Provide" sun-java6-jdk:
apt (0.9.15.4ubuntu4) trusty; urgency=low
Cherry pick fixes from the apt 1.0 branch:
[ Michael Vogt ]
* add sun-java{5,6}-jdk to breaks/replaces as that provided a "apt"
binary as well
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 0.9.15.4ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 4 13:38:24 2014
InstallationDate: Installed on 2011-07-09 (1000 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
SourcePackage: apt
UpgradeStatus: Upgraded to trusty on 2014-03-16 (18 days ago)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302736
Title:
apt 0.9.15.4ubuntu4 uninstalls ppa:webupd8team/java oracle-
java[78]-installer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1302736/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi
This issue no longer affects me. The problem went away when two changes were made to the wireless network over the span of about a week. I don't know which change actually fixed it, but I suspect it was the second of the two: One change was updating the firmware on the access points. In the other, a misconfiguration was corrected where DHCP was issuing gateway addresses outside of the subnet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 220327] Re: Stack smashing detected: ./eggdrop terminated
I ran into this error message yesterday when setting up a new Eggdrop bot. I'm posting to this ticket rather than creating a new bug report in case the two issues are related. My crash happens every time the "md5" TCL function is called. The crash can be reproduced with this simple config file: #! /usr/bin/eggdrop md5 "crash!" Removing patch "debian/eggdrop-1.6.19-ssl.patch" (aka "Rootie's SSL patch") fixes the issue for me. The error in the SSL patch is it changes src/tclmisc.c to include OpenSSL's declaration of the MD5_CTX struct, but still uses the bundled versions of MD5_Init/MD5_Update/MD5_Final in src/md5/md5c.c. Because the structs are different size (OpenSSL's is much smaller), the bundled MD5 functions end up smashing the stack. It may also be possible to fix the issue without sacrificing the SSL patch, by ensuring that src/md5/md5c.c is not built or linked into the executable. FWIW, the Eggdrop folks recommend against using Rootie's patch: http://www.eggheads.org/news/2011/05/25/39 I confirmed the crash exists on 1.6.19-1.2ubuntu3.1 (12.04 LTS) and 1.6.19-1.2ubuntu7 (13.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/220327 Title: Stack smashing detected: ./eggdrop terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eggdrop/+bug/220327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi
I have a Dell Precision M4600 with Ultimate-N 6300 (rev 35), and have
had this sort of problem for quite some time. It generally happens with
networks where there are many access points, and many people connecting
to the network (at work, at hotels, etc.)
A workaround which has been reliable in getting me connected to the
wireless network at work is to run this script in a terminal window
while NM is trying to associate with the network. For whatever reason,
running "iwconfig wlan0 essid WhateverSSID" at the right moment during
association makes it succeed for me. (On the other hand, it sometimes
causes a kernel NULL pointer derefernce in __cfg80211_mlme_deauth,
which means I have to hard-shutdown the machine.) I would be interested
in knowing if this script helps anybody else.
#! /bin/bash
connection_id="The SSID of your network"
interface="wlan0"
polls=90
interval=1
change_status() {
tput dl1
tput cr
echo "$1"
}
check_connection() {
if nmcli con status id $1 | grep -q '^GENERAL.STATE:.*activated'
then
change_status Activated
exit 0
fi
}
check_connection "$connection_id"
for (( i = 1; i <= $polls; i++ ))
do
echo -n .
sudo iwconfig "$interface" essid "$connection_id"
sleep "$interval"
check_connection "$connection_id"
done
change_status '???'
exit 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924082
Title:
NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino
Ultimate-N 6300 iwlwifi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 877803] Re: network-manager forgets wireless password after I cancel connection
This also affects me, ever since upgrading to Oneiric. What I would like the behavior to be: Only update the keyring after successfully authenticating to the wireless network. This would protect good keys from temporary failures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/877803 Title: network-manager forgets wireless password after I cancel connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/877803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Hi Seth, Thanks for your work on this. I'm trying out 0.9 right now, and ran into a problem (Dell Precision M4600). It was working fine for about 40 minutes, until the driver (apparently) lost synchronization with the event data. The mouse pointer began jittering slightly, without me touching the touchpad. Putting my finger on the touchpad generated stray click events and wild movement of the pointer. Doing an rmmod+modprobe restored it to proper behavior. Nothing interesting was written to the kernel log. (The first time loading the module after building 0.9) [400791.992874] alps.c: E6 report: 00 00 64 [400792.011962] alps.c: E7 report: 73 02 64 [400792.456794] alps.c: E6 report: 00 00 64 [400792.476472] alps.c: E7 report: 73 02 64 [400792.590917] alps.c: trackstick E7 report: 42 02 3c [400792.976807] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input26 [400792.990906] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input27 (Reloading the module after it desynchronized) [403319.694156] alps.c: E6 report: 00 00 64 [403319.713112] alps.c: E7 report: 73 02 64 [403320.165631] alps.c: E6 report: 00 00 64 [403320.185529] alps.c: E7 report: 73 02 64 [403320.306583] alps.c: trackstick E7 report: 42 02 3c [403320.711547] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input28 [403320.726815] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input29 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606238] Re: synaptic touchpad not recognized on dell latitude e6510
*** This bug is a duplicate of bug 550625 *** https://bugs.launchpad.net/bugs/550625 ** This bug has been marked a duplicate of bug 550625 Alps touchpad is recognized but synaptics clients and scrolling do not work * You can subscribe to bug 550625 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+subscribe -- synaptic touchpad not recognized on dell latitude e6510 https://bugs.launchpad.net/bugs/606238 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606448] Re: synaptic touchpad not recognized on dell latitude e6510
*** This bug is a duplicate of bug 550625 *** https://bugs.launchpad.net/bugs/550625 ** This bug is no longer a duplicate of bug 606238 synaptic touchpad not recognized on dell latitude e6510 ** This bug has been marked a duplicate of bug 550625 Alps touchpad is recognized but synaptics clients and scrolling do not work * You can subscribe to bug 550625 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+subscribe -- synaptic touchpad not recognized on dell latitude e6510 https://bugs.launchpad.net/bugs/606448 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Sorry that I haven't had the time to follow up on this in a while. If upstream is holding out for multitouch specs, then I wouldn't hold my breath waiting. From what I could tell, when I looked at it, the multitouch support in Windows is handled by the user-space driver, and not by the hardware. So if we want that support, we're on our own. I've decoded enough of the protocol that a full-featured driver can be written (with the possible exception of sensitivity adjustment; though based on the Windows driver initialization, that *might* be the job of registers 0x14d and 0x163.) But the implementation will need to handle basically everything: tapping, dragging, scrolling, gestures, etc. @mättu (#183): Try setting register 0x0005 to the value 0x03 (IMPS emulation + Disable hardware tap) -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Here's a patch against 2.6.35. I moved the reset out of initialization and into disconnect, and rewrote the "PSMOUSE_IMPS" hack a little differently (the original Dell patch would change psmouse->type, even when it wasn't supposed to do so.) I wonder if this driver should be in its own .c file, separate from alps.c, since the new protocol is so different. Maybe that's something to think about if somebody decides to implement the 6-byte absolute protocol. I tested docking/undocking from a station with a PS/2 mouse attached, and it behaved more or less sanely. While docked, the touchpad falls back to generic PS/2 mode, however. ** Patch added: "2.6.35-alps-730264-imps-emulation.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/1505124/+files/2.6.35-alps-730264-imps-emulation.patch -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Attached updated psmouse.ko for x86_64 ** Attachment added: "psmouse module (x86_64, 2.6.32-24-generic) with working suspend/resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/1502995/+files/psmouse.ko -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
Back from vacation. I rewrote the Dell patch, and fixed the suspend/resume bug. I couldn't find any way to enable hardware tapping or scrolling within absolute mode -- those features are apparently handled by the driver for this device. So, until software support is written for Linux, we're stuck with IMPS emulation mode. I did, however, figure out how to disable/enable hardware tapping in IMPS mode, and left it as a comment inside the patch. The attached patch is against the Ubuntu-2.6.32-24.40 tag. ** Patch added: "rewritten version of the dell patch that handles suspend/resume" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/1502994/+files/alps-730264-imps-emulation.patch -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
@pvillela I tried suspending, and got the same erratic pointer behavior. Looking at the code, the patch bails out of alps_init() before setting up reconnect/disconnect handlers. The hardware initialization is called from the wrong place (alps_init, instead of alps_hw_init) too, so simply assigning the reconnect handler wouldn't help without further changes. I checked back at the patchwork site, but there were no updates. -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
I applied the Dell patch (I had to modify it somewhat to make it apply cleanly), and verified that it successfully enables vertical scrolling. It still doesn't support syndaemon, but it's a big improvement from what we had before. Attached is a 64-bit psmouse.ko that I built against 2.6.32-24-generic. When I have some time, I'll see about putting together a description of how I used virtualbox to manipulate the PS/2 driver. Here's the short version: # Enable logging in the kbd driver. Output will be written to ~/.VirtualBox/Machines/YourMachineName/Logs/Vbox.log export VBOX_RELEASE_LOG=dev_kbd.e.l.l2.l3.f VirtualBox [--args] Snapshot your VM, just in case. In the VM settings, disable "VT-x/AMD-V" (System -> Acceleration), then start up your VM. The logs will look like: 00:00:10.810 kbd_write_mouse: kbd: write mouse 0xff 00:00:10.810 void kbd_queue(KBDState*, int, int): mouse command response: 0xfa 00:00:10.810 void kbd_queue(KBDState*, int, int): mouse command response: 0xaa 00:00:10.810 void kbd_queue(KBDState*, int, int): mouse command response: 0x00 This is the Windows driver conversing with VirtualBox's mouse emulation code (virtualbox-ose-3.1.6-dfsg/src/VBox/Devices/Input/DevPS2.cpp). >From that point, I replaced the kbd_write_mouse() function with my own version which, instead of emulating a mouse, would blindly reply to mouse commands by returning bytes from a hard-coded array. When it runs out of array data, reply to all further commands with 0xFA (OK). At first, I started with an empty array of responses. Then I went through many iterations of: 1) Boot up the VM. Figure out what the Windows driver is trying to do next, after exhausting my array of reply data. Power off the VM. 2) Switch to Linux, send that new command to my touchpad via the serio_raw driver (see the script I posted to https://bugzilla.kernel.org/show_bug.cgi?id=14660). Read the touchpad's response, and add it to the end of my array. 3) Rebuild VirtualBox (debian/rules build), install the updated .so files (VBoxDD*.so) to /usr/lib/virtualbox. 4) Repeat. ** Attachment added: "psmouse module (x86_64, 2.6.32-24-generic) with dell patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/550625/+attachment/1488476/+files/psmouse.ko -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
I have the "73 02 64" multitouch/dualpoint device on my Dell E6510. In a very manual process of modifying the virtualbox-ose PS/2 driver, and copying bytes between it and /dev/serio_raw0, I managed to piece together the initialization sequence performed by the Windows driver. The entire sequence, from boot-up, is attached. I also included raw event data for three different finger swipes: left-to-right across the middle, top-to-bottom across the middle, and top-to-bottom across the right-edge scroll area. Hopefully this helps in decoding the new protocol. ** Attachment added: "Alps 73-02-04 full initialization sequence, and sample raw event data" http://launchpadlibrarian.net/53451066/ALPS-730264-initialization-and-finger-swipes.txt -- Alps touchpad is recognized but synaptics clients and scrolling do not work https://bugs.launchpad.net/bugs/550625 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
