Bug 23668 - plasma-discover crash: *** longjmp causes uninitialized stack frame ***
Summary: plasma-discover crash: *** longjmp causes uninitialized stack frame ***
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-11 11:25 CEST by Morgan Leijström
Modified: 2019-11-28 16:56 CET (History)
2 users (show)

See Also:
Source RPM: discover-5.12.2-1.mga6.src.rpm
CVE:
Status comment:


Attachments

Description Morgan Leijström 2018-10-11 11:25:23 CEST
I never used this program before, just wanted to see what it do.
I browsed around in it a few seconds then it vanished from screen.

Starting it in terminal and not touching it at all, it crash after about ten seconds, with a lot of output. Notably the lines:

*** longjmp causes uninitialized stack frame ***: plasma-discover terminated
======= Backtrace: =========
/lib64/libc.so.6(+0x72435)[0x7f6b649a7435]
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f6b64a3c3a7]
/lib64/libc.so.6(+0x1072dd)[0x7f6b64a3c2dd]
/lib64/libc.so.6(__longjmp_chk+0x29)[0x7f6b64a3c239]
/lib64/libcurl.so.4(+0xe4e5)[0x7f6b1d6e04e5]
/lib64/libc.so.6(+0x338a0)[0x7f6b649688a0]
/lib64/libc.so.6(__poll+0x2d)[0x7f6b64a1efcd]
/lib64/libglib-2.0.so.0(+0x49e14)[0x7f6b6009be14]
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f6b6009bf2c]
/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x66)[0x7f6b65634776]
/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xea)[0x7f6b655dfe0a]
/lib64/libQt5Core.so.5(_ZN16QCoreApplication4execEv+0x88)[0x7f6b655e89c8]
plasma-discover[0x41045e]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7f6b64955600]
plasma-discover(_start+0x29)[0x410569]

This system is mga6 64 bit with all updates from updates_testing excluding kernel which is desktop 4.14.70.  Originally a mga4 system, it may have some cruft laying around.  I uninstalled plasma-discover and reinstalled, no change.

Could this be a variant of Bug 22828 ?  Op there say it vanished in a few seconds without touching it so timing seem similar.
Morgan Leijström 2018-10-11 11:27:26 CEST

Assignee: bugsquad => kde

Comment 1 Ulrich Beckmann 2018-10-12 08:56:52 CEST
Works here, though the exposure with the dark theme is very poor.

[beq-mageia@mag6-clone ~]$ plasma-discover
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x25a13a0)
could not find "org.kde.ktorrent.desktop" "ktorrent.desktop"
could not find "org.kde.kmymoney.desktop" "kmymoney.desktop"
could not find "blender.desktop" ""
could not find "inkscape.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.ktorrent.desktop" "ktorrent.desktop"
could not find "org.kde.kmymoney.desktop" "kmymoney.desktop"
could not find "blender.desktop" ""
could not find "inkscape.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.ktorrent.desktop" "ktorrent.desktop"
could not find "org.kde.kmymoney.desktop" "kmymoney.desktop"
could not find "blender.desktop" ""
could not find "inkscape.desktop" ""
could not find "org.kde.development" ""
could not find "org.kde.ktorrent.desktop" "ktorrent.desktop"
could not find "org.kde.kmymoney.desktop" "kmymoney.desktop"
could not find "blender.desktop" ""
could not find "inkscape.desktop" ""
could not find "org.kde.development" ""
[beq-mageia@mag6-clone ~]$

Please show your dnf and Packagekit configuration:

# dnf repolist

# pkcon update

Ulrich

CC: (none) => bequimao.de

Comment 2 Morgan Leijström 2018-10-12 10:31:11 CEST
[root@svarten morgan]# dnf repolist
Senaste kontroll av utgång av metadata: för 23:51:38 sedan den tor 11 okt 2018 10:32:46.
förråds-id                                                            förrådsnamn                                                                           status
mageia-i586                                                           Mageia 6 - i586                                                                       28 137
mageia-i586-nonfree                                                   Mageia 6 - i586 - Nonfree                                                                121
mageia-x86_64                                                         Mageia 6 - x86_64                                                                     28 136
mageia-x86_64-nonfree                                                 Mageia 6 - x86_64 - Nonfree                                                              130
updates-i586                                                          Mageia 6 - i586 - Updates                                                              8 847
updates-i586-nonfree                                                  Mageia 6 - i586 - Nonfree - Updates                                                      116
updates-x86_64                                                        Mageia 6 - x86_64 - Updates                                                            8 627
updates-x86_64-nonfree                                                Mageia 6 - x86_64 - Nonfree - Updates                                                    116
[root@svarten morgan]# pkcon update
Hämtar uppdateringar         [=========================]         
Färdigställd                [=========================]         
Inga paket behöver uppdateras till nyare versioner.

= "No package need to be updated to newer versions"

Hmm... i did try dnf a year ago or so but reverted to urpmi stuff and not actively thouched dnf for over a year i think.
Since some month ago i also use updates_testing repos, also for update.

Regardless of how it gets trigged here, the error " longjmp causes uninitialized stack frame " to mee seem like a design/compile fault that should get fixed.
Comment 3 Ulrich Beckmann 2018-10-12 12:50:14 CEST
I strictly use dnf and have all i586 repos disabled ( # dnf config-manager --set-disabled ... ). It is also a Mageia 6 installation, no system upgrade from Mga 5.
Comment 4 Morgan Leijström 2018-10-12 15:16:15 CEST
Searching web for
 "*** longjmp causes uninitialized stack frame ***" 
gets some hits on bug reports for other programs, and several point out a bug in curl, but which was fixed long ago in version 7.32 ...?  i.e see: 
https://stackoverflow.com/questions/9191668/error-longjmp-causes-uninitialized-stack-frame
Comment 5 Morgan Leijström 2018-10-12 15:30:55 CEST
So maybe a returning curl bug?

Assignee: kde => shlomif

Comment 6 Lewis Smith 2019-11-28 16:35:11 CET
This bug relates to Mageia 6, no longer supported; and an old version of the software.
Having just installed it on Mageia 7, discover-5.15.4-2.mga7, it works. Running under Plasma, both from the menu [Tools-System Tools] and console
[$ plasma-discover]. The console O/P is voluminous.

@ Ulrich Morgan: please can you say whether you still have the problem on Mageia 7? If not, please close the bug OLD.

Assignee: shlomif => bugsquad
CC: (none) => lewyssmith

Comment 7 Morgan Leijström 2019-11-28 16:50:19 CET
MGA7-64 Plasma Nvidia seem OK;
installed discover-5.15.4-2.mga7
launched "plasma-discover", Browsed around about a minute
Installed KDEConnect, and find it working

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 8 Morgan Leijström 2019-11-28 16:56:24 CET
Now when i closed discover-plasma, in the terminal from where i started it, it outputs

  PackageKit stopped running!
  Could not stop all fwupd threads

And i have to issue ^C to get the cursor back.


And yes the output when it is running is voluminous. I.e a lot of:

"Could not convert argument 0 at"
         "expression for iconName@qrc:/qml/KirigamiActionBridge.qml:35"
"Passing incompatible arguments to C++ functions from JavaScript is dangerous and deprecated."
"This will throw a JavaScript TypeError in future releases of Qt!"
qrc:/qml/KirigamiActionBridge.qml:34:5: Unable to assign [undefined] to QString

So the shape of the program is "working, but not perfect"

Note You need to log in before you can comment on or make changes to this bug.