FS#37339 - [transmageddon] crash with segmentation fault

Attached to Project: Community Packages
Opened by Miguel (mmf1902) - Monday, 14 October 2013, 20:04 GMT
Last edited by Balló György (City-busz) - Monday, 04 November 2013, 16:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Balló György (City-busz)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Transmageddon fails to start after system upgrade. It crash with segmentation fault.


Additional info:
* package version(s)

transmageddon 0.25-1
gst-plugins-base 1.2.0-1
gtk3 3.10.1-1
libnotify 0.7.6-1
python-gobject 3.10.0-1
gst-libav 1.2.0-1
gst-plugins-bad 1.2.0-1
gst-plugins-base 1.2.0-1
gst-plugins-base-libs 1.2.0-1
gst-plugins-good 1.2.0-1
gst-plugins-ugly 1.2.0-1
gst-python 1.1.90-2

* config and/or log files etc.
Terminal output:

[miguel@miguel ~]$ LC_ALL=C transmageddon
/usr/bin/transmageddon: line 3: 4239 Segmentation fault (core dumped) python3 transmageddon.py

Steps to reproduce:
Just call the program from command line or genome-shell
This task depends upon

Closed by  Balló György (City-busz)
Monday, 04 November 2013, 16:08 GMT
Reason for closing:  Upstream
Comment by Balló György (City-busz) - Saturday, 02 November 2013, 23:24 GMT
I can't reproduce the problem.

Please report the problem to the upstream developers[1] with a proper backtrace[2].

[1] https://bugzilla.gnome.org/browse.cgi?product=transmageddon
[2] https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces

Loading...