Bug 101663 - Crash when trying to switch to "Tools - Options - LibreOfficeDev - Colors" on Debian
Summary: Crash when trying to switch to "Tools - Options - LibreOfficeDev - Colors" on...
Status: RESOLVED DUPLICATE of bug 101514
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.0.alpha0+
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-22 13:55 UTC by Thomas Hackert
Modified: 2016-08-22 15:18 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
bzip2'ed "soffice --strace" output (748.73 KB, application/x-bzip)
2016-08-22 13:58 UTC, Thomas Hackert
Details
"soffice --backtrace" output (18.89 KB, text/x-log)
2016-08-22 13:59 UTC, Thomas Hackert
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Hackert 2016-08-22 13:55:31 UTC
Hello @ll
while trying to configure LO to my likings I went to "Tools - Options - LibreOfficeDev - Colors", but LO immediately crashes ... :(

Steps to reproduce:
1. Start LO
2. Go to "Tools - Options"
3. Either use the arrow down key to get there or click on "Colors"

LO immediately crashes and the Document Recovery window will pop up ... :( I will attach a "--backtrace" and bzip'ed "--strace" log to this bug ... ;)
Sorry for the inconvenience
Thomas
Comment 1 Thomas Hackert 2016-08-22 13:58:11 UTC
Created attachment 126961 [details]
bzip2'ed "soffice --strace" output

bzip'ed strace output from "soffice --strace"
Comment 2 Thomas Hackert 2016-08-22 13:59:30 UTC
Created attachment 126962 [details]
"soffice --backtrace" output
Comment 3 V Stuart Foote 2016-08-22 14:04:31 UTC
*** Bug 101662 has been marked as a duplicate of this bug. ***
Comment 4 Julien Nabet 2016-08-22 15:18:30 UTC
It shows that it's a not only Windows pb but it also shows it may be related to lib merge.
Indeed, I don't reproduce this on pc Debian x86-64 with master sources updated some days ago.

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