GNOME Bugzilla – Bug 71606
segmentation violation when loading a portfolio
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-pm Severity: normal Version: 0.8.0 Synopsis: segmentation violation when loading a portfolio Bugzilla-Product: gnome-pm Bugzilla-Component: general Description: Create a new portfolia of stock symbols and save it using the portfolia save button. Then open the stock portfolia using the open button. The open portfolio shows the correct saved stock portfolios but when select when and click OK., a bug box appears showing a segv violation. 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)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x404cad19 in wait4 () from /lib/libc.so.6
+ Trace 17820
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-02-15 12:35 ------- Unknown version unspecified in product gnome-pm. Setting version to "0.9.4". The original reporter (wes@gnat.com) 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, dobez@fnmail.com.
I wasn't getting these reports because the default owner was wrong. Changed that and now I'm reassiging all of them.
*** This bug has been marked as a duplicate of 72734 ***