To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=109028





------- Additional comments from [email protected] Wed Feb 10 23:39:28 
+0000 2010 -------
Computer: Acer Aspire 3810T-354G32n. OS: Linux. Distro: CentOS 5.4. Kernel:
2.6.18-164.10.1.el5.centos.plusPAE. OO 3.1.1 (downloaded yesterday) version
OOO310m19 Build 9420. Type of issue: software - extension. Program: Palooca,
downloaded on the day before yesterday.

Yesterday I added extension Palooca to my OO3.1. On opening Calc there appeared
a new menu "Palo". The cursor could open all menus except that one. At first
click it would not notice the event. At second click the OO crash notice window
("unexpected problem") appeared (reproduced always).

I then uninstalled and re-installed OO3.1. On first loading Calc, the Palo menu
was there again (seems OO loads the same extensions as before uninstallation!).
Problem reproduced always.

Next morning i.e. yesterday I uninstalled OO3.1 again and installed OO2.3.0 from
CentOS directory RPMs. I added Palooca (the same .oxt). The Palo menu is now
there as well and works OK on OO2.3.0. Then I downloaded the last OO3.1.1
version as found in the OO repository (see version above) and installed it. The
Palo menu was again there on OO3.1.1 last version available and, very much to
the contrary of what happens in OO2.3.0 (where it works), on OO3.1.1, as well as
under OO3.1, Palooca reproduces always the irregular and damaging behaviour
described above i.e. it crashes OO3.1.1 the same as it crashes OO3.1 and does
not work at all.

I hope that the above description is now clear for you. I will not willingly
re-install palocca on OO3.1/OO3.1.1.1 because every time I dare do that, I have
to re-install my Linux CentOS distribution before I can get rid of the buggy
Palo menu that only does one one thing, namely to crash OO3.1 and OO3.1.1.

I have no openoffice folder at /root and I have never said that, so I find your
proposal to erase it a bit confusing because there is no such folder there. If
the bug that happens in my computer was due to that, then it would perhaps not
be unreasonable to surmise that Palooca would not work with OO2.3.1 either,
which it does: very much to the contrary, it is only (if one can say 'only': the
versions affected are the most recent!) under OO3.1 and OO3.1.1 that Palocca 
fails. 

Thanks a lot for your patience and hope this bug is solved asap.
Fernando Mansito


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to