Bug 57265 - CRASH - set Thunderbird as mail client
Summary: CRASH - set Thunderbird as mail client
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha0+ Master
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-19 08:22 UTC by Alex Thurgood
Modified: 2012-12-07 08:32 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
back trace of crash on Linux 32bit (5.34 KB, text/plain)
2012-11-19 08:22 UTC, Alex Thurgood
Details
disassembly trace in gdb (4.18 KB, text/plain)
2012-11-19 08:29 UTC, Alex Thurgood
Details
bt on master (14.71 KB, text/plain)
2012-11-19 21:58 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Thurgood 2012-11-19 08:22:04 UTC
Created attachment 70243 [details]
back trace of crash on Linux 32bit

Version 3.7.0.0.alpha0+ (Build ID: 27fafb7)
Linux 32bit

Trying to set Thunderbird as the default e-mail client causes LO to SIGSEV, backtrace included.

How to reproduce :

1) Start LO master build
2) Tools > Options > Internet > E-mail
3) Click on the file navigation button to navigate to the desired  email application, which opens the /usr/bin directory by default in the dialog.
4) Click on thunderbird.
5) Click on OK.
6) Crash

Alex
Comment 1 Alex Thurgood 2012-11-19 08:29:36 UTC
Created attachment 70244 [details]
disassembly trace in gdb
Comment 2 Alex Thurgood 2012-11-19 08:40:09 UTC
(In reply to comment #0)
> Created attachment 70243 [details]
> back trace of crash on Linux 32bit
> 
> Version 3.7.0.0.alpha0+ (Build ID: 27fafb7)
> Linux 32bit


Correction on steps to reproduce

> 5) Click on OK. Click on OK again.
Comment 3 Winfried Donkers 2012-11-19 14:01:05 UTC
Not successful in trying to reproduce crash;
openSUSE 12.2 32 bit
LibO 3.7.0.0.aplha0+ (build ID: 94c508)

Went through all steps and was able to open an new writer document without problem.
I tried both with an without thunderbird application active.
I will update my sources and try once more.
Comment 4 Alex Thurgood 2012-11-19 14:13:15 UTC
Hi Winfried,

Thanks. I'm currently doing a clean rebuild.

Alex
Comment 5 Winfried Donkers 2012-11-19 18:13:25 UTC
(In reply to comment #3)
> Not successful in trying to reproduce crash;
> openSUSE 12.2 32 bit
> LibO 3.7.0.0.aplha0+ (build ID: 94c508)
> 
> Went through all steps and was able to open an new writer document without
> problem.
> I tried both with an without thunderbird application active.
> I will update my sources and try once more.

Tried again with 4.0.0.0.alpha0+ build id 156898:
no crash, I could execute all steps and send a document with thunderbird.
Comment 6 Alex Thurgood 2012-11-19 18:34:27 UTC
Oh well, I'm still waiting for my clean build to finish. Must be something in my LO config or environment I guess, or something in the Mintbuntu distro I'm using to do the build.

Thanks for testing anyway.

Alex
Comment 7 Julien Nabet 2012-11-19 21:58:04 UTC
Created attachment 70284 [details]
bt on master

On pc Debian x86-64 with master sources updated today (make clean + brand new LO profile), I reproduce the problem.

1) I tried to select /usr/bin/icedove
LO takes a lot of time before displaying the content of /usr/bin then I clicked on icedove and click "Open" it crashed.

2) Since it took a long time, I copied, just for the test, icedove exe on a specific directory, no crash ! 

So perhaps, the problem is due to some memory leak.
Comment 8 Julien Nabet 2012-11-19 22:53:17 UTC
Caolán: one for you?
Comment 9 Caolán McNamara 2012-11-21 12:24:43 UTC
There are two different backtraces here. One is a crash in SfxItemSet::~SfxItemSet from the options dialog dtor. The other is deep down in glib from the SalGtkPicker::~SalGtkPicker gtk file dialog dtor.

I can't reproduce either of them (the gtk one might be a problem in gtk/glib itself) with or without toggling the gtk file picker on/off or under valgrind under those two alternatives
Comment 10 Julien Nabet 2012-11-30 23:35:27 UTC
With master sources updated today (commit ebb4150463ef97571d8f4ffc0b8189ff94d5cf1a), I gave it a new try.
I noticed that everything was ok with LO dialogs enabled.
When disabled, LO was quite long to open /usr/bin
The main point is, in both cases, I don't reproduce the crash anymore.

Alex: could you give a new try with the most recent version you'll find? (perhaps with LO dialogs enabled and disabled?)
Comment 11 Alex Thurgood 2012-12-07 08:32:48 UTC
Yep, works for me now.


Alex