Apache OpenOffice (AOO) Bugzilla – Issue 64680
ooffice base crashes (twice) when existing from edit table
Last modified: 2006-07-12 15:30:52 UTC
When I am finished editing a table and press the "save" option in the file menu, open office crashes. This has happened twice in the past 30 minutes. A dialog box opens and says to include the following information in the bug report: Video Driver is probably nv DESKTOP_SESSION is set to libgcj version is libgcj-4.0.2-8.fc4 OpenOffice.org core rpm version is openoffice.org-core-2.0.1.1-5.1 0xe08007: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x1e007 0xe087cc: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x1e7cc 0xa86420: + 0x420 (__kernel_sigreturn + 0x0) 0xe258d4: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x3b8d4 (rtl_convertTextToUnicode + 0x93) 0xe1518e: /usr/lib/openoffice.org2.0/program/libuno_sal.so.3 + 0x2b18e (rtl_string2UString + 0x192) 0x3622197: /usr/lib/openoffice.org2.0/program/libodbcbase2.so + 0x3b197 0x3646ec4: /usr/lib/openoffice.org2.0/program/libodbcbase2.so + 0x5fec4 (connectivity::odbc::OConnection::getCatalog() + 0xc0) 0x42a1406: /usr/lib/openoffice.org2.0/program/libdbu680li.so + 0xda406 0x4248823: /usr/lib/openoffice.org2.0/program/libdbu680li.so + 0x81823 0x42495f8: /usr/lib/openoffice.org2.0/program/libdbu680li.so + 0x825f8 0x43320ae: /usr/lib/openoffice.org2.0/program/libdbu680li.so + 0x16b0ae 0x4331892: /usr/lib/openoffice.org2.0/program/libdbu680li.so + 0x16a892 0x239d7b9: /usr/lib/openoffice.org2.0/program/libfwk680li.so + 0xb67b9 0x239d844: /usr/lib/openoffice.org2.0/program/libfwk680li.so + 0xb6844 0x6b42e72: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x82e72 0x6c55e60: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x195e60 (Menu::Select() + 0x3c) 0x6c5064d: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x19064d 0x6c50660: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x190660 0x6b42e72: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x82e72 0x6c9c485: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x1dc485 0x358eed0: /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so + 0x1eed0 0x35b512b: /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so + 0x4512b (SalDisplay::DispatchInternalEvent() + 0xad) 0x9d2e1f: /usr/lib/openoffice.org2.0/program/libvclplug_gtk680li.so + 0x1ae1f 0x3a8c730: /usr/lib/libglib-2.0.so.0 + 0x25730 0x3a8a4ce: /usr/lib/libglib-2.0.so.0 + 0x234ce (g_main_context_dispatch + 0x1dc) 0x3a8d4d6: /usr/lib/libglib-2.0.so.0 + 0x264d6 0x3a8d9b8: /usr/lib/libglib-2.0.so.0 + 0x269b8 (g_main_context_iteration + 0x66) 0x9d2a51: /usr/lib/openoffice.org2.0/program/libvclplug_gtk680li.so + 0x1aa51 0x35b633d: /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so + 0x4633d (X11SalInstance::Yield(unsigned char) + 0x29) 0x6b491ba: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x891ba (Application::Yield() + 0x50) 0x6b491f8: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x891f8 (Application::Execute() + 0x26) 0x7f08015: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x29015 (desktop::Desktop::Main() + 0x15df) 0x6b4e769: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x8e769 0x6b4e819: /usr/lib/openoffice.org2.0/program/libvcl680li.so + 0x8e819 (SVMain() + 0x29) 0x7effa37: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x20a37 (sal_main + 0x57) 0x7effa83: /usr/lib/openoffice.org2.0/program/libsoffice.so + 0x20a83 (main + 0x27) 0x4e3d5f: /lib/libc.so.6 + 0x14d5f (__libc_start_main + 0xdf) 0x80484c5: /usr/lib/openoffice.org2.0/program/soffice.bin + 0x4c5 I am running redhat fedora core 4, 2.6.14-1.1656_FC4 kernel, on an i686 athlon.
Hi I can't reproduce this. Can you please give me some more information. What kind of database connection type do you use? ( HSQLDB / ODBC / JDBC /.. ) I assume that it's ODBC, right? Does the crash also occurr if you use another ODBC driver ? Bye Marc
I can't reproduce it with m163. There was a bug in prior version to input data via forms. @ jeffsilv Which is the exact version number you use?
Here is the procedure I use to connect to the database. Start OpenOffice (ooffice). File -> New -> database . Select Connect to an existing database using ODBC. Use MySQL-equipment_test as the data source name (note that this comes from the /etc/odbc.ini file). Enter the username, and turn on the password required checkbox if needed. Since the equipment_test database allows anonymous read/only access, this step is optional. Click on the test database button, and it should say that it connected successfully. Register the database, which creates a file so you can do this faster next time. Click on edit tables if you want to edit the tables. To reproduce the problem: go through the procedure above. Then, click on the create table in design view, design a table, and click on the save icon and it crashes. When I restart openoffice base, it goes through the recovery process fine. I also tried: File -> New -> database . Select Connect to an existing database using MySQL. Click on NEXT. Select ODBC. Click on Browse. Select MySQL_equipment_test. It wants a user name, enter root select password required. Select register the database. Select open database for editing. Again, click on the create table in design view, design a table, and click on the save icon and it crashes. I tried using JDBC, but it won't open the JDBC driver (probably because I haven't installed it yet - I need to go back and read the manual). I am using OpenOffice 2.0 from RedHat Fedora Core 4. [jeffs@black ~]$ rpm -q --file /usr/bin/oobase openoffice.org-core-2.0.1.1-5.1 [jeffs@black ~]$ rpm -q -a | fgrep openoffice openoffice.org-calc-2.0.1.1-5.1 openoffice.org-javafilter-2.0.1.1-5.1 openoffice.org-core-2.0.1.1-5.1 openoffice.org-debuginfo-2.0.1.1-5.1 openoffice.org-impress-2.0.1.1-5.1 openoffice.org-math-2.0.1.1-5.1 openoffice.org-xsltfilter-2.0.1.1-5.1 openoffice.org-pyuno-2.0.1.1-5.1 openoffice.org-graphicfilter-2.0.1.1-5.1 openoffice.org-writer-2.0.1.1-5.1 openoffice.org-testtools-2.0.1.1-5.1 openoffice.org-draw-2.0.1.1-5.1 [jeffs@black ~]$ uname -a Linux black 2.6.14-1.1656_FC4 #1 Thu Jan 5 22:13:22 EST 2006 i686 athlon i386 GNU/Linux Here is my odbc.ini file contents: [MySQL-test] Description = MySQL database test Driver = MySQL Server = localhost Database = test Port = 3306 [MySQL-equipment_dev] Description = MySQL equipment database development Driver = MySQL Server = black.commercialventvac.com Database = equipment_dev Port = 3306 [MySQL-equipment_test] Description = MySQL equipment database test Driver = MySQL Server = black.commercialventvac.com Database = equipment_test Port = 3306 [jeffs@black ~]$ more /etc/odbcinst.ini # Example driver definitinions # # # Included in the unixODBC package #[PostgreSQL] #Description = ODBC for PostgreSQL #Driver = /usr/lib/libodbcpsql.so #Setup = /usr/lib/libodbcpsqlS.so #FileUsage = 1 # Driver from the MyODBC package # Setup from the unixODBC package [MySQL] Description = ODBC for MySQL Driver = /usr/lib/libmyodbc.so Setup = /usr/lib/libodbcmyS.so FileUsage = 1 [jeffs@black ~]$ ls -l /usr/lib/libodbcmy* lrwxrwxrwx 1 root root 19 Jan 16 04:49 /usr/lib/libodbcmyS.so -> libodbcmyS.so.1.0.0 lrwxrwxrwx 1 root root 19 Jan 16 04:49 /usr/lib/libodbcmyS.so.1 -> libodbcmyS.so.1.0.0 -rwxr-xr-x 1 root root 6252 Sep 30 2005 /usr/lib/libodbcmyS.so.1.0.0 [jeffs@black ~]$ rpm -q --file /usr/lib/libodbcmy* unixODBC-2.2.11-3.FC4.1 unixODBC-2.2.11-3.FC4.1 unixODBC-2.2.11-3.FC4.1 [jeffs@black ~]$
Which version of mysql do you use? MySQL version <= 4.1.x doesn't support views.
clu->jeffsilv: does mechtildes hint helped you further (solved your problem)?
seems that problem is solved
=> close do not hestitate to reopen if problem still exist in current version