Download it now!
Bug 76603 - LO crashes when paste Macro-content from a Windows server to LibreOffice Basic IDE on a Remote-Windows-desktop
Summary: LO crashes when paste Macro-content from a Windows server to LibreOffice Basi...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: BASIC (show other bugs)
(earliest affected) release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2014-03-25 18:40 UTC by Diego Ariel
Modified: 2015-09-04 03:01 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:

A sample video with images of how the problem plays. (2.73 MB, application/gzip)
2014-03-25 18:40 UTC, Diego Ariel

Note You need to log in before you can comment on or make changes to this bug.
Description Diego Ariel 2014-03-25 18:40:42 UTC
Created attachment 96378 [details]
A sample video with images of how the problem plays.

Problem description: 
I'm currently migrating an application from Microsoft Access to Libreoffice Base. The application I'm migrating is located on a remote machine and I connect to it via remote desktop.
The remote machine has a Windows 2003 Server operating system that has Microsoft Access installed. The local machine where the application I'm migrating Windows XP installed Libreoffice Base. I use Remote Desktop from my local machine to connect to Windows Server.
The problem is reproduced in Windows XP and Windows 7. I have not tried other Windows systems. In GNU/Linux distribution Ubuntu 12.04 LST (64 bits) this error does not play as remmina using Remote Desktop.

Steps to reproduce:
I copy code from Microsoft Access to the local Remote Desktop window Libreoffice Basic (Base) shows an empty message and closes completely.

Current behavior:
Displays an empty message and closes.

Expected behavior:

Allowing paste and save the code of Microsoft Access (VBA) in LibreOffice Basic (Base) using Windows Remote Desktop.

Operating System: Windows XP
Version: release
Comment 1 Florian Reisinger 2014-09-04 13:44:10 UTC
Your setup is  too complex to reproduce it ourselfs.
Either you pay for professional support (e.g. ) or you could help debugging or maybe Lionel has an idea. BTW: VBA is not perfectly supported by LibreOffice.
@Lionel: What do you think?
Comment 2 Lionel Elie Mamane 2014-09-04 15:26:37 UTC
This looks rather unrelated to VBA, and unrelated to Database as such. I understand/guess Diego is just pasting text (which happens to be basic code) into the Basic IDE. The crash may be unrelated the Remote Desktop thing. We need to find the thing, among all the setup, that is essential to the crash.


1) Does it crash if you paste exactly the same text, but from:
   1.1) a *local* notepad
   1.2) a *remote* notepage

2) Does it crash if you paste exactly the same text in exactly the same way,
   into the Basic IDE for a Calc document instead of a Base document?

3) Does it crash if you copy/paste a *different* text in exactly the same way,
   say just a short string like "foo"?

4) Does it crash if you copy/paste the same text in the same way,
   but from an Access on the same machine to a LibreOffice on the same machine?

It would be nice to have a backtrace indeed... the crash may be in the syntax highligting code or something like that.
Comment 3 Diego Ariel 2014-09-15 11:16:33 UTC
Correct. What I do is paste a text from VBA using remote desktop to Basic Base.
   1.1: If the remote text stick it to a local book, and the basic book of libreoffice does not appear error.
   2.1: If I get the text from a remote notepad, the error does not appear.

2. If I paste the text from the remote computer vba to a VB Calc or Writer, the same error appears.

3. If you copy a text, for example a comment from the remote computer VBA to VBA Libreoffice, the same error appears. Rem from the remote using vba and paste in vb libreoffice, same error. From a remote notepad, the error does not appear.

4. If copy and paste the text to a local vba libreoffice same remote computer, the error does not appear.

How I can get a backtrace on Windows? Help there somewhere?
Comment 4 Buovjaga 2014-10-24 13:58:44 UTC
(In reply to Diego Ariel from comment #3)
> How I can get a backtrace on Windows? Help there somewhere?
Comment 5 Robinson Tryon (qubit) 2014-12-29 06:26:14 UTC
(In reply to Beluga from comment #4)
> (In reply to Diego Ariel from comment #3)
> > How I can get a backtrace on Windows? Help there somewhere?

Waiting on a backtrace: Status -> NEEDINFO
Comment 6 Alex Thurgood 2015-01-03 17:40:39 UTC
Adding self to CC if not already on
Comment 7 QA Administrators 2015-07-18 17:36:38 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:

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-07-18
Comment 8 QA Administrators 2015-09-04 03:01:52 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 FDO
Message generated on: 2015-09-03