Bug 560182 - [abrt] crash in anyremote-5.1-1.fc12
Summary: [abrt] crash in anyremote-5.1-1.fc12
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anyremote
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: anyremote
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:090bc93a861df2d158941679d32...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-30 05:45 UTC by Phil
Modified: 2010-02-03 19:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-03 19:29:39 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (15.05 KB, text/plain)
2010-01-30 05:46 UTC, Phil 		no flags Details
output of requested command (161.43 KB, application/octet-stream)
2010-01-31 04:51 UTC, Phil 		no flags Details
View All

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)
Note You need to log in before you can comment on or make changes to this bug.