Package: command-not-found
Version: 20.10.1-1
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
When typing in the command "lsio" (in the same vein or spirit as "lscpu",
"lsmem", etc.), I get the following error:
----------
$ lsio
Sorry, command-not-found has crashed! Please file a bug report at:
http://www.debian.org/Bugs/Reporting
Please include the following information with the report:
command-not-found version: 0.3
Python version: 3.9.2 final 0
Distributor ID: Kali
Description: Kali GNU/Linux Rolling
Release: 2021.1
Codename: kali-rolling
Exception information:
unable to open database file
Traceback (most recent call last):
File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in
crash_guard
callback()
File "/usr/lib/command-not-found", line 90, in main
cnf = CommandNotFound.CommandNotFound(options.data_dir)
File "/usr/share/command-not-found/CommandNotFound/CommandNotFound.py", line
79, in __init__
self.db = SqliteDatabase(dbpath)
File "/usr/share/command-not-found/CommandNotFound/db/db.py", line 12, in
__init__
self.con = sqlite3.connect(filename)
sqlite3.OperationalError: unable to open database file
----------
Obviously, the result should've been a normal "command not found" error,
optionally pointing to a package or packages that contained a command with
the same spelling.
-- System Information:
Distributor ID: Kali
Description: Kali GNU/Linux Rolling
Release: 2021.1
Codename: kali-rolling
Architecture: x86_64
Kernel: Linux 5.10.0-kali5-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
nShell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages command-not-found depends on:
ii apt-file 3.2.2
ii lsb-release 11.1.0
ii python3 3.9.2-2
ii python3-apt 2.1.7
cnommand-not-found recommends no packages.
Versions of packages command-not-found suggests:
pn snapd <none>
n
-- no debconf information
Best,
Sean F. Leinen
