[SRU] kstars 3.5.7 crashes with segfault on startup on 22.04 and 22.10

[Rik Mills]

U/Kubuntu 22.04
Package: kstars
Version: 5:3.5.7-1

Also see: https://bugs.kde.org/show_bug.cgi?id=453239

[Impact]

 * The application segfaults on start, so is useless in its current state

[Test Plan]

 * Does it start ok?

 * Tester familiar with kstars may wish to test if there are any regressions in functionality compared to previous releases.

[Where problems could occur]

 * Regressions in functionality compared with previous releases. Unless major, these may not be a blocker to this fix and a follow up SRU would be more appropriate.

********** original bug description below ***********

Crash with segfault on startup:

Thread 1 "kstars" received signal SIGSEGV, Segmentation fault.
doActivate<false> (sender=0x0, signal_index=9, argv=0x7fffffffd550) at kernel/qobject.cpp:3768
3768 kernel/qobject.cpp: No such file or directory.
(gdb) bt
#0 doActivate<false> (sender=0x0, signal_index=9, argv=0x7fffffffd550) at kernel/qobject.cpp:3768
#1 0x00007ffff529ba97 in QMetaObject::activate (sender=<optimised out>, m=m@entry=0x7ffff5bd50e0 <QGuiApplication::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fffffffd550)
    at kernel/qobject.cpp:3946
#2 0x00007ffff5645046 in QGuiApplication::screenAdded (this=<optimised out>, _t1=<optimised out>, _t1@entry=0x55555654fa50) at .moc/moc_qguiapplication.cpp:389
#3 0x00007ffff562a7c0 in QWindowSystemInterface::handleScreenAdded (ps=ps@entry=0x5555564ca590, isPrimary=<optimised out>) at kernel/qwindowsysteminterface.cpp:826
#4 0x00007fffef903528 in QXcbConnection::initializeScreens (this=this@entry=0x5555564b5ad0) at ./src/plugins/platforms/xcb/qxcbconnection_screens.cpp:413
#5 0x00007fffef8da680 in QXcbConnection::QXcbConnection (this=0x5555564b5ad0, nativeInterface=<optimised out>, canGrabServer=<optimised out>, defaultVisualId=<optimised out>, displayName=<optimised out>)
    at ./src/plugins/platforms/xcb/qxcbconnection.cpp:103
#6 0x00007fffef8dddb0 in QXcbIntegration::QXcbIntegration (this=this@entry=0x5555564b17d0, parameters=..., argc=@0x7fffffffdbec: 1, argv=argv@entry=0x7fffffffdf68) at ./src/plugins/platforms/xcb/qxcbintegration.cpp:197
#7 0x00007ffff7fb7523 in QXcbIntegrationPlugin::create (this=<optimised out>, system=..., argv=0x7fffffffdf68, argc=@0x7fffffffdbec: 1, parameters=...) at ./src/plugins/platforms/xcb/qxcbmain.cpp:56
#8 QXcbIntegrationPlugin::create (this=<optimised out>, system=..., parameters=..., argc=@0x7fffffffdbec: 1, argv=0x7fffffffdf68) at ./src/plugins/platforms/xcb/qxcbmain.cpp:53
#9 0x00007ffff56495ef in init_platform (argv=<optimised out>, argc=@0x7fffffffdbec: 1, platformThemeName=..., platformPluginPath=..., pluginNamesWithArguments=...) at kernel/qguiapplication.cpp:1223
#10 QGuiApplicationPrivate::createPlatformIntegration (this=0x5555564a6a50) at kernel/qguiapplication.cpp:1481
#11 0x00007ffff564ac08 in QGuiApplicationPrivate::createEventDispatcher (this=<optimised out>) at kernel/qguiapplication.cpp:1498
#12 0x00007ffff5271b07 in QCoreApplicationPrivate::init (this=this@entry=0x5555564a6a50) at kernel/qcoreapplication.cpp:835
#13 0x00007ffff564db70 in QGuiApplicationPrivate::init (this=0x5555564a6a50) at kernel/qguiapplication.cpp:1527
#14 0x00007ffff5d61ced in QApplicationPrivate::init() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x0000555555716b6c in main (argc=<optimised out>, argv=0x7fffffffdf68) at ./kstars/main.cpp:67

[Rik Mills (rikmills)]

The backtrace looked very similar to the nextcloud-desktop crash on startup when built with LTO enabled. Confirmed that building with LTO turned off for kstars likewise fixes the startup crash.

[Launchpad Janitor (janitor)]

This bug was fixed in the package kstars - 5:3.5.7-1ubuntu1

---------------
kstars (5:3.5.7-1ubuntu1) kinetic; urgency=medium

  * Disable building with LTO to fix startup segfault (LP: #1971091)

 -- Rik Mills <email address hidden> Mon, 02 May 2022 07:00:12 +0100

[Robie Basak (racb)]

Hello Rik, or anyone else affected,

Accepted kstars into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kstars/5:3.5.7-1ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Rik Mills (rikmills)]

Kstars from jammy proposed starts OK for me, and on the time I have available to test seem to function as it should.

[Launchpad Janitor (janitor)]

This bug was fixed in the package kstars - 5:3.5.7-1ubuntu0.1

---------------
kstars (5:3.5.7-1ubuntu0.1) jammy; urgency=medium

  * Disable building with LTO to fix startup segfault (LP: #1971091)

 -- Rik Mills <email address hidden> Wed, 04 May 2022 08:33:10 +0100

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for kstars has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.