Public bug reported:
Detects fine with direct connect, but when through kvm (works fine with
windows) will not detect proper resolution.
Log files should show:
1. Boot with KVM attached.
2. Plug monitor direct to motherboard (bypass) - old resolution for
instant, then change to proper
I am experiencing the same problem on 14.04 LTS but only recently. I
never had any problems with this for years! I imagined some of the
recent updates created it.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Same issue Acer Aspire One D250-1116. lubuntu 16.04 LTS.
Switching to xscreensaver appears to be a reliable workaround.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604
The solution given by @GA (#49) works like a charm with R.A.T. 7 in
Linux Mint 15 Olivia (32 bits) with XFCE 4.10 Desktop.
Horizontal scrolling is working!
Forward and reverse buttons are working fine!
lsb_release -a
LSB Version:
From this page:
http://delightlylinux.wordpress.com/2012/03/22/making-the-cyborg-rat-7
-albino-work-with-ubuntu/#comment-725
... a boy reported that the RAT 7 works perfectly in Ubuntu 12.04
(Precise Pangolin)
Just follow the instructions given by GA (# 50)
Happy hacking...!
Blackout.
--
Hmm, connecting on another machine through ssh and running the trace
steps, if I try to switch users the computer goes to a black screen. It
kills the session I'm attempting to switch from and never loads the one
I'm attempting to switch to. Since it mostly happens when I'm switching
users this is
Thank you very much @GA (# 49). Cyborg Mouse RAT 7 works on Ubuntu 10.10
(Maverick Meerkat)
Horizontal scrolling is working!
Forward and reverse buttons are working fine!
Noel Merino Hernández (aka Blackout)
--
You received this bug notification because you are a member of Ubuntu-X,
which
Public bug reported:
No HDMI output. I tried several tests. Sometimes, I get ubuntu booting
on HDMI (loading screen) but then it switches on laptop screen and
cannot access the HDMI TV anymore.
I am available for some tests if needed.
Using Ubuntu 11.10
ProblemType: Bug
DistroRelease: 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/883877
Title:
no HDMI output on HP pavilion dv6 (6250)
To manage notifications about this bug go to:
Add the x-updates PPA in addition to the low latency PPA.
--
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/821930
Title:
nvidia-current stopped compiling with linux 3.0.0-7
To
To be clear, nvidia-current (280.13 at time of posting) in the X-Updates
PPA is compatible with the -lowlatency kernel (3.0.0.9 at time of
posting) in the low-latency PPA.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers
Public bug reported:
Binary package hint: xorg
I don't know
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-28.49-generic-pae 2.6.35.11
Uname: Linux 2.6.35-28-generic-pae i686
Architecture: i386
DRM.card0.VGA.1:
status: connected
--
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/761586
Title:
ubuntu 10.10
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to :
After a time (short or long, it's depend) and when you have opening a lot of
windows, it's impossible to reach the others windows.
The only solution it's to close each window, one by one, disconnect and
reconnect.
I already have the problem with ubuntu 10.04. I have recently install the 10.10
The requested information was provided, the report was marked incomplete
with no explanation of why. The bug still exists, and should be
addressed.
** Changed in: xserver-xorg-input-synaptics (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I've just upgraded to 10.04.01 (i have an Intel 82865G graphics
procesor). My system now freezes after about 10 minutes regardless of
activity. Keyboard and screens are all locked out i have to do a reboot.
I installed the 'fixed
Why is this marked incomplete? What other information is requested?
--
Synaptics Driver doesn't load for Lenovo ThinkPad Travel Keyboard
https://bugs.launchpad.net/bugs/595495
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
output of cat /proc/bus/input/devices as requested. The travel keyboard
is connected via a dock station.
** Attachment added: cat /proc/bus/input/devices
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/595495/+attachment/1527625/+files/devices.txt
--
Synaptics
To make it even easier, here is the difference between having the
keyboard attached or not:
$ diff -u devices2.txt devices.txt
--- devices2.txt2010-08-29 12:44:57.0 -0400
+++ devices.txt 2010-08-29 12:42:30.0 -0400
@@ -94,6 +94,49 @@
B: EV=40001
B: SND=6
+I: Bus=0003
I'm seeing the same problem with the new version (256.35) of nvidia-
current that came out today, when applied to the Ubuntu Studio real-time
kernel from the PPA
(https://launchpad.net/~abogani/+archive/ppa/+packages).
It did install cleanly for the low-latency kernel, but not the real-time
Public bug reported:
Binary package hint: xserver-xorg-input-synaptics
Reposting Bug 201253, since was requested to open a new bug rather than
re-open the old one that was never touched.
Binary package hint: xserver-xorg-input-synaptics
The Lenovo ThinkPad Travel Keyboard - US
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/50491017/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/50491018/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50491020/Dependencies.txt
**
One bit of information regarding comment #70. I don't get to the login
screen because the VM is configured to auto-login.
--
keyboard input broken due to invalid keyboard variant set by VMWare installer
https://bugs.launchpad.net/bugs/548891
You received this bug notification because you are a
I have now upgraded, twice, a VM from 8.04 to 10.04, and can still
reproduce this problem despite running
# dpkg-reconfigure console-setup
to ensure correct values.
I have other Lucid VMs that I installed from scratch which work, and
this VM works as 8.04 prior to upgrading to Lucid.
Any
Found and fixed. It was necessary to rm /etc/X11/xorg.conf, which was
present because of the upgrade from 8.04.
--
keyboard input broken due to invalid keyboard variant set by VMWare installer
https://bugs.launchpad.net/bugs/548891
You received this bug notification because you are a member of
That's good news about 195.36.15, because 190.53 was the last nvidia
driver to successfully suspend and resume for me.
--
(Needs 195.36.15) X crashes during suspend/resume
https://bugs.launchpad.net/bugs/534754
You received this bug notification because you are a member of Ubuntu-X,
which is
@Pēteris, yes, those are Bug 535318 and Bug 535316, which are really
duplicates, since the latter is the cause of the former.
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a
There is a bug for the random characters on the tty: Bug 535316
--
Plymouth text-mode splash causes X to crash on first run due to shared tty7
https://bugs.launchpad.net/bugs/532047
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Are you planning on shipping .08 in Lucid since its now the latest
stable release from Nvidia ...
Not from what I see at ftp://download.nvidia.com/XFree86/Linux-x86_64/,
which still shows 190.53 as the latest stable driver.
... and MAY help to solve this issue
What in the change log
The fix in bug #488720 worked for me, too.
--
[lucid regression] random graphics effects after resume from suspend to RAM
https://bugs.launchpad.net/bugs/510004
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
The real change effecting comment #3 was that compiz-fusion-plugins-
extra is no longer installed by default. Just a note in case someone
finds my comment via Google, and wants the solution.
--
Some GL apps won't run: libGLU.so.1: No such file or directory
https://bugs.launchpad.net/bugs/506547
Public bug reported:
$ sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0B of additional disk space will
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38722725/Dependencies.txt
--
nvidia-current fails with /usr/bin/dpkg returned an error code (1)
https://bugs.launchpad.net/bugs/516760
You received this bug notification because you are a member of Ubuntu-X,
which is
*** This bug is a duplicate of bug 510004 ***
https://bugs.launchpad.net/bugs/510004
Andy, I am not reproducing this when booting without the nvidia driver.
And at the moment, I cannot get the nvidia-current driver to work
properly with 2.6.32-12, although it works with 2.6.32-11.
--
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-driver-nv (Ubuntu)
Status: New = Invalid
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Confirmed
--
building nvidia module against 2.6.33
*** This bug is a duplicate of bug 510004 ***
https://bugs.launchpad.net/bugs/510004
** This bug has been marked a duplicate of bug 510004
[lucid regression] random graphics effects after resume from suspend to RAM
--
lucid lynx xorg resume from suspend colored blocks nonresponsive
I've got this installed, and things like the GL screen savers work, but
raise on rotate is still not active with compiz, even though I have it
enabled via CSM. Any clue, other than my opening a report specifically
for that issue?
--
Some GL apps won't run: libGLU.so.1: No such file or directory
As per VMware Workstation 7 when installing VMware Tools:
Detected X.org version 7.6.2
No drivers for X.org version: 7.6.2
Skipping X configuration because X drivers are not included.
NOTE: It is worse with 64 bit Lucid Alpha 1; 64 bit Lucid will *NOT*
give back the keyboard and mouse
nvidia confirms that This driver is now the official stable release.
Would be nice to see in the official repositories for karmic and lucid
as nvidia-glx-190. People can choose to use either the 185 or 190
series, so it should be safe to add.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
What I see is that after the appropriate idle time, the screen goes
blank, I can see the backlight turn off, and then a few seconds later,
the backlight comes back on, although the screen stays blank (my
screensaver is set to simply blank the screen).
--
Karmic upgrade not shutting off backlight
@anagor, thanks. :-)
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
___
Mailing list:
I see a problem: after the appropriate idle time, the screen goes blank,
I can see the backlight turn off, and then a few seconds later, the
backlight comes back on, although the screen stays blank (that's my
screensaver).
Is anyone else seeing this failure to keep the screen turned off, and
Unfortunately, with no change in usage, it crashed (kernel crash) this
morning. What data can I provide to help, and how do we go about
getting it?
--
Jaunty X highly unstable
https://bugs.launchpad.net/bugs/359245
You received this bug notification because you are a member of Ubuntu-X,
which
I view Jaunty as unstable and unreliable; I would like for that to
change.
I've been running 2.6.28-15 and 185.18.36 for the past three days
without a reboot (or crash). So far so good, which would be nice. For
comment 26, I wonder if I am seeing a variation on the theme of Bug
296167 (and
*** This bug is a duplicate of bug 408561 ***
https://bugs.launchpad.net/bugs/408561
nvidia 185.18.29 and 185.18.31 were known bad drivers and really should
not have been put into the repository, in my opinion. Please use the
new 185.18.36 driver. Until it is in the main repository, you can
*** This bug is a duplicate of bug 408561 ***
https://bugs.launchpad.net/bugs/408561
nvidia 185.18.29 and 185.18.31 were known bad drivers and really should
not have been put into the repository, in my opinion. Please use the
new 185.18.36 driver. Until it is in the main repository, you can
** Summary changed:
- New stable release - 185.18.31 - available but see WARNING
+ New stable release - 185.18.36 - should replace 185.18.31 ASAP
** Description changed:
As per ftp://download.nvidia.com/XFree86/Linux-x86_64/latest.txt, this
is the new, latest, stable driver.
- For those
Thanks to all who got this fixed!
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
___
Mailing
What is the error message?
--
no nvidia video desktop since update kernel and packages
https://bugs.launchpad.net/bugs/412740
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
What is in /etc/X11/xorg.conf ?
--
no nvidia video desktop since update kernel and packages
https://bugs.launchpad.net/bugs/412740
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in ubuntu.
I updated to nvidia 185.18.31. Now I have no desktop at all.
It is possible that you are running into a known problem with 185.18.29
and 185.18.31. Neither works for me, either. You might try 190.18.03
from the nVidia PPA (https://launchpad.net/~nvidia-vdpau/+archive/ppa),
and see if that works
What I saw today was that the X session somehow got disconnected from
input devices. The mouse would move, but clicks and keyboard events
were ignored. CTRL-ALT-F1 got to me a virtual terminal, where I could
restart GDM, and all has been fine since.
--
Jaunty X highly unstable
Timo,
I finally had time to replace the 320GB drive in my laptop with a 500GB
drive, and have reinstated Jaunty into the list of available distros in
the boot menu. I'm up to date with the kernel (2.6.28-15.48) and nvidia
driver (190.18.03), so we'll see if this works better.
--
Jaunty X
For those who find themselves here having encountered the problem with
185.18.31, please note that there does not appear to be a problem with
190.18.03, so installing 190.* from the PPA may help.
--
New stable release - 185.18.31 - available but see WARNING
https://bugs.launchpad.net/bugs/408561
190.18.03 is now in the PPA, and does not exhibit the problems that
185.18.31 does.
--
New nvidia 190.18 driver available
https://bugs.launchpad.net/bugs/404135
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to linux-restricted-modules-2.6.24 in
Timo,
What makes you think that it is an nvidia driver problem? Every version
of the nvidia driver has failed under Jaunty, and every one of them
works fine with Intrepid and Karmic.
At present I view Jaunty as unstable and unreliable and to be skipped.
I would like for that to change.
--
That's not going to happen, jaunty shipped already
I believe that you must have misunderstood my comment. I don't mean
that Canonical should have skipped it, I mean that I (and probably other
users) should unless Jaunty is fixed, which is what I meant about
wanting change. Jaunty had been
Nikola, a PPA (which I already know about and use) does not qualify as
FIX RELEASED, as far as I know. And Karmic is still in alpha, so I
don't know that the rule you believe applies actually does.
--
New nvidia 190.18 driver available
https://bugs.launchpad.net/bugs/404135
You received this
Public bug reported:
As per ftp://download.nvidia.com/XFree86/Linux-x86_64/latest.txt, this
is the new, latest, stable driver.
For those willing to test it, it is also in the NVIDIA-VDPAU PPA
(https://launchpad.net/~nvidia-vdpau/+archive/ppa), as well as being at
crash data:
Aug 3 16:23:41 karmic kernel: [ 20.814640] Pid: 2853, comm: Xorg Tainted: P
2.6.31-5-generic #24-Ubuntu 64577WU
Aug 3 16:23:41 karmic kernel: [ 20.814641] RIP: 0010:[]
[(null)] (null)
Aug 3 16:23:41 karmic kernel: [ 20.814644] RSP:
** Description changed:
As per ftp://download.nvidia.com/XFree86/Linux-x86_64/latest.txt, this
is the new, latest, stable driver.
For those willing to test it, it is also in the NVIDIA-VDPAU PPA
(https://launchpad.net/~nvidia-vdpau/+archive/ppa), as well as being at
For the stable 185 driver, see Bug 408561.
Please note that both 185.18.29 was pulled almost immediately after
release, and although 185.18.31 is supposed to fix the defect, it does
not, so I expect it to be pulled and replaced soon, too.
--
New nvidia 190.18 driver available
See also: http://www.nvnews.net/vbulletin/showthread.php?p=2060054
--
New stable release - 185.18.31 - available but see WARNING
https://bugs.launchpad.net/bugs/408561
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in
New 190.18.03 beta driver:
http://developer.nvidia.com/object/opengl_3_driver.html
Not yet in the PPA.
--
New nvidia 190.18 driver available
https://bugs.launchpad.net/bugs/404135
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
See ftp://download.nvidia.com/XFree86/Linux-x86_64/
http://www.nvnews.net/vbulletin/showthread.php?t=136281
Changes since 185.18.*:
* Added GLX protocol support (i.e., for GLX indirect rendering) for the
following OpenGL extensions:
o
hold down Alt-SysReq and hit the keys e,s,b
Does Alt-SysReq actually work for you??
(https://answers.launchpad.net/ubuntu/+source/compiz/+question/56729)
The most I've ever been able to get out of it is the HELP text, but it
never responds to anything else.
--
Jaunty X highly unstable
I have had Jaunty lock up 3 times this week, including this evening, No
second display, nothing fancy. Using the exact same driver on
Intrepid, and I never have any problem.
--
Jaunty X highly unstable
https://bugs.launchpad.net/bugs/359245
You received this bug notification because you are a
We cannot really recommend to people to switch to pre-alpha Karmic,
either.
I agree, for most users. But then again MOST users should not be
running Jaunty. They should be running either Hardy or at most
Intrepid. WHAT, you say, but Jaunty is the latest and best and
released! So what? We
FWIW, I have been running Jaunty using 185.10.14 since Sunday without
any freeze up. Lots of VMware usage, suspends, resumes, etc., and it is
still going. That is sort of a new record for Jaunty since these
problems started, so I am marginally hopeful.
I would certainly suggest that anyone who
@Marius Kotsbak: no, it doesn't fix this cursor stuck bug for me.
--
[RV350] jaunty mouse cursor stuck on second monitor
https://bugs.launchpad.net/bugs/359840
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
miPointer*: Invalid input device pointer lines in Xorg.0.log are
coming from the patch 169_mipointer_nullptr_checks.patch in xorg-
server (seems to be an Ubuntu patch).
Perhaps this bug insert some side effects ?... It was proposed to
resolve this bug :
169_mipointer_nullptr_checks.patch could have side effects ?
On Jaunty, Xinerama with nvidia cards does not work very well... Log
messages looks like these :
miPointerConstrainCursor: Invalid input device pointer
miPointerConstrainCursor: Invalid input device pointer
miPointerWarpCursor:
72 matches
Mail list logo
