[Digikam-devel] [Bug 277928] DigiKam fails to start properly, lost albums (schema updating process from version 4 to 5 failed)

Tue Jul 19 18:11:48 BST 2011

https://bugs.kde.org/show_bug.cgi?id=277928

--- Comment #2 from Steve Toledo-Brown <stevetldbrwn gmail com>  2011-07-19 17:11:47 ---
Does this console output help? It comes from me starting digikam, attempting
to load a local collection, which failed at about 67%,
and then shutting it down. This failure at about 67% happens every time now
so it makes digikam completely unusable. Do I have any workaround other than
wiping out any databases and reinstalling?

dad at sktju:~$ digikam
KGlobal::locale::Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related functions before your main component was created. You
should not do that since it most likely will not work
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in
use, all queries will cease to work.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...
params.c:OpenConfFile() - Unable to open configuration file
"/home/dad/.smb/smb.conf":
    No such file or directory
params.c:OpenConfFile() - Unable to open configuration file
"/home/dad/.smb/smb.conf.append":
    No such file or directory
Time elapsed: 293 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
Time elapsed: 2 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 13 ms
KGlobal::locale::Warning your global KLocale is being recreated with a valid
main component instead of a fake component, this usually means you tried to
call i18n related functions before your main component was created. You
should not do that since it most likely will not work
digikam(1659)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void
Plugin_DebianScreenshots::setup(QWidget*)
Time elapsed: 2 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 11 ms
Time elapsed: 1 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
Time elapsed: 1 ms
Model: Time elapsed: 0 ms
TextureColorizer::setSeaFileLandFile: Time elapsed: 10 ms
digikam(1659)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for
Digikam::ImagePropertiesSideBarDB(0xa10ac00)  is empty. Returning the
default config group
digikam(1659)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for
Digikam::ImagePropertiesSideBarDB(0xa3268d0)  is empty. Returning the
default config group
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-143398888'
is still in use, all queries will cease to work.
klauncher(1672)/kio (KLauncher): SlavePool: No communication with slave.

QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
klauncher(1672)/kio (KLauncher): SlavePool: No communication with slave.

klauncher(1672)/kio (KLauncher): SlavePool: No communication with slave.

digikam(1659)/KIPI (general) Plugin_DebianScreenshots::setup: virtual void
Plugin_DebianScreenshots::setup(QWidget*)
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
Application asked to unregister timer 0x11000065 which is not registered in
this thread. Fix application.

(user note: now after digikam failed to load new digikam(1659)
KWidgetItemDelegateEventListener::eventFilter: User of KWidgetItemDelegate
should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
digikam(1659) KWidgetItemDelegateEventListener::eventFilter: User of
KWidgetItemDelegate should not delete widgets created by createItemWidgets!
(user note attempt 2: now after digikam failed to load new Local Collection)
(user note: about to shut down digikam)digikam(1659)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for
Digikam::Sidebar(0xa3268d0)  is empty. Returning the default config group
digikam(1659)/digikam (core)
Digikam::StateSavingObjectPriv::getGroupFromObjectName: Object name for
Digikam::Sidebar(0xa10ac00)  is empty. Returning the default config group
QSqlDatabasePrivate::removeDatabase: connection 'digikamDatabase-146553232'
is still in use, all queries will cease to work.
dad at sktju:~$

On Mon, Jul 18, 2011 at 6:12 PM, Marcel Wiesweg <marcel.wiesweg at gmx.de>wrote:

> https://bugs.kde.org/show_bug.cgi?id=277928
>
>
>
>
>
> --- Comment #1 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-07-18
> 17:12:35 ---
> We will not really be able to help here if the original error is gone and
> the
> situation is not reproducible.
> The error message is unspecific and may occur in the case of database
> corruption.
>
> Normally, parallel access should be possible, unless there is a network
> drive
> involved in which case sqlite file locking may not work.
>
> The problem of the "dialog gone later" would need more infos to
> investigate.
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.