SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As the title says, I am experiencing some odd behavior with Mozilla applications with x86_64 current.
Whenever I close either Firefox and/or Thunderbird, the process does not die and my CPU starts to crank up to the max. Once I kill each process manually, everything is back to normal.
What steps can I take to ID what the actual issue is?
I think I may have found the problem, not sure though.
I had installed gtk-qt-engine-1.1-x86_64-1_SBo.tgz from Slackbuilds. I got to thinking that since I am using current, this may be the issue. Once I uninstalled the package, it appears that both Firefox and Thunderbird processes are terminating when they should.
Thoughts?
I'll keep trying to troubleshhot it to see if I can ID exactly what it may be..............
Well, after some more testing, it is safe to say that using gtk-qt-engine-1.1-x86_64-1_SBo.tgz from Slackbuilds created my issue. I'm not smart enough to figure out what the difference would be from using it on Slackware64 13.0 that it is designed to build against and x86_64-current.
gtk-qt-engine caused firefox to hang indefinitely on my slack13 machine. The window would close, but the process wouldn't actually die. Removing gtk-qt-engine solved the problem for me as well. There is a thread relating to this on the forums: http://www.linuxquestions.org/questi...stable-773551/
Last edited by damgar; 01-06-2010 at 09:36 PM.
Reason: t1p0z
gtk-qt-engine caused firefox to hang indefinitely on my slack13 machine. The window would close, but the process wouldn't actually die. Removing gtk-qt-engine solved the problem for me as well. There is a thread relating to this on the forums: http://www.linuxquestions.org/questi...stable-773551/
Thanks, I never saw that thread.........surprised I figured it out on my own.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Odd "Mozilla" behavior x86_64 current
