Bug 560182

Summary: [abrt] crash in anyremote-5.1-1.fc12
Product: [Fedora] Fedora Reporter: Phil <phil.ingram>
Component: anyremoteAssignee: anyremote <anyremote>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anyremote
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:090bc93a861df2d158941679d32161ac1b3c58ac
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-03 19:29:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
output of requested command none

Description Phil 2010-01-30 05:45:58 UTC 
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: anyremote -fe 5050 -f /usr/share/anyremote/cfg-data/Server-mode/all-in-one2.cfg
comment: controlled amarok with anyremote
component: anyremote
executable: /usr/bin/anyremote
kernel: 2.6.31.12-174.2.3.fc12.i686.PAE
package: anyremote-5.1-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. paired LG kc910
2. configured anyremote for phone - all in 1 v2
3. connected phone
4. started amarok
5. pushed a few buttons
crash...
Comment 1 Phil 2010-01-30 05:46:00 UTC 
Created attachment 387702 [details]
File: backtrace
Comment 2 anyremote 2010-01-30 17:09:24 UTC 
Could You please run:
anyremote -fe 5050 -f
/usr/share/anyremote/cfg-data/Server-mode/all-in-one2.cfg -log
reproduce crash
and then send $HOME/.anyremote/anyremote.log
Comment 3 Phil 2010-01-31 04:51:23 UTC 
Created attachment 387808 [details]
output of requested command

* issued command from terminal
* connected phone ok
* vol up & vol down = crash
Comment 4 anyremote 2010-02-03 19:29:39 UTC 
Fixed in anyremote v5.1.1
(added call dbus_threads_init_default() to make proper thread initialization)