abrt 1.0.2 detected a crash. How to reproduce ----- 1. Try play via proxychains 2. open play list of the radio stations Attached file: backtrace cmdline: audacious2 component: audacious executable: /usr/bin/audacious2 kernel: 2.6.31.9-174.fc12.i686 package: audacious-2.1-7.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault)
Created attachment 382469 [details] File: backtrace
It's another NULL-pointer dereference crash in neon transport plugin. As why the session socket is 0, dunno yet. Please be so kind and try to reproduce with Audacious 2.2 in the updates-testing repository (or, alternatively, in Fedora development): https://admin.fedoraproject.org/updates/F12/FEDORA-2010-0028
I'm especially interested in whether this can be reproduced with a backtrace with audacious-plugins-2.2-10.fc12. [If you need additional 3rd party plugin packages, it's possible to rebuild their src.rpm from Fedora development.]
First brief look at proxychains. Can't get it to work at all: |DNS-request| club-high.rautemusik.fm |DNS-response|: club-high.rautemusik.fm is not exist Had to disable "proxydns" option. Then got: $ proxychains audacious ProxyChains-3.1 (http://proxychains.sf.net) |S-chain|-<>-217.237.148.102:80-<><>-195.13.63.136:80-<--denied ERROR: neon: neon.c:629 (open_request): <0x893c928> Could not open URL: 5 (0) ERROR: neon: neon.c:631 (open_request): <0x893c928> neon error string: Could not connect to server: Connection refused ERROR: neon: neon.c:919 (neon_aud_vfs_fopen_impl): <0x893c928> Could not open URL ** (audacious:10864): WARNING **: Unable to read from http://club-high.rautemusik.fm, giving up. ** (audacious:10864): WARNING **: Cannot play http://club-high.rautemusik.fm: no decoder found. [...] So, no test-case yet.
*** Bug 558225 has been marked as a duplicate of this bug. ***
Third-party add-on packages for Audacious 2.2 are available in their respective -updates-testing repository. Please give feedback on the Audacious 2.2 test update: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-0028 There are no plans to continue with Audacious 2.1.
*** This bug has been marked as a duplicate of bug 562164 ***