Hi Jim
I'm saying that I installed a beta copy of 64-bit 10.10 and applied the
upgrades as they became available over the next few weeks (using update
manager). The system was stable and I was not aware of any problems
apart from the Shotwell gphoto2 problem. Using synaptic to reinstall
Shotwell d
Hi Jim
I've read and understood your message - I understand the problems of debugging
a fault you can't reproduce. However, giving us a clear statement of where we
are - without making it sound as though we were simple - was really helpful and
much appreciated.
Having said all of that I have ma
I am concerned that this bug has been assigned an importance of "low" or
"unknown". I think it should be higher for the following reasons:- The
bug does not just affect the kensington mouse, it makes Shotwell
virtually unusable for those affected and there is no simple work-
around.
As mentioned
I am also experiencing this problem running Ubuntu 10.10 I would like to
run Shotwell in preference to F-spot or Picasa but, as things stand at
the moment, the problems with the mouse make it virtually unusable.
I tried the gphoto2 autodetect experiment and found that it always
locked up the mouse
Thanks for your e-mail - I'm really grateful that this driver is getting
the attention it needs, I would be very interested to try out the
binaries/modules.
Thanks
Neil
On Fri, 2010-04-09 at 08:31 +, Timo Aaltonen wrote:
> I've merged the waltop kernel driver functionality with the wacom
>
Hmm there are indeed linux drivers available from Waltop with quite
detailed compilation and installation instructions. I will give them a
try and report back. Thanks.
--
WALTOP tablets not supported anymore (with quickfix)
https://bugs.launchpad.net/bugs/392825
You received this bug notification
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41386303/Dependencies.txt
** Attachment added: "InitctlList.txt"
http://launchpadlibrarian.net/41386304/InitctlList.txt
** Attachment added: "ProcAttrCurrent.gz"
http://launchpadlibrarian.net/41386305/ProcAttrCurrent.
Public bug reported:
Binary package hint: gnome-keyring
crash detected automatically and diagnostic data sent by crash manager.
ProblemType: Bug
Architecture: amd64
Date: Thu Mar 18 23:43:04 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-keyring-daemon
InstallationMedia: Ubuntu
You may like to try the alpha2 release of lucid lynx 10.4 - I found that
this solved many of the driver problems I had been experiencing.
--
Waltop Digital Tablet clicks do not work after upgrade 9.04 -> 9.10
https://bugs.launchpad.net/bugs/498008
You received this bug notification because you ar
I have experienced similar problems. I have tested my Aiptek tablet
against the alpha2 release of lucid lynx 10.4 and this seems to solve
the problem.
--
Aiptek tablet only registers as a mouse in /dev/input
https://bugs.launchpad.net/bugs/361693
You received this bug notification because you are
Following some advice from Bryce I have tried using my Aiptek 14000U
with the alpha2 release of 10.4 Lucid Lynx 64-bit. I did a standard
installation and then plugged the tablet into the usb port. Everything
seems ok - the X-server didn't crash, the pointer moves and the mouse
clicks seem to work.
Mark I have two PCs running 64-bit Ubuntu 9.10 and I am trying to
connect an Aiptek 14000U. Out of the box I can draw lines but get no
mouse clicks. I followed you advice and - hey presto - everything worked
fine.
I then tried to replicate the success on the second PC but found that I
had introduc
I can confirm that I have seen the same behaviour with my waltop/aiptek
tablet. Frustratingly it works "out of the box" with 9.04
When trying to use the tablet with Gimp you need to go to
edit/preferences and activate the tablet as an input device. There is a
pull-down menu of available devices. U
Brian
Thanks for getting back to me. My netgear card failed recently so I took
the opportunity to replace it with a Belkin card. This works fine so
this is no longer an issue for me.
The netgear card was only bought in April so I was quite surprised when
it failed after a few months. This leaves
Brian
Thanks for getting back to me. My netgear card failed recently so I took
the opportunity to replace it with a Belkin card. This works fine so
this is no longer an issue for me.
The netgear card was only bought in April so I was quite surprised when
it failed after a few months. This leaves
Public bug reported:
I recently successfully upgraded from Edgy to Feisty. My wifi (Netgear
WG311v3 pci card) was working fine. I the tried to enter settings to
allow the card to access a wpa network rather than wep. In doing so I
found that I could no longer configure the card correctly at all.
16 matches
Mail list logo
