Menu
▾
▴
#80 Segmentation fault when editing time in Activity dialog
Frequently while editing time intervals in the "GnoTime: Journal" dialog that pops up when you right-click a project and click "Activity", the process exits due to segmentation fault. Today I ran gnotime from the command line so I'd be able to see the output and managed to catch this happening. I'm still not sure what exactly I did that caused this, but I'm starting to think it has something to do with accidentally right-clicking where I shouldn't and then modifying a time interval. Here is the last bit of output that I got before the crash:
(gnotime:2545): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GnomeDateEdit'
Segmentation fault
I'm hoping this is enough for someone to identify the root cause. If not, please let me know what I can do to provide better debug info.
Using:
Ubuntu 10.04 LTS (Lucid Lynx)
libgtk2.0-0 2.20.1-0ubuntu2
Linux kernel: 2.6.32-32-generic
Tried to reproduce this in a fresh installation of Lucid Lynx but everything worked fine.
Are you able to reproduce this with a clean data file? If not, can you send me your data file so I can try to debug it?
You can send the data file to goedson@debian.org, if needed.
Sorry this took so long, but I GOT IT!
Here is a consistently reproducible set of simulation steps that work every time on my system:
1) Activity
In the main tracker window, right click any task with existing time data and click "Activity" to bring up the Journal window for that task.
2) Edit Interval (or New Interval)
Click a time interval and click "Edit Interval" or "New Interval"
3) ESC (or ALT-F4, or click X in title bar)
Press the ESC key to close the interval window, or press ALT-F4 or click the X icon to the left of the title bar (can not reproduce issue by clicking "Cancel".)
4) Edit Interval (or New Interval)
Repeat step 2: Click a time interval and click "Edit Interval" or "New Interval"
The process aborts and the following output is displayed if started from the command line:
(gnotime:4032): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GnomeDateEdit'
Segmentation fault
This output does not show up until (immediately) after you complete step 4.
It seems like maybe clicking "Cancel" does some sort of important object cleanup or loading that gets skipped when closing the window by other methods.
I will try this on a fresh install sometime in the next few days, and if not reproducible there I will send you my data file.
Patch fixing this bug
Thank you for the complete procedure to reproduce the bug.
I've just fixed it in our revision control system. Also, attached is a patch to fix it, if you want to apply to your buid.
I should have Debian and Ubuntu packages uploaded tomorrow.
I just updated to gnotime 2.4.1 but can still reproduce the bug with the instructions from comment #2 above. Is it a regression then, or the same thing still?
The error message I get on the console is the same as shown above, and the exact same I had with this bug in 2.3.0:
(gnotime:22478): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer(gnotime:22478): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed(gnotime:22478): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'GnomeDateEdit'Segmentation fault (core dumped)