Bug 281070 - Kstars Crashes at start up
Summary: Kstars Crashes at start up
Status: RESOLVED DUPLICATE of bug 279026
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Akarsh Simha
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-30 22:03 UTC by DancesWithWords
Modified: 2011-08-30 22:39 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 DancesWithWords 2011-08-30 22:03:00 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

Application: kstars (2.0.0)
KDE Platform Version: 4.7.00 (4.7.0) (Compiled from sources)
Qt Version: 4.7.3
Operating System: Linux 2.6.36-gentoo-r8 x86_64
Distribution: "Gentoo Base System release 2.0.3"

-- Information about the crash:
- What I was doing when the application crashed: 
Just started the program.

- Custom settings of the application:
 The program worked fine until I downloaded the extra packages... catalogues etc.

The crash can be reproduced every time.

-- Backtrace:
Application: KStars (kstars), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fddb0335cd2 in QLocalePrivate::stringToLongLong(QString const&, int, bool*, QLocalePrivate::GroupSeparatorMode) const () from /usr/lib64/qt4/libQtCore.so.4
#7  0x00007fddb03529c6 in QString::toLongLong(bool*, int) const () from /usr/lib64/qt4/libQtCore.so.4
#8  0x00007fddb0352a45 in QString::toInt(bool*, int) const () from /usr/lib64/qt4/libQtCore.so.4
#9  0x0000000000455d28 in _start ()

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

Possible duplicates by query: bug 280990, bug 279486, bug 279026, bug 256133.

Report to https://bugs.kde.org

Reproducible: Didn't try

Steps to Reproduce:
Just started program from menu and form commandline.


Expected Results:  
Program should have started.
Comment 1 Christoph Feck 2011-08-30 22:39:11 UTC

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