Summary: | Digikam shutdown as I was sellecting crop to crop an image. | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Tony Kerley <tonykerley> |
Component: | Plugin-Editor-Crop | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.6.0 | |
Sentry Crash Report: |
Description
Tony Kerley
2010-03-03 19:06:41 UTC
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there. Thanks in advance Gilles Caulier Please try with digiKam 1.4.0. Thanks in advance Gilles Caulier This has started to happen to me too. In my case it is a bit more serious in that Digikam not only crashes. The crash causes all my Linux sessions to stop, so I get logged out. In this situation, I do not see how I can do a traceback. Initially I thought that it was due to memory shortage, because the first time it happened, I had a virtual Windows 7 active. But now it happens when Digikam is running alone even though I have 3 GB memory. I have been running 1.4.0 on 10.10 for some time, until the first crash on Oct 29. Could there have been a new Ubuntu update that causes this? Application that crashed: digikam Version of the application: 1.4.0 KDE Version: 4.5.1 (on Gnome 2.32.0) Qt Version: 4.7.0 Operating System: Linux 2.6.35-22-generic x86_64 Distribution: Ubuntu 10.10 Stefan Holmström I have more information on my crashes. I have managed to get a partial crash information. Since the crash logs me out, there is no backtrace. The log follows here. I have some comments after it. +++++++++ [Thread debugging using libthread_db enabled] [New Thread 0x7fffe36af710 (LWP 5620)] [New Thread 0x7fffd6ed4710 (LWP 5621)] [New Thread 0x7fffd66d3710 (LWP 5622)] QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use , all queries will cease to work. [Thread 0x7fffd66d3710 (LWP 5622) exited] [New Thread 0x7fffd66d3710 (LWP 5624)] [New Thread 0x7fffcffff710 (LWP 5625)] [New Thread 0x7fffd5b1a710 (LWP 5626)] [New Thread 0x7fffd5319710 (LWP 5627)] [New Thread 0x7fffd4b18710 (LWP 5628)] Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QS tring,QString,QString) QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOpt ionsForNewInstance() kbuildsycoca4 running... [New Thread 0x7fffcd847710 (LWP 5629)] [New Thread 0x7fffc2d46710 (LWP 5638)] [New Thread 0x7fffc1b0d710 (LWP 5639)] [New Thread 0x7fffc130c710 (LWP 5640)] [New Thread 0x7fffc0906710 (LWP 5641)] [New Thread 0x7fffbc104710 (LWP 5642)] [New Thread 0x7fffbb903710 (LWP 5643)] Time elapsed: 603 ms Model: Time elapsed: 654 ms TextureColorizer: Time elapsed: 37 ms Time elapsed: 4 ms Model: Time elapsed: 34 ms [New Thread 0x7fffb9030710 (LWP 5644)] [New Thread 0x7fffb882f710 (LWP 5645)] [New Thread 0x7fffb802e710 (LWP 5646)] [New Thread 0x7fffb782d710 (LWP 5647)] [Thread 0x7fffb882f710 (LWP 5645) exited] [New Thread 0x7fffb702c710 (LWP 5648)] [Thread 0x7fffb782d710 (LWP 5647) exited] [Thread 0x7fffb802e710 (LWP 5646) exited] [New Thread 0x7fffb782d710 (LWP 5649)] [Thread 0x7fffb702c710 (LWP 5648) exited] [Thread 0x7fffb782d710 (LWP 5649) exited] [Thread 0x7fffb9030710 (LWP 5644) exited] [New Thread 0x7fffb9030710 (LWP 5650)] [New Thread 0x7fffb782d710 (LWP 5652)] [New Thread 0x7fffb702c710 (LWP 5655)] [New Thread 0x7fffb802e710 (LWP 5656)] [New Thread 0x7fffb682b710 (LWP 5657)] [New Thread 0x7fffb602a710 (LWP 5658)] [New Thread 0x7fffb5829710 (LWP 5659)] [New Thread 0x7fffb5028710 (LWP 5660)] [Thread 0x7fffb682b710 (LWP 5657) exited] [Thread 0x7fffb5829710 (LWP 5659) exited] [Thread 0x7fffb602a710 (LWP 5658) exited] [Thread 0x7fffb802e710 (LWP 5656) exited] [Thread 0x7fffb5028710 (LWP 5660) exited] [Thread 0x7fffb702c710 (LWP 5655) exited] Error: Offset of directory Olympus, entry 0x0100 is out of bounds: Offset = 0x00003260; truncating the entry Error: Offset of directory Olympus, entry 0x0200 is out of bounds: Offset = 0x00001a44; truncating the entry Error: Offset of directory Olympus, entry 0x0204 is out of bounds: Offset = 0x00001a58; truncating the entry Error: Offset of directory Olympus, entry 0x0205 is out of bounds: Offset = 0x00001a60; truncating the entry Error: Offset of directory Olympus, entry 0x0206 is out of bounds: Offset = 0x00001a68; truncating the entry Error: Offset of directory Olympus, entry 0x0207 is out of bounds: Offset = 0x00001a74; truncating the entry Error: Offset of directory Olympus, entry 0x0209 is out of bounds: Offset = 0x00001a7a; truncating the entry Error: Offset of directory Olympus, entry 0x1011 is out of bounds: Offset = 0x00001aa4; truncating the entry Error: Offset of directory Olympus, entry 0x1012 is out of bounds: Offset = 0x00001ab6; truncating the entry Error: Offset of directory Olympus, entry 0x102b is out of bounds: Offset = 0x00001aca; truncating the entry Time elapsed: 4 ms Model: Time elapsed: 35 ms <unknown>: Fatal IO error 104 (Connection removed by partner) on X server :0.0. kdeinit4: Fatal IO error: client killed klauncher: Exiting on signal 15 <unknown>: Fatal IO error 11 (Resource temporarily unaccessible) on X server :0.0. +++++++++++++++++ In this case I was trying crop a scanned image and while defining the crop area, Digikam crashed, which it always does nowadays. So, I have to use Gimp to crop! What on earth does "directory Olympus" have to do with this? Am I being punished for using Olympus cameras? Is this a conspicary from Canikon? /Stefan Sound like a problem with your X server or with you KDE installation... It's not due to digiKam. As digiKam depend of KDE... Gilles Caulier Yes, yes! It was a problem with X. Or more correctly, a problem with the proprietary ATI drivers. After I deinstalled them, there were no more problems. Thank you for leading me in the right direction. So, I am no longer involved in this bug. Stefan Holmström |