Bug 189399 - kstars crashes with Ctrl+J action (loading moons of Jupiter)
Summary: kstars crashes with Ctrl+J action (loading moons of Jupiter)
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Akarsh Simha
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-11 20:36 UTC by Vicenç Juan Tomas Monserrat
Modified: 2009-05-31 11:05 UTC (History)
3 users (show)

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 Vicenç Juan Tomas Monserrat 2009-04-11 20:36:37 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

I have installed kdeedu-dbg


Aplicación: KStars (kstars), señal SIGSEGV
0x00007f1a516858a0 in __nanosleep_nocancel () from /lib/libc.so.6
Current language:  auto; currently c

Thread 1 (Thread 0x7f1a55744750 (LWP 7761)):
[KCrash Handler]
#5  dms::SinCos (this=0x150, sina=@0x7fff5d87f348, cosa=@0x7fff5d87f340) at ../../../kstars/kstars/dms.cpp:236
#6  0x00000000005760eb in JupiterMoons::findPosition (this=0x7fff5d87f910, num=0x7fff5d87f460, Jupiter=0x0, Sun=0xac5df0) at ../../../kstars/kstars/jupitermoons.cpp:92
#7  0x000000000048f810 in JMoonTool::initPlotObjects (this=0x35397a0) at ../../../kstars/kstars/tools/jmoontool.cpp:134
#8  0x0000000000490368 in JMoonTool (this=0x35397a0, parent=<value optimized out>) at ../../../kstars/kstars/tools/jmoontool.cpp:104
#9  0x0000000000595628 in KStars::slotJMoonTool (this=0xa4bc10) at ../../../kstars/kstars/kstarsactions.cpp:273
#10 0x00000000005928bd in KStars::qt_metacall (this=0xa4bc10, _c=QMetaObject::InvokeMetaMethod, _id=24, _a=0x7fff5d87fe90) at ./kstars.moc:252
#11 0x00007f1a52e86622 in QMetaObject::activate (sender=0x333f950, from_signal_index=<value optimized out>, to_signal_index=6, argv=0xac5df0) at kernel/qobject.cpp:3069
#12 0x00007f1a522b06e7 in QAction::triggered (this=0x150, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#13 0x00007f1a522b1b60 in QAction::activate (this=0x333f950, event=<value optimized out>) at kernel/qaction.cpp:1160
#14 0x00007f1a526de67c in QMenuPrivate::activateCausedStack (this=0x3390d00, causedStack=@0x7fff5d87ffb0, action=0x333f950, action_e=QAction::Trigger, self=16) at widgets/qmenu.cpp:962
#15 0x00007f1a526e464e in QMenuPrivate::activateAction (this=0x3390d00, action=0x333f950, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1058
#16 0x00007f1a536ceda1 in KMenu::mouseReleaseEvent (this=0x3390cc0, e=0x7fff5d880ad0) at ../../kdeui/widgets/kmenu.cpp:454
#17 0x00007f1a523077cf in QWidget::event (this=0x3390cc0, event=0x7fff5d880ad0) at kernel/qwidget.cpp:7516
#18 0x00007f1a526e6e0b in QMenu::event (this=0x3390cc0, e=0x7fff5d880ad0) at widgets/qmenu.cpp:2351
#19 0x00007f1a522b667d in QApplicationPrivate::notify_helper (this=0x93b350, receiver=0x3390cc0, e=0x7fff5d880ad0) at kernel/qapplication.cpp:4084
#20 0x00007f1a522befca in QApplication::notify (this=<value optimized out>, receiver=0x3390cc0, e=0x7fff5d880ad0) at kernel/qapplication.cpp:3786
#21 0x00007f1a535fe55b in KApplication::notify (this=0x7fff5d881e50, receiver=0x3390cc0, event=0x7fff5d880ad0) at ../../kdeui/kernel/kapplication.cpp:307
#22 0x00007f1a52e70c4c in QCoreApplication::notifyInternal (this=0x7fff5d881e50, receiver=0x3390cc0, event=0x7fff5d880ad0) at kernel/qcoreapplication.cpp:602
#23 0x00007f1a522be218 in QApplicationPrivate::sendMouseEvent (receiver=0x3390cc0, event=0x7fff5d880ad0, alienWidget=0x0, nativeWidget=0x3390cc0, buttonDown=<value optimized out>, 
    lastMouseReceiver=@0x7f1a52d18eb0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#24 0x00007f1a52327e64 in QETWidget::translateMouseEvent (this=0x3390cc0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4359
#25 0x00007f1a52326de8 in QApplication::x11ProcessEvent (this=0x7fff5d881e50, event=0x7fff5d881460) at kernel/qapplication_x11.cpp:3543
#26 0x00007f1a5234efa4 in x11EventSourceDispatch (s=0x93efa0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#27 0x00007f1a4e031e4a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007f1a4e035510 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0x00007f1a4e0356ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007f1a52e9a29f in QEventDispatcherGlib::processEvents (this=0x9272b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#31 0x00007f1a5234e74f in QGuiEventDispatcherGlib::processEvents (this=0x150, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#32 0x00007f1a52e6f4f2 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1569199952}) at kernel/qeventloop.cpp:149
#33 0x00007f1a52e6f8bd in QEventLoop::exec (this=0x7fff5d881790, flags={i = 1569200032}) at kernel/qeventloop.cpp:200
#34 0x00007f1a52e71b84 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#35 0x00000000005cd123 in main (argc=5, argv=0x7fff5d882938) at ../../../kstars/kstars/main.cpp:187
Comment 1 Médéric Boquien 2009-04-13 03:00:45 UTC
It is strange, i cannot reproduce the crash either with KDE 4.2 or trunk. Is there anything particular you do beside ctrl-J?
Comment 2 Vicenç Juan Tomas Monserrat 2009-04-13 09:25:30 UTC
No, I just open the program and go to menu and click on "moons of Jupiter" or press Ctrl+j, then the program crashes.

Ah, I've installed Qt 4.5.0-2 from experimental. It may be that?
Comment 3 Médéric Boquien 2009-04-13 14:46:42 UTC
I have not tried KDE 4.2 with Qt 4.5. It may (or may not) be the problem. Is there any possibility for you to try with Qt 4.4 or with KDE trunk?
Comment 4 Vicenç Juan Tomas Monserrat 2009-04-14 11:48:59 UTC
The same happens with Qt 4.4.3-2. I can't try with KDE trunk, sorry.
Comment 5 David Erosa García 2009-05-04 12:52:52 UTC
It's happening to me too:

After opening kstars, ctrl+j makes it crash with the following information:

Aplicación: KStars (kstars), señal SIGSEGV

Thread 1 (Thread 0xb4ef5700 (LWP 15344)):
[KCrash Handler]
#6  0x081aadba in _start ()

This is Ubuntu Jaunty with kstars 4:4.2.2-0ubuntu1 and qt 4.5.0 (4.5.0-0ubuntu4)
Comment 6 Médéric Boquien 2009-05-04 14:16:27 UTC
Could you check if the crash happens when you are using kstars with the interface in English please? IIRC Akarsh suspects it crashes because of the way the translation is handled in kstars currently.
Comment 7 David Erosa García 2009-05-04 14:21:56 UTC
Médéric, starting Kstars with:

derosa@bowman:~$ LANG=C kstars

doesn't crash when the "Jupiter Moons" tool is selected with CTRL+J
Comment 8 Vicenç Juan Tomas Monserrat 2009-05-04 16:01:30 UTC
with the interface in English doesn't crash. now using Qt 4.5.1-1 of sid.
Comment 9 Akarsh Simha 2009-05-30 08:07:11 UTC
SVN commit 975410 by asimha:

This should fix bug 189399.

"Jupiter" might be translated in some languages, so putting an i18n on
the findByName call should prevent it from returning NULL and crashing
KStars. This should not introduce new strings as "Jupiter" is
translated elsewhere.

I can't test this fix because I don't have a language that translates
the string 'Jupiter', but it leaves the German and English versions
(that don't translate Jupiter) untouched. Please test this fix and
close the bug if it works.

CCBUG: 189399
CCMAIL: kstars-devel@kde.org



 M  +1 -1      jmoontool.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=975410
Comment 10 Burkhard Lück 2009-05-31 10:49:48 UTC
kstars trunk r975780

KDE_LANG=x-test kstars
Ctrl+J

no crash, the jupiter moon window is properly displayed
--> bug seems to be fixed
Comment 11 Akarsh Simha 2009-05-31 11:05:28 UTC
Thanks!