Bug 429428

Summary:	undefined symbol: nautilus_file_info_get_vfs_file_info causes crash/restart
Product:	[Fedora] Fedora	Reporter:	Tom London <selinux>
Component:	nautilus-cd-burner	Assignee:	Alexander Larsson <alexl>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	dakingun, michal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-01-28 15:23:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tom London 2008-01-19 20:39:34 UTC

Description of problem:
Running latest rawhide, attempting to use nautilus browser results in a quick
'crash' and restart of home directory.

Below is in ~/.xsession-errors:

nautilus: symbol lookup error:
/usr/lib/nautilus/extensions-2.0/libnautilus-burn-extension.so: undefined
symbol: nautilus_file_info_get_vfs_file_info
nautilus: symbol lookup error:
/usr/lib/nautilus/extensions-2.0/libnautilus-burn-extension.so: undefined
symbol: nautilus_file_info_get_vfs_file_info
nautilus: symbol lookup error:
/usr/lib/nautilus/extensions-2.0/libnautilus-burn-extension.so: undefined
symbol: nautilus_file_info_get_vfs_file_info
nautilus: symbol lookup error:
/usr/lib/nautilus/extensions-2.0/libnautilus-burn-extension.so: undefined
symbol: nautilus_file_info_get_vfs_file_info
nautilus: symbol lookup error:
/usr/lib/nautilus/extensions-2.0/libnautilus-burn-extension.so: undefined
symbol: nautilus_file_info_get_vfs_file_info



Version-Release number of selected component (if applicable):
nautilus-2.21.5-1.fc9

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Deji Akingunola 2008-01-20 03:07:21 UTC

The problem is actually with nautilus-cd-burner-2.20.0-5.fc9, reverting to
nautilus-cd-burner-2.20.0-2.fc9 'fixes' the problem.

Comment 2 Tom London 2008-01-28 15:23:19 UTC

This seems fixed with nautilus-cd-burner-2.21.5-1.fc9.i386

closing