← Back to team overview

gnome-split-team team mailing list archive

[Bug 721198] Re: Exception: Failed to parse .recently-used.xbel

 

Ok, Thank you Guillaume.

-- 
You received this bug notification because you are a member of GNOME
Split developers, which is subscribed to GNOME Split.
https://bugs.launchpad.net/bugs/721198

Title:
  Exception: Failed to parse .recently-used.xbel

Status in GNOME Split - File splitter for GNOME desktop:
  In Progress

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



References