Bug 1507292

Summary: sugar-browse fails to launch in SoaS Fedora 27 beta
Product: [Fedora] Fedora Reporter: Frederick Grose <fgrose>
Component: sugar-browseAssignee: Simon Schampijer <simon>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 27CC: callkalpa, fgrose, manuel.por.aca, pbrobinson, simon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-29 12:27:06 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:

Description Frederick Grose 2017-10-29 11:41:40 UTC
Description of problem: The Browse Activity fails to launch


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

  sugar-browse-201.1-2.fc27.noarch

How reproducible: always

Here is the sugar log:

/usr/lib/python2.7/site-packages/sugar3/activity/activity.py:96: PyGIWarning: SugarExt was imported without specifying a version first. Use gi.require_version('SugarExt', '1.0') before import to ensure that the right version gets loaded.
  from gi.repository import SugarExt
Traceback (most recent call last):
  File "/usr/bin/sugar-activity", line 220, in <module>
    main()
  File "/usr/bin/sugar-activity", line 164, in main
    module = __import__(module_name)
  File "/usr/share/sugar/activities/Browse.activity/webactivity.py", line 58, in <module>
    from collabwrapper.collabwrapper import CollabWrapper
ImportError: No module named collabwrapper.collabwrapper
Exited with status 1, pid 2117 data (<open file '<fdopen>', mode 'w' at 0x7f7e96f0f0c0>, '688cd1c0f3e7f674ceff5e6516598ab17dac0048')

See this discussion thread:

https://www.mail-archive.com/soas@lists.sugarlabs.org/msg02848.html

Comment 1 Peter Robinson 2017-10-29 12:27:06 UTC

*** This bug has been marked as a duplicate of bug 1507296 ***