| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
This reverts commit fe1965f2cafc4616caaea0ae048bf1ff5c8975f5.
|
|
|
|
|
|
|
| |
This was introduced in commit 95d42ea01f7f9c60210b415554e7bbf6f4e1b334 and released in 3.5.91.
The error meant that when a network location was disconnected the next time you connected to it you would get the old NautilusFile object that was marked as "gone" and hit an assertion.
https://bugzilla.gnome.org/show_bug.cgi?id=708282
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=722616
|
|
|
|
|
|
|
|
| |
We crash in g_hash_table_lookup_extended if the file's symlink_name is
set but the file is not a symlink, since the hash function (g_str_hash)
does not allow NULL values but target_uri is NULL.
https://bugzilla.gnome.org/show_bug.cgi?id=711583
|
| |
|
|
|
|
|
| |
Fixes a crash where we would try to access a window active slot before
NautilusWindow's constructor set one.
|
|
|
|
|
|
|
|
|
|
| |
When we construct the NautilusWindow, we show or hide the sidebar
according to the value in GSettings, but we never sync the initial state
of the corresponding toggle action.
Based on a patch by Paul Menzel <paulepanter@users.sourceforge.net>
https://bugzilla.gnome.org/show_bug.cgi?id=699165
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As Matthias Clasen noticed, the signal handlers for the gdbus-codegen
skeleton for the shell search provider have the wrong signature, and
should return TRUE to indicate that the signal has been handled.
Otherwise, it is down to chance if the method is handled or if a
method-not-implemented error is emitted. It seems that the GCC option
-fstack-protector-strong causes the default return value to be
interpreted as FALSE, so this might explain why the problem was only
noticed by a wide variety of users recently.
The bug manifests as Nautilus not returning any search results when
using the gnome-shell activities overview search.
https://bugzilla.gnome.org/show_bug.cgi?id=692041
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=705072
|
| |
|
|
|
|
| |
Fixes bug #697807
|
|
|
|
|
|
|
| |
ignore the new current item just because the mouse is down. It is
later used for right click.
Fixes bgo #704289.
|
| |
|
|
|
|
|
|
|
| |
This prevents nautilus trying to switch to the place which is being ejected
and in turn showing an error.
https://bugzilla.gnome.org/show_bug.cgi?id=699183
|
|
|
|
|
|
|
| |
This causes the widgets to be properly destroyed before the NautilusView
is.
https://bugzilla.gnome.org/show_bug.cgi?id=702546
|
| |
|
|
|
|
|
|
|
| |
If the location string starts with 'x-nautilus-search://', set
the tooltip to the window slot title instead of the location.
https://bugzilla.gnome.org/show_bug.cgi?id=610789
|
|
|
|
|
| |
The conversion utility does not deal with such keys gracefully.
https://bugzilla.gnome.org/show_bug.cgi?id=700179
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=698661
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Grabbing the focus to a GtkEntry causes its selection to be set which
in turn causes it to reset the IM context. Avoid doing that when we
already have the search entry focused to not mess the IM context.
https://bugzilla.gnome.org/show_bug.cgi?id=698205
|
| |
|
| |
|
|
|
|
|
| |
We don't need to check if the file is in the desktop, since the desktop
view will call in with show_foreign = FALSE already.
|
|
|
|
|
| |
When a special desktop item (Home, Trash and the volumes shortcut) is
dragged, only the desktop itself is a valid destination target.
|
|
|
|
|
|
| |
Or moving icons on the desktop itself will break.
https://bugzilla.gnome.org/show_bug.cgi?id=697682
|
|
|
|
|
|
|
|
|
| |
When two search results rank equally, we fall back to the collated
order.
Since search is usually ranked reversed (highest at the top), we need to
ensure we don't accidentally reverse the collated order as well.
https://bugzilla.gnome.org/show_bug.cgi?id=688772
|
|
|
|
|
| |
Count how many letters are left after the string occurrence, and
subtract that from the match score.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
It's inconsistent with "find" and it can yield to unexpectedly large
result sets.
Do not follow symlinks when recursing the search down the hierarchy.
https://bugzilla.gnome.org/show_bug.cgi?id=697181
|
|
|
|
|
|
|
|
|
| |
Code was very fragile and didn't work when the window wasn't initially
realized, such as when launching a search from the Shell provider.
We can get the same effect by moving the cursor at the end of the entry
after the focus has been set.
https://bugzilla.gnome.org/show_bug.cgi?id=697224
|
|
|
|
|
|
|
|
|
| |
Previously, we enabled the Cut action for the Recent location, and kept
Copy and Copy To disabled. This should be the other way around, as
copying a file from there is a valid option, whereas cutting/moving it
doesn't make sense, being a virtual location.
https://bugzilla.gnome.org/show_bug.cgi?id=690138
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=696962
|
| |
|
| |
|
| |
|
| |
|
| |
|