[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
FreeNX is not a solution. It is not in the repositories and is not a default installation item. It also will not connect me to an existing session. Still awaiting a fix to this. Why has there been no research into why this broke between 8.10 and 9.04? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver 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
Can a developer explain why this all of a sudden started in Jaunty and was not a problem in Intrepid? The upstream bug report this is linked against is from mid to late 2007. I assume Jaunty didn't "Upgrade" to an Xorg release from 2007. This problem seems to be affecting a lot of people and is a regression, and the lack of activity suggests that it's not going to be fixed in Jaunty... it'd be nice if we heard something about this, as I'm willing to downgrade to Intrepid over this bug. If this truly is a problem with the new Xorg, why are we tagging on to the upstream bug report from 2007 and not creating a new bug report for the new version? -- Compiz / vnc screen refresh with nvidia-restricted driver 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 226334] Re: Insmod snd_intel8x0m doesn't complete- sl-modem-daemon startup hangs
I actually upgraded this laptop to Intrepid Alpha 5 last week and the 2.6.27 kernel, which resolved all of my problems. I'm not in a position to put Hardy back on the laptop, but 2.6.27 (or some other package in Intrepid) resolved my problem. -- Insmod snd_intel8x0m doesn't complete- sl-modem-daemon startup hangs https://bugs.launchpad.net/bugs/226334 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 226334] [NEW] No Sound Hard - insmod snd_intel8x0m doesn't complete
Public bug reported: Binary package hint: linux-image-2.6.24-17-generic Laptop: IBM Thinkpad R40 Sound worked great in Gutsy. Upgraded to Hardy, sound doesn't work, and sl-model-daemon will not start up- it hangs on "/sbin/modprobe snd_intel8x0m," which is presumably the problem. Troubleshooting steps: * Manually attempting to load the module results in failure as well. * Booting the Gutsy kernel (linux-image-2.6.22-14-generic) results in fully functioning sound. * Booting off of the i386 Hardy livecd results in no sound Did a search around didn't see anyone else report this problem. Dmesg and lspci are forthcoming... ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- No Sound Hard - insmod snd_intel8x0m doesn't complete https://bugs.launchpad.net/bugs/226334 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 226334] Re: No Sound Hard - insmod snd_intel8x0m doesn't complete
Attached dmesg ** Attachment added: "dmesg.out" http://launchpadlibrarian.net/14182642/dmesg.out -- No Sound Hard - insmod snd_intel8x0m doesn't complete https://bugs.launchpad.net/bugs/226334 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 226334] Re: No Sound Hard - insmod snd_intel8x0m doesn't complete
Attached lspci -vvnn ** Attachment added: "lspci.out" http://launchpadlibrarian.net/14182646/lspci.out -- No Sound Hard - insmod snd_intel8x0m doesn't complete https://bugs.launchpad.net/bugs/226334 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 226334] Re: No Sound Hard - insmod snd_intel8x0m doesn't complete
Sound is now working, now it's just the insmod that doesn't complete, which is blacklisted but called by the sl-modem-daemon ** Changed in: sl-modem (Ubuntu) Sourcepackagename: linux => sl-modem ** Summary changed: - No Sound Hard - insmod snd_intel8x0m doesn't complete + Insmod snd_intel8x0m doesn't complete- sl-modem-daemon startup hangs ** Description changed: Binary package hint: linux-image-2.6.24-17-generic Laptop: IBM Thinkpad R40 - Sound worked great in Gutsy. Upgraded to Hardy, sound doesn't work, and - sl-model-daemon will not start up- it hangs on "/sbin/modprobe - snd_intel8x0m," which is presumably the problem. + Upgraded to Hardy, sl-model-daemon will not start up- it hangs on + "/sbin/modprobe snd_intel8x0m," which is presumably the problem. Causes + entire boot process to hang. Troubleshooting steps: * Manually attempting to load the module results in failure as well. - * Booting the Gutsy kernel (linux-image-2.6.22-14-generic) results in fully functioning sound. - * Booting off of the i386 Hardy livecd results in no sound + * Booting the Gutsy kernel (linux-image-2.6.22-14-generic) works fine. - Did a search around didn't see anyone else report this problem. Dmesg - and lspci are forthcoming... + + Did a search around didn't see anyone else report this problem. Dmesg and lspci are forthcoming... -- Insmod snd_intel8x0m doesn't complete- sl-modem-daemon startup hangs https://bugs.launchpad.net/bugs/226334 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 prior to release 7.5
Comment #141 confirmed this is a bug with Intel drivers. So this is not limited to binary blobs. And the reason there are so many comments on this bug is because developers have ignored this bug and instead left the community to fend for itself and come up with half baked (if well intentioned) fixes which do not address the underlying regression from 8.10. Please do not mark this bug as fixed until someone confirms it is fixed. Just because an updated version of xorg is in Lucid doesn't mean this bug is fixed. in fact, there are several reports of the contrary. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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 prior to release 7.5
The reports that it's working on Nouveau make it an invalid test case, because the Ubuntu Nouveau drivers do not include Gallium which is required to make Compiz work. Remote Desktop works fine with Compiz disabled. The issue here is only with Remote Desktop + Compiz. But to make you feel better, I will download the latest beta and test it on my work laptop which has Intel video tonight. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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 prior to release 7.5
My testing results: Intel with Compiz Enabled: Works Nvidia Blob with Compiz: Still Broken My wife is using the TV so I cannot test my HTPC with fglrx yet to see the status there. Regardless, nobody has every investigated or stated why this worked for all drivers, open or not, in 8.10. At any rate, it does appear that at least the Intel driver works in 10.04. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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 prior to release 7.5
This was not brought up at nvnews because it was not originally a Binary Blob issue. Whatever was changed in xorg to fix this apparently requires a driver fix too. At any rate, I tested my ATI box and the results were as one might predict: Radeon driver + Compiz: Works FGLRX driver + Compix: Does not work I guess at this point I'll unsubscribe from this thread as any hope at getting this fixed has now been lost, since it's going to be categorized into that blackhole of "binary driver" issues. I hope whatever changes xorg made to fix the original bug are somehow directly made known to all driver vendors. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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 483170] Re: insufficient access permission for /var/run/courier/authdaemon
I too can confirm this on a 9.04 to 9.10 amd64 upgrade. Another work around I found via Google was doing a chown -R daemon:daemon on the /var/run/courier directory, but those permissions are also lost after a reboot and are changed to root on the next boot. -- insufficient access permission for /var/run/courier/authdaemon https://bugs.launchpad.net/bugs/483170 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 prior to release 7.5
This has nothing to do with closed source drivers. This bug only occurs with Compiz enables, which the Nouveau drivers do not support, so they are an invalid test case. As stated before in this bug numerous times, this worked fine in 8.10 with all closed source drivers that supported Compiz. The upgrade to 9.04 broke this. It affects any environment that supports Compiz and any driver that supports Compiz. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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 prior to release 7.5
Using Nouveau does _NOT_ fix this bug, Nouveau does not support Compiz. Can a developer PLEASE chime in on this? This worked in 8.10 and has been broken since. We were told it would be fixed with Lucid and, a month away from Lucid's release, it's still not fixed. Could someone please at least say "No, this will not be fixed" instead of forcing people to chime in with half baked solutions and leave us guessing? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 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
This bug was not fixed in either Jaunty or Karmic. From the upstream reports it hasn't been fixed upstream either, so it will probably not be fixed in Lucid either. The only true fix/workaround is to reinstall Intrepid which is the last version which had a working VNC + Active Compiz integration. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver 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
