Tomboy crash on deleting a note

Bug #566066 reported by Natim
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomboy (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: tomboy

When I delete a note, tomboy crash. It shouldn't crash, more over, it should explain that "Access to the path is denied" and also witch one !

How to solve it ?

Catch the System.Reflection.TargetInvocationException in the Tomboy.NoteManager.Delete method and display an error message with the absolute path from which the access is denied.

Here is the traceback :

[INFO]: Initializing Mono.Addins
Marshaling clicked signal
Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.UnauthorizedAccessException: Access to the path is denied.
  at System.IO.File.Move (System.String sourceFileName, System.String destFileName) [0x00000]
  at Tomboy.NoteManager.Delete (Tomboy.Note note) [0x00000]
  at Tomboy.NoteUtils.ShowDeletionDialog (System.Collections.Generic.List`1 notes, Gtk.Window parent) [0x00000]
  at Tomboy.NoteWindow.OnDeleteButtonClicked (System.Object sender, System.EventArgs args) [0x00000]
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000]
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000]
  at System.Delegate.DynamicInvokeImpl (System.Object[] args) [0x00000]
  at System.MulticastDelegate.DynamicInvokeImpl (System.Object[] args) [0x00000]
  at System.Delegate.DynamicInvoke (System.Object[] args) [0x00000]
  at GLib.Signal.ClosureInvokedCB (System.Object o, GLib.ClosureInvokedArgs args) [0x00000]
  at GLib.SignalClosure.Invoke (GLib.ClosureInvokedArgs args) [0x00000]
  at GLib.SignalClosure.MarshalCallback (IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data) [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Gnome.Program.Run()
   at Tomboy.GnomeApplication.StartMainLoop()
   at Tomboy.Application.StartMainLoop()
   at Tomboy.Tomboy.StartTrayIcon()
   at Tomboy.Tomboy.Main(System.String[] args)

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: tomboy 1.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 18 18:25:57 2010
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: tomboy

Revision history for this message
Natim (site-remy) wrote :
Revision history for this message
Natim (site-remy) wrote :

One way of fixing this bug, was to

sudo chown ${USER}:${USER} -R ~/.local/share/tomboy/

Revision history for this message
Sandy Armstrong (sanfordarmstrong) wrote :

Why did you not own your note files? Had you copied your notes over from another system and not made sure you had write permissions on them?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in tomboy (Ubuntu):
status: New → Confirmed
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.