[Bug 1693715] Re: Laptop flat panel show blank screen after undocking with 2 DP displays on dock
*** This bug is a duplicate of bug 1370720 *** https://bugs.launchpad.net/bugs/1370720 ** This bug has been marked a duplicate of bug 1370720 unity-settings-daemon can deadlock if a modeset fails -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693715 Title: Laptop flat panel show blank screen after undocking with 2 DP displays on dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1693715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426]
Yeah, it should. Thanks for the ping.
Marking fixed with commit fe4c774c572e3f55a7417f0ca336ae1479a966ad
Author: Nikhil Mahale nmah...@nvidia.com
Date: Sat Jan 24 17:06:59 2015 -0800
os: Fix timer race conditions
Fixing following kind of race-conditions -
WaitForSomething()
|
// timers - timer-1 - timer-2 - null
while (timers (int) (timers-expires - now) = 0)
// prototype - DoTimer(OsTimerPtr timer, CARD32 now,
OsTimerPtr *prev)
DoTimer(timers, now, timers)
|
|
OsBlockSignals(); OS Signal comes just before
blocking it,
timer-1 handler gets called.
// timer-1 gets served and
scheduled again;
// timers - timer-2 -
timer-1 - null
*prev = timer-next;
timer-next = NULL; // timers - null
// timers list gets corrupted here and timer-2 gets
removed from list.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=86288
Signed-off-by: Nikhil Mahale nmah...@nvidia.com
Reviewed-by: Julien Cristau jcris...@debian.org
v2: Apply warning fixes from Keith Packard kei...@keithp.com
Reviewed-by: Aaron Plattner aplatt...@nvidia.com
Signed-off-by: Aaron Plattner aplatt...@nvidia.com
Signed-off-by: Keith Packard kei...@keithp.com
os/WaitFor.c | 41 ++---
1 file changed, 26 insertions(+), 15 deletions(-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1220426
Title:
[nvidia-prime]Freeze while using touchpad
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1220426/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
Does it work if you use a path that doesn't have any spaces in it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
Fixing the bug status again. I don't know why this keeps getting reopened as an nvidia-prime or graphics driver bug. ** Changed in: nvidia-graphics-drivers-346 (Ubuntu) Status: Confirmed = Invalid ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed = Invalid ** Changed in: nvidia-drivers-ubuntu Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad
** Also affects: xorg-server Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-319 (Ubuntu) Status: Triaged = Invalid ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Triaged = Invalid ** Changed in: nvidia-graphics-drivers-343 (Ubuntu) Status: Triaged = Invalid ** Changed in: nvidia-prime (Ubuntu) Status: Triaged = Invalid ** Changed in: xorg-server Assignee: (unassigned) = Nikhil Mahale (nmahale) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1220426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370720] [NEW] unity-settings-daemon can deadlock if a modeset fails
Public bug reported: The system I used to reproduce this bug was a laptop with two display devices (one DisplayPort, one DVI) connected to a docking station. Dock the laptop. unity-settings-manager triggers a display change to extended mode. Then, undock the laptop. The following sequence of events triggers a deadlock: 1. The system generates an ACPI event that video.ko turns into a display change hotkey press. 2. Something sees the display change hotkey event and calls unity-settings-manager via dbus. 3. The X driver sees the DVI monitor go away and updates the RandR configuration. 4. unity-settings-manager enters handle_fn_f7() and calls gnome_rr_screen_refresh(). 5. gnome_rr_screen_refresh() sees that the configuration changed and calls the callbacks. 6. The X driver sees the DP monitor go away and updates the RandR configuration. 7. on_randr_event() tries to reconfigure the desktop with the DVI monitor disabled and the DP monitor enabled. 8. The RandR SetCrtcConfig call fails because it's trying to set a mode on a disconnected output. 9. apply_configuration() calls error_message(), which tries to pop up a dialog box. Step #9 deadlocks because gnome_rr_screen_refresh() called XGrabServer() in step #5. Upstream gnome-settings-daemon fixed this with commit 0f7cbfed5e5e76824e057ce9c570fad66ba001c6. https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0f7cbfed5e5e76824e057ce9c570fad66ba001c6 This change cherry-picks cleanly to unity-settings-daemon. (as an aside, the video.ko display change hotkey events are entirely pointless and probably deserve their own bug) ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370720 Title: unity-settings-daemon can deadlock if a modeset fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1370720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia cards
Christopher, is there some actual discussion somewhere where licensing is called out as a problem, or are you just referring to Stephen's comment #325? I'll bet it just that no one who has permission to push updated packages has noticed this bug and I don't know how to attract the attention of someone who does. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia cards
Ah, thanks for the clarification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia cards
Is there still some concern about accepting the patch? It was indeed authored by James Jones and signed off by him for public release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292563] Re: nvidia driver fails to initialize on Haswell without upstream kernel patch
Thanks Andy! I can confirm that your kernel fixes the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292563 Title: nvidia driver fails to initialize on Haswell without upstream kernel patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1292563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292563] [NEW] nvidia driver fails to initialize on Haswell without upstream kernel patch
Public bug reported: I have a Haswell-based Optimus laptop. Trying to initialize the NVIDIA driver fails: [ 58.885456] [drm] Initialized nvidia-drm 0.0.0 20130102 for :03:00.0 on minor 1 [ 58.885462] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 334.23 Sun Mar 9 21:06:05 PDT 2014 [ 58.886183] vgaarb: this pci device is not a vga device [ 58.887550] nvidia :03:00.0: irq 69 for MSI/MSI-X [ 58.894206] NVRM: failed to copy vbios to system memory. [ 58.896770] NVRM: RmInitAdapter failed! (0x30:0x:720) [ 58.896777] NVRM: rm_init_adapter failed for device bearing minor number 0 [ 58.896796] NVRM: nvidia_frontend_open: minor 0, module-open() failed, error -5 This is fixed by cherry-picking the following kernel commit: commit 11b88ee275ec8590a373396888c2460ee89364d6 Author: Rafael J. Wysocki rafael.j.wyso...@intel.com Date: Mon Sep 9 23:07:47 2013 +0200 ACPI / bind: Prefer device objects with _STA to those without it As reported at https://bugzilla.kernel.org/show_bug.cgi?id=60829, there still are cases in which do_find_child() doesn't choose the ACPI device object it is expected to choose if there are more such objects matching one PCI device present. This particular problem may be worked around by making do_find_child() return device obejcts witn _STA whose result indicates that the device is enabled before device objects without _STA if there's more than one device object to choose from. This change doesn't affect the case in which there's only one matching ACPI device object per PCI device. References: https://bugzilla.kernel.org/show_bug.cgi?id=60829 Reported-by: Peter Wu lekenst...@gmail.com Tested-by: Felix Lisczyk felix.lisc...@gmail.com Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com drivers/acpi/glue.c | 35 --- 1 file changed, 24 insertions(+), 11 deletions(-) Ubuntu 13.10 is also affected, while the 14.04 beta works since it includes the above commit. # lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 # apt-cache policy linux-image-3.11.0-18-generic linux-image-3.11.0-18-generic: Installed: 3.11.0-18.32~precise1 Candidate: 3.11.0-18.32~precise1 Version table: *** 3.11.0-18.32~precise1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: linux-lts-saucy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292563 Title: nvidia driver fails to initialize on Haswell without upstream kernel patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1292563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse
The original report was against GNOME 3, which doesn't use Compiz. Jamie, are you using Compiz, or gnome-shell? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288747 Title: [334] Parts of the UI randomly flicker when moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1288747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse
I'll wait for Jamie to chime in since he reported the bug, but Alex, your problem sounds like #269904. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1288747 Title: [334] Parts of the UI randomly flicker when moving the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1288747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 967091] Re: Wrong tint in flash when it uses video acceleration
On 10/23/2012 02:11 PM, Sebastian Boehm wrote: Ok, just updated my bzr branch and the debdiff. Aaron, could you have a look at it? I tried to keep changes to the bare minimum. Looks okay to me. --- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967091 Title: Wrong tint in flash when it uses video acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/libvdpau/+bug/967091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967091] Re: Wrong tint in flash when it uses video acceleration
Hi Sebastian, It probably doesn't matter for the Debian build system, but Stephen's version of the change breaks distcheck. I'd suggest using the upstream version: git format-patch -1 ca9e637c61e80145f0625a590c91429db67d0a40 ** Patch added: Upstream commit ca9e637c61e80145f0625a590c91429db67d0a40 https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/967091/+attachment/3410567/+files/0001-Implement-workarounds-for-Adobe-Flash-bugs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967091 Title: Wrong tint in flash when it uses video acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/libvdpau/+bug/967091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967091] Re: Wrong tint in flash when it uses video acceleration
Strange. The line in question is the one I mentioned in my reply to Stephen's original mail: http://lists.freedesktop.org/archives/vdpau/2012-September/23.html + +libvdpausysconfdir=$(sysconfdir) +libvdpausysconf_DATA = vdpau_wrapper.cfg This breaks distcheck: make[3]: *** No rule to make target `vdpau_wrapper.cfg', needed by `all-am'. Stop. I think this needs to be dist_libvdpausysconf_DATA. I'm not sure why you wouldn't be seeing that in the Debian package since your debdiff adds the incorrect line rather than the fixed version in the upstream repository: +@@ -27,3 +28,6 @@ libvdpauincludedir = $(includedir)/vdpau + libvdpauinclude_HEADERS = \ + $(top_srcdir)/include/vdpau/vdpau.h \ + $(top_srcdir)/include/vdpau/vdpau_x11.h ++ ++libvdpausysconfdir=$(sysconfdir) ++libvdpausysconf_DATA = vdpau_wrapper.cfg In any case, if it works for you and no one is actually expecting to use dist / distcheck from the Ubuntu package, then the difference is moot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967091 Title: Wrong tint in flash when it uses video acceleration To manage notifications about this bug go to: https://bugs.launchpad.net/libvdpau/+bug/967091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037896] Re: Starting Firefox kills xserver immediately when using 2D desktop
As Daniel mentioned, the problem is in OpenGL. If you are willing to run without it, you can work around the problem for now by disabling the glx module in /etc/X11/xorg.conf by adding the following lines: Section Module Disable glx EndSection This issue was caused because the video driver ABI version was changed correctly, but nobody noticed that the extension module ABI needed to be bumped as well. That's why the problem only affects libglx and not the nvidia X driver. Please note that we do not officially support pre-release or release candidate X servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037896 Title: Starting Firefox kills xserver immediately when using 2D desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316802] Re: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
I stopped using Liferea ages ago. Closing as Invalid - Don't Care. ** Changed in: liferea (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/316802 Title: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/316802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 733374] Re: X freeze, nvidia-current, Ubuntu 11.04 Maverick GeForce 9600GT
No, the Xid messages are not documented, they're internal error codes to help us with debugging. In Anoop's case, all they really mean is that the driver stopped hearing from the graphics card suddenly and was unable to restore communications with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/733374 Title: X freeze, nvidia-current, Ubuntu 11.04 Maverick GeForce 9600GT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/733374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 733374] Re: X freeze, nvidia-current, Ubuntu 11.04 Maverick GeForce 9600GT
Anoop, these symptoms sound very much like a hardware problem that causes the GPU to sometimes lose contact with the rest of the system. Please make sure your case is free of dust and that the fans are unobstructed, that all connectors are seated firmly, and that your power supply has a sufficiently high power rating. If you still experience the problem, please try running nvidia-settings and selecting the Thermal Settings tab to monitor the GPU temperature to see whether it's unreasonably high when the errors occur. Finally, if you have a different GPU you could try in the same system, you could tell if the one you're using is simply damaged. Moving the GPU to a different slot, if one is available, might also help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/733374 Title: X freeze, nvidia-current, Ubuntu 11.04 Maverick GeForce 9600GT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/733374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 734325] Re: Natty: Users should be able to easily turn off (disable) global menu
This menu-removing behavior also breaks the usability of multiple X screen configurations because the global menu bar is not present on the second screen, but the application menu bar is still removed, leaving no menu bar anywhere at all as a result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/734325 Title: Natty: Users should be able to easily turn off (disable) global menu To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/734325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661248] Re: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260
Thanks, Joakim. On the contrary, that's quite interesting. The first four bytes should never be all 0xff if the GPU is configured correctly by the kernel. If the kernel has misconfigured the GPU in such a way that it cannot respond to register reads, the driver has no hope of working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661248 Title: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661248] Re: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260
I think that's the wrong resource0 file (for bus 0 device 2, rather than bus 2 device 0). Probably easier to use the symlinks: /sys/bus/pci/devices/:02:00.0/resource0 However, you can't call read() on those files, they can only be mmap'd. /dev/mem should work, though. I would recommend reading a whole page: dd if=/dev/mem of=asdf bs=4096 skip=1036288 count=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661248 Title: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661248] Re: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260
TJ, that rm_is_supported_device function reads registers that it sounds like are reading back as 0x. You should be able to read the DWORD at BAR0 offset 0. If it reads as 0x, then the GPU is not configured correctly. You should be able to do that before even loading the NVIDIA RM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661248 Title: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661248] Re: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260
@TJ: The BAR configuration registers are in the PCI configuration space. I'm talking about the registeres accessed via memory read/write cycles to the addresses configured there. E.g., open /dev/mem and read at the offset that lspci reports for Region 0 for your GPU. Alternatively, mmap /sys/devices/path/to/the/gpu/resource0 and read offset 0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661248 Title: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768178] Re: compiz crashed with SIGSEGV in nux::IOpenGLShaderProgram::Begin()
Jay, can you describe in more detail what criteria Unity uses to make this decision? Nothing should have changed in the driver between 173.14.28 and 173.14.30 that would have affected this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768178 Title: compiz crashed with SIGSEGV in nux::IOpenGLShaderProgram::Begin() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703688] Re: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa)
xserver 1.10 doesn't exist yet, and the ABI it's going to use won't be frozen until 1.10 RC2 (a.k.a 1.9.99.902) is released. Until then, the NVIDIA driver can't assume that the ABI won't change in the future. I pinged the people responsible for releases, but didn't hear anything back. The official xserver 1.10 release is scheduled for Friday the 18th, according to my calendar, so hopefully RC2 will be soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703688 Title: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626974] Re: ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
Please give 96.43.19 a try. It was just released, so it might be a while before somebody packages it for Ubuntu. -- ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick https://bugs.launchpad.net/bugs/626974 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/listinfo/ubuntu-bugs
[Bug 661248] Re: Nvidia GeForce 8600M GT doesn't work with nvidia-current 260
The GPU is not responding correctly to CPU accesses, hence the nouveau error message of, Unsupported chipset 0x. This is not a driver bug: it could be a bug in the kernel, or a hardware problem. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Confirmed = Invalid -- Nvidia GeForce 8600M GT doesn't work with nvidia-current 260 https://bugs.launchpad.net/bugs/661248 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/listinfo/ubuntu-bugs
[Bug 652731] Re: Appearance settings do not work in Xubuntu 10.10 RC
This doesn't sound at all like a graphics driver bug, but rather a communication problem between the various XFCE components. The driver does not control the appearance of fonts or icons, but simply processes the drawing requests sent to it by applications. Does the problem still occur with the vesa driver? -- Appearance settings do not work in Xubuntu 10.10 RC https://bugs.launchpad.net/bugs/652731 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/listinfo/ubuntu-bugs
[Bug 652731] Re: Appearance settings do not work in Xubuntu 10.10 RC
Crap, I didn't mean to add this. Marking invalid. ** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Changed in: nvidia-drivers-ubuntu Status: New = Invalid ** Also affects: xfce4 Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New = Invalid -- Appearance settings do not work in Xubuntu 10.10 RC https://bugs.launchpad.net/bugs/652731 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/listinfo/ubuntu-bugs
Re: [Bug 626918] Re: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
On Sat, Oct 02, 2010 at 11:38:49AM -0700, Aldo Maggi wrote: a...@paperino:~$ dpkg -l nvidia-173 ii nvidia-173 173.14.27-0ubuntu1 NVIDIA binary Xorg driver, kernel module and VDPAU library should i uninstall it and get the 173.14.28 binary from nvidia site? You could, or you could wait for someone from Ubuntu to package it for you. -- /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData https://bugs.launchpad.net/bugs/626918 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/listinfo/ubuntu-bugs
[Bug 626918] Re: /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
Please try 173.14.28. -- /usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData https://bugs.launchpad.net/bugs/626918 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/listinfo/ubuntu-bugs
[Bug 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
Please try 260.19.06: http://www.nvnews.net/vbulletin/showthread.php?t=155137 -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 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/listinfo/ubuntu-bugs
[Bug 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
At least NVidias Aaron Plattner claims it is merely a regression in xserver 1.9. I didn't say that. All I said was that if an experiment shows that using the same driver, xserver 1.8 is fast and xserver 1.9 is slow, that it's not reasonable to immediately assume that the problem is in the driver. It's still possible for the problem to be in the driver, but we now have one point of circumstantial evidence that it's not (except that you just contradicted your earlier posts by saying that 256.44 is *not* slow with xserver 1.9). Somebody needs to do some more investigation to say for sure one way or the other. I don't have time to look at it right now, I'm afraid. -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623399] Re: nvidia drivers fail to start in Maverick X11
A driver with support for the new ABI should be out relatively soon, though I can't make any actual promises as to a release date. If scrolling using the same driver but a different X server shows different performance, it's highly likely that the regression is in the X server and not the driver. -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 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/listinfo/ubuntu-bugs
[Bug 595845] Re: libcairo2 1.9.10 makes Ubuntu 10.10 slow
P0per, when you say you are using current NVIDIA drivers, which version, exactly, are you using? The latest drivers accelerate gradients on all GeForce 8 series and up GPUs, and should be quite fast. -- libcairo2 1.9.10 makes Ubuntu 10.10 slow https://bugs.launchpad.net/bugs/595845 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/listinfo/ubuntu-bugs
[Bug 605979] Re: Buttons rendered wrong (with white background) with nvidia-current
Hi Benjamin. This is the first I've heard of this bug, so I'll try to take a look at it as soon as I can. Please note that just checking for the NV-CONTROL extension is not sufficient, because some screens may be using the NVIDIA driver while others use different drivers. If the extension exists, you can use XNVCTRLIsNvScreen to query if a given screen is using the NVIDIA driver. However, please don't do that. I'd much rather just fix the driver if it's broken then have a driver-specific workaround in place that we need to get rid of eventually. -- Buttons rendered wrong (with white background) with nvidia-current https://bugs.launchpad.net/bugs/605979 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/listinfo/ubuntu-bugs
[Bug 604525] Re: nvidia-settings Configure Display Device menu should be drop-down list instead of dialog box
Thanks, Philip. I've attached Bert's patch to our internal bug for this, which is #357963. -- nvidia-settings Configure Display Device menu should be drop-down list instead of dialog box https://bugs.launchpad.net/bugs/604525 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/listinfo/ubuntu-bugs
[Bug 278055] Re: nvidia-settings generates broken xorg.conf files
Hi Tim. nvidia-settings hasn't generated an RgbPath line since 177.67. Can you please confirm that the problem does not occur with the latest version? ** Changed in: nvidia-settings (Ubuntu) Status: New = Fix Released -- nvidia-settings generates broken xorg.conf files https://bugs.launchpad.net/bugs/278055 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
The code I added relies on a feature I added to xserver 1.7 to work correctly. It should still be broken in Karmic, since it ships xserver 1.6. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Right, the code was added for xserver 1.7.0, so Lucid should work since it ships a newer point release of the same server branch. You mentioned Karmic, which ships xserver 1.6.4: http://packages.ubuntu.com/karmic-updates/x11/xserver-common I would not expect that to work correctly with Vino+Compiz since it lacks the necessary X server source. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
while the screen updates under this setting, it was noticeably slower than having visual effects set to none (no compiz) This is expected. When no composite manager is running, the X server sends damage events only for the parts of the screen that changed. Because Compiz uses a much more complex API (OpenGL) to update the screen, it instead generates damage events that cover the whole screen. This makes the VNC server have to read back the whole screen instead of only a small part of it. When I tried it, x11vnc was much better than vino about updating the screen efficiently. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Doug, the code to enable damage events for this sort of use case is only available in relatively recent driver releases. The code in the X server that allows it to work was only added in the xserver 1.7 timeframe. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
No, the legacy branches do not have the code to take advantage of the code I added to the X server, and are unlikely to get it because those branches are limited to support for new kernels and X servers, and critical bug fixes only. This is basically a new feature. The latest drivers do have code to take advantage of it, but it's not completely correct as I described in my comment #245. I hope that makes things clearer! -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
I looked into this today and found that the NVIDIA driver does not correctly generate damage events for a given window when the OpenGL rendering is actually happening to a child window. In this case, x11vnc is listening for damage events on the root, but Compiz is rendering to the Composite Overlay Window, which counts as a child window as far as this code is concerned. I'll try to fix the window hierarchy problem for a future release. In the meantime, you can work around the problem by using Compiz's --use-root-window option, or by modifying Compiz to call XCreateDamage(dpy, cow, XDamageReportNonEmpty) to trigger damage events on the root window when it renders to the COW. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org https://bugs.launchpad.net/bugs/353126 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
TiGR, please reinstall the 96.43.17 driver, try to start X again, run nvidia-bug-report.sh, and attach the resulting nvidia-bug-report.log.gz file here. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
This is fixed in a release candidate. Reassigning to Alberto to update the Ubuntu packages. ftp://download.nvidia.com/XFree86/Linux-x86/96.43.17/ ftp://download.nvidia.com/XFree86/Linux-x86_64/96.43.17/ ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: Aaron Plattner (aplattner) = Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: Alberto Milone (albertomilone) = Aaron Plattner (aplattner) ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: Aaron Plattner (aplattner) = Alberto Milone (albertomilone) -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
disco_stew: I don't know when an updated driver will be released. Once a driver is released, I'll reassign this bug to Alberto to handle the Ubuntu nvidia-96 package update. Presumably this bug would be an SRU candidate, if it turns out that's necessary. You ought to be able to work around this problem by disabling Composite or RenderAccel, though I haven't actually tried that. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 516520] Re: pam_unix(gdm:auth): conversation failed
*** This bug is a duplicate of bug 553200 *** https://bugs.launchpad.net/bugs/553200 NoOp, I already mentioned in the other bug that I don't think electhor's original problem is related. Electhor was using a GeForce 8600 GT, which is not supported by the 96.43.* legacy driver, so can't have been affected by bug #553200. The rest of the discussion in this bug that *is* related to #553200 is off-topic. Electhor, when you filed this bug, were you using the NVIDIA 96.43.* legacy driver? If not, please un-duplicate / reopen this bug. -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
It should affect any card using the 96.43.* drivers. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 516520] Re: pam_unix(gdm:auth): conversation failed
NoOp unsubscribed, so the point is mostly moot, but the original report is not the same symptom, it describes a black screen and an X server restart *after* logging in. Bug #553200 is a hang or crash as soon as the password prompt is displayed. In addition, Saša's report confirming the original symptoms is from the intel driver. Unduplicating. ** This bug is no longer a duplicate of bug 553200 Mouse and keyboard stop working after selecting user -- pam_unix(gdm:auth): conversation failed https://bugs.launchpad.net/bugs/516520 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/listinfo/ubuntu-bugs
[Bug 532436] Re: nvidia driver sometime does not load at boot
Please subscribe Daniel Dadap to NVIDIA bugs instead of me. He's our support engineer now. -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 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/listinfo/ubuntu-bugs
[Bug 532436] Re: nvidia driver sometime does not load at boot
I should also mention that there's no indication in the log file that the NVIDIA driver is related. I don't think any of the usual suspects, like crashes (SEGV or BUS), unresolved symbols (ABRT), or divides by zero (FPE), can be blamed here. I would guess that some external program is sending SIGQUIT to the server. -- nvidia driver sometime does not load at boot https://bugs.launchpad.net/bugs/532436 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
Darrin, what fix are you referring to? The fix for this bug has not yet been released. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
This should be fixed in the next legacy driver release. ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: In Progress = Fix Committed -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
NoOp, it looks like that bug got hijacked. This problem sounds unrelated to the problem originally reported in that bug. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
I'll try to take a look at this soon. It's suspicious that it started occurring with a GDM update, but it'll take some digging to figure out what's going wrong. ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: (unassigned) = Aaron Plattner (aplattner) -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
I can't reproduce this problem. I used the default Ubuntu GDM setup, and I also tried installing xubuntu-gdm-theme. I don't think the latter worked correctly, though because I get a boring purple background and a little terminal picture at the top of the login prompt. Hopefully the xubuntu theme isn't supposed to be quite so ugly... I'll need to try with a fresh install, I guess, though I won't have time to do that any time soon. -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: Aaron Plattner (aplattner) = Daniel Dadap (ddadap) -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 553200] Re: Mouse and keyboard stop working after selecting user
I managed to track down the cause of this problem. I'll try to get it fixed soon. It is indeed a bug in the NVIDIA X driver. ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Assignee: Daniel Dadap (ddadap) = Aaron Plattner (aplattner) ** Changed in: nvidia-graphics-drivers-96 (Ubuntu) Status: Triaged = In Progress ** Changed in: gdm (Ubuntu) Status: Confirmed = Invalid -- Mouse and keyboard stop working after selecting user https://bugs.launchpad.net/bugs/553200 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/listinfo/ubuntu-bugs
[Bug 534881] Re: PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it
Thanks Daniel. I'll file a bug against Pidgin. -- PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it https://bugs.launchpad.net/bugs/534881 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/listinfo/ubuntu-bugs
[Bug 534881] Re: PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it
... or figure out how to make this bug apply to the Pidgin package. ** Also affects: pidgin (Ubuntu) Importance: Undecided Status: New -- PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it https://bugs.launchpad.net/bugs/534881 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/listinfo/ubuntu-bugs
[Bug 534881] [NEW] PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it
Public bug reported: Binary package hint: pulseaudio Compared to my music player application, Pidgin is ridiculously loud. Normally, I would adjust its volume in the per-application volume tab, but the slider for it appears only while the sound is actually playing. I have to have a friend constantly send me messages to trigger the sound so I can adjust it. The Pidgin slider should be visible whenever Pidgin is running, not just when Pidgin is actually playing a sound. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- PulseAudio's Pidgin volume control slider keeps disappearing before I can adjust it https://bugs.launchpad.net/bugs/534881 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/listinfo/ubuntu-bugs
[Bug 431239] Re: initctl: output better errors than D-Bus (e.g. for permission denied)
Scott, how did you determine from that message that it was a permission error? -- initctl: output better errors than D-Bus (e.g. for permission denied) https://bugs.launchpad.net/bugs/431239 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/listinfo/ubuntu-bugs
[Bug 432172] Re: nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia
Thanks Mario. I just made an 0.3 release with these changes: http://lists.freedesktop.org/archives/xorg- announce/2009-November/001200.html It now builds the documentation too, so you'll probably want a libvdpau- doc package at some point. -- nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia https://bugs.launchpad.net/bugs/432172 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/listinfo/ubuntu-bugs
[Bug 432172] Re: nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia
Mario, does this layout look okay to you? I'd like to make an 0.3 release tonight. Yet-to-be-released NVIDIA drivers will install: /usr/lib/libvdpau.so - libvdpau.so.1 /usr/lib/libvdpau.so.1 - libvdpau.so.190.NN /usr/lib/libvdpau.so.190.NN /usr/lib/libvdpau_nvidia.so - vdpau/libvdpau_nvidia.so.190.NN /usr/lib/libvdpau_trace.so - vdpau/libvdpau_trace.so.190.NN /usr/lib/vdpau/libvdpau_nvidia.so.1 - libvdpau_nvidia.so.190.NN /usr/lib/vdpau/libvdpau_nvidia.so.190.NN /usr/lib/vdpau/libvdpau_trace.so.1 - libvdpau_trace.so.190.NN /usr/lib/vdpau/libvdpau_trace.so.190.NN git HEAD libvdpau will install: /usr/lib/libvdpau.la /usr/lib/libvdpau.so - libvdpau.so.1.0.0 /usr/lib/libvdpau.so.1 - libvdpau.so.1.0.0 /usr/lib/libvdpau.so.1.0.0 /usr/lib/vdpau/libvdpau_trace.la /usr/lib/vdpau/libvdpau_trace.so - libvdpau_trace.so.1.0.0 /usr/lib/vdpau/libvdpau_trace.so.1 - libvdpau_trace.so.1.0.0 /usr/lib/vdpau/libvdpau_trace.so.1.0.0 The library will look for drivers in /usr/lib/vdpau/libvdpau_driver.so -- nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia https://bugs.launchpad.net/bugs/432172 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/listinfo/ubuntu-bugs
[Bug 432172] Re: nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia
The library will look for drivers in /usr/lib/vdpau/libvdpau_driver.so I'm sorry, that should have read /usr/lib/vdpau/libvdpau_driver.so.1 (i.e. versioned in case we ever change the libvdpau - driver interface) -- nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia https://bugs.launchpad.net/bugs/432172 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/listinfo/ubuntu-bugs
[Bug 432172] Re: nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia
I just pushed a change that should address the concerns. Please let me know if this is sufficient or if additional changes are necessary. http://cgit.freedesktop.org/~aplattner/libvdpau/commit/?id=0537b13e292bc772e984872a3986e41fb51f9258 -- nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia https://bugs.launchpad.net/bugs/432172 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/listinfo/ubuntu-bugs
[Bug 446002] [NEW] The Stupid Tricks Sampler shouldn't be in top's man page
Public bug reported: Binary package hint: procps The STUPID TRICKS Sampler section does not belong in a man page -- maybe as a post on a blog somewhere, but not in technical documentation for a core system utility. Notable gems include, Bouncing Windows and The Big Bird Window. I doubt anyone trying to actually use top cares about the steps necessary to enter the extreme bounce zone. ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- The Stupid Tricks Sampler shouldn't be in top's man page https://bugs.launchpad.net/bugs/446002 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/listinfo/ubuntu-bugs
[Bug 431076] [NEW] The Original size option fails to take the size of the side panel into account
Public bug reported: Binary package hint: vinagre Start Vinagre, then connect to a VNC session. Open the side panel by clicking View - Side Panel, and then click View - Original Size. The window is scaled to a size that would closely fit the image *if the side panel were not enabled*. The problem does not occur if the side panel is disabled: clicking Original Size exactly fits the image. I'm using vinagre-2.26.1-0ubuntu1 from Ubuntu 9.04. ** Affects: vinagre (Ubuntu) Importance: Undecided Status: New -- The Original size option fails to take the size of the side panel into account https://bugs.launchpad.net/bugs/431076 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/listinfo/ubuntu-bugs
[Bug 15495] Re: Archive Manager doesn't mean anything if you don't know what an archive is
If we're looking for synonyms, how about bundle? From dict.org:
bundle
n 1: a collection of things wrapped or boxed together [syn: {package},
{packet}, {parcel}]
2: a package of several things tied together for carrying or
storing [syn: {sheaf}]
[...]
v 1: make into a bundle; he bundled up his few possessions
[syn: {bundle up}, {roll up}]
It has less of the room full of dusty books connotation than archive.
--
Archive Manager doesn't mean anything if you don't know what an archive is
https://bugs.launchpad.net/bugs/15495
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
lewmur, .nvidia-settings-rc is not an executable, it's a configuration file that nvidia-settings uses to save user preferences for the server configuration. Wearing my Ubuntu user hat, I would personally prefer not having it save things like my brightness and contrast settings in root's home directory by default. If the gksudo change is applied and then the bug is later fixed some other way, users will be confused when the settings they had previously saved into ~root/.nvidia-settings-rc are no longer applied because the program is now reading ~/.nvidia- settings-rc instead. Wearing my upstream maintainer hat, I don't really have a say in what Ubuntu does here. If there's a way of changing xorg.conf from a non- root program in a reasonably standard and reasonably distro-agnostic way, I'll be sure to include it upstream. -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 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/listinfo/ubuntu-bugs
[Bug 316802] Re: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
*** This bug is a duplicate of bug 290666 *** https://bugs.launchpad.net/bugs/290666 Emilio, what is your rationale for marking this bug a duplicate of bug 290666? In that bug, liferea is slow to start due to an excessive number of fsyncs. In this bug, the system is completely idle and liferea goes nuts with fdatasync calls that stop when I move the mouse to kill the screensaver. -- Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use https://bugs.launchpad.net/bugs/316802 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/listinfo/ubuntu-bugs
[Bug 352485] Re: X: NVidia 8800 GT not being initialized correctly
Here's the problem: [ 30.912314] vmap allocation failed: use vmalloc=size to increase size. Please see the section in the README about this error. ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: Incomplete = Invalid -- X: NVidia 8800 GT not being initialized correctly https://bugs.launchpad.net/bugs/352485 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/listinfo/ubuntu-bugs
[Bug 352485] Re: X: NVidia 8800 GT not being initialized correctly
It's a kernel parameter. The README entry I was referring to is this one: ftp://download.nvidia.com/XFree86/Linux-x86/185.18.14/README/chapter-09.html#kva_exhaustion It appears that the message changed, but I believe this is the same problem. The RmInitAdaptor failed messages are a direct result of that problem. -- X: NVidia 8800 GT not being initialized correctly https://bugs.launchpad.net/bugs/352485 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/listinfo/ubuntu-bugs
[Bug 353098] Re: Cursor behaves oddly during logon (using Xinerama)
This is not a bug in the graphics driver -- the X server tells the driver which screens' cursors to display, what they should look like, and where to place them. If the cursor is appearing in the wrong place or on the wrong screen, then the bug is almost certainly in the X server itself. -- Cursor behaves oddly during logon (using Xinerama) https://bugs.launchpad.net/bugs/353098 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/listinfo/ubuntu-bugs
[Bug 352485] Re: X: NVidia 8800 GT not being initialized correctly
Whenever you see the message, Failed to initialize the NVIDIA graphics device, you need to check your kernel log to see why the kernel module couldn't be initialized. Your best bet is to reproduce the problem, run nvidia-bug-report.sh, and then attach the resulting log. ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New = Incomplete -- X: NVidia 8800 GT not being initialized correctly https://bugs.launchpad.net/bugs/352485 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/listinfo/ubuntu-bugs
[Bug 374141] Re: resizing window leaves garbage on screen
How large is your cursor? This looks like typical corruption that is caused by a fundamental incompatibility between GLX and the X server's software cursor code. If it's larger than 64x64, please try using a smaller cursor. It doesn't look that big from the screenshot, but it could have a lot of blank space in it. -- resizing window leaves garbage on screen https://bugs.launchpad.net/bugs/374141 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/listinfo/ubuntu-bugs
[Bug 231697] Re: Composite extension not working with dual screens using Xinerama
This is an X server limitation, not a driver limitation. ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: Confirmed = Invalid -- Composite extension not working with dual screens using Xinerama https://bugs.launchpad.net/bugs/231697 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/listinfo/ubuntu-bugs
[Bug 368081] Re: X crashes during browsing internet
Please try 180.51: http://www.nvnews.net/vbulletin/showthread.php?p=1985816 One of the release highlights was a fix for an X server crash visiting certain web pages. -- X crashes during browsing internet https://bugs.launchpad.net/bugs/368081 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/listinfo/ubuntu-bugs
[Bug 325115] Re: nvidia-settings no longer changes screen mode
Fixed in xserver 1.6. ** Changed in: xorg-server Status: New = Fix Released -- nvidia-settings no longer changes screen mode https://bugs.launchpad.net/bugs/325115 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/listinfo/ubuntu-bugs
Re: [Bug 317703] Re: Add hook scripts to be run by nvidia-installer
On Thu, Apr 02, 2009 at 12:51:53PM -0700, Bryce Harrington wrote: c. If your bug still remains, please simply reply to this email indicating so. This is an enhancement request for Ubuntu to use these hooks to allow .run packages and dpkgs to interact correctly. -- Add hook scripts to be run by nvidia-installer https://bugs.launchpad.net/bugs/317703 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/listinfo/ubuntu-bugs
[Bug 335879] Re: nvidia driver 180.35 breaks KDE 4
Please give 180.37 a try. -- nvidia driver 180.35 breaks KDE 4 https://bugs.launchpad.net/bugs/335879 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/listinfo/ubuntu-bugs
[Bug 337654] Re: Error applying Dynamic TwinView in Jaunty
*** This bug is a duplicate of bug 325115 *** https://bugs.launchpad.net/bugs/325115 ** This bug has been marked a duplicate of bug 325115 nvidia-settings no longer changes screen mode -- Error applying Dynamic TwinView in Jaunty https://bugs.launchpad.net/bugs/337654 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/listinfo/ubuntu-bugs
[Bug 325115] Re: nvidia-settings no longer changes screen mode
Fixed upstream: commit 660c2a7d4c6cb52fd0992e9d2008a24805dc8c02 Author: Aaron Plattner aplatt...@nvidia.com Date: Thu Feb 12 18:27:48 2009 -0800 Query the DDX in ProcRRGetScreenInfo. This is the RandR 1.1 version of GetScreenResources and needs to re-query the DDX to see if the mode pool changed. Fixes Launchpad bug #325115. Signed-off-by: Adam Jackson a...@redhat.com :100644 100644 da633b2... 36ef86e... M randr/rrscreen.c -- nvidia-settings no longer changes screen mode https://bugs.launchpad.net/bugs/325115 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/listinfo/ubuntu-bugs
[Bug 326344] Re: compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2
My email update from over an hour ago hasn't shown up yet, so reposting through the web interface: On Sun, Feb 08, 2009 at 06:19:48AM -0800, Albert Damen wrote: Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch. Without this patch compiz works fine again on jaunty / nvidia-glx-180. MAXCLIENTS is defined in resource.h, which is part of the server's ABI. You can't just change this number without also changing the ABI version and recompiling any modules that use it. In particular, this change causes libglx to overrun some memory, corrupting who knows what. While we can probably work around this particular problem, I don't think we want to get into the habit of supporting arbitrary unofficial changes to the server ABI. If you do think the ABI needs to be changed, please discuss it on xorg-de...@lists.freedesktop.org. There's a discussion in progress right now about how to properly increase MAXCLIENTS without breaking other apps that rely on having a lot of resource IDs available: http://lists.freedesktop.org/archives/xorg- devel/2009-February/39.html This patch needs to be reverted. -- compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2 https://bugs.launchpad.net/bugs/326344 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/listinfo/ubuntu-bugs
[Bug 326344] Re: compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2
Oh yeah, and I forgot to correct the text: MAXCLIENTS is actually defined in misc.h, not resource.h, but it's still part of the ABI. -- compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2 https://bugs.launchpad.net/bugs/326344 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/listinfo/ubuntu-bugs
Re: [Bug 326344] Re: compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2
On Sun, Feb 08, 2009 at 06:19:48AM -0800, Albert Damen wrote: Bisecting patches 157 - 160 blames patch 158_raise_maxclients.patch. Without this patch compiz works fine again on jaunty / nvidia-glx-180. MAXCLIENTS is defined in resource.h, which is part of the server's ABI. You can't just change this number without also changing the ABI version and recompiling any modules that use it. In particular, this change causes libglx to overrun some memory, corrupting who knows what. While we can probably work around this particular problem, I don't think we want to get into the habit of supporting arbitrary unofficial changes to the server ABI. If you do think the ABI needs to be changed, please discuss it on xorg-de...@lists.freedesktop.org. There's a discussion in progress right now about how to properly increase MAXCLIENTS without breaking other apps that rely on having a lot of resource IDs available: http://lists.freedesktop.org/archives/xorg- devel/2009-February/39.html This patch needs to be reverted. -- compiz/kwin freezes on login as of xorg-server 1.5.99.902-0ubuntu2 https://bugs.launchpad.net/bugs/326344 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/listinfo/ubuntu-bugs
[Bug 325115] Re: nvidia-settings no longer changes screen mode
Thanks for reporting this. I tracked this down to a regression in the X server caused by commit 56f6fb [randr: Avoid re-querying the configuration on everything but GetScreenResources]. The problem is that the DIX and DDX get out of sync with respect to the mode pool, so the DDX knows about the new configuration but the DIX doesn't. I started a thread about it on the X.org mailing list, so hopefully it'll get resolved before 1.6 comes out. In the meantime, you can work around the problem by hitting the apply button, dismissing the failure dialog, running xrandr in a terminal window, and then hitting the apply button again. http://lists.freedesktop.org/archives/xorg/2009-February/043402.html ** Bug watch added: Email to x...@lists # mailto:x...@lists.freedesktop.org ** Also affects: xorg-server via mailto:x...@lists.freedesktop.org Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu) Status: New = Invalid -- nvidia-settings no longer changes screen mode https://bugs.launchpad.net/bugs/325115 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/listinfo/ubuntu-bugs
[Bug 316802] Re: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
This happened again, so I managed to grab a backtrace and strace. The strace, including all 23 of those fdatasync calls, only spans a couple of seconds. ** Attachment added: Backtrace http://launchpadlibrarian.net/21588621/backtrace.txt -- Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use https://bugs.launchpad.net/bugs/316802 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/listinfo/ubuntu-bugs
[Bug 316802] Re: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
** Attachment added: strace http://launchpadlibrarian.net/21588630/strace.log -- Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use https://bugs.launchpad.net/bugs/316802 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/listinfo/ubuntu-bugs
[Bug 308410] Re: Latest Xorg removes nvidia driver ... conflicting xserver-xorg-video-4
I got word from the X.org folks that ABI 5 is frozen, so the next round of driver releases will no longer require -ignoreABI. I *believe* there were no breakages between the version 180.22 was complied against and the frozen version, but I haven't verified that. I still don't recommend disabling the ABI check if you're not actively developing the X server. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269904] Re: Screen refresh problems with nvidia on intrepid
Please everybody, click the This bug doesn't affect me (change) link at the top of the bug instead of posting a me too comment. The problem here is understood and additional confirmation comments only add clutter to the bug. -- 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 317703] Re: Add hook scripts to be run by nvidia-installer
Dear Bryce Harrington's automated script: This is a wishlist bug, but I can't change the importance because I'm not a project maintainer or a bug supervisor. Changing status back to New. ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: Incomplete = New -- Add hook scripts to be run by nvidia-installer https://bugs.launchpad.net/bugs/317703 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/listinfo/ubuntu-bugs
[Bug 317703] Re: Add hook scripts to be run by nvidia-installer
Attached is a patch against the 180.22 tag from git://people.freedesktop.org/~aplattner/nvidia-installer/ (http://cgit.freedesktop.org/~aplattner/nvidia-installer/) You can test it by extracting the .run file with the -x option, changing to the unpacked directory, replacing the nvidia-installer with the one you built, and then running it as ./nvidia-installer ** Attachment added: nvidia-installer patch http://launchpadlibrarian.net/21273440/0001-Add-hooks-to-run-distribution-scripts-from-usr-lib.patch -- Add hook scripts to be run by nvidia-installer https://bugs.launchpad.net/bugs/317703 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/listinfo/ubuntu-bugs
[Bug 317703] [NEW] Add hook scripts to be run by nvidia-installer
Public bug reported: Sorry this didn't make it into 180.22, Alberto. I finally got around to implementing the hook script code we talked about, and the next round of releases will include it. Here's the relevant new section in the manpage: DISTRIBUTION HOOK SCRIPTS Because the NVIDIA installer may interact badly with distribution packages that contain the NVIDIA driver, nvidia-installer provides a mechanism for the distribution to handle manual installation of the driver. If they exist, nvidia-installer will run the following scripts: · /usr/lib/nvidia/pre-install · /usr/lib/nvidia/pre-uninstall · /usr/lib/nvidia/post-uninstall · /usr/lib/nvidia/post-install · /usr/lib/nvidia/failed-install Note that if installation of a new driver requires uninstallation of a previously installed driver, the pre- and post-uninstall scripts will be called after the pre-install script. If the install fails, the installer will exe‐ cute /usr/lib/nvidia/failed-install instead of /usr/lib/nvidia/post-install. These scripts should not require user interaction. Use the --no-distro-scripts option to disable execution of these scripts. I don't know if nvidia-graphics-drivers-* is really the right place for these scripts. It might be necessary to add a new package, depending on what you want them to do. ** Affects: nvidia-graphics-drivers-180 (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- Add hook scripts to be run by nvidia-installer https://bugs.launchpad.net/bugs/317703 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/listinfo/ubuntu-bugs
[Bug 316802] [NEW] Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
Public bug reported: Binary package hint: liferea On a number of different occasions, I've woken up or arrived home to find my hard drive clicking very rapidly. Moving the mouse to deactivate the screensaver makes it stop. Today, I logged in remotely and iotop revealed the culprit to be liferea-bin: Total DISK READ: 0 B/s | Total DISK WRITE: 56.82 K/s PID USER DISK READ DISK WRITE SWAPINIOCOMMAND 27855 aaron 0 B/s 64.39 K/s 0.00 % 0.00 % liferea-bin Unfortunately, I accidentally bumped the mouse before I could attach to it with strace. I've been leaving Liferea running with the feed window open. No other processes were causing disk I/O according to iotop. I'm using liferea 1.4.18-0ubuntu2 in Ubuntu 8.10 running Gnome. ** Affects: liferea (Ubuntu) Importance: Undecided Status: New -- Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use https://bugs.launchpad.net/bugs/316802 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/listinfo/ubuntu-bugs
[Bug 316802] Re: Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use
** Description changed: Binary package hint: liferea On a number of different occasions, I've woken up or arrived home to find my hard drive clicking very rapidly. Moving the mouse to deactivate the screensaver makes it stop. Today, I logged in remotely and iotop revealed the culprit to be liferea-bin: - Total DISK READ: 0 B/s | Total DISK WRITE: 56.82 K/s + Total DISK READ: 0 B/s | Total DISK WRITE: 64.39 K/s PID USER DISK READ DISK WRITE SWAPINIOCOMMAND 27855 aaron 0 B/s 64.39 K/s 0.00 % 0.00 % liferea-bin Unfortunately, I accidentally bumped the mouse before I could attach to it with strace. I've been leaving Liferea running with the feed window open. No other processes were causing disk I/O according to iotop. I'm using liferea 1.4.18-0ubuntu2 in Ubuntu 8.10 running Gnome. -- Liferea tries to kill my hard drive with constant seeking after long idle periods / screen saver use https://bugs.launchpad.net/bugs/316802 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/listinfo/ubuntu-bugs
[Bug 200868] Re: nvidia-settings doesn't have permissions to write xorg.conf
Somebody from Ubuntu needs to decide whether the setuid PolicyKit helper is acceptable, or if something more complicated involving a daemon that connects to dbus needs to be written. If running a daemon is required, then we probably won't be able to support it in the upstream code. Assigning to Alberto to reassign to whoever makes those decisions. Feel free to reassign back to me if something different needs to be implemented. ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- nvidia-settings doesn't have permissions to write xorg.conf https://bugs.launchpad.net/bugs/200868 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/listinfo/ubuntu-bugs
