Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 167748 - pyuno python scripts are not found by OOo
pyuno python scripts are not found by OOo
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
Depends On:
  Show dependency treegraph
Reported: 2005-09-07 15:40 EDT by Bryan Cole
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-09 04:15:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screenshot of them (21.43 KB, image/png)
2005-09-08 04:33 EDT, Caolan McNamara
no flags Details

  None (edit)
Description Bryan Cole 2005-09-07 15:40:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Epiphany/1.6.5

Description of problem:
Although I have the pyuno scripting framework installed, no python scripts are found (in either ~/.openoffice.org2.0/User/Scripts/python or 

This includes the examples scripts shipped with the pyuno package. When you browse python scripts under Tools->Macros->Organise Macros->Python, no scripts are shown at all.

I guess this might be specific to the FC4 packaging (python scripts used to show up in earlier beta versions, pre FC4)

NB. Other scripts, like OOo-Basic, Beanshell etc. work fine.

Version-Release number of selected component (if applicable):
openoffice.org-1.9.125 (2beta2)

How reproducible:

Steps to Reproduce:
1. try to run a python script

Additional info:
Comment 1 Caolan McNamara 2005-09-08 04:33:25 EDT
Created attachment 118584 [details]
screenshot of them

do you have the openoffice-1.9.125-pyuno rpm installed ?
Comment 2 Bryan Cole 2005-09-09 04:15:50 EDT
Ooops... Python scripts work fine for other users on the same system (and other
systems). Guess this is a problem with my local user config. 

Appologies for any time wasted on this.

Note You need to log in before you can comment on or make changes to this bug.