Bug 711802 - xemacs modeline broken with multiple frames on different device types
Summary: xemacs modeline broken with multiple frames on different device types
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xemacs
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Jerry James
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 14:29 UTC by Henrique Martins
Modified: 2012-08-06 19:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---


Attachments (Terms of Use)

Description Henrique Martins 2011-06-08 14:29:40 UTC
Description of problem:
Modeline processing in stock Fedora 15 seems a bit broken when frames are opened on different device types, e.g. x11 and tty.

Version-Release number of selected component (if applicable):
Not sure which xemacs package is responsible but these are the ones installed on one system with the problem:
xemacs-21.5.31-1.fc15.x86_64
xemacs-common-21.5.31-1.fc15.x86_64
xemacs-el-21.5.31-1.fc15.x86_64
xemacs-filesystem-21.5.31-1.fc15.noarch
xemacs-info-21.5.31-1.fc15.noarch
xemacs-packages-base-20110502-1.fc15.noarch
xemacs-packages-base-el-20110502-1.fc15.noarch
xemacs-packages-extra-20110502-1.fc15.noarch
xemacs-packages-extra-el-20110502-1.fc15.noarch

How reproducible:
Always

Steps to Reproduce:
1. open a new xterm make sure DISPLAY is set to an X11 display
2. run 
     xemacs -vanilla &
so no customization is done. An xemacs X11 frame visiting the *scratch* buffer will show on the display. Device type will be x11. 
3. in the *scratch* buffer execute the commands below to change the background and foreground colors of the modeline. and start gnuserv.
  (set-face-background 'modeline "Gray75" )
  (set-face-foreground 'modeline "Black"  )
  (gnuserv-start)
4. back to the xterm, unset the DISPLAY environment variable, e.g.
   unset DISPLAY
or
  export DISPLAY=''
5. again in xterm invoke
   gnuclient
to start a new xemacs frame on the terminal.  Device type will be tty.

Actual results:
Modeline on original x11 frame reverts back to the default colors

Expected results:
Modeline in x11 frame should not change.  This was the behavior on F14

Additional info:
Also sent a message to xemacs-beta dev list

Comment 1 Jerry James 2011-08-05 18:01:55 UTC
Hi Henrique,

Sorry to be so slow with this.  I was hoping somebody on xemacs-beta would solve it for me. :-)  Today I followed your recipe, hoping to find some clue as to what is going on.  But I didn't reproduce the problem.  I have gnuclient running in a TTY, and the modeline colors on the X11 frame did NOT revert back to the default colors.  So something else is going on here.  Do you have any other XEmacs packages installed besides the ones you listed already?

Comment 2 Henrique Martins 2011-08-05 18:49:58 UTC
Thanks for looking into this Jerry.

Not a big problem as I created a function to reset the modeline, but your inability to replicate made me realize what is different in my case.  I set the background and foreground colors of XEmacs via xresources with entries like:
  *background: #304060
  *foreground: White
and with those the modeline reset under the conditions I described.

If I delete those entries (which I've carried for about 20 years...) and do it from within xemacs via set-face-(fore|back)ground 'default, then the modeline doesn't reset.  So something is now different but with a workaround.  Some of my mh-e colors are now different though :-)

Comment 3 Jerry James 2011-08-05 19:11:59 UTC
Hmmmm.  I think I'm out of my depth here.  It's probably worth sending a message to xemacs-beta with this new information.  (Incidentally, I'm about to kick off a new build that fixes your other bug, plus a few other things that I've been working on fixes for.)

Comment 4 Fedora End Of Life 2012-08-06 19:56:20 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2012-08-06 19:58:33 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 15. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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