Sorry, Apport definitely did not report enough information for us. There
are two independent things you can do. I recommend at least doing item
2, but doing both is better.
1. If you can, start chromium this way
snap run chromium --enable-logging=stderr --v=1 &> /tmp/chromium.log
and attach /t
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1997907/+attachment/5632855/+files/journal.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [Bug 1997596] Re: Chromium crashes without any apparent reason
+ [snap] trap invalid opcode
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Tried running journalctl -rn1000 > /tmp/journal.log, Returned error
"journalctl: invalid option -- '1'"
On Fri, Nov 25, 2022 at 7:10 AM Nathan Teodosio <1997...@bugs.launchpad.net>
wrote:
> Sorry, Apport definitely did not report enough information for us. There
> are two independent things you c
Weird. That is a documented option in man journalctl.
But anyway, -n1000 is just to show 1000 lines, the idea being we don't
want to upload the whole journal, a thousand lines should suffice.
You can do
journalctl -r | head -n 1000 > /tmp/journal.log
instead.
--
You received this bug noti
On Fri, Nov 25, 2022 at 4:35 PM Nathan Teodosio <1997...@bugs.launchpad.net>
wrote:
> Weird. That is a documented option in man journalctl.
>
> But anyway, -n1000 is just to show 1000 lines, the idea being we don't
> want to upload the whole journal, a thousand lines should suffice.
>
> You can do
6 matches
Mail list logo
