Issue 46341 - unexpected error about 1.1.4 BASIC
Summary: unexpected error about 1.1.4 BASIC
Status: CLOSED DUPLICATE of issue 28593
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 680m87
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: joerg.skottke
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-03-31 01:29 UTC by nivag
Modified: 2005-04-15 09:29 UTC (History)
2 users (show)

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


Attachments
unexpected error dialogue (59.75 KB, image/png)
2005-03-31 01:30 UTC, nivag
no flags Details
paths actually set up (116.33 KB, image/png)
2005-03-31 01:31 UTC, nivag
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description nivag 2005-03-31 01:29:53 UTC
I created a new document and went to save it as a .odt file.

I got a couple of error dialogues complaining about BASIC relating to 1.1.4, yet
I am running OOo 1.9.87!!!  I will include screen shots of the first error
dialog and the paths used.

The new document gets saved OK, and loads without any error dialogues.

OOo 1.1.4 was the previous version loaded on this machine.

At no stage have I exlicitly used BASIC in OOo, nor was I aware of anything
requiring BASIC being loaded..
Comment 1 nivag 2005-03-31 01:30:50 UTC
Created attachment 24437 [details]
unexpected error dialogue
Comment 2 nivag 2005-03-31 01:31:31 UTC
Created attachment 24438 [details]
paths actually set up
Comment 3 michael.ruess 2005-03-31 07:09:18 UTC
Reassigned to JSK.
Comment 4 nivag 2005-04-01 00:58:18 UTC
I get the 1.1.4 BASIC error dialog when OOo decides to autosave on an existing
document.
Comment 5 flibby05 2005-04-01 16:46:00 UTC
hmm, when looking at your OOo paths everything looks fine,
what 1.1.4 and 2.0 however _could_ share is your temp directory: /home/gavin/tmp
(can you maybe recall that you set your 1.1.4 tmp-directory also to
/home/gavin/tmp?)

_Maybe_ 1.1.4 left some autosave files there and the 2.0 routines will
incorrectly pick them up again and consequently refer to paths from the old
installation.

Gavin, could you post an 'ls -al' output of /home/gavin/tmp?

Also did you use any other version between 1.1.4 and m87 on your system such as
f.e. the beta 2.0?
Comment 6 nivag 2005-04-03 23:34:49 UTC
I don't think I set my 1.1.4 tmp-directory to /home/gavin/tmp, probably was /tmp
(I'm assuming OOo temp files start with "sv"):
$ cd /tmp
$ ls -al
total 156
[...]
drwx------   2 gavin    gavin     4096 Apr  4 08:55 ssh-SqV10748
drwxrwxr-x   2 gavin    gavin     4096 Mar 21 12:31 sv49f.tmp
drwxrwxr-x   2 gavin    gavin     4096 Mar 21 12:57 svgfg.tmp
-r--r--r--   1 root     root        11 Apr  1 09:24 .X0-lock
[...]


$ pwd
/home/gavin/tmp
$ ls -al
total 12
drwxrwxr-x   3 gavin gavin 4096 Apr  1 18:38 .
drwxr-xr-x  46 gavin gavin 4096 Apr  4 09:48 ..
drwxrwxr-x   2 gavin gavin 4096 Mar 24 14:14 sv34o.tmp
$ cd sv34o.tmp
$ ll
total 0
-rw-rw-r--  1 gavin gavin 0 Mar 24 14:14 sv353.tmp
-rw-rw-r--  1 gavin gavin 0 Mar 24 14:14 sv35f.tmp
-rw-rw-r--  1 gavin gavin 0 Mar 24 14:14 sv35g.tmp

versions since 1.1.4:
1.9.79  (beta 2.0)
1.9.84
1.9.87  (current version used)

I did not get the error with builds prior to 1.9.87.

On autosave, the error is only displayed up the first time autosave is invoked.
Comment 7 joerg.skottke 2005-04-05 10:11:49 UTC
The classic "Error loading BASIC of document". Setting dupe to the almost
historic issue #28593

*** This issue has been marked as a duplicate of 28593 ***
Comment 8 joerg.skottke 2005-04-15 09:29:27 UTC
close, tracking the older issue instead