Bug 237937 - Krusader closed unexpectedly
Summary: Krusader closed unexpectedly
Status: RESOLVED DUPLICATE of bug 191167
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-17 16:13 UTC by Unknown
Modified: 2010-06-30 03:00 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2010-05-17 16:13:11 UTC
Application: krusader (2.0.0 "Mars Pathfinder")
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
When starting Krusader, an error message window is displayed. Message is: We are sorry, Krusader closed unexpectedly. 
Details: Executable: krusader PID: 1978 Signal: 11 (Segmentational fault)

The crash can be reproduced every time.

 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#6  0x0808ac88 in PanelManager::slotChangePanel (this=0x91b8a78, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x080970ed in KrusaderView::start (this=0x9012178, leftTabs=..., leftTypes=..., leftProps=..., leftActiveTab=1, rightTabs=..., rightTypes=..., rightProps=..., rightActiveTab=3, 
    leftSideActive=false) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a7e54 in Krusader (this=0xbff0c4b8, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x08093d3c in main (argc=5, argv=0xbff0cc74) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

Possible duplicates by query: bug 236664, bug 236023, bug 230874, bug 230214, bug 229103.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-06-30 03:00:34 UTC

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