Bug 913646

Summary: [abrt] pinpoint-0.1.4-8.fc17: g_logv: Process /usr/bin/pinpoint was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: simgidacav
Component: pinpointAssignee: Paul W. Frields <stickster>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: pbrobinson, pfrields, stickster
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2bb09123c496f0d96a7ab95017929fdb3a3a9cb1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-25 16:59:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: smolt_data
none
File: xsession_errors
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages none

Description simgidacav 2013-02-21 17:55:48 UTC 
Description of problem:
It works properly on showing slides (which is good).
The bug shows up when editing the file with pinpoint opened on it.
Probably this has something to do with reloading of a partially written file.

I suspect (but take this with a grain of salt) that the transition causes the crash. Like when you save twice in a row, and the second time happens during a transition.


Version-Release number of selected component:
pinpoint-0.1.4-8.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        pinpoint ./OMG.pin
crash_function: g_logv
kernel:         3.7.6-102.fc17.x86_64

truncated backtrace:
:Thread no. 1 (3 frames)
: #0 g_logv at gmessages.h:101
: #2 reload at pp-clutter.c:2204
: #8 clutter_main at ./clutter-main.c:945
Comment 1 simgidacav 2013-02-21 17:55:53 UTC 
Created attachment 700679 [details]
File: core_backtrace
Comment 2 simgidacav 2013-02-21 17:55:55 UTC 
Created attachment 700680 [details]
File: environ
Comment 3 simgidacav 2013-02-21 17:55:57 UTC 
Created attachment 700681 [details]
File: limits
Comment 4 simgidacav 2013-02-21 17:56:00 UTC 
Created attachment 700682 [details]
File: backtrace
Comment 5 simgidacav 2013-02-21 17:56:02 UTC 
Created attachment 700683 [details]
File: cgroup
Comment 6 simgidacav 2013-02-21 17:56:04 UTC 
Created attachment 700684 [details]
File: smolt_data
Comment 7 simgidacav 2013-02-21 17:56:06 UTC 
Created attachment 700685 [details]
File: xsession_errors
Comment 8 simgidacav 2013-02-21 17:56:10 UTC 
Created attachment 700686 [details]
File: executable
Comment 9 simgidacav 2013-02-21 17:56:13 UTC 
Created attachment 700687 [details]
File: maps
Comment 10 simgidacav 2013-02-21 17:56:15 UTC 
Created attachment 700688 [details]
File: dso_list
Comment 11 simgidacav 2013-02-21 17:56:18 UTC 
Created attachment 700689 [details]
File: proc_pid_status
Comment 12 simgidacav 2013-02-21 17:56:20 UTC 
Created attachment 700690 [details]
File: open_fds
Comment 13 simgidacav 2013-02-21 17:56:22 UTC 
Created attachment 700691 [details]
File: var_log_messages
Comment 14 Paul W. Frields 2013-06-25 16:59:13 UTC 
https://bugzilla.gnome.org/show_bug.cgi?id=672550 upstream seems to be aimed at resolving this problem.  However, not clear what the ETA is.  I suggest cc'ing yourself on the bug upstream, and when a new release comes we can include the fix in Fedora.