Nautilus crash on filtering files over samba mount points

[Antonio Ruiz Gómez]

When I open Nautilus and navigate over a samba mount point and do this, nautilus crashes:
1. Go to a samba mount point
2. Start typing something to filter results
3. Drag mouse to select all the text you have typed
4. Start typing again to change filter and nautillus crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 18 09:47:35 2020
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'206'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1133, 727)'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']"
InstallationDate: Installed on 2020-10-29 (19 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

[Antonio Ruiz Gómez (aruizgomez)]

Hi,
I have made step 1 with the file "_usr_bin_nautilus.1151801627.crash" found
in /var/crash
The command "ubuntu-bug <crashfile>" has sent a report but i don't know
where to find the ID of the newly created bug. The system hasn't tell me
anything.
On the other hand, as you instructed in step 2, the links of the nautilus
reports are:
https://errors.ubuntu.com/oops/f58ac652-2fc2-11eb-8c7d-fa163e983629
https://errors.ubuntu.com/oops/daa39c7a-2e51-11eb-8be3-fa163e983629
https://errors.ubuntu.com/oops/f53bc03e-2e50-11eb-82f1-fa163e6cac46
https://errors.ubuntu.com/oops/ce79ed26-2b27-11eb-b7ac-fa163e102db1
https://errors.ubuntu.com/oops/e6cc764e-28cc-11eb-899e-fa163e983629
https://errors.ubuntu.com/oops/9af44cfc-27f6-11eb-b62f-fa163e102db1
https://errors.ubuntu.com/oops/a9b08fc7-25b2-11eb-8857-fa163e983629
https://errors.ubuntu.com/oops/753baa02-1ea6-11eb-b2a0-fa163e102db1
https://errors.ubuntu.com/oops/bda174d3-1a97-11eb-8422-fa163e983629

El mar., 24 nov. 2020 a las 14:30, Sebastien Bacher (<
<email address hidden>>) escribió:

> 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.
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1904709
>
> Title:
> Nautilus crash on filtering files over samba mount points
>
> Status in nautilus package in Ubuntu:
> Invalid
>
> Bug description:
> When I open Nautilus and navigate over a samba mount point and do this,
> nautilus crashes:
> 1. Go to a samba mount point
> 2. Start typing something to filter results
> 3. Drag mouse to select all the text you have typed
> 4. Start typing again to change filter and nautillus crash
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: nautilus 1:3.36.3-0ubuntu1
> ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
> Uname: Linux 5.4.0-54-generic x86_64
> ApportVersion: 2.20.11-0ubuntu27.12
> Architecture: amd64
> CasperMD5CheckResult: skip
> CurrentDesktop: ubuntu:GNOME
> Date: Wed Nov 18 09:47:35 2020
> GsettingsChanges:
> b'org.gnome.nautilus.window-state' b'sidebar-width' b'206'
> b'org.gnome.nautilus.window-state' b'initial-size' b'(1133, 727)'
> b'org.gnome.nautilus.list-view'...

[Sebastien Bacher (seb128)]

Thanks, sounds like the issue you hit there is bug #1869404 so I'm marking it duplicate

One other error in the reports was bug #1905697