Alt-D keyboard shortcuts stops working after prolonged use
After a long browser session, sometimes the keyboard shortcut Alt-D stops working, but other keyboard shortcuts like Alt-H work fine.
The shortcuts F6 and Ctrl-L still work.
A restart of the browser fixes it though, so I haven't explored further.
It's not easy to replicate consistently; Firefox doesn't show it when first opened, but after prolonged use it may occur and then stay that way until restarted.
I am using Firefox version 76.0.1 (64-bit) on Ubuntu 18.04. I am not using the [German version of Firefox].
I know I can make this go away with a restart, I'm just curious if there's some troubleshooting steps I could take to identify the cause.
Modifié le par Nathaniel Beaver
Toutes les réponses (8)
Is this only happening in the current window or also in a new window ?
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Safe Mode start window
If you have sync, and there is a problem anywhere, Shut Down Sync Immediately On All Devices to prevent the problem from spreading. Once the problem is fixed, perform the same repair on all computers/profiles before using sync again.
[v57+] Places Maintenance is built into Firefox.
Type about:support<enter> in the address bar.
You will find Places Database near the bottom. Press the Verify Integrity button.
When done, copy and post the results here.
https://support.mozilla.org/en-US/kb/fix-bookmarks-and-history-will-not-be-functional
Hi there,
Is this only happening in the current window or also in a new window ?
When I've observed it, the bug occurs in both the current window and in new windows.
switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
I always use the default theme, so I think we can safely rule this out.
Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions)
I can certainly do that, but bear in mind that when I start a fresh browser session I haven't generally seen this behavior until at least a few days have passed. Given that, I'd really like to know what to look for when I do manage to replicate the bug, such as relevant console errors or debug logs I should enable to check later. I suppose I could make a screencast demonstrating the behavior; would that be of use?
I will say that I've checked "Manage Extension Shortcuts" and none of the extensions are using the Alt-D keyboard shortcut.
or if hardware acceleration is causing the problem.
I've now disabled hardware acceleration; is this known to affect only one keyboard shortcut?
If you have sync, and there is a problem anywhere, Shut Down Sync Immediately On All Devices to prevent the problem from spreading.
I don't sync preferences or addons, so I don't think this is a concern. And I mainly sync to Firefox for Android on my phone, where Alt-D isn't even possible. Keep in mind this is only a minor bug and I've only observed it on this machine, and then only infrequently.
Press the Verify Integrity button. When done, copy and post the results here.
Certainly, see below.
- > Task: checkIntegrity
- + The places.sqlite database is sane
- + The favicons.sqlite database is sane
- > Task: invalidateCaches
- + The caches have been invalidated
- > Task: checkCoherence
- + The database is coherent
- > Task: expire
- + Database cleaned up
- > Task: originFrecencyStats
- + Recalculated origin frecency stats
- > Task: vacuum
- + Initial database size is 81920KiB
- + The database has been vacuumed
- + Final database size is 76800KiB
- > Task: stats
- + Places.sqlite size is 76800KiB
- + Favicons.sqlite size is 116128KiB
- + pragma_user_version is 53
- + pragma_page_size is 32768
- + pragma_cache_size is -2048
- + pragma_journal_mode is wal
- + pragma_synchronous is 1
- + History can store a maximum of 150658 unique pages
- + Table moz_places has 150657 records
- + Table moz_historyvisits has 212285 records
- + Table moz_inputhistory has 309 records
- + Table moz_hosts has 0 records
- + Table moz_bookmarks has 1153 records
- + Table moz_bookmarks_deleted has 0 records
- + Table moz_keywords has 1 records
- + Table sqlite_sequence has 1 records
- + Table moz_anno_attributes has 3 records
- + Table moz_annos has 760 records
- + Table moz_items_annos has 0 records
- + Table sqlite_stat1 has 20 records
- + Table moz_meta has 7 records
- + Table moz_origins has 14608 records
- + Index sqlite_autoindex_moz_inputhistory_1
- + Index sqlite_autoindex_moz_hosts_1
- + Index sqlite_autoindex_moz_bookmarks_deleted_1
- + Index sqlite_autoindex_moz_keywords_1
- + Index sqlite_autoindex_moz_anno_attributes_1
- + Index sqlite_autoindex_moz_origins_1
- + Index moz_places_url_hashindex
- + Index moz_places_hostindex
- + Index moz_places_visitcount
- + Index moz_places_frecencyindex
- + Index moz_places_lastvisitdateindex
- + Index moz_places_guid_uniqueindex
- + Index moz_historyvisits_placedateindex
- + Index moz_historyvisits_fromindex
- + Index moz_historyvisits_dateindex
- + Index moz_bookmarks_itemindex
- + Index moz_bookmarks_parentindex
- + Index moz_bookmarks_itemlastmodifiedindex
- + Index moz_bookmarks_dateaddedindex
- + Index moz_bookmarks_guid_uniqueindex
- + Index moz_keywords_placepostdata_uniqueindex
- + Index moz_annos_placeattributeindex
- + Index moz_items_annos_itemattributeindex
- + Index moz_places_originidindex
- > Task: _refreshUI
The bookmarks file looks good.
Hardware Acceleration has been known to cause issues.
Are you currently using a version from the repositories of your Linux distribution? Try the Firefox version from the official Mozilla server:
I'm curious, can you still store new history and create new bookmarks as you seem to have a lot ?
Maybe time to cleanup your history.
+ History can store a maximum of 150658 unique pages + Table moz_places has 150657 records + Table moz_historyvisits has 212285 records
Are you currently using a version from the repositories of your Linux distribution? Try the Firefox version from the official Mozilla server
Thanks for the suggestion, but I prefer to use the package manager as it ensures that the browser and its dependencies are upgraded in tandem.
I'm curious, can you still store new history and create new bookmarks as you seem to have a lot ?
Yes, and I can't recall ever having difficulty storing new history or creating new bookmarks.
Maybe time to cleanup your history.
I'd prefer not to delete my history as I often refer to it to see what pages I've visited, sometimes many months later. Incidentally, is a large history file associated with the Alt-D keyboard shortcut not working?
I do appreciate the suggestions, but I guess what I'm asking is how to debug a live session when one keyboard shortcut isn't working and the others are. Any tips on this or links to the relevant documentation?
I think that Alt+D is the only exception where a Alt keyboard shortcut doesn't access a menu, but goes to the location bar.
All other cases for Alt+key are for accessing the main menu bar and Alt+Shift+key is reserved for access keys on web pages (e.g. Alt+Shift+S submits the post a reply form on some forums).
Does Alt still bring up the menu bar assuming that ui.key.menuAccessKeyFocuses = true on the about:config page ?
There are several ui.key prefs that deal with these key combinations.
I was able to reproduce the bug again today after about two weeks. It seems to require about a three-day continuous session.
Does Alt still bring up the menu bar assuming that ui.key.menuAccessKeyFocuses = true on the about:config page ?
Yes, ui.key.menuAccessKeyFocuses is set to the default value of true, and all the other ui.key settings are set to their default values.
I can confirm that the Alt-1, Alt-2, etc. keyboard shortcuts to change tabs do work while Alt-D does not. I'd also like to add a correction: it seems that new windows in the same session do not exhibit the issue.
Here's an example:
I took a quick look at the code:
location-open-shortcut =
.key = L
location-open-shortcut-alt =
.key = D
<key id="focusURLBar" data-l10n-id="location-open-shortcut" command="Browser:OpenLocation"
modifiers="accel"/>
#ifndef XP_MACOSX
<key id="focusURLBar2" data-l10n-id="location-open-shortcut-alt" command="Browser:OpenLocation"
modifiers="alt"/>
#endif
function openLocation(event) {
if (window.location.href == AppConstants.BROWSER_CHROME_URL) {
gURLBar.select();
gURLBar.view.autoOpen({ event });
return;
}
// If there's an open browser window, redirect the command there.
let win = getTopWin();
if (win) {
win.focus();
win.openLocation();
return;
}
but I don't know how to enable logging or if that would be helpful in this case. Are there further suggestions or should I just file a bug report and call it quits?