abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 12448 bytes cmdline: gnomad2 component: gnomad2 Attached file: coredump, 21827584 bytes crash_function: strlen executable: /usr/bin/gnomad2 kernel: 2.6.35.13-92.fc14.i686.PAE package: gnomad2-2.9.4-8.fc14 rating: 4 reason: Process /usr/bin/gnomad2 was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1308018139 uid: 500 comment ----- connect with Asus Eee pad Transformer Device 0 (VID=0b05 and PID=4e0f) is UNKNOWN. even though I put it in the udev rules. How to reproduce ----- 1. just started gnomad2 up with Asus Eee Pad Transformer connected 2. 3.
Created attachment 504580 [details] File: backtrace
gnomad2-2.9.5-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gnomad2-2.9.5-1.fc14
Package gnomad2-2.9.5-1.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnomad2-2.9.5-1.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gnomad2-2.9.5-1.fc14 then log in and leave karma (feedback).
gnomad2-2.9.6-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gnomad2-2.9.6-1.fc14
gnomad2-2.9.6-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.