[Bug 786317] Re: wacom intuous3 often fails to draw stroke (release click not recognised?)
Similar problem with Bamboo CTL-460, since I upgraded to Lucid. When released after a stroke, the pointer freezes until I fully separate pen from tablet and re-approach. Then I get a bogus soft dash from the point where I released to the point where the pen re-enters proximity, and the stroke finishes there. This happens to me consistently with my Bamboo on Lucid, with all recent kernel versions (2.6.32 as far as I can tell). It didn't happen when I got my Bamboo and used Ubuntu 9.10 with drivers from "doctorno" PPA, which make no difference on 10.04. No 100% sure at which point it started failing, but most likely after the update. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/786317 Title: wacom intuous3 often fails to draw stroke (release click not recognised?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/786317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 786317] Re: wacom intuous3 often fails to draw stroke (release click not recognised?)
I forgot to mention this happens to me with GIMP, MyPAint, Inkscape and on the desktop itself, and I am using a quite plain XFCE-based Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/786317 Title: wacom intuous3 often fails to draw stroke (release click not recognised?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/786317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 223812] Re: [hardy] Regression: powernowd no longer works with some chipsets
I see. According to you... * The fix is wrong (essentially because it makes the package do what description says). * Package description is wrong (apparently in order to support your previous assertion). * Package name is wrong too, it should be named "anything-is-better- than-powernowd". * Original Debian package must be wrong also. They should be fixing it to accomodate your more accurate idea of right and wrong. What you are proposing is hijacking "powernowd" package for a purpose which would be better acomplished in other ways. (My excuses go to the list readers if I am overextending with this strange issue.) -- [hardy] Regression: powernowd no longer works with some chipsets https://bugs.launchpad.net/bugs/223812 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 69949] Re: SystemToolsBackends seems to be in busy loop
This is happening to me too with Hardy. Very annoying thing, when using "network-admin" to configure an interface (wireless), two instances of SystemToolsBackend.pl get executed and one of them seems to enter a busy loop for about one minute, and configuration settings don't seem to apply completely, at least during that period. While configuring the interface from command line with iwconfig and/or ifup/down, none of this happens. I would scrap the whole system-tools- backend stuff where it not for the nice configuration interface depending on it. -- SystemToolsBackends seems to be in busy loop https://bugs.launchpad.net/bugs/69949 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 223812] Please! - Re: [hardy] Regression: powernowd no longer works with some chipsets
First thing, the mere length of this discussion for such a simple (and well described!) issue is dismaying. What's going on here? I guess it is just too easy to add an opinion... Now, how come "powernowd" init script tries to run "ondemand" INSTEAD of "powernowd"? THIS IS THE ISSUE. I don't really want powernowd, I DON'T moinstall it in the first place... Excuse the capitals, but I thought this discussion needs some clarity. We just need to fix powernowd init script by removing every reference to "ondemand", actually to every other scaling governor which powernowd does NOT use. Let some ondemand lover go and write an ondemand package, instead of messing this one. In other words, we want an init script that does this: 1.- Load "userspace" governor if necessary, as it is the one REQUIRED by powernowd (just read the README). 2.- Run "powernowd" daemon. It can't be as complicated as the current script appears. I mean the current two-script system... Who was the genious around? Now this is the script as I think it should be: simple and direct. And working! Regards, gatopeich.- ** Attachment added: "/etc/init.d/powernowd as it should be" http://launchpadlibrarian.net/16210339/powernowd -- [hardy] Regression: powernowd no longer works with some chipsets https://bugs.launchpad.net/bugs/223812 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 203513] Re: [Hardy] display doesn't go to sleep after today's gnome-power-manager update
Still wrong with gnome-power-manager 2.22.1-1ubuntu4. gnome-power-manager disables DMPS timers. Here is a fast way to reproduce the issue: $ xset dpms 0 0 120 ; xset q | grep Standby Standby: 0Suspend: 0Off: 120 $ gnome-power-preferences [change "Put display to sleep..." setting, then close] $ xset q | grep Standby Standby: 0Suspend: 0Off: 0 -- [Hardy] display doesn't go to sleep after today's gnome-power-manager update https://bugs.launchpad.net/bugs/203513 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
