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 750388 - Nautilus accels not working (3.16.2)
Nautilus accels not working (3.16.2)
Status: RESOLVED DUPLICATE of bug 750107
Product: nautilus
Classification: Core
Component: Keyboardability
3.16.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-06-04 11:02 UTC by Jonas
Modified: 2015-07-31 09:52 UTC
See Also:
GNOME target: ---
GNOME version: 3.15/3.16


Description Jonas 2015-06-04 11:02:21 UTC 
Unable to set accels in .config/nautilus/accels. Uncommenting entries has no effect. 

Steps to reproduce: 
1) Uncomment desired accel in .config/nautilus/accels (I need 
(gtk_accel_path "<Actions>/ShellActions/Up" "BackSpace") 
Save the file.
2) quit nautilus: nautilus -q
3) restart nautilus 
4) the accel is not working

Ubuntu 15.04, Gnome-Staging PPA enabled.
Comment 1 Jonas 2015-06-09 12:53:56 UTC 
Pressing the desired accel (backspace in my case) shows this warning in the console:

(nautilus:19364): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1: Entity did not end with a semicolon; most likely you used an ampersand character without intending to start an entity - escape ampersand as &amp;

Can there be a problem with parsing accel file?
Comment 2 Max Ehrlich 2015-07-29 15:16:18 UTC 
I was actually told that this was removed as a side effect of the change to GAction, I have filed a bug here to have the behavior reinstated 

https://bugzilla.gnome.org/show_bug.cgi?id=752666

I don't know if we should consider these duplicate reports or not
Comment 3 Jonas 2015-07-31 09:52:19 UTC 
Yeah, definitely duplicate. I'd sad to see less and less functionality in gnome desktop.

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