Bug 1402208 - [abrt] baobab: _g_log_abort(): baobab killed by SIGTRAP
Summary: [abrt] baobab: _g_log_abort(): baobab killed by SIGTRAP
Keywords:
Status: CLOSED DUPLICATE of bug 1366897
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk3
Version: 25
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:cfd0f929a821aeffcb9cd7af566...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 03:54 UTC by Yonatan
Modified: 2016-12-09 07:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-09 07:36:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.69 KB, text/plain)
2016-12-07 03:54 UTC, Yonatan
no flags Details

Description Yonatan 2016-12-07 03:54:15 UTC
Version-Release number of selected component:
baobab-3.22.1-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/baobab --gapplication-service
crash_function: _g_log_abort
executable:     /usr/bin/baobab
global_pid:     5162
kernel:         4.8.10-300.fc25.i686
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 _g_log_abort at gmessages.c:487
 #1 g_log_writer_default at gmessages.c:2382
 #2 g_log_structured_array at gmessages.c:1770
 #3 g_log_structured at gmessages.c:1597
 #4 gdk_event_source_check at gdkeventsource.c:92
 #5 g_main_context_check at gmain.c:3762
 #7 g_main_context_iteration at gmain.c:3990
 #8 g_application_run at gapplication.c:2381
 #9 _vala_main at main.c:67

Comment 1 Yonatan 2016-12-07 03:54:28 UTC
Created attachment 1228830 [details]
File: backtrace

Comment 2 Ondrej Holy 2016-12-09 07:36:01 UTC

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


Note You need to log in before you can comment on or make changes to this bug.