unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 6302@debbugs.gnu.org
Subject: bug#6302: 24.0.50; Unable to use su in term.
Date: Thu, 10 Jun 2010 09:17:37 +0200	[thread overview]
Message-ID: <87wru74ar2.fsf@tux.homenetwork> (raw)
In-Reply-To: <66eigflbj0.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 10 Jun 2010 01:08:51 -0400")

Glenn Morris <rgm@gnu.org> writes:

> Thierry Volpiatto wrote:
>
>>>    thierry@tux ~ $ su -l
>> Fail. (same with --login and -)
>>
>> So it's clear that come from the -l option of su.
>
> Is there anything odd in root's ~/.bash_profile (or whatever the
> appropriate config file for root login shells is)?
I have no .bash* files in /root.

> Does it work to su -l to a non-root user?
I have not such user, only me and root, so i can't test.
I could create a new user just for test purpose, but i think it's not
useful, if it was a problem related to general config of my system,
other shell would not work, but it is not the case, M-x shell and eshell
can su ==> root without problems.

> One with no shell config files?
>
> Can you put some debug statements in the shell config files to find
> out if they get sourced at all? If so, where do things go wrong?
Yes, .bashrc and .bash_profile are sourced.

>>> Also, can you M-x trace-function-background RET term-emulate-terminal
>>> RET, reproduce the problem and then show us the *trace-output*?
>> I can't find function `term-emulate-terminal'.
>
> ? It's in term.el.
Ok i have it now.

,----
| ======================================================================
| 1 -> term-emulate-terminal: proc=#<process *ansi-term*> str="Password: "
| 1 <- term-emulate-terminal: t
| ======================================================================
| 1 -> term-emulate-terminal: proc=#<process *ansi-term*> str="
| "
| 1 <- term-emulate-terminal: t
| ======================================================================
| 1 -> term-emulate-terminal: proc=#<process *ansi-term*> str="\x1a//home/thierry
| ^[[01;32mthierry@tux^[[01;34m ~ $^[[00m "
| 1 <- term-emulate-terminal: t
| ======================================================================
`----


-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/





  reply	other threads:[~2010-06-10  7:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-29  5:24 bug#6302: 24.0.50; Unable to use su in term Thierry Volpiatto
2010-06-03 22:46 ` Glenn Morris
2010-06-04  7:33   ` Thierry Volpiatto
2010-06-04 13:35     ` Stefan Monnier
2010-06-04 14:53       ` Thierry Volpiatto
2010-06-10  5:08         ` Glenn Morris
2010-06-10  7:17           ` Thierry Volpiatto [this message]
2010-06-10  9:05           ` Thierry Volpiatto
2011-09-18 10:20         ` bug#5300: " Lars Magne Ingebrigtsen
2011-09-18 17:53           ` Thierry Volpiatto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wru74ar2.fsf@tux.homenetwork \
    --to=thierry.volpiatto@gmail.com \
    --cc=6302@debbugs.gnu.org \
    --cc=rgm@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).