Merge lp:~jjardon/indicator-datetime/fix-794312 into lp:indicator-datetime/0.3
Proposed by
Javier Jardón
Status: | Work in progress |
---|---|
Proposed branch: | lp:~jjardon/indicator-datetime/fix-794312 |
Merge into: | lp:indicator-datetime/0.3 |
Diff against target: |
29 lines (+4/-3) 1 file modified
src/indicator-datetime.c (+4/-3) |
To merge this branch: | bzr merge lp:~jjardon/indicator-datetime/fix-794312 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Charles Kerr (community) | Needs Fixing | ||
Review via email: mp+79426@code.launchpad.net |
To post a comment you must log in.
Unmerged revisions
- 142. By Javier Jardón
-
indicator-
datetime. c: Do not connect the signal before the menu is created Fixes https:/
/bugs.launchpad .net/ubuntu/ +source/ indicator- datetime/ +bug/794312
I appreciate this patch, especially since the ticket was (incorrectly) closed as a duplicate of an unrelated ticket :) But, I don't think it addresses the OP's crash -- the retrace shows the final two steps were:
> g_type_ check_instance_ cast (type_instance= 0x2849cb0, iface_type= 42195904) menu_item_ set_date (menuitem= 0x27d7440, year=2011, month=5, day=7) at idocalendarmenu item.c: 383
> ido_calendar_
menuitem wasn't NULL in this trace, so guarding against NULL in the calling code probably won't help. In fact, ido_calendar_ menu_item_ set_date( ) is already safeguarding against NULL pointers in its first line that calls IDO_IS_ CALENDAR_ MENU_ITEM( ). That's already null-safe -- but, unfortunately, not corrupt-pointer safe, which is why g_type_ check_instance_ cast() is crashing. ;)