Bug 2165383

Summary: [abrt] gpick: g_malloc0(): gpick killed by SIGABRT
Product: [Fedora] Fedora Reporter: Sandro <gui1ty>
Component: gpickAssignee: Luya Tshimbalanga <luya_tfz>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: design-devel, luya_tfz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/6900a287d8fba4f2b3189b8e9990db8d48f249ef
Whiteboard: abrt_hash:85d1dbd83ae20bff74381c00358a6c4ad49264f3;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-01-12 22:37:31 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: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Sandro 2023-01-29 16:56:45 UTC
Description of problem:
In the 'Layout preview' tab I right clicked on 'Header' and Gpick crashed. However, I'm unable to reproduce the crash.

Version-Release number of selected component:
gpick-0.2.6-34.20210528git0e858d3.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
cmdline:        gpick
crash_function: g_malloc0
executable:     /usr/bin/gpick
journald_cursor: s=e57a4b5a627d4f2abffe13a0dee868d0;i=fc2d2;b=ee78755af70d4fbba19a0006e9d7bffd;m=723ad55012;t=5f369abba466e;x=fd9888f1935eec91
kernel:         6.1.7-200.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 1 Sandro 2023-01-29 16:56:48 UTC
Created attachment 1941000 [details]
File: backtrace

Comment 2 Sandro 2023-01-29 16:56:49 UTC
Created attachment 1941001 [details]
File: core_backtrace

Comment 3 Sandro 2023-01-29 16:56:50 UTC
Created attachment 1941002 [details]
File: cpuinfo

Comment 4 Sandro 2023-01-29 16:56:52 UTC
Created attachment 1941003 [details]
File: dso_list

Comment 5 Sandro 2023-01-29 16:56:53 UTC
Created attachment 1941004 [details]
File: environ

Comment 6 Sandro 2023-01-29 16:56:54 UTC
Created attachment 1941005 [details]
File: limits

Comment 7 Sandro 2023-01-29 16:56:55 UTC
Created attachment 1941006 [details]
File: maps

Comment 8 Sandro 2023-01-29 16:56:56 UTC
Created attachment 1941007 [details]
File: mountinfo

Comment 9 Sandro 2023-01-29 16:56:57 UTC
Created attachment 1941008 [details]
File: open_fds

Comment 10 Sandro 2023-01-29 16:56:58 UTC
Created attachment 1941009 [details]
File: proc_pid_status

Comment 11 Aoife Moloney 2023-11-23 01:09:07 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Aoife Moloney 2024-01-12 22:37:31 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.