Summary: | X lockup when using Gnome 2.2 (random?) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Magnus Määttä <novell> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | VERIFIED LATER | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Magnus Määttä
2003-02-19 05:16:22 UTC
what xfree are you using ? "I'm using up-to-date unstable." "ACCEPT_KEYWORDS="x86 ~x86"" That would be XFree86 4.2.99, and it is.. is it reproducable with a stable xfree (.99 are ofcourse devel releases) ? I have not tried it.. To be more clear. This can also happen when doing other things in Gnome. But Enlightenment worked just fine for days doing lots of things. well we can't go support devel stuff, so we must rule that out first as the problem. Can you give more useful debugging info btw, backtraces with debug enabled ? What video card ? full lockups are usually hardware related . Does only X lockup or is the whole system dead ? I'm 100% sure this is not a hardware problem. Besides, it works fine in Enlightenment. But not in Gnome. And unstable is supposed to be for those who wants to try latest stuff and help finding bugs in it to make the stable release more stable. Only X lockup, otherwise I wouldn't be able to send SEGV to X after it has locked up, right ? ;) Well, I will probably recompile XFree with debugging turned on to test this more when I have time to do so. well yeah, but 4.2.99 will never be marked stable since it's a development release (imo it should be in package.mask, but thats just my take on it .. looks like the xfree guys think differently about it) anyway, closing .. reopen when you can give us debug output guess this can really go now ? |