Summary: | Crash after printing | ||
---|---|---|---|
Product: | [Applications] krecipes | Reporter: | Anthony DeRobertis <anthony> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid, colleen.beamer, endymion+kde, fstjohn, joe, johnboisclair, kungpo, marcel.kyas, mcewan.john, mkporco, mouncleg, rdgreenlaw, ryantcragun, twdickel |
Priority: | NOR | ||
Version: | 2.0-beta2 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi screenshot of what the menu changed to after dwnlodin recipes New crash information added by DrKonqi |
Description
Anthony DeRobertis
2012-09-21 11:24:54 UTC
*** Bug 310420 has been marked as a duplicate of this bug. *** *** Bug 311374 has been marked as a duplicate of this bug. *** *** Bug 312599 has been marked as a duplicate of this bug. *** Created attachment 79067 [details]
New crash information added by DrKonqi
krecipes (2.0-beta2) on KDE Platform 4.10.2 using Qt 4.8.4
- What I was doing when the application crashed:
I printed a recipe. Printing was successful, but krecipes crashed.
-- Backtrace (Reduced):
#6 data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:135
[...]
#10 0x00000037c0d5fc42 in QWebFrame::loadFinished (this=<optimized out>, _t1=true) at ./moc_qwebframe.cpp:238
#11 0x00000037c0d9d778 in WebCore::FrameLoaderClientQt::dispatchDidFinishLoad (this=0x3348230) at WebCoreSupport/FrameLoaderClientQt.cpp:527
#12 0x00000037c10ec2a6 in WebCore::FrameLoader::checkLoadCompleteForThisFrame (this=0x7fcbb59b4478) at loader/FrameLoader.cpp:2530
#13 0x00000037c10eafb3 in WebCore::FrameLoader::recursiveCheckLoadComplete (this=0x7fcbb59b4478) at loader/FrameLoader.cpp:2641
Created attachment 79491 [details]
New crash information added by DrKonqi
krecipes (2.0-beta2) on KDE Platform 4.9.5 using Qt 4.8.3
- What I was doing when the application crashed:
I printed a recipe to a PDF. As soon as I hit "print," the program crashed. The PDF file was created, but it does this every single time I print. I would really love for this bug to be fixed. I love KRecipes and use it all the time. This is the only major problem I've found with it.
-- Backtrace (Reduced):
#5 data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#9 0x00007f0600f3d642 in QWebFrame::loadFinished (this=<optimized out>, _t1=true) at ./moc_qwebframe.cpp:239
#10 0x00007f0600f7a935 in WebCore::FrameLoaderClientQt::dispatchDidFinishLoad (this=0x2417780) at WebCoreSupport/FrameLoaderClientQt.cpp:527
#11 0x00007f06012bb34e in WebCore::FrameLoader::checkLoadCompleteForThisFrame (this=this@entry=0x7f05e8c9b478) at loader/FrameLoader.cpp:2530
#12 0x00007f06012bb4f3 in WebCore::FrameLoader::recursiveCheckLoadComplete (this=0x7f05e8c9b478) at loader/FrameLoader.cpp:2641
I am having this issue too - consistently. Created attachment 84284 [details]
New crash information added by DrKonqi
krecipes (2.0-beta2) on KDE Platform 4.12.0 using Qt 4.8.5
Just printing from the app and then crashed !
-- Backtrace (Reduced):
#6 data (this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#10 0x00007fe739c02ffe in QWebFrame::loadFinished (this=<optimized out>, _t1=true) at .moc/release-shared/moc_qwebframe.cpp:238
#11 0x00007fe739c2a815 in WebCore::FrameLoaderClientQt::emitLoadFinished (this=this@entry=0x3b652d0, ok=ok@entry=true) at WebCoreSupport/FrameLoaderClientQt.cpp:1700
#12 0x00007fe739c2a89a in WebCore::FrameLoaderClientQt::dispatchDidFinishLoad (this=0x3b652d0) at WebCoreSupport/FrameLoaderClientQt.cpp:527
#13 0x00007fe739dfd003 in WebCore::FrameLoader::checkLoadCompleteForThisFrame (this=this@entry=0x7fe723bd0478) at loader/FrameLoader.cpp:2530
*** Bug 328793 has been marked as a duplicate of this bug. *** Created attachment 87447 [details]
New crash information added by DrKonqi
krecipes (2.0-beta2) on KDE Platform 4.13.2 using Qt 4.8.6
- What I was doing when the application crashed:
Previewing a recipe in the print previewer, when ever I manually close the print preiview screen or it closes automatically after clicking print krecipes crashes.
-- Backtrace (Reduced):
#5 data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#9 0x00007f32841a5c52 in QWebFrame::loadFinished(bool) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#10 0x00007f32841e8ab8 in WebCore::FrameLoaderClientQt::dispatchDidFinishLoad() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#11 0x00007f3284775d76 in WebCore::FrameLoader::checkLoadCompleteForThisFrame() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#12 0x00007f3284774934 in WebCore::FrameLoader::checkLoadComplete() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
*** Bug 340546 has been marked as a duplicate of this bug. *** Created attachment 90254 [details]
screenshot of what the menu changed to after dwnlodin recipes
the menu changed preferences was taken away or settings was taken away and the words no text took their place
Kungpo, how is this related to "Crash after printing"? ---- Albert Astals Cid <aacid@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=307150 > > Albert Astals Cid <aacid@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |aacid@kde.org > > --- Comment #12 from Albert Astals Cid <aacid@kde.org> --- > Kungpo, how is this related to "Crash after printing"? > > -- > You are receiving this mail because: > You are on the CC list for the bug. it isnt its a menu problem the menu changed on me when i started importing recipes so i cant get to preferences or settings Why are you reporting a menu problem on a bug called "Crash after printing"? ---- Albert Astals Cid <aacid@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=307150 > > --- Comment #14 from Albert Astals Cid <aacid@kde.org> --- > Why are you reporting a menu problem on a bug called "Crash after printing"? > > -- > You are receiving this mail because: > You are on the CC list for the bug. i wasnt the damn program reported that in the bug report i was trying to report the problem with the menu changing on me ---- Albert Astals Cid <aacid@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=307150 > > --- Comment #14 from Albert Astals Cid <aacid@kde.org> --- > Why are you reporting a menu problem on a bug called "Crash after printing"? > > -- > You are receiving this mail because: > You are on the CC list for the bug. the menu changed while importing recipes thats all i know This bug has been fixed in KRecipes 2.0 released 28 November 2014, please tell your distribution to update to such version or newer. (In reply to Albert Astals Cid from comment #17) > This bug has been fixed in KRecipes 2.0 released 28 November 2014, please > tell your distribution to update to such version or newer. I just confirmed that KRecipes 2.0 does not crash when you print a recipe. Thank you!!!! Created attachment 98688 [details]
New crash information added by DrKonqi
krecipes (2.0-beta2) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
Displayed recipe. Clicked print icon. Preview was displayed. Selected print. Recipe printed successfully and application crashed simultaneously.
-- Backtrace (Reduced):
#5 data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
[...]
#9 0x00007ffba0ba8c52 in QWebFrame::loadFinished(bool) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#10 0x00007ffba0bebab8 in WebCore::FrameLoaderClientQt::dispatchDidFinishLoad() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#11 0x00007ffba1178d76 in WebCore::FrameLoader::checkLoadCompleteForThisFrame() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#12 0x00007ffba1177934 in WebCore::FrameLoader::checkLoadComplete() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
*** Bug 374405 has been marked as a duplicate of this bug. *** Since this is still occurring, should it be marked fixed? See comment #17. |