Bug 218300 - krusader will not start after latest update of kde-files in ubuntu 9.10 2009-12-11
Summary: krusader will not start after latest update of kde-files in ubuntu 9.10 2009-...
Status: RESOLVED DUPLICATE of bug 191167
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 17:17 UTC by Erik Sørensen
Modified: 2009-12-12 23:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Sørensen 2009-12-11 17:17:45 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-16-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
The error is determined after Synaptic was used for update today 2009-12-11

It ends (loops) at the error-message


 -- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault
[KCrash Handler]
#6  0x0808aa88 in PanelManager::slotChangePanel (this=0x8a57840, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71
#7  0x08096943 in KrusaderView::start (this=0x88b8e78, leftTabs=..., leftTypes=..., leftProps=..., leftActiveTab=0, rightTabs=..., rightTypes=..., rightProps=..., rightActiveTab=1, 
    leftSideActive=false) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:142
#8  0x080a74e3 in Krusader (this=0xbfc3bddc, __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=1, argv=0xbfc3c594) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240

This bug may be a duplicate of or related to bug 217839

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-12 23:54:44 UTC
This bug is being tracked at bug 191167. Thanks

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