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 598693 - gnome-system-monitor crashed with SIGSEGV in g_markup_escape_text()
gnome-system-monitor crashed with SIGSEGV in g_markup_escape_text()
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: process list
2.28.x
Other Linux
: Normal critical
: ---
Assigned To: System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2009-10-16 14:44 UTC by Pedro Villavicencio
Modified: 2012-01-24 12:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pedro Villavicencio 2009-10-16 14:44:48 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/452354

"It shows the main screen, the graphs and the file system tabs but on clicking the performance tab it crashes"

".

+ Trace 218362

Thread 1 (process 2535)

  • #0 g_markup_escape_text
    from /lib/libglib-2.0.so.0
  • #1 ProcInfo
    at proctable.cpp line 703
  • #2 refresh_list
    at proctable.cpp line 738
  • #3 proctable_update_list
    at proctable.cpp line 888
  • #4 cb_timeout
    at callbacks.cpp line 413
  • #5 cb_change_current_page
    at callbacks.cpp line 342
  • #6 _gtk_marshal_VOID__POINTER_UINT
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmarshalers.c line 2658
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_notebook_switch_page
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtknotebook.c line 5859
  • #12 gtk_notebook_button_press
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtknotebook.c line 2522
  • #13 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmarshalers.c line 84
  • #14 ??
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkwidget.c line 4767
  • #20 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmain.c line 2415
  • #21 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmain.c line 1620
  • #22 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.18.2/gdk/x11/gdkevents-x11.c line 2369
  • #23 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #24 ??
    from /lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #26 IA__gtk_main
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmain.c line 1216
  • #27 Gtk::Main::run_impl
    at main.cc line 536
  • #28 Gtk::Main::run
    at main.cc line 483
  • #29 main
    at procman.cpp line 757 






Comment 1


Chris Kühl





          2011-12-11 14:16:02 UTC
        



Is this still an issue in the newest development version from master?






Comment 2


Robert Roth





          2012-01-24 12:29:57 UTC
        



The reporter from downstream has commented that he does not experience this issue anymore, so I am setting this bug to FIXED.