Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
Locked
Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
 
|
Hi,
Since I've updated my Kubuntu Maverick to Kde 4.6 using ppa backport, the only problem come with Digikam sylvain@sjc-desktop:~$ 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. QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Solid::Backends::Fstab::FstabStorageAccess::slotSetupRequested(): org.freedesktop.DBus.Error.MatchRuleInvalid (Path '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is invalid ) QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Solid::Backends::Fstab::FstabStorageAccess::slotSetupDone(int,QString): org.freedesktop.DBus.Error.MatchRuleInvalid (Path '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is invalid ) QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Solid::Backends::Fstab::FstabStorageAccess::slotTeardownRequested(): org.freedesktop.DBus.Error.MatchRuleInvalid (Path '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is invalid ) QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to Solid::Backends::Fstab::FstabStorageAccess::slotTeardownDone(int,QString): org.freedesktop.DBus.Error.MatchRuleInvalid (Path '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is invalid ) Time elapsed: 57 ms Model: Time elapsed: 87 ms TextureColorizer: Time elapsed: 15 ms Time elapsed: 5 ms Model: Time elapsed: 27 ms QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun fichier ou dossier de ce type QFileSystemWatcher: failed to add paths: /home/sylvain/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/sylvain/.kde/socket-sjc-desktop/kdeinit4__0 QSocketNotifier: Invalid socket 14 and type 'Read', disabling... QSocketNotifier: Invalid socket 39 and type 'Read', disabling... QSocketNotifier: Invalid socket 40 and type 'Read', disabling... QSocketNotifier: Invalid socket 47 and type 'Read', disabling... [1]+ Stopped digikam sylvain@sjc-desktop:~$ _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
|
|
run digiKam trough gdb and post trace here :
http://www.digikam.org/drupal/contrib Gilles Caulier 2011/1/27 Sylvain ZUCCA <[hidden email]>: > Hi, > > Since I've updated my Kubuntu Maverick to Kde 4.6 using ppa backport, the > only problem come with Digikam > > sylvain@sjc-desktop:~$ 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. > QDBusConnectionPrivate::connectSignal: received error from D-Bus server > while connecting signal to > Solid::Backends::Fstab::FstabStorageAccess::slotSetupRequested(): > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is > invalid > ) > QDBusConnectionPrivate::connectSignal: received error from D-Bus server > while connecting signal to > Solid::Backends::Fstab::FstabStorageAccess::slotSetupDone(int,QString): > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is > invalid > ) > QDBusConnectionPrivate::connectSignal: received error from D-Bus server > while connecting signal to > Solid::Backends::Fstab::FstabStorageAccess::slotTeardownRequested(): > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is > invalid > ) > QDBusConnectionPrivate::connectSignal: received error from D-Bus server > while connecting signal to > Solid::Backends::Fstab::FstabStorageAccess::slotTeardownDone(int,QString): > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' is > invalid > ) > Time elapsed: 57 ms > Model: Time elapsed: 87 ms > TextureColorizer: Time elapsed: 15 ms > Time elapsed: 5 ms > Model: Time elapsed: 27 ms > QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun > fichier ou dossier de ce type > QFileSystemWatcher: failed to add paths: /home/sylvain/.config/ibus/bus > Bus::open: Can not get ibus-daemon's address. > IBusInputContext::createInputContext: no connection to ibus-daemon > KCrash: Application 'digikam' crashing... > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > sock_file=/home/sylvain/.kde/socket-sjc-desktop/kdeinit4__0 > QSocketNotifier: Invalid socket 14 and type 'Read', disabling... > QSocketNotifier: Invalid socket 39 and type 'Read', disabling... > QSocketNotifier: Invalid socket 40 and type 'Read', disabling... > QSocketNotifier: Invalid socket 47 and type 'Read', disabling... > > [1]+ Stopped digikam > sylvain@sjc-desktop:~$ > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users > > Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
|
|
First try : http://paste.ubuntu.com/559385/ So problem ibus ? ==> I install ibus $ sudo apt-get install ibus $ibus-daemon -d Second try : http://paste.ubuntu.com/559384/ Problem with usr/lib/libmarblewidget.so.10 ? I have to packages installed of libmarblewidget libmarblewidget10 (for Kde 4.5.5) libmarblewidget11 (for Kde 4.6.0) ==> I desactivate philip5's PPA and I reinstall Digikam Third try : http://paste.ubuntu.com/559386/ Now it's /usr/lib/libQtCore.so.4 I do not know what to do ??? 2011/1/27 Gilles Caulier <[hidden email]> run digiKam trough gdb and post trace here : -- Sylvain _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
|
|
2011/1/28 Sylvain ZUCCA <[hidden email]>:
> > First try : http://paste.ubuntu.com/559385/ > > So problem ibus ? > ==> I install ibus > $ sudo apt-get install ibus > $ibus-daemon -d Marble crashed... > > > Second try : http://paste.ubuntu.com/559384/ > > Problem with usr/lib/libmarblewidget.so.10 ? > I have to packages installed of libmarblewidget > yes, Marble crashed again. Only use one shared lib here. > libmarblewidget10 (for Kde 4.5.5) > libmarblewidget11 (for Kde 4.6.0) > > ==> I desactivate philip5's PPA and I reinstall Digikam > > > Third try : http://paste.ubuntu.com/559386/ > > Now it's /usr/lib/libQtCore.so.4 > > I do not know what to do ??? > Hum. Looking previous crash i recommend to cleanup marble install and to use last version available, and only one. Gilles _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport
|
|
In reply to this post by Sylvain ZUCCA
Just for notice, I'm running KDE 4.6 and Digikam 1.8 on maverik without any problems, both coming from kubuntu-ppa backports. I assume you have installad some component from another ppa making trouble.
Regards, Jens -------- Original-Nachricht -------- > Datum: Fri, 28 Jan 2011 06:54:20 +0100 > Von: Sylvain ZUCCA <[hidden email]> > An: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> > Betreff: [Digikam-users] Re: Segmentation fault with Digikam 1.8 and Kubuntu Maverick with Kde 4.6 Backport > First try : http://paste.ubuntu.com/559385/* > * > So problem ibus ? > ==> I install ibus > $ sudo apt-get install ibus > $ibus-daemon -d > > > Second try : http://paste.ubuntu.com/559384/ > > Problem with usr/lib/libmarblewidget.so.10 ? > I have to packages installed of libmarblewidget > > libmarblewidget10 (for Kde 4.5.5) > libmarblewidget11 (for Kde 4.6.0) > > ==> I desactivate philip5's PPA and I reinstall Digikam > > > Third try : http://paste.ubuntu.com/559386/ > > Now it's /usr/lib/libQtCore.so.4 > > I do not know what to do ??? > > > > > > > 2011/1/27 Gilles Caulier <[hidden email]> > > > run digiKam trough gdb and post trace here : > > > > http://www.digikam.org/drupal/contrib > > > > Gilles Caulier > > > > 2011/1/27 Sylvain ZUCCA <[hidden email]>: > > > Hi, > > > > > > Since I've updated my Kubuntu Maverick to Kde 4.6 using ppa backport, > the > > > only problem come with Digikam > > > > > > sylvain@sjc-desktop:~$ 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. > > > QDBusConnectionPrivate::connectSignal: received error from D-Bus > server > > > while connecting signal to > > > Solid::Backends::Fstab::FstabStorageAccess::slotSetupRequested(): > > > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > > > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' > is > > > invalid > > > ) > > > QDBusConnectionPrivate::connectSignal: received error from D-Bus > server > > > while connecting signal to > > > > Solid::Backends::Fstab::FstabStorageAccess::slotSetupDone(int,QString): > > > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > > > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' > is > > > invalid > > > ) > > > QDBusConnectionPrivate::connectSignal: received error from D-Bus > server > > > while connecting signal to > > > Solid::Backends::Fstab::FstabStorageAccess::slotTeardownRequested(): > > > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > > > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' > is > > > invalid > > > ) > > > QDBusConnectionPrivate::connectSignal: received error from D-Bus > server > > > while connecting signal to > > > > > > Solid::Backends::Fstab::FstabStorageAccess::slotTeardownDone(int,QString): > > > org.freedesktop.DBus.Error.MatchRuleInvalid (Path > > > '/org/kde/solid/Device__2Forg_2Fkde_2Ffstab_2Fnas-sjc_3A_2Fc_2Fmedia' > is > > > invalid > > > ) > > > Time elapsed: 57 ms > > > Model: Time elapsed: 87 ms > > > TextureColorizer: Time elapsed: 15 ms > > > Time elapsed: 5 ms > > > Model: Time elapsed: 27 ms > > > QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: > > Aucun > > > fichier ou dossier de ce type > > > QFileSystemWatcher: failed to add paths: > /home/sylvain/.config/ibus/bus > > > Bus::open: Can not get ibus-daemon's address. > > > IBusInputContext::createInputContext: no connection to ibus-daemon > > > KCrash: Application 'digikam' crashing... > > > KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit > > > sock_file=/home/sylvain/.kde/socket-sjc-desktop/kdeinit4__0 > > > QSocketNotifier: Invalid socket 14 and type 'Read', disabling... > > > QSocketNotifier: Invalid socket 39 and type 'Read', disabling... > > > QSocketNotifier: Invalid socket 40 and type 'Read', disabling... > > > QSocketNotifier: Invalid socket 47 and type 'Read', disabling... > > > > > > [1]+ Stopped digikam > > > sylvain@sjc-desktop:~$ > > > > > > > > > _______________________________________________ > > > Digikam-users mailing list > > > [hidden email] > > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users > > > > > > -- > Sylvain -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |