The only crash-like problem I can see in those logs is:

  simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem)

which seems to be non-fatal for the Xorg process that triggered it. The
cause of that issue is also bug 2060268, but that too is not a crash. So
please follow these steps:

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 machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: gdm3 (Ubuntu) => ubuntu

** Changed in: ubuntu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2064037

Title:
  GDM session crashes after returning from a screen-off.

Status in Ubuntu:
  Incomplete

Bug description:
  I've written an AskUbuntu question about this:
  https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
  on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075

  Originally I thought it was gnome not respecting my setting to prevent
  locking the screen after idling, but after discussing the issue on
  matrix (https://matrix.to/#/!EJhpCQHHqqcNicfiql:xentonix.net/$kPbn-
  
fqDZgoG4s6PyQfki8tcSKJUpGH9QrXZSSV_vKY?via=decred.org&via=matrix.org&via=ubuntu.com)
  I think it is actually just a gdm or gnome-shell crash that happens
  when the PC idles, the screen turns off, and then I wake it.

  To summarize the symptom. I have the PC set to disable the screen
  after being idle for 5 minutes. I also set it such that it should not
  lock the session when this happens. (I want to turn on the screen and
  get right back to where I was without password overhead). What I've
  observed is that when I give the idle PC keyboard input, it wakes to a
  login screen, and when I login my windows from the previous session
  are completely gone (although tmux sessions are still alive).

  I've attached a relevant section of `journalctl --user` from around
  the time when I last tried to interact with the idle PC. I believe the
  "wake" event happens at `Apr 28 13:42:43` at which point we start
  seeing whoopsie messages:

  ```
  Apr 28 13:42:44 toothbrush systemd[1]: Started whoopsie.service - crash 
report submission.
  ```

  And then what looks like logs indicating that I was logged out and the
  previous session was ended:

  ```
  Apr 28 13:42:56 toothbrush systemd[1]: run-user-1000-gvfs.mount: Deactivated 
successfully.
  Apr 28 13:42:57 toothbrush gdm-password][60731]: 
pam_unix(gdm-password:session): session closed for user joncrall
  Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Deactivated 
successfully.
  Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Consumed 12min 
9.467s CPU time.
  Apr 28 13:42:57 toothbrush systemd-logind[1790]: Session 61 logged out. 
Waiting for processes to exit.
  Apr 28 13:42:57 toothbrush systemd-logind[1790]: Removed session 61.
  ```

  
  The time from `13:42:44` to `13:43:07` where I get:

  ```
  Apr 28 13:43:07 toothbrush systemd-logind[1790]: New session 221 of user 
joncrall.
  Apr 28 13:43:07 toothbrush systemd[1]: Started session-221.scope - Session 
221 of User joncrall.
  ```

  seems about right, because it takes a few seconds to go from de-idling
  the machine to seeing any sort of display.

  
  System Information:

  No LSB modules are available.
  Description:  Ubuntu 24.04 LTS
  Release:      24.04

  # System Details Report
  ---

  ## Report details
  - **Date generated:**                              2024-04-28 15:17:36

  ## Hardware Information:
  - **Hardware Model:**                              ASUS ROG STRIX Z590-E 
GAMING WIFI
  - **Memory:**                                      128.0 GiB
  - **Processor:**                                   11th Gen Intel® Core™ 
i9-11900K × 16
  - **Graphics:**                                    NVIDIA GeForce RTX™ 3090
  - **Graphics 1:**                                  NVIDIA GeForce RTX™ 3090
  - **Disk Capacity:**                               45.0 TB

  ## Software Information:
  - **Firmware Version:**                            0232
  - **OS Name:**                                     Ubuntu 24.04 LTS
  - **OS Build:**                                    (null)
  - **OS Type:**                                     64-bit
  - **GNOME Version:**                               46
  - **Windowing System:**                            X11
  - **Kernel Version:**                              Linux 6.8.0-31-generic

  
  Nvidia versions: 

  NVIDIA-SMI 535.171.04             Driver Version: 535.171.04   CUDA
  Version: 12.2

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 46.0-2ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 28 15:04:13 2024
  InstallationDate: Installed on 2024-04-25 (3 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2024-04-25T18:50:53.891514

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2064037/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to