SEO

a)
The display command doesn't work proper anymore, when
I put
display -geometry 800x600 -size 800x600 *.jpg&
I'd expect JPEGs in that directory to be shrunk to
fit the window, but I get the panning view, and when
I close display it says:

$ *** glibc detected *** double free or corruption (!prev): 0x080521f8
***


b)
my emacs won't start in X-mode,
complaining about

No fonts match
`-b&h-lucidatypewriter-medium-*-*-*-12-*-*-*-m-*-iso8859-1'


c)
When in X Ctrl-Alt-F<n> is being ignored, I can't get to my
full-screen consoles. And yes, I *did* adjust xorg.conf not to
say Keyboard...


If someone has a solution to either of these - please post

I'll try to live with this for one more day or two and then
downgrade back to 10.0 ...


Cheers,
Tink

a.ricnik@gmail.com wrote:
> a)
> The display command doesn't work proper anymore, when
> I put
> display -geometry 800x600 -size 800x600 *.jpg&
> I'd expect JPEGs in that directory to be shrunk to
> fit the window, but I get the panning view, and when
> I close display it says:
>
> $ *** glibc detected *** double free or corruption (!prev): 0x080521f8
> ***
>
>
> b)
> my emacs won't start in X-mode,
> complaining about
>
> No fonts match
> `-b&h-lucidatypewriter-medium-*-*-*-12-*-*-*-m-*-iso8859-1'
>
>
> c)
> When in X Ctrl-Alt-F<n> is being ignored, I can't get to my
> full-screen consoles. And yes, I *did* adjust xorg.conf not to
> say Keyboard...
>
>

From the error message look like your glibc is corrupted. I would try
to reinstall all glibc* packages.

WARNING: Replace the glibc package from a rescue CD (the slackware 10.0
second CD will do the trick) by passing the ROOT environement variable
to installpkg and removepkg. These packages are so essential that
removing them while you are running Slackware will probably crash your
system immediatly.

a.ricnik@gmail.com wrote:
> c)
> When in X Ctrl-Alt-F<n> is being ignored, I can't get to my
> full-screen consoles.

(copy and paste from a message I wrote less than a week ago in this
newsgroup)

Check your xmodmap. I had exactly the same problem when I upgraded to
X.org in Slackware 9.1. It turned out that XFree86 didn't need anything
special in xmodmap, it looked like this:
....
keycode 67 = F1 F11
keycode 68 = F2 F12
keycode 69 = F3 F13
....

But X.org needed to look like this:
....
keycode 67 = F1 XF86_Switch_VT_1
keycode 68 = F2 XF86_Switch_VT_2
keycode 69 = F3 XF86_Switch_VT_3
....

I guess that you have an old /etc/X11/xinit/.Xmodmap which causes these
problems. Otherwise, you might have your own ~/.Xmodmap.

If you are unable to find your .Xmodmap at least you could check your
current settings with "xmodmap -pke".

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
info@k-software.biz svar@webtelevision.se info@webrider.ru root@localhost

Thanks for the pointer, Hendrik!

I didn't have either a global nor a user specific .Xmodmap prior to
this ...

So I did (as root)
xmodmap -pke > /etc/X11/xinit/.Xmodmap
and edited it according yo your suggestion, and then
(since it still wouldn't switch to the console after a
Ctrl-Alt-BkSpc) also copied that file to my users ~ ...
no luck. Any other suggestions?


Ta,
Tink

"tink" <a.ricnik@gmail.com> wrote:
> So I did (as root)
> xmodmap -pke > /etc/X11/xinit/.Xmodmap and edited it according yo your
> suggestion, and then (since it still wouldn't switch to the console
> after a Ctrl-Alt-BkSpc) also copied that file to my users ~ ... no luck.
> Any other suggestions?

What if you now as a user in X type:

xmodmap -pke | grep F1

What do you get? Do you get:
keycode 67 = F1 XF86_Switch_VT_1
or do you get something like
keycode 67 = F1

If you get the later your new .Xmodmap has not given any effect. If so,
you will have to search the X startup scripts for which files are read by
xmodmap. In Slackware 9.1 the file is read from /etc/X11/xinit/xinitrc
when doing "startx" and it is read from /etc/X11/xdm/Xsession when using
xdm, kdm or gdm.

If your output from xmodmap -pke looks OK I only have one more suggestion:
Check your /etc/X11/xorg.conf for some rows like this:

-8<---------------------------------------------------
# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"
-8<---------------------------------------------------

If the last row is uncommented you will get the problem that you describe.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc2(at)uthyres.com Examples of addresses which go to spammers:
info@k-software.biz svar@webtelevision.se info@webrider.ru root@localhost

On Wed, 16 Feb 2005 19:24:10 +0100, Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:

>"tink" <a.ricnik@gmail.com> wrote:
>> So I did (as root)
>> xmodmap -pke > /etc/X11/xinit/.Xmodmap and edited it according yo your
>> suggestion, and then (since it still wouldn't switch to the console
>> after a Ctrl-Alt-BkSpc) also copied that file to my users ~ ... no luck.
>> Any other suggestions?
>
>What if you now as a user in X type:

Pardon my jumping into this thread, but I had a similar strangeness
with keyboard mapping on a text-only clean install -- using vim edit
over ssh with PuTTY: in insert mode, cursor arrow keys moved the
cursor and inserted capital letters, 'removepkg kdb' fixed the issue.

Perhaps this is related issue? Not something I noticed in 10.0 or 9.1.

I don't think I've done a startx in 10.1 yet.

Cheers,
Grant.

Hi Hendrik ...

The problem went away when I mv'ed my old xorg.conf, ran
X -configure and put that in /etx/X11 (had to edit the driver).

The old file didn't have the DontVTSwitch option turned on,
though. Didn't bother trying the xmodmap after the new
config...

Thanks for your time!

Cheers,
Tink