Bug 600440 - system-switch-mail segfaults running under screen
Summary: system-switch-mail segfaults running under screen
Alias: None
Product: Fedora
Classification: Fedora
Component: system-switch-mail   
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-04 17:47 UTC by Steven Pritchard
Modified: 2011-06-06 08:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-06 08:03:17 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Steven Pritchard 2010-06-04 17:47:45 UTC
Description of problem:
Under screen, after selecting MTA and hitting OK, you get "Segmentation fault".  It seems like links are updated and such though.

Running on the console (TERM=linux) or in an xterm (TERM=xterm), it works fine.

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

How reproducible:

Steps to Reproduce:
1. Run "screen".
2. Run "system-switch-mail" in the new screen.
3. Select the current MTA and hit OK.
Actual results:
Segmentation fault

Expected results:
                  ┌─────────────┤ Information ├──────────────┐
                  │                                          │ 
                  │ Your MTA configuration has succesfully   │ 
                  │ been updated.                            │ 
                  │                                          │ 
                  │                                          │ 
                  │                 ┌────┐                   │ 
                  │                 │ OK │                   │ 
                  │                 └────┘                   │ 
                  │                                          │ 
                  │                                          │ 

Additional info:
I only tried selecting Postfix.  It's possible that switching to other MTAs might work.

Comment 1 Steven Pritchard 2010-08-18 16:32:49 UTC
I just accidentally did "TERM=vt100 system-switch-mail" instead of "TERM=xterm system-switch-mail" like I intended, and that segfaulted as well.

Comment 2 Ngo Than 2010-08-24 10:50:50 UTC
i cannot reproduce this issue on my testing machine with above steps,  can switch MTA without any crash with system-switch-mail-1.0.1-1.fc13.noarch.

could you please attatch the output if this command line.
rpm -q slang newt newt-python python


Comment 3 Bug Zapper 2011-06-02 12:02:13 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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 Ngo Than 2011-06-06 08:03:17 UTC
I'm closing that bugzilla INSUFFICIENT_DATA because there's no testcase to reproduce this issue.  Feel free to reopen it once you find some way how to reproduce it.

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