Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157416 - undefined symbol: sn_launchee_context_get_id_has_timestamp
Summary: undefined symbol: sn_launchee_context_get_id_has_timestamp
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus
Version: 4
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-11 14:29 UTC by Thilo Pfennig
Modified: 2013-03-06 03:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-11 18:58:39 UTC


Attachments (Terms of Use)

Description Thilo Pfennig 2005-05-11 14:29:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Fedora/1.0.3-1.3.1 Firefox/1.0.3

Description of problem:
The new nautilus does not start up. With:

"nautilus: symbol lookup error: nautilus: undefined symbol: sn_launchee_context_get_id_has_timestamp"


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

How reproducible:
Always

Steps to Reproduce:
1. execute nautilus

  

Actual Results:  nautilus: symbol lookup error: nautilus: undefined symbol: sn_launchee_context_get_id_has_timestamp


Expected Results:  nautilus starts up.

Additional info:

I have not updated all packages of GNOME2.8/FC3 to the new versions. But if that should be a problem, nautilus should depend.

Comment 1 Thilo Pfennig 2005-05-11 18:30:07 UTC
I have resolved it. Nautilus seems to need a newer packages of
"startup-notification". I now have "startup-notification-0.8-2". Now Nautilus works.

Comment 2 David Zeuthen 2005-05-11 18:58:39 UTC
Great it works. Closing this bug.


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