GNU bug report logs - #13469
24.2; emacs has a tiny frame, when I embed it in a kmail text field via xembed (--parent-id %w)

Previous Next

Package: emacs;

Reported by: arne_bab <at> web.de

Date: Wed, 16 Jan 2013 23:55:01 UTC

Severity: normal

Tags: moreinfo

Found in version 24.2

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: arne.babenhauserheide <at> kit.edu, Jan Djärv <jan.h.d <at> swipnet.se>
Cc: 13469 <at> debbugs.gnu.org, arne_bab <at> web.de
Subject: bug#13469: 24.2; emacs has a tiny frame, when I embed it in a kmail text field	via	xembed (--parent-id %w)
Date: Thu, 21 Mar 2013 19:36:27 +0200
> Date: Thu, 21 Mar 2013 11:57:23 +0100
> From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide <at> kit.edu>
> CC: "13469 <at> debbugs.gnu.org" <13469 <at> debbugs.gnu.org>, "arne_bab <at> web.de"
> 	<arne_bab <at> web.de>
> 
> I just found a much easier way to reproduce it:
> 
> Run emacs with --parent-id <random number>

So it looks like something specific to using the XEmbed protocol, I
guess.

> A backtrace after clicking the minibuffer (which triggers a resize)
> looks like this (without menubar):
> 
> Breakpoint 1, change_frame_size (f=f <at> entry=0x104b4b0,
> newheight=newheight <at> entry=5, newwidth=newwidth <at> entry=21,
> pretend=pretend <at> entry=0, delay=delay <at> entry=1,
>     safe=safe <at> entry=0) at dispnew.c:5726
> 5726    in dispnew.c
> (gdb) backtrace
> #0  change_frame_size (f=f <at> entry=0x104b4b0, newheight=newheight <at> entry=5,
> newwidth=newwidth <at> entry=21, pretend=pretend <at> entry=0,
> delay=delay <at> entry=1, safe=safe <at> entry=0)
>     at dispnew.c:5726
> #1  0x00000000004ed1c8 in xg_frame_resized (f=0x104b4b0, pixelwidth=200,
> pixelheight=75) at gtkutil.c:888
> #2  0x00000000004c3056 in handle_one_xevent
> (dpyinfo=dpyinfo <at> entry=0x101a3f0,
> eventptr=eventptr <at> entry=0x7fffffffc360, finish=finish <at> entry=0xaee010
> <current_finish>,
>     hold_quit=0x7fffffffc720) at xterm.c:6813
> #3  0x00000000004c3a34 in event_handler_gdk (gxev=0x7fffffffc360,
> ev=<optimized out>, data=<optimized out>) at xterm.c:5834
> #4  0x00007ffff7543d52 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #5  0x00007ffff75454f8 in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #6  0x00007ffff754557e in ?? () from /usr/lib64/libgdk-x11-2.0.so.0
> #7  0x00007ffff68c0883 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0

This looks like GTK instructed us to resize ourselves to 200x75
pixels, which was quite reasonably translated to 21x5 characters.
Sounds like a good time for some GTK expert (Jan?) to chime in and
help us out.




This bug report was last modified 3 years and 83 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.