Re: [SLUG] compiler warnings

2003-11-25 Thread Brett Nash
 It turns out that I am sending a const string to putenv which is
 defined:
 
 ./stdlib.h:extern int putenv (char *__string) __THROW;
snip
 Should I raise this as a bug?

It isn't actually a bug.  putenv puts the supplied string into the
environment (not a copy, the supplied string).  This means a future call
to getenv will return a pointer to it, (a char *), which can be modified
to change the value.  Thus to be correct putenv can't take a const, as
it can't guarentee how the pointer will be used in future.

Take a look at the man page for putenv, in particular the notes.  As you
can see from the description, the function has a rather interesting
history in glibc ;-)

Regards,
nash
[Too much C for my own good]
-- 
Brett Nash [EMAIL PROTECTED]
Sometimes it's better to light a flamethrower than curse the darkness.
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


[SLUG] Multiple Xsessions with Gnome 2

2003-03-05 Thread Brett Nash
Hello,
I've been having some weird problems with Gnome.  I'm not sure if
gdm is the culprit or something else is.  I am currently useing gnome2.2
backported to debian 3.0.

The problem is two people use my machine.  We generally both 
like to keep an Xsession around, rather then continualy log each other
of X.  What the problem is we can't seem to start a second session of
Gnome up. 

To reproduce:
UserA: Uses startx to start an Xsession
UserB: uses 'startx -- :1' to start an Xsession

UserB's session will never start - it just hangs after it popups 
the gnoem spadh screen (no icons are shown).  UserB can log in okay if
UserA isn't logged in.  Additionally if UserB starts first, UserA won't
be able to start a session.  

To really make things strange - either user can create two
sessions, without a problem.

I'm curious if anyone has any idea what may be causing this?  If
not I'll try reporting a bug - although I'm not sure which component has
the problem.

Regards,
nash

-- 
Brett Nash [EMAIL PROTECTED]
Sometimes it's better to light a flamethrower than curse the darkness.
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Multiple Xsessions with Gnome 2

2003-03-05 Thread Brett Nash
  I've been having some weird problems with Gnome.  I'm not sure if
  gdm is the culprit or something else is.  I am currently useing gnome2.2
  backported to debian 3.0.
 
  UserA: Uses startx to start an Xsession
  UserB: uses 'startx -- :1' to start an Xsession
 
 So, if you're using startx, you're not using GDM. :-) I would recommend
 turning on GDM, and using the flexiservers feature: In the System Tools
 menu, choose New login - it will create a new X server with a login
 dialogue, and lock the current X server.

Well it has the same effect with gdm, (if userA logs in GDM it doesn't
work)

 It's cool stuff. :-)

That doesn't work either:  
- Clicking System Tools-New Login activates the screensaver on
  my current session and the monitor flickers like X restarted,
  but doesn't create a new login window.
- System Tools-New Login in a nested window works fine.

 (Not sure what the problem is with the startx approach though - perhaps look
 at .xsession-errors or something to see the error logs.)

Nothing looks bad - basically no errors in either .xession-errors, or
XFree86.1.Log.  Essentially it appears something is waiting for
something else to startup - some sort of deadlock or something.

nash
-- 
Brett Nash [EMAIL PROTECTED]
Sometimes it's better to light a flamethrower than curse the darkness.
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug


Re: [SLUG] Multiple Xsessions with Gnome 2

2003-03-05 Thread Brett Nash
  XFree86.1.Log.  Essentially it appears something is waiting for something
  else to startup - some sort of deadlock or something.
 
 Are you trying to log on as the same user (it doesn't sound like it)?
 Perhaps check the date of the other XFree86.*.log files - .1 doesn't
 necessarily mean :1...

If I start as the same user - no problem (however this is of limited
use).  The log file is the correct one.  (It even tells me on stderr
when I start X).

Basically something in gnome-session doesn;t work.  My best guess is
that gnome-session is trying to do something with the display :0.  This
will work fine for the same user as the xauth file will be fine, but if
it's a different user - no luck.

I had the same problem before, and I assumed it was something screwed in
my xfree setup (I'd had other strange problems with X previously), so I
reinstalled debian, and am now getting the same problem.  So either I've
recreated the same weirdness, or its a weird pacakge problem.

Regards,
nash

-- 
Brett Nash [EMAIL PROTECTED]
Sometimes it's better to light a flamethrower than curse the darkness.
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug