Bug 459583 - unable to process non-option command line file arguments
Summary: unable to process non-option command line file arguments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: subtitleeditor
Version: 9
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 459792
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-20 12:43 UTC by Lubos Stanek
Modified: 2008-12-02 23:22 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-12-02 23:22:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lubos Stanek 2008-08-20 12:43:34 UTC
Description of problem:
The application is not able to process files passed on the command line. It is not possible to launch the application via the file context menu in Nautilus.

Version-Release number of selected component (if applicable):
0.21.3 and higher

How reproducible:
Open the supported file's context menu in Nautilus and select Open in Subtitle Editor.
Launch the application from the command line with file parameters:
subtitleeditor <supported subtitle file>

Actual results:
Application starts without opening the file passed on the command line.

Expected results:
Application opens the file passed on the command line.

Additional info:
The application uses the glibmm's OptionEntry class with the G_OPTION_REMAINING flag to collect all non-option arguments (including the proper l10n of paths).
Although it should be fixed in glibmm-2.16.2 (currently in updates for FC9), it does not work. The minimal glibmm's release supporting this feature is 2.16.3.
It would be wise to update glibmm to the latest patch release from the stable series, currently 2.16.4 for the benefit of all applications.

See: http://bugzilla.gnome.org/show_bug.cgi?id=526831

Comment 1 Martin Sourada 2008-08-20 21:33:56 UTC
Thanks for the report and additional info. I can confirm the issue.

Comment 2 Lubos Stanek 2008-12-02 23:22:07 UTC
The problem was fixed by the solution to the dependent bug report https://bugzilla.redhat.com/show_bug.cgi?id=459792.
Close it please if my permissions are not enough.


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