Created attachment 95626 [details]
zip archive containing various files demonstrating bug

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.0.5 or later)
   https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
 If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 
3. Leave a comment with your results. 

4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03

(In reply to Andrew from comment #10)
> The problem I identified in Bug 100999, which was redirected to be a
> duplicate of this bug (whether it is or not I don't know), still exists.
> 
> That is:
> 
> 1. save links in .ods file, works fine
> 2. save links in .xls file, works fine
> 3. save links in .xlsx file, fails
> 
> LibreOffice 5.1.5.2
> Windows 10

..and is there a reason you did not test with 5.2.2 like Bartosz?

When I clicked on "Help / Check for Updates" it told me I was up to date.  Is that another bug?

Is there a reason to expect it has been fixed in between? When I do update, I will check again.

(In reply to Andrew from comment #12)
> When I clicked on "Help / Check for Updates" it told me I was up to date. 
> Is that another bug?
> 
> Is there a reason to expect it has been fixed in between? When I do update,
> I will check again.

You can just download it: http://www.libreoffice.org/download/libreoffice-fresh/

The reason we suspect that is that Bartosz reported it fixed in 5.2.2.

I have now tried running it with 5.2.2.2  I still get the same problem.

We now also have Macs in our company and i noticed the same behaviour on latest MacOSX versions.

Will someone have a look at this (how many years old?) bug finally???

(In reply to egc from comment #31)
> Will someone have a look at this (how many years old?) bug finally???
No matter how many ?????? you put, it can only be fixed if you do it yourself, find someone to do it or wait for a volunteer to do it. 
Do not annoy people who have the same problem and follow this and who maybe contribute to the project somehow -even if spending time to fix your wrong report marking as a duplicate, because you hadn't search before submitting.

(In reply to Timur from comment #32)

i mean ... are you nuts?

(In reply to egc from comment #33)
> (In reply to Timur from comment #32)
> 
> i mean ... are you nuts?

No Timur is completely right.
Why do you think people just obey to what you command?
Now, nobody forces you to use LO, if this bug is blocking for you and your company, you can also switch to another Office suite.

(In reply to Julien Nabet from comment #34)
> (In reply to egc from comment #33)
> > (In reply to Timur from comment #32)
> > 
> > i mean ... are you nuts?
> 
> No Timur is completely right.
> Why do you think people just obey to what you command?
> Now, nobody forces you to use LO, if this bug is blocking for you and your
> company, you can also switch to another Office suite.

don't worry, we will, if that's the purpose of Libreoffice ...

(In reply to egc from comment #35)
> (In reply to Julien Nabet from comment #34)
> > (In reply to egc from comment #33)
> > > (In reply to Timur from comment #32)
> > > 
> > > i mean ... are you nuts?
> > 
> > No Timur is completely right.
> > Why do you think people just obey to what you command?
> > Now, nobody forces you to use LO, if this bug is blocking for you and your
> > company, you can also switch to another Office suite.
> 
> don't worry, we will, if that's the purpose of Libreoffice ...

One of the purposes is to be sustainable. Timur explained some of the ways this is achieved (completely standard free & open source development model). Of course the result would be "nuts", if everyone would just leech without contributing. If you don't have time/money to contribute, then you just have to wait.

(In reply to egc from comment #35)
> ...
> don't worry, we will, if that's the purpose of Libreoffice ...

To stay in the ironical tone, "yes it is indeed!".

Considering https://en.wikipedia.org/wiki/Comparison_of_office_suites#Main_components, there's some choice!

(In reply to Buovjaga from comment #36)
> (In reply to egc from comment #35)
> > (In reply to Julien Nabet from comment #34)
> > > (In reply to egc from comment #33)
> > > > (In reply to Timur from comment #32)
> > > > 
> > > > i mean ... are you nuts?
> > > 
> > > No Timur is completely right.
> > > Why do you think people just obey to what you command?
> > > Now, nobody forces you to use LO, if this bug is blocking for you and your
> > > company, you can also switch to another Office suite.
> > 
> > don't worry, we will, if that's the purpose of Libreoffice ...
> [...]
> If you don't have time/money to contribute, then you just have
> to wait.

We were waiting enough now. This bug is 6 years old, since the first version of 6.x ... I tried to keep Libreoffice in the company, but i can not do it for ever ...

(In reply to Julien Nabet from comment #37)
> (In reply to egc from comment #35)
> > ...
> > don't worry, we will, if that's the purpose of Libreoffice ...
> 
> To stay in the ironical tone, "yes it is indeed!".
> 
> Considering
> https://en.wikipedia.org/wiki/Comparison_of_office_suites#Main_components,
> there's some choice!

Glad you're having fun ... As i'm not a programmer my only choice is it now to convert all the calc documents to the other office package already in use in the company.

But thanks anyway for the enlightening link, it helped us a lot!

(In reply to egc from comment #39)
> ....
> 
> Glad you're having fun ... As i'm not a programmer my only choice is it now
> to convert all the calc documents to the other office package already in use
> in the company.
Please read what several people indicated, you can:
- wait
- fix it yourself
OR
- pay someone to do it.

For the rest, you can't convince your company to stick on LO just because you like it. You/your company must consider ads/cons.
ads:
- it's free
- you can fix the bugs or pay someone to fix the bugs since it's open source
- multi envs (but I suppose most companies don't care since they use Windows and when they use Linux, it's rather for servers where Office suites are not so used, except for batch treatments for some cases)
- some relevant features for you/your company may be present in LO exclusively

cons:
- less mature than other Office suites (like Ms) (at least from my opinion)
- more difficult to have support
- depending what module you use, you may undergo lots of bugs (eg: use of Firebird in Base is a real pb for the moment)
- some relevant features for you/your company may be lacking in LO

So if you and your company:
- don't want/can't pay for bug fixes
- can't fix bug yourselves
- can't wait anymore (I agree 6 years is too long)
=> you should consider migrating.
Now, I suppose you and your company already know that migrating has also a cost:
- license (except if you choose a free Office suite)/support
- time consuming for IT people who'll do the migration and have to deal with potential incompatibilities
- user training (even if the interfaces are quite similar, there are always differences)

So perhaps it may be relevant to compare cost migration and cost to pay someone to fix this bug and other bugs which are blocking for you.

(In reply to Julien Nabet from comment #40)

As i already wrote, an other office package (MS) is already in use by some people in the company and at home, so the company for sure is not willing to pay for bug fixes in LO. 
I was hoping i could keep both office packages, but with such blocking bugs like this one, and for so long time, my arguments for keeping LO in the company are go to 0.

As i said i'm not a software developer so i can not really tell, but i could imagine, that this bug is not such a big deal to be fixed by one of the programmers of LO. LO just duplicates the external links, so someone would just need to have a look at it why this happens, fix that, and that's it. I guess it could be done in 15 minutes for someone who knows the code.

But i don't see any will of the LO developers to fix this bug ... People continue reporting the same thing since 6 years and nobody in LO seems to find it worth to deal with it. This is not just a minor bug, it is a deal breaker for a mixed environment with two office packages and more operating systems in use.
That's why i don't understand why none of the programmers is trying to fix this bug. I repeat: It is a deal breaker. Not just a little formatting (or whatever) bug. 

So you're right, at the end it will be time consuming for me to convert all the calc sheets to Excel and make them work there. This way my effort goes actually into MS Office instead of LO ... which is absurd in my eyes ...

(In reply to egc from comment #41)
> (In reply to Julien Nabet from comment #40)
> 
> As i already wrote, an other office package (MS) is already in use by some
> people in the company and at home, so the company for sure is not willing to
> pay for bug fixes in LO.
I had missed this part so no need to stick on LO indeed except if you're a big supporter of OpenSource.

> I was hoping i could keep both office packages, but with such blocking bugs
> like this one, and for so long time, my arguments for keeping LO in the
> company are go to 0.
The goal of a company is to make money so no surprise here.

> 
> As i said i'm not a software developer so i can not really tell, but i could
> imagine, that this bug is not such a big deal to be fixed by one of the
> programmers of LO. LO just duplicates the external links, so someone would
> just need to have a look at it why this happens, fix that, and that's it. I
> guess it could be done in 15 minutes for someone who knows the code.
So you're not a software dev but "you could imagine it's not a big deal".
What about taking some hours to learn some C++ (after all there are Youtube videos to learn C++ in 1 or some hours) then give it a try, here's a link to start with:
https://wiki.documentfoundation.org/Development/GetInvolved
To install needed software and build the code hours, let's suppose some 3/4 hours.
I'm pretty sure that just with a good will, you may submit a fix on gerrit in some days.
There are also some people of your IT who may contribute. If they already know how to program (and perhaps how to program in C++) perhaps they may submit a bugfix in just 2 days?

> 
> But i don't see any will of the LO developers to fix this bug ... People
> continue reporting the same thing since 6 years and nobody in LO seems to
> find it worth to deal with it. This is not just a minor bug, it is a deal
> breaker for a mixed environment with two office packages and more operating
> systems in use.
> That's why i don't understand why none of the programmers is trying to fix
> this bug. I repeat: It is a deal breaker. Not just a little formatting (or
> whatever) bug. 
Consider this:
- take a look at the number of bugs declared in Bugzilla
- there are only about a dozen of expert devs which regularly contribute and in those, there are some who are quite driven by the company they belong (I mean they fix the bugs their company indicate wrt what clients paid)
=> it may give you some hints.

>
> So you're right, at the end it will be time consuming for me to convert all
> the calc sheets to Excel and make them work there. This way my effort goes
> actually into MS Office instead of LO ... which is absurd in my eyes ...
It's just your/company choice to not pay LO because they wrongly consider since it's freely downloadable, you shouldn't pay to fix the bugs.
So stop telling it's just devs fault and see there's also you/your company fault not willing to contribute in a way (money or programming).

(In reply to Julien Nabet from comment #42)

Yeah right, learning C++ in one or more hours ... for someone who has no idea about programming languages ...

Anyway, i realise that i'm in the wrong place here. i always thought a bugtracking system (as far as i know them) is a place where normal users can find and report bugs to the developers so they fix them (of course, if someone of the users is also able to contribute for the fix they can do that too, but that's not the case with me), but that doesn't seem to be so here. Here i only get advices to fix it myself or to let it fix by the company or to get a software developer and fix it ... or to change to another office suite ... Great!

Sorry for wasting your time. Have a good one!

(In reply to egc from comment #43)
> (In reply to Julien Nabet from comment #42)
> 
> Yeah right, learning C++ in one or more hours ... for someone who has no
> idea about programming languages ...
I supposed so. Still, you considered the bug is fixable in 15 min with no programming knowledge or LO code source knowledge... Hope you don't speak the same way with mechanics, plumber, etc. when you got car or house problems :-)

> 
> Anyway, i realise that i'm in the wrong place here. i always thought a
> bugtracking system (as far as i know them) is a place where normal users can
> find and report bugs to the developers so they fix them (of course, if
> someone of the users is also able to contribute for the fix they can do that
> too, but that's not the case with me)
> but that doesn't seem to be so here.
Take a look here https://cgit.freedesktop.org/libreoffice/core/log/ and you'll see that most commits which include "tdf#" is a fix (some may be just related like automatic test to avoid some regression on this part).
So yes the bugtracking system works well for quite some bugs.

> Here i only get advices to fix it myself or to let it fix by the company or
> to get a software developer and fix it ... or to change to another office
> suite ... Great!
In this case yes, nothing wrong here. 
The pb here is you expect the same support for LO which is released freely by TDF than you'd expect from Microsoft for MsOffice which you must pay for.

> 
> Sorry for wasting your time. Have a good one!
No pb here to discuss here. Have a good day too!

(In reply to Julien Nabet from comment #44)

> The pb here is you expect the same support for LO which is released freely
> by TDF than you'd expect from Microsoft for MsOffice which you must pay for.

I was talking about other open source bug tracking systems, not Microsoft or so, i don't even know those bug tracking systems. But it's ok ...

There's a very appealing solution to this, especially if you're using LibreOffice in a company environment, helping both you and the eco system around LibreOffice: buy support from one of the commercial entities and they'll happily fix the bug for you. See https://www.libreoffice.org/get-help/professional-support/

(In reply to Eike Rathke from comment #46)
> There's a very appealing solution to this, especially if you're using
> LibreOffice in a company environment, helping both you and the eco system
> around LibreOffice: buy support from one of the commercial entities and
> they'll happily fix the bug for you. See
> https://www.libreoffice.org/get-help/professional-support/

I know i know by now ... Everybody here repeats the same thing. I just wonder if you need all the fuzz of a bug tracking system for this ...

You could have simply said already 6 years ago: "We will not fix this bug, buy yourself a support to fix it." Instead of letting people wait for t years ...

By the way, after 6 years the status of this bug, which is classified as "major" important, is still on "new" and not assigned to anybody.

You could at least add a new handy status, something like "will be ignored" or "the very appealing solution for this bug is to buy yourself a support and/or fix it yourself" ... and close the bug. This way people at least know what they can expect from this bug tracking system ...

Bug is still there in version  LibreOfficeDev_7.1.0.0.alpha1_Linux_x86-64_rpm.tar.gz