Description of problem: tried to sync with Gnote and it crashed Version-Release number of selected component: gtg-0.3.1-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/gtg crash_function: _dbus_watch_invalidate executable: /usr/bin/python2.7 kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1002 Truncated backtrace: Thread no. 1 (10 frames) #0 _dbus_watch_invalidate at dbus-watch.c:171 #1 free_watches at dbus-transport-socket.c:83 #2 socket_disconnect at dbus-transport-socket.c:987 #3 _dbus_transport_disconnect at dbus-transport.c:509 #4 _dbus_transport_queue_messages at dbus-transport.c:1165 #5 _dbus_connection_get_dispatch_status_unlocked at dbus-connection.c:4211 #6 dbus_connection_get_dispatch_status at dbus-connection.c:4342 #7 message_queue_prepare at dbus-gmain.c:71 #8 g_main_context_prepare at gmain.c:3340 #11 gtk_main at gtkmain.c:1257
Created attachment 842567 [details] File: backtrace
Created attachment 842568 [details] File: cgroup
Created attachment 842569 [details] File: core_backtrace
Created attachment 842570 [details] File: dso_list
Created attachment 842571 [details] File: environ
Created attachment 842572 [details] File: exploitable
Created attachment 842573 [details] File: limits
Created attachment 842574 [details] File: maps
Created attachment 842575 [details] File: open_fds
Created attachment 842576 [details] File: proc_pid_status
Created attachment 842577 [details] File: var_log_messages
Hi, Thank you for your bugreport. Is this reproducible? Thanks, Warm regards, Ankur
(In reply to Ankur Sinha (FranciscoD) from comment #12) > Hi, > > Thank you for your bugreport. > > Is this reproducible? > > Thanks, > Warm regards, > Ankur yes. very simple: enable syncing with Gnote and it will crash
I've reported it upstream. Thanks for the bug report. Ankur
The bug has been patched upstream. Link to revision - http://bazaar.launchpad.net/~gtg/gtg/trunk/revision/1339
is it fixed in Fedora 20?
Hi, No. It's fixed upstream and will land in the next release. If it were fixed in F20, an update would've been pushed. Thanks, Warm regards, Ankur