Scanning is aborted. 'unrecognized token' error

Bug #1084428 reported by Josef Burg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Basenji
Fix Committed
Undecided
Patrick Ulbrich

Bug Description

I'm trying to scan my external HDD. I'm on Linux 3.2.0-33-generic #52-Ubuntu SMP x86_64.
Package version of basenji is 0.9.0-1. Version reported by basenji is 0.9.0.0.

Each time, basenji enters a specific folder, it aborts the scan with the followin error:

[VolumeDB DBG]: Details for exception in ScanningThread():
Mono.Data.Sqlite.SqliteException: SQLite error
unrecognized token: "'[7:42:43:5:85:1:21:8]made by damian kang aka h4hamster for IPB"
  at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, UInt32 timeoutMS, System.String& strRemain) [0x00000] in <filename unknown>:0
  at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00000] in <filename unknown>:0

Moving the folder away from the drive got me a liitle further, but on another folder basenji reports

[VolumeDB DBG]: Details for exception in ScanningThread():
Mono.Data.Sqlite.SqliteException: SQLite error
unrecognized token: "'[7:2:43:7:85:1:21:8]@"
  at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, UInt32 timeoutMS, System.String& strRemain) [0x00000] in <filename unknown>:0
  at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00000] in <filename unknown>:0

Because I couldn't identify a single file, I attached the whole folder to this Bug report. After downloading the folder to another drive and running basenji again, the error was reproducable.

Revision history for this message
Josef Burg (jburg88) wrote :
Patrick Ulbrich (pulb)
Changed in basenji:
status: New → Confirmed
assignee: nobody → Patrick Ulbrich (pulb)
milestone: none → 1.1
Revision history for this message
Patrick Ulbrich (pulb) wrote :

Many thanks for your bugreport and sample files!
I located the bug in one of Basenji's dependencies - taglib#. Taglib# returns comment metadata strings for some of your files including the terminating zero ('\0'). Those strings are eventually passed to Basenji's SQL backend which reinterprets the zeros as the end of the sql string.

I'll report the bug upstream and provide a temporary bugfix shortly.

Revision history for this message
Patrick Ulbrich (pulb) wrote :

I commited a fix that should hit the daily PPA within the next hour. Please test.
https://launchpad.net/~pulb/+archive/basenji-daily

Revision history for this message
Josef Burg (jburg88) wrote :

Updated and tested. Bugfix works.

Thanks a lot for the quick help.

Changed in basenji:
status: Confirmed → Fix Committed
Revision history for this message
Patrick Ulbrich (pulb) wrote :

Thanks again for reporting! The upstream bugreport is available here: https://bugzilla.gnome.org/show_bug.cgi?id=599873

Patrick Ulbrich (pulb)
Changed in basenji:
milestone: 1.1 → none
milestone: none → 1.1
milestone: 1.1 → none
Revision history for this message
Paul R. (paul-nz) wrote :

This bug has appeared for me on Ubuntu 14.04, running the latest daily PPA build, 1.0.1+641-0~ubuntu14.04.1. I get the following error (and SQLite rollback) when it attempts to scan a directory with several JPGs, a PNG and a YAML file:

[VolumeDB DBG]: Details for exception in ScanningThread():
Mono.Data.Sqlite.SqliteException: SQLite error
unrecognized token: "'[7:21:43:6:85:1:21:8]"
  at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, UInt32 timeoutMS, System.String& strRemain) [0x00000] in <filename unknown>:0
  at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00000] in <filename unknown>:0

Revision history for this message
Patrick Ulbrich (pulb) wrote :

Can you try to identify the file which is responsible for the crash and attach it to this report or send it to me?

Revision history for this message
Paul R. (paul-nz) wrote :

OK, I've isolated it (a PNG), but I don't own the copyright on the file, so I've PM'd a link.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.