Bug 730585 - [abrt] openvrml-player-0.18.8-1.fc14: Process /usr/bin/openvrml-player was killed by signal 6 (SIGABRT)
Summary: [abrt] openvrml-player-0.18.8-1.fc14: Process /usr/bin/openvrml-player was ki...
Alias: None
Product: Fedora
Classification: Fedora
Component: openvrml
Version: 14
Hardware: i686
OS: Unspecified
Target Milestone: ---
Assignee: Braden McDaniel
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:bf5e42a2a17c408368c8669eaa6...
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-14 17:09 UTC by amreg
Modified: 2012-08-16 12:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-16 12:41:41 UTC

Attachments (Terms of Use)
File: backtrace (25.94 KB, text/plain)
2011-08-14 17:09 UTC, amreg
no flags Details

Description amreg 2011-08-14 17:09:33 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 26558 bytes
cmdline: openvrml-player
component: openvrml
Attached file: coredump, 55222272 bytes
crash_function: openvrml_player_curl_browser_host_load_url
executable: /usr/bin/openvrml-player
package: openvrml-player-0.18.8-1.fc14
rating: 4
reason: Process /usr/bin/openvrml-player was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1313341564
uid: 500

The OpenVRML player takes some time to launch.
The following error message is displayed : 

** (openvrml-player:7022): CRITICAL **: Browser creation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

No AVC from SELinux was raised. Eventually, the OpneVRML player windows opens.

The crash raised this second error :

ERROR:openvrml-player/curlbrowserhost.cpp:360:void openvrml_player_curl_browser_host_load_url(OpenvrmlPlayerCurlBrowserHost*, const char*): assertion failed: (host->priv->browser)
Abandon (core dumped)

How to reproduce
1. Did some 3D-modelling with Blender (2.58a).
2. Exported it in X3D format via the the built-in export script (provided with Blender). No changes in default export options seemed to be necessary. Got the x3d file with no export error.
3. Before sending it by mail, wanted to check the result by myself, by opening the resulting x3d file in openvrml-player (0.18.8, standard updated F14 package), which I just installed and was using for the first time.
4. The file extension used by Blender (*.x3d) doesn't seem to be recognised by the player "Open" dialog (I had to select "All files" as file type to see the X3D file appear in the list).
5. Trying to open the file crashed the player.

Comment 1 amreg 2011-08-14 17:09:35 UTC
Created attachment 518201 [details]
File: backtrace

Comment 2 Fedora End Of Life 2012-08-16 12:41:44 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 

Note You need to log in before you can comment on or make changes to this bug.