Abiword crashes when pasting images from Firefox

Bug #1266615 reported by Gulliver Moy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
abiword (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Simply try to copy an image from Firefox and paste it into Abiword and it comes up with the 'Ubuntu has encountered a problem' dialogue. Subsequent attempts just result in a new line. Text pastes fine, haven't tried other sources of images e.g. different browser.

A friend who runs Xubuntu 12.?, was complaining of this, then another friend running 13.10 32bit said the same thing was happening. I am running 13.10 64bit, and can also replicate the error. My abiword version is 3.0.0.

Can not believe I'm not finding more on this by searching, seems like a major problem affecting all three of the Xubuntu users I know on different versions. All I came across was a bunch of very similar problems affecting older versions of Abiword - One had a fix in a later release, the others were listed as invalid due to how they were reported.

... I'm guessing that's going to happen to this post because I haven't done done what those OPs were told to, but I have tried and don't get it. This is what I'm talking about:
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/993543/comments/3
I've followed those steps and a window opens so I click continue and it just disappears, and if it has created a crash report on here, I have no idea where it is to follow it

... Sorry, new to this

Anyway, I can get the following error by running Abiword from the Terminal and then Pasting:

** (abiword:7678): CRITICAL **: char* UT_go_url_resolve_relative(const char*, const char*): assertion 'ref_uri != NULL' failed

If you want me to do anything to give you more information or post this in a different format , just let me know. Cheers.

Revision history for this message
penalvch (penalvch) wrote :

Gulliver Moy, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install abiword-dbg && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and it does nothing, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in abiword (Ubuntu):
status: New → Invalid
Revision history for this message
Elfy (elfy) wrote :

@ penalvch - why would there be a crash report - it's not a crash - it's a bug :)

also try and bear in mind that gedit is default in Ubuntu - this is an Xubuntu bug - so could be leafpad or mousepad depending on release

Revision history for this message
Gulliver Moy (gully-moy) wrote :

Thank you both for your help. As I already said, I did try to go through those steps but the instructions I followed failed to mention the part about commenting out 'problem_types': ['Bug', 'Package']. Now I can successfully create Launchpad reports via ubuntu-bug using the terminal. Should have known there would be a bug in reporting bugs :-D

For anyone who find this in their search for a fix my new and hopefully valid report can be found here:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1267289

I do not know whether it constitutes a crash or a bug as I don't know exactly where the two differ. Abiword does not close on my machine when the error happens but a report is created in /var/crash. Does that mean it is a crash?

And precisely - not gedit, I use mousepad.

Cheers.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.