Bug 356416 - Krecipes crashed on import of recipes from Meal Master Cookbook
Summary: Krecipes crashed on import of recipes from Meal Master Cookbook
Status: RESOLVED WORKSFORME
Alias: None
Product: krecipes
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-12-09 10:01 UTC by Vit Pelcak
Modified: 2018-12-01 03:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
recipes database (900.38 KB, application/x-xz)
2015-12-09 10:03 UTC, Vit Pelcak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vit Pelcak 2015-12-09 10:01:14 UTC
Application: krecipes (2.0.0)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20151201) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I just tried to import text database of recipes from Meal Master.

-- Backtrace:
Application: Krecipes (krecipes), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd7ebc86900 (LWP 10544))]

Thread 2 (Thread 0x7fd7cee24700 (LWP 17842)):
#0  0x00007fd7e436120d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x00007fd7e0b5a264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7fd7c8003410, timeout=<optimized out>, context=0x7fd7c80009a0) at gmain.c:4135
#2  0x00007fd7e0b5a264 in g_main_context_iterate (context=context@entry=0x7fd7c80009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835
#3  0x00007fd7e0b5a36c in g_main_context_iteration (context=0x7fd7c80009a0, may_block=may_block@entry=1) at gmain.c:3901
#4  0x00007fd7e5b2726e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fd7c80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x00007fd7e5af73e1 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fd7cee23ca0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fd7e5af76f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fd7cee23ca0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007fd7e59f0a59 in QThread::exec() (this=this@entry=0xe11510) at thread/qthread.cpp:538
#8  0x00007fd7e5ad84c3 in QInotifyFileSystemWatcherEngine::run() (this=0xe11510) at io/qfilesystemwatcher_inotify.cpp:265
#9  0x00007fd7e59f323c in QThreadPrivate::start(void*) (arg=0xe11510) at thread/qthread_unix.cpp:352
#10 0x00007fd7e25754a4 in start_thread (arg=0x7fd7cee24700) at pthread_create.c:334
#11 0x00007fd7e4369b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fd7ebc86900 (LWP 10544)):
[KCrash Handler]
#6  0x00007fd7e42b4d38 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007fd7e42b618a in __GI_abort () at abort.c:78
#8  0x00007fd7e49b9b3d in __gnu_cxx::__verbose_terminate_handler() () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007fd7e49b7ba6 in __cxxabiv1::__terminate(void (*)()) (handler=<optimized out>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47
#10 0x00007fd7e49b7bf1 in std::terminate() () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57
#11 0x00007fd7e49b7e56 in __cxxabiv1::__cxa_rethrow() () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:125
#12 0x00007fd7e5af7914 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffde7dbc9b0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007fd7e5afcef9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1227
#14 0x0000000000437f97 in main ()

Possible duplicates by query: bug 353304, bug 352495, bug 352280, bug 351097, bug 350831.

Reported using DrKonqi
Comment 1 Vit Pelcak 2015-12-09 10:03:19 UTC
Created attachment 95945 [details]
recipes database
Comment 2 Andrew Crouthamel 2018-11-01 13:48:06 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-16 11:36:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-12-01 03:50:48 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!