Bug 795 - X server dies when I start gaim
Summary: X server dies when I start gaim
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 6.7.0
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-22 15:51 UTC by Ron
Modified: 2004-07-21 05:56 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Ron 2004-06-22 15:51:58 UTC
I am using a freshly compiled LinuxFromScratch system pretty much identical to 
my current LFS system and it works fine there.  When I try to use the add 
account dialog in gaim the X server just dies.  I'm pretty sure its a gtk/x 
interaction but cannot figure out what is going on because nothing leaves a 
core.  Trying to start the X server in gdb results in my system locking up.  I 
have no clue what is going on or even where to begin.  Any tips will be much 
welcomed, thank you.
Comment 1 Adam Jackson 2004-06-22 19:16:46 UTC
what hardware?  what gtk version?  what gaim version?  if ati or nvidia card,
are you using our driver or theirs?  do you get any interesting messages in
Xorg.0.log or in dmesg?  do you get a core dump if you start the server with the
-core flag?

(bumping to major since it's a crash)
Comment 2 Ron 2004-06-23 02:05:33 UTC
Latest GAIM and GTK and i865g.  The problem went away when i removed
-fomit-frame-pointer from the flags for X which is odd because I've been using
that for years, than another problem cropped up with GTK that was causing
segfaults and not disabling debugging on that fixed it.  I think something is
screwy with glibc possibly.  So this bug could probably be closed as removing
that opt made it go away.
Comment 3 Adam Jackson 2004-07-21 22:56:33 UTC
closing, entropic bug.

reporter, feel free to reopen if you hit this again.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.