Bug 1895674 - libkgapi built with LTO causes crashes when using kio-gdrive
Summary: libkgapi built with LTO causes crashes when using kio-gdrive
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libkgapi
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mario Santagiuliana
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-08 09:22 UTC by Yaroslav Sidlovsky
Modified: 2021-11-30 16:45 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:45:26 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Yaroslav Sidlovsky 2020-11-08 09:22:53 UTC
Description of problem:
I've got crash using KIO Gdrive.

Version-Release number of selected component (if applicable):
libkgapi-20.08.1-1.fc33.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Run `kioclient5 exec gdrive:/`.

Actual results:
kf.kio.core: couldn't create slave: "klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'."
"Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'."

Expected results:
No crashes.

Additional info:
Rebuilding libkgapi without LTO solves issue for me.

Comment 1 Yaroslav Sidlovsky 2020-11-12 15:01:20 UTC
Rex could you rebuild libkgapi without LTO for F33?

Comment 2 Vasiliy Glazov 2020-11-13 18:59:21 UTC
Rex, please rebuild it without LTO for F33.

Comment 3 Fedora Update System 2020-11-14 05:37:46 UTC
FEDORA-2020-b6bf57746c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-b6bf57746c

Comment 4 Fedora Update System 2020-11-15 01:05:15 UTC
FEDORA-2020-b6bf57746c has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-b6bf57746c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-b6bf57746c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2020-11-18 02:20:37 UTC
FEDORA-2020-b6bf57746c has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Ben Cotton 2021-11-04 17:14:12 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2021-11-30 16:45:26 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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