Bug 90632 - calc no vincula
Summary: calc no vincula
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.3.6.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 90633 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-04-15 12:30 UTC by Rotabre
Modified: 2016-05-09 20:07 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Captura 1 (383.50 KB, image/jpeg)
2015-04-15 12:30 UTC, Rotabre
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rotabre 2015-04-15 12:30:02 UTC
Created attachment 114806 [details]
Captura 1

Desde la versión 4.3.6, tengo inconvenientes en algunos vínculos. Tengo una planilla que se vincula con otras 32 más.
Uno de los problemas es que al abrirla, muestra valores que no se corresponden con los que debiera. Luego de aceptar que actualice los valores, no todos son correctamente actualizados (por ejemplo: las fechas).
Para corregir esto, he comprobado de debo guardarla (grabarla); volverla a abrir y volver a actualizar. En este punto si queda correctamente actualizada.
Si luego de grabarla, la vuelvo a abrir, el ciclo de errores se reinicia (vuelve a ocurrir todo lo antes descripto).
Esto se repite desde la versión 4.3.6 hasta la 4.4.2 (última). Tal es así que estoy trabajando actualmente con la versión 4.2.8 en la cual no ocurre el inconveniente.
Las planillas (todas) están hechas con la extensión ".ods"
Adjunto tres capturas de pantalla para ser más gráfico con respecto a lo que intento describirles.
Comment 1 raal 2015-04-15 13:35:20 UTC
*** Bug 90633 has been marked as a duplicate of this bug. ***
Comment 2 Buovjaga 2015-04-17 19:15:54 UTC
Please create an example document that shows the problems you describe and attach the document here. You can make it as minimal as you can, as long as it preserves the problem.

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the document.
Comment 3 QA Administrators 2015-10-14 19:51:05 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team

This NEEDINFO message was generated on: 2015-10-14
Comment 4 QA Administrators 2016-05-09 20:07:53 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

This INVALID Message was generated on: 2016-05-09