Beryl deadly signal issue

Shirakawasuna · 2007-03-11 03:11:04

I just updated Beryl to the latest release (4390-1) and suddenly I'm getting an issue with dbus. It's possible that this'll be cleared up in the next revision, but I just wondered if anyone knows what's going on. Here's the console output from beryl-manager when I try to select it as the window manager:

**************************************************************
* 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:4763): WARNING **: Beryl caught deadly signal 11

I have dbus in the DAEMONS section of my rc.conf and dbus-launch and dbus-daemon are both running, yet it always falls back to kwin.

Thanks!

Nick

Last edited by Shirakawasuna (2007-03-11 21:59:12)

Shirakawasuna · 2007-03-11 05:50:54

Looks like there's bug reports for this - the dbus message isn't important, it's the "Beryl caught deadly signal 11".

Just running beryl straight gives a segfault

Last edited by Shirakawasuna (2007-03-11 06:00:45)

EPOWER · 2007-03-11 07:10:36

I have the same problem. (Beryl caught deadly signal 11).
Just updated Beryl to the latest release 4390-1.
I dont have the dbus error. I use the nvidia beta drivers (geforce 6200AGP).

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

Detected xserver                                : NVIDIA

Checking Display :0.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 ...

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 (4096x4096)

Initiating splash

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

EPOWER · 2007-03-11 08:13:19

I found this in the beryl-forum:

Strange, if i disabled the "Decoration" plugin with beryl-settings (when beryl is not running)
I can launch beryl... (but there's no decoration)
If i renable it with beryl-settings, (when beryl is running), it works!

Its a quick fix but it works.

brain0 · 2007-03-11 17:04:43

Shirakawasuna wrote:

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:4763): WARNING **: Beryl caught deadly signal 11
I have dbus in the DAEMONS section of my rc.conf and dbus-launch and dbus-daemon are both running, yet it always falls back to kwin.

1) It is correct that your crash is unrelated to the dbus problem. I had some reports about the segfault, but no solution yet.
2) About the dbus problem. Having dbus in rc.conf is not enough, as that only enabled the dbus SYSTEM bus. In order to use the beryl dbus plugin, a dbus SESSION bus has to be running. I think gnome starts one on its own, so does kde4. If you don't control beryl via dbus, then you can forget this and disable the dbus plugin.

brain0 · 2007-03-11 17:05:27

EPOWER wrote:

I found this in the beryl-forum:
Strange, if i disabled the "Decoration" plugin with beryl-settings (when beryl is not running)
I can launch beryl... (but there's no decoration)
If i renable it with beryl-settings, (when beryl is running), it works!
Its a quick fix but it works.

Can you post the link to the thread on the beryl forums please?

EDIT: found it: http://forum.beryl-project.org/viewtopi … 747#p26618

Last edited by brain0 (2007-03-11 17:11:02)

EPOWER · 2007-03-11 18:28:50

Can you post the link to the thread on the beryl forums please?

I found it here:
http://forum.beryl-project.org/viewtopi … =36&t=4651

Shirakawasuna · 2007-03-11 22:05:09

For the moment I reverted to the older beryl release, but I'll have to check out that link. It looks like it's a segfault that's already been reported upstream. http://bugs.beryl-project.org/ticket/1648

senjin · 2007-03-12 07:59:44

I have the same problem in arch64, but error message is different - if i start beryl from xfvm:

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

Detected xserver                                : NVIDIA

Checking Display :0.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 ...

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 (4096x4096)

[Warning ]: Relaunching beryl with __GL_YIELD="NOTHING"

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

Detected xserver                                : NVIDIA

Checking Display :0.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 ...

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 (4096x4096)

beryl: Could not acquire compositing manager selection on screen 0 display ":0.0"
beryl: No manageable screens found on display :0.0

and when I start beryl from kwm the last two error lines are replaced with:

beryl: Failed to load slide: /usr/share/beryl/cubecaps.png
beryl: Failed to load slide: /usr/share/beryl/cubecaps.png
beryl: Failed to load slide: /usr/share/beryl/cubecaps.png
Błąd szyny

"Błąd szyny" translates as something like "Bus error"

brain0 · 2007-03-12 08:05:25

senjin wrote:

I have the same problem in arch64, but error message is different - if i start beryl from xfvm:

What makes you think you have the same problem if the message is entirely different? Please stop spamming threads with unrelated replies. Would a moderator please split this?

senjin · 2007-03-12 08:46:26

After update to 4390-1 I can run beryl only with the same trick as posted above - disabling decorations and enabling it after beryl is started.

phunkycow · 2007-03-31 20:43:32

brain0 wrote:

senjin wrote:
I have the same problem in arch64, but error message is different - if i start beryl from xfvm:
What makes you think you have the same problem if the message is entirely different? Please stop spamming threads with unrelated replies. Would a moderator please split this?

I'm not sure it's totally unrelated. I get the exact same message, yet the workaround (disabling window decorations) fixed this for me.

senjin · 2007-03-31 20:59:06

After updates beryl works properly for me, both in i686 and 64bit archlinux...

edit: sorry, i use mostly arch64, it worked there, but in i686 arch i still need to use the "trick"

edit2: in i686 arch it seems to work sometimes - sometimes crashes, but now starts without the "trick".

Last edited by senjin (2007-04-09 10:08:36)

Arch Linux

#1 2007-03-11 03:11:04

Beryl deadly signal issue

#2 2007-03-11 05:50:54

Re: Beryl deadly signal issue

#3 2007-03-11 07:10:36

Re: Beryl deadly signal issue

#4 2007-03-11 08:13:19

Re: Beryl deadly signal issue

#5 2007-03-11 17:04:43

Re: Beryl deadly signal issue

#6 2007-03-11 17:05:27

Re: Beryl deadly signal issue

#7 2007-03-11 18:28:50

Re: Beryl deadly signal issue

#8 2007-03-11 22:05:09

Re: Beryl deadly signal issue

#9 2007-03-12 07:59:44

Re: Beryl deadly signal issue

#10 2007-03-12 08:05:25

Re: Beryl deadly signal issue

#11 2007-03-12 08:46:26

Re: Beryl deadly signal issue

#12 2007-03-31 20:43:32

Re: Beryl deadly signal issue

#13 2007-03-31 20:59:06

Re: Beryl deadly signal issue

Board footer