@ Edward One of the qiv developers has answered to the e-mail notification.
Could you please answer his furhter question directly per mail. I want to get out as a communication bridge(not really needed one). He wrote: Hi. I'm one of the QIV developers. Unfortunately I could not reproduce it here, but my photo archive is only a tenth of his size. So if there is way for me to reproduce the issue it would be much easier for me to help. There are some issues in the report, which could perhaps be clarified. Was qiv already up and showing a picture? Or did he fire up qiv and went out while it was scanning the mentioned 60000 pictures. A SIGABRT could also be an indication for memory problems. Is a dmesg output available, to check if qiv was not taken out by the kernels OOM-killer? Also gdk_event_dispatch() is never directly called from qiv. It is part of the gdk_main_loop(), which makes it IMHO not so likely that qiv crash there. Cheers, Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1090221 Title: qiv crashed with SIGABRT in gdk_event_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qiv/+bug/1090221/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
