Marking as non-private as it has been long enough I am comfortable that
anything stored is no longer sensative. I do not think there is
anything sensitive in there anyway.
I am back here now as I have just raised bug 1839247 however that only
looks related by attributed package and nothing more.
*** This bug is a duplicate of bug 1541335 ***
https://bugs.launchpad.net/bugs/1541335
Apport is once again suggesting this is a duplicate of a private bug.
If I am mean to check whether this is a duplicate or not I cannot do so.
If apport is comfortable to strip this bug of its Private tag,
Eyeballed the attachments and cannot see anything sensitive in them.
Making this public instead of private.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bu
The Archive Manager GUI does not seem to handle some files that it
possibly should. It seems that for some files it is necessary to
instead install unrar and then uncompress these files from the command
line with `uunrar x `
--
You received this bug notification because you are a member of Ubunt
Actually, having looked at the SD card again it seems that the old
partitions were removed but the new partition was not added.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bu
I was creating a Ext4 filesystem on an SD card. AS far as I could tell
the process had completed several seconds before the crash report came
up.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bu
Making a second attempt after reopening the Disks application seemed to
work.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1547340
Title:
gnome-disks crashed with SIGS
I started seeing this message:
AppStream cache update completed, but some metadata was ignored due to errors.
on one machine on the 23rd November 2016. I would expect this to be a seperate
issue. I cannot reproduce it right now, if I am able to do so later I will
try and raise a new bug.
--
Public bug reported:
Periodically I get emails from a machine with the subject:
Cron if [ -x /etc/munin/plugins/apt_all ]; then
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
>/dev/null; fi
And a body of:
App
The error message popped out again for me just now. I still cannot get
it to reproduce reliably but I have raised Bugs1644498 to start
diagnosis.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launch
Thank you. I could not figure out which combination of commands to send
appsteamcli. I had tried status and validate without success. Here is
the requested output:
manager@Jenkins:~$ sudo appstreamcli refresh --verbose --force
[sudo] password for manager:
** (appstreamcli:32754): DEBUG: Refresh
> I think I found the issue, I'll prepare a patch.
That is great news. Is there a work around I could try that would
silence the emails for a while? Let me know if you would like me to try
out the updated binary.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Installing the fixed file is not really a work around but the error
piping would work. I'll live with the noise for now and try to get the
updated package installed once it reaches xenial-backports.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
I select 'add a new key or item' > PGP Key and I am presented with a
dialogue box requesting my Full Name and E-mail address. The first 3
attempts that I made failed but the final attempt seemed to succeed.
For the last attempt I avoided expanding the 'Advanced key options'
area. I thought that p
** Summary changed:
- Can't create EWS or MAPI account
+ Evolution appears unable to create EWS or Exchange MAPI account
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/
I can confirm that I hit this bug while running 3.10.4 installed from the
Ubuntu Software Center for the current LTS version of Ubuntu
$ lsb_release -rc
Release:14.04
Codename: trusty
I had previous setup Gmail (googlemail) and a pop account in Evolution.
Some recent changes to my
I did
$ sudo gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
the resulting file is attached. I had a quick look through it and could not
see any sensitive data in there.
** Attachment added: "$ sudo gdb --batch --ex "t a a bt" -pid=`pidof evolution`
&>bt.txt"
https://bugs
Public bug reported:
I had left evolution running overnight. It seems to develop issues
after being left to run for a while on my current system.
This morning I returned focus to the evolution window and tried to view
the latest email from my Exchange account in the preview window.
"retrieving m
strace-7088-evolution-alarm-notify.txt showing strace for evolution-
alarm-notify taken over the same few minutes.
** Attachment added: "strace-7088-evolution-alarm-notify.txt"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442848/+files/strace-7088-evolution-ala
strace-6165-evolution-source-registry.txt strace volution-source-
registry of taken over the same few minutes.
** Attachment added: "strace-6165-evolution-source-registry.txt"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442849/+files/strace-6165-evolution-sour
strace-6288-evolution-calendar-factory.txt showing strace output of
evolution-calendar-factory taken over a few minutes.
** Attachment added: "strace-6288-evolution-calendar-factory.txt"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442846/+files/strace-6288-evo
strace-25363-evolution-addressbook-factory strace of evolution-
addressbook-factory taken over the same few minutes.
** Attachment added: "strace-25363-evolution-addressbook-factory"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442850/+files/strace-25363-evolut
I seem to be seeing this now. The other suggested possibilities when
reporting were bugz #1200934, #1200819 & #1383852. I can see on this
bug that some questions were posed.
> what accounts he/she has configured, whether any are from Ubuntu Online
> Accounts or GNOME Online Accounts?
I have a p
I had evolution-source-registry running for a while without noticing the
error reproducing itself.
The only output that looks suspect is:
Adding system-memo-list ('Source_35')
Adding system-task-list ('Source_36')
module-cache-reaper-Message: Scanning data directories
module-cache-reaper-Message:
Not so easily it seems.
$ sudo aptitude install libaccounts-glib0-dbgsym
evolution-data-server-online-accounts-dbgsym libglib2.0-0-dbgsym
The following NEW packages will be installed:
evolution-data-server-online-accounts-dbgsym{b} libaccounts-glib0-dbgsym
libglib2.0-0-dbgsym{b}
0 packages up
I don't quite understand that part about "seems like you didn't active
ddeb for trusty-updates". Do you mean that there are some steps I need
to take to enable the installation of debug symbols for packages that
come from trusty-updates?
If it is likely that this is a different issue, I can raise
Public bug reported:
Raising a new bug after discussions on Bug #1494804 suggested that this
was a different issue as the one documented under #1494804 originated in
15.10.
I don't know what I did to stimulate the problem. An error report
prompt appeared one day.
I'll answer the same questions
I raised Bug #1509269 which apport marked as a duplicate of Bug
#1200819.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1494804
Title:
evolution-source-registry cras
I have just raised Bug #1527495 which was initially suggested as a
possible duplicate of this bug and Bug #1195662. Now that apport has
done its thing my new bug has been marked as a duplicate of bug #1279108
which could suggest that this bug is also a duplicate of that one.
--
You received this
I have just raised Bug #1527495 which was initially suggested as a
possible duplicate of this bug and Bug #1235177. Now that apport has
done its thing my new bug has been marked as a duplicate of bug #1279108
which could suggest that this bug is also a duplicate of that one.
--
You received this
*** This bug is a duplicate of bug 1279108 ***
https://bugs.launchpad.net/bugs/1279108
Weirdly the top of this bug report currently states it is a duplicate of
nothing. I take it that is a launchpad but, as other bits of launchpad
manage to state it is a duplicate of bug #1279108 (which I don
*** This bug is a duplicate of bug 1279108 ***
https://bugs.launchpad.net/bugs/1279108
I have added a comment to each of the similar bugs (bug #1195662 and bug
#1235177) mentioning that they may also be a bug of bug #1279108. Sadly
bug #1279108 "Cannot be found" by me, which is usually a sign
*** This bug is a duplicate of bug 1279108 ***
https://bugs.launchpad.net/bugs/1279108
I could not find an open bug for launchpad that seemed to describe the
problem with the blank after the This bug report is a duplicate of:
message so I have raised
https://bugs.launchpad.net/launchpad/+bug/1
So I have tripped over the same problem again, but this time only Bug
#1195662 and Bug #1235177 were offered as suggestions. Bug #1527495
that I raised a while ago was not seen as a likely similarity.
It seems that I am able to periodically reproduce a problem, whether it
is one of the three bug
*** This bug is a duplicate of bug 1279108 ***
https://bugs.launchpad.net/bugs/1279108
So I have tripped over the same problem again, but this time only Bug
#1195662 and Bug #1235177 were offered as suggestions. Bug #1527495
that I raised a while ago was not seen as a likely similarity.
It
So I have tripped over the same problem again, but this time only Bug
#1195662 and Bug #1235177 were offered as suggestions. Bug #1527495
that I raised a while ago was not seen as a likely similarity.
It seems that I am able to periodically reproduce a problem, whether it
is one of the three bug
Seen again today.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1195662
Title:
evolution-source-registry crashed with SIGSEGV in
magazine_chain_pop_head()
To mana
Seen again today.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1235177
Title:
evolution-source-registry crashed with SIGSEGV in
magazine_chain_pop_head()
To mana
*** This bug is a duplicate of bug 1279108 ***
https://bugs.launchpad.net/bugs/1279108
Seen again today. As before #1195662 and Bug #1235177 were offered as
suggestions but bug #1279108 was not. Can anyone that is able to view
all four of these bugs make a judgement on whether the first two
I have looked through the traces and other logs files supplied, nothing
looks sensitive to me. Setting to public as I cannot see a reason to
keep this bug marked as private.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubun
I think I have seen something quite similar to this bug. I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstan
I think I have seen something quite similar to this bug. I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstan
I think I have seen something quite similar to this bug. I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstan
I think I have seen something quite similar to this bug. I made a fresh
report as Bug #1548226 which includes some valid symbolic stack traces.
Hopefully the developers will be able to use them to work on the issue.
Should this bug ticket be marked as a duplicate of Bug #1548226 as the
circumstan
Bug #1548226 has been marked as a duplicate of this bug. I cannot
access the extra details contained at
https://errors.ubuntu.com/problem/6278aa0a9d4c4b72421d1b1f986661f47e7357c5
so I cannot confirm if this is a duplicate or not.
Please could a public facing summary of the hidden details be provi
*** This bug is a duplicate of bug 1506430 ***
https://bugs.launchpad.net/bugs/1506430
Bug #1506430 contains very little information, so it is hard to say if
this is a duplicate of that bug or not. It looks as if things should be
fixed in 3.16.5-1ubuntu2; so if anyone has that package (or a l
I could not see anything sensitive in the logs so I have opened up this
bug to being public.
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpa
Seen again today and I like Michael suspect this might be a duplicate of
bug #1195662. That would add another 6 duplicates to the other bug and
up its heat by 36 and give it 11 more affected people which is another
44. That would give a total heat of 156+36+44=236. That would even be
enough to
I have apparently seen this error on:
$ uname -a
Linux thorne-ul-dt 3.16.0-71-generic #91~14.04.1-Ubuntu SMP Mon Apr 18 19:43:36
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I do not know how I caused it to happen though. The automatic error reporting
brought me here.
--
You received this bug notif
49 matches
Mail list logo
