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.
Nope, this issue still a problem with Firefox 3.5 from -Current and when libsafe is installed.
If i comment the libsafe entry in /etc/ld.so.preload, the Firefox will work as it is
Nope, this issue still a problem with Firefox 3.5 from -Current and when libsafe is installed.
If i comment the libsafe entry in /etc/ld.so.preload, the Firefox will work as it is
I expected this. Have you reported this issue directly to Pat or one of the Slackware team members? This is especially important now that FF3.5 is in -current.
I expected this. Have you reported this issue directly to Pat or one of the Slackware team members? This is especially important now that FF3.5 is in -current.
I wonder whether Pat and his team are responsible for this as libsafe is not included in official slackware distribution. I think you should report it to mozilla instead.
I wonder whether Pat and his team are responsible for this as libsafe is not included in official slackware distribution. I think you should report it to mozilla instead.
Good eye on that one. Agreed.
Also, it might be worth checking out if one of the distros that have libsafe (maybe Fedora?) have any work arounds for FF 3.5 in place.
I expected this. Have you reported this issue directly to Pat or one of the Slackware team members? This is especially important now that FF3.5 is in -current.
I have reported this to Eric, but at that time Firefox 3.5 wasn't included in -Current, so i stopped bothering him
I did have reported this to Pat this morning, and i'm sure he (or one of the crews) will come out with a solution in the following days
I wonder whether Pat and his team are responsible for this as libsafe is not included in official slackware distribution. I think you should report it to mozilla instead.
indeed. It only occurred when libsafe is installed.
But this works on 3.0.11 but not in 3.5 and it happened on a default configuration (in this case libsafe is installed intentionally by the users with some expectation that it would give them better protection to some security problems with other applications)
Sorry, I only "find -iname '*safe*'" in 32-current mirror but not in 64bit ;( I hope you can get some idea from Pat...
That's probably because the last release of libsafe was May 21 2002,
and it's 32-bit, iirc. Alien Bob was building everything in -current
for Slackware for x86_64, and probably skipped such software as that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
