Users and developers helping users with generic and technical Pale Moon issues on all operating systems.
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
-
Aleph
Unread post
by Aleph » 2015-07-05, 07:21
Hi friends,
I installed Palemoon on "Antix 15" but it crashes all the time.
Gtk theme: Faenza-Cupertino-Mini
I had installed AdblockPlus and Ghostery, deleted the two add-ons but the crashes persists.
Any advice?
Info:
Code: Select all
$ palemoon
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkRange::activate-slider' of type `gboolean' from rc file value "((GString*) 0x7efff71fe9a0)" of type `GString'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkRange::activate-slider' of type `gboolean' from rc file value "((GString*) 0x7efff71fe9a0)" of type `GString'
Violación de segmento
luis@antix1:~
$
###!!! [Child][SyncChannel] Error: Channel error: cannot send/recv
Code: Select all
$ inxi -F
System: Host: antix1 Kernel: 4.0.5-antix.2-amd64-smp x86_64 (64 bit)
Desktop: IceWM 1.3.8
Distro: antiX-15-V_x64-full Killah P 30 June 2015
Machine: System: LENOVO product: 6457CB6 v: ThinkPad T61
Mobo: LENOVO model: 6457CB6
Bios: LENOVO v: 7LETB2WW (2.12 ) date: 02/20/2008
CPU: Dual core Intel Core2 Duo T7500 (-MCP-) cache: 4096 KB
clock speeds: max: 2201 MHz 1: 800 MHz 2: 1600 MHz
Graphics: Card: NVIDIA G86M [Quadro NVS 140M]
Display Server: X.Org 1.16.4 driver: nvidia
Resolution: 1280x800@59.91hz
GLX Renderer: Quadro NVS 140M/PCIe/SSE2
GLX Version: 3.3.0 NVIDIA 340.76
Audio: Card Intel 82801H (ICH8 Family) HD Audio Controller
driver: snd_hda_intel
Sound: ALSA v: k4.0.5-antix.2-amd64-smp
Network: Card-1: Intel 82566MM Gigabit Network Connection driver: e1000e
IF: eth0 state: down mac: 00:1c:25:78:64:e3
Card-2: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection
driver: iwl4965
IF: wlan0 state: up mac: 00:1f:3b:35:4c:57
Drives: HDD Total Size: 100.0GB (7.9% used)
ID-1: /dev/sda model: HITACHI_HTS72201 size: 100.0GB
Partition: ID-1: / size: 17G used: 3.6G (23%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 4.29GB used: 0.00GB (0%) fs: swap dev: /dev/sda4
Sensors: System Temperatures: cpu: 58.0C mobo: 46.0C gpu: 65C
Fan Speeds (in rpm): cpu: 3065
Info: Processes: 116 Uptime: 48 min Memory: 508.9/3890.2MB
Client: Shell (bash) inxi: 2.2.25
-
Aleph
Unread post
by Aleph » 2015-07-06, 09:15
Thanks SvenG,
My gtk2 theme was Mediterraneanwhite, I changed /gtk-2.0/gtkrc
Code: Select all
GtkScrollbar::activate-slider=FALSE
by
but after a reboot it doesen't wok...
More ideas?
-
SvenG
Unread post
by SvenG » 2015-07-06, 09:33
Aleph wrote:More ideas?
Unfortunately not, that was the only real solution that was given (many reports had no reply). Maybe try another theme? Just to see if it is theme related.
-
Aleph
Unread post
by Aleph » 2015-07-06, 10:43
I tried others themes but not solution...
I was testing more deeply. The crash happens always when I do click on the links of this webpage:
http://www.huffingtonpost.es/
Could be a clue?
-
SvenG
Unread post
by SvenG » 2015-07-06, 11:06
Aleph wrote:I tried others themes but not solution...
I was testing more deeply. The crash happens always when I do click on the links of this webpage:
http://www.huffingtonpost.es/
Could be a clue?
Ah, so it is not "always" crashing, just in certain situations? Does it happen on other sites as well or just this particular one?
The Gtk message might in this case be totally unrelated to the crash. Have you tried to use that website in a blank profile? On my end browsing that website with a blank Pale Moon profile doesn't cause any issues.
-
Aleph
Unread post
by Aleph » 2015-07-06, 11:31
Sorry SvenG, how should I set a blank profile...?
-
SvenG
Unread post
by SvenG » 2015-07-06, 11:43
Aleph wrote:Sorry SvenG, how should I set a blank profile...?
Open Pale Moon from the terminal as
palemoon -p, this opens the profile manager, next create a new profile and start Pale Moon.
-
Aleph
Unread post
by Aleph » 2015-07-06, 11:52
Thje same problen with a blank profile:
Code: Select all
$ palemoon -p
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkRange::activate-slider' of type `gboolean' from rc file value "((GString*) 0x7f934c65f2c0)" of type `GString'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkRange::activate-slider' of type `gboolean' from rc file value "((GString*) 0x7f934c65f2c0)" of type `GString'
Violación de segmento
-
SvenG
Unread post
by SvenG » 2015-07-06, 14:22
Do any of these messages appear as well, when you just open and close Pale Moon (without causing a crash)? That Gtk is complaining because of something is actually rather normal when you start a program but doesn't necessarily cause any trouble. My guess is that these are normal and we only have the segfault (Violación de segmento?) which can be caused by lots of things.
-
Aleph
Unread post
by Aleph » 2015-07-06, 14:43
i tried it now and Yes, also appears without crash:..
Code: Select all
$ palemoon
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkRange::activate-slider' of type `gboolean' from rc file value "((GString*) 0x7f8ee57d7b20)" of type `GString'
luis@antix1:~
-
Aleph
Unread post
by Aleph » 2015-07-08, 08:27
Well, if we have not a solution I will uninstall Palemoon because is not usable.
I will wait for a new release.
Thanks.
-
SvenG
Unread post
by SvenG » 2015-07-08, 08:35
Well, I have no ideas that lead to a specific point. It just crashes on certain sites, which could be caused a lots of things, I imagine stuff such as hardware acceleration, a buggy plugin or driver (stuff that isn't even related to the browser directly).
-
Night Wing
- Knows the dark side
- Posts: 5174
- Joined: 2011-10-03, 10:19
- Location: Piney Woods of Southeast Texas, USA
Unread post
by Night Wing » 2015-07-08, 09:17
Aleph wrote:Well, if we have not a solution I will uninstall Palemoon because is not usable.
I will wait for a new release.
I clicked on every link on that website's page and no crashing and I'm using 64 bit linux Pale Moon 25.5.0 in 64 bit linux Mint 17.
In my opinion, the stability you're experiencing is not on Pale Moon's side. I'm guessing you've done something on your end which is making Pale Moon unstable so waiting for a new release probably won't solve your problem until the underlying problem is found.
Linux Mint 21.3 (Virginia) Xfce w/ Linux Pale Moon, Linux Waterfox, Linux SeaLion, Linux Firefox
MX Linux 23.2 (Libretto) Xfce w/ Linux Pale Moon, Linux Waterfox, Linux SeaLion, Linux Firefox
Linux Debian 12.5 (Bookworm) Xfce w/ Linux Pale Moon, Linux Waterfox, Linux SeaLion, Linux Firefox
-
Moonchild
- Pale Moon guru
- Posts: 35636
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
-
Contact:
Unread post
by Moonchild » 2015-07-08, 11:58
If a problem is found that can't be reproduced by us, and the reporter bails before the cause is found, then "waiting for a new release" will not help, either, because there won't be anything known to the developers to "fix".
It's your choice to uninstall and stop here, but that inherently means the problem for you won't go away with a later version, either. We aren't magicians
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
SvenG
Unread post
by SvenG » 2015-07-08, 15:22
While you are right, Moonchild, it doesn't help the user now. If he can't track down what is the problem, the only thing he has is a crashing browser, which is not necessarily a pleasure to use. So he is at least in the short run better off switching to another browser, an understandable move. The more important question is: how can we help him find the culprit?
-
Axiomatic
Unread post
by Axiomatic » 2015-07-08, 16:17
@Aleph can you navigate to 'about:support' and copy, and paste all the information given inside a code tag? (Specifically the Important Modified Preferences, and your Graphics sections.)
Off-topic:
Are there any binaries for the Linux builds with debugging symbols enabled? If so someone should provide Aleph with a build. Then we can use gdb to be certain whether is a Pale Moon issue or a third party interaction issue.
-
Aleph
Unread post
by Aleph » 2015-07-08, 16:53
Hi Axiomatic here is:
Code: Select all
Application Basics
------------------
Name: Pale Moon
Version: 25.5.0
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.5) Gecko/20150625 Firefox/31.9 PaleMoon/25.5.0
Extensions
----------
Important Modified Preferences
------------------------------
accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.smart_size_cached_value: 307200
browser.cache.disk.smart_size.first_run: false
browser.places.smartBookmarksVersion: 4
browser.startup.homepage_override.buildID: 20150625145429
browser.startup.homepage_override.mstone: 25.5.0
extensions.lastAppVersion: 25.5.0
network.cookie.prefsMigrated: true
places.history.expiration.transient_current_max_pages: 101981
plugin.importedState: true
privacy.sanitize.migrateFx3Prefs: true
Graphics
--------
Adapter Description: NVIDIA Corporation -- Quadro NVS 140M/PCIe/SSE2
Device ID: Quadro NVS 140M/PCIe/SSE2
Driver Version: 3.3.0 NVIDIA 340.76
GPU Accelerated Windows: 0/1 Basic
Vendor ID: NVIDIA Corporation
WebGL Renderer: NVIDIA Corporation -- Quadro NVS 140M/PCIe/SSE2
windowLayerManagerRemote: false
AzureCanvasBackend: cairo
AzureContentBackend: cairo
AzureFallbackCanvasBackend: none
JavaScript
----------
Incremental GC: true
Accessibility
-------------
Activated: false
Prevent Accessibility: 1
Library Versions
----------------
NSPR
Expected minimum version: 4.10.8
Version in use: 4.10.8
NSS
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSSMIME
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSSSL
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSUTIL
Expected minimum version: 3.19
Version in use: 3.19
-
Axiomatic
Unread post
by Axiomatic » 2015-07-09, 00:31
Aleph wrote:Hi Axiomatic here is:
Code: Select all
Application Basics
------------------
Name: Pale Moon
Version: 25.5.0
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.5) Gecko/20150625 Firefox/31.9 PaleMoon/25.5.0
Extensions
----------
Important Modified Preferences
------------------------------
accessibility.typeaheadfind.flashBar: 0
browser.cache.disk.smart_size_cached_value: 307200
browser.cache.disk.smart_size.first_run: false
browser.places.smartBookmarksVersion: 4
browser.startup.homepage_override.buildID: 20150625145429
browser.startup.homepage_override.mstone: 25.5.0
extensions.lastAppVersion: 25.5.0
network.cookie.prefsMigrated: true
places.history.expiration.transient_current_max_pages: 101981
plugin.importedState: true
privacy.sanitize.migrateFx3Prefs: true
Graphics
--------
Adapter Description: NVIDIA Corporation -- Quadro NVS 140M/PCIe/SSE2
Device ID: Quadro NVS 140M/PCIe/SSE2
Driver Version: 3.3.0 NVIDIA 340.76
GPU Accelerated Windows: 0/1 Basic
Vendor ID: NVIDIA Corporation
WebGL Renderer: NVIDIA Corporation -- Quadro NVS 140M/PCIe/SSE2
windowLayerManagerRemote: false
AzureCanvasBackend: cairo
AzureContentBackend: cairo
AzureFallbackCanvasBackend: none
JavaScript
----------
Incremental GC: true
Accessibility
-------------
Activated: false
Prevent Accessibility: 1
Library Versions
----------------
NSPR
Expected minimum version: 4.10.8
Version in use: 4.10.8
NSS
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSSMIME
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSSSL
Expected minimum version: 3.19 Basic ECC
Version in use: 3.19 Basic ECC
NSSUTIL
Expected minimum version: 3.19
Version in use: 3.19
This is a long shot the only reason I suggest this is because you are running a NVIDIA graphics card. Try changing the about:config preference of 'gfx.xrender.enabled' to 'false'. Side note: You may also have to set 'layers.acceleration.force-enabled' to 'true', and 'gfx.work-around-driver-bugs' to 'false' since well, NVIDIA. (Restart your browser after you applied the changes, and see if you can recreate the segmentation fault.)