[Ubuntu-x-swat] [Bug 1212736] Re: Touch screen: Right click should be emulated by long press, like under Windows 8 and Android

2016-04-12 Thread Francesco Fumanti
The click and hold to simulate a right click used to send the virtual right click before button release until march 2010. Changes in the X server forced the mousetweaks developer to move the virtual right click after the button release because as far as I understand, the X server stopped accepting

[Ubuntu-x-swat] [Bug 998748] Re: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/998748 Title: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build To manage notifications about this

[Ubuntu-x-swat] [Bug 998748] [NEW] nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
Public bug reported: The problem occurred during the upgrade from precise to quantal. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: nvidia-current 295.49-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia

[Ubuntu-x-swat] [Bug 998767] [NEW] nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
Public bug reported: This happened after upgrading from precise to quantal. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: nvidia-current 295.49-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-1.3-generic 3.4.0-rc5 Uname: Linux 3.4.0-1-generic x86_64 ApportVersion: 2.0.1-0ubuntu7

[Ubuntu-x-swat] [Bug 998767] Re: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/998767 Title: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build To manage notifications about this

[Ubuntu-x-swat] [Bug 998767] Re: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
*** This bug is a duplicate of bug 993506 *** https://bugs.launchpad.net/bugs/993506 ** This bug has been marked a duplicate of bug 993506 nvidia kernel module fails to build on 3.4.x kernel [fatal error: asm/system.h: No such file or directory] -- You received this bug notification

[Ubuntu-x-swat] [Bug 998748] Re: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-13 Thread Francesco Fumanti
*** This bug is a duplicate of bug 993506 *** https://bugs.launchpad.net/bugs/993506 ** This bug has been marked a duplicate of bug 993506 nvidia kernel module fails to build on 3.4.x kernel [fatal error: asm/system.h: No such file or directory] -- You received this bug notification

[Ubuntu-x-swat] [Bug 837456] Re: [Oneiric] XTestFakeKeyEvent changes keyboard mapping to 'us'

2012-02-12 Thread Francesco Fumanti
Could you please tell us whether you still get the correct layout with your work around after restarting the computer without doing any new manipulation in the keyboard settings? I have three layouts defined without the US layout; when I change something in the keyboard settings, I get the

[Ubuntu-x-swat] [Bug 837456] Re: [Oneiric] XTestFakeKeyEvent changes keyboard mapping to 'us'

2012-02-12 Thread Francesco Fumanti
I added the US layout to my three layouts and Onboard showed the correct layout, even after restarting the computer. Then I removed the US layout from my layouts lists in the keyboard settings pane of the System Settings and Onboard continued to show the correct layout. Afterwards I clicked on

[Ubuntu-x-swat] [Bug 898761] Re: Display falls into sleep after a bit of use in Unity but not in Unity 2D

2011-12-13 Thread Francesco Fumanti
It turned out, that the graphics card was shutting down because it got to hot. A proper flow of air was impeded because the holes of the tower were not completely free. ** Changed in: xorg (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a

[Ubuntu-x-swat] [Bug 616023] Re: nVidia card : X won't start since 1.9 update, no screens found

2010-08-30 Thread Francesco Fumanti
@Artur Does nVidia 256.52 also work without the IgnoreABI flag? -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in

[Ubuntu-x-swat] [Bug 616023] Re: nVidia card : X won't start since 1.9 update, no screens found

2010-08-14 Thread Francesco Fumanti
I don't know whether it can be qualified as a fix; I would rather say that it is a work around the problem because I suppose that a fix should make it work without the IgnoreABI flag. -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You