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 503165 - Tomboy inappropriately calls Debug.Assert in Note Class
Tomboy inappropriately calls Debug.Assert in Note Class
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
unspecified
Other All
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-12 01:37 UTC by Thomas Wiest
Modified: 2008-02-26 20:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Thomas Wiest 2007-12-12 01:37:09 UTC
Please describe the problem:
Aaron Bockover discovered that:
"In Tomboy's Note class [1], it has a method called SetPositionExtent in
which it calls Debug.Assert twice. In Mono < 1.2.6, this appeared to
cause no problems. However, in 1.2.6, some code was added to
System.Diagnostics.DefaultTraceListener to support AssertUiEnabled.

"This means that any time Tomboy has a note visible and you switch
virtual desktops, DefaultTraceListener will effectively show a MWF
dialog box, blocking Tomboy's main loop until the user clicks "Ignore."
Worse yet, the user may click "Abort," terminating Tomboy. 

"Debug.Assert is used in a few other places in Tomboy as well."

This only seems to happen when Tomboy is running on Compiz.

We have temporarily disabled popping up the MWF Gui in Mono >1.2.6p5, but we will be re-enabling this type of functionality in 1.2.7 (probably using GTK# when appropriate). This should really be fixed in Tomboy though.

The mono bug can be tracked here:
https://bugzilla.novell.com/show_bug.cgi?id=347812

Steps to reproduce:
1. Run Tomboy on Mono 1.2.6p1 - 1.2.6p4, or on > 1.2.7
2. Make sure Tomboy is running on Compiz
3. Open a note
4. Switch to another virtual desktop
5. Notice the Debug.Assert GUI window


Actual results:
The Debug.Assert GUI window

Expected results:
Nothing

Does this happen every time?
almost every time

Other information:
Comment 1 Kevin Kubasik 2008-02-06 15:10:33 UTC
This seems perfectly valid, we should do this right.
Comment 2 Boyd Timothy 2008-02-17 00:08:23 UTC
Thanks for the report!  Fixed in SVN r1857.