Gnome-Do doesn't start when a deleted symlink in present in the Trash

[Carroarmato0]

Binary package hint: gnome-do

Gnome-Do fails to start when there is a deleted symlink that has been moved to the Trashbin.

The symlink was simply created with the ln -s command. Afterwards, that link was deleted through Nautilus and thus was moved to the TrashBin.

Gnome-Do apparently checks what's inside the Trashbin when starting, probably paniced about the broken link and exited with an exception.

A workaround is to manually delete the broken symlink from the Trashbin.

ProblemType: Bug
Architecture: amd64
Date: Fri Nov 6 12:42:50 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: wl nvidia
Package: gnome-do 0.8.2+dfsg-1
ProcEnviron:
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gnome-do
Uname: Linux 2.6.31-14-generic x86_64

[Robert Dyer (psybers)]

Thank you for your bug report. When you have a crash, please try your best to always include any stack trace/terminal output in your crash report. Please re-run Do with the '--debug' flag from the terminal and include the output here.

[Carroarmato0 (carroarmato0)]

To repeat:

I created the symbolic link with the command " ln -s School/ /home/christophe/Ubuntu\ One/School "

What I'm doing is making a symbolic link of a directory, and then deleting that directory which is then moved to the Trash.

[Robert Dyer (psybers)]

Thank you for the stack trace. That crash appears to be a bug with Mono and not with GNOME Do. Can you please re-file this bug upstream with Mono?

[Carroarmato0 (carroarmato0)]

Should I point the Mono developers (in the bug report) to this one so they can see a user case?

[Chris S. (cszikszoy)]

Yes. That would most likely be helpful for them.

[Carroarmato0 (carroarmato0)]

Description of Problem:

It is suggested by a core developer of Gnome-Do (a program written with Mono) that there is a bug in Mono that causes an IO exception when encountering a broken symbolic link.

The initial bug report was made on Launchpad because the bug was encountered in Ubuntu.

The link to the bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/476402

The debugging dump that the specific program gave can be found here: http://launchpadlibrarian.net/35270262/debug.txt

The interesting part of the debug file is this:

Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.IO.IOException: Win32 IO returned ERROR_NO_MORE_FILES. Path: /home/christophe/.local/share/Trash/files
  at System.IO.Directory.GetFileSystemEntries (System.String path, System.String searchPattern, FileAttributes mask, FileAttributes attrs) [0x00000]
  at System.IO.Directory.GetFiles (System.String path, System.String searchPattern) [0x00000]
  at System.IO.Directory.GetFiles (System.String path) [0x00000]
  at Docky.Interface.TrashDockItem.get_Icon () [0x00000]
  at Docky.Interface.AbstractDockItem.GetSurfacePixbuf (Int32 size) [0x00000]
  at Docky.Interface.AbstractDockItem.MakeIconSurface (Cairo.Surface similar, Int32 size) [0x00000]
  at Docky.Interface.AbstractDockItem.GetIconSurface (Cairo.Surface similar, Int32 targetSize, System.Int32& actualSize) [0x00000]
  at Docky.Interface.DockArea.DrawIcon (Cairo.Context cr, Int32 icon, Boolean hovered) [0x00000]
  at Docky.Interface.DockArea.DrawIcons (Cairo.Context cr, Rectangle dockArea) [0x00000]
  at Docky.Interface.DockArea.DrawDock (Cairo.Context cr) [0x00000]
  at Docky.Interface.DockArea.OnExposeEvent (Gdk.EventExpose evnt) [0x00000]
  at Gtk.Widget.exposeevent_cb (IntPtr widget, IntPtr evnt) [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Do.Do.Main(System.String[] args)
Cairo.Context: called from finalization thread, programmer is missing a call to Dispose

[Carroarmato0 (carroarmato0)]

The bug report sent to Novell is this https://bugzilla.novell.com/show_bug.cgi?id=553603