double login

[duportail]

ubuntu 9.04 with gdm 2.18 with multidsiplay/multiseat setup:
i can login root twice on the same machine in gnome or kde.
But if I login the a user twice on the same machine the xserver crashes.
Gdm's doubleloginwarnig is ignored.
Why can root login twice without the xserver crashing and a user not.
Is there a way to prevent double logings with gdm?

regards,
guy
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

What is your setting for AlwaysRestartServer?  I am not sure if it
would help, but you might try and see if changing this setting to
true helps.

It is difficult to debug your problem, though, since you do not provide
many details about what problem is actually happening.  Is there any
useful information in your Xorg logs (/var/log/Xorg*.log) that might
indicate what the problem might be?  Also, GDM will create a file
named $HOME/.xsession-errors.  Does this file contain any useful
error messages immediately after the problem happens?

What happens if you try to log into a failsafe session and run
"dbus-launch --exit-with-session gnome-session".  Does this work?
If not, are there any useful error messages echoed to the terminal
window?

Also, you could try to enable debug in GDM by setting Enable=true in
the [debug] section, recreate the problem, and then view the
gdm-related debug messages in your syslog (/var/adm/messages).  These
messages might highlight what the problem might be.

Brian

> ubuntu 9.04 with gdm 2.18 with multidsiplay/multiseat setup:
> i can login root twice on the same machine in gnome or kde.
> But if I login the a user twice on the same machine the xserver crashes.
> Gdm's doubleloginwarnig is ignored.
> Why can root login twice without the xserver crashing and a user not.
> Is there a way to prevent double logings with gdm?
>
> regards,
> guy
> _______________________________________________
> gdm-list mailing list
> gdm-list@...
> http://mail.gnome.org/mailman/listinfo/gdm-list

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Monday 19 October 2009 18:50:52 you wrote:

> What is your setting for AlwaysRestartServer?  I am not sure if it
> would help, but you might try and see if changing this setting to
> true helps.
>
> It is difficult to debug your problem, though, since you do not provide
> many details about what problem is actually happening.  Is there any
> useful information in your Xorg logs (/var/log/Xorg*.log) that might
> indicate what the problem might be?  Also, GDM will create a file
> named $HOME/.xsession-errors.  Does this file contain any useful
> error messages immediately after the problem happens?
>
> What happens if you try to log into a failsafe session and run
> "dbus-launch --exit-with-session gnome-session".  Does this work?
> If not, are there any useful error messages echoed to the terminal
> window?
>
> Also, you could try to enable debug in GDM by setting Enable=true in
> the [debug] section, recreate the problem, and then view the
> gdm-related debug messages in your syslog (/var/adm/messages).  These
> messages might highlight what the problem might be.
>
> Brian
>
> > ubuntu 9.04 with gdm 2.18 with multidsiplay/multiseat setup:
> > i can login root twice on the same machine in gnome or kde.
> > But if I login the a user twice on the same machine the xserver crashes.
> > Gdm's doubleloginwarnig is ignored.
> > Why can root login twice without the xserver crashing and a user not.
> > Is there a way to prevent double logings with gdm?
> >
> > regards,
> > guy
> > _______________________________________________
> > gdm-list mailing list
> > gdm-list@...
> > http://mail.gnome.org/mailman/listinfo/gdm-list

AlwaysRestartServer=true
but this settings was always that way in my case

Have found some soulution:
in gdm.conf set vtallocation=false and alwayslogincurrentsession=true(do not
think this is needed)
After that, it's impossible to login the same user:
if you try to login the same user ,after filling in username and password,you
get to see the username box again.So that is ok.(But there is no double login
warning,  when this is set to true in gdm.conf)
But  I can only make these eco-friendly multiseat computers(up to twelve users
on one box) with gdm 2.18.And it is very hard to downgrade gdm in the new
9.10.

guy
guy
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

Guy:

Glad to hear that you found some solution.  When
AlwaysLoginCurrentSession is true, this causes GDM to reconnect to any
running VT session.  So if you have a session running on VT7 and you try
to log into the same user on VT9, it will just switch you back to VT7.
The "double login" warning is a VT-specific feature, so it is expected
that you wouldn't see the warning when users try to login twice in
non-VT environments (such as multiseat or terminal server environments).

Note that VT switching is only useful on the console display and is,
therefore, generally not supported in multiseat environments.  If the
version of GDM you are using is not smart enough to realize that
non-console displays do not support VT, then it makes sense to disable
VT.  Setting VTallocation to false basically turns off VT support
entirely in GDM.

You are using GDM 2.18?  If you want to continue using the "old GDM",
then you might considering updating to the latest 2.20.10 version.  A
lot of bugs have been fixed in 2.20.10, so you might find it works
better.

Brian

> Have found some soulution:
> in gdm.conf set vtallocation=false and alwayslogincurrentsession=true(do not
> think this is needed)
> After that, it's impossible to login the same user:
> if you try to login the same user ,after filling in username and password,you
> get to see the username box again.So that is ok.(But there is no double login
> warning,  when this is set to true in gdm.conf)
> But  I can only make these eco-friendly multiseat computers(up to twelve users
> on one box) with gdm 2.18.And it is very hard to downgrade gdm in the new
> 9.10.
>
> guy
> guy
> _______________________________________________
> gdm-list mailing list
> gdm-list@...
> http://mail.gnome.org/mailman/listinfo/gdm-list

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Monday 19 October 2009 22:22:20 you wrote:

> Guy:
>
> Glad to hear that you found some solution.  When
> AlwaysLoginCurrentSession is true, this causes GDM to reconnect to any
> running VT session.  So if you have a session running on VT7 and you try
> to log into the same user on VT9, it will just switch you back to VT7.
> The "double login" warning is a VT-specific feature, so it is expected
> that you wouldn't see the warning when users try to login twice in
> non-VT environments (such as multiseat or terminal server environments).
>
> Note that VT switching is only useful on the console display and is,
> therefore, generally not supported in multiseat environments.  If the
> version of GDM you are using is not smart enough to realize that
> non-console displays do not support VT, then it makes sense to disable
> VT.  Setting VTallocation to false basically turns off VT support
> entirely in GDM.
>
> You are using GDM 2.18?  If you want to continue using the "old GDM",
> then you might considering updating to the latest 2.20.10 version.  A
> lot of bugs have been fixed in 2.20.10, so you might find it works
> better.
>
> Brian
>
> > Have found some soulution:
> > in gdm.conf set vtallocation=false and alwayslogincurrentsession=true(do
> > not think this is needed)
> > After that, it's impossible to login the same user:
> > if you try to login the same user ,after filling in username and
> > password,you get to see the username box again.So that is ok.(But there
> > is no double login warning,  when this is set to true in gdm.conf)
> > But  I can only make these eco-friendly multiseat computers(up to twelve
> > users on one box) with gdm 2.18.And it is very hard to downgrade gdm in
> > the new 9.10.
> >
> > guy
> > guy
> > _______________________________________________
> > gdm-list mailing list
> > gdm-list@...
> > http://mail.gnome.org/mailman/listinfo/gdm-list

Ok thanks,but I am not able to use gdm 2.20.And I do not know what's the
problem.
here is the gdm debug in syslog:
http://www.multiseatcomputer.be/syslog
It's a ubuntu 9.04 machine with two screens as multiseat
guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

The GDM crash seems to happen after this kernel error message:

  Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
libc-2.9.so[7f445cf3e000+168000]

Searching on Google for:

    gdm "general protection ip" sp error

I see a number of people on various distros complaining about similar
problems.  Most of them seem to be related to problems with drivers.
For example:

http://bbs.archlinux.org/viewtopic.php?id=50070
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/421442

If this is your problem, then you may need to contact your distro and
make sure that you have the latest drivers installed.  If your distro
has a bug tracking tool, I'd file a bug with them.

Or, perhaps, you might consider getting a different graphics card if the
one you are using is not well supported.

Some people seem to complain that this sort of error message is found
when using compiz.  You might try turning off compiz and see if that
helps.

Brian

> On Monday 19 October 2009 22:22:20 you wrote:
>> Guy:
>>
>> Glad to hear that you found some solution.  When
>> AlwaysLoginCurrentSession is true, this causes GDM to reconnect to any
>> running VT session.  So if you have a session running on VT7 and you try
>> to log into the same user on VT9, it will just switch you back to VT7.
>> The "double login" warning is a VT-specific feature, so it is expected
>> that you wouldn't see the warning when users try to login twice in
>> non-VT environments (such as multiseat or terminal server environments).
>>
>> Note that VT switching is only useful on the console display and is,
>> therefore, generally not supported in multiseat environments.  If the
>> version of GDM you are using is not smart enough to realize that
>> non-console displays do not support VT, then it makes sense to disable
>> VT.  Setting VTallocation to false basically turns off VT support
>> entirely in GDM.
>>
>> You are using GDM 2.18?  If you want to continue using the "old GDM",
>> then you might considering updating to the latest 2.20.10 version.  A
>> lot of bugs have been fixed in 2.20.10, so you might find it works
>> better.
>>
>> Brian
>>
>>> Have found some soulution:
>>> in gdm.conf set vtallocation=false and alwayslogincurrentsession=true(do
>>> not think this is needed)
>>> After that, it's impossible to login the same user:
>>> if you try to login the same user ,after filling in username and
>>> password,you get to see the username box again.So that is ok.(But there
>>> is no double login warning,  when this is set to true in gdm.conf)
>>> But  I can only make these eco-friendly multiseat computers(up to twelve
>>> users on one box) with gdm 2.18.And it is very hard to downgrade gdm in
>>> the new 9.10.
>>>
>>> guy
>>> guy
>>> _______________________________________________
>>> gdm-list mailing list
>>> gdm-list@...
>>> http://mail.gnome.org/mailman/listinfo/gdm-list
> Ok thanks,but I am not able to use gdm 2.20.And I do not know what's the
> problem.
> here is the gdm debug in syslog:
> http://www.multiseatcomputer.be/syslog
> It's a ubuntu 9.04 machine with two screens as multiseat
> guy
>
> _______________________________________________
> gdm-list mailing list
> gdm-list@...
> http://mail.gnome.org/mailman/listinfo/gdm-list

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Ray Strode]

Hi,

On Tue, Oct 20, 2009 at 1:48 PM, Brian Cameron <Brian.Cameron@...> wrote:

>
> The GDM crash seems to happen after this kernel error message:
>
>  Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
> protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
> libc-2.9.so[7f445cf3e000+168000]
>
> Searching on Google for:
>
>   gdm "general protection ip" sp error
>
> I see a number of people on various distros complaining about similar
> problems.  Most of them seem to be related to problems with drivers.
> For example:

No, that just means gdm crashed.

Look at the surround debug spew:

Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
string: daemon/FirstVT=7
Oct 20 09:54:30 ubu-desktop gdm[4624]: GLib-CRITICAL:
unquote_string_inplace: assertion `err == NULL || *err == NULL' failed
Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
string: security/DisallowTCP=true
Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
libc-2.9.so[7f445cf3e000+168000]
Oct 20 09:54:30 ubu-desktop gdm[3083]: DEBUG: mainloop_sig_callback:
Got signal 17
Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
child 4624 crashed of signal 11
Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
Slave crashed, killing its children

It's blowing an assertion when attempting to parse the daemon/FirstVT
key (the message makes it sound like a GError isn't getting properly
initialized to NULL), then it crashes trying to parse
security/DisallowTCP.

--Ray
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Tuesday 20 October 2009 20:14:32 you wrote:
> Hi,
>
> On Tue, Oct 20, 2009 at 1:48 PM, Brian Cameron <Brian.Cameron@...>
wrote:

> > The GDM crash seems to happen after this kernel error message:
> >
> >  Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
> > protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
> > libc-2.9.so[7f445cf3e000+168000]
> >
> > Searching on Google for:
> >
> >   gdm "general protection ip" sp error
> >
> > I see a number of people on various distros complaining about similar
> > problems.  Most of them seem to be related to problems with drivers.
> > For example:
>
> No, that just means gdm crashed.
>
> Look at the surround debug spew:
>
> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
> string: daemon/FirstVT=7
> Oct 20 09:54:30 ubu-desktop gdm[4624]: GLib-CRITICAL:
> unquote_string_inplace: assertion `err == NULL || *err == NULL' failed
> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
> string: security/DisallowTCP=true
> Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
> protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
> libc-2.9.so[7f445cf3e000+168000]
> Oct 20 09:54:30 ubu-desktop gdm[3083]: DEBUG: mainloop_sig_callback:
> Got signal 17
> Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
> child 4624 crashed of signal 11
> Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
> Slave crashed, killing its children
>
> It's blowing an assertion when attempting to parse the daemon/FirstVT
> key (the message makes it sound like a GError isn't getting properly
> initialized to NULL), then it crashes trying to parse
> security/DisallowTCP.
>
> --Ray

Gdm 2.20 is starting ok if I set it up for starting only one display (one
standard server)
So the error comes from starting two displays (with one standard server not
handled) or has it something to do with starting a xgl session above xorg,
(but never have problems in gdm 2.18)
Guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Tuesday 20 October 2009 20:14:32 you wrote:
> Hi,
>
> On Tue, Oct 20, 2009 at 1:48 PM, Brian Cameron <Brian.Cameron@...>
wrote:

> > The GDM crash seems to happen after this kernel error message:
> >
> >  Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
> > protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
> > libc-2.9.so[7f445cf3e000+168000]
> >
> > Searching on Google for:
> >
> >   gdm "general protection ip" sp error
> >
> > I see a number of people on various distros complaining about similar
> > problems.  Most of them seem to be related to problems with drivers.
> > For example:
>
> No, that just means gdm crashed.
>
> Look at the surround debug spew:
>
> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
> string: daemon/FirstVT=7
> Oct 20 09:54:30 ubu-desktop gdm[4624]: GLib-CRITICAL:
> unquote_string_inplace: assertion `err == NULL || *err == NULL' failed
> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
> string: security/DisallowTCP=true
> Oct 20 09:54:30 ubu-desktop kernel: [  403.527767] gdm[4624] general
> protection ip:7f445cfbec40 sp:7fff6974c088 error:0 in
> libc-2.9.so[7f445cf3e000+168000]
> Oct 20 09:54:30 ubu-desktop gdm[3083]: DEBUG: mainloop_sig_callback:
> Got signal 17
> Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
> child 4624 crashed of signal 11
> Oct 20 09:54:30 ubu-desktop gdm[3083]: WARNING: gdm_cleanup_children:
> Slave crashed, killing its children
>
> It's blowing an assertion when attempting to parse the daemon/FirstVT
> key (the message makes it sound like a GError isn't getting properly
> initialized to NULL), then it crashes trying to parse
> security/DisallowTCP.
>
> --Ray

fresh install with ubuntu 9.10 and gdm-2.20 and getting errors in:
syslog:
http://www.multiseatcomputer.be/syslog
look at the xserver not found garbage:
Oct 23 15:10:41 ubu-desktop gdm[1425]: DEBUG: gdm_server_spawn: 'À,
#001 -auth /var/lib/gdm/:0.Xauth -nolisten tcp'
Oct 23 15:10:41 ubu-desktop gdm[1425]: WARNING: gdm_server_spawn: X-server
niet gevonden: À,#001 -auth /var/lib/gdm/:0.Xauth -nolisten tcp

same error in /var/log/gdm:
http://www.multiseatcomputer.be/gdm0.log

ofcourse with gdm 2.18 no problems.

regards,
Guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

Ray:

Good catch.

>> Look at the surround debug spew:
>>
>> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
>> string: daemon/FirstVT=7
>> Oct 20 09:54:30 ubu-desktop gdm[4624]: GLib-CRITICAL:
>> unquote_string_inplace: assertion `err == NULL || *err == NULL' failed
>> Oct 20 09:54:30 ubu-desktop gdm[4624]: DEBUG: Attempting to parse key
>>
>> It's blowing an assertion when attempting to parse the daemon/FirstVT
>> key (the message makes it sound like a GError isn't getting properly
>> initialized to NULL), then it crashes trying to parse
>> security/DisallowTCP.

I don't think it is crashing when parsing the keys.  Note that the
function unquote_string_inplace is in the glib file gshell.c.  This
is called by g_shell_unquote, which is only called by
g_shell_parse_argv().  I do not think that g_shell_parse_argv is called
at all in the process of parsing configuration options.

The parsing of FirstVT is done in daemon/getvt.c in the get_free_vt*
functions, which are called by gdm_get_empty_vt_argument().  This
is called in daemon/server.c by gdm_server_start().  Immediately
after calling gdm_get_empty_vt_argument, it calls gdm_server_spawn().

This code looks as follows (in GDM 2.20.10).  Note that the call to
ve_first_word does call g_shell_parse_argv, but does pass in NULL as the
error argument, so that cannot be the problem.

        bin = ve_first_word (disp->command);

        if (bin == NULL) {
[...]
        } else if (bin[0] != '/') {

                GdmXserver *svr = gdm_daemon_config_find_xserver (bin);
                if (svr == NULL) {
[...]
                } else {
                         GError* error_p;
[...]
                        g_shell_parse_argv (str, &svr_argc,
                                &svr_command, &error_p);

                        g_shell_parse_argv (disp->command, &argc,
                                &argv, &error_p);

I note that error_p is never set to NULL.  So, I'm guessing that the
problem is that this variable isn't getting initialized to NULL, and
on your system this is triggering the assertion.

If you want to patch the code to set error_p to NULL, I think this
would resolve the problem.

I note that it only falls into this problematic code segment if the
Xserver binary is not specified by full path (note the test
"if (bin[0] != '/'" above).  So, if my analysis is right, then you
could avoid this problem by providing the full path to the Xserver
in your configuration.

If that isn't right, I have pointed you towards the code where the
problem is happening so others can do further analysis.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Friday 23 October 2009 18:40:06 you wrote:
> I note that it only falls into this problematic code segment if the
> Xserver binary is not specified by full path (note the test
> "if (bin[0] != '/'" above).  So, if my analysis is right, then you
> could avoid this problem by providing the full path to the Xserver
> in your configuration.

Where to specify the full path to the Xserver?
In ubuntu 9.10 when installing gdm-2.20 and removing the new gdm, the xserver
path's in gdm.conf are incorrect.(but that was not the problem I hope)
Is this gdm 2.20 reading from the /etc/gdm/gdm.conf?
Is the error something to do with upstart?
because my setup is working with gdm 2.18, but this gdm is not started with
upstart automaticly.(strange:the pc start is ending in console(no x), and
when I do a gdm stop, it is starting gdm 2.18.

Note, when the computer is started with gdm-2.20, i end up in console, but i
can do a startx and getting gnome alright.

Guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

duportail wrote:
> On Friday 23 October 2009 18:40:06 you wrote:
>> I note that it only falls into this problematic code segment if the
>> Xserver binary is not specified by full path (note the test
>> "if (bin[0] != '/'" above).  So, if my analysis is right, then you
>> could avoid this problem by providing the full path to the Xserver
>> in your configuration.
>
> Where to specify the full path to the Xserver?

It is specified in the [daemon] section by the "StandardXServer" key and
also in the various [server-foo] sections by the "command" key.  It is
probably the later which is being used in your case.  I'd check both.
More information is here:

http://library.gnome.org/admin/gdm/2.20/configuration.html.en

You might also check for any leading white space in the keys.  That
might also cause a problem.

If the full path is being specified and there is no leading whitespace,
then the problem is likely something else.  Further review of the code,
or building it with debug enabled and attaching a debugger may be needed
to figure out exactly where the failure is happening.  My analysis is
just a guess based on looking at the code.

> In ubuntu 9.10 when installing gdm-2.20 and removing the new gdm, the xserver
> path's in gdm.conf are incorrect.(but that was not the problem I hope)
> Is this gdm 2.20 reading from the /etc/gdm/gdm.conf?

Different distros use different filenames for the configuration file.
The default setting is usually in /usr/share/gdm/defaults.conf, and the
values can be customized in the /etc/gdm/custom.conf or
/etc/gdm/gdm.conf file.

> Is the error something to do with upstart?
> because my setup is working with gdm 2.18, but this gdm is not started with
> upstart automaticly.(strange:the pc start is ending in console(no x), and
> when I do a gdm stop, it is starting gdm 2.18.

I have no idea what upstart means.  Different distros use different
mechanisms to start GDM, so you'll probably need to talk to your distro
to find out exactly how GDM is being started, and how the service is
being managed.

Brian

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Friday 23 October 2009 19:52:13 you wrote:

> duportail wrote:
> > On Friday 23 October 2009 18:40:06 you wrote:
> >> I note that it only falls into this problematic code segment if the
> >> Xserver binary is not specified by full path (note the test
> >> "if (bin[0] != '/'" above).  So, if my analysis is right, then you
> >> could avoid this problem by providing the full path to the Xserver
> >> in your configuration.
> >
> > Where to specify the full path to the Xserver?
>
> It is specified in the [daemon] section by the "StandardXServer" key and
> also in the various [server-foo] sections by the "command" key.  It is
> probably the later which is being used in your case.  I'd check both.
> More information is here:
>
> http://library.gnome.org/admin/gdm/2.20/configuration.html.en
>
> You might also check for any leading white space in the keys.  That
> might also cause a problem.
>
> If the full path is being specified and there is no leading whitespace,
> then the problem is likely something else.  Further review of the code,
> or building it with debug enabled and attaching a debugger may be needed
> to figure out exactly where the failure is happening.  My analysis is
> just a guess based on looking at the code.
>
> > In ubuntu 9.10 when installing gdm-2.20 and removing the new gdm, the
> > xserver path's in gdm.conf are incorrect.(but that was not the problem I
> > hope) Is this gdm 2.20 reading from the /etc/gdm/gdm.conf?
>
> Different distros use different filenames for the configuration file.
> The default setting is usually in /usr/share/gdm/defaults.conf, and the
> values can be customized in the /etc/gdm/custom.conf or
> /etc/gdm/gdm.conf file.
>
> > Is the error something to do with upstart?
> > because my setup is working with gdm 2.18, but this gdm is not started
> > with upstart automaticly.(strange:the pc start is ending in console(no
> > x), and when I do a gdm stop, it is starting gdm 2.18.
>
> I have no idea what upstart means.  Different distros use different
> mechanisms to start GDM, so you'll probably need to talk to your distro
> to find out exactly how GDM is being started, and how the service is
> being managed.
>
> Brian

Ok, I got multiseat working with ubuntu 9.10 with gdm-2.20 .
It cost me some time to figure out the gdmgreeter was crashing.(but not in gdm
2.18)Changing this setting to gdmlogin works ok(but it's the old style debian
greeter).I believe that gdm is too much attached to gnome,because with dual
screens, not only the greeter is crashing also gnome-panel.
Maybe something to do with xrandr.

Guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

> Ok, I got multiseat working with ubuntu 9.10 with gdm-2.20 .
> It cost me some time to figure out the gdmgreeter was crashing.(but not in gdm
> 2.18)Changing this setting to gdmlogin works ok(but it's the old style debian
> greeter).I believe that gdm is too much attached to gnome,because with dual
> screens, not only the greeter is crashing also gnome-panel.
> Maybe something to do with xrandr.

Glad to hear you got things working.  If you could provide a stack trace
of gdmgreeter, or any further information, I'd be happy to help debug.
But glad to hear that gdmlogin is a workaround.

Sorry to hear about your problem with gnome-panel.  I'd recommend filing
a bug at http://bugzilla.gnome.org/ under gnome-panel with details about
the crash.  It's probably not a related issue.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Tuesday 27 October 2009 19:07:40 you wrote:

> > Ok, I got multiseat working with ubuntu 9.10 with gdm-2.20 .
> > It cost me some time to figure out the gdmgreeter was crashing.(but not
> > in gdm 2.18)Changing this setting to gdmlogin works ok(but it's the old
> > style debian greeter).I believe that gdm is too much attached to
> > gnome,because with dual screens, not only the greeter is crashing also
> > gnome-panel.
> > Maybe something to do with xrandr.
>
> Glad to hear you got things working.  If you could provide a stack trace
> of gdmgreeter, or any further information, I'd be happy to help debug.
> But glad to hear that gdmlogin is a workaround.
>
> Sorry to hear about your problem with gnome-panel.  I'd recommend filing
> a bug at http://bugzilla.gnome.org/ under gnome-panel with details about
> the crash.  It's probably not a related issue.
>
> Brian

Maybe some additional info:
if Vtallocation is set to false, it's not working whatsoever.
If vtallocation is set to true or commented out,it's working.
here is the syslog debug with gdmgreeter in gdm.conf but crashing:
http://www.multiseatcomputer.be/syslog

and here with gdmlogin in gdm.conf working:
http://www.multiseatcomputer.be/syslogok

maybe you see something.(do not pay attention to kdm-kde3,i've installed kde3
on the machine,but same errors without kde3)


guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[Brian Cameron]

> Maybe some additional info:
> if Vtallocation is set to false, it's not working whatsoever.
> If vtallocation is set to true or commented out,it's working.
> here is the syslog debug with gdmgreeter in gdm.conf but crashing:
> http://www.multiseatcomputer.be/syslog
>
> and here with gdmlogin in gdm.conf working:
> http://www.multiseatcomputer.be/syslogok

It looks like GDM is treating your displays as type FLEXI, but the
displays you are starting are obviously not flexi.  Setting Vtallocation
to false, just disables the VT switching support, and thus avoids the
problem.

In your GDM configuration file, if you have "flexible=true" in the
[server-Foo] section associated with the server you are trying to start,
that would cause this problem if the display doesn't really support VT.

Brian
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Tuesday 27 October 2009 19:54:16 duportail wrote:

> On Tuesday 27 October 2009 19:07:40 you wrote:
> > > Ok, I got multiseat working with ubuntu 9.10 with gdm-2.20 .
> > > It cost me some time to figure out the gdmgreeter was crashing.(but not
> > > in gdm 2.18)Changing this setting to gdmlogin works ok(but it's the old
> > > style debian greeter).I believe that gdm is too much attached to
> > > gnome,because with dual screens, not only the greeter is crashing also
> > > gnome-panel.
> > > Maybe something to do with xrandr.
> >
> > Glad to hear you got things working.  If you could provide a stack trace
> > of gdmgreeter, or any further information, I'd be happy to help debug.
> > But glad to hear that gdmlogin is a workaround.
> >
> > Sorry to hear about your problem with gnome-panel.  I'd recommend filing
> > a bug at http://bugzilla.gnome.org/ under gnome-panel with details about
> > the crash.  It's probably not a related issue.
> >
> > Brian
>
> Maybe some additional info:
> if Vtallocation is set to false, it's not working whatsoever.
> If vtallocation is set to true or commented out,it's working.
> here is the syslog debug with gdmgreeter in gdm.conf but crashing:
> http://www.multiseatcomputer.be/syslog
>
> and here with gdmlogin in gdm.conf working:
> http://www.multiseatcomputer.be/syslogok
>
> maybe you see something.(do not pay attention to kdm-kde3,i've installed
> kde3 on the machine,but same errors without kde3)
>
>
> guy
>
> _______________________________________________
> gdm-list mailing list
> gdm-list@...
> http://mail.gnome.org/mailman/listinfo/gdm-list

And this is a working setup with gdm 2.18 and de gdmgreeter:
http://www.multiseatcomputer.be/syslog218
but gdm changed the inlogscreen language(not in dutch anymore)
guy
_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list

[duportail]

On Tuesday 27 October 2009 20:15:46 you wrote:

> > Maybe some additional info:
> > if Vtallocation is set to false, it's not working whatsoever.
> > If vtallocation is set to true or commented out,it's working.
> > here is the syslog debug with gdmgreeter in gdm.conf but crashing:
> > http://www.multiseatcomputer.be/syslog
> >
> > and here with gdmlogin in gdm.conf working:
> > http://www.multiseatcomputer.be/syslogok
>
> It looks like GDM is treating your displays as type FLEXI, but the
> displays you are starting are obviously not flexi.  Setting Vtallocation
> to false, just disables the VT switching support, and thus avoids the
> problem.
>
> In your GDM configuration file, if you have "flexible=true" in the
> [server-Foo] section associated with the server you are trying to start,
> that would cause this problem if the display doesn't really support VT.
>
> Brian

No, all servers are flexible=false

all i am getting is a box with :the greeter is stopped unexpected,try to use
another one.Than i get the old style debian login box.But keyboard is not
working at that moment.

Guy

_______________________________________________
gdm-list mailing list
gdm-list@...
http://mail.gnome.org/mailman/listinfo/gdm-list