Bug 222023

Summary: krusader always crash when I start it. I have changed the computer theme and the fonts and I have changed features on compiz. After this krusader crashes always when I start it
Product: [Applications] krusader Reporter: Paolo <nennap>
Component: generalAssignee: Shie Erlich <manson>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Paolo 2010-01-10 08:33:39 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-17-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Until yesterday krusader run very well, then I have changed compiz features, themes and system fonts and I have changed something about the default function keys on the gtk libraries. I have changed also a lot of krusader settings and it continue to run.
This morning I have switched on my computer and krusader crashes all the time.

 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#6  0x0808aa88 in PanelManager::slotChangePanel (this=0x8badac0, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x08096931 in KrusaderView::start (this=0x8ba55c0, leftTabs=..., leftTypes=..., leftProps=..., leftActiveTab=1, rightTabs=..., rightTypes=..., rightProps=..., rightActiveTab=0, 
    leftSideActive=true) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:141
#8  0x080a74e3 in Krusader (this=0xbf949b8c, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x080935d5 in main (argc=5, argv=0xbf94a344) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-10 15:10:41 UTC
This is being tracked at bug 191167. (check the bug report as it seems it has some workarounds) Thanks

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