Package Details: palemoon 1:33.4.1-1

Git Clone URL: https://aur.archlinux.org/palemoon.git (read-only, click to copy)
Package Base: palemoon
Description: Open source web browser based on Firefox focusing on efficiency.
Upstream URL: https://www.palemoon.org/
Keywords: browser goanna web
Licenses: MPL-2.0
Submitter: artiom
Maintainer: WorMzy
Last Packager: WorMzy
Votes: 141
Popularity: 0.121058
First Submitted: 2014-06-05 10:54 (UTC)
Last Updated: 2024-11-05 20:54 (UTC)

Pinned Comments

WorMzy commented on 2021-03-02 16:19 (UTC) (edited on 2022-08-03 21:12 (UTC) by WorMzy)

The following key is used to sign release commits:

40481E7B8FCF9CEC

Import it into your keyring however you want.

https://wiki.archlinux.org/index.php/GnuPG#Import_a_public_key

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 38 Next › Last »

jghodd commented on 2019-03-27 19:00 (UTC) (edited on 2019-03-27 19:07 (UTC) by jghodd)

@WorMzy I'm using the latest version of libxt - even downloaded the source from xorg and rebuilt it to make sure. same problem.

the output from pacman -Qkk libxt:

libxt: 340 total files, 0 altered files

i'll check the latest update and see if it changes anything. i have a debug build of palemoon to work with, but it still shows some optimizations even though as far as i could tell, all optimization was turned off via mozconfig.in - so, i can't see all variable/parameter values when i run a backtrace in gdb.

this issue has apparently come up a number of times with palemoon. unfortunately, it appears that as soon as someone identifies libxt as the issue, all discussion in the relevant threads abruptly ends providing no solutions.

Edit: i wouldn;t assume there's something wrong with my system. it could be that i have the latest version of something installed that interacts badly with a bug in palemoon. because i maintain my own distro, i have to keep every package up to date, all the time.

WorMzy commented on 2019-03-26 18:52 (UTC) (edited on 2019-03-26 19:07 (UTC) by WorMzy)

No problems here (package built Mon 25 Feb 2019). Will try rebuilding, but since you have the same issue with the -bin package, I would guess there's an issue on your system.

pacman -Qkk libxt would be a good place to start checking.

EDIT: Rebuild completed with no change in behaviour.

jghodd commented on 2019-03-26 17:22 (UTC)

This version (28.4.0) crashes (SEGV) when loading libXt.so - so does the binary package, btw.

WorMzy commented on 2019-02-25 14:29 (UTC)

Thanks for this flag. I am indeed Away From Keyboard, but I have my laptop with my ssh keys on it this time, so update pushed. :)

WorMzy commented on 2019-01-24 22:42 (UTC)

Thanks for the heads up, haawda. Update pushed.

haawda commented on 2019-01-24 21:50 (UTC) (edited on 2019-01-24 21:50 (UTC) by haawda)

Well, palemoon 28.3.0 obviously was quite shortliving, there now is 28.3.1. The "quick version bump"-Method applies here, too.

WorMzy commented on 2019-01-24 19:32 (UTC) (edited on 2019-01-24 19:32 (UTC) by WorMzy)

Sorry for the delay, I've pushed the update out now.

I fully expect the next PM release to be around the end of February, as that's when I go to Japan for two weeks. :P

EDIT: Thanks for confirming that in the interim, barius.

barius commented on 2019-01-20 01:47 (UTC)

Just to let you know, the "quick pkgver bump" approach worked perfectly for me (v 28.2.2 -> 28.3.0).

WorMzy commented on 2019-01-18 09:26 (UTC)

I'm starting to think these updates are timed to me being AFK... :o

I don't currently have access to my dev machine, but I'll update the package ASAP. For the impatient, I don't think there's anything build-breaking in the release notes, so this should be a quick pkgver bump. There is also the palemoon-bin package, which is already updated.

WorMzy commented on 2018-12-11 17:29 (UTC)

I'm AFK until next week, if I get chance I'll update the package before I get home, but otherwise it'll be updated on the 16th/17th.

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 38 Next › Last »