GNOME Bugzilla – Bug 79311
Fatal Crash
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-pim Severity: normal Version: 1.2.0 Synopsis: Fatal Crash Class: sw-bug Distribution: Red Hat Linux release 7.1 (Seawolf) System: Linux 2.4.9-31smp i686 unknown C library: glibc-2.2.4-24 C compiler: 2.96 glib: 1.2.9 GTK+: 1.2.9 ORBit: ORBit 0.5.7 gnome-libs: gnome-libs 1.2.8 libxml: 1.8.10 gnome-print: gnome-print-0.25 gnome-core: gnome-core 1.2.4 Description: I had just entered in some data, and clicked Save. It crashes. Which is a bummer, because I was shredding the paper information as I was entering it! Debugging information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x405a11d9 in __wait4 () from /lib/i686/libc.so.6
+ Trace 21073
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-04-20 10:14 ------- The original reporter (conic@games-usa.net) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-pim-maint@bugzilla.gnome.org.
*** This bug has been marked as a duplicate of 60965 ***
If this helps, I am using KDE 2. I was using the Gnome app from under KDE. I had entered in about 3 or 4 new records. I noticed while I was entering a new record, that each tab that I went to for that record, and entered information and then clicked Apply, another new record got added. I finished entering the information for all of the tabs for that record then went back and deleted out the other records. I continued to enter a few more records and did not see numerous records added for each one of those records. Also, I was cutting and pasting using Ctrl-X and Ctrl-V. Can't think of anything else.
I do recall doing the action stated by Jay in bug report #60965. I lost all of my data too. (Luckily it was in my Agenda PDA!) Thanks. - Danno
Thanks for your excellent report. I'm on the tracks of this bug and hope to get it fixed for gnome-pim 1.4.5.