[Desktop-packages] [Bug 2009712] [NEW] Gnome lock screen loses focus if a window opens while screen is locked
Public bug reported: The Gnome lock screen has caused me a lot of frustration over time, since I've often found that is unresponsive to the keyboard when I come back to the system and try to get back in after the screen lock has activated. I finally realized that this is usually due to the "Software Updater" window popping up while I'm away from the computer, though it can be triggered by any window opening while the screen is locked. To reproduce: Open a terminal window and type "sleep 15; gnome-terminal", then immediately click on the upper-right notification area and select the "Lock" option in the popup menu. Observe the screen go into lock. Wait 15 seconds. Press a key like Ctrl or Alt to wake the screen. Attempt to type in the password (or use a fingerprint reader if you have one). Nothing happens. Click the screen (or possibly tap/swipe it if you have a touchscreen). The password prompt will now appear, and it should be possible to type in the password (or use the fingerprint reader) This is a very annoying behavior. It shouldn't be necessary to click/tap the screen to restore focus when the whole desktop has been taken over by the screen locker. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 8 08:21:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-13 (146 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2009712 Title: Gnome lock screen loses focus if a window opens while screen is locked Status in gnome-shell package in Ubuntu: New Bug description: The Gnome lock screen has caused me a lot of frustration over time, since I've often found that is unresponsive to the keyboard when I come back to the system and try to get back in after the screen lock has activated. I finally realized that this is usually due to the "Software Updater" window popping up while I'm away from the computer, though it can be triggered by any window opening while the screen is locked. To reproduce: Open a terminal window and type "sleep 15; gnome-terminal", then immediately click on the upper-right notification area and select the "Lock" option in the popup menu. Observe the screen go into lock. Wait 15 seconds. Press a key like Ctrl or Alt to wake the screen. Attempt to type in the password (or use a fingerprint reader if you have one). Nothing happens. Click the screen (or possibly tap/swipe it if you have a touchscreen). The password prompt will now appear, and it should be possible to type in the password (or use the fingerprint reader) This is a very annoying behavior. It shouldn't be necessary to click/tap the screen to restore focus when the whole desktop has been taken over by the screen locker. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 8 08:21:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-10-13 (146 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 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/2009712/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Can this be incorporated into the Ubuntu 18.04 version? I manually
patched 3.30.2-1~ubuntu18.10.3, but was overwritten by an update to
3.30.2-1~ubuntu18.10.4.
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+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 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout
Correction, I am running Ubuntu 18.10, not 18.04.
--
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/1814169
Title:
Mutter upsteam bug: cannot overwrite workspaces layout
Status in mutter package in Ubuntu:
Fix Released
Bug description:
Running up-to-date Ubuntu Cosmic. Since I am running a version with
manually applied patched from below, I couldn't use the ubuntu-bug
helper.
Bug: When using GNOME extension “Workspace grid” that arranges
workspaces in a grid, one can find that horizontal switch animation is
replaced with a vertical one. This is caused by a bug in mutter
itself, it's acknowledged and fixed in upsteam. Applying the patch for
the current version in Ubuntu solves the issue as well.
GIFs of the issue could be found here: https://medium.com/@hkdb/patch-
gnome-3-30-for-workspace-grid-1ee8b1dd92f9.
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/270.
Upsteam fix:
https://gitlab.gnome.org/rmyorston/mutter/commit/97a3a9b24b3655003467d5fac6bb1ec1c60e
(merged into master 3 months ago).
The patch to fix is, literally, adding 1 meaningful line:
From 86a719cc78149b7db189ff7e5d1f16418d257e9e Mon Sep 17 00:00:00 2001
From: Ron Yorston
Date: Tue, 2 Oct 2018 12:47:05 +0100
Subject: [PATCH] Allow workspace layout to be overridden
meta_workspace_manager_override_workspace_layout is implemented by
calling meta_workspace_manager_update_workspace_layout which
respects the workspace_layout_overridden flag. After the first call
to meta_workspace_manager_override_workspace_layout all subsequent
calls fail silently.
Reset workspace_layout_overridden to FALSE before calling
meta_workspace_manager_update_workspace_layout.
Signed-off-by: Ron Yorston
---
src/core/meta-workspace-manager.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/core/meta-workspace-manager.c
b/src/core/meta-workspace-manager.c
index 2670f4938..abc819db0 100644
--- a/src/core/meta-workspace-manager.c
+++ b/src/core/meta-workspace-manager.c
@@ -496,6 +496,8 @@ meta_workspace_manager_override_workspace_layout
(MetaWorkspaceManager *workspac
int
n_rows,
int
n_columns)
{
+ workspace_manager->workspace_layout_overridden = FALSE;
+
meta_workspace_manager_update_workspace_layout (workspace_manager,
starting_corner,
vertical_layout,
--
2.17.1
Hopefully this one is fast to test and apply ;)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1814169/+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 1048373] Re: No option to remain in one filesystem
I'm running Ubuntu 16.04.2 LTS. I noticed my laptop was running slow and discovered that it was trying to back up files over a fuse.sshfs mount to another machine in my apartment. This should not happen. I'm probably going to have to disable deja-dup because of this issue and find some other way to do backups -- the machine I was sshfs'd to is probably where I should be sending my backups! -- 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/1048373 Title: No option to remain in one filesystem Status in deja-dup package in Ubuntu: Confirmed Bug description: I used "sshfs" to mount a remote filesystem in my home directory and it was backed up by Deja-Dup. I should, of course, have added the mount-point in my home directory to the exclude list, but I didn't realise until the backup had been running for hours and many GB had been downloaded on my ADSL connection from the remote SSHFS fileserver I was connected to. It would be useful if there was an option for Deja_Dup to remain in one filesystem during a backup to avoid this type of problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1048373/+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 63587] Re: Can't queue a song more than once in Rhythmbox
This bug is still present in Rhythmbox 3.0.2-0ubuntu2. Banshee had only briefly been the default music player in Ubuntu, and Rhythmbox is the default again (in main for Ubuntu 14.04 while Banshee is in universe). I have been using Banshee for several years, but a new bug has cropped up which makes that package nearly unusable for me. This queuing problem is the main reason I have not been using Rhythmbox. I consider the software incomplete if it doesn't have this feature. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/63587 Title: Can't queue a song more than once in Rhythmbox Status in One Hundred Papercuts: Invalid Status in The Rhythmbox Music Management Application: Confirmed Status in rhythmbox package in Ubuntu: Triaged Status in rhythmbox package in Debian: Confirmed Bug description: Binary package hint: rhythmbox Add a song to the Play Queue by whatever means, and try to add it again. You cannot. Imagine you *really* love this song and can't get enough of it - you want to hear it over and over again. But you cannot have more than one instance of any song in the play queue! :( To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/63587/+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 1374896] [NEW] Cannot mount HTC One m8 via MTP on Ubuntu 14.04
Public bug reported: I am unable to mount the filesystems on my HTC One m8 phone. It is an Android 4.x device, which only supports the Media Transfer Protocol for transferring files between the phone and a connected PC. USB Mass Storage is not supported. My phone is the variant sold by T-Mobile USA. When I use the mtp-detect program to connect, this message is printed at the begininng of the output: Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=0bb4 and PID=0f25) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Found 1 device(s): 0bb4:0f25 @ bus 5, dev 17 Attempting to connect device(s) ...so I am reporting this against libmtp, but there may be other related packages that are affected. At one point, I saw a gvfs error message. This might be considered related to bug #1314556, although I suspect that many devices will run into problems when they are new. Linux in general needs very robust MTP support that is as forward- compatible with new hardware as possible, especially now that newer handsets no longer support the old USB Mass Storage method of transferring files. It is not desirable to have new devices be unusable when they are released and have to wait 6 to 12 months for a new Ubuntu release before they start working, especially since many smartphones are only sold for a year or two before being replaced by new models. I use the XFCE desktop environment. I am able to get an Android Phone icon to appear on my desktop, but when I initially clicked on it, an error would occur and I'd be unable to mount the device. After enabling USB Debugging on the phone (which is a hidden feature on this particular device, requiring using a simple Easter egg to expose the setting), I began to be able to double-click the Android Phone icon and then get a window with one icon for Internal storage and another for SD card. However, clicking on either of those results in an error dialog with the message: Unhandled error message: Unable to open MTP device '[usb:005,011]' [mike@3po][~]$ lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 [mike@3po][~]$ uname -a Linux 3po 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux [mike@3po][~]$ apt-cache policy libmtp9 mtp-tools libmtp9: Installed: 1.1.6-20-g1b9f164-1ubuntu2 Candidate: 1.1.6-20-g1b9f164-1ubuntu2 Version table: *** 1.1.6-20-g1b9f164-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status mtp-tools: Installed: 1.1.6-20-g1b9f164-1ubuntu2 Candidate: 1.1.6-20-g1b9f164-1ubuntu2 Version table: *** 1.1.6-20-g1b9f164-1ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status [mike@3po][~]$ ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1374896 Title: Cannot mount HTC One m8 via MTP on Ubuntu 14.04 Status in “libmtp” package in Ubuntu: New Bug description: I am unable to mount the filesystems on my HTC One m8 phone. It is an Android 4.x device, which only supports the Media Transfer Protocol for transferring files between the phone and a connected PC. USB Mass Storage is not supported. My phone is the variant sold by T-Mobile USA. When I use the mtp-detect program to connect, this message is printed at the begininng of the output: Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=0bb4 and PID=0f25) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team Found 1 device(s): 0bb4:0f25 @ bus 5, dev 17 Attempting to connect device(s) ...so I am reporting this against libmtp, but there may be other related packages that are affected. At one point, I saw a gvfs error message. This might be considered related to bug #1314556, although I suspect that many devices will run into problems when they are new. Linux in general needs very robust MTP support that is as forward- compatible with new hardware as possible, especially now that newer handsets no longer support the old USB Mass Storage method of transferring files. It is not desirable to have new devices be unusable when they are released and have to wait 6 to 12 months for a new Ubuntu release before they start working, especially since many smartphones are only sold for a year or two before being replaced by new models. I use the XFCE desktop environment. I am able to get an Android Phone icon to appear on my desktop, but when I initially clicked on it, an error would occur
[Desktop-packages] [Bug 1019708] Re: Firefox pegs CPU usage immediately, even in safe mode
This bad behavior seems to have been caused by issues with futex system calls. Here's the most detailed description I've seen so far, including a small test program that can be used to replicate the behavior (I haven't tried it since it modifies the system time): https://lwn.net/Articles/504658/ Rather than rebooting, simply setting the system time manually or finding some other way to call settimeofday() would have also restored normal 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/1019708 Title: Firefox pegs CPU usage immediately, even in safe mode Status in “firefox” package in Ubuntu: Confirmed Bug description: After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in safe mode with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places. My home page is about:startpage, the Ubuntu standard. This should not happen. CPU usage should be at or near zero upon loading a simple page like that. [mike@3po][~]$ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 [mike@3po][~]$ apt-cache policy firefox firefox: Installed: 13.0.1+build1-0ubuntu0.11.10.1 Candidate: 13.0.1+build1-0ubuntu0.11.10.1 Version table: *** 13.0.1+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1019708/+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 1019708] Re: Firefox pegs CPU usage immediately, even in safe mode
Thanks. I was beginning to feel a bit silly after a reboot fixed my issue as well. I had first tried restarting my X environment, thinking that some Gnome libraries or protocols might have gotten out of sync somehow. I rarely reboot my machine since issues can normally be resolved through other means. -- 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/1019708 Title: Firefox pegs CPU usage immediately, even in safe mode Status in “firefox” package in Ubuntu: Confirmed Bug description: After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in safe mode with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places. My home page is about:startpage, the Ubuntu standard. This should not happen. CPU usage should be at or near zero upon loading a simple page like that. [mike@3po][~]$ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 [mike@3po][~]$ apt-cache policy firefox firefox: Installed: 13.0.1+build1-0ubuntu0.11.10.1 Candidate: 13.0.1+build1-0ubuntu0.11.10.1 Version table: *** 13.0.1+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1019708/+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 1019708] Re: Firefox pegs CPU usage immediately, even in safe mode
Just since I'm not sure I want to file another bug against something that may be in a library function or system call, I'll note here that mythfrontend and mythbackend processes (from MythTV) were also running hot on a machine I use as a DVR. Those processes are more heavily multi-threaded, so they showed well over 100% CPU usage. -- 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/1019708 Title: Firefox pegs CPU usage immediately, even in safe mode Status in “firefox” package in Ubuntu: Confirmed Bug description: After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in safe mode with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places. My home page is about:startpage, the Ubuntu standard. This should not happen. CPU usage should be at or near zero upon loading a simple page like that. [mike@3po][~]$ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 [mike@3po][~]$ apt-cache policy firefox firefox: Installed: 13.0.1+build1-0ubuntu0.11.10.1 Candidate: 13.0.1+build1-0ubuntu0.11.10.1 Version table: *** 13.0.1+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1019708/+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 1019708] [NEW] Firefox pegs CPU usage immediately, even in safe mode
Public bug reported: After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in safe mode with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places. My home page is about:startpage, the Ubuntu standard. This should not happen. CPU usage should be at or near zero upon loading a simple page like that. [mike@3po][~]$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 [mike@3po][~]$ apt-cache policy firefox firefox: Installed: 13.0.1+build1-0ubuntu0.11.10.1 Candidate: 13.0.1+build1-0ubuntu0.11.10.1 Version table: *** 13.0.1+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1019708 Title: Firefox pegs CPU usage immediately, even in safe mode Status in “firefox” package in Ubuntu: New Bug description: After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in safe mode with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places. My home page is about:startpage, the Ubuntu standard. This should not happen. CPU usage should be at or near zero upon loading a simple page like that. [mike@3po][~]$ lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 [mike@3po][~]$ apt-cache policy firefox firefox: Installed: 13.0.1+build1-0ubuntu0.11.10.1 Candidate: 13.0.1+build1-0ubuntu0.11.10.1 Version table: *** 13.0.1+build1-0ubuntu0.11.10.1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages 100 /var/lib/dpkg/status 7.0.1+build1+nobinonly-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1019708/+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
