After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 133835 - Portfolio Manager crash
Portfolio Manager crash
Status: RESOLVED DUPLICATE of bug 72734
Product: gnome-pm
Classification: Deprecated
Component: general
0.9.4
Other Linux
: Normal normal
: ---
Assigned To: Rodney Dawes
Rodney Dawes
: 133834 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-02-09 01:23 UTC by Dr. Jim Metcalf
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dr. Jim Metcalf 2004-02-09 01:23:12 UTC
MESSAGE received from GNOME:

Application "gnome-pm" (process 5941)
has crashed due to fatal error
(Segmentation fault)
Comment 1 Rodney Dawes 2004-02-09 08:09:33 UTC
*** Bug 133834 has been marked as a duplicate of this bug. ***
Comment 2 Rodney Dawes 2004-02-09 08:15:30 UTC

*** This bug has been marked as a duplicate of 72734 ***
Comment 3 Dr. Jim Metcalf 2004-02-10 21:40:04 UTC
This says the problem was resolved, but PM STILL does not work.  I get
the same message any time I try to open the portfolio I've set up.
Comment 4 Rodney Dawes 2004-02-11 00:23:55 UTC
RESO DUP != RESO FIXED. I didn't claim it was fixed. And why does this
have a GNOMEVER2.5 keyword? gnome-pm is not a part of the desktop
release. It also hasn't been touched in years. This is a duplicate bug
that is the same as every other crash that has been reported against
gnome-pm in the last 2.5-3 years or so. The only reason anyone is
getting this crash, is because Lindows is shipping they shouldn't.
They just took the latest version, threw it in a package, and called
it "Stock Portfolio Manager" crash. Even if the bug was fixed, just
running the program again wouldn't get you the new version. You would
need Lindows to ship an update, or build the thing yourself from CVS.
Please don't reopen this again, unless you have a reliable stack trace
that is different from the trace in the bug this is marked a duplicate
as. Otherwise, if you have any actually useful data, like the
portfolio file that crashes, or something, you can attach it to that bug.

*** This bug has been marked as a duplicate of 72734 ***
Comment 5 Dr. Jim Metcalf 2004-02-11 01:26:07 UTC
Rodney -

Well, 'scuse the hell outa me.  How was I supposed to know?

I certainly won't bother you again.

BTW - you might want to temper the tone of your messages.  Just good
customer relations.  And YOU might want to contact Lindows on behalf
of your product.