Saving a file in gedit crashes desktop to login screen

[8765pu]

When saving a file in gedit (or whatever the default text editor is) it crashes my entire desktop, and I end up on the login screen.

ubuntu 20.10
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DisplayManager: sddm
DistroRelease: Ubuntu 20.10
InstallationDate: Installed on 2020-10-30 (36 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
NonfreeKernelModules: wl
Package: gnome-shell 3.38.1-1ubuntu1.1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17
RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1
Tags: wayland-session groovy
Uname: Linux 5.8.0-31-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1906919

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

I tried, but I apparently used the wrong account and now it just refuses every time.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

apport information

[8765pu (8765pukxbhc876y-deactivatedaccount)]

apport information

[8765pu (8765pukxbhc876y-deactivatedaccount)]

apport information

[8765pu (8765pukxbhc876y-deactivatedaccount)]

apport information

[8765pu (8765pukxbhc876y-deactivatedaccount)]

apport information

[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.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

Thank you for demonstrating interest. Here is the link that you requested:

https://errors.ubuntu.com/oops/b287c9e0-3850-11eb-86ea-fa163e6cac46

More info:
The crash only happens when saving a file residing on the desktop. Upon saving, the entire desktop blinks, suggesting some heavy-handed graphics operation upon modifying a desktop file. The first time this occurred I got a glimpse of some console output mentioning "iXXX" where X were digits, which reminded me of the name of Intel graphics drivers.

The crash can be reproduced by saving approximately 10 times, or by just holding down Ctrl+S (gedit allows saving an unedited document, for some reason).

[Daniel van Vugt (vanvugt)]

Thanks. It looks like the robots haven't yet analysed that one so I will need to wait.

In the meantime, after each crash please run:

  journalctl -b0 > journal.txt

or if you had to reboot then run:

  journalctl -b-1 > prevjournal.txt

and attach the resulting file here.

Also if you encounter any more crashes then please use the steps in comment #8 again.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

I can recreate the crash at will so I can do that zero to many times depending on what you need.

[Daniel van Vugt (vanvugt)]

Maybe a couple would be most helpful, please.

[Daniel van Vugt (vanvugt)]

I still don't have any data to analyse here but the test case sounds similar to my test case for bug 1898005. So I am guessing this will be a duplicate of that.

[8765pu (8765pukxbhc876y-deactivatedaccount)]

A glance through journal.txt did not give me confidence that it wasn't bleeding all sorts of info, since my name was on every line.

Here's a relevant excerpt:

```
                                               _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
                                               _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-PG8WU0”: Filen eller katalogen finns inte
dec 07 11:53:27 computer-name gnome-shell[1606]: libinput error: event5 - bcm5974: client bug: event processing lagging behind by 17ms, your system is too slow
dec 07 11:53:27 computer-name gnome-shell[1606]: JS ERROR: TypeError: fileItem is undefined
                                               _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:418:17
                                               _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340:94
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns inte
dec 07 11:53:27 computer-name gnome-shell[1606]: Error getting desktop unix mode: Gio.IOErrorEnum: Fel vid hämtning av information om filen ”/home/username/Skrivbord/.goutputstream-TOKPU0”: Filen eller katalogen finns inte
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent == NULL' failed
dec 07 11:53:28 computer-name gnome-shell[1606]: clutter_actor_add_child: assertion 'child->priv->parent =...

[8765pu (8765pukxbhc876y-deactivatedaccount)]

So where can one find the desktopManager.js file that would need the fix? I can't find a single mention online of where system bundled gnome extensions are located.

[Daniel van Vugt (vanvugt)]

Thanks for that. It confirms this is a duplicate of bug 1898005.