From: Robert Marshall <robert@capuchin.co.uk>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: 17120@debbugs.gnu.org, Juanma Barranquero <lekktu@gmail.com>
Subject: bug#17120: Fwd: Error displaying a frame modified with (tool-bar-lines . 0)
Date: Sat, 29 Mar 2014 13:25:52 +0000 [thread overview]
Message-ID: <21302.51680.942350.227585@capuchin.co.uk> (raw)
In-Reply-To: <5336BC84.5050306@swipnet.se>
Jan Djärv writes:
> Hello.
>
> Is this still an issue? I can't reproduce it on Mint 16, Gtk+ 3.8.7.
> It could be window manager related. Are you running Unity?
> I'll see if I have some Ubuntu lying around.
>
Yes it's still replicable - I'm running kde/plasma
I've just tried running the test in an Xnest session with
fluxbox/windowMaker/sawfish and in all cases the session crashes with
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter)
Major opcode of failed request: 70 (X_PolyFillRectangle)
Resource id in failed request: 0x0
Serial number of failed request: 30246
Current serial number in output stream: 30246
at the point where the second emacs frame appears. Maybe they (or Xnest)
can't cope with the weird window.
With unity there doesn't seem to be a --display option and running it
from a normal session the bug doesn't appear - the 2nd frame is drawn
normally so the bug looks very window manager related.
Robert
next prev parent reply other threads:[~2014-03-29 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAeL0SSHbEutKMJe+dE15uBCUB6Z1grTL9R-vzKebV5LXthDnA@mail.gmail.com>
2014-03-27 15:28 ` bug#17120: Fwd: Error displaying a frame modified with (tool-bar-lines . 0) Juanma Barranquero
[not found] ` <5336BC84.5050306@swipnet.se>
2014-03-29 13:25 ` Robert Marshall [this message]
2014-03-31 12:48 ` Robert Marshall
2021-05-02 8:47 ` martin rudalics
2021-05-19 8:13 ` martin rudalics
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=21302.51680.942350.227585@capuchin.co.uk \
--to=robert@capuchin.co.uk \
--cc=17120@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=lekktu@gmail.com \
/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).