Bug 418041 – Epilicious confguration doesn't work

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 418041 - Epilicious confguration doesn't work


Summary:	Epilicious confguration doesn't work


Status:	RESOLVED FIXED

Product:	epiphany-extensions
Classification:	Deprecated
Component:	epilicious
Version:	2.18.x
Hardware:	Other Linux

Importance:	Normal major
Target Milestone:	2.18.x
Assigned To:	epiphany-extensions-maint
QA Contact:	epiphany-extensions-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-13 23:00 UTC by Reinout van Schouwen
Modified:	2007-03-14 08:23 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Attempt at fix (540 bytes, patch) 2007-03-14 08:23 UTC, Magnus Therning	none	Details \| Review

Description Reinout van Schouwen 2007-03-13 23:00:14 UTC

Select Tools > Epilicious Configuration. Nothing happens.

Console output:
(epiphany:15758): libglade-WARNING **: could not find glade file '/opt/gnome-2.18/share/epiphany-extensions/glade/epilicious-config.glade'
Traceback (most recent call last):

+ Trace 118412

File "/usr/lib/epiphany/2.18/extensions/epilicious.py", line 105 in _CB_Config
```
config = ConfigWindow()
```
File "/usr/lib/epiphany/2.18/extensions/libepilicious/config.py", line 28 in __init__
```
'epilicious-config.glade'), domain='epilicious')
```

RuntimeError: could not create GladeXML object

Comment 1 Reinout van Schouwen 2007-03-13 23:17:33 UTC

Part of the problem is that the /opt/gnome-2.18 ... path is hard coded into config.py.

Comment 2 Magnus Therning 2007-03-13 23:46:55 UTC

(In reply to comment #1)
> Part of the problem is that the /opt/gnome-2.18 ... path is hard coded into
> config.py.
> 

Are the glade files installed at all?

I was under the impression that the following lines in extensions/epilicious/Makefile.am would install the glade files (they did the last time I tested it):

 gladedir = $(pkgdatadir)/glade
 glade_DATA = \
         epilicious-config.glade \
         epilicious-progress.glade

$(gladedir) is used to provide the "hard coding" of the location in config.py (or rather in epilicious.py).

Comment 3 Reinout van Schouwen 2007-03-13 23:57:37 UTC

Yes, the files are installed under /usr/share/epiphany-extensions/glade/.

As you say, I found that these paths are dynamically generated
with the autogen/make/make install process. However something clearly went
wrong when generating the RPM containing this glade path.

Comment 4 Christian Persch 2007-03-14 00:30:26 UTC

The problem is that the epilicious.py file gets distributed. It's generated from the .in on build, and ends up in the tarball (so contains the paths from MY build); but it's not being regenerated when YOU build it.

Comment 5 Christian Persch 2007-03-14 00:35:09 UTC

Should be fixed in svn trunk and gnome-2-18.

Until 2.18.1, as a workaround, just delete epilicious.py and it'll be regenerated on build.

Comment 6 Magnus Therning 2007-03-14 08:23:11 UTC

Created attachment 84559 [details] [review]
Attempt at fix

Untested, but based on automake's documentation I'm fairly confident it'll work.