After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595098 - Crash when opening "Search All Notes" window [applet only]
Crash when opening "Search All Notes" window [applet only]
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
0.15.x
Other Linux
: Normal critical
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-13 20:45 UTC by Seán de Búrca
Modified: 2009-09-14 17:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Seán de Búrca 2009-09-13 20:45:57 UTC
Attempting to open the "Search All Notes" window from the applet's menu causes the applet to die. Using the CLI, running `tomboy --search' or `tomboy --search foo' prints out the following error message and nothing else happens:

Unhandled Exception: System.Exception: System.NullReferenceException: Object reference not set to an instance of an object

Server stack trace: 


Exception rethrown at [0]: 

  at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke (System.Runtime.Remoting.Proxies.RealProxy rp, IMessage msg, System.Exception& exc, System.Object[]& out_args) [0x00000]
Comment 1 Sandy Armstrong 2009-09-14 12:36:41 UTC
What distro are you on?  What kind of processor?  What version of Tomboy?

Do you also get the crash if you start Tomboy without --search, and try to open the dialog?

If so, please do the following:

1. Run `tomboy --debug &> output.txt` from the CLI (do not use --search)
2. Open the Search dialog (presumably, Tomboy will crash at this point)
3. Attach output.txt to this bug

If you can do this within the next few hours that would be great, as today is code freeze.
Comment 2 Seán de Búrca 2009-09-14 15:15:43 UTC
I'm on Ubuntu, using a 64-bit processor (Intel Core 2 Duo) and using tomboy-0.15.7-0ubuntu1. The patches applied to this version are at the end of the file at http://archive.ubuntu.com/ubuntu/pool/main/t/tomboy/tomboy_0.15.7-0ubuntu1.diff.gz

I do not get a crash starting Tomboy without --search. However, I do not get the crash if the panel applet is not running and I run `tomboy --search'. If it is, I get the crash both at the CLI and through the applet menu. Running `tomboy' from the CLI, I get it neither at the CLI or through the tray icon menu.
Comment 3 Sandy Armstrong 2009-09-14 15:19:22 UTC
Thanks for the details.

If you start `tomboy --debug` in one CLI, and then `tomboy --search` in the other CLI (after Tomboy has started in the other CLI), do you get a crash?  If so, I would like the output from both please. :-)
Comment 4 Seán de Búrca 2009-09-14 16:09:41 UTC
No crash in that situation.
Comment 5 Sandy Armstrong 2009-09-14 17:09:43 UTC
Okay, I misunderstood you earlier, and I am able to reproduce this bug now:

1. Add Tomboy to panel
2. Try to open Search window (either via shortcut key, or Tomboy menu, or `tomboy --search`)

Expected results:

Search window appears

Actual results:

Tomboy crashes
Comment 6 Sandy Armstrong 2009-09-14 17:11:28 UTC
Here's the important part of the stack trace (achieved by hacking /usr/bin/tomboy-panel a bit...I should do that for realz):

Marshaling activate 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 ta
rget of an invocation. ---> System.NullReferenceException: Object reference not 
set to an instance of an object
  at Tomboy.Tomboy.get_TrayIconShowing () [0x00000] 
  at Tomboy.NoteRecentChanges.CreateMenuBar () [0x00000] 
  at Tomboy.NoteRecentChanges..ctor (Tomboy.NoteManager manager) [0x00000] 
  at Tomboy.NoteRecentChanges.GetInstance (Tomboy.NoteManager manager) [0x00000]
 
  at Tomboy.Tomboy.OpenSearchAll (System.Object sender, System.EventArgs args) [
0x00000]
Comment 7 Sandy Armstrong 2009-09-14 17:13:18 UTC
Easy fix coming, so glad you caught this in time!  What an embarrassing mistake! :-)
Comment 8 Sandy Armstrong 2009-09-14 17:20:52 UTC
Fixed in master.