xiphos crashed with SIGSEGV in main_update_parallel_page()

[ginnyh532]

Binary package hint: xiphos

I was trying to use the edit preferences section where you set the parallel Bibles to be used. When I clicked on the first parallel to change it, Xiphos froze. It then shut down and I got the request to report the error. I am using Karmic Alpha 4.

ProblemType: Crash
Architecture: i386
Date: Fri Aug 14 10:45:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xiphos
NonfreeKernelModules: nvidia
Package: xiphos 3.1-1
ProcCmdline: xiphos
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x80add38 <main_update_parallel_page+1144>: cmpb $0x0,(%esi)
 PC (0x080add38) ok
 source "$0x0" ok
 destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xiphos
StacktraceTop:
 main_update_parallel_page ()
 on_combobox8_changed ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: xiphos crashed with SIGSEGV in main_update_parallel_page()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:main_update_parallel_page () at parallel_view.cc:862
on_combobox8_changed (combobox=0xcf1a9c0, user_data=0x0)
IA__g_cclosure_marshal_VOID__VOID (closure=0xd14dcf0,
IA__g_closure_invoke (closure=0xd14dcf0, return_value=0x0,
signal_emit_unlocked_R (node=<value optimized out>,

[Matthew Talbert (ransom1982)]

Hi, I'm an upstream Xiphos developer. Could you provide a little more information on this crash? Here are a few questions:
1. Was this the first time you had run Xiphos?
2. How many Bible modules did you have installed at the time?
3. Which parallel were you trying to set? (1,2,3,4,5)
4. Did you have the parallel view open at the time you were setting the modules?
5. If so, was it open in a tab, or the detached display?

Finally, could you attach ~/.xiphos/settings.xml to the report?

Thank you,
Matthew

[ginnyh532 (ginnyh532)]

1. It was the first time I had tried to use Xiphos after a re-install of Karmic.

2. I had 5 Bible modules installed at the time - KJV, WEB, ESV, NET and NETfree.

3. I was trying to set the first parallel.

4. I did not have the parallel view open while I was setting the modules.

I didn't know if ~/.xiphos/settings.xml will help you, because I reinstalled Karmic Alpha 5 recently. However, I repeated what I did to see if the problem still exists. I got Xiphos to crash again, so I am attaching the file. I had to copy it out of .xiphos to get the browse button on the form to work.

[Matthew Talbert (ransom1982)]

Sorry to not get back sooner, but we had a problem with Xiphos that prevented me from building on Karmic for a while. I was able to reproduce your bug under very specific conditions. Here's what I did:

1. run Xiphos for the first time (no Bibles installed or settings created)
2. during first run, install one Bible (ESV)
3. immediately after Xiphos started, I installed another Bible (NET)
4. opened preferences, went to parallel settings, changed first parallel to ESV
5. without closing preferences, changed the parallel to NET
6. segfault

Could you confirm that this is essentially what you did?

[Matthew Talbert (ransom1982)]

The bug is now reported upstream at https://sourceforge.net/tracker/?func=detail&aid=2871689&group_id=5528&atid=105528

[ginnyh532 (ginnyh532)]

That is essentially what I did. I had more Bible versions installed from the Sword repository, but I was trying to set the preference to NET and got the segfault.

Thank you for getting back to me. I don't know how many people you have to get back to on how many versions of Linux so I deeply appreciate this. :)

[Dimitri John Ledkov (xnox)]

This bug has been fixed upstream. It will land in Natty after 3.1.4 will be synced from Debian Experimental. Alternativly you can use ppa:pkgcrosswire/ppa now, which doesn't have this bug anymore. Thank you for reporting this issue.

[Dimitri John Ledkov (xnox)]

In natty 3.1.4-1