timer-applet crashed with SIGSEGV in g_type_check_is_value_type()

Bug #313142 reported by bford16
78
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Timer Applet
Invalid
Undecided
Unassigned
timer-applet (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: timer-applet

The applet crashed when unlocking account from screensaver (the screensaver also crashed).

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/timer-applet/timer-applet
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: fglrx
Package: timer-applet 2.0.1-3
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: python /usr/lib/timer-applet/timer-applet --oaf-activate-iid=OAFIID:TimerApplet_Factory --oaf-ior-fd=18
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: timer-applet
StacktraceTop:
 g_type_check_is_value_type ()
 g_value_type_compatible () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
Title: timer-applet crashed with SIGSEGV in g_type_check_is_value_type()
Uname: Linux 2.6.27-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
bford16 (bford16) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_type_check_is_value_type () from /usr/lib/libgobject-2.0.so.0
g_value_type_compatible () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in timer-applet (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pauli Virtanen (pauli-virtanen) wrote :
Download full text (5.1 KiB)

Here is a backtrace:
---------------------------------
(gdb) bt
#0 0x00df12ae in type_check_is_value_type_U (type=157287768)
    at /build/buildd/glib2.0-2.22.0/gobject/gtype.c:3834
#1 IA__g_type_check_is_value_type (type=157287768)
    at /build/buildd/glib2.0-2.22.0/gobject/gtype.c:3863
#2 0x00df7648 in IA__g_value_type_compatible (src_type=157287768,
    dest_type=155698800) at /build/buildd/glib2.0-2.22.0/gobject/gvalue.c:501
#3 0x00dd9590 in g_value_object_collect_value (value=0x9cd8e3c,
    n_collect_values=1, collect_values=0xbf95f29c, collect_flags=0)
    at /build/buildd/glib2.0-2.22.0/gobject/gobject.c:2711
#4 0x00deb7ba in IA__g_signal_emit_valist (instance=0x9b906a0, signal_id=318,
    detail=0, var_args=0xbf95f39c "\364oA")
    at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:2955
#5 0x00debd92 in IA__g_signal_emit_by_name (instance=0x9b906a0,
    detailed_signal=0x24f8f94 "volume-removed")
    at /build/buildd/glib2.0-2.22.0/gobject/gsignal.c:3074
#6 0x024f67c6 in signal_emit_in_idle_do (data=0x9c03300)
    at gproxyvolumemonitor.c:498
#7 0x0038a0f1 in g_idle_dispatch (source=0x9d164c8, callback=0,
    user_data=0x9c03300) at /build/buildd/glib2.0-2.22.0/glib/gmain.c:4065
#8 0x0038be78 in g_main_dispatch (context=0x9605028)
    at /build/buildd/glib2.0-2.22.0/glib/gmain.c:1960
#9 IA__g_main_context_dispatch (context=0x9605028)
    at /build/buildd/glib2.0-2.22.0/glib/gmain.c:2513
#10 0x0038f720 in g_main_context_iterate (context=0x9605028,
    block=<value optimized out>, dispatch=1, self=0x9615a58)
    at /build/buildd/glib2.0-2.22.0/glib/gmain.c:2591
#11 0x0038fb8f in IA__g_main_loop_run (loop=0x9af5f98)
    at /build/buildd/glib2.0-2.22.0/glib/gmain.c:2799
#12 0x012b2cc3 in bonobo_main () at bonobo-main.c:311
#13 0x012b0e89 in bonobo_generic_factory_main_timeout (
    act_iid=0x9af5f70 ":0.0,OAFIID:TimerApplet_Factory",
    factory_cb=0xa1d070 <panel_applet_factory_callback>, user_data=0x9affc30,
    quit_timeout=2000) at bonobo-generic-factory.c:411
#14 0x012b0f13 in bonobo_generic_factory_main (
    act_iid=0x9af5f70 ":0.0,OAFIID:TimerApplet_Factory",
    factory_cb=0xa1d070 <panel_applet_factory_callback>, user_data=0x9affc30)
    at bonobo-generic-factory.c:368
#15 0x00a1d9b4 in panel_applet_factory_main_closure (
    iid=0xb7f746fc "OAFIID:TimerApplet_Factory", applet_type=157681344,
    closure=0x9affc40) at panel-applet.c:1774
#16 0x00841b4a in _wrap_panel__applet_bonobo_factory (self=0x0,
    args=0x98c65fc, kwargs=0x0) at applet.override:109
#17 0x080dc0f0 in call_function (f=0x9394374, throwflag=0)
    at ../Python/ceval.c:3706
#18 PyEval_EvalFrameEx (f=0x9394374, throwflag=0) at ../Python/ceval.c:2389
#19 0x080dde12 in PyEval_EvalCodeEx (co=0xb7f73728, globals=0xb7fb71c4,
    locals=0xb7fb71c4, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
    defcount=0, closure=0x0) at ../Python/ceval.c:2968
#20 0x080ddf17 in PyEval_EvalCode (co=0xb7f73728, globals=0xb7fb71c4,
    locals=0xb7fb71c4) at ../Python/ceval.c:522
#21 0x080faa1f in run_mod (fp=0x9342af8,
    filename=0xbf961aef "/usr/lib/timer-applet/timer-applet", start=257,
    globals=0xb7fb71c4, locals=0xb7fb71c4, closeit=1, flags=0x...

Read more...

Changed in timer-applet (Ubuntu):
status: Incomplete → New
Revision history for this message
Susan Cragin (susancragin) wrote :

Mine crashed with identical warning message but I don't have screensaver activated.
Screen may have been dimming to save power on laptop.

Revision history for this message
Kenny Meyer (knny-myer) wrote :

I cannot reproduce this here on Ubuntu 10.04. I guess this is not a Timer Applet specific bug.

Marking this as invalid, as long as there are no new reports.

Changed in timer-applet:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in timer-applet (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in timer-applet (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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