Bug 638644 - brasero fails to start, says: "brasero: symbol lookup error: brasero: undefined symbol: g_application_new"
Summary: brasero fails to start, says: "brasero: symbol lookup error: brasero: undefin...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: brasero
Version: 14
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-29 15:02 UTC by Richard W.M. Jones
Modified: 2012-08-16 19:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 19:01:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2010-09-29 15:02:35 UTC
Description of problem:

While trying to fix bug 631987 I updated glib2 package and now
brasero won't start at all.  It says:


$ brasero 
Gtk-Message: Failed to load module "atk-bridge": libatk-bridge.so: cannot open shared object file: No such file or directory

(brasero:3884): Bonobo-WARNING **: Bonobo must be initialized before use
brasero: symbol lookup error: brasero: undefined symbol: g_application_new

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

brasero-2.31.91-1.fc14.x86_64
gtk2-2.21.7-1.fc14.x86_64
glib2-2.26.0-1.fc14.x86_64

How reproducible:

Always.

Steps to Reproduce:
1. Try to start brasero.
2.
3.

Comment 1 Piotr Wierzbicki 2010-10-02 21:29:53 UTC
g_application_new has been deprecated in glib2 (as of 2.26?)

Comment 2 Aron Parsons 2010-10-04 17:28:43 UTC
brasero won't start for me either with the same error message.

glib2-2.26.0-2.fc14.x86_64
brasero-2.31.91-1.fc14.x86_64

Comment 3 Fedora End Of Life 2012-08-16 19:01:21 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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