Ubuntu
sqliteman package

sqliteman crashes on startup

Bug #628044 reported by Dennis Schridde on 2010-09-01

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	sqliteman (Ubuntu)	Fix Released	Medium	Unassigned

Bug Description

Binary package hint: sqliteman

Following crash is perfectly reproducable, I just start sqliteman. It will crash even before I see the mainwindow:

Starting program: /usr/bin/sqliteman
[Thread debugging using libthread_db enabled]
(3789) KSharedDataCache::Private::mapSharedMemory: Opening cache "/var/tmp/kdecache-$USER/icon-cache.kcache" page size is 4096
(3789) KSharedDataCache::Private::mapSharedMemory: Attached to cache, determining if it must be initialized
(3789) KSharedDataCache::Private::mapSharedMemory: Cache fully initialized -- attached to memory mapping
(3789) KSharedDataCache::Private::mapSharedMemory: 4349952 bytes available out of 10485760
Checking for sqlite3 :
[New Thread 0xb6065b70 (LWP 3795)]
3.6.22
Checking for Qt version: 4.7.0
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
[New Thread 0xb4873b70 (LWP 3797)]
QFileSystemWatcher: failed to add paths: /home/$USER/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
[New Thread 0xb3fe6b70 (LWP 3798)]

Program received signal SIGSEGV, Segmentation fault.
0x00f268f6 in QsciScintillaBase::SendScintilla(unsigned int, unsigned long, long) const () from /usr/lib/libqscintilla2.so.5
(gdb) bt full
#0 0x00f268f6 in QsciScintillaBase::SendScintilla(unsigned int, unsigned long, long) const () from /usr/lib/libqscintilla2.so.5
No symbol table info available.
#1 0x00f1ccc3 in QsciScintilla::recolor(int, int) () from /usr/lib/libqscintilla2.so.5
No symbol table info available.
#2 0x00f25b5d in QsciScintilla::startAutoCompletion(QsciScintilla::AutoCompletionSource, bool, bool) () from /usr/lib/libqscintilla2.so.5
No symbol table info available.
#3 0x00f26228 in QsciScintilla::autoCompleteFromAll() () from /usr/lib/libqscintilla2.so.5
No symbol table info available.
#4 0x00f24584 in QsciScintilla::setLexer(QsciLexer*) () from /usr/lib/libqscintilla2.so.5
No symbol table info available.
#5 0x080e95e1 in SqlEditorWidget::SqlEditorWidget(QWidget*) ()
No symbol table info available.
#6 0x0809de62 in Ui_DataViewer::setupUi(QMainWindow*) ()
No symbol table info available.
#7 0x0809a55f in DataViewer::DataViewer(QWidget*) ()
No symbol table info available.
#8 0x080aae91 in LiteManWindow::initUI() ()
No symbol table info available.
#9 0x080b5356 in LiteManWindow::LiteManWindow(QString const&) ()
No symbol table info available.
#10 0x080bb8cf in main ()
No symbol table info available.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: sqliteman 1.2.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Wed Sep 1 14:36:00 2010
InstallationMedia: Kubuntu-Netbook 10.04 "Lucid Lynx" - Beta i386 (20100318)
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: sqliteman

Tags:

Related branches

lp:ubuntu/maverick/sqliteman

Revision history for this message

Dennis Schridde (devurandom) wrote on 2010-09-01:

Dependencies.txt Edit (1.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Niall Creech (sevenmachines-deactivatedaccount) wrote on 2010-09-17:

confirmed 1.2.2-0ubuntu1 on maverick

Changed in sqliteman (Ubuntu):
status:	New → Confirmed

Revision history for this message

Niall Creech (sevenmachines-deactivatedaccount) wrote on 2010-09-17:

A no-change rebuild to pick up newer libscintilla2-5 library seems to fix it in maverick, i'll check lucid later
I'll attach a debdiff for habits sake but it is just a rebuild

sqliteman (1.2.2-0ubuntu2) maverick; urgency=low

* No change rebuild to pick up new libscintilla2-5 changes

Test-Build: https://edge.launchpad.net/~sevenmachines/+archive/release+1

Changed in sqliteman (Ubuntu):
status:	Confirmed → In Progress
assignee:	nobody → SevenMachines (sevenmachines)

Niall Creech (sevenmachines-deactivatedaccount) on 2010-09-17

Changed in sqliteman (Ubuntu):
assignee:	SevenMachines (sevenmachines) → nobody
status:	In Progress → Confirmed

Revision history for this message

Niall Creech (sevenmachines-deactivatedaccount) wrote on 2010-09-17:

I cant reproduce this bug on lucid amd64 or i386, but the rebuild is valid for maverick. Should the rebuild close the bug?

Stefano Rivera (stefanor) on 2010-09-17

Changed in sqliteman (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Stefano Rivera (stefanor) wrote on 2010-09-17:

SevenMachines: You forgot to close the bug in the changelog.

I can't reproduce this bug on maverick amd64.

Revision history for this message

Niall Creech (sevenmachines-deactivatedaccount) wrote on 2010-09-17:

sqliteman_1.2.2-0ubuntu2.debdiff Edit (444 bytes, text/plain)

I was wondering if this bug was lucid and not maverick whether or not to close it.
I have maverick i386 fully up-to-date here and get
$ sudo apt-get sqliteman
$ sqliteman
* Then a pop up window
"Sqliteman crashes due to Signal #11

All database opened will be rollbacked and closed.

Collect last steps that forced this
situlation and report it as a bug, please."

* gdb backtrace,
Program received signal SIGSEGV, Segmentation fault.
0x00f15596 in QsciScintillaBase::SendScintilla(unsigned int, unsigned long, long) const () from /usr/lib/libqscintilla2.so.5
(gdb) backtrace
#0 0x00f15596 in QsciScintillaBase::SendScintilla(unsigned int, unsigned long, long) const () from /usr/lib/libqscintilla2.so.5
#1 0x00f0b953 in QsciScintilla::recolor(int, int) ()
from /usr/lib/libqscintilla2.so.5
#2 0x00f147fd in QsciScintilla::startAutoCompletion(QsciScintilla::AutoCompletionSource, bool, bool) () from /usr/lib/libqscintilla2.so.5

so it looks like the same bug as originally reported.

It doesnt seem to be a qscintilla thing on second look though, and looking at https://bugs.archlinux.org/task/20271, sqlite seems like the more likely option

I'll redo and attach

Revision history for this message

Stefano Rivera (stefanor) wrote on 2010-09-17:

Taking your word for the bug

Changed in sqliteman (Ubuntu):
status:	Confirmed → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-09-17:

This bug was fixed in the package sqliteman - 1.2.2-0ubuntu2

---------------
sqliteman (1.2.2-0ubuntu2) maverick; urgency=low

* No change rebuild to pick up newer sqlite version (LP: #628044)
-- Niall Creech <email address hidden> Fri, 17 Sep 2010 23:22:37 +0200

Changed in sqliteman (Ubuntu):
status:	Fix Committed → Fix Released

Revision history for this message

Rolf Leggewie (r0lf) wrote on 2010-09-18:

#10

JFTR, I'm the one preparing the original sqliteman package. My system runs lucid. I was never able to reproduce this crash.

Revision history for this message

Niall Creech (sevenmachines-deactivatedaccount) wrote on 2010-09-18:

#11

I couldnt reproduce it on lucid i386 here and apparently its not on maverick amd64 either. The rebuild has fixed it on maverick i386 here though, strange.