If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)

Sure. Thanks for the tip. Always wandered, how to obtain a stacktrace.

===
Thread 1 (Thread 0xb53ed700 (LWP 8033)):
#0  0x0808aaf8 in PanelManager::slotChangePanel (this=0x9840208, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#1  0x08095f11 in KrusaderView::start (this=0x97e1dd8, leftTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd3698c}, d = 0xbfd3698c}}, <No data fields>}, leftTypes=
        {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd36990}, d = 0xbfd36990}}, leftProps=
        {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd36994}, d = 0xbfd36994}}, leftActiveTab=1, rightTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd36998}, d = 0xbfd36998}}, <No data fields>}, rightTypes=
        {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd3699c}, d = 0xbfd3699c}}, rightProps=
        {{p = {static shared_null = {ref = {_q_value = 10836}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfd369a0}, d = 0xbfd369a0}}, rightActiveTab=0, leftSideActive=false)
    at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:141
#2  0x080a6514 in Krusader (this=0xbfd36b24) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#3  0x08092d9a in main (argc=3, argv=0xbfd36ae0) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240
===

same
Krusader crashes SIGSEGV 11 bugreport:
Ubuntu jaunty jackalope

Application: Krusader (krusader), signal SIGSEGV

Thread 1 (Thread 0xb5413700 (LWP 5215)):
[KCrash Handler]
#6  0x0808aaf8 in PanelManager::slotChangePanel (this=0xa04cfd8, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x08095f26 in KrusaderView::start (this=0x9eb7320, leftTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd3c}, d = 0xbfb5fd3c}}, <No data fields>}, leftTypes={{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd40}, d = 0xbfb5fd40}}, leftProps=
        {{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd44}, d = 0xbfb5fd44}}, leftActiveTab=2, rightTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd48}, d = 0xbfb5fd48}}, <No data fields>}, rightTypes={{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd4c}, d = 0xbfb5fd4c}}, rightProps=
        {{p = {static shared_null = {ref = {_q_value = 21698}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbfb5fd50}, d = 0xbfb5fd50}}, rightActiveTab=2, leftSideActive=false)
    at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a6514 in Krusader (this=0xbfb5fed4) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x08092d9a in main (argc=3, argv=0xbfb5fe90) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

Same here. Over Debian Sid package.

As already noticed, removing the configuration folder ~/.kde/share/apps/krusader is not enough. 
But however krusader works properly if started in superuser mode.

Hope it helps.


======

Application: Krusader (krusader), signal SIGSEGV

Thread 1 (Thread 0xb536c710 (LWP 29712)):
[KCrash Handler]
#6  0x0808a7e8 in PanelManager::slotChangePanel (this=0x8866730, p=0x0) at /home/mark/src/kde-extras/build-area/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x08095bd6 in KrusaderView::start (this=0x86f4b80, leftTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe488c}, d = 0xbffe488c}}, <No data fields>}, leftTypes={{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe4890}, d = 0xbffe4890}}, leftProps=
        {{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe4894}, d = 0xbffe4894}}, leftActiveTab=0, rightTabs=
          {<QList<QString>> = {{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe4898}, d = 0xbffe4898}}, <No data fields>}, rightTypes={{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe489c}, d = 0xbffe489c}}, rightProps=
        {{p = {static shared_null = {ref = {_q_value = 10728}, alloc = 0, begin = 0, end = 0, sharable = 1, array = {0x0}}, d = 0xbffe48a0}, d = 0xbffe48a0}}, rightActiveTab=5, leftSideActive=true)
    at /home/mark/src/kde-extras/build-area/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a61c4 in Krusader (this=0xbffe4a18) at /home/mark/src/kde-extras/build-area/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x08092a69 in main (argc=3, argv=0xbffe49e0) at /home/mark/src/kde-extras/build-area/krusader-2.0.0/krusader/main.cpp:240

*** Bug 193379 has been marked as a duplicate of this bug. ***

I've got the same problem:

Anwendung: Krusader (krusader), Signal SIGSEGV
[Current thread is 1 (Thread 0xb59b16d0 (LWP 15203))]

Thread 1 (Thread 0xb59b16d0 (LWP 15203)):
[KCrash Handler]
#6  0x08085ee7 in _start ()
____________________

My configuration:
Mandriva 9.1 powerpack, KDE 4.2.2, Krusaderf 2.0.0
krusader works properly if started in superuser mode.

removing the configuration folder
~/.kde/share/apps/krusader doesn't solves the problem.

system: Debian testing
kde: 4.2.2
krusader: 2.0.0 

Got the same problem several times. In my case, the source of it is bad [Startup] section in krusader configuration file
~/.kde/share/config/krusaderrc

Somehow, from time to time, active tab index became "out of range", as in example below for left panel: active tab index = 2, it mean third left active panel, but only two exists in "Left Tab Bar" 

[Startup]
Left Active Tab=2
Left Panel Popup=0
Left Side Is Active=false
Left Tab Bar[$e]=/mnt,/opt
Left Tab Bar Props=0,0,0
Left Tab Bar Types=0,0,0
Right Active Tab=0
Right Panel Popup=0
Right Tab Bar[$e]=/ext/tmp
Right Tab Bar Props=0,0,0
Right Tab Bar Types=0,0,0
Vertical Mode=false

Workaround in this case obviously is this: manually edit configuration file and set wrong active tab index to zero.

And imho krusader should not crash, no matter whatever data contained in config.

*** Bug 202237 has been marked as a duplicate of this bug. ***

*** Bug 203204 has been marked as a duplicate of this bug. ***

*** Bug 204456 has been marked as a duplicate of this bug. ***

*** Bug 205716 has been marked as a duplicate of this bug. ***

*** Bug 206234 has been marked as a duplicate of this bug. ***

In my case, krusader could be made functional again by calling it with 'krusader -left /home/'

*** Bug 207428 has been marked as a duplicate of this bug. ***

I've started it up again using the following command, after which it behaved normaly again:
'krusader -left /home/ -right /home/'

*** Bug 213126 has been marked as a duplicate of this bug. ***

I confirm this bug, and the workaround to edit .krusaderrc

*** Bug 217839 has been marked as a duplicate of this bug. ***

*** Bug 218327 has been marked as a duplicate of this bug. ***

*** Bug 218300 has been marked as a duplicate of this bug. ***

*** Bug 219474 has been marked as a duplicate of this bug. ***

same for me (from gnome). it started to behave weird in ubuntu 9.04 around october (i always auto-update to latest packages). upgrade to 9.10 did not help.

thanks for hint with -left -right options.

From bug 222023:
--
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.

*** Bug 222023 has been marked as a duplicate of this bug. ***

Confirmed on Gentoo (kde 4.4.0, krusader 2.0.0).

Also had problem with:
Right Active Tab=3
while there were only 3 tabs in right panel

Problem occurred when i quickly closed two instances of krusader one of which had 4 tabs in right panel, causing indefinite state in krusaderrc

- you need to develop or fix locking mechanism when multiple instances of krusader wants to write to configuration file

- you should be able to ignore bad values for 'Right Active Tab' and possibly other not-critical config parameters

Confirmed on Gentoo with kde-4.4.4 and krusader-2.0.0-r1
Maybe as a workaround a quick check in the config-loading part could be added to see whether the stored left/right active tab is actually existing, or else reset it to 0?

*** Bug 238370 has been marked as a duplicate of this bug. ***

*** Bug 237937 has been marked as a duplicate of this bug. ***

*** Bug 236664 has been marked as a duplicate of this bug. ***

*** Bug 236023 has been marked as a duplicate of this bug. ***

*** Bug 230214 has been marked as a duplicate of this bug. ***

*** Bug 229103 has been marked as a duplicate of this bug. ***

Krusader doesn't crash with a wrongly saved tab number on 2.2.0-beta1 anymore. Please try the new version.

The update to 2.2.0-beta1 fixes it for me, thanks :)

*** Bug 245327 has been marked as a duplicate of this bug. ***

*** Bug 246420 has been marked as a duplicate of this bug. ***

*** Bug 246449 has been marked as a duplicate of this bug. ***

Confirmed that this is fixed in 2.2.0 beta1

*** Bug 248964 has been marked as a duplicate of this bug. ***

*** Bug 244826 has been marked as a duplicate of this bug. ***

*** Bug 243457 has been marked as a duplicate of this bug. ***

Created attachment 51955 [details]
New crash information added by DrKonqi

Removing following lines from krusaderrc resolved this error.

Left Active Tab=1
Left/Right Tab Bar[$e].....

*** Bug 255255 has been marked as a duplicate of this bug. ***

*** Bug 258000 has been marked as a duplicate of this bug. ***

*** Bug 265059 has been marked as a duplicate of this bug. ***

*** Bug 266592 has been marked as a duplicate of this bug. ***

confirmed to be resolved in 2.2.0

Created attachment 58008 [details]
New crash information added by DrKonqi

Krusader is closed with an error at startup. An error occurs when the last run of the leave in one of the windows show the contents of removable disk usb and close krusader, this is not unmounting removable disk usb. Tried to remove the path to the last opened directory and manually edit the configuration file "~ / .kde / share / config / krusaderrc" in the section "[Startup]" parameter of "Left Tab Bar" or "Right Tab Bar". Placed manually in the parameter "Right Tab Bar [$ e]" value "/, $ HOME". But it did not help and the next time the error again.

Created attachment 60534 [details]
New crash information added by DrKonqi

krusader (2.0.0 "Mars Pathfinder") on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.4

It crashes in a regular user mode but not as Sysadmin-mode.

-- Backtrace (Reduced):
#6  0x0000000000453b3a in PanelManager::slotChangePanel (this=0xbb3200, p=0x0) at /usr/src/debug/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x000000000045e9ff in KrusaderView::start (this=<optimized out>, leftTabs=<optimized out>, leftTypes=..., leftProps=<optimized out>, leftActiveTab=0, rightTabs=<optimized out>, rightTypes=..., rightProps=..., rightActiveTab=2, leftSideActive=true) at /usr/src/debug/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x000000000046ca85 in Krusader::Krusader (this=0x7fff70d7ec90, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x000000000045bb6e in main (argc=1893200336, argv=<optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/main.cpp:240

Created attachment 61135 [details]
New crash information added by DrKonqi

krusader (2.0.0 "Mars Pathfinder") on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

- What I was doing when the application crashed:

Just Krudader startup, a previously opened flash disk was removed.

-- Backtrace (Reduced):
#6  0x0000000000453b3a in PanelManager::slotChangePanel (this=0xa32c60, p=0x0) at /usr/src/debug/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x000000000045e9ff in KrusaderView::start (this=<value optimized out>, leftTabs=<value optimized out>, leftTypes=..., leftProps=<value optimized out>, leftActiveTab=2, rightTabs=<value optimized out>, rightTypes=..., rightProps=..., rightActiveTab=2, leftSideActive=false) at /usr/src/debug/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x000000000046ca85 in Krusader::Krusader (this=0x7fff5c013c90, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x000000000045bb6e in main (argc=1543586256, argv=<value optimized out>) at /usr/src/debug/krusader-2.0.0/krusader/main.cpp:240

*** Bug 279899 has been marked as a duplicate of this bug. ***

Hi,
it's seems that the bug is still there :
after a crash of my computer (freeze after unmonting an external HDD..) I manualy restarted it (by a reset). Then Krusader didn't wanted to start!
I've edited the file krusaderrc : active tab index=2, but only 2 exists!
I added a tab, and it's now ok.

So it means that the bug is still here, isn't it?

Precision : I'm on Mageia (not ubuntu)

Jean-Michel,
What Krusader version do you use?

Hi,
I use : "Version 2.0.0 "Mars Pathfinder"
Utilisation de la plate-forme de développement de KDE 4.6.5 (4.6.5)"

On 08/30/2011 10:41 PM, Steffen Schaumburg wrote:
> https://bugs.kde.org/show_bug.cgi?id=191167
>
>
>
>
>
> --- Comment #54 from Steffen Schaumburg<steffen sycamoretest info>   2011-08-30 14:41:10 ---
> Jean-Michel,
> What Krusader version do you use?
>
Thanks for the response,

Krusader ver 1:2.0.0-1ubuntu3         running in a Kubuntu environment.

Jean-Michel, Kirk,
You will need to update to Krusader-2.2.0-beta1 or higher. Since I don't use Mageira or (K)Ubuntu I can't tell you what the best way to achieve this is.

Sorry, I haven't seen that the fix was in the beta version, so I've haven't seen that my version was older (but latest stable) than the fix!
So I've have installed krusader-2.2.0-beta1 (with tarball, since it's not in my reposetory). Then I (wrong) edited the file krusaderrc in order to provoque the crash.
Results : It's ok!!

thanks (I think I will install the version krusader-2.4.0-beta1 now :-) )

Thank you Steffen.

I'll install

Krusader-2.2.0-beta1  or higher.

Let's assume this bug is solved.

If I have similar issues with the beta version, I'll resend with the same bug number.

have a great week ahead,
Kirk


On 09/03/2011 01:04 AM, Steffen Schaumburg wrote:
> https://bugs.kde.org/show_bug.cgi?id=191167
>
>
>
>
>
> --- Comment #57 from Steffen Schaumburg<steffen sycamoretest info>   2011-09-02 17:04:33 ---
> Jean-Michel, Kirk,
> You will need to update to Krusader-2.2.0-beta1 or higher. Since I don't use
> Mageira or (K)Ubuntu I can't tell you what the best way to achieve this is.
>

*** Bug 287741 has been marked as a duplicate of this bug. ***

Created attachment 67024 [details]
New crash information added by DrKonqi

I think Krusader began to crash after I installed an nfs-kernel-server (or something having to do with setting up my an nfs server from the same computer).  Now it crashes every time on its startup

*** Bug 290567 has been marked as a duplicate of this bug. ***

On 01/07/2012 12:54 AM, Christoph Feck wrote:
> https://bugs.kde.org/show_bug.cgi?id=191167
>
>
> Christoph Feck<christoph@maxiom.de>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |pletisan@gmail.com
>
>
>
>
> --- Comment #62 from Christoph Feck<christoph maxiom de>   2012-01-06 16:54:22 ---
> *** Bug 290567 has been marked as a duplicate of this bug. ***
>
I upgraded to Krusader 2.4 and its working fine. So, my problem is solved.

Thanks!!

Kirk

*** Bug 293423 has been marked as a duplicate of this bug. ***

*** Bug 295979 has been marked as a duplicate of this bug. ***