Bug 650128 - [abrt] lock-keys-applet-1.0-20.fc14: raise: Process /usr/libexec/lock-keys-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] lock-keys-applet-1.0-20.fc14: raise: Process /usr/libexec/lock-keys-ap...
Keywords:
Status: CLOSED DUPLICATE of bug 659434
Alias: None
Product: Fedora
Classification: Fedora
Component: lock-keys-applet
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: cq92j9y+rlkr0w
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f76e62443545694a3331c6180c4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-05 10:20 UTC by edo
Modified: 2010-12-04 16:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-04 16:23:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.78 KB, text/plain)
2010-11-05 10:20 UTC, edo 		no flags Details
View All

Description edo 2010-11-05 10:20:16 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/lock-keys-applet --oaf-activate-iid=OAFIID:GNOME_LockKeysApplet_Factory --oaf-ior-fd=22
component: lock-keys-applet
crash_function: raise
executable: /usr/libexec/lock-keys-applet
kernel: 2.6.35.6-48.fc14.x86_64
package: lock-keys-applet-1.0-20.fc14
rating: 4
reason: Process /usr/libexec/lock-keys-applet was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1288952395
uid: 501

How to reproduce
-----
1. start helper
2.
3.
Comment 1 edo 2010-11-05 10:20:19 UTC 
Created attachment 458045 [details]
File: backtrace
Comment 2 edo 2010-11-08 11:35:15 UTC 
Package: lock-keys-applet-1.0-20.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Start Help in num-lock applet
2.
3.
Comment 3 edo 2010-11-09 11:57:09 UTC 
Package: lock-keys-applet-1.0-20.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. click Help
2.
3.
Comment 4 cq92j9y+rlkr0w 2010-12-04 16:23:00 UTC 

*** This bug has been marked as a duplicate of bug 659434 ***
Note You need to log in before you can comment on or make changes to this bug.