Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
|
06-28-2010, 07:55 AM
|
#1
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Rep:
|
Slackware 13.1: Firefox 3.6.6 not opening, no terminal info output.
Hi again, people.
Here's the issue: Firefox does not open under any circumstances, it's allocated in the memory and has it's process ids, but the browser is not opened at all. There's not terminal output when ran in terminal, no dmesg, debug..., nothing. The only info I could give:
Terminal try:
Code:
rodrigo@darkstar:~$ firefox
ps aux output:
Code:
rodrigo 5223 0.0 0.0 3060 1440 pts/1 S+ 09:48 0:00 /bin/sh /usr/bin/firefox
rodrigo 5236 0.0 0.0 3104 1500 pts/1 S+ 09:48 0:00 /bin/sh /usr/lib/firefox-3.6.6/run-mozilla.sh /usr/lib/firefox-3.6.6/firefox-bin
rodrigo 5240 0.0 0.3 33308 6288 pts/1 S+ 09:48 0:00 /usr/lib/firefox-3.6.6/firefox-bin
So, I really don't know what's happening, if someone have some light to shed, I'd be glad.
EDIT: Forgot some info: Slackware 13.1 32-bit x86, package is mozilla-firefox-3.6.6-i686-1. Also, I found this post with the same issue: http://www.linuxquestions.org/questi...-start-816486/
Last edited by rfernandez; 06-28-2010 at 08:11 AM.
|
|
|
|
06-28-2010, 08:18 AM
|
#2
|
|
Member
Registered: May 2009
Location: Warsaw, Poland
Distribution: Slackware64-current
Posts: 191
Rep:
|
Backup and remove ~/.mozilla directory, and re-run firefox. Maybe You profile is broken, and thus it cannot be initialized properly.
See, what will happened after the removal of this directory.
|
|
|
|
06-28-2010, 08:23 AM
|
#3
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
Hi, Martinezio, and thanks for your reply.
So i did what you asked
Code:
rodrigo@darkstar:~$ ls -a | grep .mozilla
.mozilla/
rodrigo@darkstar:~$ mv .mozilla mozilla-backup
rodrigo@darkstar:~$ firefox
And still no love from Firefox.
EDIT: There were no new .mozilla/ directory created.
Last edited by rfernandez; 06-28-2010 at 08:27 AM.
|
|
|
|
06-28-2010, 11:10 AM
|
#4
|
|
Member
Registered: Jan 2005
Location: Istanbul, Turkey
Distribution: Slackware 13.37, Pardus 2011.2
Posts: 884
Rep:
|
Did you try this under another window manager?
|
|
|
|
06-28-2010, 11:25 AM
|
#5
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
No, Ilgar, I haven't. I've only got KDE to use.
|
|
|
|
06-28-2010, 11:26 AM
|
#6
|
|
Senior Member
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
|
Since this is Firefox 3.6.6, means you did the upgrade, and I assume everything was working previously to this upgrade?
How did you upgrade Firefox? slackpkg, upgradepkg, installpkg?
Check that you only have one Firefox installed.
ls /var/log/packages | grep firefox
You can try safe mode
firefox -safe-mode
double check you don't have a non compatible plugin. By default Slackware only ships with libnpjp2.so (java) and skypebuttons.so (something from KDE. Still not sure why KDE would assume I have/will install skype)
Double check the /usr/lib/firefox directory is linked to /usr/lib/firefox-$VERSION, and there is not another /usr/lib/firefox-$SOMETHING.
Could even be a missing library.
ldd /usr/lib/firefox/firefox-bin | grep "not found"
|
|
|
|
06-28-2010, 11:35 AM
|
#7
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
I upgrade via slackpkg. I'm synced to the -current tree, so: slackpkg update -> slackpkg install-new -> slacpkg upgrade-all.
Firefox was, indeed, working fine. I really don't know when things got messed up.
As requested:
Code:
rodrigo@darkstar:~$ ls /var/log/packages | grep firefox
mozilla-firefox-3.6.6-i686-1
rodrigo@darkstar:~$ firefox -safe-mode
rodrigo@darkstar:~$ ls /usr/lib/firefox-3.6.6/plugins/
libnullplugin.so*
rodrigo@darkstar:~$ ls /usr/lib/mozilla/plugins/
libnpjp2.so@
rodrigo@darkstar:~$ ls -l /usr/lib/mozilla/plugins/
total 0
lrwxrwxrwx 1 root root 34 2010-05-30 19:05 libnpjp2.so -> /usr/lib/java/lib/i386/libnpjp2.so*
rodrigo@darkstar:~$ ldd /usr/lib/firefox/firefox-bin | grep "not found"
libxul.so => not found
libxpcom.so => not found
The "firefox -Safe-mode" line means that everything is as usual: no reponse. The ldd returing those "not found" libs it's because libxul.so and libxpcom.so are under the /usr/lib/firefox-3.6.6 directory, and are included in $PATH once the firefox script starts.
Anything else, just ask.
Thank you, guys.
|
|
|
|
06-28-2010, 11:49 AM
|
#8
|
|
Senior Member
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
|
Quote:
Originally Posted by rfernandez
The ldd returing those "not found" libs it's because
|
Is because things are not installed properly
libxul.so and libxpcom.so are part of seamonkey. Granted the 32bit firefox may ship with that library in that path, but it (firefox) looks to /usr/lib/seamonkey-$VERSION/ for the libraries.
On my clean full Slackware 32bit install, I can remove libxul from /usr/lib/firefox , and firefox runs. I put that libxul back, and remove the one from seamonkey, firefox does not run.
You might get by with linking those two missing libs from /usr/lib/firefox to /usr/lib. Or install seamonkey.
|
|
|
|
06-28-2010, 01:37 PM
|
#9
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
But, that's weird, since:
Code:
rodrigo@darkstar:~$ ls /var/log/packages/ | grep seamonkey
seamonkey-solibs-2.0.5-i486-1
rodrigo@darkstar:~$ ls /usr/lib/seamonkey
seamonkey/ seamonkey-2.0.5/
rodrigo@darkstar:~$ ls /usr/lib/seamonkey-2.0.5/
libfreebl3.chk libmozjs.so* libnss3.so* libnssutil3.so* libplds4.so* libsoftokn3.chk libssl3.so*
libfreebl3.so* libnspr4.so* libnssckbi.so* libplc4.so* libsmime3.so* libsoftokn3.so*
It isn't there, but I don't know why. Well, nevertheless I've made the symlinks, but still, nothing happens.
EDIT: Just installed seamonkey, and still, no love from Firefox.
EDIT2: Seamonkey works fine, though.
Last edited by rfernandez; 06-28-2010 at 01:49 PM.
|
|
|
|
06-28-2010, 02:26 PM
|
#10
|
|
Senior Member
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
|
If you notice your ls /usr/lib/seamonkey-2.0.5/ does not contain the missing libraries, that's only the seamonkey-solibs. Strange things still did not work after installing Seamonkey, yet Seamonkey itself works. On my test system, I removed seamonkey, and did an ln -s of those two Firefox libs to /usr/lib/ - I hate it when other people say this but, works for me. Sounds like a side effect from not doing a complete install .... but things worked before, and all you did was upgrade Firefox. Wonder what's missing?
Might want to try Firefox in it's own directory. Just uncompress the file from the Slackware source. It's the same thing Mozilla ships upstream. Should run from it's own directory. The SlackBuilds between 13.1 and the security release of Firefox have not changed, so this is something upstream.
|
|
|
|
06-28-2010, 02:35 PM
|
#11
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
I think the main problem is that I have no output about anything, it just hangs at the terminal without any further info - I can only guess, but I don't know for sure. On my install I only select packages in the A, AP, N, X and XAP series. The D, F, L, K, T and TCL are fully installed, so I don't know if it is a full install issue. It used to work, but got lost somewhere.
I'll try later the static firefox download and see if anything changes, but thank you, disturbed1.
EDIT: I've just tried the static firefox download and things are just the same - firefox won't show a browser window, although the process is allotacted in memory. I have no idea what's going on or if I'm missing some dependecies, but 'till firefox updates, I'll just stay with Google Chrome.
Thanks, everyone.
Last edited by rfernandez; 06-28-2010 at 04:02 PM.
|
|
|
|
06-28-2010, 04:17 PM
|
#12
|
|
Slackware Maintainer
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 634
|
Quote:
Originally Posted by disturbed1
Is because things are not installed properly
libxul.so and libxpcom.so are part of seamonkey. Granted the 32bit firefox may ship with that library in that path, but it (firefox) looks to /usr/lib/seamonkey-$VERSION/ for the libraries.
On my clean full Slackware 32bit install, I can remove libxul from /usr/lib/firefox , and firefox runs. I put that libxul back, and remove the one from seamonkey, firefox does not run.
You might get by with linking those two missing libs from /usr/lib/firefox to /usr/lib. Or install seamonkey.
|
The seamonkey libs should not be required to use Firefox, although it will probably fall back on them if some of Firefox's libraries are removed.
While Firefox is running, you can try this to see that it does in fact use its own copy of libxul.so:
lsof | grep libxul
As far as why the 32-bit Firefox 3.6.6 would not be running, I'll admit I was a bit concerned since we do not compile the 32-bit Firefox and perhaps a change in the upstream compile could break it on Slackware, but I've tested on a 32-bit Slackware 13.1 updated with slackpkg to include Firefox 3.6.6 and the other updates and can report that it's working here.
|
|
|
|
06-28-2010, 04:30 PM
|
#13
|
|
Member
Registered: Mar 2010
Location: Brazil
Distribution: Slackware64
Posts: 264
Original Poster
Rep:
|
Well, indeed a lsof | grep libxul show that firefox use it's own copy, the same for libxpcom. But, is there someway I can trace or debug the application in order to see what it's trying to accomplish? Without any output it's hard just guessing... AFAIK, all dependencies are solved.
|
|
|
|
06-28-2010, 05:29 PM
|
#14
|
|
Senior Member
Registered: Sep 2005
Distribution: Slackware
Posts: 1,439
Rep:
|
Try downgrading back to FF 3.6.4 and let us know if that still comes up.
Also, /usr/lib/firefox*/firefox is just a shell script to launch the binaries. You can try editing it to see more precisely where it hangs. Be sure to read the comments (at least one refers to debugging)
|
|
|
|
06-28-2010, 05:38 PM
|
#15
|
|
Senior Member
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
|
Quote:
|
The seamonkey libs should not be required to use Firefox, although it will probably fall back on them if some of Firefox's libraries are removed.
|
I see where my mistake was. Did not pay enough attention to the /usr/bin/firefox script, and only looked at the ldd output 
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 12:54 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|