In case someone like me comes across this discussion but the workaround
for the issue doesn't work:
Turns out that in the Profile Preferences' Command tab, if the "Run a
custom command instead of my shell" is checked, the same problem occurs,
but is likely unrelated to this bug. (Right click in t
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.sh login script
Typo: ... On the other hand, blocking update of these components until
all of them has a vte-0.38-based version released *sounds* even worse to
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
A BIG FAT WARNING ABOUT PARALLEL VTE 0.36/0.38 INSTALLS VS BRAIN-DAMAGED
PYTHON GIR:
https://bugzilla.redhat.com/show_bug.cgi?id=1114379 (especially comment
9)
Summary: Just by installing vte-0.38 (next to the already installed
vte-0.36), python apps that happily used 0.36 before will now try to
I'm not sure what 'supported' means in this context, but I guess it's
something like the core/default packages of Ubuntu (e.g. config tools,
default desktop including gnome-terminal etc.) as opposed to the
additional software (e.g. other vte-based terminals). Am I right?
I understand that the form
On Thu, Nov 06, 2014 at 09:26:54AM -, Egmont Koblinger wrote:
> Fair enough, thanks :)
This was trivial to do as you suggested so I just did it. Might as well
save people from crashers in the meantime. :)
I do want to move to 3.14, but I'm not sure if the team which decides
our 'supported' co
Fair enough, thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.sh login script
To manage notifications about this bug go to:
http
Oh, I expect us to upgrade to 3.14 ASAP. We just had 3.12 prepared for
quite some time, and as you say for 3.14 we need to upgrade vte first,
so we wanted to land this in two smaller steps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Great, thanks!
While we're at it, could you please make sure to upgrade to vte-0.36.3
and gnome-terminal-3.12.3?
Both contain important bugfixes, especially gnome-terminal-3.12.3 fixes
a nasty crash that happens relatively often.
We're talking about minor version numbers here, it should be as ea
This bug was fixed in the package gnome-terminal - 3.12.2-0ubuntu1
---
gnome-terminal (3.12.2-0ubuntu1) vivid; urgency=low
[ Iain Lane ]
* NOTE: This version changes behaviour around the "Switch to tab" keyboard
shortcuts. They are now active all the time, whereas previously t
Egmont Koblinger [2014-10-15 9:18 -]:
> I guess it's way too late for Utopic, but will make it into VV, correct?
Right. Utopic releases next week, and shipping and outdated
g-terminal is far from being release-critical. So it will land as soon
as V opens.
--
You received this bug notificati
Thanks Martin!
I guess it's way too late for Utopic, but will make it into VV, correct?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.s
Patch sent upstream (rejected though), and applied to our gnome-terminal
packaging bzr.
** Changed in: gnome-terminal (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Branch linked: lp:~ubuntu-desktop/gnome-terminal/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.sh login script
To manage noti
** Changed in: gnome-terminal
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.sh login script
To manage n
** Changed in: gnome-terminal (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing of vte.
Cheers, thanks for the research! That explains where my ~/.bashrc got
that PROMPT_COMMAND from.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132700
Title:
gnome-terminal >= 3.7 requires sourcing o
Looking at http://old-releases.ubuntu.com/ubuntu/pool/main/b/bash/, it seems
that up to bash_3.2-0 (which was shipped by Hardy 08.04 LTS) bash's
/etc/skel/.bashrc defined
PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007"'
Beginning with bash_3.2-4 (Intrepid 08.10) PROMPT_
One more thing to consider with the "fallback" approach:
If you do this, users who've manually set PROMPT_COMMAND will remain
with the old method of figuring out the cwd, including all its bugs and
limitations (not remembering symlink components, not working after sudo,
etc.) They would probably
Egmont Koblinger [2014-10-07 10:16 -]:
> Indeed it could be crucial to know if PROMPT_COMMAND was ever present in
> /etc/skel. I think it's fair game if users who have once touched their
> configs will need to touch that again.
Yes, I agree.
> OSC stands for operating system command, this is
Further discussion in the upstream bug showed a better compromise:
- Let's use vte.sh for the cases where ~/.bashrc doesn't overwrite
$PROMPT_COMMAND
- Add back cwd_from_pid() as a fallback for the other cases, to avoid
regressions.
--
You received this bug notification because you are a mem
Indeed it could be crucial to know if PROMPT_COMMAND was ever present in
/etc/skel. I think it's fair game if users who have once touched their
configs will need to touch that again.
And it's not that they'll live with something fundamentally broken until
then - it's one convenience feature that
OK, then we need to figure out the scope of how many people will likely
set $PROMPT_COMMAND in their ~/.bashrc (i. e. which older releases had
that in their /etc/skel/, or perhaps it was just added there manually).
If that's reasonably small or has never been in /etc/skel/, we can
revisit what's wr
Also, if you really hate to touch configs and love to patch binaries,
how about patching bash/zsh to automatically emit OSC 7 without any
configs or env vars? :) I know it sounds crazy first, but if you think
about it for a while, it's probably not such a brain-damaged idea after
all, is it?
--
Y
Sorry, I missed the fact that you're not a random single user, but
Ubuntu's developer finally updating gnome-terminal. I'm grateful you're
doing it and supportive of your work!
You *don't* need to modify any user's existing settings!
You need/should modify some global files under /etc, such as pr
** Summary changed:
- gnome-terminal requires sourcing of vte.sh login script -- go back to reading
/proc/pid/cwd
+ gnome-terminal >= 3.7 requires sourcing of vte.sh login script -- go back to
reading /proc/pid/cwd
--
You received this bug notification because you are a member of Ubuntu
Bugs,
26 matches
Mail list logo
