** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: Confirmed => In Progress
--
Please update nvidia-glx-180 to 180.29 in Jaunty
https://bugs.launchpad.net/bugs/327690
You received this bug notification because y
removing nvidia-glx-177 before installing 180 should solve the problem.
I'll make sure that this doesn't happen any more.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Alberto Milone (albertomilone)
S
Ok, let me rephase what I said:
1) please attach the output of the following command:
lspci -v
2) attach your /etc/X11/xorg.conf and your /var/log/Xorg.0.log
--
nVidia 177 (red in boot log) can't init. "cman" with dual 8600 GT
https://bugs.launchpad.net/bugs/331114
You received this bug notifi
Moving a "goto" did the trick. I have provided upstream with a patch.
The bug however affects gnome-settings-daemon.
** Bug watch added: GNOME Bug Tracker #572876
http://bugzilla.gnome.org/show_bug.cgi?id=572876
** Also affects: gnome-control-center via
http://bugzilla.gnome.org/show_bug.c
Medium
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => In Progress
--
nvidia: Multiple versions in DKMS
https://bugs.launchpad.net/bugs/261816
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please motu-sru team upload this fix to Hardy (SRU):
http://albertomilone.com/ubuntu/newlrm/pitti/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.diff.gz
http://albertomilone.com/ubuntu/newlrm/pitti/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.dsc
http://albertomilone.com/ubuntu/n
** Also affects: nvidia-graphics-drivers-71 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-71 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => Confirmed
** C
** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => Fix Released
--
New version of 177 driver available. (177.70)
https://bugs.launchpad.net/bugs/262745
You received
Graham: that happened because the .prerm file of 177.68 was still there
and was affected by the problem. The upgrade from 177.70 to newer
releases should no longer cause this bug.
--
nvidia: Multiple versions in DKMS
https://bugs.launchpad.net/bugs/261816
You received this bug notification becaus
Fabien: can you reproduce the problem if you set the driver to "nv" in
the Device section of your xorg.conf and restart the xserver?
--
X Lockup in Intrepid (infinite loop)
https://bugs.launchpad.net/bugs/259808
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1) What happens if you remove these options from the xorg.conf?
Option "NvAGP" "1"
Option "AddARGBGLXVisuals" "True"
Option "DisableGLXRootClipping" "True"
2) can you reproduce the problem if you install nvidia-glx-173?
--
[G86GL] Latest NVIDIA drivers: X hang
André:
1) the method which you suggested will break some symlinks created by the
packages in Ubuntu. Be careful.
2) proprietary drivers are not loaded by default unless specified in the
xorg.conf
3) without a log or further information on your system (you will have to
reproduce the problem) I'm
plun: the error was caused by the NVIDIA installer.
--
nvidia: Multiple versions in DKMS
https://bugs.launchpad.net/bugs/261816
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
htt
*** This bug is a duplicate of bug 227717 ***
https://bugs.launchpad.net/bugs/227717
** Changed in: envyng-gtk (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => Triaged
--
envynggtk.py crashed with Impor
It looks like you ran out of space:
failed in buffer_write(fd) (10, ret=-1): backend dpkg-deb during
`./usr/lib/dri/fglrx_dri.so': No space left on device
You should free up disk space and try to install the package again.
** Changed in: fglrx-installer (Ubuntu)
Status: New => Invalid
-
get to /var/lib/dkms/nvidia/ and start removing any directory which
starts with a number e.g. 173.14.09, 177.67, 177.68 but not
kernel-2.6.27-2-generic-i686.
then type:
sudo apt-get install --reinstall nvidia-177-kernel-source
and attach the output
--
Intrepid: Latest update destroys X serve
just to be sure type:
sudo rmmod nvidia
sudo modprobe nvidia
and restart your computer
--
Intrepid: Latest update destroys X server configuration on MacBook Pro (Nvidia
GeForce 8600M GT, nvidia-glx-177)
https://bugs.launchpad.net/bugs/263528
You received this bug notification because you are a
can you attach your /var/log/Xorg.0.log and /var/log/Xorg.0.log.0 ?
--
Intrepid: Latest update destroys X server configuration on MacBook Pro (Nvidia
GeForce 8600M GT, nvidia-glx-177)
https://bugs.launchpad.net/bugs/263528
You received this bug notification because you are a member of Ubuntu
Bug
can you attach your /var/log/Xorg.0.log and /var/log/Xorg.0.log.old ?
--
Intrepid: Latest update destroys X server configuration on MacBook Pro (Nvidia
GeForce 8600M GT, nvidia-glx-177)
https://bugs.launchpad.net/bugs/263528
You received this bug notification because you are a member of Ubuntu
B
gspat: your new problem is not the same as the one described in this
report. Feel free to file another report.
I'm closing this report since the problem was caused by the NVIDIA
installer and not by the package.
** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
Status: Confirmed => Inval
oss_test_launchpad:
set the driver to "nvidia" in the Device section of your xorg.conf
then press CTRL+ALT+F1 (you will see only the command line)
type:
sudo /etc/init.d/gdm stop (or kdm stop if you use Kubuntu)
startx -- -logverbose 5 &> $HOME/bugreport.log
if the xserver fails again you can si
** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
The NVIDIA driver in the lrm-envy doesn't support Geforce 9xxx
https://bugs.launchpad.net/bugs/239115
You received this bug notification because you are a m
Public bug reported:
The NVIDIA driver in the lrm-envy (169.12) doesn't support Geforce 9xxx
cards and certain 8xxx cards.
Here are the release highlights for driver 173.14.05:
* Added support for the following new GPUs:
o Quadro FX 3600M
o GeForce 9800 GX2
o GeF
can you try this:
sudo apt-get remove xorg-driver-fglrx-envy fglrx-kernel-source-envy
then try the dist-upgrade again.
** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu)
Status: New => Incomplete
--
fglrx installation crashes after distri update 7.1 to hardy
https://bugs.launc
If the driver loads but freezes randomly there can be several reasons for the
failure:
1) your motherboard conflicts with your graphic card
2) there's a regression in the new fglrx driver
3) your card is dying.
In any case this is not something which I can fix, thererfore I suggest you to
file a
Cesare: thanks, I'll deal with it.
--
The NVIDIA driver in the lrm-envy doesn't support Geforce 9xxx
https://bugs.launchpad.net/bugs/239115
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.ub
goes. If there are problems, please post them here.
** Changed in: linux-restricted-modules-envy-2.6.24 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
nvidia-glx-new-envy 173.14 not working
https://bugs.launchpad.net/bugs/239536
You received this bug notificat
Marco, Cristoph: did you put nv or nv_new in the blacklist in /etc
/linux-restricted-modules-common ?
This is what people do when they install the driver from the installer
from NVIDIA's website.
--
nvidia-glx-new-envy 173.14 not working
https://bugs.launchpad.net/bugs/239536
You received this b
Cristoph: try this:
1) log out and press CTRL+ALT+F1 (so as to get to the command line).
2) Shut down the Xserver with either:
sudo /etc/init.d/gdm stop
or (if you use KDM):
sudo /etc/init.d/kdm stop
3) type:
sudo rmmod nvidia
sudo modprobe nvidia
4) Restart the Xserver:
sudo /etc/init.d/gdm s
Cristoph: try this:
1) log out and press CTRL+ALT+F1 (so as to get to the command line).
2) Shut down the Xserver with either:
sudo /etc/init.d/gdm stop
or (if you use KDM):
sudo /etc/init.d/kdm stop
3) type:
sudo rmmod nvidia
sudo modprobe nvidia
4) Restart the Xserver:
sudo /etc/init.d/gdm s
You can install EnvyNG and enable the hardy-proposed repositories so as
to get the latest release of the driver.
Read here for further details:
http://albertomilone.com/wordpress/?p=210
--
update nVidia driver to newest release (173.14)
https://bugs.launchpad.net/bugs/239863
You received this bu
You can install EnvyNG and enable the hardy-proposed repositories so as
to get the latest release of the driver.
Read here for further details:
http://albertomilone.com/wordpress/?p=210
--
Nvidia 9600gt card not working correctly
https://bugs.launchpad.net/bugs/231989
You received this bug notif
Carsten: I don't understand the errors since they are in German.
1) try typing:
sudo apt-get install linux-headers-$(uname -r)
2) I don't know whether the -server flavour is xen-enabled (and this
could explain the failure)
--
nvidia-glx-new-envy 173.14 not working
https://bugs.launchpad.net/bug
William: you can install the latest driver by using EnvyNG. Read my comment
here:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/231989/comments/19
--
nvidia-glx-new driver displays white screen of death
https://bugs.launchpad.net/bugs/208718
You received this bug
William Anderson: enable -proposed, install only the packages you need
and then disable -proposed. See, it's not that difficult.
drink: feel free to think whatever pleases you but read what Bryce Harrington
said about updating drivers and EnvyNG:
http://blog.qa.ubuntu.com/node/10
--
nvidia-glx-
The problem affects me too (I use an Nvidia card). I have noticed that
if I create a directory on the desktop shown by the second display and I
double click there, nautilus shows up in the right screen. If I try to
open a videoclip with totem (by clicking on it from the nautilus window
in the 2nd s
SRU request:
Testcase: add a dependecy on nvidia-common to allow jockey to detect driver 180.
Source code:
http://albertomilone.com/ubuntu/nvidia-common/nvidia-common_0.2.4.1.tar.gz
http://albertomilone.com/ubuntu/nvidia-common/nvidia-common_0.2.4.1.dsc
--
Intrepid: Installing the 180 nvidia dri
I haven't had the time to look at this very hardware specific bug but I
think I can try to revert patch only for ALPS touchpads so as not to
cause regressions with synaptics touchpads.
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug
The attached debdiff should solve the problem. The change is minimal and
is just an addition to my previous patch so that if an ALPS touchpad is
detected the right edge is not auto adjusted.
** Attachment added: "xfree86-driver-synaptics_0.99.3-2ubuntu4.debdiff"
http://launchpadlibrarian.net/2
Ok, I'll work on another patch but we'll have to test the package for
regressions as it will affect all synaptics touchpads.
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug notification because you are a member of Ubuntu
Bugs, which
The attached debdiff sets the SpecialScrollArea to False by default.
** Attachment added: "xfree86-driver-synaptics_0.99.3-2ubuntu4.debdiff"
http://launchpadlibrarian.net/24366782/xfree86-driver-synaptics_0.99.3-2ubuntu4.debdiff
--
tap-to-click and edge-scrolling broken in Jaunty
https://bug
I have uploaded the package to my PPA, can you try it and let me know how it
goes, please?
https://launchpad.net/~albertomilone/+archive/ppa
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug notification because you are a member of U
Can you also attach the output of the following command?
xrandr --prop
--
Show screens as "unknown" instead of displaying the monitor names
https://bugs.launchpad.net/bugs/356834
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
Serbitar: can you attach the output of this command, please?
xinput list-props name_of_your_synaptic_device
replace "name_of_your_synaptic_device" with the name of your synaptic
device (as reported by "xinput list")
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/b
Serbitar: 1.1.0-0ubuntu1 is not available in Ubuntu Jaunty. Can you
please install version 0.99.3-2ubuntu4, restart the xserver and attach
the output of the same command?
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug notification
What resolution did you set for your Dell monitor (when you used System
> Preferences > Display)?
--
Wrong virtual desktop size setting set in xorg.conf
https://bugs.launchpad.net/bugs/358147
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Tim: what's the output of this command?
nvidia-detector
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
** Visibility changed to: Public
--
nvidia-detector crashed with ImportError in ()
https://bugs.launchpad.net/bugs/346099
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://l
the fact that it returns "none" (now that 177 is no longer installed) is
ok.
nvidia-common is already used by Update Manager to migrate drivers from
obsolete versions to more appropriate versions. I wonder why this didn't
work.
Michael: any ideas?
--
nvidia -177 needs to be transitioned to -180
If I force the installation of driver 177 in Jaunty and I type nvidia-detector
I get this:
$ nvidia-detector
nvidia-glx-180
which means that nvidia-glx-180 should be installed instead.
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You receive
Tim: did you upgrade your system using Update Manager or did you use the
command line?
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Serbitar, Michael: thanks for making it clear that the problem affects
the package in the PPA and not the package in Ubuntu.
I think this bug is finally fixed.
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug notification because yo
In conclusion we found 2 different bugs.
1) If "restricted" is disabled, Update Manager won't know what driver to
select, in which case it should simply comment out the Driver line in xorg.conf
so that X.org can use an open source driver which works (or is supposed to
work) with the card.
2) X.o
** Also affects: xserver-xorg-video-nv (Ubuntu)
Importance: Undecided
Status: New
** Package changed: nvidia-common (Ubuntu Jaunty) => update-manager
(Ubuntu Jaunty)
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug
** Changed in: jockey (Ubuntu)
Importance: Undecided => Low
** Changed in: jockey (Ubuntu)
Status: New => In Progress
** Changed in: jockey (Ubuntu)
Milestone: None => ubuntu-9.04
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
Driver names shows
Ricardo: first of all, thanks for reporting the problem and for
suggesting a workaround. I have worked on a solution which will not
break the drivers whose handlers do not report the version in the name
of the driver (i.e. any other handler but the nvidia one).
Martin: can you have a look at my so
** Changed in: screen-resolution-extra (Ubuntu)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu)
Status: New => In Progress
** Changed in: screen-resolution-extra (Ubuntu)
Milestone: None => ubuntu-9.04
Assignee: (unassigned) => Al
As regards what is described in the bug report, I have found a solution to the
problem and I made it available in my bzr branch (whose content is now ready
for an upload to Ubuntu's repository):
https://code.launchpad.net/~albertomilone/screen-resolution-extra/main
Here's the source:
http://www.
Public bug reported:
The patch suggested by Havoc Pennington should solve the problem that
causes a white flash on X login with compositing. The issue is
http://bugs.freedesktop.org/show_bug.cgi?id=20912
The patch has been already accepted by upstream and I tested it with
Nvidia and Intel (with b
See the attached debdiff.
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Low
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
** Changed in: xorg-server (Ubuntu)
Milestone: None => ubuntu-9.04
Assignee: (unassigned) => Alberto Milone (a
Dragan: then (currently) you have no other choice. Things will change in
the future.
--
policyui.py crashed with AttributeError in checkVirtual()
https://bugs.launchpad.net/bugs/282283
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Can you attach your /var/log/Xorg.0.log, please?
--
Show screens as "unknown" instead of displaying the monitor names
https://bugs.launchpad.net/bugs/356834
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Martin:
yes, that could be done (in this very specific case) but it would still be nice
to see what happened.
In this case the transition can be smooth but usually there is no such
clear transition to new drivers. For example what happens if 180 is no
longer supported and part of the cards that i
** Changed in: xorg (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
Automatically enable mirroring for projectors
https://bugs.launchpad.net/bugs/359147
You received this bug notification because you are a member of Ubuntu
Bugs, which
What you're asking hasn't been implemented yet. It involves using KMS
(kernel mode setting) and sending events when a cable is plugged in
(i.e. interrupt-driven hotplug). Currently these events exist but are
sent only when you probe hardware manually (i.e. there's no auto
probing). Furthermore, eve
Larrin: Nvidia dropped the support for 177 and there's nothing we can do
about it, other than migrating users to 180.
--
nvidia -177 needs to be transitioned to -180 on upgrade
https://bugs.launchpad.net/bugs/351394
You received this bug notification because you are a member of Ubuntu
Bugs, which
the label in that UI is not accurate as it should say "Enable vertical
edge scrolling". What you describe is multifinger scrolling.
--
HP530: Touchpad vertical scrolling possible when "Enable vertical scrolling"
set to false.
https://bugs.launchpad.net/bugs/360023
You received this bug notificat
The bug affects a label in gnome-control-center instead of the synaptics
driver.
** Package changed: xserver-xorg-input-synaptics (Ubuntu) => gnome-
control-center (Ubuntu)
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
mobile: the package is in Jaunty's repository now.
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
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.
** Changed in: nvidia-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
linux-image-2.6.27-9-generic failed to install/upgrade : run-parts:
/etc/kernel/postinst.d/nvidia-common exited with return code 10
https://bugs.launchpad.net/bugs/303825
You received this
Martin, the following problem depended on Python but, according to doko it's
fixed now:
ERROR:root:NvidiaDetector can not be imported No module named
NvidiaDetector.nvidiadetector
As regards this error:
ERROR:root:NvidiaDetection returned a error: dir ./modaliases/ not found
it looks like only
** Changed in: nvidia-common (Ubuntu)
Status: Confirmed => In Progress
--
linux-image-2.6.27-9-generic failed to install/upgrade : run-parts:
/etc/kernel/postinst.d/nvidia-common exited with return code 10
https://bugs.launchpad.net/bugs/303825
You received this bug notification because y
Thanks for reopening a bug. I managed to reproduce the bug by setting
the path of the modaliases to a non valid value (so as to simulate the
case in which the modaliases are not found in the system) and I fixed
the problem by avoiding to raise an error when such path points to a
directory that does
Here's the same fix (with some changes due to the changes in Python) for
Jaunty.
** Attachment added: "nvidia-common_0.2.10.debdiff"
http://launchpadlibrarian.net/25455321/nvidia-common_0.2.10.debdiff
--
linux-image-2.6.27-9-generic failed to install/upgrade : run-parts:
/etc/kernel/postinst
SRU request for Intrepid:
Test case: nvidiadetector.py raises an exception when the modaliases are not
installed thus causing this bug.
Changes:
* NvidiaDetector/nvidiadetector.py:
- Exit without an error exit status in NvidiaDetection.__init__()
so as not to break dist-upgrades if the
if killing both gnome-setting-daemon and gnome-power-manager doesn't solve the
problem, please file a new bug report and follow the instructions reported here
to diagnose the problem:
https://wiki.ubuntu.com/X/Troubleshooting/HighCPU
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
I have just tried the driver and doesn't seem to work with my card
(Geforce 7300) while 180.37 does. Let's wait for a reply from Nvidia
about this.
--
nvidia driver 180.41 is available
https://bugs.launchpad.net/bugs/348852
You received this bug notification because you are a member of Ubuntu
Bug
*** This bug is a duplicate of bug 348852 ***
https://bugs.launchpad.net/bugs/348852
** This bug has been marked a duplicate of bug 348852
nvidia driver 180.41 is available
--
Sync nvidia binary driver 180.44
https://bugs.launchpad.net/bugs/352044
You received this bug notification becaus
** This bug is no longer a duplicate of bug 352044
Sync nvidia binary driver 180.44
** Summary changed:
- nvidia driver 180.41 is available
+ nvidia driver 180.44 is available
--
nvidia driver 180.44 is available
https://bugs.launchpad.net/bugs/348852
You received this bug notification becau
Here's the source for this new release (which works with my card) in addition
to a fix for bug 335621:
http://albertomilone.com/ubuntu/newlrm/recent/jaunty/nvidia-graphics-drivers-180_180.44-0ubuntu1.diff.gz
http://albertomilone.com/ubuntu/newlrm/recent/jaunty/nvidia-graphics-drivers-180_180.44-0u
I have reuploaded the tarball.
--
nvidia driver 180.44 is available
https://bugs.launchpad.net/bugs/348852
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
danielhollocher:
can you open hardware drivers manager take a screenshot and attach it?
--
nvidia-glx-177 isn't configured correctly after installation
https://bugs.launchpad.net/bugs/260049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
can you attach your /var/log/Xorg.0.log and your /etc/X11/xorg.conf ?
--
compiz.real crashed with SIGSEGV in _nv72gl()
https://bugs.launchpad.net/bugs/263040
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
oss_test_launchpad:
this is the problem:
Data incomplete in file /etc/X11/xorg.conf
Undefined InputDevice "Generic Keyboard" referenced by ServerLayout
"Default Layout".
(EE) Problem parsing the config file
(EE) Error parsing the config file
can you attach your /etc/X11/xorg.conf ?
--
I
Remove the ServerLayout section and the modules section so that it looks
like the following:
Section "Device"
Identifier "Configured Video Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Id
See the attached file
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/17231812/xorg.conf
--
Intrepid: Latest update destroys X server configuration on MacBook Pro (Nvidia
GeForce 8600M GT, nvidia-glx-177)
https://bugs.launchpad.net/bugs/263528
You received this bug notificatio
At least we know that it wasn't the nvidia driver.
It looks like either you or some other application modified the
xorg.conf and broke it. The references to the touchpad, keyboard and
mouse shouldn't have been put in the serverlayout section since they
didn't have their own sections.
I would like
*** This bug is a duplicate of bug 263528 ***
https://bugs.launchpad.net/bugs/263528
1) make sure that the linux-headers for your kernel are installed
2) type:
ls -Rl /var/lib/dkms/nvidia/ > dkms.txt
and attach the dkms.txt file
3) what's the model of your graphics card?
--
nvidia-glx doesnt
Unless you used displayconfig-gtk my only guess is that Jockey used
Guidance to set up your xorg.conf and something weird happened with
input devices. Let's assign the bug report to Jockey for now. I'll look
into this problem.
** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
Status: New
*** This bug is a duplicate of bug 261816 ***
https://bugs.launchpad.net/bugs/261816
type:
sudo apt-get install linux-headers-generic
sudo dkms build -m nvidia -v 177.70 -k 2.6.27-2-generic
sudo dkms install -m nvidia -v 177.70 -k 2.6.27-2-generic
and let me know what happens
** This bug is
** Changed in: nvidia-kernel-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: Confirmed => In Progress
--
Still uses multiuser argument to dh_installinit
https://bugs.launchpad.net/bugs/254264
You received this bug notification because you are a
Michael Vogt:
if you want I can give you a hand with this. We could do what we already do
with nvidia-common and change the driver in the xorg.conf (maybe with X-Kit)
according to what the modalias files say. This should be done for the fglrx
driver and for 2 nvidia drivers (71 and 96).
--
und
are you using Compiz? If yes, can you disable it, restart the Xserver
and see if you can reproduce the problem?
--
[intrepid] nvidia-settings fails to locate running nvidia driver
https://bugs.launchpad.net/bugs/264687
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Matt: I'm aware of the problem and I'm working on it. I'll also make
sure that dist-upgrades to Intrepid go smoothly.
--
[Intrepid] nvidia_drv.so: undefined symbol: AllocateScreenPrivateIndex
https://bugs.launchpad.net/bugs/251107
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 251107 ***
https://bugs.launchpad.net/bugs/251107
** This bug has been marked a duplicate of bug 251107
[Intrepid] nvidia_drv.so: undefined symbol: AllocateScreenPrivateIndex
--
nvidia-71.86.04 fails to build nv.o in DKMS
https://bugs.launchpad.net/bugs/
*** This bug is a duplicate of bug 263528 ***
https://bugs.launchpad.net/bugs/263528
Have a look at what I suggest here:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bug/263528/comments/1
** This bug has been marked a duplicate of bug 263528
Intrepid: Latest updat
** Changed in: nvidia-settings (Ubuntu)
Status: New => Invalid
--
[intrepid] nvidia-settings fails to locate running nvidia driver
https://bugs.launchpad.net/bugs/264687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
please type:
sudo nvidia-bug-report.sh
and attach the nvidia-bug-report.log which will be created in the same
directory in which you type the command
--
Intrepid Ibex: Nvidia GLX not present
https://bugs.launchpad.net/bugs/267475
You received this bug notification because you are a member of Ubu
yes, those are different bugs therefore you should file different bug
reports.
Thanks in advance for taking the time to report them.
--
Intrepid: Latest update destroys X server configuration on MacBook Pro (Nvidia
GeForce 8600M GT, nvidia-glx-177)
https://bugs.launchpad.net/bugs/263528
You rec
can you try with the attached xorg.conf?
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/17364544/xorg.conf
** Also affects: nvidia-graphics-drivers-177 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
Can't st
901 - 1000 of 4204 matches
Mail list logo
