What's odd, though, and makes it seem unlikely it's a disk issue is, this is happening on 2 different machines -- a brand new laptop that had F16 (where screen was working) on it before the clean install of F17 alpha and another machine where screen was working without a problem with F16, but then the first time I tried running 'xterm -e screen' after updating to F17, it crashed. That's my home computer, so I don't know if it's the same message I got on my laptop, but can look at home.
I'll check /var/log/messages, dmesg, and do an strace as you recommended though.
Brian
On Thu, Apr 19, 2012 at 4:13 PM, Michal Jaegermann <michal@xxxxxxxxxxxx> wrote:
On Thu, Apr 19, 2012 at 01:22:19PM -0400, Brian Johnson wrote:Why that may affect 'screen' I have no idea. Does not seem to be a
>
> So, here's what is flashing:
>
> manpath: warning: $MANPATH set, ignoring /etc/man_db.conf
> free(207da4d) bad block. (memtop = 0x21bd000 membot = 0x2074000)
likely cause but I cannot really tell. OTOH the above _may_ mean
that your disk is acting up (and possibly swap is affected). If that
is really the case then you should get quite a lot to read in
/var/log/messages and in dmesg output.
If this is not the case then running
strace -o /tmp/screen.trace screen
and looking at results may give you some clues (but you have to
be careful how you read that and pay attention to a context).
Michal
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
