After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781344 - Searching for blank search term causes crash
Searching for blank search term causes crash
Status: RESOLVED DUPLICATE of bug 777214
Product: nautilus
Classification: Core
Component: File Search Interface
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-04-15 15:07 UTC by krinkodot22
Modified: 2017-04-16 06:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description krinkodot22 2017-04-15 15:07:45 UTC 
Searching for a blank search term while no item is selected causes Nautilus to crash with a SIGSEGV.

To reproduce, first make sure that no file/folder is selected. Then, enter the Search bar (like with Ctrl+F), and then either
-press Enter, or
-type something in the Search bar, clear the search term, and then press Enter.
Comment 1 Alexandru Pandelea 2017-04-15 16:34:07 UTC 
Hi! Can you please check what version of Nautilus you have?
This bug was fixed in bug 777214 and I can't reproduce it anymore, so your version of Nautilus might not have that patch
Comment 2 Ernestas Kulik 2017-04-15 16:42:03 UTC 
(In reply to Alexandru Pandelea from comment #1)
> Hi! Can you please check what version of Nautilus you have?
> This bug was fixed in bug 777214 and I can't reproduce it anymore, so your
> version of Nautilus might not have that patch

Backported it to 3.22 just now. I don’t think another 3.22 release is going to happen anytime soon, so it would be best to have the packager work the patch in (or upgrade to 3.24) (if this bug indeed is duplicate).
Comment 3 krinkodot22 2017-04-15 22:00:49 UTC 
I am using Nautilus 3.22.3.

And yes, this is a duplicate of bug 777241 after all. If I had found that bug posting, I wouldn't have filed this one. Sorry for the dup.

Also, if the fix for this bug had to be backported to 3.22, what version was it originally fixed for? Bug 777241 is marked under version 3.22, so wouldn't the fix already have been present in 3.22? (This isn't an issue for me, I'm just curious.)

*** This bug has been marked as a duplicate of bug 777241 ***
Comment 4 Ernestas Kulik 2017-04-16 06:00:58 UTC 
(In reply to krinkodot22 from comment #3)
> I am using Nautilus 3.22.3.
> 
> And yes, this is a duplicate of bug 777241 after all. If I had found that
> bug posting, I wouldn't have filed this one. Sorry for the dup.
> 
> Also, if the fix for this bug had to be backported to 3.22, what version was
> it originally fixed for? Bug 777241 is marked under version 3.22, so
> wouldn't the fix already have been present in 3.22? (This isn't an issue for
> me, I'm just curious.)

The bug was fixed for 3.24, since it was during its development cycle. What happens usually is that the fix is cherry-picked into the stable branch as well, but it appears to not have happened.

> *** This bug has been marked as a duplicate of bug 777241 ***

*** This bug has been marked as a duplicate of bug 777214 ***