Bug 26261 - tcsh: undefined variable VTE_VERSION at startup prior to executing .cshrc
Summary: tcsh: undefined variable VTE_VERSION at startup prior to executing .cshrc
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-26 18:33 CET by Ralf Brown
Modified: 2020-04-10 20:01 CEST (History)
2 users (show)

See Also:
Source RPM: vte3-profile-0.59.91-2.mga8
CVE:
Status comment:


Attachments

Description Ralf Brown 2020-02-26 18:33:09 CET
Description of problem:
After system update, every invocation of tcsh prints error message "VTE_VERSION: Undefined variable." and then fails to execute ~/.cshrc.  I've traced the problem to /etc/profile.d/vte.csh

Version-Release number of selected component (if applicable):
0.59.91-2.mga8

How reproducible:
Run tcsh in a terminal window or from a commandline login.

Steps to Reproduce:
1. tcsh
2. observe the error message and lack of effects from user .cshrc

Fix: add a test for the existence of $VTE_VERSION to /etc/profile.d/vte.csh
Note that I tried adding the test in the existing 'if' statement, but that still left the error, so I had to split it into two.

--- /etc/profile.d/vte.csh~     2020-02-26 12:06:39.904818401 -0500
+++ /etc/profile.d/vte.csh      2020-02-26 12:07:38.970079983 -0500
@@ -18,3 +18,4 @@
 # exit if non-interactive, csh, no terminal or old VTE versions
-if ( ! $?prompt | ! $?tcsh | ! $?TERM | 0$VTE_VERSION < 3405) exit
+if ( ! $?prompt | ! $?tcsh | ! $?TERM | ! $?VTE_VERSION ) exit
+if ( 0$VTE_VERSION < 3405) exit
Comment 1 David GEIGER 2020-02-26 18:57:05 CET
This should be reported upstream at: https://gitlab.gnome.org/GNOME/vte

CC: (none) => geiger.david68210
Assignee: bugsquad => gnome

Comment 2 Olav Vitters 2020-04-10 20:01:24 CEST
Seems this was fixed at some time, guessing by upstream.

CC: (none) => olav
Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.