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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
*** 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
*** 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:
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.
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
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
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,
@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
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
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,
25 matches
Mail list logo
