krusader crashes on startup

Bug #426827 reported by smidl
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
krusader (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Karmic by Jan Včelák

Bug Description

Binary package hint: krusader

Krusader-dbg 1:2.0.0-1ubuntu2(amd64) crashes on startup with the following backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x0000000000453cda in PanelManager::slotChangePanel (this=0xc34ca0, p=0x0)
    at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
71 in /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp

(gdb) bt

#0 0x0000000000453cda in PanelManager::slotChangePanel (this=0xc34ca0, p=0x0)
    at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#1 0x000000000045eb7a in KrusaderView::start (this=0xb2a7c0, leftTabs=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
)
    at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:141
#2 0x000000000046e03d in Krusader (this=0x7fffffffcf50,
    __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>)
    at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#3 0x000000000045baea in main (argc=<value optimized out>,
    argv=<value optimized out>)
    at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

Revision history for this message
Jan Včelák (jvcelak) wrote :

I can confirm this problem. Krusader crashes immediately after startup. I also tried deleting krusader's settings but it did not help.

Distributor ID: Ubuntu
Description: Ubuntu karmic (development branch)
Release: 9.10
Codename: karmic

krusader 1:2.0.0-1ubuntu2

Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#5 0x0000000000453cda in PanelManager::slotChangePanel (this=0x104ca40, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#6 0x000000000045eb8a in KrusaderView::start (this=0xf47e10, leftTabs=) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:142
#7 0x000000000046e03d in Krusader (this=0x7fffb7f3a640, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#8 0x000000000045baea in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

Changed in krusader (Ubuntu):
status: New → Confirmed
Revision history for this message
Jan Včelák (jvcelak) wrote :

I removed ~/.kde/share/config/krusaderrc and segfaults are gone. But I think this should not happen after upgrade. Unfortunatelly I don't have backup of that krusaderrc to reproduce the problem again.

Revision history for this message
Vladimir Rutsky (rutsky) wrote :

I have same problem as described in this bug report on Ubuntu 10.04 (krusader 1:2.0.0-1ubuntu3).

In my case problem was with value of "Left Active Tab" in krusaderrc at "[Startup]" section - looks like it was greater than total number of saved tabs at left panel.

Workaround for this bug is to open ~/.kde/share/config/krusaderrc, find "Left Active Tab=XXX" (or "Right Active Tab=XXX") and replace it with "Left Active Tab=0" ("Right Active Tab=0").

More stable option, I think, will be in removing whole "[Startup]" section.

Attaching configuration on which bug can be reproduced with following callstack:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#5 0x0000000000453eca in PanelManager::slotChangePanel (this=0x1252730, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#6 0x000000000045f28a in KrusaderView::start (this=0x12b5180, leftTabs=) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:141
#7 0x000000000046ed91 in Krusader (this=0x7fffe81210a0, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#8 0x000000000045c22c in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.