Bug 265059 - krusader crashes at startup
Summary: krusader crashes at startup
Status: RESOLVED DUPLICATE of bug 191167
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-01 09:09 UTC by Martin Popel
Modified: 2011-02-01 15:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Popel 2011-02-01 09:09:11 UTC
Application: krusader (2.0.0 "Mars Pathfinder")
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-28-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Workaround: editing [Startup] section of ~/.kde/share/config/krusaderrc
Right Active Tab=2
# 2 is out of range, so changed to 
Right Active Tab=0

The crash can be reproduced every time.

 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#6  0x0808ac88 in PanelManager::slotChangePanel (this=0x94877d0, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x080970ed in KrusaderView::start (this=0x93fa008, leftTabs=..., leftTypes=..., leftProps=..., leftActiveTab=0, rightTabs=..., rightTypes=..., rightProps=..., rightActiveTab=2, 
    leftSideActive=false) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a7e54 in Krusader (this=0xbfa4e638, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376
#9  0x08093d3c in main (argc=5, argv=0xbfa4edf4) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

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

Possible duplicates by query: bug 258000, bug 255255, bug 248964, bug 246449, bug 246420.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-02-01 15:39:20 UTC

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