Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#25304 - [gvim]desktop file changes breaks mime-type linkage

Attached to Project: Arch Linux
Opened by Ng Oon-Ee (ngoonee) - Friday, 29 July 2011, 05:22 GMT
Last edited by Eric Belanger (Snowman) - Monday, 22 August 2011, 05:34 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


After upgrading (using [testing]) to the latest version of gvim/vim-runtime my *.tex files which previously opened with gvim started opening in firefox instead. After comparing versions, I realize the file gvim.desktop has changed drastically, but only one line actually caused the behaviour I was seeing. Removing 'Terminal=0' from gvim.desktop fixed it. I use a command-line file browser (ranger), hence gvim could not be launched from it.

I suspect the desktop file came from upstream (though its included in our package and not downloaded from elsewhere). Could I request removal of the above line, or do I need to go upstream?

Additional info:
* package version(s)
From gvim/vim-runtime 7.3.206-1 to gvim/vim-runtime 7.3.266-1
This task depends upon

Closed by  Eric Belanger (Snowman)
Monday, 22 August 2011, 05:34 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#25694 
Comment by Eric Belanger (Snowman) - Sunday, 21 August 2011, 13:05 GMT
Does it work if you replace:
Comment by Ng Oon-Ee (ngoonee) - Monday, 22 August 2011, 03:45 GMT
Yes it does.
Comment by Eric Belanger (Snowman) - Monday, 22 August 2011, 04:05 GMT
I already made the change in trunk ( FS#25694 ). I'm not sure if it's worth rebuilding the package for this, especially that it's a split package.
Comment by Ng Oon-Ee (ngoonee) - Monday, 22 August 2011, 05:06 GMT
I concur that not many would be affected, since this does not affect GUI filemanagers. No objection (from me) to leaving this till the next necessary rebuild (or update, whichever comes sooner). Thanks much.