[Bug 41301] Re: Mouse clicks stop working sporadically
sorry typo, mount = mouse in 2nd paragraph. -- Mouse clicks stop working sporadically https://bugs.launchpad.net/bugs/41301 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41301] Re: Mouse clicks stop working sporadically
I agree with Jethro_UK, this is really a showstopper for using ubuntu as a desktop replacement. I can see the exact same problem as he does, but I have some reservations about somethings: In my experience, using a xterm session, mount appears to be responsive and I can't make mouse button events disappear as they are so easily doing when on a gnome desktop. I can also say that I previously used Gentoo with a KDE desktop and there a very similar problem occurred whereby mouse click events would completely stop. After quite some frustration I found that the only way to resolve that (save logging out/in again) was to alt-ctrl to console terminal and then back to windows and then use alt-next to flip windows. Then mouse clicks started registering again. Initially I have to say that my experience on Gentoo was the worst, but at least there it was something you could work yourself out of, here now on Ubuntu the issue that the desktop feels sluggish and unresponsive. A bit like having to deal with someone who is deaf or can't understand what you are saying. Needless to say, if you have any streak of impatience in you then this is not going to make you hang around for long. So, is there any commonality between KDE/Gnome which could explain this behaviour, which I feel cannot be seen on a straight "window manager less" environment. I'm going to swap over to window manager less for a while to see if the behaviour reappears. Could it be a specific application. I use amarok, could that be it? -- Mouse clicks stop working sporadically https://bugs.launchpad.net/bugs/41301 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 474917] Re: nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic
@Alberto Milone: well you can't do that because it is not a genuine ubuntu package, so I am not sure how to proceed with it. I am not familiar to the Ubuntu defect process and trying to raise something directly on the website doesn't work. Anyhow, the issue I posted appears to be the cause of the issues people have to getting Nvidia (and probably other graphics cards) up and running again. -- nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic https://bugs.launchpad.net/bugs/474917 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 474917] Re: nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic
I think this is the problem with Nvidia during an upgrade to 9.10 from a previous version: libxine1-bin: Depends: nvidia-185-libvdpau but it is not going to be installed This is preventing an upgrade or reinstall of Nvidia properly, because nvidia-185-libvdpau won't be removed with all the other dependencies the libxine1-bin will generate (amarok etc...). Is this an erroneous dependency? -- nvidia drivers 185.xx compile into kernel 2.6.28 instead of 2.6.31 on update from jaunty to karmic https://bugs.launchpad.net/bugs/474917 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
