Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1475609

Summary: [abrt] sakura: sakura_set_size(): sakura killed by signal 11
Product: [Fedora] Fedora Reporter: ztb0001
Component: sakuraAssignee: Christoph Wickert <cwickert>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: cwickert, jenschjoshua
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2cbba45409279e7533d56b598a68b9d199569443
Whiteboard: abrt_hash:603bc78dcb1f2e3062050fc526832e133d6386d8;VARIANT_ID=workstation;
Fixed In Version: sakura-3.5.0-1.fc28 sakura-3.5.0-1.fc26 sakura-3.5.0-1.fc27 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-06 21:59:43 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description ztb0001 2017-07-26 21:02:16 EDT
Description of problem:
Fresh install from live iso
dnf install sakura
sakura (or just open the program)

Version-Release number of selected component:
sakura-3.2.0-3.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        sakura
crash_function: sakura_set_size
executable:     /usr/bin/sakura
journald_cursor: s=d2354125e7384fcb9a80c87e96263874;i=1377;b=4fe48d01116241849da77557a3ec3db4;m=4bbe6574;t=55541ebc9f9b1;x=cf3adbed523e4553
kernel:         4.11.8-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 sakura_set_size at /usr/src/debug/sakura-3.2.0/src/sakura.c:2514
 #1 sakura_add_tab at /usr/src/debug/sakura-3.2.0/src/sakura.c:2758

Potential duplicate: bug 1336445
Comment 1 ztb0001 2017-07-26 21:02:20 EDT
Created attachment 1305120 [details]
File: backtrace
Comment 2 ztb0001 2017-07-26 21:02:20 EDT
Created attachment 1305121 [details]
File: cgroup
Comment 3 ztb0001 2017-07-26 21:02:21 EDT
Created attachment 1305122 [details]
File: core_backtrace
Comment 4 ztb0001 2017-07-26 21:02:22 EDT
Created attachment 1305123 [details]
File: cpuinfo
Comment 5 ztb0001 2017-07-26 21:02:23 EDT
Created attachment 1305124 [details]
File: dso_list
Comment 6 ztb0001 2017-07-26 21:02:24 EDT
Created attachment 1305125 [details]
File: environ
Comment 7 ztb0001 2017-07-26 21:02:24 EDT
Created attachment 1305126 [details]
File: exploitable
Comment 8 ztb0001 2017-07-26 21:02:25 EDT
Created attachment 1305127 [details]
File: limits
Comment 9 ztb0001 2017-07-26 21:02:26 EDT
Created attachment 1305128 [details]
File: maps
Comment 10 ztb0001 2017-07-26 21:02:27 EDT
Created attachment 1305129 [details]
File: open_fds
Comment 11 ztb0001 2017-07-26 21:02:28 EDT
Created attachment 1305130 [details]
File: proc_pid_status
Comment 12 ztb0001 2017-07-26 21:02:28 EDT
Created attachment 1305131 [details]
File: var_log_messages
Comment 13 Joshua Jensch 2017-07-30 15:58:52 EDT
Similar problem has been detected:

I installed sakura on a fresh install and when trying to start it instantly segfaults.
I remember having the same problem a while back on my gentoo installation, it was related to a kernel or graphics driver update
(I am running a Radeon HD 7770)

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        sakura
crash_function: sakura_set_size
executable:     /usr/bin/sakura
journald_cursor: s=a37bbff57df54d8592e99afdcdfb2e7f;i=5b4b;b=284b21c0b5de4e7db59fb93b99667e34;m=1053fde3;t=5558df831af50;x=e80d0118f579d720
kernel:         4.11.11-300.fc26.x86_64
package:        sakura-3.2.0-3.fc26
reason:         sakura killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 14 Fedora Update System 2018-04-24 19:03:00 EDT
sakura-3.5.0-1.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-21d6e4debb
Comment 15 Fedora Update System 2018-04-24 19:03:20 EDT
sakura-3.5.0-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-e165397a75
Comment 16 Fedora Update System 2018-04-24 19:03:32 EDT
sakura-3.5.0-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-6d9dcb0442
Comment 17 Fedora Update System 2018-04-25 15:43:11 EDT
sakura-3.5.0-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-e165397a75
Comment 18 Fedora Update System 2018-04-25 16:10:43 EDT
sakura-3.5.0-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-6d9dcb0442
Comment 19 Fedora Update System 2018-04-26 00:52:10 EDT
sakura-3.5.0-1.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-21d6e4debb
Comment 20 Fedora End Of Life 2018-05-03 04:29:32 EDT
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 21 Fedora Update System 2018-05-06 21:59:43 EDT
sakura-3.5.0-1.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.
Comment 22 Fedora Update System 2018-05-06 23:37:40 EDT
sakura-3.5.0-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 23 Fedora Update System 2018-05-07 00:14:52 EDT
sakura-3.5.0-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.