gsplit don't start if recent documents are disabilited

[Nico]

the only way to disable recent documents on ubuntu that i know and i can find on internet is:

rm ~/.recently-used.xbel
mkdir ~/.recently-used.xbel

but this cause a problem with gnome-split.
this is what terminal show:

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 `~/.recently-used.xbel', but the parser failed: Error reading file '~/.recently-used.xbel': Is a directory.
 at org.gnome.gtk.GtkFileChooserButton.gtk_file_chooser_button_new(Native Method)
 at org.gnome.gtk.GtkFileChooserButton.createFileChooserButton(GtkFileChooserButton.java:41)
 at org.gnome.gtk.FileChooserButton.<init>(FileChooserButton.java:57)
 at org.gnome.split.gtk.widget.SplitWidget.<init>(SplitWidget.java:147)
 at org.gnome.split.gtk.MainWindow.<init>(MainWindow.java:151)
 at org.gnome.split.GnomeSplit.<init>(GnomeSplit.java:142)
 at org.gnome.split.GnomeSplit.main(GnomeSplit.java:229)

i think that the program need to not crash only for not find a file.

i hope to be helpfull

sorry for my bad english

[Guillaume Mazoyer (respawneral)]

Hello Nico,

It's actually not a GNOME Split bug. When you use this:

mkdir ~/.recently-used.xbel

You are creating a directory right? But ".recently-used.xbel" *must* be a file (not a directory).
Also, if you use :

touch ~/.recently-used.xbel

The file will be empty and GNOME Split will crash too.

To avoid this, you can just remove the file :

rm ~/.recently-used.xbel*

And then GNOME Split will start. As I already said, it is not a GNOME Split bug. But, it can be a java-gnome bug or even a glib / gtk bug (but I don't think so). So, I will report it as a java-gnome bug and will see how will it go.

[Guillaume Mazoyer (respawneral)]

I confirmed that it is a java-gnome bug.
A program using GTK in C will never crash in the cases that we discovered.

When the file is actually a directory, just a GtkWarning occurs and it should not crash the program. So I will report this problem as a java-gnome bug.