Opened 15 years ago

Closed 15 years ago

#831 closed defect (fixed)

WebActivity not launching in sugar-jhbuild

Reported by: RafaelOrtiz Owned by: sascha_silbe
Priority: Unspecified by Maintainer Milestone: Unspecified
Component: sugar-jhbuild Version: Unspecified
Severity: Unspecified Keywords:
Cc: Distribution/OS: Ubuntu
Bug Status: Unconfirmed

Description

i got something like

from hulahop._hulahop import shutdown
import error:libxul.so cab open shared object: file or directory doesn't exists

Attachments (1)

hulahoperror.txt (3.6 KB) - added by RafaelOrtiz 15 years ago.

Download all attachments as: .zip

Change History (13)

comment:1 Changed 15 years ago by RafaelOrtiz

correction: can't open shared object: file or directory doesn't exist.

comment:2 Changed 15 years ago by sascha_silbe

  • Component changed from sugar to sugar-jhbuild
  • Owner changed from tomeu to sascha_silbe
  • Status changed from new to assigned

Which distribution? What does

./sugar-jhbuild depscheck

say?

comment:3 Changed 15 years ago by RafaelOrtiz

Hi sascha.

This is on ubuntu 8.10.

depscheck doesn't give any output..

comment:4 Changed 15 years ago by sascha_silbe

  • Distribution/OS changed from Unspecified to Ubuntu

How exactly are you starting Sugar? Did "./sugar-jhbuild build" finish successfully?
Can you attach the full log, please?

Changed 15 years ago by RafaelOrtiz

comment:5 Changed 15 years ago by RafaelOrtiz

re building gives this (attached)

comment:6 Changed 15 years ago by sascha_silbe

OK, Browse obviously can't work if hulahop is not built correctly.
Am I guessing right that you've used "./sugar-jhbuild build" and since updated xulrunner on your distro (there was a security update recently)?
In that case the following tip from the dealing with dependencies section of the JHBuild wiki page should help:

hulahop stopped building because I had installed a more recent version of xulrunner on my machine. The workaround was to rm -rf ~/sugar-jhbuild/source/hulahop and then run update and build again.

The root cause of this problem is #137.

comment:7 Changed 15 years ago by RafaelOrtiz

While trying this solution i had a problem with jhbuild itself...


Traceback (most recent call last):

File "/sugar-jhbuild/jhbuild/jhbuild/config.py", line 115, in init

execfile(_defaults_file, self._config)

File "/sugar-jhbuild/jhbuild/jhbuild/defaults.jhbuildrc", line 11, in <module>

modulesets_dir = os.path.join(SRCDIR, 'modulesets')

NameError: name 'SRCDIR' is not defined
sugar-jhbuild: could not load config defaults


This trace appears while doing sugar-jhbuild update

comment:8 Changed 15 years ago by sascha_silbe

Yes, had the same error yesterday, seems like Gnome broke Jhbuild.
Not sure if I'll get around to report/fix/do a work-around before SugarCamp, sorry.

comment:9 Changed 15 years ago by RafaelOrtiz

where can we report the bug to gnome ?.

comment:10 Changed 15 years ago by RafaelOrtiz

If it helps there is a bug report on Gnome's bugzilla

http://bugzilla.gnome.org/show_bug.cgi?id=582490

comment:11 Changed 15 years ago by RafaelOrtiz

This is the response by the gnome people


CC| |fpeters@…

Status|UNCONFIRMED |RESOLVED

Resolution| |FIXED


Your jhbuild start script is too old; perhaps you have an old copy in ~/bin/
while the new one got installed in ~/.local/bin/, or you didn't run make
install.

I commited a change so it detects that situation and display an informative
message:

jhbuild: Obsolete jhbuild start script, do run 'make install'

commit 55749bf95c0a09b5a16a9be578230a93c1f034fd
Author: Frédéric Péters <fpeters@…>
Date: Thu May 14 00:30:19 2009 +0200

abort on obsolete start script (GNOME #582490)


comment:12 Changed 15 years ago by RafaelOrtiz

  • Resolution set to fixed
  • Status changed from assigned to closed
Note: See TracTickets for help on using tickets.