[Sugar-devel] [SoaS] SoaS Fedora 27 beta fails to launch Sugar session

Peter Robinson pbrobinson at gmail.com
Fri Nov 3 07:01:59 EDT 2017
Previous message (by thread): [Sugar-devel] [SoaS] SoaS Fedora 27 beta fails to launch Sugar session
Next message (by thread): [Sugar-devel] [RELEASE] Browse-201.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Nov 2, 2017 at 8:50 PM, James Cameron <quozl at laptop.org> wrote:
> On Sat, Oct 28, 2017 at 11:36:13AM +0100, Peter Robinson wrote:
>> On Thu, Oct 26, 2017 at 9:29 PM, James Cameron <quozl at laptop.org> wrote:
>> > On Thu, Oct 26, 2017 at 10:00:11AM +0100, Peter Robinson wrote:
>> >> On Thu, Oct 26, 2017 at 9:54 AM, James Cameron <quozl at laptop.org> wrote:
>> >> > On Thu, Oct 26, 2017 at 08:58:01AM +0100, Peter Robinson wrote:
>> >> >> On Tue, Oct 24, 2017 at 12:24 AM, James Cameron <quozl at laptop.org> wrote:
>> >> >> > On Mon, Oct 23, 2017 at 07:15:16PM -0400, Frederick Grose wrote:
>> >> >> >> On Mon, Oct 23, 2017 at 6:39 PM, James Cameron <[1]quozl at laptop.org> wrote:
>> >> >> >>
>> >> >> >>     On Mon, Oct 23, 2017 at 06:13:51PM -0400, Frederick Grose wrote:
>> >> >> >>     > On Mon, Oct 23, 2017 at 6:03 PM, James Cameron <[1][2]quozl at laptop.org>
>> >> >> >>     wrote:
>> >> >> >>     >     Familiar.  Looks like RHBZ #1490668.
>> >> >> >>     >     [3]https://bugzilla.redhat.com/show_bug.cgi?id=1490668
>> >> >> >>     >
>> >> >> >>     >     Sugar doesn't log to systemd journal, so best log file is still
>> >> >> >>     >     ~/.sugar/default/logs/shell.log ... is that file present?
>> >> >> >>     >
>> >> >> >>     >     On Mon, Oct 23, 2017 at 05:38:21PM -0400, Frederick Grose wrote:
>> >> >> >>     >     > Tested with Fedora-SoaS-Live-x86_64-27-20171023.n.0.iso (similar
>> >> >> >>     failure
>> >> >> >>     >     > on Fedora-SoaS-Live-x86_64-27_Beta-1.5.iso)
>> >> >> >>     >     >
>> >> >> >>     >     > The image boots to the liveuser login screen but fails to
>> >> >> >>     >     > launch into the Sugar session.
>> >> >> >>     >     >
>> >> >> >>     >     > journalctl -ab -o short-monotonic > soas27bootjournal.txt
>> >> >> >>     >     >
>> >> >> >>     >     > [4]https://gist.github.com/FGrose/97d834d362c7e1e3f690b97612c673dd
>> >> >> >>     >     >
>> >> >> >>     >     > The lightdm lines look suspicious to me...
>> >> >> >>     >     >
>> >> >> >>     >     > $ grep lightdm /home/fgrose/Documents/soas27bootjournal.txt
>> >> >> >>     >     >
>> >> >> >>     >     > [...]
>> >> >> >>     >     >
>> >> >> >>     >
>> >> >> >>     > Yes,
>> >> >> >>     > Traceback (most recent call last):
>> >> >> >>     >   File "/usr/lib64/python2.7/runpy.py", line 174, in _run_module_as_main
>> >> >> >>     >     "__main__", fname, loader, pkg_name)
>> >> >> >>     >   File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
>> >> >> >>     >     exec code in run_globals
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/main.py", line 73, in
>> >> >> >>     <module>
>> >> >> >>     >     from jarabe.view import keyhandler
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/view/keyhandler.py", line
>> >> >> >>     32,
>> >> >> >>     > in <module>
>> >> >> >>     >     from jarabe.journal import journalactivity
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/journal/journalacti
>> >> >> >>     vity.py",
>> >> >> >>     > line 45, in <module>
>> >> >> >>     >     from jarabe.journal.volumestoolbar import VolumesToolbar
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/journal/volumestool
>> >> >> >>     bar.py",
>> >> >> >>     > line 42, in <module>
>> >> >> >>     >     from jarabe.view.palettes import VolumePalette
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/view/palettes.py", line
>> >> >> >>     38, in
>> >> >> >>     > <module>
>> >> >> >>     >     from jarabe.view.viewhelp import setup_view_help
>> >> >> >>     >   File "/usr/lib/python2.7/site-packages/jarabe/view/viewhelp.py", line
>> >> >> >>     46, in
>> >> >> >>     > <module>
>> >> >> >>     >     from jarabe.view.viewhelp_webkit2 import Browser
>> >> >> >>     > ImportError: No module named viewhelp_webkit2
>> >> >> >>
>> >> >> >>     Thanks.
>> >> >> >>
>> >> >> >>     The ImportError suggests file viewhelp_webkit2.py is missing; can you
>> >> >> >>     confirm that?  It should be right next to
>> >> >> >>     /usr/lib/python2.7/site-packages/jarabe/view/viewhelp.py
>> >> >> >>
>> >> >> >> ls -la usr/lib/python2.7/site-packages/jarabe/view/
>> >> >> >> total 432
>> >> >> >> drwxr-xr-x.  2 root root  4096 Oct 23 08:17 .
>> >> >> >> drwxr-xr-x. 11 root root  4096 Oct 23 08:17 ..
>> >> >> >> -rw-r--r--.  1 root root  2028 Aug 12 08:30 alerts.py
>> >> >> >> -rw-r--r--.  2 root root  2647 Aug 12 08:30 alerts.pyc
>> >> >> >> -rw-r--r--.  2 root root  2647 Aug 12 08:30 alerts.pyo
>> >> >> >> -rw-r--r--.  1 root root  2754 Aug 12 08:30 buddyicon.py
>> >> >> >> -rw-r--r--.  2 root root  3008 Aug 12 08:30 buddyicon.pyc
>> >> >> >> -rw-r--r--.  2 root root  3008 Aug 12 08:30 buddyicon.pyo
>> >> >> >> -rw-r--r--.  1 root root  8687 Aug 12 08:30 buddymenu.py
>> >> >> >> -rw-r--r--.  2 root root  9396 Aug 12 08:30 buddymenu.pyc
>> >> >> >> -rw-r--r--.  2 root root  9396 Aug 12 08:30 buddymenu.pyo
>> >> >> >> -rw-r--r--.  1 root root  1728 Aug 12 08:30 cursortracker.py
>> >> >> >> -rw-r--r--.  2 root root  1330 Aug 12 08:30 cursortracker.pyc
>> >> >> >> -rw-r--r--.  2 root root  1330 Aug 12 08:30 cursortracker.pyo
>> >> >> >> -rw-r--r--.  1 root root  7418 Aug 12 08:30 customizebundle.py
>> >> >> >> -rw-r--r--.  2 root root  6241 Aug 12 08:30 customizebundle.pyc
>> >> >> >> -rw-r--r--.  2 root root  6241 Aug 12 08:30 customizebundle.pyo
>> >> >> >> -rw-r--r--.  1 root root  2473 Aug 12 08:30 gesturehandler.py
>> >> >> >> -rw-r--r--.  2 root root  2896 Aug 12 08:30 gesturehandler.pyc
>> >> >> >> -rw-r--r--.  2 root root  2896 Aug 12 08:30 gesturehandler.pyo
>> >> >> >> -rw-r--r--.  1 root root   677 Aug 12 08:30 __init__.py
>> >> >> >> -rw-r--r--.  2 root root   143 Aug 12 08:30 __init__.pyc
>> >> >> >> -rw-r--r--.  2 root root   143 Aug 12 08:30 __init__.pyo
>> >> >> >> -rw-r--r--.  1 root root  8290 Aug 12 08:30 keyhandler.py
>> >> >> >> -rw-r--r--.  2 root root  9438 Aug 12 08:30 keyhandler.pyc
>> >> >> >> -rw-r--r--.  2 root root  9438 Aug 12 08:30 keyhandler.pyo
>> >> >> >> -rw-r--r--.  1 root root  6044 Aug 12 08:30 launcher.py
>> >> >> >> -rw-r--r--.  2 root root  6752 Aug 12 08:30 launcher.pyc
>> >> >> >> -rw-r--r--.  2 root root  6752 Aug 12 08:30 launcher.pyo
>> >> >> >> -rw-r--r--.  1 root root 11282 Aug 12 08:30 palettes.py
>> >> >> >> -rw-r--r--.  2 root root 12132 Aug 12 08:30 palettes.pyc
>> >> >> >> -rw-r--r--.  2 root root 12132 Aug 12 08:30 palettes.pyo
>> >> >> >> -rw-r--r--.  1 root root  7262 Aug 12 08:30 pulsingicon.py
>> >> >> >> -rw-r--r--.  2 root root  9199 Aug 12 08:30 pulsingicon.pyc
>> >> >> >> -rw-r--r--.  2 root root  9199 Aug 12 08:30 pulsingicon.pyo
>> >> >> >> -rw-r--r--.  1 root root  3237 Aug 12 08:30 service.py
>> >> >> >> -rw-r--r--.  2 root root  3216 Aug 12 08:30 service.pyc
>> >> >> >> -rw-r--r--.  2 root root  3216 Aug 12 08:30 service.pyo
>> >> >> >> -rw-r--r--.  1 root root  6117 Aug 12 08:30 tabbinghandler.py
>> >> >> >> -rw-r--r--.  2 root root  5539 Aug 12 08:30 tabbinghandler.pyc
>> >> >> >> -rw-r--r--.  2 root root  5539 Aug 12 08:30 tabbinghandler.pyo
>> >> >> >> -rw-r--r--.  1 root root 12199 Aug 12 08:30 viewhelp.py
>> >> >> >> -rw-r--r--.  2 root root 12816 Aug 12 08:30 viewhelp.pyc
>> >> >> >> -rw-r--r--.  2 root root 12816 Aug 12 08:30 viewhelp.pyo
>> >> >> >> -rw-r--r--.  1 root root 29829 Aug 12 08:30 viewsource.py
>> >> >> >> -rw-r--r--.  2 root root 28835 Aug 12 08:30 viewsource.pyc
>> >> >> >> -rw-r--r--.  2 root root 28835 Aug 12 08:30 viewsource.pyo
>> >> >> >>
>> >> >> >> rpm -q sugar
>> >> >> >> sugar-0.110.0-5.fc27.src.rpm
>> >> >> >
>> >> >> > Files are missing from package.
>> >> >>
>> >> >> From the sugar package PoV this hasn't changed since F-26 and it was
>> >> >> working fine then, if someone can point me to a patch I can pull in I
>> >> >> can fix this but it'll need to be RSN.
>> >> >
>> >> > Not a Sugar problem.  Traceback refers to files that you added in a packaging patch to 0.110, from files I added after 0.110 upstream, so I've no idea why F-27 hasn't got the files.
>> >>
>> >> Sure, but it worked in F26 so there's something regressed somewhere
>> >> and I don't have time to debug it so Fredrick or someone will need to
>> >> assist.
>> >
>> > Agreed, something has regressed, but I don't know what.  It is a bit
>> > unusual to lose files added during packaging.
>> >
>> >> > You might avoid the packaging patch by taking 0.112.
>> >>
>> >> Is that even released? I've seen no announcement for it,
>> >
>> > It was released on 8th October, here's the announcement;
>> > http://lists.sugarlabs.org/archive/sugar-devel/2017-October/054834.html
>> >
>> > Tarball uploaded at the same time.
>> >
>> > Was there some other place you needed notification?
>>
>> I'm on sugar-devel I believe but I don't see any release announcements
>> for any of this in my gmail which is weird as I'm getting this
>> message, really not sure what's going on there, add the SoaS list, cc:
>> me or ping me on IRC or other means if you don't see I've updated
>> packages.
>
> You don't get list mail reliably.  The announcements are in the list
> archives.  gmail bounced or dropped the messages before you got them.

Sure but that requires me to do something manually on a semi regular
basis "just in case"

> We have bounce_notify_owner_on_bounce_increment set to No, so we would
> not have noticed a bounce.  I'll leave it as No.  With 386 members
> that would be a lot of noise for the list administrators.
>
> Dropped messages is gmail's responsibility, and you might contact them.

TBH I suspect they drop it for a reason, I doubt it's a gmail thing,
I'm on a lot of lists and this is the only one I ever see issues with.

> You might use git tags or the download directory to detect missed
> announcements.  You might also subscribe another address.
>
> Yes, we can certainly ping you, but when?  Depends on distribution
> release phase?

Whenever, it doesn't bother me, if I'm aware I can then update it when
I have some cycles.

> I've added to the release process "One week later, check that the
> corresponding packages have been updated, and if not contact the
> downstream packager."
>
> https://wiki.sugarlabs.org/go/Development_Team/Release#Glucose_.28base.29_modules
>
> +CC Jonas, as Debian is also a downstream, and we must be fair.
>
>> Also happy to have you co-maintain the packages too.
>
> Thanks.  Likewise, I'm unlikely to find time.
>
>> >> and since Fedora is in freeze now I'm unlikely to rebase now
>> >
>> > The beta freeze on 9th September combined with lack of Sugar release
>> > manager prompted my decision to fill the gap.  Sugar 0.111 was
>> > released on 13th September.
>>
>> Again I never saw the announcement of that.
>
> http://lists.sugarlabs.org/archive/sugar-devel/2017-September/054631.html
>
>> _______________________________________________
>> SoaS mailing list
>> SoaS at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/soas
>
> --
> James Cameron
> http://quozl.netrek.org/
Previous message (by thread): [Sugar-devel] [SoaS] SoaS Fedora 27 beta fails to launch Sugar session
Next message (by thread): [Sugar-devel] [RELEASE] Browse-201.3
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Sugar-devel mailing list