Issue 26751 - Document format changes.
Summary: Document format changes.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 1.1
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: ulf.stroehler
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2004-03-19 20:39 UTC by mestech
Modified: 2005-07-25 14:40 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Document in the original format as it normally opens. (108.86 KB, image/jpeg)
2004-03-29 18:09 UTC, mestech
no flags Details
Document after when the problem occurs. Note font size change. (110.16 KB, image/jpeg)
2004-03-29 18:10 UTC, mestech
no flags Details
strace of oowriter when the fault occurs. (187.90 KB, application/x-gzip)
2004-04-08 17:49 UTC, mestech
no flags Details
strace of oowriter when the fault does not occur (147.18 KB, application/x-gzip)
2004-04-08 17:50 UTC, mestech
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description mestech 2004-03-19 20:39:32 UTC
Linux, Fedora core1 rpm installs.

I have come across this before but this time it is causing me a major headache.
 I have to fill in some templates and all the formats of the templates have
changed and thus I have to re-format all of them again before I can use them.  I
tried to open a document that I saved on this computer a couple of weeks ago and
I am in the same boat with the format changed and thus I cannot use that document.

XFree86 was updated between the time that the documents were used and today.  It
could be a font related issue and XFree86 but a document saved under the old
fonts have a different problem than the template that it was created with.
Comment 1 flibby05 2004-03-20 18:40:27 UTC
Hello mestech,
could you please attach a sample file for reproducing your issue?

To send attachments regarding issues, please attach the file directly to
the issue. Use the link "Create a new attachment" on the issue and then
select Binary file (application/octet-stream) where asked, "What kind of
file is this?" if your file's type does not show in the list.

Thank you,
Max Weber
Comment 2 mestech 2004-03-23 20:55:32 UTC
Further info.

I have found that the problem is intermittent.

Now that I have had some time to investigate with more detail, the problem could
be related to either gnome, gimp or XFree86 in conjunction with OOo.

To expand, today I was working and I decided to try to re-create the fault and
all worked well.  After a while the problem occured.  I ran top and found that
gnome-panel was running over 90%.  I closed off all applications and re-started
gnome-panel but that did not correct the problem.  Logged out of X and startx
again.  Problem gone.

I am trying to re-create the situation and problem again.  It isn't a file
problem as formatting changes on all documents opened in writer.

I have posted a bug report for fedora as well.
Comment 3 mestech 2004-03-26 16:09:47 UTC
Well it has occured every day this week and I have been trying to trace problem
in any way that I can.

What I have found is that it occurs on two different systems, both running
Fedora Core 1.

It is not related to another problem that I thought was causing it.  (gnome-panel).

I think it is related to either gnome or XFree86 but it could be communication
between them.  While running startx 2>xerror and tailing xerror, I keep coming
up with;

Window manager warning: Property _NET_WM_NAME on window 0x1e00020 contained
invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x1e00020 contained
invalid UTF-8

This occurs with any window or sub window that opens (file open).  I don't know
if the invalid UTF-8 is part of the problem or not.  It also occurs with any OOo
program such as Calc or Impress.

Now that I know if I close X-windows and startx again and the problem is gone. 
I can work around it so it isn't so critical, just annoying now.

I am trying to increase debugging on gnome and XFree86 but I have to read the
manuals on how to configure it first.  Man I wish I had taken more programming
classes.

As time permits, I am trying to trace this problem the best I can.
Comment 4 mestech 2004-03-29 18:07:31 UTC
It occured today again and I had done a screen capture of the before/after
effects.  As I now look at the pictures I notice that the font size is changeing
and thus is affecting the display and printing of the document.  I am attaching
the photos.
Comment 5 mestech 2004-03-29 18:09:39 UTC
Created attachment 14156 [details]
Document in the original format as it normally opens.
Comment 6 mestech 2004-03-29 18:10:35 UTC
Created attachment 14157 [details]
Document after when the problem occurs.  Note font size change.
Comment 7 mestech 2004-03-29 20:37:07 UTC
Boy, my mind was not on track when I posted the images.

The font does not change in size as I mentioned.  I just checked from a
reference point and the font is still the same on both documents.  Only the
display changes.  The font size depends on where the cursor was located.  Duh.

On examining the two pictures, I notice that the font spacing is different
between the two examples.  This causes row height changes.  As this occurs
throughout the form, there is a major headache.  This corrupted format will
print out as well so it isn't just in the display.
Comment 8 mestech 2004-04-08 17:49:44 UTC
Created attachment 14423 [details]
strace of oowriter when the fault occurs.
Comment 9 mestech 2004-04-08 17:50:37 UTC
Created attachment 14424 [details]
strace of oowriter when the fault does not occur
Comment 10 michael.ruess 2004-08-19 15:05:51 UTC
reassigned to mru.
Comment 11 michael.ruess 2004-10-14 09:53:12 UTC
MRU->US: this sounds like a font related issue on Linux.
Comment 12 mandreiana 2004-10-16 11:09:57 UTC
Reporter, could you please attach the document too?

When it happens, does un-checking of Tools -> Options -> Writer -> Compatibility
-> Use printer metrics for document formatting fix it?

Thanks.
Comment 13 thackert 2004-12-12 11:33:46 UTC
I have seen that the last entry was in October and that this issue is OOo-1.1 related. Have you tried this 
with a newer version of OOo (1.1.x or 1.9.xx)? Does this problem occur there also or could this issue 
be closed?
Comment 14 ulf.stroehler 2004-12-13 11:35:05 UTC
@reporter: as earlier requested by "mandreiana", could you pls. attach the
document in question.
Comment 15 thackert 2005-01-16 15:39:36 UTC
I have not seen any comment from the reporter since December 13th ... :( Does
this mean that someone can close this issue as invalid or such?
Comment 16 haxwell 2005-02-09 23:25:00 UTC
The reporter hasn't responded on this issue since Oct 2004. Per the comments it
is not reproducible. If more info becomes available the issue can be reopened.
Also please check to see that 1.1.4 or a recent development snapshot do not
address this issue. Thanks..

Resolving Invalid.
Comment 17 eric.savary 2005-07-25 14:40:55 UTC
Closed