[Desktop-packages] [Bug 1700645] Re: gpg-agent not running when needed by Déjà Dup
'morning,
I'm also affected, I'm not sure since when as I only occasionally receive
encrypted emails.
Ubuntu 16.04.5 LTS
gpgv 1.4.20-1ubuntu3.3
gnupg-agent 2.1.11-6ubuntu2.1
1) use-agent is active in ~/.gnupg/gpg.conf
2) gpg-agent fails to start due to a missing /run/usr/$UID/gnupg directory
(/run/usr/$UID exists)
3) After repair ("mkdir /run/usr/$UID/gnupg"), gpg-agent starts automagically
with these arguments: --homedir /home/josef/.gnupg --use-standard-socket
--daemon, but still the socket is create in /run/user/UID/gnupg!
4) /etc/X11/Xsession.d/90gpg-agent exists
5) I use KDE (kde-baseapps-bin 4:15.12.3-0ubuntu1, though other KDE packages
are 4:5.5.5-0ubuntu1).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1700645
Title:
gpg-agent not running when needed by Déjà Dup
Status in Déjà Dup:
Invalid
Status in deja-dup package in Ubuntu:
Invalid
Status in gnupg2 package in Ubuntu:
New
Bug description:
Some have reported problems before with repeated demands for
encryption passwords, but mine gives a different error. I've deleted
all my previous backups and reinstalled duplicity and deja-dup, but I
still get the error:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no
effect
DUPLICITY: . gpg: invalid size of lockfile
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
DUPLICITY: . gpg: cannot read lockfile
DUPLICITY: . gpg: can't connect to the agent: Invalid argument
DUPLICITY: . gpg: problem with the agent: No agent running
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
DUPLICITY: .
DUPLICITY: ERROR 31 GPGError
DUPLICITY: . GPGError: GPG Failed, see log below:
DUPLICITY: . = Begin GnuPG log =
DUPLICITY: . gpg: WARNING: "--no-use-agent" is an obsolete option - it has no
effect
DUPLICITY: . gpg: invalid size of lockfile
'/home/username/.gnupg/gnupg_spawn_agent_sentinel.lock'
DUPLICITY: . gpg: cannot read lockfile
DUPLICITY: . gpg: can't connect to the agent: Invalid argument
DUPLICITY: . gpg: problem with the agent: No agent running
DUPLICITY: . = End GnuPG log =
DUPLICITY: .
System details:
Ubuntu 17.04
deja-dup 34.4-0ubuntu1
duplicity 0.7.06-2ubuntu3
Thank you in advance!
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1700645/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808275] Re: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
Does rebooting successfully restore sound? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Summary changed: - [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all + [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] Changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped Status in pulseaudio package in Ubuntu: Incomplete Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I got an error when building the modules from @VanVan's github due to /sound/pci/hda_codec.h having been moved to /include/sound/hda_codec.h Fixing this let the compile finish without error (this is on Fedora 29). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I'm seeing something like this on a 32bit Acer laptop - with Intel graphics - running Kubuntu 18.04.1 - it's been doing it for quite a long time - but it's still a current bug - I did a full apt upgrade/update just today. When the machine awakes from a sleep (eg with by closing and opening the lid) the mouse cursor is gone - and the whole screen below the mouse position is white. So as you move the mouse up and down and it covers and uncovers the entire screen. You have no way to tell where the X position of the mouse is - but it does seem to work and you can still click on things. Switching to a different virtual console and back again using Ctrl-Alt- Fn seems to fix it...until the machine goes to sleep again. Seems like maybe some piece of graphics state isn't being properly saved and restored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
i also got errors when trying to follow that ubuntu guide for compiling your own kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808275] [NEW] [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all
Public bug reported: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1808275 Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: The green headphone out was working and I changed the sound output from analog output to digital output(S/PDIF) and it suddenly stopped and changing it back to Analog Output didn't restore the sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Dec 12 23:10:39 2018 InstallationDate: Installed on 2018-12-06 (7 days ago) InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [, SigmaTel STAC9221D A2, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97510J.86A.1487.2007.0902.1724 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX dmi.board.vendor: Intel Corporation dmi.board.version: AAD27094-305 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97510J.86A.1487.2007.0902.1724:bd09/02/2007:svn:pn:pvr:rvnIntelCorporation:rnD975XBX:rvrAAD27094-305:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808264] Re: caldav free-busy query is broken
Whoops, misinterpreted the version numbering scheme and accidentally submitted a patch numbered for 18.04.2! ** Patch added: "Patch with correct version number" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+attachment/5221828/+files/2-3.28.5-0ubuntu1.18.04.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I am experiencing this on Thinkpad T460s running 64 bit Ubuntu 18.04.1 (4.15.0-42-generic) with Gnome 3.28.2, utilizing Intel® Core™ i7-6600U CPU @ 2.60GHz × 4, Intel® HD Graphics 520 (Skylake GT2) I was not experiencing this problem on the same machine running 16.04, and only started experiencing it after upgrading to 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
1600x1200: No space left on device]
Status in gnome-shell package in Ubuntu:
Fix Released
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808264] Re: caldav free-busy query is broken
I have added a patch which applies both upstream merge requests linked above. I was not above to successfully set up pbuilder, but built and tested it successfully with debuild in a bionic VM. Subscribing ubuntu- sru in accordance with http://packaging.ubuntu.com/html/security-and- stable-release-updates.html as I'm pretty sure the change I'm requesting would be a stable release update. Aiming justify that update: this is a significant regression because somewhere between Xenial and Bionic, this caldav freebusy code was rewritten and broken. Additionally somewhere in that timeframe the behavior changed from using the address book's FBURL to using this caldav-based technique (which, again, doesn't work :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808264] Re: caldav free-busy query is broken
** Patch added: "Patch for this issue" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+attachment/5221827/+files/1-3.28.5-0ubuntu0.18.04.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 41159] Re: timezone data is duplicated over at least three packages in main
I wonder if we should change the packaging of tzdata to always build the stuff that icu needs/wants. Such that an update of tzdata ripples through to icu as well. Somehow. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/41159 Title: timezone data is duplicated over at least three packages in main Status in evolution-data-server package in Ubuntu: Fix Released Status in gcj-4.1 package in Ubuntu: Fix Released Status in icu package in Ubuntu: Confirmed Status in postgresql-8.2 package in Ubuntu: Fix Released Status in python-tz package in Ubuntu: Fix Released Status in icu package in Debian: New Bug description: timezone data is duplicated over at least three packages in main, these are: - belocs-locales - icu - python-tz probably not something to solve before dapper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805715] Re: password exposed in application windows
Yes, in fact we can say with some confidence that the issue was probably fixed in a later Gnome version since no one else is reporting the issue in 18.04/18.10. If only we knew what fixed it and where then we would be able to backport that fix :/ ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in application windows Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1805715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device]
I updated to 18.10 in place. That fixes the problem with the blank
screen. Unfortunately the menu to the upper left does not seem to get
focus. To logout I go to the upper right and type logout which loads a
'logout app.' I suppose that's a different bug.
Thank you for your help. Please let me know if you would like further
testing. I'm working with scripts to install Ubuntu (and Debian) on ZFS
root and can load up a fresh install in a little longer than it takes to
install using the conventional installer.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
1600x1200: No space left on device]
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805715] Re: password exposed in application windows
I did some tests with 18.10 but the problem did not occur. Since the bug is intermittent, these tests may not be significant. Please leave this case open to future updates. ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in application windows Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1805715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I have noticed that
a) systemctl suspend
does actually suspend, but it takes about 30 seconds.
I'm on 18.04.1 with kernel 4.18.0-13-generic from the proposed PPA
This is quite surprising, but good news. I don't know why this is working
now. It works with either Chromium or Chrome open, with hangouts running.
Because gnome uses systemctl suspend, this means that manual suspend from
gnome shell is also working.
I just suspended right now with a hangouts conversation in progress and a
Zoom meeting started, and it succeeded.
Maybe the more recent kernel fixes it?
b)
pkexec systemctl -i suspend
(run with root privileges)
always works, but this is less suprising, since -i means ignore
inhibitors.
On Thu, 13 Dec 2018 at 12:16, ethanbrown wrote:
> I agree with W-barath-hotmail that this is a serious problem that needs
> to be addressed. I believe on some occasions suspend fails even after
> I've killed Chrome.
>
> Please increase the Importance ranking of this bug.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1600622
>
> Title:
> Screen doesn't lock or go to sleep when certain Chrome tabs are open
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab
[Desktop-packages] [Bug 1745866] Re: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on
See also bug 1707611. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1745866 Title: [nvidia] Audio does not auto-switch to HDMI after switching the connected HDMI TV on Status in pulseaudio package in Ubuntu: Confirmed Bug description: When I start the computer is the connected TV (HDMI) is off and the pulseaudio device stays on unplugged when I switch the TV on. If I switch the TV on before I start the computer, everything works fine. alsa_output.pci-_01_00.1.hdmi-stereo linux-image-14.0-15-generic nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic Regards, Norbert --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.14.0-15-generic. AplayDevices: aplay: device_list:270: no soundcards found... ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 ArecordDevices: arecord: device_list:270: no soundcards found... AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-12-25 (36 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171222) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu4 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: bionic third-party-packages Uname: Linux 4.14.0-15-generic x86_64 UnreportableReason: Das ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von Drittanbietern und wiederholen Sie den Vorgang. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.10 dmi.board.name: H67M-GE/HT dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd04/27/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-GE/HT:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2018-01-30T18:59:12.789526 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1745866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792081] Re: auto-hide dual monitor only hides dock on one monitor
** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1792081 Title: auto-hide dual monitor only hides dock on one monitor Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: i have two monitors I have set auto hide for my monitors 3) What you expected to happen I expect autohide to work on BOTH monitors it does not not autohide only works on the primary monitor the second monitor still shows dock see attached screenshot left side ideally user would have option to auto hide on one monitor and show dock on another as it is auto hide only works on one monitor lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 08:25:54 2018 InstallationDate: Installed on 2015-08-23 (1115 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-08-21 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1792081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1711101, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1711101 Audio doesn't auto switch away from HDMI after unplugging HDMI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1802350 Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: On a fresh install of ubutu 18.04 all sound work (youtube and system sounds) I connected external hdmi monitor with speakers. I switched audio output to hdmi in settings Then all audio was channeled to external monitor speakers (youtube and system sounds) Then I disconnected external monitor and did not touch the audio output Now only system sounds are working. Youtube in chrome does not work. Audio settings says internal speakers. Firefox youtube has audio normally After reboot same issue ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ed 1412 F pulseaudio /dev/snd/controlC1: ed 1412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:28:37 2018 InstallationDate: Installed on 2018-11-01 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 5547 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774496] Re: Display defaults back to 200% on external screen connection
** Tags added: hidpi multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774496 Title: Display defaults back to 200% on external screen connection Status in gnome-shell package in Ubuntu: New Bug description: I have a 2560x1440 screen that by default gets set to 200% which is way too large. I just set it to 100% and tweak the font scaling a bit instead. This is equivalent to the 1.38 scaling that used to be available in settings in 16.04. When connecting an external 1920x1080 screen the settings revert back to 200% on the internal screen. This makes no sense. The internal screen hasn't changed its properties so there's no real reason to change to 200% just because there's a second screen attached. Particularly since the setting is per-screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:02:32 2018 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788535] Re: gnome-control-center shows 120Hz display frequencies that the display doesn't support (it's really only 60Hz)
Maybe, maybe not. I haven't verified that yet since gnome-control-center is presently the only thing reporting bogus numbers. ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1788535 Title: gnome-control-center shows 120Hz display frequencies that the display doesn't support (it's really only 60Hz) Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/275 --- gnome-control-center shows 120Hz display frequencies that the display doesn't support (it's really only 60Hz) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.29.91-1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Thu Aug 23 11:08:09 2018 InstallationDate: Installed on 2018-08-17 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1788535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808183] Re: server console output extremely slow after upgrade to 18.04
Please: 1. Clarify what is meant to be visible on your server console. Are you using Gnome Shell, just text mode, or something else? 2. Run 'lspci -k > lspcik.txt' on the machine and send us the 'lspcik.txt' file 3. Install package 'mesa-utils' and then run 'glxinfo > glxinfo.txt' on the machine and send us the file 'glxinfo.txt'. 4. Run 'dmesg > dmesg.txt' on the machine and send us the 'dmesg.txt' file. 5. Run 'journalctl > journal.txt' on the machine and send us the file 'journal.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1808183 Title: server console output extremely slow after upgrade to 18.04 Status in Ubuntu: Incomplete Bug description: After the upgrade from 16.04 to 18.04 my server console is extremely slow. It looks similar to the youtube clips mentioned in the problem described here: https://ubuntuforums.org/showthread.php?t=2399941 My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD. It runs on an ASUS P9D-X board. Before the upgrade everything was fine. Now it is so slow that it sometimes even hangs during boot and goes into an emergency console where I just can do a ctrl-alt-delete as described in bug 1802469 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Wed Dec 12 17:07:48 2018 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1808183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805715] Re: password exposed in application windows
Testing 18.10 would help us the most in the short term. But in the long term be aware that 18.04 has a longer support life: https://wiki.ubuntu.com/Releases ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1805715 Title: password exposed in application windows Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: Plain text Linux user id password exposed in calculator input box. The first character of the password is dropped. This is reproducible as follows: 0. the calculator window has the desktop focus and the input box is empty. 1. allow screen saver to kick in or invoke it manually with ctrl+alt+l 2. type in password 3. hit enter 4. view password in input box of calculator (less first character) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calculator 1:3.18.3-0ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Nov 28 16:37:44 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2018-11-14 (13 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1805715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807540] Re: When an external monitor is attached some windows protrude onto this new monitor
** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/846 + + --- + I have connected an external monitor to my notebook. The display of the new monitor had some windows protruding that were actually displayed in maximized mode on the internal monitor (GNOME Calendar and Tasks). It wasn't until I selected these windows that they retreated from the external monitor and were maximized only on the internal monitor. The windows should adjust their resolution immediately after the connection and be displayed only on the internal monitor. There are many cases where I don't want to show what's running on my internal monitor. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 9 00:02:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807540 Title: When an external monitor is attached some windows protrude onto this new monitor Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/846 --- I have connected an external monitor to my notebook. The display of the new monitor had some windows protruding that were actually displayed in maximized mode on the internal monitor (GNOME Calendar and Tasks). It wasn't until I selected these windows that they retreated from the external monitor and were maximized only on the internal monitor. The windows should adjust their resolution immediately after the connection and be displayed only on the internal monitor. There are many cases where I don't want to show what's running on my internal monitor. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 9 00:02:25 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807539] Re: Screen orientation is locked if external monitor is connected
** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/847 + + --- + As described above. I'm using a Thinpad X1 Yoga. Normally the screen orientation changes when I rotate the device or operate it in tent mode, for example. Unfortunately, this does not work if an external monitor (via HDMI) is connected to the device. In this case the screen orientation is fixed, so that e.g. a change into the tent mode is no longer possible. It would be nice if the screen would still change its orientation despite the attached external screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 23:52:43 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807539 Title: Screen orientation is locked if external monitor is connected Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/847 --- As described above. I'm using a Thinpad X1 Yoga. Normally the screen orientation changes when I rotate the device or operate it in tent mode, for example. Unfortunately, this does not work if an external monitor (via HDMI) is connected to the device. In this case the screen orientation is fixed, so that e.g. a change into the tent mode is no longer possible. It would be nice if the screen would still change its orientation despite the attached external screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 23:52:43 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (8 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: rotated screen is blank
Thanks.
If you can then please try the latest stable release of Gnome Shell by
installing Ubuntu 18.10. But only if it is convenient.
If you don't or can't find that the problem is fixed in a later release
already then please report it to the developers here:
https://gitlab.gnome.org/GNOME/mutter/issues
with details of the symptoms and the error message. And then tell us the
new bug ID.
** Summary changed:
- rotated screen is blank
+ Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
1600x1200: No space left on device]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
1600x1200: No space left on device]
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808264] [NEW] caldav free-busy query is broken
Public bug reported: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1808264 Title: caldav free-busy query is broken Status in evolution-data-server package in Ubuntu: New Bug description: A couple of bugs are present which make CalDAV scheduling effectively useless - the combined effect of them is that everyone else shows as having your availability information, rather than their own. I have patched the bugs upstream, and they have been merged into the branches for both 3.30.4 and 3.31.4: * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/8 * https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/7 I'm hoping to backport these patches to bionic, which packages 3.28 -- I will submit such a debdiff later today. I am submitting here rather than to Debian as the versions of this package in Debian are out of lockstep with Ubuntu's, so the patch doesn't cleanly transfer -- let me know if this is the wrong approach. Cosmic is on the 3.30 release series, which I assume means the fix will come from upstream and doesn't need to be applied here, but let me know if I should do a patch for that as well. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 22:05:38 2018 InstallationDate: Installed on 2018-12-10 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evolution-data-server UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1808264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808193] Re: Battery indicator shows false reading
Please run this command to send us more information about the system: apport-collect 1808193 ** Project changed: ubuntu-power-consumption => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1808193 Title: Battery indicator shows false reading Status in gnome-shell package in Ubuntu: Incomplete Bug description: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808193] [NEW] Battery indicator shows false reading
You have been subscribed to a public bug: The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% (Fully charged when plugged in) but when plugged out the battery shows 94%. Batteries are fine, no issues whatsoever with batteries. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: battery power -- Battery indicator shows false reading https://bugs.launchpad.net/bugs/1808193 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: rotated screen is blank
Yes, seems to be related to Wayland.
I have attached xrandr output from an Xorg session.
Thanks!
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+attachment/5221818/+files/xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
rotated screen is blank
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: rotated screen is blank
It sounds like this bug is only affecting "Ubuntu on Wayland" and not
"Ubuntu". Is that right?
The error message:
Failed to set CRTC mode 1600x1200: No space left on device
comes from mutter's eglnative (Wayland) backend, after calling
drmModeSetCrtc. So "No space left on device" is an error from the
kernel with no further explanation :(
Can you please try logging into "Ubuntu" (the Xorg session), run
'xrandr' and send us the output?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
rotated screen is blank
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808226] Re: rotated screen is blank
** Tags added: black-screen
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1808226
Title:
rotated screen is blank
Status in gnome-shell package in Ubuntu:
New
Bug description:
Using "ubuntu-gnome-desktop" ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.
1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90
deg left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal.
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200:
No space left on device
Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.
hbarta@saugage:/var/log$ lsb_release -rd
Description: Ubuntu 18.04.1 LTS
Release: 18.04
hbarta@saugage:/var/log$
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.shell' b'favorite-apps' redacted by apport
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US
SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
Thanks. I can't find any obvious explanation in that log. Are you able to try installing a shell that's not gnome-shell? I would like to know if the problem is confined to gnome-shell. Try installing package 'unity-session' and log into Unity instead. Does the problem still happen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807056] Re: Occasional Keyboard freeze
@Daniel Attaching Prevboot.txt from the command you gave ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+attachment/5221807/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1807056 Title: Occasional Keyboard freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I am using 18.04 and sometimes, whatever I type does not work. It is as if there is no keyboard connected while I have my laptop keyboard and an external keyboard connected to the machine. I even enabled On Screen Keyboard and tried to type through it. Same result. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Dec 6 05:41:04 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-29 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 41159] Re: timezone data is duplicated over at least three packages in main
** Changed in: icu (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/41159 Title: timezone data is duplicated over at least three packages in main Status in evolution-data-server package in Ubuntu: Fix Released Status in gcj-4.1 package in Ubuntu: Fix Released Status in icu package in Ubuntu: Confirmed Status in postgresql-8.2 package in Ubuntu: Fix Released Status in python-tz package in Ubuntu: Fix Released Status in icu package in Debian: New Bug description: timezone data is duplicated over at least three packages in main, these are: - belocs-locales - icu - python-tz probably not something to solve before dapper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open
I agree with W-barath-hotmail that this is a serious problem that needs
to be addressed. I believe on some occasions suspend fails even after
I've killed Chrome.
Please increase the Importance ranking of this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
Status in gnome-session package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
$ apt-cache policy gnome-session-bin
gnome-session-bin:
Installed: 3.18.1.2-1ubuntu1.16.04.1
Candidate: 3.18.1.2-1ubuntu1.16.04.1
Version table:
*** 3.18.1.2-1ubuntu1.16.04.1 500
500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.18.1.2-1ubuntu1 500
500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
I'm using gnome-session-flashback
What happens:
The screen doesn't lock when having certain pages in Chrome tabs
Expected:
The screen should lock after the configured timeout in settings.
I've been having this issue sice before 14.04, which I recently
upgraded (fresh install) to 16.04.
After fresh install, the screen would turn down and lock the computer
after 10 minutes (or whatever time I setup). At one point it stopped
working. The screen never shuts down unless I manually lock the
session with CTRL-ALT-L.
I've followed the steps in
https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure
The culprit seems to be that Chrome issues some suspend inhibitions
through dbus when doing certain operations. Many people find this
problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
pretty sure that Chrome is doing something else of what i've found
out.
1) Gnome screen saver works correctly. I can trigger it manually with:
$ gnome-screensaver-command -a
2) Gnome screen saver never receives the "session idle" status
callback.
3) When Chrome is not running, I can manually inhibit the idle status:
$ gnome-session-inhibit --app-id test --reason "manual idle inhibit"
--inhibit-only --inhibit idle:suspend
Inhibiting until Ctrl+C is pressed...
4) I can query the inhibitors:
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103
reply_serial=2
array [
object path "/org/gnome/SessionManager/Inhibitor1686"
]
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetAppId
('test',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetReason
('manual idle inhibit',)
$ gdbus call --session --dest org.gnome.SessionManager --object-path
/org/gnome/SessionManager/Inhibitor1686 --method
org.gnome.SessionManager.Inhibitor.GetFlags
(uint32 12,)
12=4(suspend) + 8(idle)
5) When testing, I can inhibit for 70 seconds, idle timeout being 60
(1 minute). After these 70 seconds pass, the screen locks.
6) Regarding Chrome, this is the information I get when querying the
inhibitor:
GetAppId: ('/usr/bin/google-chrome-stable',)
GetReason: ('Uploading data to 10.200.0.163',)
GetFlags: (uint32 4,)
The flags just inhibits suspend, not locking or entering powersaving
mode.
This inhibitor seems to stay for 10-15 seconds, then goes away for
another 30-60 seconds. The screen NEVER locks when this tab is open.
No matter the inhibitor is present or not.
I'm not sure where to go on. If it's a Chrome bug it must be using
other mechanisms to prevent the idle timeout. Any ideas on what to
look for?
Julian.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1600622/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs (he/him) from comment #137) > (In reply to Jesse Peden from comment #136) > > On macOS, how can I bring back CMD-Enter for URL completion? I do not want > > CTRL-Enter on macOS, and I can't seem to find the option in about:config to > > change it back. > > There isn't one. Ctrl-Return is consistent with Safari and Chrome on mac. I suppose it is, but it seems to be counter-productive to get users used to having it be CMD-Enter for all of these years and then change it out of the middle of nowhere. They could have at least added an option to allow people to opt out of it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
@z80-ben Yes, you are right, UX931UA is not part of the list, it could have worked :/ Be sure that you have no configuration error on /etc/modprobe.d/alsa-base.conf Tested on Asus UX333, UX433, UX533 with ALC294 Support for Asus G751, P5440FF, X430UN, D640SA, UX550GE, X705FD; X430UN, GL503VM, Q524UQK, X542UN with ALC256 and some others. A lot of Acer computers too and some other brands. @klintfr It depends on your Linux distribution -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to David Balažic from comment #134) > How exactly is this fixed? Where? > > The https://www.mozilla.org/en-US/firefox/64.0/releasenotes/ doesn't mention > it. It does: "The macOS keyboard shortcut to add "www" and ".com" to a URL is now ctrl-enter instead of [apple]-enter" This is the only by-default change here. See the end of comment 124. > (In reply to Julien Cristau [:jcristau] from comment #132) > > Added to 64beta release notes: > > Changes to URL bar autocomplete keyboard shortcuts: use ctrl-enter for URL > > canonicalization on all platforms, and offer an opt-out for Windows/Linux > > users where it interferes with opening URLs in (background) tabs > > Was this dropped for the final release? No, the relnote just got repeatedly rewritten to simplify it and make it understandable/relevant for people who hadn't followed this bug. > What is the opt-out mechanism? On Windows/Linux you can change this by setting `browser.urlbar.ctrlCanonizesURLs` to false. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
How exactly is this fixed? Where? The https://www.mozilla.org/en-US/firefox/64.0/releasenotes/ doesn't mention it. (In reply to Julien Cristau [:jcristau] from comment #132) > Added to 64beta release notes: > Changes to URL bar autocomplete keyboard shortcuts: use ctrl-enter for URL > canonicalization on all platforms, and offer an opt-out for Windows/Linux > users where it interferes with opening URLs in (background) tabs Was this dropped for the final release? What is the opt-out mechanism? PS: Bugzilla needs a "final summary" field where things like this are documented. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
On macOS, how can I bring back CMD-Enter for URL completion? I do not want CTRL-Enter on macOS, and I can't seem to find the option in about:config to change it back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Hi! Yes it is possible! Well no to be exact, not possible with ctrl+enter but with ctrl+shift+enter instead. You can try the newest nightly/alpha/Aurora version of Firefox and test it out yourself. So you could use it right now :-) So if Webextensions can modify about:config settings you could revive your extension but with ctrl+shift+enter instead. I don't think it's possible for Webextensions to edit that keyboard command (some others like ctrl+f are possible to rewrite though). If you want to track progress on that issue, it is https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 However enter is not even a keyboard shortcut I suppose so it is probably not affected by that issue, right? Oh and it's not possible with the search bar right now! They don't seem to share the code. Is that considered as a bug? :Gijs? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Followup issues for inconsistencies of combinations and search input added: https://bugzilla.mozilla.org/show_bug.cgi?id=1506203 https://bugzilla.mozilla.org/show_bug.cgi?id=1506247 respectively. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Jesse Peden from comment #136) > On macOS, how can I bring back CMD-Enter for URL completion? I do not want > CTRL-Enter on macOS, and I can't seem to find the option in about:config to > change it back. There isn't one. Ctrl-Return is consistent with Safari and Chrome on mac. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797936] Re: Control Center->Disks cannot create ext4 partition on 5 TB external USB drive
Dear Sebastien Bacher, Yes< I was using the Disks app from the Control Center. I used gParted and solved the problem. Unfortunately I have had to reinstall Ubuntu 3 times since then, so additional data is not available. (Always keep you data in a separate partition from the Linux partition. Then when you have to reinstall Linux, your data stays intact.) I am currently using the leading edge Ubuntu MATE 18.10 since I am disappointed in the LTS ever since I found that the bug with duplex- printing in LibreOffice for HP printers was reported over 5 YEARS ago and no one has ever been assigned to fix it. They were considering removing the bug since it is so old and has never been fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797936 Title: Control Center->Disks cannot create ext4 partition on 5 TB external USB drive Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: I deleted the pre-existing NTFS and got a drive with all space unallocated. When I tried to create an ext4 partition, I got an error about the size of the partition. Closed Control Center->Disks and used gParted. No problem creating the ext4 partition. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 13 15:40:29 2018 ExecutablePath: /usr/bin/gnome-disks InstallationDate: Installed on 2018-07-06 (99 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1797936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Marco Bonardo [::mak] from comment #106) > So, we apparently do: > ctrl => .com > shift => .net > ctrl + shift => .org > > First, I'm not convinced .net and .org are more important than the other > many tlds around, for example in a localized build it would be far more > interesting to canonize to the local tld (for example .it for italian). I'd > totally support ctrl+shift to complete to the localized tld rather than .org > (though this would require localization support). > Second, I'd like if ctrl would be the necessary key to activate canonization > in general, so all the shortcuts should required ctrl to be pressed. Shift > is far too common when typing and as I said it's already used by > tab/tabshifted, it's just confusing. > I understand changing this we could break muscle memory of a minority, but > it's for a totally undiscoverable feature on less critical tlds than .com. > and we're changing cmd on Mac already, for which we'll want a relnote. > I'd honestly propose to drop the shift and ctrl+shift behaviors completely. Color me surprised when I updated to Nightly 64.0 and found out that the keyboard shortcuts that I've relied on Firefox having for the past 15 years apparently requires some rewiring of muscle memory. This change does make sense and does indeed make it more consistent all around -- but will definitely catch A LOT of long-time macOS Firefox users off- guard if not announced gracefully. This goes the same for keybord- shortcut aficionados/ power users. It will also require documentation updates (i.e. https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox- tasks-quickly#w_miscellaneous_2 and https://blog.mozilla.org/firefox /keyboard-shortcuts-command-qwerty/) since this is literally 15 year old behavior that is changing. It's also been blogged about over the years throughout various websites that cater to the power user (such as LifeHacker and How-To-Geek), but that's nothing that Mozilla controls. That being said, can we get about:config options to configure the Ctrl- Shift and Shift-Enter shortcuts in the address bar? When this feature was first added, .com, .net. and .org were the most popular of TLD suffixes. Today, I can see how that is different, and I will admit that I do not complete .net and .org domains as often. I agree that not many people used it, but perhaps it can be more accessible if a user can configure those prefixes and suffixes directly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Hey all, I think opening a new tab in background in a fast way/without leaving the current page is very useful. I had an extension for that but it's no longer possible because webext API does not offer that possibility. That's why I'm following this bug closely. However now I'm surprised. Here are all the things that happen on Firefox nightly 64.0a1 (2018-09-06) (64-Bit): ctrl: add www..com ctrl shift: www.com (should be add www..com in new window?) shift: new window foreground alt: new tab foreground alt ctrl: add www..com and open in new tab foreground alt shift: nothing happens, should be default action in tab background or new window background? alt shift ctrl: www.com new tab background The name/description of this bug is "Inconsistent "open in new tab" shortcuts (Ctrl+Enter for links, but Alt+Enter in address bar and search bar)" So I think the changes now are useful, but do they solve the original issue? Ctrl+Enter still doesn't open a new tab in background, like it does everywhere else. I suggest: ctrl: open in new tab in background shift: open in new window in foreground alt: Doesn't matter to me, maybe add www..com so people who want it still have it or keep it as new tab in foreground (but what's the advantage of that? just hit ctrl+t) ctrl shift: open in new window in background alt shift: like alt but in new window in foreground alt ctrl: like alt but in new background tab alt shift ctrl: like alt but in new window in background What do you think? Sorry, I don't want to stand in the way of closing this or marking it as fixed, but it doesn't seem to address the original point to me. Anyway thanks for the changes and reading this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Hi -- I developed (an overstatement, maybe) the now-defunct extension Background Tabs which allowed ctrl-enter to open URL bar and search bar items in a background tab. I was excited to see this: > This behavior is now possible, but it's behind a pref (about:config, browser.urlbar.ctrlCanonizesURLs) ...does that mean that a user will be able to change that pref and then ctrl-enter in the URL bar will open a background tab without switching to it? Will there be a similar option for the search bar? (Consistency would seem to dictate that there should be?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Seeing that both Chrome and Safari are using Cmd/Ctrl-Enter for opening something in a new background tab AND that this is also consistent with our use of Cmd/Ctrl in other contexts, I would support changing it. Re- opening on that basis. As far as priority goes, this is obviously on the lower end though... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
https://hg.mozilla.org/mozilla-central/rev/6b31860ce710 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
That's fantastic, thanks for attending to it! I'll miss ctrl-enter, but ctrl-shift-enter is a perfectly reasonably compromise. :-) I filed bug #1490138 for the search bar (hopefully I got the details right). I probably won't bother making a new extension just for the about:config pref. If the search bar implements something similar as well, Background Tabs will be happily obsolete! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(Yeah, but not using the URL bar is just not as nice. For example look & feel, use search & bookmarks keywords, afaik.) Ah thanks, I missed the mention of that pref! Well I'd rather have it not be consistent, but I understand your reasoning and gave my opinion. Still, should the combinations not stack like ctrl+shift canonize and open in new window? alt+ctrl does already stack as expected (canonize and open new tab). Why does only that stack? And alt+shift to open in new background tab would be incredibly useful for users who don't want to mess with about:config or don't know about it. They can just find it by trying it out or understanding how stacking should work. Anyway this is a followup issue and you said you wanted this bug to be closed, so if I don't hear back soon I'll submit a new ticket. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Added to 64beta release notes: Changes to URL bar autocomplete keyboard shortcuts: use ctrl-enter for URL canonicalization on all platforms, and offer an opt-out for Windows/Linux users where it interferes with opening URLs in (background) tabs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Release Note Request (optional, but appreciated) [Why is this notable]: see comment #121 [Affects Firefox for Android]: no [Suggested wording]: not sure, maybe: "Changes to URL bar autocomplete shortcuts" [Links (documentation, blog post, etc)]: I'll update https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-tasks-quickly#w_miscellaneous_2 . (In reply to Stanley Chan from comment #121) > It will also require documentation updates (i.e. > https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox- > tasks-quickly#w_miscellaneous_2 and I'll submit an update for this after submitting this comment; it'll need to be approved by the SUMO admins. > https://blog.mozilla.org/firefox/keyboard-shortcuts-command-qwerty/) I'll set user-doc-needed here for the above and to get this updated as well. > this is literally 15 year old behavior that is changing. It's also been > blogged about over the years throughout various websites that cater to the > power user (such as LifeHacker and How-To-Geek), but that's nothing that > Mozilla controls. No, I'm afraid if we could never update something that had been documented anywhere else, we would have long ago stopped making Firefox because of our inability to change pretty much anything... even our easter eggs get documented, for better and for worse... > That being said, can we get about:config options to configure the Ctrl-Shift > and Shift-Enter shortcuts in the address bar? There is already for the ctrl-enter case (you can change the suffix via about:config's browser.fixup.alternate.suffix). We removed the shift /ctrl-shift option completely because no other browser has those and they didn't seem useful. > When this feature was first > added, .com, .net. and .org were the most popular of TLD suffixes. Today, I > can see how that is different, and I will admit that I do not complete .net > and .org domains as often. I agree that not many people used it, but perhaps > it can be more accessible if a user can configure those prefixes and > suffixes directly. I see your point, but can I just point out that: - shift-click/enter normally opens new windows on all other types of shortcuts / bookmark/history entries etc. - shift-click/enter is also used for "turning off" switch-to-tab (in order to open links that you have open already a second time) - shift when used with opening new tabs in other places (which uses 'ctrl' on Win/Linux) toggles the background/foreground-ness of tabs so having Yet Another Possible Meaning for the 'shift' modifier here is neither very user-friendly nor all that maintainable in the codebase we have. In fact, even removing it caused me a few different headaches trying to not break any of the other behaviors. The other thing is the value proposition. You'd want this shortcut to avoid typing '.' followed by 2-3 other characters (generally... if you use loads of different '.americanexpress' domains and want to configure ctrl-shift-enter for those, then I'm very sorry...). Just the awkwardness of `ctrl-shift-enter` rather than simply typing those 3-4 chars doesn't seem very valuable to me. That's in addition to the fact that, 15 years since this stuff was implemented, we now autofill history for domains, so if you've visited the site before you can just hit 'enter' straightaway anyway... We're also much more reluctant to add more magical about:config switches that we don't expose in the "regular" options/preferences (and yet more reluctant to add *more* things to those options). So on the whole, I'm not excited about adding this back, not even with configurable suffixes. If my arguments don't seem convincing, please file a separate bug and we'll discuss there, but with 121 comments here so far, I don't think this is the best place. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762726] Re: Context menu does not show on passwords fields
If the website has the option to let you see what you enter into the password field then the menu will show. Example: https://mail.protonmail.com/login Running Firefox from the terminal after unsetting GTK_IM_MODULE fixes it: $ unset GTK_IM_MODULE $ firefox Since upgrading to 18.04 I'm unable to use autotype in password managers like KeePassXC, it always enters the wrong password. I quite positive the problem with autotyping is actually caused by this same issue as it skips some characters when the password is hidden, but it do enters it correctly if the website have the option to make the field visible (like in the example above) or after unsetting GTK_IM_MODULE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1762726 Title: Context menu does not show on passwords fields Status in firefox package in Ubuntu: Confirmed Bug description: As many people I use a password manager in order to manage my logins. For that I simply copy/paste the username and password in the respective fields from another application. Given some webpages block this by JavaScript, I have the following about:config preference: dom.event.clipboardevents.enabled=false This mostly as an information, because it doesn't seem to affect the problem. Take a login page (I tried AliExpress - https://login.aliexpress.com/), and right click in the username field. A context menu is shown, containing -amongst others- "Paste". Click right in the password field, and the context menu is not shown. I would expect it to be shown. Using Ctrl-V does work. I tried a recreated profile in order to exclude profile-based issues. The same happens. This does not happen on Ubuntu 16.04LTS (59.0.2+build1-0ubuntu0.16.04.3) with equivalent version Firefox (59.0.2) I am not 100% sure this is a firefox issue. Perhaps this is Gnome related, because I use the default interface on each installation: Unity on 16.04LTS and Gnome3 on 18.04LTS. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy firefox firefox: Installed: 59.0.2+build1-0ubuntu1 Candidate: 59.0.2+build1-0ubuntu1 Version table: *** 59.0.2+build1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs (he/him) from comment #114) > (In reply to avada from comment #113) > > (In reply to Marco Bonardo [::mak] from comment #111) > > > It should, yes. Overall the idea is that CTRL will be the canonization > > > key, > > > and it should be possible to disable it, as well as it should imo be > > > possible to set what to canonize to (if one prefers .it to .com, for > > > example). > > > Then on Mac, CMD will open in a new tab, rather trying to canonize. > > > > Will this finally work with the normal find bar an not just the quickfind > > bar? > > I don't understand - this bug has nothing to do with the find bar, it's > about the location bar. The 'search bar' in the summary is about the bar > that searches on your default search engine (e.g. duckduckgo, google, bing, > ...), not the find-in-page feature. Did you mean to comment on a different > bug? Not at all. With the quickfind bar you can press enter to open a link, or press ctrl+enter to open it in a new tab. But you can not do this with the normal findbar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to alexander.kern from comment #128) > Oh and it's not possible with the search bar right now! They don't seem to > share the code. Is that considered as a bug? :Gijs? Could you file a separate issue, and we can work out if it's fixable there? IIRC there are some other subtleties with how search behaves (e.g. defaults for whether tabs open in the foreground or not when you use the page context menu to search are governed by a different pref to the one governing "normal" links opened in tabs). So I'm not sure off- hand how easy it would be to fix. Either way we usually try to fix 1 thing per bug to avoid confusion about what is/isn't fixed. So fixing the search bar, given that it's not using the same code as per your comment, will need to have its own bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
I have reproduced this bug with Nightly version 1.0+ (2004-12-14)[] on Windows 7, 64 Bit! User agent- Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.8a6) Gecko/20041224 Firefox/1.0+ Thus bug's fix is verified with latest Nightly! Build ID20180927220034 User Agent Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to alexander.kern from comment #123) > Hey all, I think opening a new tab in background in a fast way/without > leaving the current page is very useful. I had an extension for that but > it's no longer possible because webext API does not offer that possibility. Not from the URL bar, but extensions can definitely open background tabs, so an add-on could still do this using a page/browser action or a sidebar to offer you UI. > That's why I'm following this bug closely. However now I'm surprised. Here > are all the things that happen on Firefox nightly 64.0a1 (2018-09-06) > (64-Bit): > > ctrl: add www..com > ctrl shift: www.com (should be add www..com in new window?) > shift: new window foreground > alt: new tab foreground > alt ctrl: add www..com and open in new tab foreground > alt shift: nothing happens, should be default action in tab background or > new window background? > alt shift ctrl: www.com new tab background > > The name/description of this bug is "Inconsistent "open in new tab" > shortcuts (Ctrl+Enter for links, but Alt+Enter in address bar and search > bar)" > > So I think the changes now are useful, but do they solve the original issue? > Ctrl+Enter still doesn't open a new tab in background, like it does > everywhere else. I suggest: > > ctrl: open in new tab in background This behavior is now possible, but it's behind a pref (about:config, browser.urlbar.ctrlCanonizesURLs), because the outcome of some of the (long) discussion here was that to remain consistent with Chrome and IE/Edge, we would continue to keep that as the default (see e.g. comment #93). Note that AFAIK Chrome uses `ctrl-enter` even on Linux and Mac, so per the spreadsheet in comment #103 ( https://docs.google.com/spreadsheets/d/1VVEVjyIYRZIFteM71j5bJhENa2xXT82gaikr0WgpKLA/edit#gid=0 ) the default there is also to use ctrl-enter. (This is a change on mac, where it used to be cmd-enter.) I'll change the summary to more accurately reflect what was changed here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to alexander.kern from comment #125) > (Yeah, but not using the URL bar is just not as nice. For example look & > feel, use search & bookmarks keywords, afaik.) Yep... perhaps there's room for webextensions to have a larger scope for interaction with the URL bar - you could file a bug in the webextensions product. > Ah thanks, I missed the mention of that pref! Well I'd rather have it not be > consistent, but I understand your reasoning and gave my opinion. Likewise! It's a tricky problem - I was joking on IRC the other day that really we need like 10 modifier keys instead of just 3, then it wouldn't be so hard to come up with a way to make things not conflict... > Still, should the combinations not stack like ctrl+shift canonize and open > in new window? alt+ctrl does already stack as expected (canonize and open > new tab). Why does only that stack? And alt+shift to open in new background > tab would be incredibly useful for users who don't want to mess with > about:config or don't know about it. They can just find it by trying it out > or understanding how stacking should work. > > Anyway this is a followup issue and you said you wanted this bug to be > closed, so if I don't hear back soon I'll submit a new ticket. Thanks! Yes, please submit a new bug for alt-shift / ctrl-shift. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to avada from comment #118) > Not at all. With the quickfind bar you can press enter to open a link, or > press ctrl+enter to open it in a new tab. But you can not do this with the > normal findbar. That is not relevant to this bug, which is about the location bar and the web search bar and what happens if you press ctrl-enter in that. Those don't share any code with the find bar, so any changes there would have to be a different bug, in a different component, and affecting different code. Your suggestion was discussed in bug 1232096 and wontfixed there. This bug is not related and therefore not the right place to ask for reconsideration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Pushed by gijskruitbo...@gmail.com: https://hg.mozilla.org/integration/autoland/rev/6b31860ce710 allow turning off URL canonization, remove shift support, and move the remainder from 'cmd' to 'ctrl' on mac, r=mak -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Marco Bonardo [::mak] from comment #111) > It should, yes. Overall the idea is that CTRL will be the canonization key, > and it should be possible to disable it, as well as it should imo be > possible to set what to canonize to (if one prefers .it to .com, for > example). > Then on Mac, CMD will open in a new tab, rather trying to canonize. Will this finally work with the normal find bar an not just the quickfind bar? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Maybe we could telemetry the usage of the canonize feature, while we are at it. Though, it's likely something that falls into the "pretty much unused cause it's undiscoverable, but will have a vocal minority of fans", so not sure if it's worth it. FWIW, Edge still support CTRL+Enter, but doesn't add www. anymore, only .com. Maybe we should do the same for consistency if the feature is intended as an help for users migrating from IE/Edge to Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
So, we apparently do: ctrl => .com shift => .net ctrl + shift => .org First, I'm not convinced .net and .org are more important than the other many tlds around, for example in a localized build it would be far more interesting to canonize to the local tld (for example .it for italian). I'd totally support ctrl+shift to complete to the localized tld rather than .org (though this would require localization support). Second, I'd like if ctrl would be the necessary key to activate canonization in general, so all the shortcuts should required ctrl to be pressed. Shift is far too common when typing and as I said it's already used by tab/tabshifted, it's just confusing. I understand changing this we could break muscle memory of a minority, but it's for a totally undiscoverable feature on less critical tlds than .com. and we're changing cmd on Mac already, for which we'll want a relnote. I'd honestly propose to drop the shift and ctrl+shift behaviors completely. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Thomas D. (currently busy elsewhere) from comment #108) > Does this still cover the original intention of this bug and several > duplicates that users want an option (ideally on by default) where > Ctrl+Enter in location bar opens the address in a new tab? It's confusing > that sometimes we need to press Ctrl and sometimes Alt to open things in a > new tab. It should, yes. Overall the idea is that CTRL will be the canonization key, and it should be possible to disable it, as well as it should imo be possible to set what to canonize to (if one prefers .it to .com, for example). Then on Mac, CMD will open in a new tab, rather trying to canonize. > Why can't we just make ALT the default canonizer shortcut key? It would not be coherent with any other browser, and we want users to feel home when then move to Firefox. All of the other browsers canonize on CTRL. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
So what is blocking this exactly? Why can't we get this fixed? What should I do to get this fixed? This bug has been reported 14 years ago, maybe it doesn't need to live through its 15th year, does it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs Kruitbosch from comment #83) > Seems to me from comment 81 that this change should not be OS X - specific. So do you think we should remove the maybeCanonizeURL code altogether? I wasn't sure if we wanted to keep this behavior inherited from Internet Explorer on at least Windows, so I suggested making the minimal behavior change for a first patch (I was helping nox understand how this code works while we were waiting at the airport). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs (Not available 3-19 Aug; he/him) from comment #104) >> Note that the spreadsheet doesn't cover shift-enter, which also canonifies > today. I left that as-is, though of course that now also comes under the > pref, and can therefore be turned off (at which point we'll open a new > window instead). Ah, I didn't remember shift, why are we doing that exactly? it sounds wrong. Nor Edge nor Chrome do that, so it's not a parity reason. And I can see why they don't, it's trivial to leave your finger on shift when typing text and then we'd try to canonize it. Additionally we also use shift for tab VS tabshifted, so this is just adding confusion. May we file a bug to stop supporting shift and relegate canonize to just CTRL? provided we don't want to do that here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Anthony Ramine [:nox] from comment #95)
> What should I do to get this fixed?
Your patch does:
> } else if (this.AppConstants.platform == "macosx") {
and
> this.AppConstants.platform == "macosx") {
It also hardcodes 'accel' to always mean 'ctrl'.
Instead, leave the accel handling as-is, don't check for the OS, but add
a preference line in all.js, e.g. for
"browser.urlbar.accelenter.newtab". Use #ifdefs for that pref and, on
Windows, set it to false, and on everything else, to true.
Then instead of checking the OS in your patch, check the preference, and
use that to decide what to do.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/66566
Title:
Inconsistent shortcuts for new tab
Status in Mozilla Firefox:
Fix Released
Status in firefox package in Ubuntu:
Won't Fix
Status in firefox-3.0 package in Ubuntu:
Won't Fix
Status in firefox-3.5 package in Ubuntu:
Won't Fix
Bug description:
There are currently too many shortcuts when opening a link in a new
tab:
- location bar: +
- GO button: + click
- search bar: +
- SEARCH button + click
- links: + click
- menu bar: + click
- BACKWARD/FORWARD button: + click
This is one of the reasons I'm keeping with Opera. There it is always
the shift key and I have to remember only one key.
Thanks for reading!
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Does this still cover the original intention of this bug and several duplicates that users want an option (ideally on by default) where Ctrl+Enter in location bar opens the address in a new tab? It's confusing that sometimes we need to press Ctrl and sometimes Alt to open things in a new tab. Why can't we just make ALT the default canonizer shortcut key? Otherwise allow user to switch canonization off and have Ctrl+Enter = open in new tab behaviour instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(but all that is subject to what Philipp says - he reopened the bug in comment #81 so it's up to him to clarify.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
OK, so it looks like Edge, IE, Chrome and Firefox on Windows all currently do a version of autocompleting to www.$query.com on Ctrl-Enter. So I agree that doing this per-OS makes sense, since macOS seems to lean more heavily towards interpreting Cmd-something as doing things in a new tab. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
> "Cmd+Enter" not opening a new tab from the address bar has been my biggest hangup as I attempt to switch from Chrome to Firefox now. Current Behaviour 1. On Links on a page - Command + Click - Opens up on new tab (As expected) 2. On Browser Back and Forward button - Command + Click - Opens up in new tab (As expected) 3. On Address Bar - Command + Enter - Reloads in the same page (Unexpected, should Open in new page) For now, I do Option+Enter, but is inconsistent with the rest of the behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Created attachment 8996717 Bug 237027 - allow turning off URL canonization, remove shift support, and move the remainder from 'cmd' to 'ctrl' on mac, r?mak This isn't convention on macOS or other *nix platforms. Even on Windows, some people may prefer a different behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Florian Quèze [:florian] [:flo] from comment #84) > (In reply to :Gijs Kruitbosch from comment #83) > > > Seems to me from comment 81 that this change should not be OS X - specific. > > So do you think we should remove the maybeCanonizeURL code altogether? I > wasn't sure if we wanted to keep this behavior inherited from Internet > Explorer on at least Windows, so I suggested making the minimal behavior > change for a first patch (I was helping nox understand how this code works > while we were waiting at the airport). I'm not familiar with the pedigree of maybeCanonizeURL. It looks like the functionality was originally introduced in 2002 by Hyatt with no bug number. It does look like IE still does this type of completion. Philipp, what do you want to do? (note that "keep matching IE on Windows" != "only change this on OS X"; we should specialcase Windows, not OS X) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs from comment #96) > add a preference line in all.js Err, might need to be in firefox.js - check where the other urlbar behaviour prefs live. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Comment on attachment 8996717 Bug 237027 - allow turning off URL canonization, remove shift support, and move the remainder from 'cmd' to 'ctrl' on mac, r?mak Marco Bonardo [::mak] has approved the revision. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Marco Bonardo [::mak] (Away 9-26 Aug) from comment #103) > I made a small sheet to better understand what changes here, please check > and comment if something doesn't look correct. > https://docs.google.com/spreadsheets/d/ > 1VVEVjyIYRZIFteM71j5bJhENa2xXT82gaikr0WgpKLA/edit#gid=0 > > I didn't test the patch, I just assumed, on IRC Gijs said it's likely > different. > Anyway, I added a row with the behavior I'm suggesting, that is pretty much > the same as Chromium, apart ALT+Enter on the Mac. I think I implemented this in the updated patch, though I left out the support for downloads using 'alt-enter' on mac. I'm not convinced people want that behaviour, and in any case it'd re-introduce per-platform checks and some redundant calls to whereToOpenLink that I'm not super- fond of. Note that the spreadsheet doesn't cover shift-enter, which also canonifies today. I left that as-is, though of course that now also comes under the pref, and can therefore be turned off (at which point we'll open a new window instead). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to avada from comment #113) > (In reply to Marco Bonardo [::mak] from comment #111) > > It should, yes. Overall the idea is that CTRL will be the canonization key, > > and it should be possible to disable it, as well as it should imo be > > possible to set what to canonize to (if one prefers .it to .com, for > > example). > > Then on Mac, CMD will open in a new tab, rather trying to canonize. > > Will this finally work with the normal find bar an not just the quickfind > bar? I don't understand - this bug has nothing to do with the find bar, it's about the location bar. The 'search bar' in the summary is about the bar that searches on your default search engine (e.g. duckduckgo, google, bing, ...), not the find-in-page feature. Did you mean to comment on a different bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
"Cmd+Enter" not opening a new tab from the address bar has been my biggest hangup as I attempt to switch from Chrome to Firefox now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
It's now public, cheers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Hello, can we have alt+return open the page in the background? It's useful when you want to do something later. If you want to focus the page immediately, like Firefox does right now for alt+return, you can just use ctrl+t so I don't understand why alt+return opens in foreground too since there is already ctrl+t for that. Before there was the extension background tabs but there is no Webextension version of that. Thanks for reading -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs (he/him) from comment #96) > (In reply to Anthony Ramine [:nox] from comment #95) Was this hidden preference ever implemented? Is there an undocumented way to change this behavior? On MacOs, Chrome and Safari both open a new tab on Cmd+Enter. Maintaining an IE behavior on a Mac seems counter-intuitive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
*** Bug 1339412 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
And, we could make canonize complete to browser.fixup.alternate.prefix and browser.fixup.alternate.suffix, so the user can adapt it to his needs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Marco Bonardo [::mak] from comment #107) > And, we could make canonize complete to browser.fixup.alternate.prefix and > browser.fixup.alternate.suffix, so the user can adapt it to his needs. We already use .suffix, see https://searchfox.org/mozilla- central/rev/c3fef66a5b211ea8038c1c132706d02db408093a/browser/base/content/urlbarBindings.xml#1048-1055 . I think using prefix can be a follow-up bug, that doesn't seem super valuable to me (in fact, I would prefer to get rid of the alternate stuff as it's currently needlessly being mixed in with other bits of URL fixup in nsDefaultURIFixup, but that's a separate discussion). I'll remove shift support here because it affects the pref name, and adding a pref and then renaming it immediately seems stupid. Try: https://treeherder.mozilla.org/#/jobs?repo=try=aad17bf2c7fa4acaf46e1d71cf79069d192d5ecd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
https://treeherder.mozilla.org/#/jobs?repo=try=e1ef953500c15e1a86adb2456623e886df479bf8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Also, if we're going to change this on only some platforms, given the contention, the most straightforward thing would be to have a pref that we default to different values on Windows - then Windows users who don't care for the IE behaviour can flip it, or vice versa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Comment on attachment 8818332 Bug 237027 - Properly handle accel keys in address bar on macOS. https://reviewboard.mozilla.org/r/98432/#review98694 Seems to me from comment 81 that this change should not be OS X - specific. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
:Gijs I don't understand what you mean about a pref on Windows if we only change this "on only some platforms", given that platform would be macOS where that behaviour is the odd one. Why do a pref? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to :Gijs Kruitbosch from comment #86) > Also, if we're going to change this on only some platforms, given the > contention, the most straightforward thing would be to have a pref that we > default to different values on Windows - then Windows users who don't care > for the IE behaviour can flip it, or vice versa. A pref would make sense, especially if we want to be able to test both behaviors on all platforms. I didn't suggest it mostly because of comment 62, but that comment was arguably more about exposing the pref in the UI than about having a pref in the implementation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Marco Bonardo [::mak] (Away 9-26 Aug) from comment #103) > I made a small sheet to better understand what changes here, please check > and comment if something doesn't look correct. > https://docs.google.com/spreadsheets/d/ > 1VVEVjyIYRZIFteM71j5bJhENa2xXT82gaikr0WgpKLA/edit#gid=0 > > I didn't test the patch, I just assumed, on IRC Gijs said it's likely > different. > Anyway, I added a row with the behavior I'm suggesting, that is pretty much > the same as Chromium, apart ALT+Enter on the Mac. Unfortunately, I failed to access that table. Can you make it public? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Florian Quèze [:florian] [:flo] from comment #90) > (In reply to :Gijs Kruitbosch from comment #86) > > Also, if we're going to change this on only some platforms, given the > > contention, the most straightforward thing would be to have a pref that we > > default to different values on Windows - then Windows users who don't care > > for the IE behaviour can flip it, or vice versa. > > A pref would make sense, especially if we want to be able to test both > behaviors on all platforms. I didn't suggest it mostly because of comment > 62, but that comment was arguably more about exposing the pref in the UI > than about having a pref in the implementation. Yeah - I don't think we want UI, but if we're going to do different things per-OS we might as well implement-via-hidden-pref than hardcode the OS distinctions. There's plenty of precedent for that, e.g. backspace-for-history.back being a hidden pref (browser.backspace_action) that's different on Linux vs. elsewhere. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Created attachment 8818332 Bug 237027 - Properly handle accel keys in address bar on macOS. Review commit: https://reviewboard.mozilla.org/r/98432/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/98432/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
(In reply to Anthony Ramine [:nox] from comment #87) > :Gijs I don't understand what you mean about a pref on Windows if we only > change this "on only some platforms", given that platform would be macOS > where that behaviour is the odd one. Why do a pref? As I understand comment #84, if we keep this behaviour (ctrl-enter completing to www..com) at all, it'll be on Windows only. I don't see how macOS is special - Windows is, and Linux and macOS should get the 'open in a new tab' behaviour. What I'm saying is that whether we use the existing canonizeURL behaviour should go be behind a pref that's true on Windows and false everywhere else (ifdef'd in all.js). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
I made a small sheet to better understand what changes here, please check and comment if something doesn't look correct. https://docs.google.com/spreadsheets/d/1VVEVjyIYRZIFteM71j5bJhENa2xXT82gaikr0WgpKLA/edit#gid=0 I didn't test the patch, I just assumed, on IRC Gijs said it's likely different. Anyway, I added a row with the behavior I'm suggesting, that is pretty much the same as Chromium, apart ALT+Enter on the Mac. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Change puts a burden on current users. But if the new way is better, lets change. I remember when the ribbon replace menus in Microsoft Office. The change meant extra work for those of us used to the old behavior. However, it looked to me like a couple of people who were not good at computers were able to learn to use the ribbon more easily than they had used the menus. I believe the ribbon is better than the menus, and was worth having to learn. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
Yes, it's true that any change has the potential to interrupt current users. But, if FF could detect when to append ".com" vs. when to open a new tab based on the entered URL, then this is a very minimal change for current users. The current behavior of ".com-completion in same tab, when applicable" could remain in place. The only behavior that's actually needs to change is from the existing "cmd-enter does nothing" to "cmd-enter opens in new tab" when .com-completion is not applicable. Furthermore, with the proliferation of TLDs, it seems like .com-completion has become less useful. Adding a config to change this behavior doesn't seem like an unreasonable approach either. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 66566]
As a lowly user (not dev), please can we have some kind of option regarding ALT+ENTER behaviour? And to summarise my following comments, options for behaviour for CTRL+ENTER too? It could be just set in about:config, depending on how popular the alternative behaviours are. For example, CTRL+ENTER autocomplete vs open address in new tab. I personally don't use ALT+ENTER for generating a URL in a new tab. In fact, I can't explain why but I've only just noticed its new tab behaviour literally today. For example, I use tab mix plus to generate duplicate pages with history when I need a new tab (using CTRL+T), except with links, when CTRL+mouseclick works very nicely. I do appreciate that users develop habits and look for flexibility in usage between keyboard and mouse actions, so if ALT+ENTER is good for someone, then that's what they like and why should they change. Having said that, I haven't ever used ALT+ENTER for that functionality. I actually use ALT+ENTER with an extension called URL suffix (lovely, practical add-on IMO), which allows additional keystroke combos (beyond CTRL+ENTER) to generate additional URL prefixes & suffixes. I've configured ALT+ENTER to add a www. and .co.uk to a URL. This 'open address in a new tab' honestly never used to occur (for me), so I sense something may have changed or has been updated in firefox, relatively recently, given I do use these keyboard shortcuts for autocompletion. I've found some references to loss of this behaviour when using tab mix plus. Most posts are ancient but there was an isolated report in Nov 2015, involving a beta of FF 43. Anyway, ALT+ENTER and firefox led me here. I do agree with one contributor that one can't just bung in an option every time there's a conflict but when one's talking about keystrokes (both ALT+ENTER and CTRL+ENTER) which directly affect daily tasks/usability, perhaps there's an argument for considering support for alternatives. Standardisation is generally speaking good but we've got usage differences across browsers and platforms, which I can't see being harmonised easily and, depending on the solution, I would have thought we're not talking about much in the way of code changes, if we just added some choices in about:config. Sorry if I'm talking nonsense though - I'm not a coder. Regards, Gary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/66566 Title: Inconsistent shortcuts for new tab Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Won't Fix Status in firefox-3.0 package in Ubuntu: Won't Fix Status in firefox-3.5 package in Ubuntu: Won't Fix Bug description: There are currently too many shortcuts when opening a link in a new tab: - location bar: + - GO button: + click - search bar: + - SEARCH button + click - links: + click - menu bar: + click - BACKWARD/FORWARD button: + click This is one of the reasons I'm keeping with Opera. There it is always the shift key and I have to remember only one key. Thanks for reading! To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
