Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6080 - Newest Beryl broken

Attached to Project: Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Tuesday, 26 December 2006, 06:07 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 10 January 2007, 00:15 GMT
Task Type Bug Report
Category Packages: Unstable
Status Closed
Assigned To Jan de Groot (JGC)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The latest Beryl svn does not work well. Windows have white borders around them. Menus, windows etc, are all white. And after a while, the desktop becomes white too. It seems that somehow Beryl has a bug and does not display textures or something.

HOWEVER, this new Beryl build is much faster! I don't know if it's because it can't deal with the textures anymore because of this new bug, or because a new patch really made it faster (and as a consequence created the bug).

I am using a Radeon 9000 Mobility (r250), 64 MB AGP on a laptop.
This task depends upon

Closed by  Jan de Groot (JGC)
Wednesday, 10 January 2007, 01:51 GMT
Reason for closing:  Fixed
Comment by Roman Kyrylych (Romashka) - Tuesday, 26 December 2006, 09:45 GMT
The latest beryl == which build number?
The latest from Unstable worked fine for me. Now I use even more later experimental version, made by brain0, which didn't went to Unstable because of unstability issues and bugs (though works fine for me too :p).
Comment by Eugenia Loli-Queru (Eugenia) - Tuesday, 26 December 2006, 10:17 GMT
As I said, I run the latest SVN as offered by the Unstable (this bug report is filed against the Unstable category too). And yes, this new build is broken for my graphics card. It creates white rectangular borders around windows/menus/panels.
Comment by Denis Martinez (denis) - Tuesday, 26 December 2006, 12:36 GMT
Today I upgraded my mesa to 6.5.2 and the problem started to appear. Beryl worked fine with the previous version of mesa. Downgrading mesa and libgl-dri to 6.5.1 fixed the problem. I think this build of beryl is OK.
Comment by Eugenia Loli-Queru (Eugenia) - Tuesday, 26 December 2006, 20:18 GMT
Ok, could someone assign this bug report to the dri/mesa maintainer too then? Thanks.
Hopefully, when the textures come back when this bug is fixed, the speed that I have gained with the latest build is still there. Otherwise, there is a real bottleneck to be found and optimized... ;)
Comment by Roman Kyrylych (Romashka) - Tuesday, 26 December 2006, 20:20 GMT
The problem seems to be with the latest libgl-dri. Only nvidia card users seems to be unafected.
Comment by Jan de Groot (JGC) - Tuesday, 26 December 2006, 23:20 GMT
I rebuilt beryl with the newest mesa and libgl-dri installed. I also disabled beryl-xgl in this build since that pulls in a static build of mesa I don't trust. Could someone test http://www.archlinux.org/~jgc/beryl-core-svn-1774-2.pkg.tar.gz to see if things are still working?

Another thing that might help: try using beryl-xgl instead of beryl as binary name, beryl-xgl is static linked against an internal snapshot of mesa in the package which is in the repositories at this moment.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 27 December 2006, 00:11 GMT
Running beryl-xgl instead of just beryl (from the current Unstable repository) WORKS with my AIXGL setup, yes. This works well.

After I installed your package though, it removed beryl-xgl, and then new beryl executable has the SAME bug as I described above. In other words, your new test package did not fix the problem. The problem seems to be a real incompatibility between the GL libs and Beryl rather than just a recompilation/relinking problem.

BTW, if I re-install the Unstable beryl-core package, how do I make my Gnome load beryl-xgl rather than beryl by default? I had added "beryl" and "beryl-manager" in my Gnome's startup programs via gnome-session-properties, but now that I revisited that panel, only beryl-manager is there! Weird stuff...
Comment by Roman Kyrylych (Romashka) - Wednesday, 27 December 2006, 00:17 GMT
Have you tried newer beryl builds?
I use 1918 now, except for heliodor, which was not updated by brain0 at that time. Due to more experimental nature these packages haven't hit Unstable, but they work for me.
Maybe build 1918 has those compatability issues fixed, just a guess. :-/
Comment by Roman Kyrylych (Romashka) - Wednesday, 27 December 2006, 00:19 GMT
btw, only beryl-manager should be added to gnome session autostart. It will run beryl automatically.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 27 December 2006, 00:25 GMT
>I use 1918 now

I prefer to use stuff that are provided by Arch Linux only -- even if they are in their unstable trees. I prefer to minimize future problems and file conflicts.

>only beryl-manager should be added to gnome session autostart.

How do I tell it to run beryl-xgl instead then?
Comment by Roman Kyrylych (Romashka) - Wednesday, 27 December 2006, 00:34 GMT
> I prefer to use stuff that are provided by Arch Linux only
brain0 is Arch dev and beryl package manager, so I assume those packages are provided by Arch.
He just gave me those packages for testing and I liked new features, so I keep those packages until new version will be out.

> How do I tell it to run beryl-xgl instead then?
symlink?
Comment by Jan de Groot (JGC) - Wednesday, 27 December 2006, 00:35 GMT
I'm fresh to beryl also, I used the wiki to get something working on my system. The most simple way to force beryl-xgl is to use "cp /usr/bin/beryl-xgl /usr/bin/beryl" for now, that will make sure you will have beryl-xgl running all the time until we fix our packages (either mesa+xorg-server, or a static build of beryl).

I think https://bugs.freedesktop.org/show_bug.cgi?id=9456 describes the problem best, I filed it at freedesktop.org a few minutes ago.

I suspect something is going wrong in the initialization of textures here. A temporary "fix" would be to compile beryl with a static mesa snapshot which doesn't have this bug, as it only affects the texture_from_pixmap things at this moment, which is hardly used by other programs.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 27 December 2006, 00:41 GMT
Thanks Jan! You rock!
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 27 December 2006, 01:20 GMT
BTW, a new major version was released today: http://www.digg.com/linux_unix/Beryl_0_1_4_Released
Comment by Thomas Bächler (brain0) - Wednesday, 27 December 2006, 11:38 GMT
Due to absence of a fast compiling and testing machine, there won't be any new beryl packages until January 8th or maybe a few days later. Due to absence of an AIGLX machine, I will have to rely on you guys for testing it, I can only provide testing for nvidia, which apparently always works.

Using the statically built beryl-xgl binary is sort of a workaround, we should always be able to use the system's libGL with AIGLX, that should be investigated once I am back.

As for 0.1.4: I won't put any beryl releases into extra until beryl 0.2 (the first "stable") will be released in February. The 0.1.X are only development "releases", which aren't much better than the svn versions.
Comment by Scott H (stonecrest) - Wednesday, 27 December 2006, 15:54 GMT
For what it's worth, I'll be happy to provide any testing with AIGLX on an i810 card. For now, I have downgraded the libgl-dri package and things are working well here.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 27 December 2006, 22:00 GMT
Nobody said putting it on Extra, unstable is fine. I will compile the 0.1.4 by myself until you have a new version out. Hopefully you don't use anything else other than --prefix=/usr in the configure script...
Comment by Scott H (stonecrest) - Wednesday, 27 December 2006, 23:09 GMT
Erm, why not use abs && versionpkg to update beryl? Granted svn will be a little different than the 0.1.4 release at this point, but probably not much.

Or, at the very least, you can look at the PKGBUILD and see the compile options..
Comment by Eugenia Loli-Queru (Eugenia) - Thursday, 28 December 2006, 08:14 GMT
I just tried the 0.1.4 release and it also has the bug.
Comment by Jason Carr (jason2) - Wednesday, 03 January 2007, 06:29 GMT
I'm also having this problem. I'd be happy to test with my:

01:00.0 VGA compatible controller: ATI Technologies Inc M24 1T [FireGL M24 GL] (rev 80)

:)
Comment by héctor (hacosta) - Tuesday, 09 January 2007, 23:53 GMT
this should definitely be confirmed
Comment by Jan de Groot (JGC) - Wednesday, 10 January 2007, 01:45 GMT
OK, it appeared to be a GLX protocol mismatch between mesa and Xorg. Xorg-server contains some pregenerated files which are generated by the mesa 6.5 sources. With a bit of bad luck, 6.5.1 shouldn't work either.

I regenerated these files from mesa for xorg-server-1.1.1-6, which will appear in the repository soon (also fixes a security issue).

Loading...