Package: emacs23
Version: 23.3+1-5
Severity: normal

Hi,

Running Emacs in a terminal (the -nw option) results in an infinite
loop when GLib 2.31 (from experimental) is used.

Relevant upstream bugs:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9754
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10631

There are a couple of suggested patches in the bug reports, but
upstream apparently doesn't care about Emacs 23 any longer...

It would be great if this could be fixed before GLib 2.31 hits sid.

Thanks in advance,

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.3.0-rc2 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages emacs23 depends on:
ii  emacs23-bin-common  23.3+1-5
ii  gconf-service       3.2.3-3
ii  libasound2          1.0.25-2
ii  libatk1.0-0         2.3.93-1
ii  libc6               2.13-27
ii  libcairo2           1.10.2-7
ii  libdbus-1-3         1.5.8-1
ii  libfontconfig1      2.8.0-3.1
ii  libfreetype6        2.4.8-1
ii  libgconf-2-4        3.2.3-3
ii  libgdk-pixbuf2.0-0  2.25.2-1
ii  libgif4             4.1.6-9
ii  libglib2.0-0        2.31.20-1
ii  libgpm2             1.20.4-4
ii  libgtk2.0-0         2.24.10-1
ii  libice6             2:1.0.7-2
ii  libjpeg8            8d-1
ii  libm17n-0           1.6.3-1
ii  libncurses5         5.9-4
ii  libotf0             0.9.12-1
ii  libpango1.0-0       1.29.4-3
ii  libpng12-0          1.2.47-1
ii  librsvg2-2          2.35.2-1
ii  libsm6              2:1.2.0-2
ii  libtiff4            3.9.6-1
ii  libtinfo5           5.9-4
ii  libx11-6            2:1.4.99.1-1
ii  libxft2             2.2.0-3
ii  libxpm4             1:3.5.9-4
ii  libxrender1         1:0.9.6-2
ii  zlib1g              1:1.2.6.dfsg-2

emacs23 recommends no packages.

Versions of packages emacs23 suggests:
pn  emacs23-common-non-dfsg  <none>

-- no debconf information



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to