Description of problem: After yum updating to the new beryl yesterday, it now shows the splash screen when I load beryl, and then goes to a white screen! I am using nvidia driver and 64 bit fedora. It seems quite a few people are having this problem. See the fedoraforum.org thread at http://forums.fedoraforum.org/showthread.php?p=735634#post735634 Version-Release number of selected component (if applicable): 1.99.2-2 How reproducible: yum update beryl from earlier version restart beryl. I have tried deleting the .beryl and .beryl-managerrc directory, but it did not fix problem. Steps to Reproduce: 1. 2. 3. Actual results: Splash screen shows then goest to solid white screen. Expected results: the usually awesome berylness. Additional info:
*** Bug 226798 has been marked as a duplicate of this bug. ***
I use a nvidia graphic adapber too. After I have manualy upgrade the graphic driver from 1.0-9742 (livna) to 1.0-9746 the reported problem doesn't occured anymore on my computer.
Supposedly, this has been fixed upstream. I'm not seeing the issue here, so I can't verify, nor do I have the time or desire to peck through changelogs to find the specific fix, so unless someone else wants to do so, the fix probably won't show up until there are new bery tarballs on releases.beryl-project.org... :\
Beryl 0.20 RC1 has just been released, hopefully we'll see it in extras soon :)
I've encountered the same issues and I've installed the svn version of beryl as suggested at http://forums.fedoraforum.org/showthread.php?p=735634#post735634 This has resolved my issues with the white screen so it seems to be fixed upstream
Humorous that someone in that forum is questioning a beryl "beta" being packaged... Technically, there hasn't been anything *but* a beta (or less) packaged so far, and 0.2.0 is slated to be the first "stable" release. I'm still quite dubious that a "stable" beryl release is possible... :) I'll try to work on 0.1.9999.1 (aka 0.20 rc1, love the numbering scheme) tomorrow.
0.1.9999.1 bits are almost done making their way through the build system
Thanks a lot Jarod - well if just packaging a new snapshop is the solution - easy ... As I don't know what's the difference between these packages I don't know what's the reason for the issue, but it actually works ;) Thanks for packaging a new "official" version. Cheers, Jo
Yes, perhaps that is a mesa problem, which I don't understand. I was iritated, becouse my system show a different behavour after I have installed the nvidia driver von www.nvidia.com instead of the livna rpms.
I have just yum updated beryl to this new version and I'm still getting the white screen. I'm using nvidia drivers from livna. [maners@athlon64 ~]$ rpm -qa | grep beryl beryl-plugins-0.1.9999.1-1.fc6 beryl-settings-simple-0.1.9999.1-2.fc6 beryl-manager-0.1.9999.1-1.fc6 beryl-gnome-0.1.9999.1-2.fc6 beryl-0.1.9999.1-2.fc6 beryl-core-0.1.9999.1-2.fc6 beryl-settings-0.1.9999.1-2.fc6 beryl-kde-0.1.9999.1-2.fc6 [maners@athlon64 ~]$ rpm -qa | grep nvidia xorg-x11-drv-nvidia-1.0.9746-7.lvn6 xorg-x11-drv-nvidia-libs-32bit-1.0.9746-7.lvn6 kmod-nvidia-xen-1.0.9746-1.2.6.19_1.2895.fc6 kmod-nvidia-1.0.9746-1.2.6.19_1.2895.fc6 [maners@athlon64 ~]$ rpm -qa | grep mesa mesa-libGL-6.5.1-9.fc6 mesa-libGLU-6.5.1-9.fc6 mesa-libGL-devel-6.5.1-9.fc6 mesa-libGLU-devel-6.5.1-9.fc6 mesa-libGLU-6.5.1-9.fc6
Update after starting beryl with --use-copy it works ok but I get low performance: http://forum.beryl-project.org/viewtopic.php?f=36&t=2077 Compiz is working fine.
the 0.1.9999 files do not fix the problem for me either. I still have the same white screen issue.
Argh. I've got a box I can reproduce this on now. Can work around it by hitting up the beryl-manager menu -> advanced beryl options -> rendering path and selecting copy instead of automatic. Not sure if the auto-detection broke or if texture-from-pixmap support broke though... I'll poke around upstream a little.
The beryl folks insist this is nVidia's problem. http://bugs.beryl-project.org/ticket/848 http://bugs.beryl-project.org/ticket/875 So for now, use copy (or an XGL X server) w/the nvidia driver, I guess... Re-closing CANTFIX, since the only place I can reproduce it is on a box using the proprietary nvidia driver and upstream beryl says the bug isn't theirs... :\
Okay, not nVidia's problem, its a build issue. See ticket bug 229778. This'll be fixed in the next build.
Resolved for me with the newest beryl-0.2.0-1 Thanks, Jo