[arch-general] Sorting by subject makes Evolution crash
Hi :)
Evolution crashes if I sort mails by subject. I got the obligatory reply
at the Evolution mailing list, that usually other users get, when having
an issue with Evolution. "It should be the fault of the distro", in my
case Arch Linux.
I don't think so, however, can anybody sort mails by subject with an up
to date Arch Linux install? Reporting the bug to upstream seems to be
useless. Perhaps something is broken for Arch or my Arch install only.
Regards,
Ralf
-------- Forwarded Message --------
From: Ralf Mardorf
On Fri, 2013-11-29 at 13:37 +0100, Ralf Mardorf wrote:
On Fri, 2013-11-29 at 13:21 +0100, Andre Klapper wrote:
On Fri, 2013-11-29 at 12:46 +0100, Ralf Mardorf wrote:
However, Evolution does change it's behaviour with each upgrade to current stable versions of it's dependencies from upstream Either stop spreading FUD, or be way more exact. The issues do change,
Of course they change; releases done to include changes.
at the moment it's annoying for me that Evolution crashes when I try to sort by subject.
Something in your distributions is *seriously* broken. That is not Evolution. I have not seen Evolution crash for a very long time; and I *use* it every single day for 8+ hours.
I'm serious and not trolling. What distro does provide a stable Evolution?
openSUSE. At least it is entirely stable for me, on my hardware.
It's in the mail header, but FWIW, the version is 3.10.2 on a 64-bit up to date Arch Linux, IOW every dependency should be the current stable release from upstream. I don't remember when the issue started, but it seems to be one of the issues that appeared after upgrading other software, IOW seemingly something from the dependency chain.
Of course, everything of significance is built on a dependency chain. It is a problem when people believe it is OK to just willy-nilly upgrade random parts of that chain. That component W is a stable release does not mean that X, Y, and Z will run using it without issue; X, Y, and Z may need to be updated to reflect changes in W. Or at least QC needs to occur.
Anyway, again, 3.8.x was stable for me, and 3.10.x is stable for me. I sort, and search, and read, and send... all day long.
Neither Arch Linux nor I do willy-nilly upgrade something, but I will forward this to Arch general mailing list. I'm using Linux only for more then 10 years. Suse isn't an option for my needs. Regards, Ralf
[2013-11-29 16:13:42 +0100] Ralf Mardorf:
Evolution crashes if I sort mails by subject.
As usual, a backtrace would be nice...
I'm using Linux only for more then 10 years.
Then you must know that discussing problems without giving the least bit of debugging information never goes very far. No, other people should not have to ask. It's up to you to describe all the details from your first message on. Next time you do this your post will be rejected. Cheers. -- Gaetan
On Fri, 2013-11-29 at 06:54 -1000, Gaetan Bisson wrote:
[2013-11-29 16:13:42 +0100] Ralf Mardorf:
Evolution crashes if I sort mails by subject.
As usual, a backtrace would be nice...
I'm using Linux only for more then 10 years.
Then you must know that discussing problems without giving the least bit of debugging information never goes very far. No, other people should not have to ask. It's up to you to describe all the details from your first message on. Next time you do this your post will be rejected.
I'm a Linux user, not a Linux developer. It's hard to get useful information when Evolution does crash. When Evolution does run without issues there are already tons of confusing messages, for example, today Evolution run without an issue, while not sorting by subject. When everything is ok [1]. I deleted the contend of the .xsession-errors files and tried to forced a crash by sorting by subject, running Evolution in a terminal emulation. _No_ crash, it took a very long time to sort by subject and Evolution became unresponsive during sorting. Nothing was ad to .xsession-errors and the only output after starting Evolution was: (evolution:9200): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files It's not that easy to _use_ something and to troubleshoot. At the moment I'm willing to disassemble my computer to troubleshoot a kernel issue. I will do this, when I don't need the computer, but usually I need this computer and the Evolution bug(s) appear from time to time, not when I decide to troubleshoot. What can a user do, to _use_ the machine and to troubleshoot? Linux isn't my hobby, I'm using Linux as a tool. More precise, what should I do to troubleshoot the Evolution bug? Regards, Ralf [1] $ grep evolution .xsession-errors ** (evolution:805): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (evolution:805): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files ** (evolution-alarm-notify:835): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (evolution:805): libnotify-WARNING **: Failed to connect to proxy ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): Gtk-CRITICAL **: gtk_widget_get_style_context: assertion 'GTK_IS_WIDGET (widget)' failed (evolution:805): Gtk-CRITICAL **: gtk_style_context_invalidate: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files (evolution:805): camel-WARNING **: CamelVeeStore::get_trash_folder_sync() reported failure without setting its GError ** (evolution:805): WARNING **: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files
[2013-11-29 18:20:57 +0100] Ralf Mardorf:
I'm a Linux user, not a Linux developer.
I'm not asking you to develop anything. Just to report informative messages that your operating system makes readily available to you through a few simple commands. Obtaining a backtrace is a straightforward, well-documented process: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#Getting_the_trac... It's fine for a Linux user of ten years not to know how to do this, but it shows that they have little interest in getting things fixed...
I deleted the contend of the .xsession-errors files and tried to forced a crash by sorting by subject, running Evolution in a terminal emulation.
You mean that you just typed "evolution" in an xterm?
_No_ crash, it took a very long time to sort by subject and Evolution became unresponsive during sorting. Nothing was ad to .xsession-errors and the only output after starting Evolution was:
(evolution:9200): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Now *that* is an actual piece of information. Although it seems unrelated to your sort-crash, thanks for reporting it...
It's not that easy to _use_ something and to troubleshoot. At the moment I'm willing to disassemble my computer to troubleshoot a kernel issue. I will do this, when I don't need the computer, but usually I need this computer and the Evolution bug(s) appear from time to time, not when I decide to troubleshoot.
Your original message made it sound like Evolution crashes every single time you try to sort by subject. And now you say that the issue is not always reproducible? When you report an issue, you need to give all the information you have in the first email you send. Not just say "X crashes; help" and wait for someone else to extract details from you later on. -- Gaetan
On Fri, 29 Nov 2013 18:20:57 +0100
Ralf Mardorf
[...]
When everything is ok [1].
When an application crashes, it can't produce a useful info in a log file. You need to use an external tool like gdb or valgrind. Of course, gdb backtrace is useful only when debugging symbols are not stripped, and I'm pretty sure they are in extra/evolution...
[...]
What can a user do, to _use_ the machine and to troubleshoot? Linux isn't my hobby, I'm using Linux as a tool. More precise, what should I do to troubleshoot the Evolution bug?
Speaking from my own experience, if you need an email client that just works (tm), avoid evolution: there are plenty of other similar programs...
Regards, Ralf
Cheers, -- Leonid Isaev GnuPG key: 0x164B5A6D Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
On , Leonid Isaev wrote:
Speaking from my own experience, if you need an email client that just works (tm), avoid evolution: there are plenty of other similar programs...
From my experience, I never had ANY problem with mutt. Tomas Volf -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
participants (4)
-
Gaetan Bisson
-
Leonid Isaev
-
Paladin
-
Ralf Mardorf