unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Roland Winkler <winkler@gnu.org>, 23925@debbugs.gnu.org
Subject: bug#23925: 25.0.95; display broken when maximizing frame
Date: Sat, 09 Jul 2016 11:20:12 +0200	[thread overview]
Message-ID: <5780C1CC.8070509@gmx.at> (raw)
In-Reply-To: <26943.50736.587398.22400@gargle.gargle.HOWL>

 > After a long time I build again a more recent emacs.  Unfortunately
 > it gives me a rather unpleasant experience when maximizing the emacs
 > frame (using the maximize function of the xfce window manager):
 > somehow the frame is not redrawn properly, emacs seems to be unaware
 > of the new frame size and the minibuffer disappears completely.
 > Instead the desktop background is displayed in large parts of the
 > emacs frame.  Unmaximizing makes the problem go away.  But obviously
 > that is no solution.  I can provide more details if you let me know
 > what would be interesting.
 >
 >
 >
 >
 > In GNU Emacs 25.0.95.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.18.9, cairo version 1.14.6)
 >   of 2016-07-08 built on regnitz
 > Windowing system distributor 'The X.Org Foundation', version 11.0.11803000
 > System Description:	Ubuntu 16.04 LTS
 >
 > Configured using:
 >   'configure --with-xwidgets --with-x-toolkit=gtk3 --with-cairo'

Please post the results after doing each of the following:

(1) Evaluate (display-monitor-attributes-list)

(2) With the badly maximized frame evaluate (frame-geometry)

(3) Before maximizing evaluate (setq frame-size-history '(5))
     Then maximize and evaluate (frame--size-history).  The result can be
     found in the buffer *frame-size-history*.

And obviously please also follow Eli's proposal to build without cairo.

Thanks, martin





  parent reply	other threads:[~2016-07-09  9:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09  3:02 bug#23925: 25.0.95; display broken when maximizing frame Roland Winkler
2016-07-09  7:11 ` Eli Zaretskii
2016-07-09  9:45   ` Clément Pit--Claudel
2016-07-09 15:30     ` martin rudalics
2016-07-10  1:52       ` Clément Pit--Claudel
2016-07-11  9:14         ` martin rudalics
2016-07-11 17:47           ` Clément Pit--Claudel
2016-07-12  7:29             ` martin rudalics
2016-07-12  9:29               ` Clément Pit--Claudel
2016-07-13 14:58               ` Roland Winkler
2016-07-13 17:34                 ` martin rudalics
2018-11-22 14:12     ` Dmitry Gutov
2018-12-11  1:40       ` Dmitry Gutov
2018-12-17 19:28         ` Clément Pit-Claudel
2019-03-26  2:12           ` YAMAMOTO Mitsuharu
2019-06-18 20:03           ` Clément Pit-Claudel
2019-06-18 21:33             ` Dmitry Gutov
2019-06-19  0:26               ` YAMAMOTO Mitsuharu
2019-06-19  1:22                 ` Dmitry Gutov
2019-06-19  1:38                   ` YAMAMOTO Mitsuharu
2019-06-19  1:48                     ` Dmitry Gutov
2019-06-19 14:07                     ` Clément Pit-Claudel
2019-06-21  0:36                       ` YAMAMOTO Mitsuharu
2019-06-19  3:31                   ` Roland Winkler
2019-06-18 23:52             ` YAMAMOTO Mitsuharu
2018-12-11  3:36     ` Dmitry Gutov
2018-12-11  8:49       ` Robert Pluim
2016-07-09 21:05   ` Roland Winkler
2016-07-09  9:20 ` martin rudalics [this message]
2016-07-09 17:32 ` Glenn Morris
2016-07-09 17:42   ` Eli Zaretskii
2016-07-10  1:03     ` Glenn Morris
2016-07-10 14:27       ` Eli Zaretskii
2016-07-15 15:46         ` Roland Winkler
2016-07-15 16:04           ` Eli Zaretskii
2016-07-23 17:44           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5780C1CC.8070509@gmx.at \
    --to=rudalics@gmx.at \
    --cc=23925@debbugs.gnu.org \
    --cc=winkler@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).