Bug 27470 - xlog-2.0.19 segfaults on launch
Summary: xlog-2.0.19 segfaults on launch
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Barry Jackson
QA Contact: Barry Jackson
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2020-10-26 23:46 CET by Barry Jackson
Modified: 2022-02-21 00:45 CET (History)
0 users

See Also:
Source RPM: xlog-2.0.19-1.mga8.src.rpm
CVE:
Status comment:

Attachments
backtrace (4.29 KB, text/plain)
2020-10-26 23:50 CET, Barry Jackson 		Details
strace output (341.08 KB, text/plain)
2020-10-26 23:54 CET, Barry Jackson 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Barry Jackson 2020-10-26 23:46:20 CET 
Description of problem:
As summary.

Reported upstream here:-
https://savannah.nongnu.org/bugs/index.php?59362

Version-Release number of selected component (if applicable):
xlog-2.0.19

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Barry Jackson 2020-10-26 23:50:17 CET 
Created attachment 11956 [details]
backtrace
Comment 2 Barry Jackson 2020-10-26 23:54:38 CET 
Created attachment 11957 [details]
strace output
Barry Jackson 2020-10-26 23:55:14 CET

Source RPM: xlog-2.0.19-1- => xlog-2.0.19-1.mga8.src.rpm
QA Contact: (none) => zen25000

Comment 3 Aurelien Oudelet 2020-10-27 00:00:43 CET 
Hi thanks reporting this.

Already assigned.
Already reported upstream.
Packager: please set status to Assigned when working on this.

Assignee: bugsquad => zen25000
Keywords: (none) => UPSTREAM

Comment 4 Barry Jackson 2020-10-29 21:41:51 CET 
I have tested this version in a new user and the problem does not exist, so it seems to be triggered by configs or logs created by the previous version.

Reduced bug severity until I can pin-point the culprit.

Severity: critical => normal

Comment 5 Barry Jackson 2022-02-21 00:45:21 CET 
Now works for me so closing.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.