[Bug 112310] Re: Setting Wacom pen button to double click doesn't work

On Jaunty: While looking at 'tail -f Xorg.0.log' I see that mappins that include a 'dblclick' are ignored while others are not. E.g. the following work: xsetwacom set "Wacom Graphire2 4x5" button2 3 xsetwacom set "Wacom Graphire2 4x5" button1 1 while this one does not: xsetwacom set "Wacom Graph

[Bug 362917] Re: Unable to determine the partition number.

I can confirm that creating a partitiontable with gparted works. -- Unable to determine the partition number. https://bugs.launchpad.net/bugs/362917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs

[Bug 112310] Re: Setting Wacom pen button to double click doesn't work

This is probably related to 570550 "Can't make Wacom button emit double- click when compiz enabled". -- Setting Wacom pen button to double click doesn't work https://bugs.launchpad.net/bugs/112310 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 112310] Re: Setting Wacom pen button to double click doesn't work

Confirming that value 196609 does not work on Ubunu 9.04: e...@oosttop:~$ sudo tail -f /var/log/Xorg.0.log (**) Wacom Bamboo: max y = 9225 (**) Wacom Bamboo: max z = 511 (**) Option "Button2" "3" (**) Wacom Bamboo: button2 assigned to 3 (**) Option "Button3" "196609" (**) Wacom Bamboo: button3 ass

[Bug 410538] Re: Vinagre 2.26.1 won't auth with older VNC servers

I have the same problem. Here is the output of the terminal: e...@oosttop:~$ vinagre --gtk-vnc-debug 192.168.1.55 ** (vinagre:10951): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed gtk-vnc: Expose 0x0 @ 442,420 gtk-vnc: Started background coroutine gtk-vnc: Resolving host 192.

[Bug 1388955] [NEW] POODLE vulnerability because SSL3 can not be disabled

Public bug reported: Please upgrade pound package to the latest mainstream release (2.7d) so that SSL3 can be disabled. SSL3 needs to be disabled because of the POODLE vulnerability. More details around other options on http://www.apsis.ch/pound/pound_list/archive/2014/2014-10/1414097953000 Tha

[Bug 1388955] Re: POODLE vulnerability because SSL3 can not be disabled

The problem has not gone away. I guess this package could use a new maintainer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388955 Title: POODLE vulnerability because SSL3 can not be disabled To