Bug 214253 - krusader viewer (F3) segfaults on alt-F4
Summary: krusader viewer (F3) segfaults on alt-F4
Status: RESOLVED DUPLICATE of bug 198996
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-12 12:45 UTC by Erno Rigo
Modified: 2009-11-12 14:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
file used for testing (9.80 KB, text/xml)
2009-11-12 12:48 UTC, Erno Rigo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erno Rigo 2009-11-12 12:45:37 UTC
Application that crashed: krusader
Version of the application: 2.0.0 "Mars Pathfinder"
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I can fairly constantly reproduce this crash by opening a fresh krusader and open any .xml document for viewing (F3), then pressing alt-F4.

When I open other (non-.xml) files for viewing first, the crash does not occur, even for .xml files.


 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fd86800d654 in QObject::parent (this=0x1c042b0) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:243
#6  QWidget::parentWidget (this=0x1c042b0) at ../../include/QtGui/../../src/gui/kernel/qwidget.h:988
#7  QWidget::window (this=0x1c042b0) at kernel/qwidget.cpp:3882
#8  0x00007fd867fd2683 in QApplicationPrivate::dispatchEnterLeave (enter=<value optimized out>, leave=0x1c042b0) at kernel/qapplication.cpp:2527
#9  0x00007fd868037a66 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fffc1b96f70) at kernel/qapplication_x11.cpp:3546
#10 0x00007fd868060d0c in x11EventSourceDispatch (s=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#11 0x00007fd862e10bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#12 0x00007fd862e14588 in ?? () from /lib/libglib-2.0.so.0
#13 0x00007fd862e146b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#14 0x00007fd8676241a6 in QEventDispatcherGlib::processEvents (this=0x1305110, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#15 0x00007fd8680604be in QGuiEventDispatcherGlib::processEvents (this=0x1c042b0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#16 0x00007fd8675fa532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#17 0x00007fd8675fa904 in QEventLoop::exec (this=0x7fffc1b972a0, flags=) at kernel/qeventloop.cpp:201
#18 0x00007fd8675fcab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#19 0x000000000045bc78 in _start ()

This bug may be a duplicate of or related to bug 198996

Reported using DrKonqi
Comment 1 Erno Rigo 2009-11-12 12:48:10 UTC
Created attachment 38280 [details]
file used for testing
Comment 2 Dario Andres 2009-11-12 14:02:29 UTC
This is indeed probably related to bug 198996. Thanks

*** This bug has been marked as a duplicate of bug 198996 ***