nautilus segfault libgio-2.0.so.0.6600.1

[Hassan El Jacifi]

Hi Guys,

Some nautilus segfaulting:

[ 3337.426167] nautilus[7770]: segfault at 20 ip 00007f987a903844 sp 00007fffeb101b08 error 4 in libgio-2.0.so.0.6600.1[7f987a852000+119000]

[ 5551.902495] nautilus[10777]: segfault at 20 ip 00007f7c0c502844 sp 00007ffe513a3178 error 4 in libgio-2.0.so.0.6600.1[7f7c0c451000+119000]

Packages:

libnautilus-extension1a:amd64 1:3.38.1-1ubuntu1
nautilus 1:3.38.1-1ubuntu1
nautilus-data 1:3.38.1-1ubuntu1
nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
nautilus-sendto 3.8.6-3
nautilus-share 0.7.3-2ubuntu3

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: nautilus 1:3.38.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.1
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Tue Nov 24 12:37:57 2020
InstallationDate: Installed on 2018-01-01 (1057 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
SourcePackage: nautilus
UpgradeStatus: Upgraded to groovy on 2019-10-19 (401 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-01-18T18:05:44.880717
usr_lib_nautilus:
 evince 3.38.0-1
 file-roller 3.38.0-1
 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1
 nautilus-share 0.7.3-2ubuntu3

[Sebastien Bacher (seb128)]

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.

[Hassan El Jacifi (waver)]

Hi Sebastien,

As requested, you can find the apport report here "https://errors.ubuntu.com/oops/0f82c2e1-3053-11eb-b9cb-fa163e102db1"

Do you also need my Whoopsie-id ?

Best regards,

[Sebastien Bacher (seb128)]

Thanks and no I don't need the id, the report information indicates it's bug #1820859

[Sebastien Bacher (seb128)]

Could you perhaps describe what you did to trigger the segfault and if you are able to trigger the problem again following some steps?