FS#18473 - [xiphos] opens nautilus instead of modules

Attached to Project: Community Packages
Opened by mike green (greenbehemoth) - Friday, 26 February 2010, 09:55 GMT
Last edited by Stefan Husmann (stefanhusmann) - Sunday, 25 April 2010, 20:07 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Stefan Husmann (stefanhusmann)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

On launching xiphos, 15 instances of nautilus are opened instead of installed modules. Modules are listed in modules pane as normal, but all other panes are empty. Selecting individual modules opens further instances of nautilus instead of the modules themselves.

In addition, any attempt to use Module Manager results in xiphos crashing with the following error:

Gdk-CRITICAL **: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed


Additional info:

* package version(s)
xiphos 3.1.2-1
arch up-to-date


Steps to reproduce:
1. Run xiphos (multiple nautilus)
2. Select modules (more nautilus)
3. Run Module Manager (program crash)
This task depends upon

Closed by  Stefan Husmann (stefanhusmann)
Sunday, 25 April 2010, 20:07 GMT
Reason for closing:  Fixed
Comment by Matt Braymiller (Rumor) - Monday, 01 March 2010, 12:46 GMT
I also have this same problem. I removed the program and ALL dependencies / dotfiles. A reinstall starts as normal by invoking the module manager. When I click to connect to the remote, I get the same error message as above and the program windows closes.

Gdk-CRITICAL **: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed

Comment by Stefan Husmann (stefanhusmann) - Tuesday, 02 March 2010, 14:11 GMT Comment by mike green (greenbehemoth) - Tuesday, 02 March 2010, 17:38 GMT
Thanks for looking at this Stefan. I have confirmed the bug on sourceforge and will monitor.

EDIT: Actually there are two bug reports on sourceforge, the other one is here:
https://sourceforge.net/tracker/index.php?func=detail&aid=2958644&group_id=5528&atid=105528
Everyone is reporing two separate but similar issues. Could be they are related. As you can see I have stuck my nose into both threads ;)
Comment by Francisco Rivas (fjrivas) - Friday, 12 March 2010, 06:43 GMT
Hi, I have the same issue here :

My System : x86_64, 2.6.32
I Installed Xiphos using Pacman : When I run the application from console (the very first time) It recommends me to retrieve information from CrossWire but when it reach 100% the application crash displaying a "Segmentation Fault".

I tried downloading some modules and copying them in the rigth place and the application starts normally without telling me to refresh the information from CrossWire but when I choose the Bible text I get no information, I mean, clicking (for example) in Romanos 2,3 I got no text at all.

So unistalled the application and installed, via yaourt, the svn version got the same issue plus the another one mentioned above, but instead of nautilus it opens 15+/- thunar instances.

Thanks Stefan and all the maintainers, it is really good to find this kind of software for Linux, seriously. God Bless you all! :D
Comment by Eric (TripleE) - Sunday, 21 March 2010, 20:52 GMT
I can confirm that this is still an issue for me on my i686 and x86_64 machines.
Comment by mike green (greenbehemoth) - Monday, 22 March 2010, 09:52 GMT
[EDIT: Xiphos 3.1.3 has just been released today on SourceForge http://sourceforge.net/projects/gnomesword which kind of makes what follows redundant. If Module Manager is still broken you can still install modules manually by doing what I say in the last paragraph.]

If you want a working (almost) Xiphos in the meantime you might try the latest svn by running the following commands (please note that I can only get the installation to work by doing all of it as root):

svn co https://gnomesword.svn.sourceforge.net/svnroot/gnomesword/trunk xiphos
cd xiphos
./autogen.sh --prefix=/usr --disable-maintainer-mode
make
make install

Limitations:

Module Manager still not working and existing sword modules not recognized for me (but I think I'd lost my config files in the mod.d folder, so you might be ok). You can manually download and install modules by following the links here: http://xiphos.org/links/. Just download modules (raw zips) to your ~/.sword folder and then run:

cd ~/.sword
unzip ModuleFileName.zip
Comment by Eric (TripleE) - Monday, 05 April 2010, 00:55 GMT
I have just downloaded community-testing/xiphos 3.1.3-2. The Module Manger still will not work, but everything else that I have tested appears to work.
NOTE: Using x86_64.
Comment by Stefan Husmann (stefanhusmann) - Monday, 05 April 2010, 01:15 GMT
Can you please test the following PKGBUILD and patch for the sword library? See

https://sourceforge.net/tracker/?func=detail&atid=105528&aid=2979674&group_id=5528

for explanation.
Comment by Stefan Husmann (stefanhusmann) - Monday, 05 April 2010, 02:05 GMT
Can you please test the following PKGBUILD and patch for the sword library? See

https://sourceforge.net/tracker/?func=detail&atid=105528&aid=2979674&group_id=5528

for explanation.

Loading...