Crash adding a new item with alacarte

Bug #60933 reported by Adam McMaster
18
Affects Status Importance Assigned to Milestone
alacarte (Ubuntu)
Fix Released
Medium
Travis Watkins

Bug Description

Binary package hint: alacarte

While creating a new menu item, alacarte crashed when I started typing the command. Didn't crash the second time I tried. Backtrace from Bug Buddy shortly.

Revision history for this message
Adam McMaster (adammc) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

That happens when opening the window for a menu item too sometimes on edgy:

"(gdb) bt
#0 0x00002afbe7a92be4 in _g_utf8_normalize_wc (str=0x0, max_len=-1,
    mode=G_NORMALIZE_ALL) at gunidecomp.c:354
#1 0x00002afbe7a93253 in IA__g_utf8_normalize (str=0x0, len=-1,
    mode=G_NORMALIZE_ALL) at gunidecomp.c:515
#2 0x00002afbe8135d7a in IA__gtk_entry_completion_complete (
    completion=0xdc1800) at gtkentrycompletion.c:1098
#3 0x00002afbe812c368 in check_completion_callback (completion=0x0)
    at gtkentry.c:5613
#4 0x00002afbe781f15b in source_closure_marshal_BOOLEAN__VOID (
    closure=<value optimized out>, return_value=0x7fffc3be6d50,
    n_param_values=2, param_values=0x0, invocation_hint=0x1, marshal_data=0x1)
    at gsourceclosure.c:81
#5 0x00002afbe780859a in IA__g_closure_invoke (closure=0x10fa7d0,
    return_value=0x7fffc3be6d50, n_param_values=0, param_values=0x0,
    invocation_hint=0x0) at gclosure.c:490
#6 0x00002afbe781f123 in source_closure_callback (data=0x10fa7d0)
    at gsourceclosure.c:123
#7 0x00002afbe7a6ed44 in IA__g_main_context_dispatch (context=0x83d510)
    at gmain.c:2045
#8 0x00002afbe7a71b8d in g_main_context_iterate (context=0x83d510, block=1,
    dispatch=1, self=<value optimized out>) at gmain.c:2677
#9 0x00002afbe7a71e9a in IA__g_main_loop_run (loop=0x10f8e90) at gmain.c:2881"

Changed in alacarte:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Travis Watkins (amaranth) wrote :

I _think_ this is fixed in CVS now, will be making an 0.10.1 release soon.

Changed in alacarte:
assignee: nobody → amaranth
status: Confirmed → In Progress
Revision history for this message
Sebastien Bacher (seb128) wrote :

seems to work fine with 0.10.1, marking as fixed. Feel free to reopen if you get the issue again after upgrading

Changed in alacarte:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.