Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. 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#24016 - [(free)nx] It is not possible to log into a gnome session after upgrade to Gnome3

Attached to Project: Arch Linux
Opened by Henrik Skärnell (munkoil) - Sunday, 01 May 2011, 09:17 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 23 June 2011, 07:43 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Andreas Radke (AndyRTR)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After an upgrade to Gnome3 the remote login to a gnome session breaks. There is a message over the screen that says

Oh no! Something has gone wrong.
A problem has occured and the system can't recover.
Please log out and try again.

There is only the possibility to log out.

It also seems that sometimes the menu appears and I'm able to start programs but the windows don't work the way they are supposed to. This seems to happen the first time after a reboot.

Gnome3 works on a local login, both in standard and fallback mode. In the NX session the fallback mode is the only available.

Additional info:
All packages are up to date. Freenx has a standard configuration from arch-wiki.

Steps to reproduce:
Upgrade to Gnome3 and try to login with nx.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Thursday, 23 June 2011, 07:43 GMT
Reason for closing:  Fixed
Additional comments about closing:  OP reports that the issue does not exist with newer packages.
Comment by Ionut Biru (wonder) - Sunday, 01 May 2011, 11:43 GMT
can you paste ~/.xsession-errors to see what happens and why is failing to start the fallback mode automatically when using freenx?
Comment by Henrik Skärnell (munkoil) - Sunday, 01 May 2011, 12:02 GMT
There is no ~/.xsession-errors.

Maybe because the X starts properly and the problem is with gnome. I don't know. I've searched the whole disc for *xsession* and only find a .xsession-errors for another user not used for NX.

I attach an screenshot of what I get. Maybe it can help in some way. There is an session only it doesn't work properly.
   screenshot.jpg (81.2 KiB)
Comment by Ionut Biru (wonder) - Sunday, 01 May 2011, 16:51 GMT
i really don't know where freenx stores the log but without it we cannot do anything
Comment by Henrik Skärnell (munkoil) - Sunday, 01 May 2011, 17:44 GMT
Hi,

I found a file I think is the one you are asking for. It was located in ~/.nx/<session-id>/session, where <session-id> is a folder with a name of the session. At least the last part looks like the .xsession-errors file I have for another user.

I also made a new user to test this so no old configs would interfere.
   session (2.8 KiB)
Comment by Ionut Biru (wonder) - Sunday, 01 May 2011, 17:47 GMT
definitely report this to http://bugzilla.gnome.org
Comment by Henrik Skärnell (munkoil) - Sunday, 01 May 2011, 17:49 GMT
I'm kind of new to reporting bugs here :). Is it usually the one, in this case me, who report this upstream or do someone who knows more than me usually do it?

I don't even know to what part of gnome this should be reported. Metacity?
Comment by Isenmann Daniel (ise) - Tuesday, 03 May 2011, 18:07 GMT
I have set up a FreeNX server on my x86_64 box and connecting with the nomachine nx client for windows into my gnome3 session. It uses the fallback mode of GNOME3 but it works without any errors. No error appears on login or startup. I'm starting GNOME3 with a custom command in the nx client and set it to "/usr/bin/gnome-session".
Comment by Michael Oczak (dsoul) - Monday, 09 May 2011, 09:10 GMT
here is a patch for gnome-desktop
https://bugzilla.gnome.org/show_bug.cgi?id=649053
already commited upstream
http://git.gnome.org/browse/gnome-desktop/commit/?id=aa93854f2ba6b0f72f1bdff9699b5724a72c89c9
Comment by Ionut Biru (wonder) - Monday, 09 May 2011, 10:41 GMT
thanks for letting me know. i'll fix that soon
Comment by Ionut Biru (wonder) - Tuesday, 10 May 2011, 16:21 GMT
i pushed gnome-desktop-3.0.1-2. let me know if is working
Comment by Henrik Skärnell (munkoil) - Tuesday, 10 May 2011, 17:29 GMT
It looks different, much quicker to log in, and actually I can see the background for a short while but still the same problem. See picture and log.

P.S. I built the package myself from trunk since it wasn't on the servers yet.
   screenshot.png (94.2 KiB)
   session (3.7 KiB)
Comment by Josh (segfault) - Wednesday, 11 May 2011, 15:03 GMT
The problem still exists for me with gnome-desktop 3.0.1-2 as well - I see the same thing as munkoil.
Comment by Michael Oczak (dsoul) - Thursday, 12 May 2011, 07:17 GMT
I'm using x2go which is based on nx and it works almost ok after update. Based on session.log from munkoil I would try with clean user, switch on gnome fallback mode, launch gnome-session witch console-kit, ck-launch-session gnome-session.
Comment by Henrik Skärnell (munkoil) - Thursday, 12 May 2011, 08:35 GMT
dsoul: I still have the same problem. I just created a new user and used ck-launch-session gnome-session into fallback mode. The session.log is almost identical.
   session (3.1 KiB)
Comment by Henrik Skärnell (munkoil) - Thursday, 12 May 2011, 09:33 GMT
I just did a fresh install to a virtual machine and it still does not work. The virtual machine produce the same error.
Comment by Michael Oczak (dsoul) - Thursday, 12 May 2011, 13:48 GMT
what is the output of 'gsettings get org.gnome.desktop.session session-name'?
Comment by Henrik Skärnell (munkoil) - Thursday, 12 May 2011, 14:11 GMT
'gnome-fallback'
Comment by Michael Oczak (dsoul) - Friday, 13 May 2011, 14:25 GMT
start xserver and metacity from terminal
Comment by Henrik Skärnell (munkoil) - Saturday, 14 May 2011, 07:34 GMT
How do you want me to do this? Do you want me to do it over ssh, NX or locally? Locally it just works. But I don't exactly understand what you want me to do. I have logged into the session with both ssh and NX. When I run 'startx' on both. I can't see anything, maybe it uses the local display. When I run 'ck-launch-session gnome-session' I get the same error on both the ssh and NX session. Please clarify if you ment me to do this in any other way.

By the way, when I run 'metacity' there if a segmentation fault but 'metacity-window-demo' works.

Loading...