Bug 1265143 - avidemux3_gtk Glade Cannot load glade file
Summary: avidemux3_gtk Glade Cannot load glade file
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: glade
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 08:26 UTC by redhat
Modified: 2016-07-19 17:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 17:58:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description redhat 2015-09-22 08:26:50 UTC
Description of problem:
Starting the avidemux program crashes immediatly with the errormessage 
"Glade

Cannot load glade file"

Version-Release number of selected component (if applicable):
Name        : avidemux
Arch        : x86_64
Epoch       : 0
Version     : 2.6.8
Release     : 3.fc22
Größe       : 18 k
Paketquelle : @System


How reproducible:
Always.

Steps to Reproduce:
1. sudo dnf install avidemux
2. avidemux3_gtk

Actual results:
Crash with gui error message

Expected results:
Starting avidemux program

Additional info:
Output of STDOUT when starting in a terminal:
http://fpaste.org/270007/09962144/

Component avidemux was not available. Used glade instead. Please reassign to what is applicable.

Comment 1 Fedora End Of Life 2016-07-19 17:58:58 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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