Impress won't save changes in master slide

Hi all,

When trying to fix the problem with the disappearing footers (see previous
message) I noticed something strange.

I edited the slide master (resized the auto-layout areas for the title and
outline) and saved the file. When re-opening that file both areas are back to
their old sizes and auto-fit modes again. It seems the changes were not saved.

Has anyone noticed this behavior before? Did you find a workaround?

I tried to find out if this was a known bug, but did not find it in the buglist.
If it is new, then I'll report it.

Grx HdV

Ah, I found a bug report matching this problem. Seems this is known for years,
but it hasn't been fixed (yet). Too bad. (#641175)

What If I would be willing to sponsor resolving this bug? What would be the
best way to find a developer that could fix this? We use LO a lot in my company,
so I wouldn't mind to invest in something that would help ourselves and all
other users of LO. If anyone knows someone who would be able and willing to fix
this bug, then please let him/her contact me.

Grx HdV

HdV wrote:

Hi all,

When trying to fix the problem with the disappearing footers (see previous
message) I noticed something strange.

I edited the slide master (resized the auto-layout areas for the title and
outline) and saved the file. When re-opening that file both areas are back
to their old sizes and auto-fit modes again. It seems the changes were not
saved.

Has anyone noticed this behavior before? Did you find a workaround?

I tried to find out if this was a known bug, but did not find it in the
buglist. If it is new, then I'll report it.

Grx HdV

Ah, I found a bug report matching this problem. Seems this is known for years,
but it hasn't been fixed (yet). Too bad. (#641175)

That number doesn't seem to exist in LibreOffice's bug tracker:
   https://bugs.freedesktop.org/show_bug.cgi?id=641175
But it does appear in the Ubuntu Linux bug tracker and looks related:
   https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/641175

The equivalent in LibreOffice bug tracker appears to be #34987:
   https://bugs.freedesktop.org/show_bug.cgi?id=34987
Although marked as having been fixed in version 3.3.1, it does look like it recurred, but is fixed again in newer versions - maybe 4.0.6 in the 4.0 series and 4.1.3 in the 4.1 series (not certain I've interpreted the comments correctly). So may be worth updating to 4.0.6 or 4.1.3 if you're not already using one of those versions.

Hi :slight_smile:
Wrt sponsoring devs to work on key issues affecting your company

Many companies employ devs to work directly on LibreOffice. Famously
openSuSE and Redhat but also many others such as Canonical also
various governments and companies that are not primarily
computer-related. Smaller companies can do so on a smaller scale,
perhaps just 1 and only part-time. Also very possible to have maybe 2
part-time devs working on a variety of projects (incl the company
website's under-laying structure (marketing deals with the surface
images and content right?)) but being given specific tasks and
priorities as and when a need arises.

There are crowd sponsoring sites for specific "one off" issues but i
can't remember any and anyway it looks like this issue is already
solved by just upgrading to a newer release in (hopefully) the same
branch. Moving to another branch sometimes means surprises and not
always good, usually but not always. Staying in the same branch (such
as 4.0.4 to 4.0.6 - or 4.1.0 to 4.1.5) is roughly the equivalent of
just adding a new "Service Pack".

Regards from
Tom :slight_smile:

Hi Tom,

Wrt sponsoring devs to work on key issues affecting your company

Many companies employ devs to work directly on LibreOffice. Famously
openSuSE and Redhat but also many others such as Canonical also
various governments and companies that are not primarily
computer-related. Smaller companies can do so on a smaller scale,
perhaps just 1 and only part-time. Also very possible to have maybe 2
part-time devs working on a variety of projects (incl the company
website's under-laying structure (marketing deals with the surface
images and content right?)) but being given specific tasks and
priorities as and when a need arises.

There are crowd sponsoring sites for specific "one off" issues but i
can't remember any and anyway it looks like this issue is already
solved by just upgrading to a newer release in (hopefully) the same
branch. Moving to another branch sometimes means surprises and not
always good, usually but not always. Staying in the same branch (such
as 4.0.4 to 4.0.6 - or 4.1.0 to 4.1.5) is roughly the equivalent of
just adding a new "Service Pack".

Thanks for your answer. I am going to install the latest version to verify
this, but I've read somewhere that the problem still persists even in the most
recent version. Not sure yet if it does for me. I'll find out. I think I'll try
to find a "crowd sponsoring" site if the issue isn't solved.

Grx HdV