FS#6572 - Beryl error with update to 4390-1

Attached to Project: Arch Linux
Opened by Shira K (Shirakawasuna) - Sunday, 11 March 2007, 05:36 GMT
Task Type Bug Report
Category Packages: Unstable
Status Closed
Assigned To No-one
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Recently installed arch linux, installed beryl-svn on the 8th of March, everything worked fine. With the recent update, the Beryl WM fails to load, giving this message:

**************************************************************
* Beryl system compatibility check *
**************************************************************

Detected xserver : AIGLX

Checking Display :0 ...

Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed

Checking Screen 0 ...

libGL warning: 3D driver claims to not support visual 0x5b
Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : passed
Checking maximum texture size : passed (2048x2048)

libGL warning: 3D driver claims to not support visual 0x5b
beryl: dbus_bus_get error: Failed to execute dbus-launch to autolaunch D-Bus session
beryl: Plugin 'dbus':initDisplay failed
beryl: Couldn't activate plugin 'dbus'
Couldn't initialize dbus. This should not happen!

** (beryl-manager:4472): WARNING **: Beryl caught deadly signal 11

This is on a dell laptop with the intel 915gm card, everything including AIGLX was working fine before the update, the dbus and hal services are started and running at the time I get this error.

This looks like it may be a repeat, but the other bugs reports had little information and had german messages.
This task depends upon

Closed by  Jan de Groot (JGC)
Sunday, 11 March 2007, 10:04 GMT
Reason for closing:  Duplicate
Comment by Shira K (Shirakawasuna) - Sunday, 11 March 2007, 05:49 GMT
Well I can't figure out how to edit this thing, but I thought the dbus message was important - it's not, and this is just a repeat of that german bug report I mentioned. (Beryl caught deadly signal 11)

Loading...