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.
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.
|
|
|
01-15-2014, 05:39 AM
|
#1
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Rep:
|
Firefox/Thunderbird crash on Slackware64 14.1
Hi everyone.
I decided to install a Slackware 14.1 (64 bits version). However, I got some problems with Firefox/Thundebird. For example, when I launch Firefox, I get this message :
Code:
GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
And after a few moment (it can be 10 seconds, or 5 hours, it's very randomly), Firefox crashes with a "segmentation fault". Same problem with Thunderbird. The bug has been included in Bugzilla, but nobody is working on it... Am I the only affected by this problem? I can't use my Slackware, too many crashes...
I tried:
- remove my profile and all my extensions
- test latest version of Firefox (and even recompile my own version)
- I tested my memory with memtest
The problem is still there... One more point: I do not have crashes on Slackware64 14.0...
Is anybody can help me identifying and solving this problem? In another case, I'll have to switch to another Linux distribution, and I don't really want it..;
Thanks a lot!
|
|
|
01-15-2014, 09:45 AM
|
#2
|
Member
Registered: Jun 2013
Location: Germany
Distribution: Slackware
Posts: 174
Rep:
|
i can tell you, that i cant recreate this problem so you may be the only one with it. what i dont know is why, sorry.
sys_page_size sounds like hardware. maybe you give us some more data about you machine?! or maybe its the kernel? do the kernel versions of the other distributions differ from the slackware one or do you have another one compiled than standard?
sry for fishing blindliy, i do not really have a clue right now, but maybe some more info helps the others to help you.
greatings
|
|
|
01-15-2014, 12:58 PM
|
#3
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
Hum, I'm not sure to be the only one affected by the problem. You can check this Google page, many people talk about crashes. In my case, they're really randomly (no crash this afternoon, for the moment...).
I check the md5sum of the iso, upgraded all my packages with slackpkg. I use the generic kernel from Slackware64 14.1. My config: Intel i5, 8 Go RAM DDR3 and ATI Radeon 4850 HD.
The problem is: I do not have informations, except a "GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed" when starting Firefox, and a "segmentation fault" at the crash. Do you have the Glib critical error with Slackware64 14.1 ?
|
|
|
01-15-2014, 04:24 PM
|
#4
|
Member
Registered: Nov 2008
Location: US
Distribution: slackware
Posts: 782
|
Hi counthark,
I also get that message from Firefox, and yes it sometimes will crash. The same thing occurs when I happen to use a non-slackware OS (BSD), both cases are rare with Slackware being far more infrequent. Both systems also use the same rev of Firefox.
I suspect it is a Firefox bug, the next time it happens try:
and see if Firefox is still active. When it happens to me, Firefox loses the DISPLAY and starts pegging the CPU. If your issue is the same as mine, to fix, either kickoff Firefox again or kill the "orphan" process.
|
|
|
01-15-2014, 05:30 PM
|
#5
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
Thanks for your response.
For me, it's not a rare problem. No crash this afternon, and three crashes in three hours this evening. Firefox is my mainly software (I work on CMS), so I can't use my Slackware system (I think I will go back to Windows if I can't solve this issue). I installed firefox 26, and sent report to the Firefox team. On the other hand, the Firefox included in the tor package does not crash.
For me, when Firefox crashes, there is no active process. Just a "segmentation fault".
|
|
|
01-15-2014, 05:47 PM
|
#6
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
Four crashes in ten minutes. What must I do? I really have to find a solution to have a stable version of Firefox...
Last edited by counthark; 01-15-2014 at 06:06 PM.
|
|
|
01-15-2014, 06:13 PM
|
#7
|
Member
Registered: Jan 2014
Posts: 186
Rep:
|
From what I have read the g_slice_set_config error does not cause crashes, or any other problem. That is why the Mozilla ticket has been open for more than a year.
Changing the following about:config setting fixed my intermittent crashing problems in Firefox:
gfx.xrender.enabled false
I still have the g_slice_set_config error, but no crashing.
|
|
|
01-15-2014, 07:34 PM
|
#8
|
Member
Registered: Jun 2013
Location: Germany
Distribution: Slackware
Posts: 174
Rep:
|
i checked, my server with 32bit 14.1 gets the error too, but doesnt crash.. on my desktop i dont get the message with slack64 14.1
so its not 100% reproducable (i hope i write this right) for me.
didnt change anything in firefox's config besides the language.
|
|
|
01-16-2014, 03:45 AM
|
#9
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
The gfx.xrender.enabled false didn't solve my problem...
I think I will give up soon and test another Linux distribution, or go back to Windows XP (which is more stable... sic). I can't identify the issue, I do not have any log or any information! Just a fucking "segmentation fault", houra! What I know is my Slackware is unusable... Believe me, a Firefox crashing 10 times a day is not very funny.
I would like to fix the problem, but... what must I do? I'm working on it for a week, and I'm tired now. I'm not a difficult user, I just want a stable Firefox, which is my main software for working. I don't mind about other things. Just a Firefox. And it crashes on my Slackware
You said you have the issue on your 32 bits server, and not on your 64 bits desktop. So, what's the difference between those two machines?
Last edited by counthark; 01-16-2014 at 03:49 AM.
|
|
|
01-16-2014, 04:45 AM
|
#10
|
Member
Registered: Jul 2009
Location: NYC
Distribution: Slackware64-multilib 15.0, SARPI, artix
Posts: 408
Rep:
|
Maybe you need to install/update your graphics drivers?
You could also try enabling/disabling hardware acceleration in FF's option menu.
It might also could have to do with flash player. Try disabling plugins.
|
|
|
01-16-2014, 04:48 AM
|
#11
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
That's the first thing I tried. My firefox crashes even if I remove my profile (and so, no extensions). I disabled hardware acceleration in Firefox, and also in Xfce, no results. I use radeon driver with Xorg (Slackware64 14.1), and I do not really want to install fglrx from ATI...
Do you know a solution to have more informations than a "segfault"?
|
|
|
01-16-2014, 04:55 AM
|
#12
|
Member
Registered: Jan 2014
Posts: 163
Rep:
|
being new to slack, i have nothing constructive to add to help; only to chip in that this message appears when i run FF (and some other programs) intermittently. Nothing seems to crash out though.
this machine is slack 14.1 64bit on asus 1225b radeon hd 6290 AMD Brazos APU
my other thread regarding total failure of flash plugin has provided me some advice to try a different kernel... i intend to do this when i can drum up courage and time :-) and see what happens..... it may be a hardware/kernel/module thing..... only thing is, no other distros ive tried on this machine have the problem in this thread (or the flash plugin). All rather odd to me :-)
keep trying things.
thank you
|
|
|
01-16-2014, 04:58 AM
|
#13
|
Member
Registered: Jul 2009
Location: NYC
Distribution: Slackware64-multilib 15.0, SARPI, artix
Posts: 408
Rep:
|
Well, plugins are different than extensions. Go to about:plugins and menu -> addons -> plugins
Sorry, I can't be more helpful. I just thought I'd throw some basic ideas out in case you missed one.
|
|
|
01-16-2014, 05:03 AM
|
#14
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
When I tried with a new profile, I do not have any extensions... or plugins
Thanks for your posts, I appreciate. I think I will test another GNU/Linux distribution on another hard disk (I want to stay on Slackware, my first Linux distribution...). I have to find a solution, it's the first time I can't solve a problem, because I don't have informations, except this fucking segfault. Every nights, I dream about segmentation fault
Last edited by counthark; 01-16-2014 at 05:05 AM.
|
|
|
01-17-2014, 05:32 PM
|
#15
|
LQ Newbie
Registered: Jan 2014
Location: France
Posts: 10
Original Poster
Rep:
|
More informations. When Firefox crashes, I get this error tracing with gdb:
Code:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff345f77b in ?? () from /usr/lib64/firefox-24.2.0/libxul.so
|
|
|
All times are GMT -5. The time now is 09:52 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
|
|