Summary: | after merging glibc-2.3.5 my aterm-1.00_beta2 segfaults... all efforts to remerge aterm and get it back to work correctly havent succeeded yet | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nicolas Vilz <niv> |
Component: | Current packages | Assignee: | Michal Januszewski (RETIRED) <spock> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nicolas Vilz
2005-04-22 04:29:12 UTC
I run on 2.3.4-20050125-r1 now so that i am able to use aterm (with fvwm-crystal), the strace-output was with 2.3.5 Is aterm the only application that misbehaves after the glibc upgrade? Can you try merging an older version of aterm (0.4.2-x) to see whether it works with the new glibc? i tried 0.4.2-r13 and it works ... strange... i haven't notice any other misbehaviour, yet, but i keep watching... on my ppc-box i had aterm 0.4.2-r11 and it worked fine after upgrading glibc... i am trying to upgrade to 0.4.2.r13 now... ok guys, i got errors on restarting xorg-x11, i only got Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved! Symbol __glXgetActiveScreen from module /usr/lib/modules/extensions/libdri.a is unresolved! and no x11-screen. after downgrading to 2.3.4.20050125-r1 i worked again... i will try remerging xorg-x11 again and i hope that will help... strange... now with other libtool, aterm works (with 1.00_beta2, too) ... i havent restartet my x11-session yet, so i leave that bug open... If you restart your x session, please make sure that you put a comment here so that I know whether the bug can be closed :) d'oh... sorry, i forgot about that... i restarted x11 and my computer... and it seems to be ok :) thx for your help. Well then, I'm closing the bug :) |