Bug 1413390

Summary: Sugar desktop environment fail to start
Product: [Fedora] Fedora Reporter: Jérôme Benoit <jerome.benoit>
Component: sugarAssignee: Simon Schampijer <simon>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 25CC: nachoel01, pbrobinson, sebastian, simon, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:02:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
shell.log none

Description Jérôme Benoit 2017-01-15 17:15:09 UTC
Created attachment 1240960 [details]
shell.log

Description of problem:
Sugar fail to start and through out an error

Version-Release number of selected component (if applicable):
sugar version 0.108


How reproducible:
Always

Steps to Reproduce:
1. Just install the sugar desktop with "dnf groupinstall" 
2. Choose sugar desktop on the login manager
3.

Actual results:
Crash and log out


Expected results:
Log in without any problem


Additional info:
I join the ~/sugar/default/logs/shell.log file

Comment 1 Ignacio Rodríguez 2017-01-15 19:34:13 UTC
Hi, Jérôme Benoit, looks like a WebKit version problem (not Gtk as it says)
can you try by installing libwebkitgtk3?

If you keep having problems, can you try by installing Sugar 0.110?
https://copr.fedorainfracloud.org/coprs/ignacio/sugar0.110

Comment 2 Peter Robinson 2017-01-16 04:49:58 UTC
install webkitgtk3 and it should work.

Comment 3 Jérôme Benoit 2017-01-21 11:18:32 UTC
That dependency must be explicitly stated in the .spec, not guessed by the sugar on Fedora end-users.

Comment 4 Peter Robinson 2017-01-21 11:27:55 UTC
(In reply to Jérôme Benoit from comment #3)
> That dependency must be explicitly stated in the .spec, not guessed by the
> sugar on Fedora end-users.

It's already fixed in rawhide, I'm well aware of how dependencies work. I've not yet had the time to review versions etc in F-25 because I've been traveling and no longer have a F-25 sugar install so will have to redeploy and test first.

Comment 5 Fedora End Of Life 2017-11-16 18:58:28 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 6 Fedora End Of Life 2017-12-12 10:02:49 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.