Bug 487670 - glipper breaks working with regions in xemacs
glipper breaks working with regions in xemacs
Product: Fedora
Classification: Fedora
Component: glipper (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Damien Durand
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-02-27 07:02 EST by Michael Schmitz
Modified: 2009-12-18 03:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 03:04:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Schmitz 2009-02-27 07:02:26 EST
Description of problem:
As soon as I add the "glipper" applet to a panel creating regions in xemacs stops working.

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

How reproducible:

Steps to Reproduce:
1. Remove the "glipper" applet from all panels
2. start xemacs
3. Add the "glipper" applet to a panel
4. set a mark in xemacs (C-<space>)
5. move point and copy the region (M-w)
6. set a new mark in xemacs (C-<space>)
7. move point and try to copy the region (M-w)

Actual results:
Copying the region results in the following error message:

 Invalid operation: The region is not active now

Expected results:
Copying the region succeeds, no error message

Additional info:
1. The problem disappears as soon as I remove "glipper" from the panel.
2. "glipper" does not only break local xemacs processes, but also xemacs
   processes running on a remote host (with different OS, like OpenSuSE)
   but using the local X display.
Comment 2 Bug Zapper 2009-11-18 06:14:50 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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 3 Bug Zapper 2009-12-18 03:04:17 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.