[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened
I can confirm that the bug described in the askubuntu.com link above is
the bug I'm seeing; the workaround stated there (renaming `~/.fonts`)
was enough to prevent it occurring.
I have fontconfig 2.12.6-0ubuntu2 installed (and my fontconfig-config is
the same version).
Should this bug report be moved to the fontconfig package, as apparently
it's the underlying cause of the bug? Presumably it will be fixed
if/when Ubuntu updates to a newer version of fontconfig.
--
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/1856624
Title:
Firefox freezes temporarily at 100% CPU when Chromium is opened
Status in Mozilla Firefox:
Unknown
Status in firefox package in Ubuntu:
Confirmed
Bug description:
When Firefox is open, and I open Chromium, many features of Firefox
fail to work for several seconds. (To reproduce, start with neither
Firefox nor Chromium open; open Firefox, and allow one or more web
pages to load; then open Chromium; the issue starts a second or two
after Chromium is opened.) This is a temporary issue, lasting for
several seconds; the length of time it lasts appears to depend on how
many open tabs have been viewed since Firefox opened (on my computer,
around 10 seconds with 1 tab having been viewed, around a minute with
10 tabs having been viewed). This reproduces even when running Firefox
as `firefox -safe-mode`.
While the issue is ongoing (i.e. starting around a second after Chromium is
open, and persisting for typically tens of seconds), some features of Firefox
work, but most do not:
- Scrolling the current tab short distances succeeds, showing the expected
text on the page.
- Scrolling the current tab long distances (several screeenfuls) causes the
page to be "cut off" past a certain point, with only a blank background
rendering.
- Moving the mouse cursor over a link does not change the mouse cursor
(expected behaviour, and behaviour while the issue is not ongoing, is for it to
change to a hand shape).
- Changing tab causes the resulting page not to display: rather, a grey
background is displayed, and sometimes a loading spinner.
- Changing tab back then causes the original page not to render, as if it
were new, despite the fact it was correctly displayed earlier.
- The address bar functions as normal; the issue does not appear to affect
address bar functionality.
Additionally, while the issue is ongoing, Firefox uses 100% CPU.
At some point after the issue in question starts, it stops, and all
Firefox features return to normal (including any missing or
incorrectly rendered page content, which renders again when the issue
ends).
The trigger is specifically the act of opening Chromium: Firefox can
function just fine once the issue ends, even if Chromium is still
open, and functions just fine if Chromium is opened first.
I have an (unconfirmed) theory that opening Chromium is causing some
operation within Firefox to become very slow, using up all the CPU
time, and the other observed misbehaviours within Firefox are a
consequence of how slowly it is running; however, I've listed them all
anyway in case it provides clarity into what the specific nature of
the bug is.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 71.0+build5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ais523 1800 F pulseaudio
BuildID: 20191205184924
Channel: Unavailable
CurrentDesktop: X-Cinnamon
Date: Tue Dec 17 00:29:10 2019
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-11-11 (35 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric
600
MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:722
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profile
[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened
I have a total of 8 GB of RAM and 2 GB of swap.
Reproducing the issue with a memory monitor opened, however, showed that
the issue was not related to memory exhaustion: I had at least 2 GB of
unused RAM at all times, and although the swap was enabled, it was not
used (the swap usage remained at 0 throughout the entire period).
Also observed during this test: eight Firefox processes (seven Web
Content and one WebExtensions) were running at 50% CPU usage each
throughout the time of nonresponsiveness (my computer has 4 cores, so
between them they were using up the entire CPU usage of the computer).
** Changed in: firefox (Ubuntu)
Status: Incomplete => 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/1856624
Title:
Firefox freezes temporarily at 100% CPU when Chromium is opened
Status in firefox package in Ubuntu:
New
Bug description:
When Firefox is open, and I open Chromium, many features of Firefox
fail to work for several seconds. (To reproduce, start with neither
Firefox nor Chromium open; open Firefox, and allow one or more web
pages to load; then open Chromium; the issue starts a second or two
after Chromium is opened.) This is a temporary issue, lasting for
several seconds; the length of time it lasts appears to depend on how
many open tabs have been viewed since Firefox opened (on my computer,
around 10 seconds with 1 tab having been viewed, around a minute with
10 tabs having been viewed). This reproduces even when running Firefox
as `firefox -safe-mode`.
While the issue is ongoing (i.e. starting around a second after Chromium is
open, and persisting for typically tens of seconds), some features of Firefox
work, but most do not:
- Scrolling the current tab short distances succeeds, showing the expected
text on the page.
- Scrolling the current tab long distances (several screeenfuls) causes the
page to be "cut off" past a certain point, with only a blank background
rendering.
- Moving the mouse cursor over a link does not change the mouse cursor
(expected behaviour, and behaviour while the issue is not ongoing, is for it to
change to a hand shape).
- Changing tab causes the resulting page not to display: rather, a grey
background is displayed, and sometimes a loading spinner.
- Changing tab back then causes the original page not to render, as if it
were new, despite the fact it was correctly displayed earlier.
- The address bar functions as normal; the issue does not appear to affect
address bar functionality.
Additionally, while the issue is ongoing, Firefox uses 100% CPU.
At some point after the issue in question starts, it stops, and all
Firefox features return to normal (including any missing or
incorrectly rendered page content, which renders again when the issue
ends).
The trigger is specifically the act of opening Chromium: Firefox can
function just fine once the issue ends, even if Chromium is still
open, and functions just fine if Chromium is opened first.
I have an (unconfirmed) theory that opening Chromium is causing some
operation within Firefox to become very slow, using up all the CPU
time, and the other observed misbehaviours within Firefox are a
consequence of how slowly it is running; however, I've listed them all
anyway in case it provides clarity into what the specific nature of
the bug is.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 71.0+build5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ais523 1800 F pulseaudio
BuildID: 20191205184924
Channel: Unavailable
CurrentDesktop: X-Cinnamon
Date: Tue Dec 17 00:29:10 2019
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-11-11 (35 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric
600
MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:grepre
[Desktop-packages] [Bug 1856624] [NEW] Firefox freezes temporarily at 100% CPU when Chromium is opened
Public bug reported:
When Firefox is open, and I open Chromium, many features of Firefox fail
to work for several seconds. (To reproduce, start with neither Firefox
nor Chromium open; open Firefox, and allow one or more web pages to
load; then open Chromium; the issue starts a second or two after
Chromium is opened.) This is a temporary issue, lasting for several
seconds; the length of time it lasts appears to depend on how many open
tabs have been viewed since Firefox opened (on my computer, around 10
seconds with 1 tab having been viewed, around a minute with 10 tabs
having been viewed). This reproduces even when running Firefox as
`firefox -safe-mode`.
While the issue is ongoing (i.e. starting around a second after Chromium is
open, and persisting for typically tens of seconds), some features of Firefox
work, but most do not:
- Scrolling the current tab short distances succeeds, showing the expected text
on the page.
- Scrolling the current tab long distances (several screeenfuls) causes the
page to be "cut off" past a certain point, with only a blank background
rendering.
- Moving the mouse cursor over a link does not change the mouse cursor
(expected behaviour, and behaviour while the issue is not ongoing, is for it to
change to a hand shape).
- Changing tab causes the resulting page not to display: rather, a grey
background is displayed, and sometimes a loading spinner.
- Changing tab back then causes the original page not to render, as if it were
new, despite the fact it was correctly displayed earlier.
- The address bar functions as normal; the issue does not appear to affect
address bar functionality.
Additionally, while the issue is ongoing, Firefox uses 100% CPU.
At some point after the issue in question starts, it stops, and all
Firefox features return to normal (including any missing or incorrectly
rendered page content, which renders again when the issue ends).
The trigger is specifically the act of opening Chromium: Firefox can
function just fine once the issue ends, even if Chromium is still open,
and functions just fine if Chromium is opened first.
I have an (unconfirmed) theory that opening Chromium is causing some
operation within Firefox to become very slow, using up all the CPU time,
and the other observed misbehaviours within Firefox are a consequence of
how slowly it is running; however, I've listed them all anyway in case
it provides clarity into what the specific nature of the bug is.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 71.0+build5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ais523 1800 F pulseaudio
BuildID: 20191205184924
Channel: Unavailable
CurrentDesktop: X-Cinnamon
Date: Tue Dec 17 00:29:10 2019
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-11-11 (35 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600
MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:722
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=71.0/20191205184924 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0DDKKC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DDKKC:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.
** Affects: firefox (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 firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1856624
Title:
Firefox freezes temporar
[Desktop-packages] [Bug 1629587] Re: ESC ] 6; 12; ? ESC \ freezes xterm with 100% CPU usage
This is now fixed in Ubuntu Bionic. Version information: $ xterm -version XTerm(330) $ dpkg -s xterm | grep ^Version Version: 330-1ubuntu2 This seems consistent with the statement that it was fixed in version 326d. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1629587 Title: ESC ] 6;12;? ESC \ freezes xterm with 100% CPU usage Status in xterm package in Ubuntu: Confirmed Bug description: Running the following command: printf "\x1b]6;12;?\x1b\\" while inside an xterm window causes xterm to stop responding to user input, produce no output, and consume 100% CPU usage (i.e. it runs indefinitely on a single core). Most likely this is a consequence of an infinite loop. The bug is triggered by the character sequence produced by the above printf command being sent to the terminal via any means (e.g. placing it in a text file, and then using cat to display the text file, also causes xterm to enter an infinite loop). The character sequence that printf outputs when running this command has a similar form to that of many xterm terminal commands, so most likely xterm is attempting to interpret it a command. That said, I don't think it's actually meaningful (it starts an OSC 6 command but then gives it invalid parameters). Nonetheless, xterm probably shouldn't go into an infinite loop as a response to a program printing text on it, no matter how meaningless that text is. (I stumbled across this particular sequence by chance when writing a terminal testsuite.) I'm not sure whether this is a security-related bug or not, but it's certainly plausible that it could be used as a remote denial of service, or possibly to make it harder to view text files (as attempting to display them in xterm will cause it to crash). People don't normally expect running cat to be able to crash their terminal. As such, I'm classifying it as security-related as a precaution. Feel free to override this setting if you disagree. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xterm 322-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,snap,compiztoolbox,move,place,grid,gnomecompat,neg,obs,session,vpswitch,mousepoll,imgpng,resize,animation,expo,ezoom,workarounds,wall,fade,unitymtgrabhandles,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 1 18:11:36 2016 DistUpgraded: 2016-05-02 01:10:52,869 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExecutablePath: /usr/bin/xterm GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:2186] InstallationDate: Installed on 2014-06-03 (851 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic.efi.signed root=UUID=e92d655d-cf36-4d45-90e7-30a0f9d0949e ro quiet splash vt.handoff=7 SourcePackage: xterm UpgradeStatus: Upgraded to xenial on 2016-05-02 (152 days ago) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.68 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2186 dmi.board.vendor: Hewlett-Packard dmi.board.version: 35.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.68:bd09/21/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2186:rvr35.12:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Just to clarify why this bug has so many me-too votes: the bug happened once to me, during an update, and never happened again (i.e. it fixed itself, and I can print just fine, etc.). I subscribed to this thread because I was curious as to what was going on, and I did see the problem myself once but the bug doesn't have any ongoing effect on me and I can't reproduce it. I suspect that the majority of the people who have confirmed the bug are in the same boat, whereas some people here have the issue recurring for some reason. (It's unclear why; either there's something relevantly different about their configuration, or this is actually two different bugs with the same symptoms.) So although there are a lot of people here, I suspect rather fewer people are in a position to test the fix; I can't reproduce the bug, and thus there's no point in me testing the fix, as a working fix would look the same as a fix that had no effect at all. Would it be reasonable for people in my position to retract our confirmations of the bug, if we can no longer reproduce? Or is it best to leave the confirmation there, because I definitely did see the bug happen, once? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Yakkety: Fix Committed Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"
I haven't seen this happen on my Ubuntu system for a while. I'm now on Evolution 3.22.3 and Ubuntu 16.10, so I'm guessing it was fixed when a newer version of Evolution was included in Ubuntu via the normal release process. As for how long these things take to get fixed after an upstream fix, it basically depends on whether the distribution consider the bug important enough to warrant an update or backport (doing these is always somewhat risky, because there's the chance that a fix for one bug could end up unintentionally breaking something else, and there's a definite desire that the system should not become worse as the result of an update). Possibilities on Ubuntu involve pushing the bugfix to everyone (this normally only happens if it's a really big problem or a security problem); pushing the bugfix only to people who've opted in to receiving backports faster; pushing the bugfix only to people who have opted into "proposed changes" to the OS (although I don't know for certain, this is typically done if pushing the change more widely is considered a good idea but there's a worry that something might break in the process); or only pushing the changes out with the next version of the OS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1615732 Title: Execution of filter 'Junk check' fails with "Empty cache file" Status in Evolution: Unknown Status in evolution package in Ubuntu: Confirmed Status in evolution package in Debian: New Bug description: I currently use an Evolution setup in which I retrieve email via IMAP from an unfiltered mailbox, and then use Evolution to automatically filter for spam/junk mail. This process works as expected upon starting Evolution: all email is retrieved from the mailbox (and thus resides in the Inbox folder, where it arrived), then it's filtered to identify spam, and then the spam is moved from the Inbox to a Junk folder. However, after Evolution has been running for some time (hard to estimate because it requires an email to be received, but likely 5-10 minutes; it's possible that this is just "one email refresh interval" but also possible that something else is going on), newly received email stops being filtered for spam, and all the email remains in the Inbox. This happens at least in the case of receiving one email at a time, and most likely in the case where multiple emails are received in one send/receive cycle. When this failure to remove spam/junk happens, there's a yellow banner at the top of the screen saying, for example (the filename is not always the same), "Error while performing operation. Execution of filter 'Junk check' failed: Empty cache file: /home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052" I checked the contents of the file in question; it appears to be a copy of the email that was just received, including all headers. (It's possible that there's a race condition here and that the file was empty when the filter looked at it, but became populated just after it errored out, but perhaps something else is going on.) This behaviour is a problem because it means that either I have to delete junk mail by hand, or else that I have to repeatedly close and reopen Evolution so that the automated system will work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 22 17:19:59 2016 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-06-03 (811 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_GB.UTF-8 LANGUAGE=en_GB:en XDG_RUNTIME_DIR= SourcePackage: evolution UpgradeStatus: Upgraded to xenial on 2016-05-02 (112 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1615732/+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 1589472] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install
Same issue is happening to me, although in my case it's happening on attempts to upgrade or remove rather than on initial install. Here's what happens (the .deb file in question is a security update that was obtained from the Ubuntu archives using apt and should be the latest version): $ sudo dpkg -i /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb Selecting previously unselected package nvidia-opencl-icd-340:i386. (Reading database ... 817449 files and directories currently installed.) Preparing to unpack .../nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb (--install): there is no script in the new version of the package - giving up Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.23-0ubuntu4) ... Errors were encountered while processing: /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb $ sudo dpkg -r nvidia-opencl-icd-340:i386 (Reading database ... 817447 files and directories currently installed.) Removing nvidia-opencl-icd-340:i386 (340.96-0ubuntu3.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: error processing package nvidia-opencl-icd-340:i386 (--remove): subprocess installed pre-removal script returned error exit status 5 Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.23-0ubuntu4) ... Errors were encountered while processing: nvidia-opencl-icd-340:i386 Incidentally, I have no idea why the package in question is on my system in the first place. It doesn't appear to be a dependency of anything (neither apt nor dpkg complains when I try to remove it), and I don't have an NVidia graphics card, so I'd have had no reason to install it manually. /var/lib/snapd/lib/gl (which seems to be relevant due to the "Unit var- lib-snapd-lib-gl.mount" message) exists, but is an empty directory. Nothing appears to be mounted there. ** Summary changed: - package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install + package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 cannot be installed, removed or upgraded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1589472 Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 cannot be installed, removed or upgraded Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hi! I am can not install package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 in Ubuntu 16.04. See video attachment. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 6 17:52:23 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 ocl-icd-libopencl1 2.2.8-1 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgTerminalLog: Removing nvidia-opencl-icd-340 (340.96-0ubuntu3.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: error processing package nvidia-opencl-icd-340 (--remove): subprocess installed pre-removal script returned error exit status 5 DuplicateSignature: package:nvidia-opencl-icd-340:340.96-0ubuntu3.16.04.1 Removing nvidia-opencl-icd-340 (340.96-0ubuntu3.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: error processing package nvidia-opencl-icd-340 (--remove): subprocess installed pre-removal script returned error exit status 5 ErrorMessage: subprocess installed pre-removal script returned error exit status 5 GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2015-05-23 (380 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
[Desktop-packages] [Bug 1615732] [NEW] Execution of filter 'Junk check' fails with "Empty cache file"
Public bug reported: I currently use an Evolution setup in which I retrieve email via IMAP from an unfiltered mailbox, and then use Evolution to automatically filter for spam/junk mail. This process works as expected upon starting Evolution: all email is retrieved from the mailbox (and thus resides in the Inbox folder, where it arrived), then it's filtered to identify spam, and then the spam is moved from the Inbox to a Junk folder. However, after Evolution has been running for some time (hard to estimate because it requires an email to be received, but likely 5-10 minutes; it's possible that this is just "one email refresh interval" but also possible that something else is going on), newly received email stops being filtered for spam, and all the email remains in the Inbox. This happens at least in the case of receiving one email at a time, and most likely in the case where multiple emails are received in one send/receive cycle. When this failure to remove spam/junk happens, there's a yellow banner at the top of the screen saying, for example (the filename is not always the same), "Error while performing operation. Execution of filter 'Junk check' failed: Empty cache file: /home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052" I checked the contents of the file in question; it appears to be a copy of the email that was just received, including all headers. (It's possible that there's a race condition here and that the file was empty when the filter looked at it, but became populated just after it errored out, but perhaps something else is going on.) This behaviour is a problem because it means that either I have to delete junk mail by hand, or else that I have to repeatedly close and reopen Evolution so that the automated system will work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 22 17:19:59 2016 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-06-03 (811 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_GB.UTF-8 LANGUAGE=en_GB:en XDG_RUNTIME_DIR= SourcePackage: evolution UpgradeStatus: Upgraded to xenial on 2016-05-02 (112 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1615732 Title: Execution of filter 'Junk check' fails with "Empty cache file" Status in evolution package in Ubuntu: New Bug description: I currently use an Evolution setup in which I retrieve email via IMAP from an unfiltered mailbox, and then use Evolution to automatically filter for spam/junk mail. This process works as expected upon starting Evolution: all email is retrieved from the mailbox (and thus resides in the Inbox folder, where it arrived), then it's filtered to identify spam, and then the spam is moved from the Inbox to a Junk folder. However, after Evolution has been running for some time (hard to estimate because it requires an email to be received, but likely 5-10 minutes; it's possible that this is just "one email refresh interval" but also possible that something else is going on), newly received email stops being filtered for spam, and all the email remains in the Inbox. This happens at least in the case of receiving one email at a time, and most likely in the case where multiple emails are received in one send/receive cycle. When this failure to remove spam/junk happens, there's a yellow banner at the top of the screen saying, for example (the filename is not always the same), "Error while performing operation. Execution of filter 'Junk check' failed: Empty cache file: /home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052" I checked the contents of the file in question; it appears to be a copy of the email that was just received, including all headers. (It's possible that there's a race condition here and that the file was empty when the filter looked at it, but became populated just after it errored out, but perhaps something else is going on.) This behaviour is a problem because it means that either I have to delete junk mail by hand, or else that I have to repeatedly close and reopen Evolution so that the automated system will work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
[Desktop-packages] [Bug 1191238] Re: Color palette resets to default upon losing focus
And still fixed on Wily. I think Ubuntu has pulled in the upstream fix and there's nothing more to change now. ** Changed in: gnome-terminal (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus Status in gnome-terminal package in Ubuntu: Fix Released Bug description: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: "Use colors from system theme" off, "Built-in schemes": custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced". Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different application that does not overlap gnome-terminal, you can see the color change happen onscreen.) I'm on a system (Unity) where keyboard focus always follows window focus, so I'm not sure if the trigger is losing keyboard focus or window focus; if you have a different window manager, you might want to test both separately. Expected behaviour: the bright blue text remains bright blue upon switching away from the window, and continues to remain bright blue when returning to the window. Text continues to be bright blue unless the foreground color or palette are changed again. Observed behaviour: the bright blue text becomes light red upon switching away from the window, and continues to remain light red upon returning to the window. Text continues to be light red unless the foreground color or palette are changed again. Changing palette entries other than 9 does not cause the text to become blue again; nor does changing the foreground color away from 9 and then back to 9. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 Date: Sat Jun 15 09:25:32 2013 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2009-12-14 (1278 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-10-18 (239 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+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 1191238] Re: Color palette resets to default upon losing focus
Cannot reproduce on Trusty. I assume the change has filtered through to Ubuntu by now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus Status in “gnome-terminal” package in Ubuntu: Triaged Bug description: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: Use colors from system theme off, Built-in schemes: custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced. Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different application that does not overlap gnome-terminal, you can see the color change happen onscreen.) I'm on a system (Unity) where keyboard focus always follows window focus, so I'm not sure if the trigger is losing keyboard focus or window focus; if you have a different window manager, you might want to test both separately. Expected behaviour: the bright blue text remains bright blue upon switching away from the window, and continues to remain bright blue when returning to the window. Text continues to be bright blue unless the foreground color or palette are changed again. Observed behaviour: the bright blue text becomes light red upon switching away from the window, and continues to remain light red upon returning to the window. Text continues to be light red unless the foreground color or palette are changed again. Changing palette entries other than 9 does not cause the text to become blue again; nor does changing the foreground color away from 9 and then back to 9. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 Date: Sat Jun 15 09:25:32 2013 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2009-12-14 (1278 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-10-18 (239 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+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 1203414] Re: evolution crashes shortly after opening when evolution-indicator is installed
Cannot reproduce on trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed Status in “evolution-indicator” package in Ubuntu: New Bug description: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double- clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+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 1203414] Re: evolution crashes shortly after opening when evolution-indicator is installed
I just checked on saucy. The bug is still reproducible (evolution crashes with evolution-indicator installed, does not crash if evolution- indicator is not installed). ** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed Status in “evolution-indicator” package in Ubuntu: New Bug description: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double- clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+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 1191238] Re: Color palette resets to default upon losing focus
Just tested on saucy; I can still reproduce this bug. ** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: Use colors from system theme off, Built-in schemes: custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced. Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different application that does not overlap gnome-terminal, you can see the color change happen onscreen.) I'm on a system (Unity) where keyboard focus always follows window focus, so I'm not sure if the trigger is losing keyboard focus or window focus; if you have a different window manager, you might want to test both separately. Expected behaviour: the bright blue text remains bright blue upon switching away from the window, and continues to remain bright blue when returning to the window. Text continues to be bright blue unless the foreground color or palette are changed again. Observed behaviour: the bright blue text becomes light red upon switching away from the window, and continues to remain light red upon returning to the window. Text continues to be light red unless the foreground color or palette are changed again. Changing palette entries other than 9 does not cause the text to become blue again; nor does changing the foreground color away from 9 and then back to 9. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 Date: Sat Jun 15 09:25:32 2013 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2009-12-14 (1278 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-10-18 (239 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+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 1203414] Re: evolution crashes shortly after opening
Followup: I tried running Evolution in a terminal, and opening a message via double-click to reproduce the crash. I've attached the output that it spewed to the terminal. ** Attachment added: output sent to the terminal via evolution (probably stderr, may be stdout, I didn't redirect them separately) https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1203414/+attachment/3744053/+files/evolution-stderr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed Status in “evolution-indicator” package in Ubuntu: New Bug description: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double- clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+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 1203414] Re: evolution crashes shortly after opening
The crash appears to be in evolution-indicator from the backtrace, and went away when I uninstalled evolution-indicator, so that's a good guess as to the culprit ** Package changed: evolution (Ubuntu) = evolution-indicator (Ubuntu) ** Summary changed: - evolution crashes shortly after opening + evolution crashes shortly after opening when evolution-indicator is installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-indicator in Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed Status in “evolution-indicator” package in Ubuntu: New Bug description: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double- clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+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 1203414] [NEW] evolution crashes shortly after opening when evolution-indicator is installed
Public bug reported: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double-clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) ** Affects: evolution-indicator (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: _usr_bin_evolution.1000.crash https://bugs.launchpad.net/bugs/1203414/+attachment/3744051/+files/_usr_bin_evolution.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed Status in “evolution-indicator” package in Ubuntu: New Bug description: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double- clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+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 1191238] [NEW] Color palette resets to default upon losing focus
Public bug reported: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: Use colors from system theme off, Built-in schemes: custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced. Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different application that does not overlap gnome-terminal, you can see the color change happen onscreen.) I'm on a system (Unity) where keyboard focus always follows window focus, so I'm not sure if the trigger is losing keyboard focus or window focus; if you have a different window manager, you might want to test both separately. Expected behaviour: the bright blue text remains bright blue upon switching away from the window, and continues to remain bright blue when returning to the window. Text continues to be bright blue unless the foreground color or palette are changed again. Observed behaviour: the bright blue text becomes light red upon switching away from the window, and continues to remain light red upon returning to the window. Text continues to be light red unless the foreground color or palette are changed again. Changing palette entries other than 9 does not cause the text to become blue again; nor does changing the foreground color away from 9 and then back to 9. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 Date: Sat Jun 15 09:25:32 2013 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2009-12-14 (1278 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-10-18 (239 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus Status in “gnome-terminal” package in Ubuntu: New Bug description: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: Use colors from system theme off, Built-in schemes: custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced. Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different
[Desktop-packages] [Bug 1005007] Re: evolution takes forever to retrieve new messages
Can no longer reproduce, presumably because the offending IMAP server has started working again. This bug may well require access to a broken IMAP server for testing; I'm not entirely sure where I could get one, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages Status in “evolution” package in Ubuntu: Confirmed Bug description: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+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 1005007] [NEW] evolution takes forever to retrieve new messages
Public bug reported: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages Status in “evolution” package in Ubuntu: New Bug description: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+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 1005007] Re: evolution takes forever to retrieve new messages
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages Status in “evolution” package in Ubuntu: New Bug description: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+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 1005007] Re: evolution takes forever to retrieve new messages
Oh, and just checked: the list of emails shown in the problematic mailbox is the list as of the last time the mailbox worked, it doesn't account for emails received since. (Emails related to this bug are going into that mailbox; that's how I noticed.) I can also access the mailbox in question via a web browser, so I should still be able to communicate about the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages Status in “evolution” package in Ubuntu: New Bug description: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+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 1005007] Re: evolution takes forever to retrieve new messages
One more experiment: if I reboot the system and then load Evolution and give it no input, nor switch to the offending mailbox, it's left with one Checking for new mail in the status bar. (There were originally four; I have four mailboxes. But three of them disappeared.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages Status in “evolution” package in Ubuntu: New Bug description: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+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
