[Digikam-devel] [digikam] [Bug 314385] New: Digikam crashes at startup: "Creating pipes for GWakeup: Too many open files"

[Luke]

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

            Bug ID: 314385
           Summary: Digikam crashes at startup: "Creating pipes for
                    GWakeup: Too many open files"
    Classification: Unclassified
           Product: digikam
           Version: 2.8.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: digikam-devel at kde.org
          Reporter: lcampagn at email.unc.edu

When I start digikam, it immediately crashes with the following errors:

    QFileSystemWatcher: failed to add paths: /home/luke/Pictures/2001
    [ .. snip: many more similar errors .. ]
    QFileSystemWatcher: failed to add paths: /home/luke/Pictures/2012/12
    digikam(19492) KIO::SlavePrivate::SlavePrivate: Connection server not
listening, could not connect

    (digikam:19492): GLib-ERROR **: Creating pipes for GWakeup: Too many open
files

    Trace/breakpoint trap (core dumped)

My collection is about 32k files and 950 directories.
I started seeing this error upon copying my Pictures folder (including
digikam4.db and all photos) to a new machine on which I had not previously run
digikam (and I have the same problem even after deleting
.kde/share/apps/digikamrc).

I can work around this by running 'ulimit -n 2048' before running digikam, but
probably digikam should check or modify its own limits instead of crashing. 
I'll also mention that, after increasing the open file limit, digikam still
crashes, but for a seemingly unrelated reason.

Reproducible: Always

Steps to Reproduce:
1. Start fresh: empty ~/Pictures, remove .kde/share/config/digikamrc
2. Create ~/Pictures with 1000 subdirs:
     for i in {1..1000}; do mkdir ~/Pictures/$i; done
3. Start digikam
Actual Results:  
Crashes with error similar to above.

-- 
You are receiving this mail because:
You are the assignee for the bug.