Description of problem:sugar desktop starts in journal.
Version-Release number of selected component (if applicable):
sugar desktop starts in journal. not in f3 Main menu as it should.
seen in f27 and f28 rawhide live install
Steps to Reproduce:
Proposed as a Freeze Exception for 28-beta by Fedora user satellit using the blocker tracking app because:
wrong behavior on start of soas
should open in f3 Desktop main menu
Created attachment 1360622 [details]
wrong sugar start screen
Discussed during the 2017-12-11 blocker review meeting: 
The decision to classify this bug as an AcceptedFreezeException was made as it is clearly wrong behaviour in a non-blocking live image that can't be fixed with an update, and the fix is highly likely to be localized to Sugar.
still present in Fedora-SoaS-Live-x86_64-Rawhide-20180107.n.0.iso
(also present in ubuntu) James Cameron
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle.
Changing version to '28'.
This needs to be actually assigned to a component that's not actually dead, the Journal had for years been part of core sugar.
note to get to main screen (f3) hit f1 key then f3 key
Per satellit this is still happening in F29, so let's propose it as an FE for F29 Beta...
(In reply to Adam Williamson from comment #9)
> Per satellit this is still happening in F29, so let's propose it as an FE
> for F29 Beta...
Removing, this needs to be fixed upstream and there's no movement in the upstream issue referenced in comment 4. Once we have a patch there it would be worth considering a FE but until that point it's a waste of time and process.
it has nothing to do with fedora, it is a gtk+ vs sugar toolkit problem at heart, also seen in debian and ubuntu. (James Cameron)
(In reply to satellitgo from comment #11)
> it has nothing to do with fedora, it is a gtk+ vs sugar toolkit problem at
> heart, also seen in debian and ubuntu. (James Cameron)
So until it's fixed upstream in Sugar please stop proposing it as a blocker and wasting everyone's time in the process!
https://bugzilla.redhat.com/show_bug.cgi?id=1519042 still present
all work in Oracle VirtualBox f28
The triggering cause wasn't Sugar, but Metacity.
It was the upgrade of Metacity from 3.24.0 to 3.25.2, and git bisect shows first bad commit is
"unminimize windows with initial IconicState if first known on MapRequest"
ported from mutter
It isn't clear to me that this represents a problem with Sugar. I'd like to hear from any Metacity or X-Windows experts on the matter, thanks!
Re-assigning so we can get that feedback from the metacity maintainers.
Created attachment 1509235 [details]
log shortly after first boot
The patch offered at http://lists.sugarlabs.org/archive/iaep/2018-November/020586.html was applied to F29-SOAS-x86_64-20181119-Live.iso, a fedora-respin, loaded onto a USB device before it was booted.
The Home View opened, showed the central icon with Journal icon below and no Activity icons at first. Then all the Activity icons appeared in the circle.
The shell log shows some evidence of the metacity issue.
I applied the patch to a F30 soas live install to a T400 Thinkpad with Mate as a 2nd DE, used sugar terminal and USB with fix on it. Starts fine in f3 Home screen of sugar desktop.
metacity-3.30.1-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d6502e66b8
Created attachment 1509864 [details]
logs shortly after first boot with upgraded metacity
metacity-3.30.1-2.fc29 was installed into a freshly loaded USB device with F29-SOAS-x86_64-20181127-Live.iso, a fedora-respin, before it was booted.
Home View showed as expected.
metacity-3.30.1-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d6502e66b8
fixed in Fedora-SoaS-Live-x86_64-Rawhide-20181130.n.0.iso
An update associated with this bug has been pushed to stable.