Mantis - libz1
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
4373 | regular use | major | always | 2010-03-26 15:03 | 2010-09-26 04:50 |
|
|||||
Reporter: | skayser | Platform: | |||
Assigned To: | hson | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | |||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | |||
|
|||||
Summary: | 0004373: zlib 1.2.4 breaks wireshark (maybe others too) | ||||
Description: |
After upgrading a Solaris 10 system running with current/ I could observe zlib related problems with wireshark just like reported elsewhere: FS#18061 - [wireshark] packet capture trouble with latest zlib http://bugs.archlinux.org/task/18061 [^] For now, downgrading to zlib 1.2.3 helped to fix the problem. There are a couple of related bugs over at the wireshark bug tracker. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4439 [^] https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4606 [^] Ben Walton informally reported suspected zlib 1.2.4 issues with libxml2. http://lists.opencsw.org/pipermail/users/2010-March/008635.html [^] |
||||
Steps To Reproduce: | |||||
Additional Information: | 1.2.4,REV=2010.03.19 | ||||
Relationships | |||||
Attached Files: | |||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2010-03-26 15:03 | skayser | New Issue | |||
2010-03-28 07:00 | hson | Note Added: 0007770 | |||
2010-04-02 22:30 | hson | Status | new => assigned | ||
2010-04-02 22:30 | hson | Assigned To | => hson | ||
2010-04-11 14:55 | hson | Note Added: 0007845 | |||
2010-04-11 14:55 | hson | Status | assigned => feedback | ||
2010-09-26 04:50 | hson | Note Added: 0008298 | |||
2010-09-26 04:50 | hson | Status | feedback => closed | ||
2010-09-26 04:50 | hson | Resolution | open => fixed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|