Bug 251823 - x11/xfce4-terminal does not want to start a login shell
Summary: x11/xfce4-terminal does not want to start a login shell
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-xfce (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-13 21:03 UTC by Per Gunnarsson
Modified: 2021-02-14 20:51 UTC (History)
1 user (show)

See Also:
madpilot: maintainer-feedback+


Attachments
shell configuration file, (1.03 KB, text/plain)
2020-12-15 21:31 UTC, Per Gunnarsson
no flags Details
bash_profile. (4.15 KB, text/plain)
2020-12-15 21:32 UTC, Per Gunnarsson
no flags Details
bashrc (1.72 KB, text/plain)
2020-12-15 21:34 UTC, Per Gunnarsson
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Per Gunnarsson 2020-12-13 21:03:20 UTC
Maybe there is some daisy chaining in my ~/.bashrc and my ~/.bash_profile, but they worked until recently.

Link to movie with the behavious:

https://mustafejen.se/~per/video/oddshell.mkv

Using bash -l changes nothing in xfce4-terminal, but a regular xterm seems to go back to what I consider normal after typing bash -l.
Comment 1 Guido Falsi freebsd_committer 2020-12-15 17:21:45 UTC
This is a strange thing. Not easy to debug.

My first guess is you're doing some ansi/terminal sequence magic in you bash configuration that confuses terminals and in some way confuses xfce terminal more than xterm.

Anyway it does confuse xterm too, the "bash -l" trick is just a< workaround that happens to work there.

I'm not sure I can help you much, because I'm no terminal sequence expert and don't know much about bash peculiarities.

Could you share your bashrc and profile? Without looking at what they are doing it's difficult to guess what the problem is.

Also "working till recently" does not help much. bash has got a few updates recently too. It can't be ruled out an update to bash is the cause of the issue appearing.
Comment 2 Per Gunnarsson 2020-12-15 21:31:58 UTC
Created attachment 220593 [details]
shell configuration file,

my .profile
Comment 3 Per Gunnarsson 2020-12-15 21:32:55 UTC
Created attachment 220594 [details]
bash_profile.
Comment 4 Per Gunnarsson 2020-12-15 21:34:41 UTC
Created attachment 220595 [details]
bashrc
Comment 5 Per Gunnarsson 2020-12-15 21:39:45 UTC
(In reply to Guido Falsi from comment #1)

I removed a lot of things from my  ~/.bash_profile and ~/.bashrc, now things work as expected. Still I attach the unmodified bad examples.
Comment 6 Guido Falsi freebsd_committer 2021-02-14 20:51:55 UTC
Can this issue be closed?

While there may be a bug crawling around, it could also be an error in these, relatively complicated, configuration files.

To really assert this as an upstream bug a simple use case would be required.