Bug 1796072 - [abrt] createrepo_c: g_mutex_unlock(): createrepo_c killed by SIGSEGV
Summary: [abrt] createrepo_c: g_mutex_unlock(): createrepo_c killed by SIGSEGV
Keywords:
Status: CLOSED DUPLICATE of bug 1795052
Alias: None
Product: Fedora
Classification: Fedora
Component: createrepo_c
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL: http://localhost/faf/reports/bthash/e...
Whiteboard: abrt_hash:824e619c67979111bae927b795d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-29 14:35 UTC by Martin Kutlak
Modified: 2020-01-29 14:37 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-01-29 14:37:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (22.50 KB, text/plain)
2020-01-29 14:35 UTC, Martin Kutlak
no flags Details

Description Martin Kutlak 2020-01-29 14:35:53 UTC
Description of problem:
Run createrepo_c --xz --deltas /var/tmp/local_repo

Version-Release number of selected component:
createrepo_c-0.15.5-1.fc32

Additional info:
reporter:       libreport-2.11.3
backtrace_rating: 4
cmdline:        createrepo --xz --deltas /var/tmp/local_repo/
crash_function: g_mutex_unlock
executable:     /usr/bin/createrepo_c
journald_cursor: s=0a60c0fc72ce4c1da58f325e8a0cf008;i=1d758;b=415200eb183042e798efddcb52707dd6;m=152bbe6c5;t=59d48201be35d;x=90c80973f9f5a37
kernel:         5.5.0-0.rc6.git3.1.fc32.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_mutex_unlock at ../glib/gthread-posix.c:1477
 #1 g_cond_wait at ../glib/gthread-posix.c:1526
 #2 g_thread_pool_start_thread at ../glib/gthreadpool.c:488
 #3 g_thread_pool_push at ../glib/gthreadpool.c:688

Comment 1 Martin Kutlak 2020-01-29 14:35:57 UTC
Created attachment 1656284 [details]
File: backtrace

Comment 2 Martin Kutlak 2020-01-29 14:37:07 UTC

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


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