Summary: | Digikam hangs on startup (splash screen: reading database) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Michael Körber <m.koerber> |
Component: | ProgressManager-Splashscreen | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.9.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.0.0 | |
Sentry Crash Report: |
Description
Michael Körber
2011-06-16 13:10:29 UTC
- is the relevant CIFS collection added as a network collection or as a normal collection in setup? Is the directory sometimes not mounted? - is the command find /home/username/Bilder/net_bilder considerably faster than digikam's scanning? The relevant cifs-collection is added as a network collection in setup. The find /home/username/Bilder/net_bilder takes 00:02:36.69. Yes it is considerably faster. Even over night digikam is unable to start. I tried starting digikam without the cifs being mounted. Digikam starts immediately. Perhaps this cli output is helpful. 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. Time elapsed: 61 ms Model: Time elapsed: 0 ms TextureColorizer::setSeaFileLandFile: Time elapsed: 9 ms Time elapsed: 4 ms Model: Time elapsed: 0 ms kbuildsycoca4 running... 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 'digikamDatabase-158723464' is still in use, all queries will cease to work. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. QSocketNotifier: Invalid socket 13 and type 'Read', disabling... klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. klauncher(1835)/kio (KLauncher): SlavePool: No communication with slave. I switched to another Linux distribution. The reported Bug occured with Fedora 15. Now I'm using Ubuntu 11.04. Everything works fine and digikam starts within 4 minutes. In consideration of my collection's size (see above) this is acceptable for me. It is still slower than a local collection, and needs improvement, but as you see the major issue was due to CIFS implementation probably in connection with adding KDirWatches. |