Bug 550868

Created attachment 380555 [details]
File: backtrace

Would you provide in detail the procedure to reproduce this
issue?

I thought I did provide step by step details:
            running alexandria 0..6.6-beta1
            pasting image of cover into properties
            save record
            crash

(In reply to comment #3)
> I thought I did provide step by step details:
>             running alexandria 0..6.6-beta1
>             pasting image of cover into properties
>             save record
>             crash  

Please explain in detail how to reproduce the issue
so that we can reproduce the issue by doing exactly
what you wrote.

- Where does "image of cover" appear?
  If some image file is needed, then please attach it.
  and what does "properties" mean?
- What does "save record" mean?

Please explain like:
- First clean up ~/.alexandria by $ rm -rf ~/.alexandria
- From terminal type $ alexandria
- On the launched window choose "Library -> Add Book"
- On the poped up window write "4-xxxxx" on "ISBN" column
- Then click "Add"
....
....
(By the way please clean up ~/.alexandria first so that we can
 reproduce the bug from the beginning)

1. Start alexandria 0..6.6-beta1
2. click on the "+" to add a new book to your library
3. type in the books ISBN number or do a search using title, author, etc.
4. Repeat until the resulting entry does not have a graphic associated with it
5. double click the entry or right click and select "properties"
6. in the upper right hand corner, you will see a square with a blank cover on it
   "cover" is above the box and if you hover your mouse over it, you will see
   "click to select cover"
7. Browse to amazon.com or barnes and noble, search for the book you entered,
   find a graphic of it's cover, right click on the graphic, save it to your HD
8. Click on "click to select cover" (aka, blank cover)
9. Browse to where you saved the graphic
10. double click on the graphic file or single click and click on "open"
    the grapic of the books cover is inserted
11. click on "save"

CRASH

Alexandria also crashes when I move entries into another library (do I need to give step by step instructions?) particularly when the graphic is one I manually inserted (versus one alexandria selected).

I don't know what you mean by "clean up ~/.alexandria" all that is in there are the data for the entries that I have made. Are you suggesting that I delete all my data and start over (yes I know that I can make a backup)????? Why?

So would you provide us the example what book you actually
added and what graphics file you chose for cover file?
It may be book or image specific.

(In reply to comment #5)
> I don't know what you mean by "clean up ~/.alexandria" all that is in there are
> the data for the entries that I have made. Are you suggesting that I delete all
> my data and start over (yes I know that I can make a backup)????? Why?  

To make it clear if the bug is reproducible for everybody or
some specific condition is needed to reproduce the issue.
Of course $ rm -rf ~/.alexandria can be replaced with 
$ mv ~/.alexandria ~/.alexandria.save

> Alexandria also crashes when I move entries into another library (do I need to
> give step by step instructions?)

Please give up the detailed procedure (and for this file another seperated
bug)

No.
I lost count as to the number of crashes. It was well over a dozen, probably closer to two dozen. It happened *every time* I imported a graphic. It happened with png files, with jpeg files and with gif files. I could zip the directory where I saved my images and my /.alexandria directory if that would help but it will have to wait until I boot back into linux.

How does eliminating *my* /.alexandria directory show whether or not the bug is reproducible for *everybody?*

(In reply to comment #7)
> I could zip the directory
> where I saved my images and my /.alexandria directory if that would help

It is appreciated.

> How does eliminating *my* /.alexandria directory show whether or not the bug is
> reproducible for *everybody?*  

~/.alexandria of you and me and the upstream is quite different.
The only trustworthy way to reproduce the bug for everybody is
to try to reproduce the bug from the beginning (i.e. with no
~/.alexandria)

*** Bug 550898 has been marked as a duplicate of this bug. ***

Created attachment 380670 [details]
copy if the version of alexandria that I installed

Created attachment 380672 [details]
copy of my ~/.alexandria

Created attachment 380674 [details]
graphics I used to import into alexandria

I've attached a copy of the beta version of Alexandria that I installed as well as my ~/.alexandria directory and a folder containing the graphics that I imported.

The images that I scanned are (I think) substantially larger than the ones I copied from amazon.com. Alexandria crashed with almost every import and, as I noted earlier, I stopped paying attention to pop up messages from ABRT but some of those messages included something to the effect that the "file was too big, adjust size in ABRT preferences" (something like that). If ABRT is including a copy of the graphic, I can see where the file size would get large. Otherwise, not sure what it's talking about.

I renamed /.alexandria and added ISBDN numbers 0452267404 and 0399130397
I did not like the cover for the first so replaced it with dark tower III wastelands.jpeg; the second did not come up with a cover after entering the ISBDN so I used skeleton crew.jpeg. Unfortunately, no crash.

trying a png file, I entered "dark tower VI song of susanna.PNG" (after searching for the book by title). Still no crash.

I can't recall the order I first entered the books and I had first set up the collection using the latest release version of alexandria (0.6.5?) and then installed the beta.

It doesn't look like I can recreate the crash. At least not until I send this and start entering more books into the collection.

Well, if you use the original ~/.alexandria (which you say causes
alexandria crash) and try

$ alexandria --debug

what message does alexandria show on the terminal?

Created attachment 380879 [details]
output of $ alexandria --debug

output attached in alexandria --output.txt

(In reply to comment #13)
> Well, if you use the original ~/.alexandria (which you say causes
> alexandria crash) and try
> 
> $ alexandria --debug
> 
> what message does alexandria show on the terminal?  

Ah, what I meant is that I want to see what $ alexandria --debug
shows when alexandria crash occurs. If alexandria crash is
still reproducible, would you attach the output? Thank you.

ahhhh ok.
next crash, that's what I'll do. Added about 75 books last night but no crash (I didn't import any graphics either). 

the beta release showed up as an update tonight. yum reported it as version 0.6.6-0.3 beta 1; I do not recall 0.3 being part of the version I downloaded. It's not part of the file name...

So.. this update may have fixed the problem. I'll see if i can't spend some time scanning tomorrow so as to import some graphics.

Created attachment 381115 [details]
output from $ alexandria --debug (after a crash)

Bug number 550898 may be a duplicate of this one.

In this case I was in the process of adding books to my (PSYCH) library. I wanted to add books into another library (RELIGIOUS). Instead of closing the add book window and clicking on the RELIGIOUS library so as to make that active, I used the drop down window in the add book dialog box to select the RELIGIOUS library. I typed in the ISBDN number 0385235852. The application crashed.

I tried to repeat the process using the same ISBDN number and I got the message that the book was already in the library. when I pulled up the properties of that book I see the ISBDN 9780385235853 (978 appears to be added as a prefix to all the ISBDN numbers but the last digit is 3 not 2).

I repeated the process with a different book (ISBDN 0060669330)-- with the psych library showing and selecting "religious" from the drop down menu in the add book dialog box. The application crashed (bug # 551630). Upon restart, the book was added to the correct library, the ISBDN number had the 978 prefix and the last digit was "1" not "0." If I try to add ISBDN number 0060669330 it is reported as being in my collection (with the correct title associated with it). Is the displayed ISBDN always off by one digit?

*** Bug 551630 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.