| Summary: | Crash on start-up due to user resource limitations set in PAM configuration | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Gerrit Holl <gerrit.holl> |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | grave | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 5.1.0 | |
| Sentry Crash Report: | |||
| Attachments: | output of 'strace -o -ff' in a tar.gz (22 strace files) | ||
|
Description
Gerrit Holl
2014-06-08 02:36:04 UTC
I upgraded to 3.5.0. The crash persists and is reproducable, but the error messages are not always the same: $ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable terminate called recursively KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Error: Could not determine display. KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly terminate called recursively Unable to start Dr. Konqi Not forwarding the crash to Apport. $ digikam Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is still in use, all queries will cease to work. terminate called recursively terminate called recursively KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Error: Could not determine display. KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly KCrash: Application 'digikam' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit Error: Could not determine display. KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly terminate called recursively Unable to start Dr. Konqi terminate called after throwing an instance of 'St9bad_alloc' terminate called recursively terminate called recursively QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable QThread::start: Thread creation error: Resource temporarily unavailable digikam: Fatal IO error 9 (Bad file descriptor) on X server :0.0. what(): std::bad_alloc terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively terminate called recursively Not forwarding the crash to Apport. Created attachment 87066 [details]
output of 'strace -o -ff' in a tar.gz (22 strace files)
output of 'strace -o -ff digikam' in a tar.gz (22 strace files).
This is a fully clean install (removed apps/digikam and config/digikamrc, as well as thumbs.db and digikam4.db).
Strace is not informative about the problem. Please run digiKam in GDB as explained here and give us a suitable backtrace to hack... http://www.digikam.org/contrib Gilles Caulier Oops, I didn't notice the gdb comment until now. However, I have discovered a very valuable piece of additional information. The crash happens if I set a too low ulimit. With ulimit -v 1500000, it crashes. With ulimit -v 4000000, it does not crash. Please let me know if you are able to reproduce the bug with this information. Will I need to compile digikam from source for gdb to provide useful information? Didi you try to get a suitable backtrace with GDB, installing digiKam debug package ? Gilles Caulier New digiKam 4.11.0 is available with official PKG installer for OSX. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. Gilles Caulier On 20 August 2015 at 07:50, Gilles Caulier <caulier.gilles@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=335937 > > --- Comment #7 from Gilles Caulier <caulier.gilles@gmail.com> --- > digiKam 4.12.0 is out : > > https://www.digikam.org/node/741 > > We need a fresh feedback using this release please... Ok, I will have a look later. Gerrit. This problem is not reproducible with last 5.0.0. I close this file now. Don't hesitate to re-open it if necessary. Gilles Caulier |