Ticket #64 (closed Defect: fixed)

Opened 7 months ago

Last modified 3 months ago

"=false: not a valid identifier" gets outputed in bash login after autopackage installation

Reported by: isak Assigned to: taj
Priority: Medium Milestone: 1.2.5
Component: main Version: 1.2.4
Severity: Normal Keywords: bash-paths
Cc:

Description

Something is wrong with _updateBashEnv() which causes it to sometimes add the following to ~/.config/autopackage/paths-bash: 

__autopackage_addBashPath ""  false

The empty string as first argument gets chewed by bash, and it'll just see "export =false", resulting in the error message in the summary.

Attachments

bashenv.patch (474 bytes) - added by Jan-Nik on 04/01/08 13:07:14.
checks if the really starts with "P"

Change History

04/01/08 13:07:14 changed by Jan-Nik

  • attachment bashenv.patch added.

checks if the really starts with "P"

04/01/08 13:08:39 changed by Jan-Nik

I think the only way this could happen is, if there's a empty line inside "paths". The empty line will not be ignored, instead handled as an line starting with "P".

I could be wrong, don't know about bash and this function at all.

(I wanted to say "the line" in the comment to my patch)

04/20/08 08:24:37 changed by isak

  • status changed from new to closed.
  • resolution set to fixed.

Thanks. This should take care of it. Committed in r2439