Public bug reported:

I had recently installed firebird:

[EMAIL PROTECTED]:~$ sudo apt-get install firebird2-classic-server
firebird2-dev firebird2-utils-classic firebird2-examples libmono-
firebirdsql1.7-cil

I copied /usr/lib/firebird2/examples/ into my home directory, expanded
one of the example databases and added my user to the firebird group.

After logging out of X and then back in I executed the following
command:

[EMAIL PROTECTED]:examples$ isql-fb ./employee.fdb -user sysdba -password <my 
sysdba password>
Database:  ./employee.fdb, User: sysdba
lock manager: couldn't set uid to superuser
SQL> show tables;
       COUNTRY                                CUSTOMER                       
       DEPARTMENT                             EMPLOYEE                       
       EMPLOYEE_PROJECT                       JOB                            
       PHONE_LIST                             PROJECT                        
       PROJ_DEPT_BUDGET                       SALARY_HISTORY                 
       SALES                           
SQL> quit;

I then executed the command again with superuser priviledges:

[EMAIL PROTECTED]:examples$ sudo isql-fb ./employee.fdb -user sysdba -password 
<my sysdba password>
Password:
Database:  ./employee.fdb, User: sysdba
SQL> show tables;
       COUNTRY                                CUSTOMER                       
       DEPARTMENT                             EMPLOYEE                       
       EMPLOYEE_PROJECT                       JOB                            
       PHONE_LIST                             PROJECT                        
       PROJ_DEPT_BUDGET                       SALARY_HISTORY                 
       SALES                           
SQL> quit;
[EMAIL PROTECTED]:examples$ 

Shortly after quitting the isql-fb session, a dialog appeared informing
me that the fb_lock_mgr program had crashed.

I'm using edgy and all of the firebird2 packages I installed were
version 1.5.3.4870-10. I tried the same thing on Dapper on another
machine a couple of days ago and encountered no such problem. The
differences I've noted between Dapper and Edgy are:

- the Dapper version of the packages is 1.5.3.4870-3
- the "lock manager: couldn't set uid to superuser" message didn't appear (in 
isql-fb) on Dapper
- there was no message during the install on Dapper stating:
Recommended packages:
  firebird2-server
 (I have not yet installed this recommended package)

I've been asked to attach a file
(/var/crash/_usr_lib_firebird2_bin_fb_lock_mgr.1000.crash) to this bug
report, but can't yet see how I do this. I'm hoping that I get chance to
do so after I've clicked "Submit Bug Report".

** Affects: firebird2 (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed

-- 
firebird2 fb_lock_mgr program crash
https://launchpad.net/bugs/86190

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to