Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 103150 - Postinstall causes segfault in scrollkeeper-update
Summary: Postinstall causes segfault in scrollkeeper-update
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: scrollkeeper
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: CambridgeBlocker
TreeView+ depends on / blocked
 
Reported: 2003-08-27 05:42 UTC by Fulton Green
Modified: 2007-04-18 16:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-08-29 12:21:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Fulton Green 2003-08-27 05:42:03 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
When I install the latest gnome-applets package, I get an indication that the
scrollkeeper-update program has hit a segmentation fault.  This appears to be a
consequence of the postinstall scriptlet.

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1. Install Severn.
2. Update scrollkeeper from Raw Hide.
3. Update gnome-applets (and required dependencies) from Raw Hide.
    

Actual Results:  I get a nastygram saying that scrollkeeper-update has hit a
segmentation fault.

Expected Results:  I would not have seen any errors.

Additional info:

Here's the exact message:

/var/tmp/rpm-tmp.12716: line 2:  3557 Segmentation fault      scrollkeeper-update

Comment 1 Alexander Larsson 2003-08-29 12:21:59 UTC
fixed in 0.3.12-2.


Note You need to log in before you can comment on or make changes to this bug.