Bug 506325 - Access violation in skychart
Access violation in skychart
Product: Fedora
Classification: Fedora
Component: skychart (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Lubomir Rintel
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-16 13:09 EDT by Martin Mancuska
Modified: 2010-06-28 09:03 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 09:03:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
full backtrace (5.33 KB, text/plain)
2009-07-28 12:43 EDT, Tomáš Bžatek
no flags Details

  None (edit)
Description Martin Mancuska 2009-06-16 13:09:46 EDT
Description of problem:
Skychart reports this error message after its launch:
"Load zlib: Access violation.
Something go wrong during program initialization. We must now close.
Please try to reinstall the program."

I tried to remove all config files, reinstall it. without any effect. 

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

How reproducible:
just install from Fedora repository. 

Steps to Reproduce:
1. install skychart
2. launch it
3. error is shown
Comment 1 James 2009-07-07 18:16:05 EDT
I find installing the i586 version works.
Comment 2 Tomáš Bžatek 2009-07-28 12:43:22 EDT
Created attachment 355439 [details]
full backtrace

GDB is weird, reporting call from pu_main.pas:1510 but on line 1510, there's only simple debug print.

I think the real problem are lines 1609 - 1616 in pu_main.pas:

if zlib<>0 then begin
  gzopen:= Tgzopen(GetProcAddress(zlib,'gzopen'));
  gzread:= Tgzread(GetProcAddress(zlib,'gzread'));
  gzclose:= Tgzclose(GetProcAddress(zlib,'gzclose'));
  gzeof:= Tgzeof(GetProcAddress(zlib,'gzeof'));
end else zlibok:=false;

...and insufficient check for missing symbols. The const libz = 'libz.so' in u_constant.pas:558 might be source of problems as the RTL chooses 32bit library on 64bit system (wrong library search path).
Comment 3 Bug Zapper 2010-04-27 10:59:23 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
Comment 4 John Duchek 2010-05-15 14:46:50 EDT
This error is only in the 64 bit.  It installs but gets an access violation when it tries to us zlib  
It says:  Load zlib: Access violation and shuts down.
Comment 5 Bug Zapper 2010-06-28 09:03:59 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

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