Bug 385325

Summary:	Ark does not open/extract a specific RAR file
Product:	[Applications] ark	Reporter:	Patrick Silva <bugseforuns>
Component:	plugins	Assignee:	Ragnar Thomsen <rthomsen6>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	elvis.angelaccio
Priority:	NOR
Version:	17.11.70
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	debug ark

Description Patrick Silva 2017-10-03 13:49:53 UTC

Neon dev unstable here...
Ark does not open/extract the rar file from the link below.
http://www.mediafire.com/file/hmosbw9wvnek4jg/extraction_fails.rar

Ark says "Loading the archive /home/username/extraction_fails.rar failed with the following error:
No suitable plugin found. Ark does not seem to support this file type."
And 'Extract..." is missing from dolphin context menu when I do right-click on the file.
I can open/extract this same file on windows 7 using bandizip.
Ark opens/extracts other rar files without any problem on my neon.

Comment 1 Elvis Angelaccio 2017-10-03 14:19:00 UTC

Works fine here. Please start ark from a terminal using:

    QT_LOGGING_RULES='ark.*.debug=true' ark

and attach here the output.

Comment 2 Patrick Silva 2017-10-03 14:30:23 UTC

Created attachment 108142 [details]
debug ark

Comment 3 Elvis Angelaccio 2017-10-03 14:36:01 UTC

Comment on attachment 108142 [details]
debug ark

>rk.main: Entering application loop
>ark.part: Attempting to open archive "/home/stalker/extraction_fails.rar"
>ark.kerfuffle: Going to create archive "/home/stalker/extraction_fails.rar"
>ark.kerfuffle: Mimetype for filename extension ( "application/x-rar" ) did not match mimetype for content ( "application/pdf" ). Using content-based mimetype.

That's the bug. This was fixed in shared-mime-info, but I guess the version in Neon/Ubuntu 16.04 is too old.
There is nothing we can do, either try to ask the Neon people to update shared-mime-info, or unpack the archive using unar/unrar from terminal.

Comment 4 Elvis Angelaccio 2017-10-03 14:37:21 UTC


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