Thank you for interesting of this bug! I've doing some experiments and here are the results:
This is not reproduced on clean installation of Ubuntu Karmic i386. The package version is same, the steps are same, but works as expected. But, on my Ubuntu Jaunty (x86_64) it is 100% reproducible. The differences are the CPU and configuration file. I have found that my ODBC configuration file is the source of this bug. == part of /etc/odbcinst.ini file == [Text File] Description = Text File ODBC driver Driver = /usr/lib/odbc/libodbctxt.so Driver64 = Setup = /usr/lib/odbc/libodbctxtS.so Setup64 = UsageCount = 1 CPTimeout = CPReuse = == end of part == When Setup64 parameter is missing, the ODBCConfig crushes as I have described above. When Setup64 is equal to Setup parameter - all fine - dialog appears. So, with this configuration file ODBCConfig works as expected: == part of /etc/odbcinst.ini file == [Text File] Description = Text File ODBC driver Driver = /usr/lib/odbc/libodbctxt.so Driver64 = /usr/lib/odbc/libodbctxt.so Setup = /usr/lib/odbc/libodbctxtS.so Setup64 = /usr/lib/odbc/libodbctxtS.so UsageCount = 1 CPTimeout = CPReuse = == end of part == It will be great to fix the bug. IMHO, the program should show message box with error message on invalid or incomplete parameters, but shouldn't crash. Good luck with bugfixing and thank you again. -- ODBCConfig fails on configure existing data source https://bugs.launchpad.net/bugs/362603 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to unixodbc in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
