Package: firejail
Version: 0.9.64.4-2
Severity: normal
X-Debbugs-Cc: debbug.firej...@sideload.33mail.com
Using Firejail to run reportbug sometimes works and sometimes
doesn’t. When it doesn’t work, it reports that it cannot find
emacs. Sample command:
$ firejail --env=EDITOR=/usr/bin/emacs\
--whitelist="$HOME"/.reportbugrc\
--whitelist=/etc/passwd\
--whitelist=/var/lib/apt/lists\
--whitelist=/var/lib/dpkg/status\
--whitelist=/etc/apt/sources.list\
--whitelist=/etc/apt/sources.d\
--whitelist=/etc/debian_version\
--whitelist="$draft_folder"\
/usr/bin/reportbug -b --no-check-available --email="$my_email"
--paranoid --draftpath="$draft_folder" --no-cc
Output:
===8<------------------------------
Reading profile /etc/firejail/default.profile
Reading profile /etc/firejail/disable-common.inc
Reading profile /etc/firejail/disable-passwdmgr.inc
Reading profile /etc/firejail/disable-programs.inc
** Note: you can use --noprofile to disable default.profile **
Parent pid 8934, child pid 8935
Warning: cleaning all supplementary groups
Warning: cleaning all supplementary groups
Warning: cleaning all supplementary groups
Child process initialized in 103.73 ms
Please enter the name of the package in which you have found a problem, or type
'other' to report a more general problem. If you don't know
what package the bug is in, please contact debian-u...@lists.debian.org for
assistance.
> firejail
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'anonymous coward <debbug.firej...@sideload.33mail.com>' as your from
address.
Getting status for firejail...
Will send report to Debian (per lsb_release).
Maintainer for firejail is 'Reiner Herrmann <rei...@reiner-h.de>'.
Looking up dependencies of firejail...
Getting changed configuration files...
Rewriting subject to 'firejail: profile needed for reportbug'
How would you rate the severity of this problem or report?
1 critical makes unrelated software on the system (or the whole system)
break, or causes serious data loss, or introduces a security
hole on systems where you install the package.
2 grave makes the package in question unusable by most or all users,
or causes data loss, or introduces a security hole allowing
access to the accounts of users who use the package.
3 serious is a severe violation of Debian policy (that is, the problem
is a violation of a 'must' or 'required' directive); may or
may not affect the usability of the package. Note that
non-severe policy violations may be 'normal,' 'minor,' or
'wishlist' bugs. (Package maintainers may also designate
other bugs as 'serious' and thus release-critical; however, end
users should not do so.). For the canonical list of issues
deserving a serious severity you can refer to this webpage:
http://release.debian.org/testing/rc_policy.txt .
4 important a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
5 does-not-build a bug that stops the package from being built from source.
(This is a 'virtual severity'.)
6 normal a bug that does not undermine the usability of the whole
package; for example, a problem with a particular option or menu
item.
7 minor things like spelling mistakes and other minor cosmetic errors
that do not affect the core functionality of the package.
8 wishlist suggestions and requests for new features.
Please select a severity level: [normal] 8
invalid report type None, defaulting to debbugs
Spawning emacs...
sh: 1: /usr/bin/emacs: not found
Warning: possible error exit from emacs: 32512
No changes were made in the editor.
Report will be sent to Debian Bug Tracking System <sub...@bugs.debian.org>
Submit this report on firejail (e to edit) [y|n|a|c|E|i|l|m|p|q|d|t|?]? q
Saving a backup of the report at
/tmp/reportbug-firejail-backup-20220623182047-x0toa9s3
Bug report written to $draft_folder/reportbug-firejail-20220623182039-7kfg55kv
Hint: You can resume an unsent report using reportbug -r TEMPFILE
Thank you for using reportbug
Parent is shutting down, bye...
===8<------------------------------
I saw this command correctly spawn emacs several times all on the same
day. Another day (after a reboot), reportbug running inside of firejail
consistently fails to spawn emacs. Rebooting should not have made a
difference. I don’t see how the state of the system can influence
this. I’m write this bug report herein using reportbug without
firejail, and reportbug spawns emacs fine every time when firejail is
not involved.
Note that there is another problem: before failing to find emacs,
reportbug reports “invalid report type None, defaulting to debbugs”
when in fact it did not prompt for a report type. Yet in the previous
session when firejail-reportbug was working, it correctly prompted for
the report type and got no error on that.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'testing'), (990, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firejail depends on:
ii libapparmor1 2.13.6-10
ii libc6 2.31-13
ii libselinux1 3.1-3
Versions of packages firejail recommends:
ii firejail-profiles 0.9.64.4-2
ii iproute2 5.10.0-4
ii iptables 1.8.7-1
ii xauth 1:1.1-1
ii xdg-dbus-proxy 0.1.2-2
ii xpra 3.0.13+dfsg1-1
ii xvfb 2:1.20.11-1
firejail suggests no packages.
-- Configuration Files:
/etc/firejail/firejail.config changed [not included]
-- no debconf information
