Created attachment 1048658 [details]
Sugar shell log showing the error
Description of problem:
The '/lib64/libsugarext.so.0' file installed by the package manager causes an error, crashing startup. The error is enclosed in the log attached.
However, when compiling sugar using sugar-build, the '/lib64/libsugarext.so.0' generated is proper and does not cause any errors.
Version-Release number of selected component (if applicable):
Tested on a Fedora Rawhide desktop install. Also tested on a SoaS Rawhide build <http://koji.fedoraproject.org/koji/taskinfo?taskID=10290898>
Steps to Reproduce:
1. Launch sugar (sugar-runner or using it as your de)
Sugar does not crash
Can you use abrt to submit a full crash dump so I can see full crash dump
Actually looks like it's trying to load it from the wrong location
** (main.py:1932): WARNING **: Failed to load shared library 'libsugarext.so.0' referenced by the typelib: /lib64/libsugarext.so.0: undefined symbol: sugar_event_controller_get_state
It should be /usr/lib64 not /lib64
I'm not 100% sure how to get the full dump.
The error does not show up in ABRT gui app.
Just tested; the issue is still present in the 0.106 builds for rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.
(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)
More information and reason for this action is here:
Ok, I'm going to clear the need info in hope of getting some info. Is there a way to get the ABRT dump if it doesn't show up in the gui?
Hum, can't find it there either. All return nothing:
~ $ abrt-cli ls | grep 'sugar-runner --resolution="1200x900"'
~ $ abrt-cli ls | grep -i 'sugarext'
~ $ abrt-cli ls | grep '/lib64'
Hum, when I ran "Fedora-Live-SoaS-i686-23_Alpha-2.iso" I get exactly the same issue. It appears that the compilation issue is cross arch.
This is a BLOCKER bug for Sugar and SoaS BTW.
*** Bug 1240354 has been marked as a duplicate of this bug. ***
sugar-toolkit-gtk3-0.106.0-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15309
sugar-toolkit-gtk3-0.106.0-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update sugar-toolkit-gtk3'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15309
"On 9/9/2015 10:05 AM, Jerry Vonau wrote:
Confirmed for F23, boot TC4 with systemd.unit=runlevel3.target, login as
liveuser, "sudo dnf --enablerepo=updates-testing update
"sudo systemctl isolate runlevel5.target" results in Sugar loading."
I can confirm this works in virt-manager install of f23 SoaS live x86_64
(In reply to satellitgo from comment #13)
> "On 9/9/2015 10:05 AM, Jerry Vonau wrote:
> Confirmed for F23, boot TC4 with systemd.unit=runlevel3.target, login as
> liveuser, "sudo dnf --enablerepo=updates-testing update
> "sudo systemctl isolate runlevel5.target" results in Sugar loading."
> I can confirm this works in virt-manager install of f23 SoaS live x86_64
also f23 soas live i686 TC-4
no reason to block AlphaFreezeException any more.
Discussed at 2015-09-10 freeze exception review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-09-10/f23-blocker-review.2015-09-10-16.00.log.txt . Accepted as a Beta freeze exception issue: this would be a blocker for a release-blocking desktop, hence it's accepted as a freeze exception issue for non-release-blocking desktop.
sugar-toolkit-gtk3-0.106.0-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Peter Robinson from comment #2)
> Actually looks like it's trying to load it from the wrong location
> ** (main.py:1932): WARNING **: Failed to load shared library
> 'libsugarext.so.0' referenced by the typelib: /lib64/libsugarext.so.0:
> undefined symbol: sugar_event_controller_get_state
> It should be /usr/lib64 not /lib64
Could an error warning like below cause the above wrong location?
libtool: install: warning: remember to run `libtool --finish /usr/lib64'
I noticed this warning in a copr build, just wondering.