Summary: | Krusader crash during F3-viewing some files | ||
---|---|---|---|
Product: | [Applications] krusader | Reporter: | Andrei ILIE <andrei.ilie> |
Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bersik87, jan_lepper, klebezettel, krusader-bugs-null |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Andrei ILIE
2012-02-25 17:17:47 UTC
1) Can you reproduce that every time you're trying? 2) Does this happen with all files html and txt files or only some certain files? Can you provide the files? 3) You've selected two files and pressed F3 for viewing, correct? 1. I can't reproduce this bug anymore, as I lost the files that triggered it... 2. Tried moments ago to F3 thow random files (one txt and one html); couldn't reproduce the bug. 3. Correct. Maybe the backtrace has any leads ? Created attachment 72130 [details]
New crash information added by DrKonqi
krusader (2.4.0-beta1 "Migration") on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
viewing html file (f3)
after alt+f4 press to close viewer krusader crashed
-- Backtrace (Reduced):
#7 QApplication::x11ProcessEvent (this=0xbfd36818, event=0xbfd362cc) at kernel/qapplication_x11.cpp:3721
#8 0x068a9eac in x11EventSourceDispatch (s=0x9d0b200, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
[...]
#12 0x0321f887 in QEventDispatcherGlib::processEvents (this=0x9cdeed8, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#13 0x068a9aaa in QGuiEventDispatcherGlib::processEvents (this=0x9cdeed8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x031eb50d in QEventLoop::processEvents (this=0xbfd365c4, flags=...) at kernel/qeventloop.cpp:149
This is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=198996. Feel free to reopen if the bug occurs again. *** This bug has been marked as a duplicate of bug 198996 *** |