Apache OpenOffice (AOO) Bugzilla – Issue 95970
OpenOffice crash on closing queries in design view
Last modified: 2009-02-14 10:29:11 UTC
OpenOffice Database is consistently crashing whenever I close the Edit Query window in Design View. Steps to reproduce: - File->New Database... - select Create a new database; click Next >> - Click Finish - give the file a name - Tables->Use Wizard to create table - Load all columns from the default example table (Assets); click Finish\ - close the Table window - Queries->create query in design view - add the Assets table, double-click on some fields to add them to the query - save the query - close the query window. - at this point openoffice crashes, displaying the Document Recovery screen. this problem happens consistently, while editing any query. Switching out of Design View before closing the Query Editor will allow the query to be closed without any problems. The query can be edited in design view without problems, and as long as the editor is not in Design View, ie is in SQL edit mode, when the query editor is closed, there is no problem. I've developed a fairly complex database using this workaround. Opening an existing query with right-click->Edit, adding a field, and then closing the editor will consistently cause this crash. I'm running Ubuntu Hardy Heron (8.04) 64-bit. It's fully updated, which gives me the ooo package openoffice.org-core 1:2.4.1-1ubuntu2, Mon Jun 30 11:50:15 UTC 2008, as displayed in Help->About. the java package that openoffice is depending on is sun-java6-jre 6-07-3ubuntu2. When the crash occurs I'm getting an hs_err_pid*.log file output to my home directory. I've had this error occur with both the openjdk jre and the sun jre.
Created attachment 57770 [details] log file generated by crash on query design view closing
works fine for me on 32-bit hardy. Maybe this is a 64-bit issue? Do you have access to a 32-bit system to try and verify there? Can you try with a different user and see if the problem still occurs?
I tried this as a freshly-created user on the same machine and there was no crash. As the original user, I renamed ~/.openoffice.org2 and tried it again; the problem reoccurred. In case it's relevant: I'm also experiencing frequent crashes when debugging in the Basic Editor. These seem to be most likely to occur when clicking on the name of a variable in the watch window. Drilling down (clicking on the [+] ) works pretty reliably but clicking on the actual name of the variable seems to frequently lead to a crash. Base has crashed in other situations as well. I'm always using as the same user on the same machine. The crash described in my initial bug report is the only one that I can reliably reproduce. In addition to having happened consistently with the openjdk and sun JREs listed above, it was also occurring when i was using the sun 1.5.0.15 jre. My system is generally stable, apart from these problems with OOo Base. I haven't had stability problems with any of the other OOo components.
Alright, so this is a problem somehow related to the user. Alas, I don't have much of an idea of what you could try to pinpoint this further. You say that renaming the openoffice folder for your user does not help. That would point to some other software on your system, I'm guessing some extension or something you have enabled.
I cant't reproduce it neither with the 64 bit build of Pavel (2.4.1) nor with the 64 bit build of Sun (3.0.0) So I assume that this is a problem of the Ubuntu build. Please fill an issue against bugs.ubuntu.com so I add ccheney to Cc
I don't think this is a Ubuntu-specific problem, I am on Ubuntu as well. We kind of already established this to be a problem with the particular user account that intuited is using.
I can't also reproduce it with 2.4.1-12 from Debian Lenny so it's works for me
It's kind of sad to see this little understood issue (see comment Fri Nov 14 08:51:15 +0000 2008) closed in haste. Why the rush? And btw, I was told, an app should never crash, no matter how borked a user's home dir might be. But we didn't even yet establish this to be the case. intuited, I'm sorry, I cannot reopen this ticket for you. I think the premature closure reflects poorly on OOo. I'd reopen it if I still had the powers to do so, but that expired some time ago.
this is not a place for support If intuited need help to find the problem on her/his system it is better to use the open mailing list users@dba.openoffice.org so long nobody can reproduce the crash, it is not possible to fix anything -> closed
I am still baffled by how you know this is a support request and where you derive your confidence from that there is not a valid issue underneath? The app crashed! If OOo did not have a problem, it wouldn't have. Period.
Indeed. Hopefully a low-priority one affecting a small number of users, but certainly a bug. This based on the fact that there was a crash of three different java vm's when performing the same operation. Whether that's due to inappropriate coding in OOo, or appropriate coding in OOo that's at the mercy of inappropriate coding in something that's it's interacting with in my system is unknown at this point. However the chances that it's something that could be fixed by changing the OOo code are high, and the chances that _should_, because the fault lies in OOo, are high enough to be worthy of consideration. At a minimum we ought to be able to inform people of other packages/configurations that OOo is incompatible with. That's my opinion at any rate. As I mentioned my system is otherwise stable; no other applications have left hs_err_pid*.log files due to java crashes. If anyone has any suggestions as to how to pinpoint what's causing this, please let me know. At this point it's certainly not a support request, since I've moved over to developing my database app in a windows vm -- that's what it will be run under, so given potential instability and compatibility issues it makes the most sense to develop it there. It's also not true that nobody can reproduce the problem; i can do so quite readily. I'm interested in helping with QA on this issue, please let me know what I can do.
You can look at the Build number under "Help -> Info about OpenOffice.org" and then hold the CTRL-Key and press SDT. Then you get the build number. something like 93xx. Can you please post your whole number?
the build number is 9310.
Please report this bug to https://launchpad.net/ubuntu/+bugs This is an ubuntu only bug. This can't be fix in the upstream because there isn't this bug. A suggestion for a solution is to install the upstream version from http://download.openoffice.org/other.html So this issue is invalid for the upstream
Very strange is all I can say! Mechtilde, are you actually reading and understanding what is being discussed here? I specifically said that ubuntu works fine for me. The OP said this was only occurring in one user's account on his machine and not another one. I think your crystal ball needs serious polishing - or even better, dump it. I prefer the analytical approach to bug triaging, because one actually has a chance to find and fix bugs that way. Intuited, maybe you can be bothered to try with the official binaries and the user's account where you see this problem? If indeed you don't see the problem then, we'd have confirmed what Mechtilde is only assuming for the sake of closing the maximum number of bugs (The real aim should be *fixing* the maximum number of bugs).
yes I read the issue reports. The problem here is that intuited has a problem with the ubuntu version on a 64-bit system. This problem isn't reproducable on another 64 bit system. So nobody can analyse and describe whats going wrong. There are two possibilities: 1. it is a bug only of the ubuntu version 2.4.1. Then it has to be reported to https://launchpad.net/ubuntu/+bugs 2. it is a problem of the reporter's system then it is a problem for the suopport and not for the issuezilla. Then the reporter should ask on users@dba.openoffice.org. And: There are several known bugs only in the Ubuntu version specially in the base modul.
Again, I'm quite willing to help with testing on this bug. Of course you'll have to take my word for it that I'm competent in this capacity. Is there a location where I can still download an upstream version of 2.4.1 in English for x86_64 Linux? Between the link you gave me and the peer-to-peer downloads I only have download options for 3.0 or 2.1 for this combination of language, architecture, and operating system. A third possibility is that this is a problem inherent in both the ubuntu and upstream versions of 2.4.1, possibly in addition to other versions, that only occurs when certain other system (profile) elements are present, or when they have a certain configuration or value. Again if you have any suggestions of profile-dependent elements that would be likely to cause such a problematic interaction I will change or disable them to see what effect this has on the bug. I can try the process-of-elimination method, but it will take a lot longer. So far I've determined that the error still occurs when Compiz is disabled. I understand where you're coming from but it seems premature to classify this as an ubuntu bug when it seems to be related to the way that OOo is interacting with some other installed app or with profile settings. Although this could be something that is Ubuntu-specific, we don't have any evidence that that is the case. If we can determine which element's presence or configuration is triggering the bug, we may be able to reproduce it on another system, and from there determine whether this is indeed a bug in the OOo code or in the other element's code. I will install 3.0.0 to test it with the problematic profile. Of course if the bug does not occur for me with that version, this will only indicate that the issue is not occurring in 3.0.0 mainstream, and not that it is something specific to the ubuntu version of 2.4.1. The fact that other bugs have been found in the ubuntu version has no bearing on this issue unless they seem likely to be related to whatever may be causing this problem.
there is no upstream version 2.4.1 for 64 bit systems only some distributions have such a version and I tested the Debian version of 2.4.1 for a 64 bit system which deoesn't show this problem.
As we've already established, the problem is specific to certain settings in my user profile. This is based on the fact that following the same steps when using OOo as a different user on the same system does not result in a crash or any other problem. So the fact that it doesn't occur when you are testing it does not mean that it is because you are not using the ubuntu version, it may just be that you don't have the profile element enabled, installed, or configured in a way that gives lead to this problem. Can you give me a link to download the Debian package for 2.4.1?
As I know it is impossible to install the Debian packages from the Debian repository under ubuntu. IMO you need a Debian/Lenny System. If there is something wrong in your own home directory then we can discuss it at users@dba.openoffice.org how to solve the problem. But this is not a bug in OpenOffice.org upstream
@ intuited can you test it with the latest Ubuntu build? If you have new informations about this you can reopen
.