Bug 229103 - krusader doesn't start with signal 11
Summary: krusader doesn't start with signal 11
Status: RESOLVED DUPLICATE of bug 191167
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-02 09:29 UTC by Maxim
Modified: 2010-06-30 03:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maxim 2010-03-02 09:29:35 UTC
Application: krusader (2.0.0 "Mars Pathfinder")
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.2
Operating System: Linux 2.6.30.10-105.2.4.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

-- Information about the crash:
Yesterday my Krusader worked fine. Then I've updated my system and today Krusader doesn't start with signal 11 

The crash can be reproduced every time.

 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#5  0x000000000044eeda in PanelManager::slotChangePanel (this=0x2e96110, p=0x0) at /usr/src/debug/krusader-2.0.0/krusader/panelmanager.cpp:71
#6  0x0000000000459e1a in KrusaderView::start (this=0x2da02a0, leftTabs=) at /usr/src/debug/krusader-2.0.0/krusader/krusaderview.cpp:142
#7  0x000000000046931d in Krusader::Krusader (this=0x7fff73089720, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/krusader.cpp:376
#8  0x0000000000456d34 in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/main.cpp:240
Warning: the current language does not match this frame.

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

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