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:
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)
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
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
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
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.
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
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
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
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
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-
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
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.
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
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
15 matches
Mail list logo
