Bug#730050: vcalendar plugin crash
You wrote:
> Or before, is it different without claws-mail running?
Before starting claws or anything else:
interface org.gnome.Shell.CalendarServer {
methods:
GetEvents(in x since,
in x until,
in b force_reload,
out a(sssbxxa{sv}) events);
signals:
Changed();
properties:
readonly x Since = 0;
readonly x Until = 0;
};
With claws running and looking around in the gnome calendar, it swaps
between these two variants:
interface org.gnome.Shell.CalendarServer {
methods:
GetEvents(in x greeting,
in x greeting,
in b greeting,
out a(sssbxxa{sv}) events);
signals:
properties:
};
interface org.gnome.Shell.CalendarServer {
methods:
GetEvents(in x since,
in x until,
in b force_reload,
out a(sssbxxa{sv}) events);
signals:
Changed();
properties:
readonly x Since = 1388404620;
readonly x Until = 1391428620;
};
and once claws crashes it is in the last step (except the timestamps
changes).
/Simon
signature.asc
Description: PGP signature
Bug#730050: vcalendar plugin crash
On Thu, Nov 21, 2013 at 01:25:14PM +0100, Simon Josefsson wrote: > You wrote: > > > On Thu, Nov 21, 2013 at 10:28:00AM +0100, Simon Josefsson wrote: > > > You wrote: > > > > > > > tags 730050 moreinfo > > > > thanks > > > > > > > > Hi Simon, > > > > > > > > On Wed, Nov 20, 2013 at 07:17:13PM +0100, Simon Josefsson wrote: > > > > > Package: claws-mail-vcalendar-plugin > > > > > Version: 3.8.1-2 > > > > > > > > > > The plugin crashes with the backtrace below. I've used the > > > > > plugin for several months without issue, but something seems to > > > > > be causing problems. I'm not convinced it is related, but > > > > > whenever this happens, I have always clicked around in the > > > > > GNOME Calendar from the toolbar at the top of the screen. > > > > > > > > I don't think it's related but thanks for the details. Anyway > > > > the backtrace doesn't contain useful info other than the crash. > > > > Can you install the debug package (claws-mail-extra-plugins-dbg), > > > > and reproduce the crash? > > > > > > > > Please run “env LC_MESSAGES=C gdb” (or your preferred way to do > > > > it) to be sure the diagnostic messages are in English. > > > > > > I reproduced it again, I still had to click around a bit in the > > > GNOME Calendar to trigger it (no idea why). Maybe just clicking in > > > any non-claws window is sufficient, although I wasn't able to > > > trigger it that way. Or it is just not related. > > > > Now it's clear it's related, because the crash is within the > > function which handles the DBus requests (generated by the GNOME > > Calendar). > > > > AFAICS the assert causing the crash fails because of the null > > user_data pointer in frame #4 (user_data=0x0). > > > > Could be the interface of the org.gnome.Shell.CalendarServer has > > been changed? Can you try the following command in a terminal and see > > the how the org.gnome.Shell.CalendarServer looks? > > It looks the same for me. Should I run it after claws has crashed? Or before, is it different without claws-mail running? -- Ricardo Mones ~ RTFM - "Read The Manual" (The 'F' is silent). Usually a very good idea. Bjarne Stroustrup signature.asc Description: Digital signature
Bug#730050: vcalendar plugin crash
You wrote:
> On Thu, Nov 21, 2013 at 10:28:00AM +0100, Simon Josefsson wrote:
> > You wrote:
> >
> > > tags 730050 moreinfo
> > > thanks
> > >
> > > Hi Simon,
> > >
> > > On Wed, Nov 20, 2013 at 07:17:13PM +0100, Simon Josefsson wrote:
> > > > Package: claws-mail-vcalendar-plugin
> > > > Version: 3.8.1-2
> > > >
> > > > The plugin crashes with the backtrace below. I've used the
> > > > plugin for several months without issue, but something seems to
> > > > be causing problems. I'm not convinced it is related, but
> > > > whenever this happens, I have always clicked around in the
> > > > GNOME Calendar from the toolbar at the top of the screen.
> > >
> > > I don't think it's related but thanks for the details. Anyway
> > > the backtrace doesn't contain useful info other than the crash.
> > > Can you install the debug package (claws-mail-extra-plugins-dbg),
> > > and reproduce the crash?
> > >
> > > Please run “env LC_MESSAGES=C gdb” (or your preferred way to do
> > > it) to be sure the diagnostic messages are in English.
> >
> > I reproduced it again, I still had to click around a bit in the
> > GNOME Calendar to trigger it (no idea why). Maybe just clicking in
> > any non-claws window is sufficient, although I wasn't able to
> > trigger it that way. Or it is just not related.
>
> Now it's clear it's related, because the crash is within the
> function which handles the DBus requests (generated by the GNOME
> Calendar).
>
> AFAICS the assert causing the crash fails because of the null
> user_data pointer in frame #4 (user_data=0x0).
>
> Could be the interface of the org.gnome.Shell.CalendarServer has
> been changed? Can you try the following command in a terminal and see
> the how the org.gnome.Shell.CalendarServer looks?
It looks the same for me. Should I run it after claws has crashed?
/Simon
>
> Command is “gdbus introspect --session --dest
> org.gnome.Shell.CalendarServer
> --object-path /org/gnome/Shell/CalendarServer”
>
> Expected output (only claws-mail running here):
> [...]
> interface org.gnome.Shell.CalendarServer {
> methods:
> GetEvents(in x greeting,
> in x greeting,
> in b greeting,
> out a(sssbxxa{sv}) events);
> signals:
> properties:
> };
> [...]
>
> This could also be related with http://bugs.debian.org/683283.
>
> thanks in advance,
>
> > Thanks,
> > /Simon
> >
> > (claws-mail:5435): GLib-CRITICAL **: g_variant_unref: assertion
> > `value->ref_count > 0' failed icalcomponent.c:265: BADARG: Bad
> > argument to function claws-mail: icalcomponent.c:265:
> > icalcomponent_as_ical_string: Assertion `0' failed.
> >
> > Program received signal SIGABRT, Aborted.
> > 0x7437e475 in *__GI_raise (sig=)
> > at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> > 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or
> > directory. (gdb) bt
> > #0 0x7437e475 in *__GI_raise (sig=)
> > at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> > #1 0x743816f0 in *__GI_abort () at abort.c:92
> > #2 0x74377621 in *__GI___assert_fail (
> > assertion=assertion@entry=0x7fffe2356d98 "0", file= > out>, file@entry=0x7fffe2358a70 "icalcomponent.c",
> > out>line=line@entry=265,
> > function=function@entry=0x7fffe2358d60
> > "icalcomponent_as_ical_string") at assert.c:81
> > #3 0x7fffe2328d76 in icalcomponent_as_ical_string
> > (component=0x1b89b10) at icalcomponent.c:265
> > #4 0x7fffe2320498 in handle_method_call (connection= > out>, sender=, object_path=,
> > interface_name=, method_name=,
> > parameters=, invocation=0xd4de40, user_data=0x0)
> > at vcal_dbus.c:103
> > #5 0x73142b55 in ?? ()
> > from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6
> > 0x74f1b355 in g_main_context_dispatch ()
> > from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688
> > in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8
> > 0x74f1ba82 in g_main_loop_run ()
> > from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77293797
> > in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> > ---Type to continue, or q to quit---
> > #10 0x0044d320 in main (argc=1, argv=0x7fffe368) at
> > main.c:1686 (gdb) bt
> > #0 0x7437e475 in *__GI_raise (sig=)
> > at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> > #1 0x743816f0 in *__GI_abort () at abort.c:92
> > #2 0x74377621 in *__GI___assert_fail (
> > assertion=assertion@entry=0x7fffe2356d98 "0", file= > out>, file@entry=0x7fffe2358a70 "icalcomponent.c",
> > out>line=line@entry=265,
> > function=function@entry=0x7fffe2358d60
> > "icalcomponent_as_ical_string") at assert.c:81
> > #3 0x7fffe2328d76 in icalcomponent_as_ical_string
> > (component=0x1b89b10) at icalcomponent.c:265
> > #4 0x7fffe2320498 in handle_method_call (connection= > out>, sender=, object_path=,
> > interface_name=, method_name=,
Bug#730050: vcalendar plugin crash
On Thu, Nov 21, 2013 at 10:28:00AM +0100, Simon Josefsson wrote:
> You wrote:
>
> > tags 730050 moreinfo
> > thanks
> >
> > Hi Simon,
> >
> > On Wed, Nov 20, 2013 at 07:17:13PM +0100, Simon Josefsson wrote:
> > > Package: claws-mail-vcalendar-plugin
> > > Version: 3.8.1-2
> > >
> > > The plugin crashes with the backtrace below. I've used the plugin
> > > for several months without issue, but something seems to be causing
> > > problems. I'm not convinced it is related, but whenever this
> > > happens, I have always clicked around in the GNOME Calendar from
> > > the toolbar at the top of the screen.
> >
> > I don't think it's related but thanks for the details. Anyway the
> > backtrace doesn't contain useful info other than the crash. Can you
> > install the debug package (claws-mail-extra-plugins-dbg), and
> > reproduce the crash?
> >
> > Please run “env LC_MESSAGES=C gdb” (or your preferred way to do it)
> > to be sure the diagnostic messages are in English.
>
> I reproduced it again, I still had to click around a bit in the GNOME
> Calendar to trigger it (no idea why). Maybe just clicking in any
> non-claws window is sufficient, although I wasn't able to trigger it
> that way. Or it is just not related.
Now it's clear it's related, because the crash is within the function
which handles the DBus requests (generated by the GNOME Calendar).
AFAICS the assert causing the crash fails because of the null user_data
pointer in frame #4 (user_data=0x0).
Could be the interface of the org.gnome.Shell.CalendarServer has been
changed? Can you try the following command in a terminal and see the how
the org.gnome.Shell.CalendarServer looks?
Command is “gdbus introspect --session --dest org.gnome.Shell.CalendarServer
--object-path /org/gnome/Shell/CalendarServer”
Expected output (only claws-mail running here):
[...]
interface org.gnome.Shell.CalendarServer {
methods:
GetEvents(in x greeting,
in x greeting,
in b greeting,
out a(sssbxxa{sv}) events);
signals:
properties:
};
[...]
This could also be related with http://bugs.debian.org/683283.
thanks in advance,
> Thanks,
> /Simon
>
> (claws-mail:5435): GLib-CRITICAL **: g_variant_unref: assertion
> `value->ref_count > 0' failed icalcomponent.c:265: BADARG: Bad argument
> to function claws-mail: icalcomponent.c:265:
> icalcomponent_as_ical_string: Assertion `0' failed.
>
> Program received signal SIGABRT, Aborted.
> 0x7437e475 in *__GI_raise (sig=)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> 64../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or
> directory. (gdb) bt
> #0 0x7437e475 in *__GI_raise (sig=)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #1 0x743816f0 in *__GI_abort () at abort.c:92
> #2 0x74377621 in *__GI___assert_fail (
> assertion=assertion@entry=0x7fffe2356d98 "0", file=,
> file@entry=0x7fffe2358a70 "icalcomponent.c", line=line@entry=265,
> function=function@entry=0x7fffe2358d60
> "icalcomponent_as_ical_string") at assert.c:81
> #3 0x7fffe2328d76 in icalcomponent_as_ical_string
> (component=0x1b89b10) at icalcomponent.c:265
> #4 0x7fffe2320498 in handle_method_call (connection= out>, sender=, object_path=,
> interface_name=, method_name=,
> parameters=, invocation=0xd4de40, user_data=0x0)
> at vcal_dbus.c:103
> #5 0x73142b55 in ?? ()
> from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x74f1b355
> in g_main_context_dispatch ()
> from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688
> in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8
> 0x74f1ba82 in g_main_loop_run ()
> from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77293797 in
> gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
> ---Type to continue, or q to quit---
> #10 0x0044d320 in main (argc=1, argv=0x7fffe368) at
> main.c:1686 (gdb) bt
> #0 0x7437e475 in *__GI_raise (sig=)
> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #1 0x743816f0 in *__GI_abort () at abort.c:92
> #2 0x74377621 in *__GI___assert_fail (
> assertion=assertion@entry=0x7fffe2356d98 "0", file=,
> file@entry=0x7fffe2358a70 "icalcomponent.c", line=line@entry=265,
> function=function@entry=0x7fffe2358d60
> "icalcomponent_as_ical_string") at assert.c:81
> #3 0x7fffe2328d76 in icalcomponent_as_ical_string
> (component=0x1b89b10) at icalcomponent.c:265
> #4 0x7fffe2320498 in handle_method_call (connection= out>, sender=, object_path=,
> interface_name=, method_name=,
> parameters=, invocation=0xd4de40, user_data=0x0)
> at vcal_dbus.c:103
> #5 0x73142b55 in ?? ()
> from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x74f1b355
> in g_main_context_dispatch ()
> from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688
> in ?? () from /lib/x86_64-linux-gnu/li
Bug#730050: vcalendar plugin crash
You wrote: > tags 730050 moreinfo > thanks > > Hi Simon, > > On Wed, Nov 20, 2013 at 07:17:13PM +0100, Simon Josefsson wrote: > > Package: claws-mail-vcalendar-plugin > > Version: 3.8.1-2 > > > > The plugin crashes with the backtrace below. I've used the plugin > > for several months without issue, but something seems to be causing > > problems. I'm not convinced it is related, but whenever this > > happens, I have always clicked around in the GNOME Calendar from > > the toolbar at the top of the screen. > > I don't think it's related but thanks for the details. Anyway the > backtrace doesn't contain useful info other than the crash. Can you > install the debug package (claws-mail-extra-plugins-dbg), and > reproduce the crash? > > Please run “env LC_MESSAGES=C gdb” (or your preferred way to do it) > to be sure the diagnostic messages are in English. I reproduced it again, I still had to click around a bit in the GNOME Calendar to trigger it (no idea why). Maybe just clicking in any non-claws window is sufficient, although I wasn't able to trigger it that way. Or it is just not related. Thanks, /Simon (claws-mail:5435): GLib-CRITICAL **: g_variant_unref: assertion `value->ref_count > 0' failed icalcomponent.c:265: BADARG: Bad argument to function claws-mail: icalcomponent.c:265: icalcomponent_as_ical_string: Assertion `0' failed. Program received signal SIGABRT, Aborted. 0x7437e475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x7437e475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x743816f0 in *__GI_abort () at abort.c:92 #2 0x74377621 in *__GI___assert_fail ( assertion=assertion@entry=0x7fffe2356d98 "0", file=, file@entry=0x7fffe2358a70 "icalcomponent.c", line=line@entry=265, function=function@entry=0x7fffe2358d60 "icalcomponent_as_ical_string") at assert.c:81 #3 0x7fffe2328d76 in icalcomponent_as_ical_string (component=0x1b89b10) at icalcomponent.c:265 #4 0x7fffe2320498 in handle_method_call (connection=, sender=, object_path=, interface_name=, method_name=, parameters=, invocation=0xd4de40, user_data=0x0) at vcal_dbus.c:103 #5 0x73142b55 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x74f1b355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x74f1ba82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77293797 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ---Type to continue, or q to quit--- #10 0x0044d320 in main (argc=1, argv=0x7fffe368) at main.c:1686 (gdb) bt #0 0x7437e475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x743816f0 in *__GI_abort () at abort.c:92 #2 0x74377621 in *__GI___assert_fail ( assertion=assertion@entry=0x7fffe2356d98 "0", file=, file@entry=0x7fffe2358a70 "icalcomponent.c", line=line@entry=265, function=function@entry=0x7fffe2358d60 "icalcomponent_as_ical_string") at assert.c:81 #3 0x7fffe2328d76 in icalcomponent_as_ical_string (component=0x1b89b10) at icalcomponent.c:265 #4 0x7fffe2320498 in handle_method_call (connection=, sender=, object_path=, interface_name=, method_name=, parameters=, invocation=0xd4de40, user_data=0x0) at vcal_dbus.c:103 #5 0x73142b55 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x74f1b355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x74f1ba82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77293797 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ---Type to continue, or q to quit--- #10 0x0044d320 in main (argc=1, argv=0x7fffe368) at main.c:1686 (gdb) q A debugging session is active. Inferior 1 [process 5435] will be killed. Quit anyway? (y or n) y jas@latte:~$ signature.asc Description: PGP signature
Bug#730050: vcalendar plugin crash
tags 730050 moreinfo thanks Hi Simon, On Wed, Nov 20, 2013 at 07:17:13PM +0100, Simon Josefsson wrote: > Package: claws-mail-vcalendar-plugin > Version: 3.8.1-2 > > The plugin crashes with the backtrace below. I've used the plugin for > several months without issue, but something seems to be causing > problems. I'm not convinced it is related, but whenever this happens, > I have always clicked around in the GNOME Calendar from the toolbar at > the top of the screen. I don't think it's related but thanks for the details. Anyway the backtrace doesn't contain useful info other than the crash. Can you install the debug package (claws-mail-extra-plugins-dbg), and reproduce the crash? Please run “env LC_MESSAGES=C gdb” (or your preferred way to do it) to be sure the diagnostic messages are in English. thanks in advance, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README signature.asc Description: Digital signature
Bug#730050: vcalendar plugin crash
Package: claws-mail-vcalendar-plugin Version: 3.8.1-2 The plugin crashes with the backtrace below. I've used the plugin for several months without issue, but something seems to be causing problems. I'm not convinced it is related, but whenever this happens, I have always clicked around in the GNOME Calendar from the toolbar at the top of the screen. /Simon (claws-mail:5301): GLib-CRITICAL **: g_variant_unref: assertion `value->ref_count > 0' failed icalcomponent.c:265: BADARG: Bad argument to function claws-mail: icalcomponent.c:265: icalcomponent_as_ical_string: Försäkran "0" falsk. Program received signal SIGABRT, Aborted. 0x7437e475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 ../nptl/sysdeps/unix/sysv/linux/raise.c: Filen eller katalogen finns inte. (gdb) bt #0 0x7437e475 in *__GI_raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x743816f0 in *__GI_abort () at abort.c:92 #2 0x74377621 in *__GI___assert_fail (assertion=0x7fffe20a9d98 "0", file=, line=265, function=0x7fffe20abd60 "icalcomponent_as_ical_string") at assert.c:81 #3 0x7fffe207bd76 in icalcomponent_as_ical_string () from /usr/lib/claws-mail/plugins/vcalendar.so #4 0x7fffe2073498 in ?? () from /usr/lib/claws-mail/plugins/vcalendar.so #5 0x73142b55 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x74f1b355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x74f1b688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x74f1ba82 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x77293797 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #10 0x0044d320 in main (argc=1, argv=0x7fffe368) at main.c:1686 (gdb) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
