[Bug 1839247] Re: gvfsd-smb-browse crashed with SIGABRT

*** 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,

[Bug 1651130] Re: gvfsd-smb-browse crashed with SIGABRT in talloc_abort()

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.

[Bug 1705287] Re: gedit crashed with SIGSEGV in gd_tagged_entry_remove_tag() when closing a file or searching through the text of one

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.

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

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

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

> 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

[Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

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:

[Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

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.

[Bug 1644498] [NEW] apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

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

[Bug 1575248] Re: "AppStream cache update completed, but some metadata was ignored due to errors." on "sudo apt-get update"

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.

[Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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.

[Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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.

[Bug 1547340] Re: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

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

[Bug 1527817] Re: unhelpful error message "Parsing filters is unsupported."

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

[Bug 1364285] Re: nautilus does not start

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

[Bug 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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

[Bug 1557370] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

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.

[Bug 1506430] Re: /usr/lib/evolution/evolution-alarm-notify:5:g_settings_set_property:object_set_property:g_object_new_internal:g_object_new_valist:g_object_new

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

[Bug 1548226] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist() on Login

*** 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

[Bug 273951] Re: evolution-alarm-notify crashed with SIGSEGV in g_object_newv()

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

[Bug 1264075] Re: evolution-alarm-notify crashed with signal 5 in g_settings_set_property()

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

[Bug 1386599] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist()

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

[Bug 1259943] Re: evolution-alarm-notify crashed with signal 5 in g_settings_set_property()

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

[Bug 1548226] Re: evolution-alarm-notify crashed with signal 5 in g_object_new_valist() on Login

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

[Bug 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

*** 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

[Bug 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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

[Bug 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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

[Bug 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

*** 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

[Bug 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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 1195662] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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

[Bug 1235177] Re: evolution-source-registry crashed with SIGSEGV in magazine_chain_pop_head()

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

[Bug 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

*** 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

[Bug 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

*** 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

[Bug 1527495] Re: evolution-source-registry crashed with SIGSEGV in g_slice_alloc() after closing evolution

*** 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

[Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

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

[Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

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

[Bug 1509269] [NEW] evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()

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

[Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_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

[Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

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

[Bug 1494804] Re: evolution-source-registry crashed with SIGABRT in g_assertion_message()

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

[Bug 1483643] Re: evolution hangs (grey window) while previewing an email

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

[Bug 1483643] Re: evolution hangs (grey window) while previewing an email

strace-25363-evolution-addressbook-factory strace of evolution- addressbook-factory taken over the same few minutes. ** Attachment added: strace-25363-evolution-addressbook-factory

[Bug 1483643] Re: evolution hangs (grey window) while previewing an email

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

[Bug 1483643] Re: evolution hangs (grey window) while previewing an email

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

[Bug 1483643] Re: evolution hangs (grey window) while previewing an email

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

[Bug 1483643] [NEW] evolution hangs (grey window) while previewing an email

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

[Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

** 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.

[Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account

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

[Bug 1299747] Re: Cannot create PGP key in Ubuntu 14.04

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