Bug 824064

Created attachment 586079 [details]
File: dso_list

Created attachment 586080 [details]
File: build_ids

Created attachment 586081 [details]
File: maps

Created attachment 586082 [details]
File: backtrace

> comment:        saved session startup 

Could you be *much* more verbose, please? Tell exactly what you've done and whether this crash is reproducible. It looks a lot like a test-case will be needed.

| #0  event_get_from_xml (node=0xffffffff02e37920, uid=0x8cc8acb
| "040000008200E00074C5B7101A82E0080000000090B9A6B868B6CC01",
| '0' <repeats 16 times>, "1000000050DB45247DCEB74298CBCB88EB74B8C7")
| at vcal_manager.c:1056
|
| #1  vcal_manager_load_event (uid=0x8cc8acb
| "040000008200E00074C5B7101A82E0080000000090B9A6B868B6CC01",
| '0' <repeats 16 times>, "1000000050DB45247DCEB74298CBCB88EB74B8C7")
| at vcal_manager.c:1108
|        node = 0x2d7a600

To me, the upper 32 bits of the node=0xffffffff02e37920 ptr look very suspicious (invalid).

  1049          node = node->children;
  1050          while (node != NULL) {
  1051                  gchar *attendee = NULL;
  1052                  gchar *name = NULL;
  1053                  enum icalparameter_partstat answer = ICAL_PARTSTAT_NEEDS
ACTION;
  1054                  enum icalparameter_cutype cutype   = ICAL_CUTYPE_INDIVID
UAL;
  1055                  
  1056                  xmlnode = node->data;

Hello, 

I can't be so much more verbose than abrt: the gnome session have been saved and at session login, claws-mail was intended to startup. 

I can't reproduce so far with my current config. Unpredictable crash until ... claws-mail will maybe crash or not again, who knows ?   

Try to save your gnome session (with gnome-session-properties) with claws-mail started and login/logout with the calendar plugin. It only happen once to me so it's still not a test case to will reach a way to reproduce to crash. 

Cheers.

Thanks!


> I can't be so much more verbose than abrt

That's a common fallacy to assume that the backtrace is sufficient in all cases. There are plenty of cases, where the additional context added by a bug reporter may make a difference. For example, while some backtraces tell why and where the program crashed, they don't always tell what made the program arrive at such a fatal state.

So, it's not reproducible for you either.


> Try to save your gnome session (with gnome-session-properties)
> with claws-mail started and login/logout with the calendar plugin.

For my limited interest in Claws Mail bug triaging/monitoring, endless playing with the vcalendar plugin would be beyond my time. It could be that without a similar setup (perhaps with corrupted XML files or with webcal errors), I wouldn't have a chance to reproduce the issue. Maybe special steps are required, such as terminating Claws Mail while editing the calendar.

As far as I see, the vcalendar plugin does not feature any special support for desktop sessions. So, if it's enabled in Claws Mail, for a resumed session it would simply load as if Claws Mail were started normally. But it would not resume an open "New meeting" window, for example.

I've looked at the config files, AFAIK, they do not look like corrupted. 

I can't find a good repro case to "bug" upstream but I've a limited bandwidth to investigated on claws mail.

Thks.

Is it reproducible with Claws Mail 3.8.1 in updates-testing?
https://admin.fedoraproject.org/updates/FEDORA-2012-10349

I can't reproduce reliably with either version of Claws Mails.

That's a vague answer, unfortunately.

So, the problem still exists in Claws Mail 3.8.1, too?

Sure since the session handling code have not changed. But I can't reproduce reliably (the version do not matter).

I've forwarded this ticket at:
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2707

Many thks Michael.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.