[jaunty] Two different plugins tried to register 'NautilusBurn'.

Bug #315618 reported by Bogdan Butnaru
2
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Up-to-date Jaunty. I get the error below when I'm starting Nautilus from the console. I've no idea what's it related to.

$ nautilus
Initializing nautilus-share extension

(nautilus:23926): GLib-GObject-WARNING **: Two different plugins tried to register 'NautilusBurn'.

(nautilus:23926): GLib-GObject-CRITICAL **: g_type_add_interface_dynamic: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

(nautilus:23926): GLib-GObject-CRITICAL **: g_type_add_interface_dynamic: assertion `G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
seahorse nautilus module initialized

** (nautilus:23926): WARNING **: Unable to add monitor: Not supported

For the record, AFAIK I don't have anything special installed for burning:
$ aptitude search ~nburn~i
i libnautilus-burn4 - Nautilus Burn Library - runtime version
i nautilus-cd-burner - CD Burning front-end for Nautilus

Tags: likely-dup
Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

By the way, I noticed this when I encountered bug #315623, I don't know if it's related.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for the report, that's a known bug and should be fixed soon.

Changed in nautilus:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in nautilus:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.