Summary: | Orbit 2.14.8 causes gconfd-2 to loop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Bill Krueger <bill_krueger> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 188825 | ||
Bug Blocks: |
Description
Bill Krueger
2007-08-10 18:00:31 UTC
does all your gnomey programs are stopped when you log off kde ? did you trying downgrading to 2.14.7 ? as a side note, gconf-cleaner isn't supported on gentoo and considered dangerous. (In reply to comment #1) > does all your gnomey programs are stopped when you log off kde ? I think you're asking if there were any gnome related apps left over from a prior session and I don't think so. I actually re-booted (as loath as I am to do), logged in and tried FF and I still got the same results (i.e. 100%cpu and no FF). > did you trying downgrading to 2.14.7 ? Yes, sorry I forgot to mention it. I downgraded t 2.14.7 and all was well. > as a side note, gconf-cleaner isn't supported on gentoo and considered > dangerous. I wondered why it wasn't in portage. I thought I might have some corrupted files in my $HOME/.gconf directory so I was going to use it to see if I could clean that up. What it did was tell me that because it had the same problem as FF that it wasn't a FF specific problem. I bet it's the GIOP_timeout rewrite that is causing this. I updated orbit on my desktop as well and I don't have such problem but I'm using a gnome desktop. Before filling the bug upstream, could you tell me if all your gnome related apps are up to date and if you could consider trying gconf-2.19.1 from the gnome-overlay. Although if you could provide a trace of gconf while it's eating your CPU, that might help us understand the problem. (In reply to comment #3) > Before filling the bug upstream, could you tell me if all your gnome related > apps are up to date and if you could consider trying gconf-2.19.1 from the > gnome-overlay. I keep my system as up to date as possible so I'm pretty sure they are. As for 2,19.1, I'd be happy to try that. > > Although if you could provide a trace of gconf while it's eating your CPU, that > might help us understand the problem. I took an strace of FF (with -f -ff) and I think I kept the traces. The problem (and the traces) are on my machine at work and I can't access that from home so any further information will have to wait until Monday. Also, this may be a bit of a moot point. I keep a similar system updated at home the same way I do at work (KDE, ~x86, etc) and I now see that I have orbit-2.14.8 on that system and I'm not seeing any problems (I'm posting with the same level of FF on this system). I'm sure there's lots of differences in the two systems with regards to the installed packages. looks like bug #188825 has the answer to this problem. please get back to us, 2.14.8-r3 has some more bug fixes. |