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 715062 - crash on .desktop file change
crash on .desktop file change
Status: RESOLVED DUPLICATE of bug 720460
Product: gnome-menus
Classification: Core
Component: libgnome-menu
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-menus dummy account
gnome-menus dummy account
Depends on:
Blocks:
 
 
Reported: 2013-11-23 13:14 UTC by Frederic Peters
Modified: 2018-12-24 17:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Frederic Peters 2013-11-23 13:14:36 UTC 
I was running a system upgrade and gnome-shell crashed as a file in /usr/share/applications/ got updated.

Core was generated by `/scratch/jhbuild/bin/gnome-shell'.
Program terminated with signal 11, Segmentation fault.

+ Trace 232823

  • #0 cached_dir_ref
    at entry-directories.c line 171
  • #0 cached_dir_ref
    at entry-directories.c line 171
  • #1 cached_dir_add_reference
    at entry-directories.c line 738
  • #2 cached_dir_add_reference
    at entry-directories.c line 742
  • #3 cached_dir_add_reference
    at entry-directories.c line 742
  • #4 cached_dir_queue_monitor_event
    at entry-directories.c line 506
  • #5 handle_cached_dir_changed
    at entry-directories.c line 593
  • #6 invoke_notifies
    at menu-monitor.c line 85
  • #7 emit_events_in_idle
    at menu-monitor.c line 122
  • #8 g_idle_dispatch
    at gmain.c line 5254
  • #9 g_main_dispatch
    at gmain.c line 3066
  • #10 g_main_context_dispatch
    at gmain.c line 3640
  • #11 g_main_context_iterate
    at gmain.c line 3711
  • #12 g_main_loop_run
    at gmain.c line 3905
  • #13 meta_run
    at core/main.c line 556
  • #14 main
    at main.c line 437 






Comment 1


Sebastien Bacher





          2013-12-09 14:34:01 UTC
        



seems like a duplicate of bug #712161






Comment 2


Jeremy Bicha





          2018-12-24 17:42:38 UTC
        




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