Bug 70728 - Libreoffice impress craches loading odp file
Summary: Libreoffice impress craches loading odp file
Status: RESOLVED DUPLICATE of bug 68839
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.1.2.3 release
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-21 15:58 UTC by Gaetano
Modified: 2013-10-22 12:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
odp file not working in libo 4.1.2.3 (1.42 MB, application/vnd.oasis.opendocument.presentation)
2013-10-21 15:58 UTC, Gaetano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gaetano 2013-10-21 15:58:10 UTC
Created attachment 87933 [details]
odp file not working in libo 4.1.2.3

Libreoffice 4.1.2.3 - OS Linux Mint 13 maya.

today  libreoffice crashes whithout any message trying to open a .odp file.
The same file worked fine yesterday.
I deleted the .config/libreoffice folder in my home but without success.

To recovery the file I had to open it with a previous version of libreoffice 4.0.3.3, save it and then it worked.
Comment 1 Jorendc 2013-10-21 18:38:46 UTC
I fail to reproduce this, tested using Mac OSX 10.8.5 with LibreOffice Version: 4.1.3.1 Build ID: b42498da0e3f91b17e51b55c8295ec4f8f22087

Please retest when 4.1.3 will be published, or download (http://dev-builds.libreoffice.org/pre-releases/deb/) and install (http://www.libreoffice.org/get-help/installation/linux/) the first RC version.

Kind regards,
Joren
Comment 2 Terrence Enger 2013-10-21 19:09:12 UTC
With my debug build of master commit 95e95e0 (fetched 2013-09-19),
built and running on Linux, the file opens just fine.  Messages in
terminal (beyond those I get all the time):

    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <metadata> (!)
    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <rdf:RDF> (!)
    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <cc:Work> (!)
    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <dc:format> (!)
    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <dc:type> (!)
    warn:legacy.osl:4499:1:svgio/source/svgreader/svgtools.cxx:40: Unknown Base SvgToken <dc:title> (!)
Comment 3 Jorendc 2013-10-21 19:13:52 UTC
@Terrence: The bug reporter mentions clearly in his description he can reproduce this bug with LibreOffice 4.1.2.3, so please do not change the bug version, unless you can confirm this behavior with an older version.

Thanks for your understandings
Joren
Comment 4 Terrence Enger 2013-10-21 23:02:01 UTC
@Jorendc:

My change to the version was an accident.  I think you entered the
verision after the time I loaded the bugzilla page and before I added
myself to the cc.  But I am quite sure that I did not see the
midair-collision warning that bugzilla sometimes presents for
conflicting updates.  So, I am left uncertain of just how I did it.

Sorry.
Comment 5 Gaetano 2013-10-22 07:29:45 UTC
tested with version 4.1.3.1 it works fine. thank you.

kind regards
Gaetano


(In reply to comment #1)
> I fail to reproduce this, tested using Mac OSX 10.8.5 with LibreOffice
> Version: 4.1.3.1 Build ID: b42498da0e3f91b17e51b55c8295ec4f8f22087
> 
> Please retest when 4.1.3 will be published, or download
> (http://dev-builds.libreoffice.org/pre-releases/deb/) and install
> (http://www.libreoffice.org/get-help/installation/linux/) the first RC
> version.
> 
> Kind regards,
> Joren
Comment 6 Jorendc 2013-10-22 10:18:46 UTC
(In reply to comment #4)
> @Jorendc:
> 
> My change to the version was an accident.  I think you entered the
> verision after the time I loaded the bugzilla page and before I added
> myself to the cc.  But I am quite sure that I did not see the
> midair-collision warning that bugzilla sometimes presents for
> conflicting updates.  So, I am left uncertain of just how I did it.
> 
> Sorry.

No problem :), just mentioning it :-).

(In reply to comment #5)
> tested with version 4.1.3.1 it works fine. thank you.

Good to hear it works again!
Because we couldn't reproduce and we don't know which patch fixed the issue, lets mark it as RESOLVED WORKFSORME (a more proper status for this bug).

Kind regards,
Joren
Comment 7 Maxim Monastirsky 2013-10-22 12:09:31 UTC
According to the backtrace, looks like a duplicate of Bug 68839.

*** This bug has been marked as a duplicate of bug 68839 ***