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 710753 - clipboard crash (was gedit SIGSEGV in gedit_multi_notebook_get_active_tab)
clipboard crash (was gedit SIGSEGV in gedit_multi_notebook_get_active_tab)
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-10-23 20:25 UTC by Sebastien Bacher
Modified: 2018-04-15 00:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (1.21 KB, patch)
2015-09-05 19:56 UTC, Paolo Borelli
none Details | Review

Description Sebastien Bacher 2013-10-23 20:25:24 UTC
The bug has been reported on https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1180665

gedit 3.8.0

The comments suggest in happen when deleting a file from disk while it's open in gedit

"#0  0x0000000000460076 in gedit_multi_notebook_get_active_tab ()
No symbol table info available.
  • #1 ??
  • #2 selection_received
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkclipboard.c line 939
  • #3 g_closure_invoke
    at /build/buildd/glib2.0-2.37.0/./gobject/gclosure.c line 777
  • #4 signal_emit_unlocked_R
    at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c line 3584
  • #5 g_signal_emit_valist
    at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c line 3328
  • #6 g_signal_emit_by_name
    at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c line 3424
  • #7 gtk_selection_retrieval_report
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkselection.c line 2983
  • #8 _gtk_selection_notify
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkselection.c line 2787
  • #9 _gtk_marshal_BOOLEAN__BOXEDv
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c line 130
  • #10 _g_closure_invoke_va
    at /build/buildd/glib2.0-2.37.0/./gobject/gclosure.c line 840
  • #11 g_signal_emit_valist
    at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c line 3234
  • #12 g_signal_emit
    at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c line 3384
  • #13 gtk_widget_event_internal
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkwidget.c line 6714
  • #14 gtk_widget_event
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkwidget.c line 6371
  • #15 gtk_main_do_event
    at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkmain.c line 1645
  • #16 gdk_event_source_dispatch
    at /build/buildd/gtk+3.0-3.8.2/./gdk/x11/gdkeventsource.c line 364
  • #17 g_main_dispatch
    at /build/buildd/glib2.0-2.37.0/./glib/gmain.c line 3058
  • #18 g_main_context_dispatch
    at /build/buildd/glib2.0-2.37.0/./glib/gmain.c line 3634
  • #19 g_main_context_iterate
    at /build/buildd/glib2.0-2.37.0/./glib/gmain.c line 3705
  • #20 g_main_context_iteration
    at /build/buildd/glib2.0-2.37.0/./glib/gmain.c line 3766
  • #21 g_application_run
    at /build/buildd/glib2.0-2.37.0/./gio/gapplication.c line 1624
  • #22 main

Comment 1 Paolo Borelli 2015-09-05 19:51:46 UTC
Sorry for never looking at this... obviously at this point the stack trace is quite old, however I just took a look at the gtk clipboard code stack trace and it seems to me it is missing a null check. I am changing the title, attaching a patch and reassigning to gtk
Comment 2 Paolo Borelli 2015-09-05 19:56:14 UTC
Created attachment 310721 [details] [review]
patch

I am not familiar with the clipboard internals, but I took a quick look since it appears in the reported stack trace and it seems to me it should check that request_info is not null before calling request_info->callback, since the get_request_content_info function can return NULL
Comment 3 Matthias Clasen 2018-02-10 05:01:23 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 4 Matthias Clasen 2018-04-15 00:14:50 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new