Bug 77448 - DATALOSS: single character subscript/superscript disappearance with corrupted registrymodifications.xcu
Summary: DATALOSS: single character subscript/superscript disappearance with corrupted...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2014-04-14 18:50 UTC by bruno.binet
Modified: 2018-09-22 02:30 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

simple odt file containing a single word (before any formating) (8.53 KB, application/vnd.oasis.opendocument.text)
2014-05-04 18:44 UTC, bruno.binet
the same document with letter "o" subscripted (8.54 KB, application/vnd.oasis.opendocument.text)
2014-05-04 18:48 UTC, bruno.binet
normal findings under Win7x64 (8.89 KB, application/vnd.oasis.opendocument.text)
2014-05-04 19:18 UTC, tommy27
the bad file (in the profile) (293.54 KB, text/xml)
2014-05-05 11:37 UTC, bruno.binet

Note You need to log in before you can comment on or make changes to this bug.
Description bruno.binet 2014-04-14 18:50:33 UTC
I think this is a recent regression. At least, LO was ok. Steps to reproduce:

1) Select a single character in a Word
2) Format/Character/Position/Subscript or Superscript
3) See the character disapears (in fact, replaced by a very small space).

Workaround: with CTRL-SHIFT-B, I get the normal behaviour (subscript).

No such problem in Calc.
Comment 1 tommy27 2014-05-04 00:25:05 UTC
I do not reproduce issue under Win7x64 using LibO

please define exactly your O/S and provide a test file.
Comment 2 bruno.binet 2014-05-04 18:44:59 UTC
Created attachment 98427 [details]
simple odt file containing a single word (before any formating)
Comment 3 bruno.binet 2014-05-04 18:48:06 UTC
Created attachment 98428 [details]
the same document with letter "o" subscripted

The letter "o" is not visible, but you can select the small space (between "w" and "r") and return the the "normal" character position to see that a "o" is really there.
Comment 4 bruno.binet 2014-05-04 18:53:26 UTC
I'm on Linux Mint 13 Cinnamon 64 bit. See the attachments.
Comment 5 tommy27 2014-05-04 19:18:03 UTC
Created attachment 98429 [details]
normal findings under Win7x64

your test file are abnormal indeed...
but I cannot reproduce the issue from scratch under Win7x64
see attached file

probably that's a Linux specific issue that has to be confirmed by another Linux user. In the meantime try resetting the user profile and see if it change things.

Comment 6 bruno.binet 2014-05-04 19:25:37 UTC
The attachment created under Win7 is displayed correctly on Linux (superscript O).
Comment 7 bruno.binet 2014-05-04 19:39:54 UTC
I deleted my profile (~/.config/libreoffice) and now it works normally! Thank you for this hint.

I still have a copy of my defective profile but I don't know which file I should upload (to help someone to confirm). 

I don't mark the bug as resolved, since it can happen with a given profile.

At least, deleting the profile is a workaround.
Comment 8 tommy27 2014-05-05 09:06:19 UTC
try copying a single folder one-by-one of the corrupted profile into the working one and retest soon after.

this would allow you to idenfity where the corrupted file is.
then once you identify the "bad folder" do the same thing with any singular file of it.

once you find who's guilty upload it here but I cannot assure we can find a solution. sometimes user profile corruption are unpredictable and unfixable

I set status to NEEDINFO, revert it to UNCONFIRMED once you identify the corrupted file
Comment 9 bruno.binet 2014-05-05 11:37:17 UTC
Created attachment 98472 [details]
the bad file (in the profile)

put this in ~/.config/libreoffice/4/user
Comment 10 tommy27 2014-05-05 17:02:33 UTC
good catch bruno!!!
I can reproduce your same bug using that corrupted registrymodifications.xcu file in my user profile under Win7x64

I add Writer expert to CC-list to hear if this may be useful to disclose the root of the bug and maybe prevent further episodes.

@Michael, would you please take a look at it?
Comment 11 QA Administrators 2016-02-21 08:37:27 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2017-03-06 15:50:07 UTC Comment hidden (obsolete)
Comment 13 Thomas Lendo 2018-09-22 02:30:35 UTC
Closing this bug as INVALID because the only chance to ever fix it is to find the reason why xcu corrupted. Only having the file won't help.