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 769322 - Corrupted prompt on attempt to change shortcut icon
Corrupted prompt on attempt to change shortcut icon
Status: RESOLVED DUPLICATE of bug 767229
Product: nautilus
Classification: Core
Component: File Properties Dialog
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-07-30 08:12 UTC by Egor Panfilov
Modified: 2016-07-30 09:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egor Panfilov 2016-07-30 08:12:35 UTC 
Description:
Nautilus opens corrupted prompt (cannot interact via neither keyboard nor mouse) on attempt to change shortcut icon.
When the prompt is opened, system and nautilus itself still operate just fine (no hangs, excessive CPU load, etc).

Additional info:
* up-to-date system, no testing repos enabled;
* package version(s): gnome-shell 3.20.2-1, nautilus 3.20.2-1 (same with 3.20.1-1);
* config and/or log files etc: ordinary configuration.

Steps to reproduce:
1. Create a shortcut (symlink) to user owned folder;
2. Right-click -> 'Properties' -> click on folder icon;
3. Try to interact with the opened prompt.

Etc:
I have found only this related post, although, there is no solution: https://forum.antergos.com/topic/4459/nautilus-freeze-when-trying-to-change-icon/10


/xref https://bugs.archlinux.org/task/49346
Comment 1 Ernestas Kulik 2016-07-30 08:21:50 UTC 
Works for me.
Comment 2 Ernestas Kulik 2016-07-30 08:32:08 UTC 

*** This bug has been marked as a duplicate of bug 767229 ***
Comment 3 Egor Panfilov 2016-07-30 08:38:44 UTC 
(In reply to Ernestas Kulik from comment #1)
> Works for me.

Thanks for the quick feedback!

I'm now in doubt if it actually fails in 3.20.2. I've cleaned up configuration files and everything works well now.
Comment 4 Ernestas Kulik 2016-07-30 09:00:19 UTC 
(In reply to Egor Panfilov from comment #3)
> (In reply to Ernestas Kulik from comment #1)
> > Works for me.
> 
> Thanks for the quick feedback!
> 
> I'm now in doubt if it actually fails in 3.20.2. I've cleaned up
> configuration files and everything works well now.

That is pretty weird, though. I use Arch and the update fixed it without forcing me to do configuration file gymnastics.

Anyway, it is good to hear that it works for you now—I even started installing Antergos to look for anything suspicious.
Comment 5 Ernestas Kulik 2016-07-30 09:05:19 UTC 
And it indeed still works on a fresh installation.