Bug 82174

Summary: Other: Opening Template Manager / Saving Template Causes Crash
Product: LibreOffice Reporter: Joseph <joseph.m.beck>
Component: LibreofficeAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: serval2412
Version: 4.2.6.2 releaseKeywords: have-backtrace
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
i915 platform: i915 features:
Attachments: Backtrace File (Template Crashing)
The real trace log, I hope
Icon Issue

Description Joseph 2014-08-05 05:10:10 UTC
Problem description: 
Whenever I try to manage templates or save a new one it crashes LibreOffice entirely. Happens in Writer, Calc, and Impress. I assume it effects all programs. Not sure if this is fixed in 4.3. I downloaded it today from PPA but 4.3 hasn't been added yet.

Steps to reproduce:
1. Click File, Mouse Over Templates
2. Click Manage or Save Template
3. LibreOffice Crashes

Current behavior:
Crashing

Expected behavior:
Not Crashing
              
Operating System: Linux (Other)
Version: 4.2.6.2 rc
Comment 1 ign_christian 2014-08-05 15:03:55 UTC
Not reproducible in LO 4.2.6.2 (from PPA) - Ubuntu 12.04 x86

Please try resetting user profile: https://wiki.documentfoundation.org/UserProfile
Then mark RESOLVED WORKSFORME if that resolved.
Comment 2 Joseph 2014-08-05 15:17:46 UTC
If it matters I am using LinuxMint 17 - Cinnamon Edition. I tried resetting the profile and it still results in a crash.
Comment 3 ign_christian 2014-08-05 15:26:40 UTC
Hi again Joseph.. It could be..

Would you mind to do debugging: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux

Or possibly it's because package from PPA, you could also try deb package from LO official site: http://www.libreoffice.org/download/libreoffice-still/
Comment 4 Julien Nabet 2014-08-05 19:23:02 UTC
On pc Debian x86-64 with master sources updated today, I don't have crash but it takes about 15 secs to show templates when clicking "Manage template" (i5, 6GB)
Comment 5 Joseph 2014-08-05 19:38:58 UTC
Created attachment 104099 [details]
Backtrace File (Template Crashing)

Not sure if this is directly what you wanted but here the result of doing the BackTrace method described.
Comment 6 Joseph 2014-08-05 19:57:36 UTC
I thought my GUI looked on so I went ahead and did the following, since someone else had mentioned that their GUI looked odd in the past:

sudo apt-get install libreoffice-style-tango libreoffice-gtk libreoffice-gtk3 libreoffice-style-human

I can now manage templates and save templates without crashing.The icons on the Welcome window are now black which is not pleasant but I am working on fixing that.
Comment 7 Julien Nabet 2014-08-05 20:16:45 UTC
Joseph: to retrieve a backtrace you can follow this link:
https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace

Your gdbtrace doesn't contain a backtrace but commands on gdb.
Comment 8 Joseph 2014-08-06 00:18:40 UTC
Created attachment 104112 [details]
The real trace log, I hope
Comment 9 Joseph 2014-08-06 00:19:40 UTC
Created attachment 104113 [details]
Icon Issue

I have just replaced the logfile, I apparently was looking in the wrong location before after following the steps. I've also included a screenshot to demonstrate the black icon problem.
Comment 10 Julien Nabet 2014-08-09 05:49:30 UTC
Black icon problem is perhaps because you use HiContrast. You can test:
Menu/Tools/Options/View
Icon and size: choose something else than HiContrast (Tango for example).

This trace is ok.
I noticed this part:
#22 0xb5f5d1f1 in ?? () from /usr/lib/libreoffice/program/libmergedlo.so
#23 0xb5f5e03a in SfxDocumentTemplates::GetRegionCount() const () from /usr/lib/libreoffice/program/libmergedlo.so
#24 0xb5e50e16 in TemplateLocalView::Populate() () from /usr/lib/libreoffice/program/libmergedlo.so

I'm pretty sure having already seen a trace with GetRegionCount. Hope will find the other bug to put it in See also.

Anyway, I put it at NEW since there's a bt.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.