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 768126 - Crash
Crash
Status: RESOLVED INCOMPLETE
Product: glib
Classification: Platform
Component: network
2.40.x
Other Linux
: Normal major
: ---
Assigned To: libnotify-maint
libnotify-maint
https://developer.pidgin.im/ticket/17055
Depends on:
Blocks:
 
 
Reported: 2016-06-28 07:56 UTC by Thedemon007
Modified: 2017-11-15 12:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Backtrace (3.43 KB, text/plain)
2016-06-28 07:56 UTC, Thedemon007 		Details

Description Thedemon007 2016-06-28 07:56:32 UTC 
Created attachment 330474 [details]
Backtrace

I use pidgin with libnotify plugin activate and give crash on various occasions.

Info of others trackers:

https://developer.pidgin.im/ticket/1705

https://github.com/dequis/purple-facebook/issues/253 (closed)

Here https://github.com/dequis/purple-facebook/issues/253#issuecomment-228561122 @dequis say "GSource that crashed was some dns query related function" I think it's maybe something exploitable and a security issue..
Comment 1 Thedemon007 2016-06-29 06:48:52 UTC 
libnotify no is the problem i disable it and give crash.

+ Trace 236398

  • #0 g_main_dispatch
    at /build/buildd/glib2.0-2.40.2/./glib/gmain.c line 3019
  • #1 g_main_context_dispatch
    at /build/buildd/glib2.0-2.40.2/./glib/gmain.c line 3663
  • #2 g_main_context_iterate
    at /build/buildd/glib2.0-2.40.2/./glib/gmain.c line 3734 






Comment 2


Michael Catanzaro





          2016-10-04 23:47:29 UTC
        



Unfortunately the backtrace you attached contains no useful information.

Why do you think this is a glib-networking bug?






Comment 3


Philip Withnall





          2017-11-15 12:44:38 UTC
        



No information provided in a year: closing.

Thedemon007: If you can still reproduce this problem, please can you provide an up-to-date backtrace, plus a log from valgrind. This looks like memory corruption rather than a segfault. You can use the following command to create a valgrind log:

valgrind --tool=memcheck --leak-check=full --leak-resolution=high --num-callers=50 --show-leak-kinds=definite /program/to/execute