Bug 621007 - [abrt] crash in gnome-applets-1:2.30.0-1.fc13: do_idle_run_queue: Process /usr/libexec/gweather-applet-2 was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-applets-1:2.30.0-1.fc13: do_idle_run_queue: Process /us...
Keywords:
Status: CLOSED DUPLICATE of bug 590834
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:85c12e0288f312071cc9b738731...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-03 23:58 UTC by Matthew Saltzman
Modified: 2010-11-08 09:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 09:31:15 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (15.20 KB, text/plain)
2010-08-03 23:58 UTC, Matthew Saltzman 		no flags Details
View All

Description Matthew Saltzman 2010-08-03 23:58:31 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gweather-applet-2 --oaf-activate-iid=OAFIID:GNOME_GWeatherApplet_Factory --oaf-ior-fd=23
comment: Changed location in the Preferences dialog
component: gnome-applets
crash_function: do_idle_run_queue
executable: /usr/libexec/gweather-applet-2
global_uuid: 85c12e0288f312071cc9b738731e23b13d1e8f01
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: gnome-applets-1:2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/gweather-applet-2 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Open Preferences dialog
2. Select a new location
3. Close dialog
Comment 1 Matthew Saltzman 2010-08-03 23:58:33 UTC 
Created attachment 436405 [details]
File: backtrace
Comment 2 Jeff Raber 2010-11-08 09:31:15 UTC 

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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