abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/libexec/clock-applet --oaf-activate-iid=OAFIID:GNOME_ClockApplet_Factory --oaf-ior-fd=28 component: gnome-panel executable: /usr/libexec/clock-applet kernel: 2.6.32.9-70.fc12.i686.PAE package: gnome-panel-2.28.0-16.fc12 rating: 4 reason: Process /usr/libexec/clock-applet was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Modify location in Clock 2. 3.
Created attachment 399856 [details] File: backtrace
Comment ----- dont sure what the cause was
How to reproduce ----- 1.add new location 2.change the temperature units 3.if it didn't crash its just my machine, usefull still to let me go through the bugreporting system, Comment ----- I added a new location (leeds england) followed by changing the unit for the temperature from F to C, it is at this point that the clock-applet crashed.
How to reproduce ----- 1. I clicked on the date/time GNOME panel applet. 2. I clicked the Edit button by Locations. 3. I removed the default Boston location. 4. I added my location (Mansfield, Ohio, USA). Comment ----- See above.
How to reproduce ----- 1. change weather location 2. 3. Comment ----- just changed my weather-location
How to reproduce ----- 1.edit location 2.set city 3.apply Comment ----- just edited location and saved
How to reproduce ----- 1.opened clock to change time zone as clock is 1 hour wrong. 2.attempted to load London timezone 3.Clock Crashed
How to reproduce ----- 1. Adding a new location to gnome clock on a fresh install
Adding a new location to gnome clock on a fresh install
How to reproduce ----- 1. I removed the date display from the clock. And it crashed.
How to reproduce ----- 1.Delete the default Location (Boston, USA) 2.Select the new Location (Santiago, Chile) 3.Acept Comment ----- I've entered the wrong credentials once.
*** Bug 553853 has been marked as a duplicate of this bug. ***
*** Bug 583950 has been marked as a duplicate of this bug. ***
*** Bug 586673 has been marked as a duplicate of this bug. ***
*** Bug 587065 has been marked as a duplicate of this bug. ***
*** Bug 587840 has been marked as a duplicate of this bug. ***
*** Bug 590246 has been marked as a duplicate of this bug. ***
How to reproduce ----- 1. Expand the clock applet 2. Click Edit button next to Locations. 3. Here I have removed the only one saved Location i had (Prague). 3. Then added new Location (typing Prague again - I selected it using autofill) 4. Confirm with Ok -> Close -> An Internal system error has occured Comment ----- The error occures everytime I repeat this procedure. Creating Location without deleting the previous one doesn't generate this error.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.