Ubuntu
anki package

Anki crash at starts with unsupported QT library version

Bug #1796273 reported by Nicolas Michel on 2018-10-05

This bug report is a duplicate of: Bug #1786631: anki 2.1.0: fails to start. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	anki (Ubuntu)	New	Undecided	Unassigned

Bug Description

Installing Anki from the repository in Ubuntu 18.10 makes the application crashing because of a mismatch of QT library (5.9 required by Anki upstream, and built with 5.11). Going further make the application crashing.

Installing the application from the tarball downloadable from the website works.

Maybe Anki should be converted also to snap?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: anki 2.1.0+dfsg-1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 5 13:39:59 2018
InstallationDate: Installed on 2017-09-17 (383 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
PackageArchitecture: all
SourcePackage: anki
UpgradeStatus: Upgraded to cosmic on 2018-10-02 (2 days ago)

Tags:

Revision history for this message

Nicolas Michel (be-nicolas-michel) wrote on 2018-10-05:

Screenshot from 2018-10-05 13-43-01.png Edit (48.9 KiB, image/png)
Dependencies.txt Edit (11.0 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (328 bytes, text/plain; charset="utf-8")

Revision history for this message

Nicolas Michel (be-nicolas-michel) wrote on 2018-10-05:

Screenshot from 2018-10-05 13-42-43.png Edit (60.8 KiB, image/png)

QT error message when launching Anki

Revision history for this message

Hans Joachim Desserud (hjd) wrote on 2018-10-06:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1786631, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.