[Kexi] Problems starting with Kexi

[Alejandro Exojo]

El Miércoles, 28 de Junio de 2006 17:42, Jaroslaw Staniek escribió:
> Alejandro Exojo said the following, On 2006-06-28 13:10:
> > I'm trying kexi 1.5.1 (packages from debian unstable). And I'm having
> > problems with my first steps. For example:
> >
> > Kexi / Import existing database / Import database wizard + Next /
> > Mark "projects stored on a database server" / Edit database connection /
> > Type a password, and click "test connection"
> >
> > At this step, Kexi hangs most of the times. The dialog saying it
> > succeeded or failed appears fine, but after clicking OK, it doesn't
> > returns, Kexi doesn't repaints, and appears grey. Especially I can
> > reproduce it if I click twice the "test connection" button. At this step
> > is not consuming CPU, or writing anything to a console, if started from
> > it.
>
> Hi,
> Thanks for the report. Please send a copy to kexi at kde.org next time.

OK, doing now.

> The bug was already reported here:
> https://bugs.kde.org/show_bug.cgi?id=124959 and fixes are planned for 1.6
> and/or 1.5.2.
>
> Feel free to send additional info, if there's any.
> I understand creation of the database connection and performing the
> connection didn't fail?

Well, it seems so. The dialog says "Test connection to alex at localhost database 
server established successfully.", so I assume yes. Oh, and later it shows 
the correct list of available databases, so yes again.

> > Another problem I have is doing this steps:
> >
> > Kexi / Import existing database / Import database wizard + Next /
> > Mark "projects stored on a database server" + Next / Choose a database
> > from the mysql DBs available + Next / Choose sqlite3 as Destination type
> > + Next / Enter a project caption + Next / Enter a Location + Next /
> > Structure and data + Next / And Next again. Here I have this:
> >
> > Import failed.
> > Could not import data from data source "alex at localhost".
> > Not connected to the database server.
> > You can click "Back" button and try again.
> >
> > Then I try to come back and do some changes (e.g., choosing only
> > structure, instead of structure and data), but I have the same error
> > again. If I cancel, I have this backtrace:
> >
> > Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
> > [Thread debugging using libthread_db enabled]
> > [New Thread -1509677376 (LWP 9271)]
> > [KCrash handler]
> > #6  0x00000000 in ?? ()
> > #7  0xa5ca60ae in QAsciiDict<KexiMigration::KexiMigrate>::deleteItem (
> >     this=0x82bc044, d=0x83c4058) at
> > /usr/share/qt3/include/qasciidict.h:97 #8  0xa6de43f5 in QGDict::clear ()
> > from /usr/lib/libqt-mt.so.3
> > #9  0xa5ca1e56 in ~MigrateManagerInternal (this=0x82bbfd0)
> >     at /usr/share/qt3/include/qasciidict.h:75
> > #10 0xa5ca0f3e in ~MigrateManager (this=0xa5cb0a00)
> >     at /tmp/buildd/koffice-1.5.1/./kexi/migration/migratemanager.cpp:286
> > #11 0xa5ca0fa0 in __tcf_0 ()
> >     at /tmp/buildd/koffice-1.5.1/./kexi/migration/migratemanager.cpp:50
> > #12 0xa7d3a384 in exit () from /lib/tls/i686/cmov/libc.so.6
> > #13 0xa7d22eb8 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
> > #14 0x080483d1 in _start () at ../sysdeps/i386/elf/start.S:119
> >
> >
> > I've tried changing the user to mysql's root, and it fails the same way.
>
> Can you see the list of mysql databases when you used "file->open" ?

Yes.

> Are you able to open any mysql database selected from the list?

No. :( Any database I try to open (including the "test" one, using root) 
fails: it says it need to import it because was not created with kexi, and 
the import process fails with the problem described above.

> I know you'll get error like "could not open project 'testdb'. invalid
> database contents. kexidb_major_ver database property not found." ... but
> if this message appears, this means you're at least able to connect
> physically to the mysql server.
>
> If you jsut get "Could not load list of available projects for... server" ,
> please check you connection settings. In particular: port number, or if
> it's "default", and your connection local, be sure you have selected "use
> socket file instead of TCP/IP port" in the "Details" tab.

No, I get the errors I say above ("Import failed (...)", etc.). I tried making 
explicit which socket file is, but still the same messages.

Thanks for your help.

-- 
Alex (a.k.a. suy) - GPG ID 0x0B8B0BC2
http://barnacity.net/ - Jabber ID: suy at bulmalug.net