Bug 1297632

Created attachment 1113838 [details]
File: backtrace

Created attachment 1113839 [details]
File: cgroup

Created attachment 1113840 [details]
File: core_backtrace

Created attachment 1113841 [details]
File: dso_list

Created attachment 1113842 [details]
File: environ

Created attachment 1113843 [details]
File: limits

Created attachment 1113844 [details]
File: maps

Created attachment 1113845 [details]
File: mountinfo

Created attachment 1113846 [details]
File: namespaces

Created attachment 1113847 [details]
File: open_fds

Created attachment 1113848 [details]
File: proc_pid_status

Created attachment 1113849 [details]
File: var_log_messages

I just hit this. It seems like an especially nasty bug, because it can cause data loss.

What happened was that I wanted to save a document. I chose the directory I wanted to go in, and was trying to type the file name I wanted it to have. For some reason, GTK+ decided I was typing a search string within the list of existing files in the directory - I don't know exactly what happened there, it's certainly not what I wanted. I then changed focus to the filename text entry box and typed the desired file name again, but I couldn't save, because the Save button isn't available when there's a search active and it returns no results(?), which seems like a bug in itself.

So I switched back to the search text entry, blanked it out, and hit enter; this did not clear the search and return the full file list, which seems like *another* bug in itself. So I typed a single space character and pressed enter (which is my usual trick for fixing recalcitrant search boxes), then tried to go back to the filename text entry box. At some point there, the crash happened.

So I got the frustration of a misbehaving save dialog, and then I lost the notes I just spent a half hour writing. Great.

Another user experienced a similar problem:

Hello,
the crash happened to my NAS while saving a text about " SAMBA ".
Since upgrading from Fedora 22 to Fedora 23 I can " gedit " text in newly created not
save on my NAS. It appears the attached error message.
thank you
Jürgen
(Excuse for my bad English, it is the result of a translator's programme)

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/gedit --gapplication-service
crash_function: get_display_name_from_file_list
executable:     /usr/bin/gedit
global_pid:     16865
kernel:         4.3.3-303.fc23.x86_64
package:        gedit-3.18.3-1.fc23
reason:         gedit killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            1000

Hello,
since today storing away an anew provided text functions in "gedit" on my NAS again.
Unfortunately, the cause is not known to me. After problems with gnome and next Updats this problem is removed.
Thanks
Jürgen 
(Excuse for my bad English, it is the result of a translator's programme)

*** Bug 1289041 has been marked as a duplicate of this bug. ***

*** Bug 1294332 has been marked as a duplicate of this bug. ***

*** Bug 1294681 has been marked as a duplicate of this bug. ***

Moving to gtk+ as this can be reproduced in filechooser dialogs in various applications.

Steps I use to reproduce:
- mkdir ~/test
- touch ~/test/foo
- start gedit
- press save button
- navigate to ~/test
- click on 'foo' in the file list
- type 'foo' to trigger the search bar
- click in the toplevel 'name' text entry
- type 'bar'
  -> the save button becomes grayed out
- click on 'foo' in the file list
- press the save button
  -> crash

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.