[Ubuntu-x-swat] [Bug 192508] Re: mouse keys turns on randomly

2011-01-08 Thread Mossroy
I'm facing the same issue with the following configuration: - ubuntu 10.04.1 32bit, with remote desktop enabled (vino version 2.28.2-0ubuntu2) - ubuntu 10.04.1 64bit, connecting to the above computer with vinagre (version 2.30.2-0ubuntu1) The mouse keys activate on the first computer (the VNC ser

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-22 Thread Mossroy
The problem is still the same with the RC of lucid. - on first boot on the liveCD, I had the ubuntu logo, and then the grey lines symptom (see the photo of comment #4) - on second boot on the liveCD, I added the "nouveau.noaccel=1" in the startup parameters, which allowed me to boot succesfully

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-19 Thread Mossroy
At least, if it's not possible or too complicated/risky before the final release, the video card should be blacklisted for acceleration, as it has been done for other cards : see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/544088 It seems to be called the "noaccel quirk". I think it's

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-17 Thread Mossroy
Christopher was right : I opened the upstream bug too quickly. I saw the same behavior on Fedora 13 beta, and thought these 2 distributions used very recent versions of nouveau. I was wrong : the problem seems to be already solved upstream. As suggested by Christopher, I enabled the xorg-edgers P

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
** Also affects: fedora Importance: Undecided Status: New ** Also affects: nouveau via http://bugs.freedesktop.org/show_bug.cgi?id=27706 Importance: Unknown Status: Unknown -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referenc

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
I opened a bug on the nouveau bugtracker : https://bugs.freedesktop.org/show_bug.cgi?id=27706 ** Bug watch added: freedesktop.org Bugzilla #27706 http://bugs.freedesktop.org/show_bug.cgi?id=27706 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error refer

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
** Description changed: Binary package hint: xserver-xorg-video-nouveau - I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200 SE (NV44A rev A1) : the screen stays blank after booting. + I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
** Attachment added: "Dmesg when booting on lucid beta 2 with nouveau.noaccel=1" http://launchpadlibrarian.net/44427545/dmesg-beta2-noaccel -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmi

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
Adding "nouveau.noaccel=1" in the grub parameters of the fedora 13 beta livecd makes it work too -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You re

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
Adding "nouveau.noaccel=1" in the grub parameters is sufficient to work around the problem -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
When the screen stays blank, ubuntu is not completely frozen : if I push the power button (without holding it), the hard disk flashes a few seconds and then it powers down : looks like a proper shutdown I found a temporary workaround by adding startup parameters in grub : if I add "nouveau.modeset

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
Rarely, the screen doesn't stay blank : I can see the ubuntu logo, and then it shows a weird screen of grey lines (see attached photo) It happened only twice, and without changing anything to the configuration, boot options or BIOS Also, the first time I started this computer this morning, it re

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
Maybe this is related : before these error lines appear the following lines in dmesg : agpgart-nvidia :00:00.0: AGP 3.0 bridge agpgart: modprobe tried to set rate=x12. Setting to AGP3 x8 mode. agpgart-nvidia :00:00.0: putting AGP V3 device into 8x mode nouveau :03:00.0: putting AGP

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
** Attachment added: "Dmesg when booting on lucid alpha 3" http://launchpadlibrarian.net/44417372/dmesg-alpha3 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic https://bugs.launchpad.net/

[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
** Attachment added: "Dmesg when booting on lucid beta 2 (with all updates)" http://launchpadlibrarian.net/44417313/dmesg-beta2 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic https://bu

[Ubuntu-x-swat] [Bug 564617] [NEW] Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. "Error referencing VRAM ctxdma: -12". Worked in alpha 3 and in karmic

2010-04-16 Thread Mossroy
Public bug reported: Binary package hint: xserver-xorg-video-nouveau I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200 SE (NV44A rev A1) : the screen stays blank after booting. It works properly with a lucid alpha 3 liveCD, and with a karmic liveCD. I managed to ins

[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5

2010-02-28 Thread Mossroy
It works great on my ubuntu 10.04 alpha 3 (with Intel drivers), accessed from an ubuntu 9.04 VNC client, or a ubuntu 10.04 alpha 3 client. With compiz fully activated, the screen refreshes correctly, and I can see the desktop effects through VNC -- Compiz / vnc screen refresh with nvidia-restri

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-02-10 Thread Mossroy
I change the status to invalid, as it seems to come from the overclocking of my CPU ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New => Invalid -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received thi

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-02-10 Thread Mossroy
It does not seem to be related to the screen resolution (tried both 1024x768 and 1600x1200), or to the VGA/DVI port (tried both). So I assume it was related to the overclocking -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You r

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-02-10 Thread Mossroy
I now think that the freeze issue might come from a hardware problem : I made a test that worked well : - I removed the overclocking of my CPU (so that the CPU uses its normal speed). The overclocking was stable for years, but one never knows. My graphic card is not overclocked - I reduced the sc

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-02-02 Thread Mossroy
At least I solved the problem of blank screen after hibernation : I found in the forums that I needed to put "NvAGP" "1" in my xorg.conf. See https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/34043 Now I can resume correctly from hibernation. But I still have freezes wh

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-01-31 Thread Mossroy
I just made a test on a ubuntu 9.04 liveCD : installed nvidia drivers version 180.44, and version 10.0.22.87 of flash plugin (through http://pubmirrors.reflected.net/debian-multimedia/pool/main/f/flash- player/flashplayer-mozilla_10.0.22.87-0.0_i386.deb) The system froze after a few minutes watchi

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-01-31 Thread Mossroy
This time, I reproduced the freeze on a ubuntu 9.04 liveCD. I installed version 180.44 of the nvidia proprietary drivers, and version 10.0.42.34 of adobe proprietary flash plugin. The computer froze again while displaying the "Home" movie. One interesting thing : I never experienced such freezes

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-01-16 Thread Mossroy
Today, I tried to watch the same youtube video in a virtualized environment. I made this test with Virtualbox 3.1.2 (non-OSE version), on two different virtual machines : - one under Ubuntu 10.04 alpha 2, on which I only installed the proprietary flash plugin (version 10.0.42.34). I did not inst

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2010-01-07 Thread Mossroy
Same freezes after the kernel upgrade to 2.6.31-17.54 -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ub

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-12-31 Thread Mossroy
I reproduced the same problem on a ubuntu 9.10 liveCD : After booting on the liveCD, I installed version 185 of the nvidia proprietary drivers, as proposed a few seconds after the boot. Then, I installed the ubuntu-restricted-extras package (in order to have the proprietary flash plugin). I launc

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-12-12 Thread Mossroy
The flashplugin-nonfree update of yesterday (to version 10.0.42.34ubuntu0.9.10.1) does not solve the problem of freezes with flash videos -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because yo

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-12-01 Thread Mossroy
The xorg updates of today did not solve the problem of wake up after an hibernation : the screen is blank on wake-up -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubu

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-29 Thread Mossroy
Watching the same youtube video from Totem works without freezing. Same thing for another fullscreen streaming video with VLC : no freeze. So I suspect something related to Adobe Flash and/or nvidia drivers -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.la

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-29 Thread Mossroy
I was hoping that the recent kernel upgrade (to 2.6.31-15) could help with this issue. It does not : still the same freezes with flash videos. I can reproduce that easily : - activate nvidia proprietary drivers - open a flash video, for example http://www.youtube.com/watch?v=jqxENMKaeCU and watch

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-23 Thread Mossroy
Here is what a grep gives me in /var/log for the "NVRM" string : /var/log/dmesg:[ 16.933681] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/dmesg.0:[ 13.398677] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-22 Thread Mossroy
I forgot to mention that everything was fine before upgrading to karmic (at least for flash videos, I did not use the hibernate feature at that time). The flash video does not necessarily have to be in fullscreen mode. And it works for a few minutes before freezing the system. -- Freezes with n

[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-22 Thread Mossroy
The version of adobe-flashplugin I use is 10.0.32.18-1karmic2, within firefox 3.5.5. The freezes make the computer completely unresponsive : the mouse does not move, ctrl-alt-F1 does nothing. The only thing I can do is a manual power-off -- Freezes with nvidia-glx-185 or -190 after upgrade from

[Ubuntu-x-swat] [Bug 486837] [NEW] Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic

2009-11-22 Thread Mossroy
Public bug reported: I did a standard dist-upgrade from jaunty to karmic. I have a nvidia graphic card and was using the standard proprietary drivers (proposed by jockey-gtk), and with desktop effects activated. Since the upgrade, I experience freezes that seem to be related to this proprietary