Hi
I didn't have to wait long.
This freeze happened today after 2x Foxit Reader hung when trying to edit a pdf
document.
The cascade of lines like this"
/usr/lib/gdm3/gdm-x-session[4938]: (II) modeset(0): EDID vendor "BOE",
prod id 2391
is what I typically see when the freeze occurs.
Thanks. It appears there have been no relevant crash reports from that
machine:
https://errors.ubuntu.com/user/e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87
Next time a freeze happens, please:
1. Wait 10 seconds.
Thanks Daniel.
cat /var/lib/whoopsie/whoopsie-id
e85201b46e9f1cd63274a63c5926fbb947a65e98887bdffa63fc5cf3e1a51379df0326aa35c54b472f5bb7443a49964f84a569d7fb5efb75d5c48e5148695c87root@robert-msiLaptop:/home/rbrown#
--
You received this bug notification because you are a member of Ubuntu
Bugs,
What is the content of the file: /var/lib/whoopsie/whoopsie-id ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951683
Title:
Freeze
To manage notifications about this bug go to:
New crash today. Log attached.
cat /var/crash/kexec_cmd
/sbin/kexec -p -s --command-line="BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-89-generic
root=UUID=3405df65-a898-4ac8-86a0-474b4da9b724 ro rootflags=subvol=@ quiet
splash vt.handoff=7 reset_devices systemd.unit=kdump-tools-dump.service
nr_cpus=1
Preferably:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID
where ID is the content of file /var/lib/whoopsie/whoopsie-id on
the
Thanks Daniel. Your comments and help are much appreciated. The
attachments in #1 are all pre-nvidia when using Nouveau so not likely to
be relevant now. I will try and capture some new logs in case of another
freeze.
--
You received this bug notification because you are a member of Ubuntu
I can't see any crashes around the time before 12:50:17 but also if
you're using LXQt then I wouldn't know what programs to look for...
I suggest repeating the steps in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
in case the freeze is caused by
journalctl -b-1 > syslog2202-02-08A.txt ends at Feb 08 12:47:48
journalctl -b-2 > syslog2202-02-08C.txt starts at Feb 08 12:50:17 and ends at
Feb 08 16:11:54
I thought the crash happened before 12:50:17 and the start of the reboot
was a t 12:50:17 so the freeze should have been in the
Thanks again.
The log file in comment #9 appears to be older than where the log in
comment #6 ended. So comment #9 is from the wrong boot. Try using a
different number in the journalctl command.
Also _usr_bin_qlipper.1000.crash is probably not relevant here. We're
only interested in gnome-shell
Thanks.
syslog attached. but it seems to end too early(?).
ubuntu-bug YOURFILE.crash ran but it generated no new bug ID so how will
it be linked to this current bug report? Filemname was
/var/crash/_usr_bin_qlipper.1000.crash
** Attachment added: "syslog2202-02-08A.txt"
11 matches
Mail list logo
