Yeah, you might be right. I just tried to reproduce the effect but I haven't found a reliable way to make an application crash in a way that a crash report is written (by itself that's a good thing *sight*). I tried so send some signals that trigger core dumps, but they left no crash reports in /var/crash.
So I tried apport-cli --file-bug on some running program and it works as expected when run as my unprivileged user but it fails to open a web browser tab/window when being run as root. This seems closely related to bug #198694, so I decided to hijack that bug instead of opening a new one. I can not recall if I was running apport-cli as root or not when I wrote the above comment, but I think / hope that I have only done that if I was asked to do so by apport-cli. -- apport should use whichever browser is open rather than using preferred browser https://bugs.launchpad.net/bugs/202502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
