pysol.py crashed with ModuleNotFoundError in /usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py: No module named 'formatter'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pysolfc (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Pysolfc crashed. Updated packages this morning. Had worked last week. Using Xubuntu Noble Numbat 24.04 pre-release daily installed for tracking purposes last week.
~$ apt-cache policy pysolfc
pysolfc:
Installed: 2.6.4-3
Candidate: 2.6.4-3
Version table:
*** 2.6.4-3 500
500 http://
500 http://
500 http://
500 http://
500 http://
500 http://
500 http://
500 http://
500 https:/
500 https:/
100 /var/lib/
Application never resumed after crash.
A spreadsheet from LibreOffice Calc, and 3 tabs open on Brave browser at time of crash.
Not a necessary application, but I like to play the Shisen-Sho option while waiting for updates or listening to podcasts.
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: pysolfc 2.6.4-3
ProcVersionSign
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: XFCE
Date: Fri Nov 17 10:26:24 2023
ExecutablePath: /usr/share/
InstallationDate: Installed on 2023-11-11 (6 days ago)
InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231111)
InterpreterPath: /usr/bin/python3.11
JournalErrors: -- No entries --
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/games/pysolfc
ProcEnviron:
LANG=en_US.UTF-8
LANGUAGE=en_US
PATH=(custom, user)
SHELL=/bin/bash
XDG_RUNTIME_
Python3Details: /usr/bin/
PythonArgs: ['/usr/
PythonDetails: N/A
SourcePackage: pysolfc
Title: pysol.py crashed with ModuleNotFoundError in /usr/share/
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1964387, so 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. Please continue to report any other bugs you may find.