https://bugs.kde.org/show_bug.cgi?id=455031
--- Comment #6 from battyanyi.d...@gmail.com --- (In reply to battyanyi.dani from comment #5) > I've been playing around with it for a little bit, and as it turns out if i > delete/rename all of these: > > ~/.local/share/digikam/db_misc/mysql.socket > ~/Pictures/.mysql.digikam/ > ~/.local/share/digikam/mysql.conf > ~/.config/digikamrc, > > it succeeds in creating the database, but crashes when clicking "configure > digikam" . > > [warn] epoll_wait: Bad file descriptor > pa_write() failed while trying to wake up the mainloop: Bad file descriptor > pa_write() failed while trying to wake up the mainloop: Bad file descriptor > Invalid write to eventfd: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > [warn] epoll_wait: Bad file descriptor > Code should not be reached at ../pulseaudio/src/pulsecore/fdsem.c:188, > function pa_fdsem_post(). Aborting. > [warn] epoll_wait: Bad file descriptor > > Thread 36 "digikam" received signal SIGABRT, Aborted. > [Switching to Thread 0x7fff6d7fa640 (LWP 1312231)] > 0x00007ffff4a8e36c in ?? () from /usr/lib/libc.so.6 > > After that, on the second start digikam works fine, but on the third start > it runs into the database problem. If the program exits correctly it fails > to load the database after restarting it. "After that, on the second start digikam works fine, but on the third start it runs into the database problem. If the program exits correctly it fails to load the database after restarting it." This last part is resolved by not deleting the "~/.local/share/digikam/db_misc/mysql.socket" file, only the rest of the ones above. Currently testing whether this resolves the issue completely. -- You are receiving this mail because: You are watching all bug changes.
