ersion: 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:
5-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 pu
Disabled: 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/
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
Packag
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 bu
ns, 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/fo
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
unk 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 t
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
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 def
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
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 l
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
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 separa
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
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
+
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
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
Pa
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
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
--
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:
Evo
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)
22 matches
Mail list logo
