Share

Xiphos Bible Study Software

Tracker: Bugs

9 gnomesword will not establish "firstrun" settings - ID: 1475903
Last Update: Comment added ( charcoal )

If built with --disable-debug, gnomesword will not do
its firstrun settings. Instead, it will immediately crash.

The temporary workaround is to first compile gnomesword
with "--enable-debug", run gnomesword, then recompile
gnomesword with "--disable-debug" after the settings
are created.


Nobody/Anonymous ( nobody ) - 2006-04-25 02:06

9

Closed

Works For Me

Terry Biggs

build

None

Public


Comments ( 5 )




Date: 2006-11-16 10:51
Sender: charcoalProject Admin


As mentioned on gnomesword-devel... No one else has ever been able to
reproduce it, there's been no action regarding it in 6 months, no one
currently building GS sees it -- so I'm closing this one. It may be that
this was from the old first-run code that isn't even active any more. If
in fact someone really still sees it, they can re-open this one or file a
new one.


Date: 2006-05-11 05:32
Sender: nobody

Logged In: NO

ok, I can pretty consistently repeat this problem now. First
of all, I configure gnomesword with the following:
$ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu
--mandir=/usr/share/man --infodir=/usr/share/info
--datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --enable-pspell --disable-gtk-doc
--libdir=/usr/lib64 --build=x86_64-pc-linux-gnu

Please note that I have sword-1.5.8 and this is repeatable
with the --enable-sword-svn option.

$ rm -rf ~/.gnomesword-2.0
$ make
$ || ( gnomesword2 ./src/gnome2/gnomesword2 ) #depends on if
you did a make install or not

Initiating GNOME session handler

<gnome error pop-up>The Application "gnomesword2" has quit
unexpectedly.You can inform the developers of what happened
to help them fix it. Or you can restart the application
right now.

Now then, I'm starting to think this is a bug in sword, not
gnomesword, because if I add a debug line or a printf
anywhere in the code before:
OLD_CODESET = (char*)sw_locale->getEncoding();
everything works fine and I no longer get the error message.

Again, this is a very odd error, but at least I've narrowed
down where it's failing now.

-Jon


Date: 2006-05-11 05:07
Sender: nobody

Logged In: NO

Terry, this is the oddest bug I have ever run into. I don't
experience it on many systems, but I do on quite a few.
Gnomesword (and it's the same for 2.1.7) is bailing out in
the src/backend/sword_main.cc in the
BackEnd::set_sword_locale() function. When I attempted to
put in standard printf("debugging messages"), everything
works correctly; my ~/.gnomesword-2.0 directory is created
and the program runs great. However, when I take them out, I
run into this bug again.


Date: 2006-04-26 14:19
Sender: squinky86

Logged In: YES
user_id=679187

2.1.6; gentoo

I'd like to add 2.1.6 to portage in Gentoo, but this issue
is holding me back a little. I can reproduce it on every
system here.


Date: 2006-04-26 12:54
Sender: tbiggsProject Admin

Logged In: YES
user_id=31632

I can't duplicate this.

Which release of gnomesword are you using?

which linux distro?

terry


Log in to comment.




Attached File

No Files Currently Attached

Changes ( 5 )

Field Old Value Date By
status_id Open 2006-11-16 10:51 charcoal
resolution_id None 2006-11-16 10:51 charcoal
close_date - 2006-11-16 10:51 charcoal
priority 5 2006-04-25 02:22 tbiggs
assigned_to nobody 2006-04-25 02:22 tbiggs