Re: cannot log in with gdm after lenny upgrade
On Wed, Jan 02, 2008 at 12:58:22AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: On Mon, 31 Dec 2007 09:49:43 -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 03:58:03AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): INvalid argument mkdtemp: private socket dir: Permission denied That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR [snip -- glad to hear it worked for you] Thanks. How did you ever manage to think of this? The main thing for me was to ignore all those messages about suid GTK+ programs; since the log continues past those messages, it's a good (although not certain) bet that they're unrelated to the problem. Once I read past them I saw the failures above (listen and mkdtemp), which sound like a program trying to create a listen socket in /tmp and failing. In particular, there's no other obvious reason for mkdtemp to fail with permission denied; even nobody can write to /tmp on a default Debian system. As Andrew said, that message is a pretty big clue, once you've waded through all the other chatter in the log. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Wed, 02 Jan 2008 07:57:22 -0800, Daniel Burrows wrote: On Wed, Jan 02, 2008 at 12:58:22AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: On Mon, 31 Dec 2007 09:49:43 -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 03:58:03AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): Invalid argument mkdtemp: private socket dir: Permission denied That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR [snip -- glad to hear it worked for you] Thanks. How did you ever manage to think of this? The main thing for me was to ignore all those messages about suid GTK+ programs; since the log continues past those messages, it's a good (although not certain) bet that they're unrelated to the problem. Once I read past them I saw the failures above (listen and mkdtemp), which sound like a program trying to create a listen socket in /tmp and failing. In particular, there's no other obvious reason for mkdtemp to fail with permission denied; even nobody can write to /tmp on a default Debian system. As Andrew said, that message is a pretty big clue, once you've waded through all the other chatter in the log. Daniel I'm trying to understand how these library calls are related to /tmp, since this is the kind of stuff I think I should know about. I looked for the specification of listen(), and found a man page with the synopsis int listen(int socket, int backlog); No reference to /tmp here. And for mkdtemp I find char *mkdtemp(char *template); Could it be the template starts with /tmp/XX or something like that? Or are temporary directory is alwayse put inside /tmp ? How is a temporary directory related to a socket? Or, where should I look to find the answers to this kind of question? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Thu, Jan 03, 2008 at 02:57:20AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: On Wed, 02 Jan 2008 07:57:22 -0800, Daniel Burrows wrote: On Wed, Jan 02, 2008 at 12:58:22AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: Thanks. How did you ever manage to think of this? The main thing for me was to ignore all those messages about suid GTK+ programs; since the log continues past those messages, it's a good (although not certain) bet that they're unrelated to the problem. Once I read past them I saw the failures above (listen and mkdtemp), which sound like a program trying to create a listen socket in /tmp and failing. In particular, there's no other obvious reason for mkdtemp to fail with permission denied; even nobody can write to /tmp on a default Debian system. As Andrew said, that message is a pretty big clue, once you've waded through all the other chatter in the log. I'm trying to understand how these library calls are related to /tmp, since this is the kind of stuff I think I should know about. I'm glad to hear you were actually interested, I was a little worried I might be replying to a rhetorical question. :-) I looked for the specification of listen(), and found a man page with the synopsis int listen(int socket, int backlog); No reference to /tmp here. And for mkdtemp I find char *mkdtemp(char *template); Could it be the template starts with /tmp/XX or something like that? Or are temporary directory is alwayse put inside /tmp ? How is a temporary directory related to a socket? mkdtemp() is for creating temporary directories, which traditionally go in /tmp. Most programs will check $TMPDIR and default to /tmp if it's not set. A number of popular desktop IPC packages use Unix-domain sockets or named pipes created in /tmp. I'm particularly thinking of dbus, mcop (?), and. Unix-domain sockets are sockets for communication between processes on the same computer; they can appear in the filesystem (see unix(7), socket(2) and bind(2) for more information on them) and are subject to filesystem permission rules. They can also be created in an abstract namespace which is not tied to the filesystem, and apparently at least dbus does this. In that case permissions problems would not affect them. It's possible that the listen() failure was a red herring and I was just lucky. ;-) It looks like dbus and friends create their sockets in the abstract namespace, so the /tmp thing wouldn't affect them. (you can use find /tmp -type s to find sockets in /tmp) Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Mon, 31 Dec 2007 09:49:43 -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 03:58:03AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): INvalid argument mkdtemp: private socket dir: Permission denied That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR Daniel Sure looks like it. Mounting lenny's root partition on /other on my backup etch system, I get lovesong:/farhome/hendrik# ls -ld /other/tmp drwxr-xr-x 6 root root 4096 2007-12-31 10:05 /other/tmp This is about as wrong for /tmp as I imagine. (Well, no, I could imagine it being a file, or a named pipe -- that would work worse) Easy to fix, once diagnosed. Will report back after I have a chance to reboot. Thanks. How did you ever manage to think of this? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Wed, 02 Jan 2008 00:58:22 +, Hendrik Boom wrote: On Mon, 31 Dec 2007 09:49:43 -0800, Daniel Burrows wrote: That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR Daniel Sure looks like it. Mounting lenny's root partition on /other on my backup etch system, I get lovesong:/farhome/hendrik# ls -ld /other/tmp drwxr-xr-x 6 root root 4096 2007-12-31 10:05 /other/tmp This is about as wrong for /tmp as I imagine. (Well, no, I could imagine it being a file, or a named pipe -- that would work worse) Easy to fix, once diagnosed. Will report back after I have a chance to reboot. Thanks. How did you ever manage to think of this? -- hendrik Works like a charm now. Thanks again. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Wed, Jan 02, 2008 at 12:58:22AM +, Hendrik Boom wrote: On Mon, 31 Dec 2007 09:49:43 -0800, Daniel Burrows wrote: On Mon, Dec 31, 2007 at 03:58:03AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): INvalid argument mkdtemp: private socket dir: Permission denied That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR Daniel Sure looks like it. Mounting lenny's root partition on /other on my backup etch system, I get lovesong:/farhome/hendrik# ls -ld /other/tmp drwxr-xr-x 6 root root 4096 2007-12-31 10:05 /other/tmp This is about as wrong for /tmp as I imagine. (Well, no, I could imagine it being a file, or a named pipe -- that would work worse) Easy to fix, once diagnosed. Will report back after I have a chance to reboot. Thanks. How did you ever manage to think of this? I'm not sure how Daniel managed to think of it, but it does pop up here from time to time... just one of those things people see enough times to remember. plus mkdtemp is a pretty good clue ;) A signature.asc Description: Digital signature
Re: cannot log in with gdm after lenny upgrade
On Mon, 31 Dec 2007 03:58:03 +, Hendrik Boom wrote: The kernel I used is 2.6.18-5-486 I tried again with a more recent kernel. uname tells me 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 GNU Linux Same results. This time, though I noticed that on the first failed login attempt the line failed in listen(): Invalid argument does not appear. It does appear on subsequent attempts to login. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: cannot log in with gdm after lenny upgrade
On Mon, Dec 31, 2007 at 03:58:03AM +, Hendrik Boom [EMAIL PROTECTED] was heard to say: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): INvalid argument mkdtemp: private socket dir: Permission denied That almost sounds like you don't have write permission to $TMPDIR. Do you have any configuration that changes the value of $TMPDIR? (if you don't know about it you probably don't) What do the following commands output? ls -dl /tmp echo $TMPDIR Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cannot log in with gdm after lenny upgrade
I just upgraded my etch to lenny, using aptitude. Several runs of aptitude ofer a few days did it. Now the only package that it can't install is postfix-doc, which I suspect I don't need to worry about. I can log i as root on the alt-F! console just fine. That's when I mount the NFS volume that contains my home directory. But when I try to log in as an ordinary desktop user after gdm has been started (no, not as root, as the ordinary user hendrik which worked fine on etch before the upgrade, and still works fine when I boot my backup etch system) it iimmediately/i informs me that my session lasted less than 10 seconds, and when I ask to see the details it says: (process:8822): Gtk-Warning **: This process is currently running setuid or setgid This is not a supported use of GTK+. You must create a helper program instead. For further details, see: http://www.gtk.org/setuid.html Refusing to initialise GTK+ Then the same information for process 8826. Then: /etc/gdm/Xsession: Beginning session startup ... Setting 1M through im-switch for locale=en_CA Start IM through /farhome/hendrik/.xinput.d/en_CA linked to /etc/X11/xinit/xinput.d/uim_toolbar. failed in listen(): INvalid argument mkdtemp: private socket dir: Permission denied Now I doubt this is because I haven't successfully installed postfix-doc. It looks as if something is being started setuid/setgid which chouldn't be, but I don't know what. It further looks as if some necessary interprocess communication path is not being set up correctly, but again I don't know what. Perhaps that is related to the failure to set up the GTK+ environment. Perhaps something else is going on. The window manager I use is Icewm. But I have the same symptom with several others. Perhaps it isn't even getting that far. The kernel I used is 2.6.18-5-486 Any hints what to try? where to look? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
