I don't think the authors consider this a bug.  As of 18.04, it's still
hardcoded this way.  The following is one of two essentially (for your
purposes) identical instances:

src/lxterminal.c:1252:  
  vte_terminal_fork_command_full(
                    VTE_TERMINAL(term->vte),
                    VTE_PTY_NO_LASTLOG | VTE_PTY_NO_UTMP | VTE_PTY_NO_WTMP,
                    pwd,
                    exec,
                    env,
                    G_SPAWN_SEARCH_PATH | G_SPAWN_FILE_AND_ARGV_ZERO,
                    NULL,
                    NULL,
                    &term->pid,
                    NULL);

Probably, replacing those flags with a zero in both cases would be sufficient 
for a personal system, although I haven't checked for unanticipated 
consequences.
In my opinion, they should have at least made it an option to configure. 

I did a quick test just now, of manually zeroing the argument in gdb, which 
verified that something like the following should work:
Probably something like:
#if USE_UTMP
#define LOG_UTMP VTE_PTY_NO_LASTLOG | VTE_PTY_NO_UTMP | VTE_PTY_NO_WTMP
#else 
#define LOG_UTMP 0
#endif

except it only works for root, presumably  because before the call to
the fork (or spawn) routine, there must be a setuid call that is too
early. I hope it's not in the vte library, but I doubt it, if other
terminals (such as xterm) do the right thing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201134

Title:
  LXDM logins not being logged in utmp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxdm/+bug/1201134/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to