After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712161 - software-center hits segfault in cached_dir_ref()
software-center hits segfault in cached_dir_ref()
Status: RESOLVED DUPLICATE of bug 720460
Product: gnome-menus
Classification: Core
Component: libgnome-menu
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-menus dummy account
gnome-menus dummy account
Depends on:
Blocks:
 
 
Reported: 2013-11-12 16:40 UTC by Sebastien Bacher
Modified: 2014-01-08 19:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2013-11-12 16:40:10 UTC 
The issue is a frequently reported one in the current Ubuntu version, it started in the cycle where we updated gnome-menus from 3.6 to 3.8 (not sure if that means the issue is new to 3.8 though)

The bug reports don't really have useful descrition, but that's the stacktrace:

"#0  cached_dir_ref (dir=0x1e0) at /build/buildd/gnome-menus-3.8.0/./libmenu/entry-directories.c:171
No locals.

+ Trace 232748

  • #1 cached_dir_add_reference
    at /build/buildd/gnome-menus-3.8.0/./libmenu/entry-directories.c line 738
  • #2 cached_dir_queue_monitor_event
    at /build/buildd/gnome-menus-3.8.0/./libmenu/entry-directories.c line 506
  • #3 invoke_notifies
    at /build/buildd/gnome-menus-3.8.0/./libmenu/menu-monitor.c line 85
  • #4 emit_events_in_idle
    at /build/buildd/gnome-menus-3.8.0/./libmenu/menu-monitor.c line 122
  • #5 g_idle_dispatch
    at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 5245
  • #6 g_main_dispatch
    at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3068
  • #7 g_main_context_dispatch
    at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3641
  • #8 g_main_context_iterate
    at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3684
  • #9 g_main_loop_run
    at /build/buildd/glib2.0-2.38.0/./glib/gmain.c line 3908
  • #10 gtk_main
    at /build/buildd/gtk+3.0-3.8.4/./gtk/gtkmain.c line 1156
  • #11 ffi_call_SYSV
    at ../src/x86/sysv.S line 65
  • #12 ffi_call
    at ../src/x86/ffi.c line 411
  • #13 g_callable_info_invoke
    at girepository/gicallableinfo.c line 680
  • #14 g_function_info_invoke
    at girepository/gifunctioninfo.c line 274
  • #15 _invoke_callable
    at ../../gi/pygi-invoke.c line 64
  • #16 pygi_callable_info_invoke
    at ../../gi/pygi-invoke.c line 652
  • #17 _wrap_g_callable_info_invoke
    at ../../gi/pygi-invoke.c line 675
  • #18 _callable_info_call
    at ../../gi/pygi-info.c line 439
  • #19 PyObject_Call
    at ../Objects/abstract.c line 2529
  • #20 do_call
    at ../Python/ceval.c line 4239
  • #21 call_function
    at ../Python/ceval.c line 4044
  • #22 PyEval_EvalFrameEx
    at ../Python/ceval.c line 2666
  • #23 PyEval_EvalCodeEx
    at ../Python/ceval.c line 3253
  • #24 PyEval_EvalCode
    at ../Python/ceval.c line 667
  • #25 run_mod
    at ../Python/pythonrun.c line 1365
  • #26 PyRun_FileExFlags
    at ../Python/pythonrun.c line 1351
  • #27 PyRun_SimpleFileExFlags
    at ../Python/pythonrun.c line 943
  • #28 PyRun_AnyFileExFlags
    at ../Python/pythonrun.c line 747
  • #29 Py_Main
    at ../Modules/main.c line 640
  • #30 main
    at ../Modules/python.c line 23 






Comment 1


Jasper St. Pierre (not reading bugmail)





          2013-11-12 17:19:46 UTC
        



Try reverting https://git.gnome.org/browse/gnome-menus/commit/?id=7d90221e27fcc72de497f45db4f3ef3c2d623fd6






Comment 2


Sebastien Bacher





          2013-11-12 17:28:18 UTC
        



Thanks Jasper, I can't reproduce the issue but I'm going to upload a package to the Ubuntu devel serie and see if that makes the reports stop there...






Comment 3


Sebastien Bacher





          2013-11-19 18:42:43 UTC
        



Reverting that commit seems to do the trick






Comment 4


Adam Williamson





          2014-01-08 19:17:40 UTC
        



There's a similar looking crash in Rawhide ATM:

https://bugzilla.redhat.com/show_bug.cgi?id=1039180

my Shell usually crashes a half dozen times a day or so and I think it's that crash in all cases. Is that the same thing?






Comment 5


Jasper St. Pierre (not reading bugmail)





          2014-01-08 19:18:37 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 720460 ***