Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54427 - [smplayer] SIGABRT with latest qt5-base (5.9.0-1)

Attached to Project: Community Packages
Opened by A M (s3rb31) - Monday, 12 June 2017, 19:00 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 14 June 2017, 22:59 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

SMPlayer does not start with latest qt5-base (5.9.0-2) and qt5-script (5.9.0-1). It just aborts with the message "Aborted (core dumped)".

Downgrading qt5-base to 5.8.0-12 and qt5-script to 5.8.0-1 solves the issue.

Output:

>> $ smplayer
>> This is SMPlayer v. 17.6.0 (revision 8580) running on Linux
>> Aborted (core dumped)

Additional info:
* SMPlayer 17.6.0-1 (revision 8580)

Steps to reproduce:

Update qt, start 'smplayer' from terminal.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 14 June 2017, 22:59 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Config issue
Comment by Doug Newgard (Scimmia) - Tuesday, 13 June 2017, 00:46 GMT
No problem here. Get a backtrace.
Comment by Darek (blablo) - Tuesday, 13 June 2017, 07:46 GMT
No problem here also.
package version(s):
local/qt5-base 5.9.0-2 (qt qt5)
local/qt5-script 5.9.0-1 (qt qt5)
Comment by A M (s3rb31) - Wednesday, 14 June 2017, 21:29 GMT
Okay, I figured it out.

It seems like there was something wrong with one or more settings files
saved at '.config/smplayer/'. I removed the folder, and it works again.

Sorry for the hasty report, I should have tried that before opening the ticket.

Although there probably is a bug as newer versions shouldn't abort() on older
configurations but rather validate the input and exit gracefully with a proper
error message. :)

Greetings

Loading...