** Description changed:
In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
up to 16.10 beta the touchpad became unusable.
When holding a single finger on the touchpad, without moving my finger,
the cursor jumps around like crazy, and even performs clicks. When
Public bug reported:
In 16.04 LTS, the touchpad behaved perfectly, and as soon as I stepped
up to 16.10 beta the touchpad became unusable.
When holding a single finger on the touchpad, without moving my finger,
the cursor jumps around like crazy, and even performs clicks. When
placing a second
Sorry for the late reply.
1) Well, I have another Ubuntu-based machine that does not have any
custom kernel parameters, and it does leave these artifacts every-now-
and-then as well.
2) And yes, I do remember seeing those artifacts in previous Ubuntu
versions, too, but simply assumed that would
I can confirm this issue still persisting on Trusty, after all these years.
FYI - I usually hide my Launcher; coming out of suspend shows a garbled mess
where the launcher normally would be. See screenshot attached.
** Attachment added: Screenshot from 2014-03-11 07:27:37.png
** Attachment added: Screenshot from 2014-03-11 07:27:37.png
https://bugs.launchpad.net/unity/+bug/676166/+attachment/4018114/+files/Screenshot%20from%202014-03-11%2007%3A27%3A37.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@Christopher: I ended up giving the G75 to my wife, and I got a System76
Bonobo Extreme, pre-installed with Ubuntu. Everything works as it should
on that puppy. :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates
Public bug reported:
This seems to be a regression, as I haven't had that issue before.
When dragging an application window to the 2nd monitor, that application
window can no longer be accessed using the mouse. Clicking on it doesn't
do anything. Trying to drag it by clicking and holding the
** Package changed: nvidia-graphics-drivers-experimental-310 (Ubuntu) =
nvidia-common (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-experimental-310 in
Ubuntu.
https://bugs.launchpad.net/bugs/1132785
Title:
Public bug reported:
During one of the updates, I lost my Codeweaver Crossover installation.
Come to find out that ia32libs got deleted. Now I am unable to run
Office 2010. I tried to re-install, but I get the following message:
Selecting previously unselected package ia32-crossover.
(Reading
Public bug reported:
I've got an Asus G75VW laptop with an nVidia GTX660M video card.
After some tweaking of the xorg.conf file to include Option
registryDwords EnableBrightnessControl=1, I am able to use the
Fn+F5 and Fn+F6 brightness control keys (and the brightness slider
inside System
Public bug reported:
This just happened after logging in.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: xdiagnose 3.4.2
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno
Well, I just upgraded to 13.04 and guess what? Brightness control does
work perfectly now.
Current kernel:
Linux rrohde-G75VW 3.7.0-3-generic #9-Ubuntu SMP Tue Nov 20 22:38:45 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu-X,
Oh the horror... Guess what? What ever upgrade came down the pipe
earlier today did not seem to have survived a reboot. What a damn
shame.
Now, my brightness control NO LONGER works, and we're back to square
one. Still the same kernel, still on 13.04.
I was so happy to see the brightness
@Robert Leinardi
I tried what you've suggested and I still don't have any brightness.
What else did you do? Did you install nvidiabl or any other module?
Just wondering, as this issue seems to be the last big issue for me on
my G75...
--
You received this bug notification because you are a
I tried this as well; here's a snippet from my xorg.conf:
Section Device
Identifier Device0
Driver nvidia
VendorName NVIDIA Corporation
BoardName GeForce GTX 660M
Option NoLogo true
Option RegistryDwords EnableBrightnessControl=1
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Please see Launchpad Bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1046088
--
Yours truly,
Rainer Rohde
Whatever the mind can conceive and believe, the mind can achieve.
~Napoleon Hill
--
You received this bug notification because you are a member
Delivery to the following recipient failed permanently:
linux-...@vger.kernel.org
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient
domain. We recommend contacting the other email provider for further
information about the
I am so sorry -- I am getting confused with the bugs I am posting. I
thought this was for the USB3 issue I am facing. :) Sorry about that. I
will do try this again soon.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I think that ACPI functions should be available at kernel level.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness Control on ASUS G75VW
*** This bug is a duplicate of bug 1046088 ***
https://bugs.launchpad.net/bugs/1046088
The same issue persists with nvidia drivers 304.48.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
The same issue persists with nvidia drivers 304.48.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness Control on ASUS G75VW Notbook (304.43)
I tried this on the 3.6 kernel as well, and the bug still persists on my
Asus G75.
I found it interesting that on my old MacBook Pro 5,2 I didn't have any
problem with brightness control...
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member
** Changed in: nvidia-settings (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1055674
Title:
nvidia-settings crash when clicking on certain
The funny thing is, pretty much all other Fn keys work, including media
buttons, wifi on/off, suspend, switch monitors, turn off monitor, audio,
and even calling up the calculator with Fn+NumEnter works.
So, what can be done in order to have this ACPI call work for the screen
brightness?
--
You
** Visibility changed to: Public
--
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/1055634
Title:
Xorg crashed with SIGABRT
To manage notifications about this bug go to:
I noticed that it crashes the nvidia-settings app whenever I am clicking
on nvidia-settings Configuration and OpenGL/GLX Information.
All other entries behave normally and don't cause a crash.
** Tags added: nvidia nvidia-settings
** Description changed:
- This just happens after today's
Also, whenever I click on nvidia-settings OpenGL/GLX Information,
the window manager crashes as well.
--
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/1055634
Title:
Xorg
Public bug reported:
I've reported this already here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers/+bug/1055634 , however the Apport Retracing Service said I need
to file a new bug.
This just happens after today's dist-upgrade -- the Nvidia Settings app
crashes when
** Tags added: metacity nvidia nvidia-settings
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1055674
Title:
nvidia-settings crash when clicking on certain entries
To manage
** Visibility changed to: Public
** Tags added: unison
--
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/1055689
Title:
Xorg crashed with SIGABRT
To manage notifications about
I am really curious as to why nobody tackles this issue? About a month
left until release, and this issue still persists.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
I am really curious as to why nobody tackles this issue? About a month
left until release, and this issue still persists.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
nvidiabl in its current form does not work on the ASUS G75.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness Control on ASUS G75VW Notbook
Would be nice if this would be fixed so that it does *not* involve
hacking. :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness Control on
I've also added this to my kernel params -- still no brightness control.
:(
acpi_osi=Linux acpi_backlight=vendor
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1049359
Public bug reported:
I have no screen brightness control on my Asus G75VW laptop with Nvidia
GeForce 660m GTX. I've observed this on 12.04 and 12.10 alpha through
beta1.
This is what I've tried:
-- Pressing Fn+F5/F6 doesn't do anything; it should increase/decrease
screen brightness.
-- Looking
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1049359
Title:
No Brightness Control
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
*** This bug is a duplicate of bug 1037518 ***
https://bugs.launchpad.net/bugs/1037518
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
This just now happens with Quantal Beta1, running Chromium. The hit on
the CPU by Xorg was even greater this time around (see attached
screenshot).
** Attachment added: Screenshot from 2012-09-07 23:04:49.png
** Tags added: asus nvidia-current
** Tags added: backlight
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1046088
Title:
No Brightness Control on ASUS G75VW Notbook
To manage notifications about this bug go to:
Public bug reported:
I've got no brightness control via Fn+F5 and Fn+F6 keys on my 17 ASUS
G75VW notbeook with NVIDIA GeForce 660M GTX.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: nvidia-current-updates 304.43-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux
*** This bug is a duplicate of bug 1041743 ***
https://bugs.launchpad.net/bugs/1041743
** Visibility changed to: Public
** Tags added: lightdm nvidia unity
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
It's all good, Robbie -- Aaron Plattner of NVIDIA just announced that
the Xorg/NVIDIA bug was fixed with nvidia-current 304.43. I tested it,
and everything works like a charm now!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Thank you for clearing this up, Robbie. That helps a lot.
--
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/1037173
Title:
Xorg crashed with SIGABRT in FreeResource()
To manage
Nouveau doesn't work for me... after a reboot, it drops me to the CLI.
When running startx or service lightdm restart, the system freezes.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: _usr_lib_unity_unity-panel-service.1000.crash
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3277933/+files/_usr_lib_unity_unity-panel-service.1000.crash
--
You received this bug notification because you are a member of
** Attachment added: _usr_bin_nautilus.1000.crash
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3277934/+files/_usr_bin_nautilus.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: _usr_bin_Xorg.0.crash
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3277935/+files/_usr_bin_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Attachment added: _usr_bin_compiz.1000.crash
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3277941/+files/_usr_bin_compiz.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This is definitely related to Xorg. I have crashes left and right,
regardless whether I am using nvidia-current or nouveau. Nouveau crashes
less, but its always a sefault in Xorg it seems.
The most stable workaround for me is to run Classic Gnome, and even
there, certain apps trigger a crash
** Attachment added: _usr_bin_Xorg.0.crash
https://bugs.launchpad.net/bugs/1041958/+attachment/3278216/+files/_usr_bin_Xorg.0.crash
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
This happens to me a lot. Unity crashes immediately with Xorg segfault.
Installed nvidia-current, 12.10 alpha 3.
** Tags added: quantal xorg
** Tags added: unity
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in
I have the same exact issue.
I can run startx from the cli and then launch Unity from a terminal --
as soon as Unity tries to launch, it kicks me back out with the same
error message you guys are seeing:
https://launchpadlibrarian.net/113232426/IMG_0855.JPG
I started a bug report here as well:
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1041743
Title:
Xorg crashed with SIGABRT
To manage notifications about this bug go to:
Even with the latest Xorg from xorg edgers PPA and the lateste nvidia
driver, Unity on 12.10 immediately crashes with a segmentation fault.
The sad part is that now they removed Unity 2D and I am also unable to
install Classic Gnome, so there is NO fallback. I am trying to work with
nouveau now,
Public bug reported:
I get regular Segmentation Fault (Core Dumped) errors while working
in Unity under 12.10 alpha 3.
I also tried Xorg from xorg edgers PPA in order to install nvidia-
current, however, I am getting a segmentation fault there 100% of the
time and I am unable to use Ubuntu at
** Tags added: compiz nouveau nvidia unity
** Package changed: xorg (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1041269
Title:
Unity keeps crashing under Nouveau
Public bug reported:
My laptop has a NVIDIA GeForce 660M GTX as dedicated video card and I am
unable to install nvidia-current due to a dependency that's impossible
to resolve (see below). This s especially frustrating since the only
fallback is nouveau, which keeps crashing Unity rather often.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1041330
Title:
Unable to install nvidia-current
To manage notifications about this bug go to:
Here's some output from my dmesg regarding Xorg as well; not sure if
that helps at all...
[3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic
#11-Ubuntu
[3.576579] Call Trace:
[3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0
[3.576585]
Here's some output from my dmesg regarding Xorg as well; not sure if
that helps at all...
[3.576578] Pid: 1127, comm: Xorg Tainted: P O 3.5.0-11-generic
#11-Ubuntu
[3.576579] Call Trace:
[3.576583] [81051c4f] warn_slowpath_common+0x7f/0xc0
[3.576585]
I tried something different to generate more meaningful output.
-- Logged in from the command-line and ran startx. The session
started just fine, however there was no Gnome Panel loaded whatsoever.
-- Pressed F12 to launch Guake terminal and typed unity --replace
and hit enter. This dropped me
** Attachment removed: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272142/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: IMG_0854.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272147/+files/IMG_0854.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Attachment added: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1039148/+attachment/3272152/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I tried something different to generate more meaningful output.
-- Logged in from the command-line and ran startx. The session started
just fine, however there was no Gnome Panel loaded whatsoever.
-- Pressed F12 to launch Guake terminal and typed unity --replace
and hit enter. This dropped me
** Attachment added: IMG_0855.JPG
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+attachment/3272169/+files/IMG_0855.JPG
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
This happens on Quantal alpha 3, installed on an Asus G75VW, with a
dedicated GeForce 660M GTX.
On my previous Dell XPS 15z, running a descrete nVidia Optimus card, it
worked just fine when running apps with optirun.
--
You received this bug notification because you are a member of Ubuntu-X,
** Tags added: compiz
--
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/1039148
Title:
When logging in to Unity, the Desktop session crashes
To manage notifications about this
** Tags added: nvidia-current quantal
** Tags added: unity
--
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/973096
Title:
Nvidia driver causes xorg crash
To manage
Here's some more content to look at for those working towards a fix: I
ran unity --debug and got this:
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x73b5c700 (LWP 10817)]
Program received signal SIGHUP,
Here's some more content to look at for those working towards a fix: I
ran unity --debug and got this:
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x73b5c700 (LWP 10817)]
Program received signal SIGHUP,
** Package changed: unity (Ubuntu) = nvidia-graphics-drivers (Ubuntu)
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
** Summary changed:
- When launching Thunderbird (or Firefox), the Desktop session crashes
+ When logging in to Unity (or launching Thunderbird or Firefox from Classic
Gnome), the Desktop session crashes
** Tags added: ubuntu
** Summary changed:
- When logging in to Unity (or launching
** Visibility changed to: Public
--
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/1039141
Title:
Xorg crashed with SIGABRT in FreeResource()
To manage notifications about this
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1038831
Title:
Xorg crashed with SIGABRT in raise()
To manage notifications about this bug go to:
Currently running the 3.5.0-4-generic kernel and I am surprised that
there still is no support for this touchpad. It's a cypress touchpad,
which, from what I understand, is also found in Apple laptops. I didn't
have any issues with my MacBook Pro and multitouch under Ubuntu...
--
You received
** Summary changed:
- Touchpad on Dell XPS 16z not working as expected
+ Touchpad on Dell XPS 15z not working as expected
** Tags added: cypress touchpad xserver-xorg-input-synaptics
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
There's currently no Touchpad option associated with this device, even
though the Dell XPS 15z has a multi-touch capable touchpad, similar to
my former MacBook Pro (which, btw, worked perfectly fine in Ubuntu).
Currently, the touchpad only works in mouse emulation, and
** Attachment added: Screenshot from 2012-07-02 07:49:36.png
https://bugs.launchpad.net/bugs/1020086/+attachment/3210802/+files/Screenshot%20from%202012-07-02%2007%3A49%3A36.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
This affects me as well. MacBookPro 5,2.
The mouse cursor is still visible, and I can right-click and get a
context menu, but I am unable to move the mouse cursor around my screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
This is a regression - just started a couple of days ago.
When coming out of suspend, my MacBookPro 5,2's touchpad stops working.
The mouse cursor is still visible, and I can right-click and get a
context menu, but I am unable to move the mouse cursor around my screen.
On
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/970574
Title:
Touchpad stops working when coming out of suspend
To manage notifications about this bug go to:
Well, it seems to work just fine now - no issues to report. I am very
glad that this has been fixed. Thanks to everyone involved!
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of
As of yesterday, things seem to have improved. I have been using the
same test right after logging in, and the touchpad continues to work
just fine! This is good news indeed, and I will keep an eye on the
touchpad's behavior.
--
You received this bug notification because you are a member of
Just to keep this going - I tried this in Ubuntu, Gnome Shell and Gnome
(without effects), and the behavior is the same: as soon as I start
typing, the touchpad is dead until I log out and back in again.
What is being done towards getting this issue sorted? Is there anything
I can do in order to
Public bug reported:
I'd like to post this as a new bug since for some reason there's no
movement (bug #938039) and the bug is really affecting my productivity
at work.
Again, when adjusting the keyboard backlight by pressing F5 on the
keyboard a few times the touchpad is effectively 'dead'. I
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/948389
Title:
Touchpad stops working after using the keyboard (including function
keys)
To manage notifications about
It seems that as of now the problem is solved. I will keep an eye on it,
but so far, so good! :)
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Well, that didn't last long. After a reboot I adjusted the keyboard
backlight with the respective function key on the MBP and the touchpad
stopped working immediately... So, here we go again.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Fix Released = Confirmed
--
You
Forgot to mention my current xserver-xorg-input-synaptics version:
xserver-xorg-input-synaptics:
Installed: 1.5.99~git20120223-0ubuntu2
Candidate: 1.5.99~git20120223-0ubuntu2
Version table:
*** 1.5.99~git20120223-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main
** Summary changed:
- Lose Touchpad functionality
+ Touchpad breaks when after using keyboard in textfields function keys
** Summary changed:
- Touchpad breaks when after using keyboard in textfields function keys
+ Touchpad stops working after using keyboard in textfields function keys
--
Sorry to change this back to incomplete, but this is not fixed yet and
still persists. Every time I start to type or use the keys within the
Desktop environment after logging in I lose my touchpad functionality.
:(
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Fix Released =
I noticed that even when pressing the function keys to adjust the
keyboard back-light or screen brightness causes the touchpad to become
unavailable for that session...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics
This issue still persists as of now...
xserver-xorg-input-synaptics:
Installed: 1.5.99~git20120223-0ubuntu1
Candidate: 1.5.99~git20120223-0ubuntu1
Version table:
*** 1.5.99~git20120223-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100
I get a similar corruption when I log in as shown in the screenshot in
#23.
--
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/931967
Title:
Corrupted graphics after the login
I also noticed that it breaks the touchpad as soon as I try and open a
Nautilus window via keyboard shortcut. So, not only entering text within
a text field, but using any combined keyboard input seems to cause this
issue to appear.
--
You received this bug notification because you are a member
1 - 100 of 112 matches
Mail list logo
