From: "Robert Thorpe" <rthorpe@realworldtech.com>
Subject: Re: Emacs corrupted
Date: 20 Dec 2006 11:03:51 -0800 [thread overview]
Message-ID: <1166641431.927357.120580@a3g2000cwd.googlegroups.com> (raw)
In-Reply-To: <mailman.2138.1166618695.2155.help-gnu-emacs@gnu.org>
DigitalDingo wrote:
> A couple of days ago I tried to open both Emacs and Maple using the Deskbar
> in Ubuntu with the command "emacs & xmaple". Well, it was a try - and it
> didn't work either - and now emacs seems to have been corrupted. Much of the
> text is just squares and the menu bar has an ugly large font as you can see
> on the screen shots. Also, when I hover the pointer over something, it
> should bring up a description, but it just shows squares.
> I don't use an .emacs file.
>
> Does anyone know how to correct this?
>
> http://www.nabble.com/file/4959/emacs1.png
> http://www.nabble.com/file/4960/emacs2.png
> http://www.nabble.com/file/4961/emacs3.png
This isn't corruption of Emacs itself, it's an Ubuntu bug AFAIK.
>From a previous post of mine....
This problem is the interaction of Emacs and X.org config. It can
affect Debian and Ubuntu. See the Debian bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352811 and the Ubuntu
bug https://launchpad.net/distros/ubuntu/+source/xorg/+bug/53038.
There has been quite a lot of discussion about where to best fix it.
See the threads for details.
It affects every part of X on the relevant distributions. Type
"xfontsel" to see what I mean.
The problem is fonts used to be in /usr/share/X11/fonts/ now they are
in /usr/share/fonts/X11/, the config file xorg.conf was not updated to
reflect this change.
Dave Love wrote a patch to fix it:
http://librarian.launchpad.net/4860914/diff
next parent reply other threads:[~2006-12-20 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2138.1166618695.2155.help-gnu-emacs@gnu.org>
2006-12-20 19:03 ` Robert Thorpe [this message]
2006-12-21 15:19 ` Emacs corrupted DigitalDingo
2006-12-21 17:02 ` Tim X
2006-12-20 12:44 DigitalDingo
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=1166641431.927357.120580@a3g2000cwd.googlegroups.com \
--to=rthorpe@realworldtech.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.
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).