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
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
b
Just tested on saucy; I can still reproduce this bug.
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1191238
Title:
Color palette resets to default upo
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 Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1191238
Title:
Color palette resets to
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 Ubuntu
Desktop Bugs, which is subscribed
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
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
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:
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
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1005007
Title:
evolution takes forever to retrieve new messages
To manage notifications about this bug go to:
https://bugs.launchpa
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)
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
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
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 Ubuntu
Des
Public bug reported:
Binary package hint: evolution
When sorting a folder by the "To" column, I would expect (and want) the
column to be sorted by the email address the message was sent to;
instead, it appears to be sorted by the literal text of the "To" column,
which often contains a realname fo
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/16710156/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/16710157/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/16710158/ProcStatus.txt
--
To col
Reported upstream as
https://gitlab.gnome.org/GNOME/evolution/issues/318.
(Launchpad thinks GNOME's bug tracker is somewhere else, so I haven't
been able to link that bug report to this one "officially".)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
Upstream have committed a fix at
https://gitlab.gnome.org/GNOME/evolution/commit/b66cdbbe6f33bcbfc12af52b788cf87f7c78c40b.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1814527
Ti
It isn't (except that if apport-bug were working, it would have made
sure the bug was filed against the right package!). Sorry, it's easy to
make a mistake when filing a bug manually.
** Package changed: evolution (Ubuntu) => apport (Ubuntu)
--
You received this bug notification because you are
Public bug reported:
Steps to reproduce:
In Evolution, open any email by double-clicking on it (so that the email
appears in a separate window). Press Ctrl-Shift-F to bring up a search
box at the bottom of the screen (allowing you to search for words in an
email). Type in a word that appears at l
`apport-cli --save /tmp/1814529.apport apport` appears to save the
collected information to a file, as intended. I used this mechanism to
generate the following information so that I could attach it to this bug
report (due to this bug, I can't use the normal mechanism):
ProblemType: Bug
ApportLog:
And an attempt using apport-collect:
I ran the command `apport-collect 1814529`.
apport-collect noticed the lack of authorisation, printing the following
text (I redacted the OAuth token):
{{{
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=«redacted»&allow_permissi
r, clicking either button
closes apport-bug with no visible further effect (and no messages on
standard output or standard error). Expected behaviour is for apport-bug
to open a page in my Web browser to allow me to file the bug.
If I revoke my computer's authorisation at https://launchpad.net/~
23 matches
Mail list logo
