unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast()

Bug #764962 reported by Kenny Strawn
124
This bug affects 25 people
Affects Status Importance Assigned to Milestone
DBus Menu
Invalid
Undecided
Unassigned
Indicator Date and Time
Invalid
Undecided
Unassigned
Unity
Invalid
Undecided
Unassigned
indicator-datetime (Ubuntu)
Invalid
Undecided
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: indicator-datetime

Apparently, after Firefox launched while Unity was running, this crash report occurred.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.2.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-0.1-chromeos-intel-menlow
Uname: Linux 2.6.32.26+drm33.12 i686
Architecture: i386
Date: Mon Apr 18 10:57:42 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x76f1dfee <g_type_check_instance_cast+78>: movzbl 0xe(%edx),%edi
 PC (0x76f1dfee) ok
 source "0xe(%edx)" (0x002e2e3a) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ido_calendar_menu_item_set_date () from /usr/lib/libido-0.1.so.0
 ?? () from /usr/lib/indicators/5/libdatetime.so
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to natty on 2011-04-18 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Kenny Strawn (realkstrawn93) wrote :
visibility: private → public
Revision history for this message
Karl Lattimer (karl-qdh) wrote :

this appears to be related to a set date on ido calendar, which is triggered by a menu close.

Did you have the menu open at the time? I think I saw this bug once when I installed a new package and the menu was open but I couldn't reproduce it.

Changed in indicator-datetime:
status: New → Incomplete
Changed in indicator-datetime (Ubuntu):
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
tags: removed: need-i386-retrace
Revision history for this message
Omer Akram (om26er) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
lipstick (sinanaykut-gmail) wrote :

This bug effects me as well, i use ubuntu 11.10 alpha release...

Revision history for this message
Gerry Boland (gerboland) wrote :
Download full text (6.8 KiB)

Bug appeared today on my up-to-date Oneiric. I can reproduce it easily. Let me know what info you need.

$ gdb /usr/lib/unity/unity-panel-service
GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/lib/unity/unity-panel-service...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/lib/unity/unity-panel-service
[Thread debugging using libthread_db enabled]
Gtk-Message: Failed to load module "gail"
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libappmenu.so
(unity-panel-service:1742): Indicator-Appmenu-DEBUG: New Desktop Window: 2A00004
[New Thread 0xb7d7fb70 (LWP 1745)]
[New Thread 0xb757eb70 (LWP 1746)]
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libmessaging.so
[New Thread 0xb6bffb70 (LWP 1747)]
[New Thread 0xb63feb70 (LWP 1748)]

(unity-panel-service:1742): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libdatetime.so
[New Thread 0xb4eb5b70 (LWP 1749)]
(unity-panel-service:1742): Indicator-Datetime-DEBUG: Evaluating bitmask for '%H:%M'
(unity-panel-service:1742): Indicator-Datetime-DEBUG: Checking against 1 possible times
(unity-panel-service:1742): Indicator-Datetime-DEBUG: Guessing max time width: 36
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libsoundmenu.so

(unity-panel-service:1742): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libpower.so

(unity-panel-service:1742): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libsession.so

(unity-panel-service:1742): GLib-CRITICAL **: g_error_free: assertion `error != NULL' failed
(unity-panel-service:1742): Indicator-Session-DEBUG: get entries
** (unity-panel-service:1742): DEBUG: Loading: /usr/lib/indicators3/6/libapplication.so
** (unity-panel-service:1742): DEBUG: Initializing PanelUtilAccessible class

** (unity-panel-service:1742): CRITICAL **: atk_object_set_description: assertion `description != NULL' failed

** (unity-panel-service:1742): CRITICAL **: atk_object_set_description: assertion `description != NULL' failed

** (unity-panel-service:1742): CRITICAL **: atk_object_set_description: assertion `description != NULL' failed
(unity-panel-service:1742): Indicator-Session-DEBUG: get entries

** (unity-panel-service:1742): CRITICAL **: atk_object_set_description: assertion `description != NULL' failed
** (unity-panel-service:1742): DEBUG: Unity accessibility started, using bridge on /usr/lib/gtk-3.0/modules/libatk...

Read more...

Revision history for this message
Javier Jardón (jjardon) wrote :

Hey Gerry,

It would be very helpfull if you explain here the steps to reproduce the bug.

Revision history for this message
Florian Boucault (fboucault) wrote :

Speaking for Gerry: launching unity-panel-service produces the crash immediately.

Revision history for this message
Florian Boucault (fboucault) wrote :

I believe that it happens when you enable accessibility support.

Revision history for this message
Gerry Boland (gerboland) wrote :
Download full text (5.1 KiB)

Yes. I believe I enabled accessibility support just before this started happening. I've since disabled accessibility from the Universal Access app, but crash is still happening.

Here is a better backtrace (sorry, last one is missing gobject debug symbols):

Program received signal SIGSEGV, Segmentation fault.
g_type_check_instance_cast (type_instance=0x8164ac0, iface_type=134665448) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:3985
3985 /build/buildd/glib2.0-2.29.16/./gobject/gtype.c: No such file or directory.
 in /build/buildd/glib2.0-2.29.16/./gobject/gtype.c
(gdb) bt
#0 g_type_check_instance_cast (type_instance=0x8164ac0, iface_type=134665448) at /build/buildd/glib2.0-2.29.16/./gobject/gtype.c:3985
#1 0x0048b88a in ?? () from /usr/lib/libgtk-3.so.0
#2 0x0081e9fa in g_cclosure_marshal_VOID__PARAM (closure=0x8101be8, return_value=0x0, n_param_values=2, param_values=0x81f8ef0, invocation_hint=0xbfffea70,
    marshal_data=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c:539
#3 0x0081ca5c in g_closure_invoke (closure=0x8101be8, return_value=0x0, n_param_values=2, param_values=0x81f8ef0, invocation_hint=0xbfffea70)
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
#4 0x00830ec0 in signal_emit_unlocked_R (node=0x805df28, detail=96, instance=0x815d158, emission_return=0x0, instance_and_params=0x81f8ef0)
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3271
#5 0x00839b8f in g_signal_emit_valist (instance=0x815d158, signal_id=1, detail=96, var_args=0xbfffec20 "\300\244\024\b\002")
    at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3002
#6 0x00839d03 in g_signal_emit (instance=0x815d158, signal_id=1, detail=96) at /build/buildd/glib2.0-2.29.16/./gobject/gsignal.c:3059
#7 0x0081fe1f in g_object_dispatch_properties_changed (object=0x815d158, n_pspecs=1, pspecs=0xbfffec90) at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:925
#8 0x0081f17f in g_object_notify_dispatcher (object=0x815d158, n_pspecs=1, pspecs=0xbfffec90) at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:331
#9 0x00822392 in g_object_notify_queue_thaw (nqueue=<optimized out>, object=0x815d158) at /build/buildd/glib2.0-2.29.16/./gobject/gobjectnotifyqueue.c:132
#10 g_object_notify_by_spec_internal (pspec=<optimized out>, object=0x815d158) at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:983
#11 g_object_notify (object=0x815d158, property_name=0x55b566 "visible") at /build/buildd/glib2.0-2.29.16/./gobject/gobject.c:1024
#12 0x00421f0d in gtk_widget_show () from /usr/lib/libgtk-3.so.0
#13 0x0125e291 in ?? () from /usr/lib/libdbusmenu-gtk3.so.4
#14 0x0081ec6a in g_cclosure_marshal_VOID__OBJECT (closure=0x817db08, return_value=0x0, n_param_values=2, param_values=0x81f8ec8, invocation_hint=0xbfffee90,
    marshal_data=0x0) at /build/buildd/glib2.0-2.29.16/./gobject/gmarshal.c:644
#15 0x0081ca5c in g_closure_invoke (closure=0x817db08, return_value=0x0, n_param_values=2, param_values=0x81f8ec8, invocation_hint=0xbfffee90)
    at /build/buildd/glib2.0-2.29.16/./gobject/gclosure.c:773
#16 0x00830ec0 in signal_emit_unlocked_R (node=0x8169758, detail=0, instance=0x80cb9a0, emission_return=0x0, instance_and_params=0x81f8ec8)
    at /build...

Read more...

Revision history for this message
Lukasz Olszewski (olszewskil) wrote :

Please see the attachments provided in the duplicate report ( bug 845783 ) as they seem more complete.

Changed in unity (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Javier Jardón (jjardon) wrote :

The latest reported backtraces are not related with indicator-datetime anymore

Changed in indicator-datetime:
status: Incomplete → Invalid
Changed in indicator-datetime (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Ted Gould (ted) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

Changed in dbusmenu:
status: New → Invalid
Changed in unity (Ubuntu):
status: Confirmed → Invalid
Changed in unity:
status: Incomplete → Invalid
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

Remote bug watches

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