nautilus-filename-repairer doesn't do anything

Bug #410818 reported by Max Harmathy
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus-filename-repairer (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: nautilus-filename-repairer

I installed the nautilus-filename-repairer (0.0.5-1) and after loging out and in again the respective menu entry appears for corrupted file names (see attached screenshot). But clicking the entry doesn't seem to have any effect.

Revision history for this message
Max Harmathy (max-harmathy) wrote :
summary: - nautilus-filename-repairer doensn't do anything
+ nautilus-filename-repairer doesn't do anything
Revision history for this message
Nighty (nighty) wrote :

Verified on my machine. This is what nautilus spews on the commandline when I try to rename such a file or directory:

(nautilus:31298): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed

(nautilus:31298): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?

(nautilus:31298): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed

(nautilus:31298): libgnomevfs-WARNING **: Internal error: the configuration system was not initialized. Did you call _gnome_vfs_configuration_init?

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_uri_append_file_name: assertion `uri != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_get_file_info_uri_cancellable: assertion `uri != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_move_uri_cancellable: assertion `old != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed

(nautilus:31298): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed

Revision history for this message
Nighty (nighty) wrote :

Fixed on my machine; gnome_vfs_init was not called on module initialization. See attachment for the patch.

Works correctly now as far as I can tell.

Revision history for this message
Choe Hwanjin (choe-hwanjin) wrote :

The cause of this problem is that nautilus does not use Gnome VFS anymore.
So the nautilus-filename-repairer should use GIO instead.

This problem will be fixed on next release.
See this issue:
http://code.google.com/p/repairer/issues/detail?id=1

Revision history for this message
Choe Hwanjin (choe-hwanjin) wrote :

nautilus-filename-repairer 0.0.6 has been released.

Now you can download new version here:
http://code.google.com/p/repairer/downloads/list

Revision history for this message
Artur Rona (ari-tczew) wrote :

This bug has been fixed in 0.0.6, right?

Revision history for this message
Choe Hwanjin (choe-hwanjin) wrote :

Yes. 0.0.6 use gio instead of Gnome VFS.
Now it works.

Revision history for this message
Artur Rona (ari-tczew) wrote :

nautilus-filename-repairer (0.0.6-1) unstable; urgency=low

  * New Upstream Version (Closes: #559623)
  * New upstream project homepage (Closes: #559456)
  * Standards-Version: 3.8.3
 -- Ubuntu Archive Auto-Sync <email address hidden> Mon, 01 Feb 2010 23:59:50 +0000

Changed in nautilus-filename-repairer (Ubuntu):
status: New → Fix Released
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.