gnome-session "last only 10 second" dialog

Thank you for your bug. Do you have any apport crash file to /var/crash then?

Could you also get a valgrind log (https://wiki.ubuntu.com/Valgrind)?

i'm not too sure on how to go about running it in a way to get a log,
since my session starts fine, only if i hit the ok, does it actually
crash

On 3/18/07, Sebastien Bacher <email address hidden> wrote:
> Could you also get a valgrind log (https://wiki.ubuntu.com/Valgrind)?
>
> --
> gnome-session "last only 10 second" dialog
> https://launchpad.net/bugs/93291
>

you can use a failsafe login and run valgrind gnome-session then

Well if I run gnome failsafe, I get the error dialog , if I run
failsafe terminal and run valgrind gnome-session, gnome starts fine
and I don't get any error dialog. Should I run it with gnome-session
already started in failsafe gnome, or in the failsafe terminal?

On 3/19/07, Sebastien Bacher <email address hidden> wrote:
> you can use a failsafe login and run valgrind gnome-session then
>
> --
> gnome-session "last only 10 second" dialog
> https://launchpad.net/bugs/93291
>

--
- Justin Lintz

could you installed libglib2.0-0-dbg libgtk2.0-0-dbg gnome-session-dbgsym (https://wiki.ubuntu.com/DebuggingProgramCrash), use the failsafe terminal option, run valgrind and attach the log to the bug? It might show an error even if you don't get the crash

I've got the same problem.
This is the error.

http://phpfi.com/232945

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

I'm having a problem like this. I'm trying to install java but when a finished to do it and restart the session I got an error message that says something about 10 seconds at the last session

Refusing to initialize GTK+.
/etc/gdm/Xsession: Beginning session setup...
export DESKTOP_SESSION='gnome'
export DISPLAY=':0'
export GDMSESSION='gnome'
export GDM_LANG='pt_BR.UTF-8'
export GDM_XSERVER_LOCATION='local'
export GNOME_KEYRING_PID='5964'
export GNOME_KEYRING_SOCKET='/tmp/keyring-eqvj9f/socket'
export HOME='/home/gustavo'
export LANG='pt_BR.UTF-8'
export LANGUAGE='pt_BR:pt:en'
export LOGNAME='gustavo'
export PATH='/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games'
export PWD='/home/gustavo'
export SHELL='/bin/bash'
export USER='gustavo'
export USERNAME='gustavo'
export WINDOWPATH='7'
export XAUTHORITY='/tmp/.gdm4TN8ZT'
export XDG_DATA_DIRS='/usr/local/share/:/usr/share/:/usr/share/gdm/'
export XDG_SESSION_COOKIE='9379c47bb0f5b9a9d973380047195000-1193228955.816989-138308842'
export: 24: /bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games: bad variable name

What hell could be this? :)

i'm getting this same problem, only that i know i'm editing some files due to a java install. i need to set my JAVA_HOME variable, and to do so, i've been trying without any luck to edit this files

/etc/environment
/etc/profile
/home/username/.profile
/etc/bash.bashrc

So, perhaps this info could lead to some solution.

This started happening after I upgraded* from 8.10 (Intrepid) to 9.04 (Jaunty), last week.

Following reboot, the first login attempt to my usual user account fails, bringing me back to the login screen. The next login attempt to results in the dialog saying "Your last session lasted 10 seconds..." and the gnome session doesn't go any further. The only option at this point is to click OK in the dialog (or close the dialog), which sends me back to the login screen. The ~/.xsession-errors displayed in the dialog is attached.

My ~/.xsession is as follows (The behavior was the same with the default Xsession start script):
<code>
#!/bin/bash

exec gnome-session

### The following is a workaround for the issue with the GConf daemon not getting started...
/usr/bin/gnome-settings-daemon
</code>

I am able to start a failsafe terminal session, and the gnome session launches when I do...
<code>
$ valgrind gnome-session
</code>

I will attach the stderr & stdout (combined) below...

* The Ubuntu Intrepid -> Jaunty upgrade was in the absence of a network connection -- I suddenly lost wired and wireless networking in Intrepid, and gambled that the upgrade would fix it; alas, no such luck.

Would like to have this bug reopened. I've attached supporting info.

Re my comment above -- https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/93291/comments/13 --

Installing the recommended driver for my Nvidia graphics card seems to have fixed this.

Reverting the status back to what it was before I changed it to Confirmed -- in my case the problem was a missing graphics driver.