setup.py imports GTK
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GTG |
Fix Released
|
Medium
|
Unassigned |
Bug Description
bochecha on IRC reported that setup.py fails when running 'install'. This makes it _very_ hard for GTG to be packaged reliably into an RPM.
Here's the error:
1. + python setup.py install
2. Traceback (most recent call last):
3. File "setup.py", line 26, in <module>
4. import GTG
5. File "/home/
6. from gtk import glade
7. File "/usr/lib64/
8. _
9. File "/usr/lib64/
10. _gtk.init_check()
11. RuntimeError: could not open display
The problem is that setup.py imports GTG (which is ok, I guess), but GTG imports gtk and gtk needs a running X server. It's a bug that you need to have a running X to install GTG.
Changed in gtg: | |
importance: | Undecided → Medium |
milestone: | none → 0.2 |
status: | New → Confirmed |
Changed in gtg: | |
assignee: | nobody → Lionel Dricot (ploum) |
status: | Confirmed → In Progress |
Changed in gtg: | |
status: | Fix Committed → In Progress |
Changed in gtg: | |
status: | In Progress → Fix Committed |
Changed in gtg: | |
status: | Fix Committed → Fix Released |
Thanks Jonathan for reporting it, I just opened my Launchpad account 5 minutes ago :)
« This makes it _very_ hard for GTG to be packaged reliably into an RPM. »
This might be nit-picking, but it is actually inaccurate:
- it is not « very hard », it is « totally impossible » ^^'
- this issues shows up on Fedora only it seems, not on all RPM-based OSes.
After some investigation, this is due to this patch that we use in our pygtk package: http:// cvs.fedoraproje ct.org/ viewvc/ devel/pygtk2/ pygtk-nodisplay -exception. patch?view= markup
Thanks a lot for considering this as an issue in GTG. Let me know if there's some particular bazaar commit that I can try to see if that fixes it.