After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590478 - Crash due to database file locked
Crash due to database file locked
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
1.5.0
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-01 19:56 UTC by Ramy Eid
Modified: 2009-08-02 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
the log that contains the error message (1.96 KB, text/plain)
2009-08-01 19:57 UTC, Ramy Eid
Details
The log of the debug process (2.62 KB, text/plain)
2009-08-02 08:01 UTC, Ramy Eid
Details
debug log with banshee compiled version (7.77 KB, text/plain)
2009-08-02 14:02 UTC, Ramy Eid
Details

Description Ramy Eid 2009-08-01 19:56:34 UTC
I upgraded from banshee stable version 1.4.3 to the one available in the launchpad unstable ppa. Trying to run banshee I got an error message regarding a database problem.
Comment 1 Ramy Eid 2009-08-01 19:57:37 UTC
Created attachment 139701 [details]
the log that contains the error message
Comment 2 Ramy Eid 2009-08-01 20:05:22 UTC
(In reply to comment #0)
> I upgraded from banshee stable version 1.4.3 to the one available in the
> launchpad unstable ppa. Trying to run banshee I got an error message regarding
> a database problem.
> 

Sorry for the typos in the bug title, I meant database instead of databe. I searched to modify it but it does not seem possible.
Comment 3 Alexander Kojevnikov 2009-08-02 01:28:32 UTC
Looks like a dupe of bug 356983. A few questions:

1. Do you have other instances of banshee running? You can check with:

$ ps aux | grep banshee

2. Is anything else locking your database file? You can check with:

$ lsof -- ~/.config/banshee-1/banshee.db

3. Could you attach the full log file by running:

$ banshee-1 --debug > log.txt
Comment 4 Ramy Eid 2009-08-02 08:00:37 UTC
(In reply to comment #3)

1- I don't have other copies of banshee

2- It is only banshee is using the file
eid@aboSamoor:/tmp/bug report 3$ lsof -- ~/.config/banshee-1/banshee.db
COMMAND     PID USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
banshee-1 16373  eid    9ur  REG    8,6  3928064 459061 /home/eid/.config/banshee-1/banshee.db

3- I attached the log file
Comment 5 Ramy Eid 2009-08-02 08:01:24 UTC
Created attachment 139718 [details]
The log of the debug process
Comment 6 Bertrand Lorentz 2009-08-02 10:08:30 UTC
It seems that one of the database migration queries fails, then tries to rollback, which in turn fails with the "The database file is locked" error.

Would you be OK with me having a look at your database file ? It would help in diagnosing the problem.
You can send me the ~/.config/banshee-1/banshee.db directly by e-mail, or put it somewhere and send me the link.
See my bugzilla login for my e-mail address.
Comment 7 Alexander Kojevnikov 2009-08-02 12:23:20 UTC
Apparently it's a mono bug, I filed it at BNO: https://bugzilla.novell.com/show_bug.cgi?id=527414

In the meantime I committed a work-around.

Ramy, please check your email.
Comment 8 Ramy Eid 2009-08-02 14:02:30 UTC
Created attachment 139733 [details]
debug log with banshee compiled version
Comment 9 Ramy Eid 2009-08-02 14:03:08 UTC
I compiled banshee and it ran smoothly. I tried to generate a log to be sure that everything ok. banshee-1 with --debug is giving database error,  it was hard to reproduce. Anyway, I attached one of the corrects runs log.