Ctrl + c (copy) anywhere some times crashes gnome session

[Boris Rybalkin]

Copy text anwyhere (browser, terminal) crashes user session and shows login screen.
It may take few login attempts to actually login back.

I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 19 20:55:37 2019
DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057]
InstallationDate: Installed on 2019-07-21 (121 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
 Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
 Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Shuttle Inc. XH270
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
dmi.bios.date: 01/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02
dmi.board.asset.tag: Default string
dmi.board.name: FH270
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X
dmi.product.name: XH270
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Shuttle Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-07-21 (213 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
Tags: eoan
Uname: Linux 5.3.0-29-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Boris Rybalkin (ribalkin)]

It happened around this time (journalctl.log):

Nov 19 20:38:00 tv xdg-desktop-por[3284]: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Nov 19 20:38:00 tv gdm-password][1338]: pam_unix(gdm-password:session): session closed for user tv
Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Nov 19 20:38:00 tv pulseaudio[3108]: X connection to :0 broken (explicit kill or server shutdown).
Nov 19 20:38:00 tv kernel: rfkill: input handler enabled

[Boris Rybalkin (ribalkin)]

attaching journalctl.log

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash 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.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

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.

[Boris Rybalkin (ribalkin)]

All I have in /var/crash is tbis, does not seem to be related:

tv@tv:~$ ll /var/crash/
total 2716
drwxrwsrwt 2 root whoopsie 4096 Dec 3 07:39 ./
drwxr-xr-x 15 root root 4096 Aug 8 08:05 ../
-rw-r----- 1 tv whoopsie 1828782 Nov 29 09:17 _usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 tv whoopsie 0 Nov 29 09:17 _usr_bin_gnome-shell.1000.upload
-rw------- 1 whoopsie whoopsie 37 Nov 29 09:17 _usr_bin_gnome-shell.1000.uploaded
-rw-r----- 1 tv whoopsie 932012 Nov 29 09:06 _usr_bin_mutter.1000.crash
-rw-r--r-- 1 tv whoopsie 0 Nov 29 09:04 _usr_bin_mutter.1000.upload
-rw------- 1 whoopsie whoopsie 37 Nov 29 09:05 _usr_bin_mutter.1000.uploaded

[Daniel van Vugt (vanvugt)]

That looks very relevant. Please follow ALL the steps in comment #5.

[Boris Rybalkin (ribalkin)]

Here are the links:

https://errors.ubuntu.com/oops/459a8e5c-1287-11ea-b753-fa163e102db1
https://errors.ubuntu.com/oops/1e72be06-1289-11ea-a63b-fa163ee63de6
https://errors.ubuntu.com/oops/de33adf4-19e1-11ea-b7a1-fa163e102db1

[Daniel van Vugt (vanvugt)]

Thanks. Unfortunately those don't have any stack traces so please wait till the problem happens again and repeat the above steps.

[Boris Rybalkin (ribalkin)]

Two more:

https://errors.ubuntu.com/oops/50e85af4-19fe-11ea-b10e-fa163e983629
https://errors.ubuntu.com/oops/94669eda-2034-11ea-a701-fa163ee63de6

[Daniel van Vugt (vanvugt)]

Thanks. The only information I can get from those is that in one of them the login screen crashed due to:

malloc_printerr (str=str@entry=0x7fa4a99a6148 "free(): corrupted unsorted chunks") at malloc.c:5332

AFAIK this does not generally happen to other people so there might be something unusual about your system. Please check that you don't have any Gnome Shell extensions installed, other than those provided by default with Ubuntu. If you do have any such extensions then please uninstall them all and retest. We need extensions to be fully uninstalled because even when disabled they can interfere with the system.

Also, please keep collecting and sending us more crash reports since we don't yet have a reliable pattern or a crash report that's clean enough to formally track.

[Boris Rybalkin (ribalkin)]

This one is definitely after the crash:
https://errors.ubuntu.com/oops/94669eda-2034-11ea-a701-fa163ee63de6

Strange thing that, file says Dec 16, 18:47:

tv@tv:/var/crash$ ll
total 22492
drwxrwsrwt 2 root whoopsie 4096 Dec 17 07:35 ./
drwxr-xr-x 15 root root 4096 Aug 8 08:05 ../
-rw-r----- 1 gdm whoopsie 23015251 Dec 16 18:47 _usr_bin_gnome-shell.123.crash
-rw-r--r-- 1 root whoopsie 0 Dec 16 18:47 _usr_bin_gnome-shell.123.upload
-rw------- 1 whoopsie whoopsie 37 Dec 16 18:48 _usr_bin_gnome-shell.123.uploaded

But report on my whoopsie page says:

Occurred Received Problem Type Program
2019-12-13 09:12 2019-12-16 18:12 UTC Crash gnome-shell

Uploaded file content is the same.

[Daniel van Vugt (vanvugt)]

Thanks. That gives us a more formal issue to track: bug 1856781:
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d

But not really.

The problem with heap corruption issues like this is that regardless of the root cause they will often look the same. So in this particular case we should not join the two bugs together. To find the root cause for your case please try adding:

  MALLOC_CHECK_=3

to your /etc/environment. Then reboot and send us more crash reports. The crashes you get after that should be slightly different, crashing in a different location more suggestive of the root cause of the bug.

Please also ensure you have UNINSTALLED all extensions.

[Daniel van Vugt (vanvugt)]

Correction:

To find the root cause for your case please try adding:

  MALLOC_CHECK_=3
  G_SLICE=always-malloc

to your /etc/environment.

[Boris Rybalkin (ribalkin)]

One more, I not sure if I have restarted after adding G_SLICE.

https://errors.ubuntu.com/oops/7d2f8154-2427-11ea-a97e-fa163e6cac46

[Daniel van Vugt (vanvugt)]

Thanks. That's definitely a crash and sounds related to memory corruption:

Dec 21 19:24:09 tv systemd[3388]: gnome-shell-x11.service: Main process exited, code=dumped, status=7/BUS
Dec 21 19:24:09 tv systemd[3388]: gnome-shell-x11.service: Failed with result 'core-dump'.

But unfortunately it does not include a stack trace for some reason so isn't usable. Maybe this is a problem with errors.ubuntu.com?

[Daniel van Vugt (vanvugt)]

Please also ensure you have UNINSTALLED all gnome-shell extensions.

[Daniel van Vugt (vanvugt)]

Actually, just to be sure, can you please now run:

  apport-collect 1853199

It should give us a slightly different set of attachments now.

[Boris Rybalkin (ribalkin)]

Crashed few times today and yesterday, /var/crash is empty :(

[Boris Rybalkin (ribalkin)]

Also I think at the same time Alt + F4 stops closing apps but instead switches to another console.

[Boris Rybalkin (ribalkin)]

This was actually ctrl + x inside libreoffice calc 100% reproducable (did 3 times in a row).

https://errors.ubuntu.com/oops/0a86d610-331b-11ea-b88b-fa163e102db1
https://errors.ubuntu.com/oops/615fd93e-3312-11ea-b1f4-fa163e983629
https://errors.ubuntu.com/oops/3279fd88-3188-11ea-a9c1-fa163e6cac46

[Daniel van Vugt (vanvugt)]

It seems the robots either can't or haven't yet got to providing analysis of those crash reports...

In the meantime, immediately after each crash happens please run:

  journalctl -b0 > journal.txt

and attach 'journal.txt' here.

If you have to reboot after each crash before you can run that command then please use this instead:

  journalctl -b-1 > prevjournal.txt

[Daniel van Vugt (vanvugt)]

Please also ensure you have UNINSTALLED all gnome-shell extensions.

[Boris Rybalkin (ribalkin)]

attached the output

[Boris Rybalkin (ribalkin)]

Another one

[Daniel van Vugt (vanvugt)]

Thanks for those. Please delete the files in your /var/crash/ directory. Then reproduce the bug again and we should have a better chance of seeing a clear crash report.

[Boris Rybalkin (ribalkin)]

1. removed the files
2. done ctrl + c
3. gnome restarted
4. had to repeat login for 10-20 times before gnome actually opened the desktop
5. /var/crash is empty :(

[Daniel van Vugt (vanvugt)]

Thanks. I can't find any usable info in that log right now, other than it was only yesterday that you deleted /var/crash/* so best to just wait for the next crash file from gnome-shell. Then follow comment #5 again.

Please also remember to keep the changes in comment #14.

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

apport information

[Boris Rybalkin (ribalkin)]

it stopped crashing for few days I think but then started again, so ran "apport-collect 1853199" to provide more info.

[Daniel van Vugt (vanvugt)]

Next time it happens please follow the steps in comment #5.

[Daniel van Vugt (vanvugt)]

Actually, comment #33 suggests the gnome-shell crash is benign:

[1203381.012425] tv gnome-shell[7509]: gnome-shell: Fatal IO error 4 (Interrupted system call) on X server :0.

So it sounds like Xorg is crashing and that's the main problem.

[Boris Rybalkin (ribalkin)]

Actually there is one crash file from gnome you are right:
https://errors.ubuntu.com/oops/071369c4-5364-11ea-a0ab-fa163e6cac46

[Boris Rybalkin (ribalkin)]

I am actually typing this comment form Ubuntu on Wayland, should it help?

[Boris Rybalkin (ribalkin)]

XWayland does not have this issue for me.

[Daniel van Vugt (vanvugt)]

The link in comment #38 doesn't seem to have any error link so we can't use that.

Next time it happens please follow the steps in comment #5.

[Boris Rybalkin (ribalkin)]

Issues sill happens even in XWayland session :(
No crash dumps yet.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Boris Rybalkin (ribalkin)]

I think this is exactly my problem: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/comments/1

From time to time my keyboard switches to a mode when alt + f1 starts to switch me to console.
The bug comment also mentions Ctrl+C killing the GUI.

[Boris Rybalkin (ribalkin)]

Please reopen the bug it is not working.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash 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.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

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.

[Boris Rybalkin (ribalkin)]

Fresh install of 20.04 fixed the issue.
Probably previously I had something installed which was triggering it.