Let me rephrase my request.
SRU: minimal patch for Jaunty is attached (see comment 3)
Nominating for SRU, fulfills: (1) have an obviously safe patch
The patch modifies only a header file so that extern "C" is used when
developers include the header in a C++ program. This condition is tested
with
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => In Progress
--
update request: nVidia ver 180.25, stable
https://bugs.launchpad.net/bugs/322416
You received
** Changed in: nvidia-settings (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Alberto Milone (albertomilone)
Status: New => Triaged
--
nvidia-settings needs to be updated
https://bugs.launchpad.net/bugs/315667
You received this bug notification because
*** This bug is a duplicate of bug 309116 ***
https://bugs.launchpad.net/bugs/309116
** This bug has been marked a duplicate of bug 309116
when removing nvidia-glx-177 /usr/lib/libGL.so is gone
--
package nvidia-glx-177 None failed to install/upgrade: ??
pre-installation script ?
Max: does killing gnome-settings-daemon solve the problem?
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Ok Max, it must be a different bug then. Please file a new bug report
and explain that, differently from this bug, killing gnome-settings-
daemon and gnome-power-manager doesn't solve the problem.
--
upgrade to 2:1.2.99.2-0ubuntu1 makes session utterly slow
https://bugs.launchpad.net/bugs/307306
This bug report is about a bug which seems to be triggered by nvidia-
common (even though it might depend on something else). This is what
William reported.
@all but William
You're facing a different bug. The NVidia driver doesn't seem to work (hence
DKMS fails to build and install the module) wi
William, can you still reproduce the problem?
--
2.6.30-8 kernel related packages fail to install
https://bugs.launchpad.net/bugs/384639
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.ubunt
To test the fix you can get the following source:
http://albertomilone.com/ubuntu/touchpad/daemon/x-bus_0.1-0ubuntu1.dsc
http://albertomilone.com/ubuntu/touchpad/daemon/x-bus_0.1-0ubuntu1.diff.gz
http://albertomilone.com/ubuntu/touchpad/daemon/x-bus_0.1.orig.tar.gz
I created two distinct environme
I have ported some of my patches from Jaunty to Karmic. Can anyone test
them in karmic, please?
See the attached debdiff.
** Attachment added:
"xserver-xorg-input-synaptics_1.1.1~git20090510-1ubuntu1.debdiff"
http://launchpadlibrarian.net/27527242/xserver-xorg-input-synaptics_1.1.1%7Egit2009
Currently it looks like Nvidia don't plan on adding the support for new
releases of X.org to the -71 flavour of their driver, therefore I'm
setting this bug report "Won't Fix".
Should Nvidia change their mind, don't hesitate to reopen this bug
report.
** Changed in: nvidia-graphics-drivers-71 (Ub
Let's pick up upstream's solution (which does the same thing as my patch
but in a different way) in commit
3f811a611185a3bdbb6b6d4c19590bd26ae1dc82
** Bug watch added: GNOME Bug Tracker #578111
http://bugzilla.gnome.org/show_bug.cgi?id=578111
** Changed in: gnome-desktop
Status: New =>
No, it wouldn't help because that still doesn't work with the new
xserver.
--
Please update to nVidia 71.86.09
https://bugs.launchpad.net/bugs/322895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
#n160
** Affects: libxi (Ubuntu)
Importance: Medium
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Changed in: libxi (Ubuntu)
Importance: Undecided => Medium
** Changed in: libxi (Ubuntu)
Status: New => In Progress
** Changed in: li
SRU Request:
I have cherrypicked the fix from upstream and it works for me. Please accept in
in jaunty-proposed.
Use case:
It should be possible to catch Xinput events from C++ as we do in C.
** Attachment added: "libxi_1.2.0-1ubuntu2.debdiff"
http://launchpadlibrarian.net/26465278/libxi_1.2.
Sorry, there was a mistake in the previous debdiff which said "jaunty"
instead of "jaunty-proposed" in the changelog. Please use this debdiff
instead.
** Attachment added: "libxi_1.2.0-1ubuntu2.debdiff"
http://launchpadlibrarian.net/26469592/libxi_1.2.0-1ubuntu2.debdiff
--
_XiGetDevicePresenc
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided => Medium
Status: Confirmed => In Progress
--
Please Upgrade to NVIDIA Stable 180
Can anyone who has an ALPS touchpad test the package in my PPA, 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 Ubuntu
Bugs, which is
darylb: can you attach the output of the following command?
xinput list-props 7
replace 7 with the identifier of your synaptic device.
--
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
Ok, my bad. Can you test the latest package in my PPA (0.99.3-2ubuntu3.1 ),
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 Ubuntu
B
Luke: type:
xinput list
and find the line about your touchpad so as to find it's id (for example you
will see "id=7"). Then type:
xinput list-props YOUR_ID
and attach the output
--
[Jaunty] Does not respond to tapping (scrolling fine)
https://bugs.launchpad.net/bugs/320585
You received this bu
darylb: can you attach the output of the following command again, please?
xinput list-props 7
replace 7 with the identifier of your synaptic device.
--
tap-to-click and edge-scrolling broken in Jaunty
https://bugs.launchpad.net/bugs/320632
You received this bug notification because you are a mem
dashua: thanks for reporting.
Nicolò: no, it's not but I don't own an ALPS touchpad therefore I rely on your
feedback. I'll upload a new version with the following settings:
SingleTapTimeout = 0
ClickTime = 0
But of course I'll have to hear from others to make sure that these
values don't cause
Ok, I've just uploaded 0.99.3-2ubuntu3.5 to my PPA. Here's a list of changes
(which will only affect ALPS touchpads):
- Set RightEdge to 840 (hoping that it solves darylb's problem).
- Set ClickTime to 0.
- Set SingleTapTimeout to 0.
- Set MinSpeed to 0.45.
- Set MaxSpeed to 0.75.
Let me kno
darylb: can you attach your /var/log/Xorg.0.log ?
--
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.u
Sure, if darylb reports that 895 works for him and this doesn't cause
problems to other ALPS users I'll put it in my patch.
--
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
Ok, I've just uploaded 0.99.3-2ubuntu3.6 to my PPA. Here's the only change
(only for ALPS touchpads):
- Set RightEdge to 910.
Let me know if the new settings work better for you or if something doesn't
work. In the latter case, please attach the output of of the following command:
xinput list-p
it's set to 900 in 0.99.3-2ubuntu3.7. Feedback is welcome
--
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
Can you attach your xorg.conf?
--
xkit exit with TypeError
https://bugs.launchpad.net/bugs/366624
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/
Should you have further doubts on X-Kit's API I suggest that you type:
import XKit.xutils
help(XKit.xutils)
--
xkit exit with TypeError
https://bugs.launchpad.net/bugs/366624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
ance: Undecided => Low
** Changed in: x-kit (Ubuntu)
Status: New => Triaged
** Changed in: x-kit (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
xkit exit with TypeError
https://bugs.launchpad.net/bugs/366624
You received this bug notification because yo
I have pushed the corrections to my bazaar branch:
https://code.launchpad.net/~albertomilone/xorgparser/main
and this:
print 'Position of "Configured Video Device" =', a.getIdentifier('Device',
'Configured Video Device')
should really have been:
print 'Position of "Configured Video Device" =', a
*** This bug is a duplicate of bug 364965 ***
https://bugs.launchpad.net/bugs/364965
** This bug has been marked a duplicate of bug 364965
Stable NVIDIA driver 180.53 released - please upgrade in Jaunty
--
[jaunty] Xorg crashes with NVIDIA when visit http://www.tim.it
https://bugs.launchp
The md5sum is correct.
it should say:
compiled for 1.6.0, module version = 1.0.0
instead of:
compiled for 1.5.2, module version = 1.0.0
and:
ABI class: X.Org Server Extension, version 2.0
instead of:
ABI class: X.Org Server Extension, version 1.1
--
Xorg couldn't load libglx.so because of inc
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
Xorg couldn't load libglx.so because of incorrect ABI version
https://bugs.launchpad.net/bugs/367316
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
As discussed on IRC the problem was solved after restarting the system.
--
Xorg couldn't load libglx.so because of incorrect ABI version
https://bugs.launchpad.net/bugs/367316
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
Close Jockey then type:
sudo killall jockey-backend
Install nvidia-common:
sudo apt-get install nvidia-common
Then launch Jockey again and see if it solves the problem.
--
(NVidia) "Hardware Drivers" is empty
https://bugs.launchpad.net/bugs/31
You received this bug notification because you
** Bug watch added: freedesktop.org Bugzilla #21613
https://bugs.freedesktop.org/show_bug.cgi?id=21613
** Also affects: xorg-driver-synaptics via
https://bugs.freedesktop.org/show_bug.cgi?id=21613
Importance: Unknown
Status: Unknown
--
Touchpad is sensitive over physical button a
** Bug watch added: freedesktop.org Bugzilla #21614
https://bugs.freedesktop.org/show_bug.cgi?id=21614
** Also affects: xorg-driver-synaptics via
https://bugs.freedesktop.org/show_bug.cgi?id=21614
Importance: Unknown
Status: Unknown
--
Mouse cursor jumps when two fingers are used
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Triaged
--
gnome-display-properties mistakenly requires logout to increase resolution
https://bugs.launchpad.net/bugs/365210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have provided upstream with a fix. See the patch in the upstream bug
report.
** Package changed: gnome-control-center (Ubuntu) => gnome-desktop
(Ubuntu)
** Bug watch added: GNOME Bug Tracker #580754
http://bugzilla.gnome.org/show_bug.cgi?id=580754
** Also affects: gnome-desktop via
http:
*** This bug is a duplicate of bug 314406 ***
https://bugs.launchpad.net/bugs/314406
SanketMedhi: please file a new bug report. I think you're facing a
different bug (otherwise the workaround would work for you).
--
gnome-settings-daemon segmentation fault
https://bugs.launchpad.net/bugs/309
nassigned) => Alberto Milone (albertomilone)
--
Stable NVIDIA driver 180.51 released - please upgrade in Jaunty
https://bugs.launchpad.net/bugs/364965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
nassigned) => Alberto Milone (albertomilone)
--
system freezes with nvidia 180.37 driver
https://bugs.launchpad.net/bugs/353502
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.ubun
Unfortunately driver 71.xx won't be updated to work with the new xserver
and there is nothing we can do about it. Should things change in the
future, feel free to reopen this bug report.
** Changed in: nvidia-graphics-drivers-71 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia
It says "Unknown monitor" because the Nvidia driver doesn't support
RandR 1.2 or higher. There is nothing we can do about it.
You should use "nvidia-settings" instead of gnome-display-properties.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Low => Wishlist
--
Unknown monit
*** This bug is a duplicate of bug 354638 ***
https://bugs.launchpad.net/bugs/354638
** This bug has been marked a duplicate of bug 354638
package nvidia-glx-180 180.37-0ubuntu2 failed to install/upgrade:
conflicting packages - not installing nvidia-glx-180
--
ed to install/upgrade: conf
DERG: I can't open the patches suggested in this bug report. Can you
attach them here on launchpad, please?
--
In Ubuntu 8.10 & Ubuntu 9.04 alpha 6 fully updated certain Nvidia drivers
causes programs to crash.
https://bugs.launchpad.net/bugs/345337
You received this bug notification because you
In the logs I can only see that the vesa driver is used instead of Nvidia.
Please reproduce the problem, then go the console and type:
sudo nvidia-bug-report.sh
and you will find a new log in you home directory, please attach it.
--
Nvidia driver 180 does not install on Intrepid - followup from
SRU request:
The debdiff and the package can be found in bug 365943. This patch won't
cause regressions (as the option is disabled by default) and will be
very useful to the OEM team.
Please accept it in jaunty-proposed.
--
Touchpad is sensitive over physical button area
https://bugs.launchpad.
SRU request:
Here is the debdiff which also includes the patch from bug 365952. Both patches
have been tested and the package can be found in the PPA of the X team:
https://edge.launchpad.net/~ubuntu-x-swat/+archive/x-updates/
Please accept this in jaunty-proposed.
** Attachment added: "xfree86
to take place after the movement thus causing me to
click on the wrong icon, button, etc.
The driver should allow the deactivation of the area over the physical
buttons.
** Affects: xfree86-driver-synaptics (Ubuntu)
Importance: Wishlist
Assignee: Alberto Milone (albertomilone
I have modified the title of the bug report since having driver 180.53
would fix bug 353502 too.
** Summary changed:
- Stable NVIDIA driver 180.51 released - please upgrade in Jaunty
+ Stable NVIDIA driver 180.53 released - please upgrade in Jaunty
--
Stable NVIDIA driver 180.53 released - plea
I found the cause of the problem and I dramatically reduced the problem
(we tested this in the OEM team).
Sometimes the reported movement deltas are too big to actually take
place in 20 milliseconds or less (no human hand would ever be able to
move this fast).
Furthermore, a comparison between th
Assignee: Alberto Milone (albertomilone)
Status: In Progress
** Changed in: xfree86-driver-synaptics (Ubuntu)
Importance: Undecided => Medium
** Changed in: xfree86-driver-synaptics (Ubuntu)
Status: New => In Progress
** Changed in: xfree86-driver-synaptics (Ubuntu)
Mil
As you can see in the attached patch, I have implemented the support for
a "MovementBottomEdge" option which, if set through either xorg.conf,
synclient or xinput, allows users to blacklist the area of the touchpad
below the value set in this option.
For example to set the new property to "4100" t
The new driver is available in this PPA:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
--
Stable NVIDIA driver 180.53 released - please upgrade in Jaunty
https://bugs.launchpad.net/bugs/364965
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
** Changed in: update-manager (Ubuntu)
Status: Confirmed => Invalid
--
Latest Xorg removes nvidia driver ... conflicting xserver-xorg-video-4
https://bugs.launchpad.net/bugs/308410
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I can confirm that the package in jaunty-proposed solves the problem. I
can compile my program without getting the error.
--
_XiGetDevicePresenceNotifyEvent can't be used from C++
https://bugs.launchpad.net/bugs/373711
You received this bug notification because you are a member of Ubuntu
Bugs, wh
FFE request:
I am convinced that a stable release shouldn't ship with a tool which
breaks the xorg.conf, therefore I have replaced the nvidia-xconfig
binary with a python script (which depends on python-xkit) that covers
the basic functionalities of the binary.
See the attached debdiff.
** Attac
can you post the output of this command?
ls -l /usr/lib/xorg/modules/extensions/
--
package nvidia-glx-177 177.80-0ubuntu1 [modified: usr/bin/nvidia-bug-report.sh
usr/bin/nvidia-xconfig usr/lib/xorg/modules/drivers/nvidia_drv.so
usr/share/man/man1/nvidia-xconfig.1.gz] failed to install/upgrade:
Rocko: I suggested that before Aaron came up with a fix.
--
Screen refresh problems with nvidia on intrepid
https://bugs.launchpad.net/bugs/269904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
can you attach your /var/log/dist-upgrade/apt-term.log ?
--
nvidia upgrade fail in kernel 2.6.24-21 upgrade
https://bugs.launchpad.net/bugs/283905
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Lars:
I know that it will take a lot of time but I would be glad if you could follow
these steps from your backup:
1) upgrade only the linux-restricted-modules manually
2) run the dist-upgrade from Update Manager and see if you can reproduce the
problem
I believe that doing so will remove any fg
Thanks for posting your ids (with lspci) but this is not required any
more.
--
Screen refresh problems with nvidia on intrepid
https://bugs.launchpad.net/bugs/269904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Did you launch the program with "sudo"?
** Changed in: nvidia-common
Status: New => Invalid
** Changed in: xorg-server
Status: New => Invalid
--
nvidia-settings crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/284177
You received this bug notification bec
1) what resolution do you use in Windows?
2) can you attach your /etc/X11/xorg.conf ?
--
nvidia graphics card error when you install drivers
https://bugs.launchpad.net/bugs/271618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
This part looks very suspicious:
Purging configuration files for nvidia-glx ...
dpkg-divert: mismatch on package
when removing `diversion of /usr/lib/libGL.so.1 to
/usr/lib/nvidia/libGL.so.1.xlibmesa by nvidia-glx'
found `diversion of /usr/lib/libGL.so.1 to
/usr/lib/nvidia/libGL.so.1.xlibmesa
This line from the log looks very suspicious:
(II) NVIDIA(0): Virtual screen size determined to be 1600 x 1280
Type:
sudo nvidia-settings
and try to set the correct resolution from there. Then save your
settings and restart the Xserver.
Let me know how it goes.
--
nvidia graphics card error wh
Did you install the driver through the installer from NVIDIA's website
too?
--
package nvidia-glx-177 177.80-0ubuntu1 [modified: usr/bin/nvidia-bug-report.sh
usr/bin/nvidia-xconfig usr/lib/xorg/modules/drivers/nvidia_drv.so
usr/share/man/man1/nvidia-xconfig.1.gz] failed to install/upgrade: tryi
Ok, here's the debdiff.
** Attachment added:
"linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.debdiff"
http://launchpadlibrarian.net/18607186/linux-restricted-modules-envy-2.6.24_2.6.24.503-503.31.debdiff
--
nvidia: Multiple versions in DKMS
https://bugs.launchpad.net/bugs/261816
You
3) yes please. Furthermore you will have to install nvidia-settings:
sudo apt-get install nvidia-settings
4) no, I meant the /var/log/Xorg.0.log
--
nvidia graphics card error when you install drivers
https://bugs.launchpad.net/bugs/271618
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 261816 ***
https://bugs.launchpad.net/bugs/261816
Michael: that's a problem that I solved in Intrepid, however the error refers
to the packages in Hardy (which don't have the fix yet):
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bu
fglrx-kernel-source depends on the following packages:
Depends: make, dkms, linux-libc-dev, linux-headers
maybe we could make it depend on the following packages as I did with
nvidia-VER-kernel-source:
Depends: make, dkms, linux-libc-dev, linux-headers-generic | linux-headers
** Also affects: fg
As regards Hardy, I will backport the fix from Intrepid soon.
--
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.ubun
Ok but did you click on "Save to X Configuration File"?
--
nvidia graphics card error when you install drivers
https://bugs.launchpad.net/bugs/271618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Brian: did you have the fglrx driver installed or do you have evidence
that the fglrx driver was loaded during the upgrade?
Lars: thanks for the update. Let me know how the next dist-upgrade goes
--
fglrx kernel module crashes system hard during hardy to intrepid upgrade
https://bugs.launchpad.n
Graham: can you attach the output of this command?
dpkg-divert --list
--
Update the NVIDIA driver to 173.14.12
https://bugs.launchpad.net/bugs/254596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
*** This bug is a duplicate of bug 261816 ***
https://bugs.launchpad.net/bugs/261816
I can't see the problem in the logs. Can you attach all the files you
have in your /var/log/apt/ directory, please?
--
nvidia upgrade fail in kernel 2.6.24-21 upgrade
https://bugs.launchpad.net/bugs/283905
Y
Brian: ok, then it's not the same problem as the one that Lars reported
since he wasn't using fglrx and the module got loaded somehow.
--
fglrx kernel module crashes system hard during hardy to intrepid upgrade
https://bugs.launchpad.net/bugs/278963
You received this bug notification because you
I guess the fglrx module was still loaded (hence the garbled screen).
The "refresh" icons which show up in Jockey after you install or
uninstall a driver suggest to restart the computer.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: New => Invalid
--
Deactivating fglrx through jo
As far as I know there is very little Jockey can do as it can't do "sudo
rmmod fglrx" if the module is in use. when you log out and log in or
simply press CTRL+ALT+Backspace, there's nothing which unloads the
module, therefore you use the open source driver with a proprietary
kernel module and the
I don't know how the nvidia driver works but it looks like nvidia-
settings is the best way to deal with its peculiarities.
Thanks for taking the time to report the problem.
** Changed in: xserver-xorg-video-nv (Ubuntu)
Status: Incomplete => Invalid
--
nvidia graphics card error when you
You really can't compare fglrx with ati.
Martin, I know that it's too late for Jockey in Intrepid but maybe in
Jaunty we might want to notify users in a different way.
--
Deactivating fglrx through jockey in intrepid gives garbled screen
https://bugs.launchpad.net/bugs/284433
You received this b
It's ok. I asked him to attach those files.
--
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
https://lis
Authority:
1) Did you install the NVIDIA driver from the NVIDIA installer (the one from
NVIDIA's website) too?
2) can you attach the output of these commands?
ls -l /usr/lib/
--
package nvidia-glx-173 None failed to install/upgrade: trying to overwrite
`/usr/lib/libGL.so.1', which is also in pa
Bryce: I think that the only thing we can do is adopt Aaron's patch for Compiz.
Here's his PPA:
https://launchpad.net/~aplattner/+archive
Maybe either you or Michael (mvo) can review his patch (see the
attachment)?
** Attachment added: "049-damage-report-non-empty.patch"
http://launchpadlibra
can you attach the following files?
/var/log/Xorg.0.log
/var/log/Xorg.0.log.old
/etc/X11/xorg.conf
--
X fails to start with proprietary nvidia driver
https://bugs.launchpad.net/bugs/284715
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Lars: this is good news. At least we have a workaround now and we can
use it in Update Manager.
Henrik: thanks for your feedback. I have yet to figure out what can
modprobe fglrx at random.
Steve: right.
Brian: can you try the dist-upgrade again (so as to reproduce the
problem) and attach your /
Public bug reported:
Binary package hint: nvidia-settings
Request for nvidia-settings to be included in main, as a "recommends" of
the nvidia-glx-VER packages, so as to allow users to configure NVIDIA's
proprietary driver as regards power management, multiple screens, colour
correction, etc.
See
Grandr? What program are you using to set up your screens?
--
Multiple screens window doesn't remember setting after reboot
https://bugs.launchpad.net/bugs/278038
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: fglrx-installer (Ubuntu)
Status: New => Invalid
--
fglrx module fails to build
https://bugs.launchpad.net/bugs/284854
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
Well, I don't know why it's installed on your system but I can assure
you that it's not installed by default.
--
Multiple screens window doesn't remember setting after reboot
https://bugs.launchpad.net/bugs/278038
You received this bug notification because you are a member of Ubuntu
Bugs, which i
what's the output of this command?
ls -lR /var/lib/dkms/nvidia
--
nVidia Corporation NV18GL [Quadro NVS 280 SD] (rev a2) not detected by jockey,
no binary drivers available
https://bugs.launchpad.net/bugs/293107
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ok, it looks like the problem was not fixed in driver 71 but only in 96.
--
[Intrepid] nvidia_drv.so: undefined symbol: AllocateScreenPrivateIndex
https://bugs.launchpad.net/bugs/251107
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Can you reproduce the problem (with full screen applications) if you
disable Compiz?
--
Input Signal Out of Range(Specific to Full-Screen Apps)
https://bugs.launchpad.net/bugs/293739
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
Xavier: can you attach the log which says "No devices detected"?
--
[Intrepid] nvidia_drv.so: undefined symbol: AllocateScreenPrivateIndex
https://bugs.launchpad.net/bugs/251107
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Xavier: here's the problem:
(WW) NVIDIA(0): The NVIDIA RIVA TNT2 Model 64/Model 64 Pro GPU installed in
(WW) NVIDIA(0): this system is supported through the NVIDIA Legacy
(WW) NVIDIA(0): drivers. Please visit
(WW) NVIDIA(0): http://www.nvidia.com/object/unix.html for more
(WW) NVIDIA(0)
It is likely that your BIOS is assigning the IRQs instead of the OS. Check
your bios settings and let the OS manage the IRQs. For example if your BIOS
has an option for "Plug and Play Operating System", or similar, and if it is
set to 'Yes' or 'Enabled' then set it to 'No' or 'Disabled'.
Let me
Please type the following command:
sudo nvidia-bug-report.sh
and attach the nvidia-bug-report.log that will be created in the same
directory in which you type the command.
--
Conflict between nvidia-glx and openafs-modules kernel module
https://bugs.launchpad.net/bugs/294527
You received this bu
101 - 200 of 4204 matches
Mail list logo
