Incomplete logout options with XGL

Bug #36321 reported by cbudden
28
Affects Status Importance Assigned to Milestone
gnome-session (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs
ubuntu-meta (Ubuntu)
Invalid
Medium
Unassigned
xserver-xgl (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Hello.
When I am using XGL, I have incomplete logout options. When I switch back to non XGL, the other missing options are there. This is regardless of whether i'm running Compiz or not.

http://img209.imageshack.us/img209/923/untitled0em.png

Thanks

cbudden (chrisbudden)
description: updated
Revision history for this message
Dreaden (christophe-mestdag) wrote :

Hello,
I'v got the same problem as cbudden.
When I logout in standard metacity (non-xgl) configuration, the normal Log Out Dialog appears, with all the options available.

When I do the same while using XGL, the lower row isn't longer available (only: log out, switch user and lock screen)

I do start XGL with a script after I logged in in GDM. So I guess GDM doesn't run on XGL. (or I'm wrong here?)

Thx

Revision history for this message
Daniel Holbach (dholbach) wrote :

No ubuntu-meta bug.

Changed in ubuntu-meta:
status: Unconfirmed → Rejected
Revision history for this message
Yotam Benshalom (benshalom) wrote :

Same problem here. I use ATI card and run xgl & compiz from ~/.Xsession file, running after gdm is loaded. I can only logout, switch user, lock screen and hibernate from gnome when running xgl, but not shutdown or restart.

Revision history for this message
Bazon (bazonbloch) wrote :

This happens to me, too, and I'd like to add how XGL is started exactly to make it better reproduceable:
A new xsession is created:
/usr/share/xsessions/xgl.desktop

containing:

[Desktop Entry]
Encoding=UTF-8
Name=XGl
Exec=/usr/bin/startxgl.sh
Icon=
Type=Application

where /usr/bin/startxgl.sh is the script which actually starts xgl and looks in a minimal case (not starting compiz withit) like this:

#!/bin/bash

Xgl -fullscreen :1 -ac -accel glx:pbuffer -accel xv:fbo & sleep 2 && DISPLAY=:1 gnome-session

This is a popular method to start XGL, as it leaves you the option to start a normal Xorg Session from GDM.

It is reported e.g.:
http://ubuntuforums.org/showthread.php?t=174233
http://compiz.net/viewtopic.php?pid=3645#p3645
http://tinyurl.com/lgjsz
http://tinyurl.com/n8vkk
(tiny as I don't want to break the layout...)

Revision history for this message
Bazon (bazonbloch) wrote :

There is another way to reproduce this, even without XGL, just normal Xorg:
When X is started anywhere exept tty7, the logout options miss aswell!

To see this, first stop x on tty7, then startx on e.g. tty1 and hit the logout panel there...

So maybe this bug should be described as "Incomplete logout options on secondary X-Servers".

Revision history for this message
dejitarob (rheck) wrote :

I have this problem and never installed XGL and my X is on tty7.

Revision history for this message
dejitarob (rheck) wrote :

Sorry for the double post, accidently hit refresh. Since I do not have XGL, mine might be related more to https://launchpad.net/distros/ubuntu/+source/gnome-session/+bug/44585

Revision history for this message
Didier L (l-farquaad) wrote :

I think that bug comes from the fact that it is GDM that manages halt and reboot (because only root can do that). To do that, it uses a socket file which is /tmp/.gdm_socket. On the other side, gnome-panels sends request through that socket using (I think) gdmflexiserver, as stated in the other bug (44585). Here, under Xgl, here is what I have:
$ gdmflexiserver -a -c QUERY_LOGOUT_ACTION

(process:10648): GLib-GObject-CRITICAL **: gtype.c:2215: initialization assertion failed, use IA__g_type_init() prior to this function

(process:10648): Gdk-CRITICAL **: gdk_display_get_name: assertion `GDK_IS_DISPLAY (display)' failed
ERROR 100 Not authenticated

But if I tell him to use the display 0 then...
$ DISPLAY=:0 gdmflexiserver -a -c QUERY_LOGOUT_ACTION

(process:10653): GLib-GObject-CRITICAL **: gtype.c:2215: initialization assertion failed, use IA__g_type_init() prior to this function

(process:10653): Gdk-CRITICAL **: gdk_display_get_name: assertion `GDK_IS_DISPLAY (display)' failed
OK HALT;REBOOT;SUSPEND;HIBERNATE

So I suppose that gnome-panel, which is launched by gnome-session itself having DISPLAY=:1 receives the same answer and so, does not show those options.

I just wonder why hibernate and suspend appear, and even work (I only tried suspend) as it should also be gdm (or at least a program launched as root) which manages that...

Revision history for this message
Anakin Starkiller (sunrider) wrote :

Same problem here. With the first installation method for Xgl, this issue disappear. So I think the problem is in the GDM config files...

Revision history for this message
Sebastien Bacher (seb128) wrote :

sleep and hibernate come from gnome-power-manager. Why do you have an another display used?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Reassigning to gnome-session which has the code for that dialog

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Medium → Low
Revision history for this message
Dreaden (christophe-mestdag) wrote : Re: [Bug 36321] Re: Incomplete logout options with XGL

Sebastien Bacher wrote:
> sleep and hibernate come from gnome-power-manager. Why do you have an
> another display used?
>

Hello,

I use another display to run XGL upon the normal Xorg. So that I would
have an option in GDM te select XGL/compiz or Xorg/metacity. So if
compiz should break down, I'm able to switch very easely.

I know it's not the best way to use XGL, but the only problem is just
the lack of the shutdown option. Otherwise, everything works fine this
way. I guess that the problem will vanish when Edgy will run AIGLX directly.

Kind Regards,

Christophe Mestdag

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you still have that problem with edgy or feisty?

Changed in gnome-session:
status: Unconfirmed → Needs Info
Revision history for this message
cbudden (chrisbudden) wrote :

Don't know about feisty and as I use XGL via gdm now I don't get the problem, but when I tested XGL with a .Xsession file, it was still there.

Revision history for this message
none (ubuntu-bugs-nullinfinity-deactivatedaccount) wrote :

This bug is still present in Feisty.

Revision history for this message
none (ubuntu-bugs-nullinfinity-deactivatedaccount) wrote :

Using the script from http://wiki.beryl-project.org/index.php/Install/Ubuntu/Edgy/XGL#Adding_an_Xgl_login_session , under "Shutdown and reboot buttons in GNOME" fixes the issue for me.

Revision history for this message
Didier L (l-farquaad) wrote :

I confirm that the two lines given in the script from beryl-project's wiki correct this issue. It seems finally that it came from incomplete howto and not from a bug in Xgl.

I just noticed that the French wiki was already modified to include those lines, but it seems absent from in wiki.ubuntu.com.

Thanks a lot to Johan Brannlund for finding this fix (workaround ?)

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you use xgl or aiglx?

Revision history for this message
none (ubuntu-bugs-nullinfinity-deactivatedaccount) wrote :

I use Xgl. The problem seems to be that the Xgl server running on :1 doesn't have access to the authentication cookies on :0 .

Revision history for this message
Umuntu-Tim- (thembinkosi) wrote :

you need to add this to your start up programes "gnome-settings-daemon &" that will fix the ugly gray them to fix the incomplete logout options look here --------------------> http://wiki.beryl-project.org/wiki/Install_Beryl_on_Ubuntu_Edgy_with_XGL

just find the line were it talks about "Shutdown and reboot buttons in GNOME"

or click (Ctrl+f) and paste "Shutdown and reboot buttons in GNOME"

good luck!!

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I don't see this problem in Feisty's XGL which I launch via GDM (using steps similar to those outlined on https://help.ubuntu.com/community/CompositeManager/Xgl#head-0e4ffce2a76cdb03b8dbd57642f13fac385afef0 ).

cbudden:
Can you indicate whether you see this problem in Feisty when launching XGL from GDM?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Setting to neesinfo pending reply from cbudden.

Changed in xserver-xgl:
status: Unconfirmed → Needs Info
Revision history for this message
John Dong (jdong) wrote :

Comment #21 has the correct workaround for this (giving Xgl the X cookie to talk to dbus properly)

Revision history for this message
Daniel Holbach (dholbach) wrote :

Is this really a gnome-session problem?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does anybody still get the bug on feisty and could describe some easy steps to trigger it?

Revision history for this message
John Dong (jdong) wrote :

This is not a bug, but rather misconfiguration..
If you start Xgl as a session (rather than having GDM hosted on Xgl), X cookies are not forwarded by default. Make sure your Xgl starter script contains two lines like:
cookie="$(xauth -i nextract - :0 | cut -d ' ' -f 9)"
xauth -i add :1 . "$cookie"

and you will get full logout options.

Changed in xserver-xgl:
status: Needs Info → Rejected
Changed in gnome-session:
status: Needs Info → Rejected
Revision history for this message
maverick (maverick1-go2) wrote :

Not always.
I know that my problem is not a bug for gnome.
But there are my scripts:

 maverick@maverick:~% cat /usr/share/xsessions/xgl.desktop 3:23
[Desktop Entry]
Encoding=UTF-8
Name=Xgl
Comment=Start an Xgl Session
Exec=/usr/bin/startxgl
Icon=
Type=XSession

maverick@maverick:~% cat /usr/bin/startxgl 3:24
#!/bin/bash
Xgl :1 -fullscreen -ac -accel xv:pbuffer -accel glx:pbuffer -br &
DISPLAY=:1
export KDEWM="/usr/bin/beryl-manager"
cookie="$(xauth -i nextract - :0 | cut -d ' ' -f 9)"
xauth -i add :1 . "$cookie"
# beryl-manager &
exec startkde

Unfortunatelly on logout window there is only logout button.

What is wrong in those scripts ?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.