Bug 2101096 - [abrt] bottles: mem_error(): python3.10 killed by SIGABRT
Summary: [abrt] bottles: mem_error(): python3.10 killed by SIGABRT
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bottles
Version: 36
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Artem
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:be3aaac7081c6dfca51a3df122f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-25 12:56 UTC by newnick
Modified: 2022-10-27 12:20 UTC (History)
2 users (show)

Fixed In Version: bottles-2022.7.14-1.fc36
Clone Of:
Environment:
Last Closed: 2022-10-27 12:20:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (249.45 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: core_backtrace (27.26 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: cpuinfo (2.61 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: environ (1.18 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: limits (1.29 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: maps (3.99 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: mountinfo (3.07 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: open_fds (2.34 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
File: proc_pid_status (1.39 KB, text/plain)
2022-06-25 12:56 UTC, newnick 		no flags Details
View All

Description newnick 2022-06-25 12:56:45 UTC 
Version-Release number of selected component:
bottles-2022.5.28-2.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-com.usebottles.bottles-59168.scope
cmdline:        /usr/bin/python3 /usr/bin/bottles
crash_function: mem_error
dso_list:       /usr/bin/python3.10 python3-3.10.5-2.fc36.x86_64 (Fedora Project) 1655901923
executable:     /usr/bin/python3.10
journald_cursor: s=9c0ae3b868cc4708b1f98a36e4fcf3cb;i=ada7b;b=33f4b084c1d0405d8dccd82e70e8085f;m=113e4d4833;t=5e244dc7a78ac;x=67d5c9b4477f3ac2
kernel:         5.18.5-200.fc36.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 1 newnick 2022-06-25 12:56:48 UTC 
Created attachment 1892692 [details]
File: backtrace
Comment 2 newnick 2022-06-25 12:56:50 UTC 
Created attachment 1892693 [details]
File: core_backtrace
Comment 3 newnick 2022-06-25 12:56:51 UTC 
Created attachment 1892694 [details]
File: cpuinfo
Comment 4 newnick 2022-06-25 12:56:52 UTC 
Created attachment 1892695 [details]
File: environ
Comment 5 newnick 2022-06-25 12:56:53 UTC 
Created attachment 1892696 [details]
File: limits
Comment 6 newnick 2022-06-25 12:56:54 UTC 
Created attachment 1892697 [details]
File: maps
Comment 7 newnick 2022-06-25 12:56:56 UTC 
Created attachment 1892698 [details]
File: mountinfo
Comment 8 newnick 2022-06-25 12:56:57 UTC 
Created attachment 1892699 [details]
File: open_fds
Comment 9 newnick 2022-06-25 12:56:58 UTC 
Created attachment 1892700 [details]
File: proc_pid_status
Comment 10 Fedora Update System 2022-10-25 05:13:50 UTC 
FEDORA-2022-14524d28ef has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-14524d28ef
Comment 11 Fedora Update System 2022-10-25 13:17:05 UTC 
FEDORA-2022-14524d28ef has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-14524d28ef`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-14524d28ef

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 12 Fedora Update System 2022-10-27 12:20:08 UTC 
FEDORA-2022-14524d28ef has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.