mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2212] firefox: cannot create crash dump and send crash report after crash #1484
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1484
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @juxi500 on GitHub (Oct 23, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2212
Hello, I noticed that when I am running Firefox inside firejail, when Firefox crashes, it is not able to create crash dump and send crash report to Mozilla. Is it intended behaviour or do I have something misconfigured? If you need any more information just let me know.
Thank you very much and have a nice day! :)
@Vincent43 commented on GitHub (Oct 23, 2018):
Generally speaking, it's intended.. It may be caused by
apparmor(if your distro has apparmor support like ubuntu) or maybenodbus. If you need crash report you may try to addignorerule for that options infirefox.localor in command line.@SkewedZeppelin commented on GitHub (Oct 23, 2018):
@Vincent43 I think it is either caps or seccomp, I've seen it happen many times.
@juxi500 commented on GitHub (Oct 23, 2018):
I use EL7 so I have SeLinux instead of AppArmor... Ok so if I want to disable nodbus I will try ignore nodbus option...? :) Is it a big security risk?
@juxi500 commented on GitHub (Oct 23, 2018):
Is it possible to somehow tell caps or seccomp to let Firefox send crash reports or should I disable them?
@crass commented on GitHub (Oct 25, 2018):
@juxi500 It would be nice if you can find a situation where you can reliably create a crash report in firefox without using firejail (perhaps using one of these suggestions). Then follow these steps:
audit: type=1326 audit(1539671071.136:146): auid=666 uid=0 gid=0 ses=2 subj==unconfined pid=18184 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=c000003e syscall=8 compat=0 ip=0x7fd821118cd7 code=0x0.seccompis not currently preventing the crash reporter.firejail --debug-syscallsfor the syscall number identified in the audit line (lseekin the above example).--seccomp.keep=<syscall name>[,<syscall name>], where a comma separated list of all syscall names that you've found in the audit messages are given, and do the crash againWe should add a
firefox-common-crashreporter.profileto be included with the other firefox profiles like we do with thefirefox-common-addons.profile.@juxi500 commented on GitHub (Oct 30, 2018):
Well I will try but the "problem" is I can't reliably crash Firefox... :) In my experience it is pretty stable these days (I was looking for reliable way already)... But when I will encounter a crash and I will see something like this in command line I will let you know :)
@juxi500 commented on GitHub (Nov 3, 2018):
Today I managed to crash Firefox, with caps, seccomp and nodbus ignored, but still it can not send crash reports. (When run without firejail, it is possible to send crash reports)
$ firejail --ignore=seccomp --ignore=caps --ignore=nodbus /home/user/firefox-beta/firefoxReading profile /etc/firejail/firefox.profileReading profile /etc/firejail/firefox.localReading profile /etc/firejail/firefox-common.profileReading profile /etc/firejail/disable-common.incReading profile /etc/firejail/disable-devel.incReading profile /etc/firejail/disable-interpreters.incReading profile /etc/firejail/disable-programs.incReading profile /etc/firejail/whitelist-common.incReading profile /etc/firejail/whitelist-var-common.incParent pid 10261, child pid 10262Post-exec seccomp protector enabledSeccomp list in: @clock,@cpu-emulation,@debug,@module,@obsolete,@raw-io,@reboot,@resources,@swap,acct,add_key,bpf,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,ni_syscall,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount,umount2,userfaultfd,vhangup,vmsplice, check list: @default-keep, prelist: adjtimex,clock_adjtime,clock_settime,settimeofday,modify_ldt,lookup_dcookie,perf_event_open,process_vm_writev,delete_module,finit_module,init_module,_sysctl,afs_syscall,create_module,get_kernel_syms,getpmsg,putpmsg,query_module,security,sysfs,tuxcall,uselib,ustat,vserver,ioperm,iopl,kexec_load,kexec_file_load,reboot,set_mempolicy,migrate_pages,move_pages,mbind,swapon,swapoff,acct,add_key,fanotify_init,io_cancel,io_destroy,io_getevents,io_setup,io_submit,ioprio_set,kcmp,keyctl,mount,name_to_handle_at,nfsservctl,open_by_handle_at,personality,pivot_root,process_vm_readv,ptrace,remap_file_pages,request_key,setdomainname,sethostname,syslog,umount2,userfaultfd,vhangup,vmsplice,Child process initialized in 77.80 ms[Parent 7, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 736ExceptionHandler::GenerateDump cloned child ExceptionHandler::WaitForContinueSignal waiting for continue signal...427ExceptionHandler::SendContinueSignalToChild sent continue signal to child [Child 117, Chrome_ChildThread] WARNING: pipe error: Broken pipe: file /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 7362018-11-03 13:40:07: minidump.cc:5094: ERROR: Minidump could not open minidump /home/user/.mozilla/firefox/12345678.default/minidumps/07bb2bc7-0418-a12a-3706-2a51fa5f2b47.dmp, error 2: No such file or directory2018-11-03 13:40:07: minidump.cc:5191: ERROR: Minidump cannot open minidump Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.Parent is shutting down, bye...Please do you have some ideas what could be the problem?
If you need any more information just let me know.
Have a nice day :)
@chiraag-nataraj commented on GitHub (May 20, 2019):
It's most likely the seccomp filter, but I don't know. Is this still an issue?
@matu3ba commented on GitHub (Jun 21, 2019):
@juxi500 Please provide feedback.
Otherwise this should be closed.
@rusty-snake commented on GitHub (Aug 22, 2019):
@juxi500 I'm closing here due to inactivity, please fell free to reopen if you still have this issue.
@byteit101 commented on GitHub (Feb 1, 2020):
I was able to reproduce this. I seem to be stuck hitting https://crash-stats.mozilla.org/signature/?product=Firefox&signature=mozilla%3A%3Aa11y%3A%3ADOMtoATK%3A%3AATKStringConverterHelper%3A%3AFinishUTF16toUTF8 every few days, so I'll try adding those flags and reporting back in a few days when I invariably hit that again
@rusty-snake commented on GitHub (Feb 1, 2020):
@byteit101 if @chiraag-nataraj is right, you can find the blocked syscall with
journalctl --grep=SECCOMP.@byteit101 commented on GitHub (Feb 12, 2020):
hmm, my journalctl was:
Compiled without pattern matching support
but this is what appeared:
(about 150 lines in total of this repeating)
@rusty-snake commented on GitHub (Feb 12, 2020):
You can also try it with
journalctl | grep SECCOMP, however this error is about AppArmor, has you enabled the debian AA profile for firefox or is it just the firejail one?@Vincent43 commented on GitHub (Feb 12, 2020):
@byteit101 could you show
firejail --versionoutput?@byteit101 commented on GitHub (Feb 14, 2020):
I think the AA profile was enabled automatically when I upgraded to debian 10
@Vincent43 commented on GitHub (Feb 14, 2020):
@byteit101 try adding:
ptrace (trace,tracedby) peer=@{profile_name},line in/etc/apparmor.d/local/firejail-defaultthen runsystemctl restart apparmoror reboot.@rusty-snake commented on GitHub (Feb 14, 2020):
ptraceis also blocked by firejails seccomp filter, you should also addallow-debuggers.@byteit101 commented on GitHub (Feb 17, 2020):
I added @Vincent43's ptrace line to apparmor, and running with:
firejail --ignore=seccomp --ignore=caps --ignore=nodbus firefoxI got the Mozilla crash dialog and was able to send a report!@rusty-snake commented on GitHub (Feb 19, 2020):
Are all ignores needed? Can you try with
firejail --allow-debuggers --ignore=caps --ignore=nodbus firefox.@byteit101 commented on GitHub (Feb 23, 2020):
firejail --ignore=seccomp --ignore=caps --ignore=nodbus firefoxshows the dialogfirejail --allow-debuggers --ignore=caps --ignore=nodbus firefoxshows the dialogfirejail --allow-debuggers firefoxshows the dialogfirejail firefoxdoesn't show the dialog@rusty-snake commented on GitHub (Feb 23, 2020):
To summary:
firejail --allow-debuggers firefoxor
firejail --seccomp.drop=@default --ignore=seccomp firefoxor
firejail '--seccomp=!ptrace' firefoxand
@Vincent43 AA rule for apparmor users
@byteit101 commented on GitHub (Feb 23, 2020):
Correct