Bug 19200

Summary: 6RC classic GNOME launches emacs in terminal mode only
Product: Mageia Reporter: Len Lawrence <tarazed25>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: marja11, olav, thierry.vignaud
Version: CauldronKeywords: NEEDINFO, UPSTREAM
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Len Lawrence 2016-08-16 00:58:48 CEST
I normally launch emacs via my edit alias under tcsh:
emacs -Q -u lcl -background white -foreground black -geometry 88x50+200+200 -fn "-*-andale mono-medium-r-normal--13-*-*-*-*-*-*-*" !$ &

This functions perfectly under Plasma5 and Mate, launching a separate window which supports mouse functions and keyboard shortcuts.  In GNOME it appears in the terminal which means no mouse support.  This applies to the built in menu bar as well.  Keyboard shortcuts are ignored.

This looks like another upstream bug.
Len Lawrence 2016-08-16 00:59:39 CEST

Keywords: (none) => UPSTREAM

Comment 1 Marja Van Waes 2016-08-17 08:38:19 CEST
Assigning to all packagers collectively, since there is no registered maintainer for most of Gnome.

Note that, though it looks like an upstream bug, this hasn't been confirmed, yet. 


@ Len

Assuming this isn't a release bug, so changing the component to RPM Packages (it can be changed back if needed, e.g. if you don't have the bug in a fully updated installed older cauldron, but only in a 6RC Gnome Live)

Did you hit this bug in an installed system (if so, classical or Live install?)?

Could you check whether there's an upstream bug report about this issue, or - if you have time - whether you can reproduce it in a different Linux distribution?

Keywords: (none) => NEEDINFO
CC: sysadmin-bugs => marja11, olav, thierry.vignaud
Component: Release (media or process) => RPM Packages
Assignee: bugsquad => pkg-bugs

Comment 2 Len Lawrence 2016-08-17 11:00:16 CEST
I was just about to withdraw this because I have been unable to reproduce it on the original machine over a period of three days and it does not occur on any of the other test machines.  I do not have any other Linux distributions.  It now looks like a glitch of some kind on just one computer so I think the bug should be marked as either UNCONFIRMED or INVALID (my preference).

Will have a look around for upstream bug reports of this kind.
Comment 3 Len Lawrence 2016-08-17 11:03:49 CEST
Oops.  Those comments (#2) refer to another bug so ignore them.
Comment 4 Len Lawrence 2016-08-17 13:25:15 CEST
Checked this on two machines with fully updated Cauldron from mageia6 RC classic installs, one of them i586.  The behaviour is the same.

A web search on this topic does provide some hits.  Shall collect the links  when I have time.  Note, different distributions also.

It does look like an upstream change of some kind.
Comment 5 Len Lawrence 2016-08-17 19:28:13 CEST
The behaviour is equivalent to running:
$ emacs -nw .....

Looking at /usr/bin/emacs, it is a symlink to /etc/alternatives/emacs which is another symlink pointing to emacs-nox.  It looks as if GNOME is forcing the issue.
Further investigation revealed that the emacs binary can be run from /usr/bin as emacs-24.5.  So it is just a matter of making a local alias or copying the binary to /usr/bin/emacs.  emacs-24.5 works fine, running in its own window.

If this is GNOME policy then there is no bug.  How to mark it?  INVALID?
Comment 6 Olav Vitters 2016-08-17 23:36:01 CEST
I don't really understand the steps to reproduce.
Comment 7 Len Lawrence 2016-08-18 00:29:58 CEST
Simply run emacs from a terminal.  The sysmlink ensures that emacs comes up in the same terminal rather than in its own window.  In other words the default behaviour of emacs has changed.  I never install emacs-nox because I never use it but it seems to be installed anyway.
Comment 8 Len Lawrence 2016-08-18 00:39:23 CEST
Override GNOME's settings:
$ sudo urpme emacs
$ sudo urpmi emacs
$ emacs junk
emacs now launches in its own window.
Comment 9 Len Lawrence 2017-03-21 10:00:04 CET
This bug is not valid in Mageia 6sta2.
Comment 10 Rémi Verschelde 2017-03-21 10:07:53 CET
Please don't hesitate to mark as fixed yourself then. (Done this time).

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