Bug 13144 - xemacs crashes when trying to edit faces
Summary: xemacs crashes when trying to edit faces
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-04-04 11:28 CEST by Gilles Allard
Modified: 2016-02-13 10:30 CET (History)
2 users (show)

See Also:
Source RPM: xemacs
CVE:
Status comment:


Attachments
Proposal for a solution to the crash of xemacs-21.4.22 (354 bytes, patch)
2014-04-04 11:28 CEST, Gilles Allard
Details | Diff

Description Gilles Allard 2014-04-04 11:28:04 CEST
Created attachment 5093 [details]
Proposal for a solution to the crash of xemacs-21.4.22

Description of problem:
xemacs-21.4.22-24mga4 built from source pkg crashes (segmentation fault) when trying to edit faces (Options->Edit faces). The crash occurs when buttons are about to be displayed.
The stack displayed by Gdb shows a faulty call to "png_get_text" (from libpng16_16-1.6.8-1mga4)in file "src/glyphs_eimage.c". Switching to libpng15 or libpng13 doesn't solve the problem.


Version-Release number of selected component (if applicable):
xemacs-21.4.22-24mga4 with libpng16_16-1.6.8-1mga4

How reproducible:
Very easily

Steps to Reproduce:
1. Launch xemacs; starts ok
2. Try to edit faces using the menu bar (Options->Edit Faces). Displaying the buttons crashes xemacs
3.

The attachment is my proposal for a patch. With this small patch applied, xemacs works fine.
An alternate solution may be to update the patch file named "xemacs-21.4.22-libpng15.patch" that is part of the source pkg.
Manuel Hiebel 2014-07-02 20:51:32 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => nanardon
Source RPM: (none) => xemacs

Comment 1 Florian Hubold 2014-10-03 15:42:08 CEST
Actually here xemacs segfaults directly when starting on my mga4 install with xemacs-21.4.22-24.mga4 and lib64png16_16-1.6.10-1.1.mga4

CC: (none) => doktor5000

Comment 2 Samuel Verschelde 2015-09-21 13:20:40 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Marja Van Waes 2015-10-12 16:01:28 CEST

CC: (none) => marja11
Assignee: nanardon => bugsquad

Comment 3 Marja Van Waes 2015-10-27 06:57:51 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Resolution: (none) => OLD
Status: NEW => RESOLVED

Comment 4 Gilles Allard 2015-10-30 17:51:24 CET
(In reply to Marja van Waes from comment #3)
> As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status
> on 2015-09-19. It is is no longer maintained, which means that it will not
> receive any further security or bug fix updates.
> 
> This issue may have been fixed in a later Mageia release, so, if you still
> see it and didn't already do so: please upgrade to Mageia 5 (or, if you read
> this much later than this is written: make sure you run a currently
> maintained Mageia version)
> 
> If you are able to reproduce it against a maintained version of Mageia, you
> are encouraged to 
> 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to
> "REOPENED"
> 2. click on "Version" and change it against that version of Mageia. If you
> know it's valid in several versions, select the highest and add MGAxTOO in
> whiteboard for each other valid release.
> Example: it's valid in cauldron and Mageia 5, set to cauldron and add
> MGA5TOO.
> 3. give as much relevant information as possible. If you're not an
> experienced bug reporter and have some time: please read this page:
> https://wiki.mageia.org/en/How_to_report_a_bug_properly
> 
> If you see a similar issue, but are _not_sure_ it is the same, with the same
> cause, then please file a new bug report and mention this one in it (please
> include the bug number, too). 
> 
> 
> If you would like to help fixing bugs in the future, don't hesitate to join
> the
> packager team via our mentoring program [1] or join the teams that fit you 
> most [2].
> [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
> [2] http://www.mageia.org/contribute/

The same problem occurs using xemacs-21.4.22-26mga5 : xemacs crashes when trying to edit faces exactly for the same reason than with the mga4 release
The proposed patch is therefore still valid.
Compiling this release with gcc-4.7.2 shows a warning on glyphs-eimage.c at line 1049 (call to "png_get_text") explaining the error.
So I reopen the bug as explained and change the version to "mga5".

Status: RESOLVED => REOPENED
Version: 4 => 5
Resolution: OLD => (none)

Comment 5 Marja Van Waes 2016-02-13 10:30:15 CET
@ Gilles,

Thanks for reopening the bug report.

Unfortunately, we don't have anyone who has time to work on xemacs, and it was obsoleted in cauldron because of the huge problems with it.

See https://bugs.mageia.org/show_bug.cgi?id=11254#c36

If you customized xemacs, and would like to port your customization to emacs, then please read: 
https://wiki.mageia.org/en/Guide_to_customizing_Emacs

Alternatively, you can consider becoming a Mageia packager 
https://wiki.mageia.org/en/Becoming_a_Mageia_Packager and reimport and maintain xemacs after you graduate.

Kind regards,
Marja

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX


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