Bug 230874

Summary: Krusader crashes with "Signal: 11 (Segmentation fault)" everytime it is launched
Product: [Applications] krusader Reporter: palash0791
Component: generalAssignee: Shie Erlich <manson>
Status: RESOLVED FIXED    
Severity: crash CC: palash0791
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description palash0791 2010-03-15 20:53:25 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.32.9-70.fc12.i686.PAE i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
Running Fedora 12. Krusader was working fine till I updated some (a bunch of) recommended crucial bug fixes and updated to the system. since then it keeps on crashing immediately after it is loaded. 
  I did try uninstalling and reinstalling it - but that does not change anything at all.

The crash can be reproduced every time.

 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#6  0x08085cc8 in PanelManager::slotChangePanel (this=0x99c8448, p=0x0) at /usr/src/debug/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x08091bc3 in KrusaderView::start (this=0x9849508, leftTabs=..., leftTypes=..., leftProps=..., leftActiveTab=1, rightTabs=..., rightTypes=..., rightProps=..., rightActiveTab=1, leftSideActive=
    false) at /usr/src/debug/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a27c3 in Krusader::Krusader (this=0xbfb49f0c, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x0808e829 in main (argc=5, argv=0xbfb4a6c4) at /usr/src/debug/krusader-2.0.0/krusader/main.cpp:240

This bug may be a duplicate of or related to bug 229103.

Possible duplicates by query: bug 229103.

Reported using DrKonqi
Comment 1 palash0791 2010-03-15 22:59:02 UTC
This has been resolved in the following way.

1. I switched to another user login. Krusader was working OK for the other user login. This meant that Krusader itself was ok, the problem was with some configuration file(s) of the main user.

2. Renamed the krusaderrc file in .kde/share/config to something else and re-launched Krusader. It went through the first-time-launch process and started working ok.

3. Did a comparision between the two files - there were quite a lot of differences, but didn't find anything that could point to the issue.