Exception: Failed to parse .recently-used.xbel

Bug #721198 reported by Manu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Split
In Progress
Low
Guillaume Mazoyer

Bug Description

As I don't want an recent files history on my box, I changed ~/.recently-used.xbel to a directory:

drw------- 2 manu manu 4096 2010-09-09 12:21 .recently-used.xbel

see here: http://ubuntuforums.org/showthread.php?t=375510

Gnome-split crashes at startup with this exception:

 DANGER: Gtk-WARNING, Attempting to read the recently used resources file at `/home/manu/.recently-used.xbel', but the parser failed: Erreur de lecture du fichier « /home/manu/.recently-used.xbel » : est un dossier.
UncaughtException in thread: main
  Thread ID = 1
  Thread prority = 5
Exception stacktrace:
org.gnome.glib.FatalError: Gtk-WARNING
Attempting to read the recently used resources file at `/home/manu/.recently-used.xbel', but the parser failed: Erreur de lecture du fichier « /home/manu/.recently-used.xbel » : est un dossier.
        at org.gnome.gtk.GtkFileChooserButton.gtk_file_chooser_button_new(Native Method)
        at org.gnome.gtk.GtkFileChooserButton.createFileChooserButton(GtkFileChooserButton.java:64)
        at org.gnome.gtk.FileChooserButton.<init>(FileChooserButton.java:78)
        at org.gnome.split.gtk.widget.SplitWidget.<init>(SplitWidget.java:137)
        at org.gnome.split.gtk.MainWindow.<init>(MainWindow.java:187)
        at org.gnome.split.GnomeSplit.buildUserInterface(GnomeSplit.java:182)
        at org.gnome.split.GnomeSplit.<init>(GnomeSplit.java:113)
        at org.gnome.split.GnomeSplit.main(GnomeSplit.java:334)

[1]+ Exit 1 gnome-split

IMHO accessing recent files is not a must have and the exception should be handled

Thanks

Revision history for this message
Guillaume Mazoyer (respawneral) wrote :

I agree with you. Someone already report such a bug.
The problem is due to the way that java-gnome is handling warning from the gtk+ native library.

In few words, java-gnome considers as an error the warning of gtk+.
Is it a wrong behavior? I don't know but it should be discussed.

The problem would not appear if this long time bug would have been resolved.
https://bugzilla.gnome.org/show_bug.cgi?id=305325

Revision history for this message
Manu (manubing) wrote :

Hi Guillaume,

Thanks for your feedback and links to java-gnome issue.

I fully understand the problem caused by the handling of this error, but in the meantime there should be a way to catch this exception upfront in GnomeSplit, no?

Manu

Revision history for this message
Guillaume Mazoyer (respawneral) wrote :

There is probably a way to catch that exception yes.
I'm going to work on it and do a bug fix release when this bug will be in the world of death.

Changed in gnome-split:
status: New → Confirmed
importance: Undecided → Low
assignee: nobody → Guillaume Mazoyer (respawneral)
status: Confirmed → In Progress
Revision history for this message
Manu (manubing) wrote :

Ok, Thank you Guillaume.

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.