This bug was fixed in the package bash - 5.2.37-2ubuntu4
---
bash (5.2.37-2ubuntu4) questing; urgency=medium
* /etc/bash.bashrc: Explicitly source /etc/profile.d/vte*.sh, and
sync the color prompt setting from /etc/skel/.bashrc.
-- Matthias Klose Mon, 16 Jun 2025 19:54:28 +0
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notifications about this bug go to:
https://bugs.launchp
I confirm that that /etc/bash.bashrc does what I need. Thank you!
** Tags removed: block-proposed
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs
this needs more syncing with the skeleton bashrc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notifications about this bug
** Patch added: "bashrc.diff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2083705/+attachment/5883610/+files/bashrc.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New
this is what I'm currently testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notifications about this bug go to:
https:
When there is a conflict between what different people want for a
package but there is a team that is the bug owner for MIR purposes, then
it seems clear to me that the team gets to make the final decision.
https://launchpad.net/ubuntu/+source/bash is the responsibility of
Debcrafters Packages.
S
I don't mind having this mechanism work, however it should be an opt-in,
not an opt-out. The system-provided bashrc scripts should be minimal,
not including any bells and whistles. Even bash-completion alone changes
the shell in such an intrusive way, that it's not suitable for every
user. Opt-in
** Changed in: bash (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notifications abou
There is another explanation of the problem in
https://bugs.debian.org/1083281
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manag
Matthias, I spoke to you in person in Frankfurt in early November 2024 about
this issue. At your request, I emailed you later in November about it with the
subject line "reconsider bash sourcing for non-login interactive shells". I
never heard back from you. I replied to the email in January. Wh
** Tags added: block-proposed questing
** Changed in: bash (Ubuntu)
Status: Opinion => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current wor
** Changed in: bash (Ubuntu)
Status: Fix Committed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notifica
and your comment is very misleading ...
+# Source profile.d even though "it's meant to be for login shells
+# only", because we need a hook integration for
+# e.g. command-not-found, bash-completion, gnome-terminal/vte,
+# screen/byobu etc. And e.g. on fedora systems, bashrc does source
+# profile
I don't think this is a good thing. Please revert that, or at least
leave it there commented out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working
** Package changed: ptyxis (Ubuntu) => bash (Ubuntu)
** Changed in: bash (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: bash (Ubuntu)
Assignee: (unassigned) => Jeremy Bícha (jbicha)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Yes, the bash fix will also fix gnome-console and I believe tilix
automatically.
The root Debian bug is more than a decade old and the fix was briefly
landed once in Ubuntu development (as a kind of Non Maintainer Upload)
before being reverted by the then Debian/Ubuntu bash maintainer.
--
You re
This workaround is the same as one has to do for tilix.
=> https://gnunn1.github.io/tilix-web/manual/vteconfig/
When fixing this to unblock ptyxis could you please consider doing so in
a way fixing that as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ptyxis (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083705
Title:
New tabs don't open in current working directory
To manage notificati
19 matches
Mail list logo
