i don't know whether this is a problem with new p7zip or jalview's source, so the safest way is to use the old version which works for now. I keep a local branch for p7zip update here, just in case we found a better solution.

1 members found this post helpful.

It's now updated in master branch.

Thanks

For me the version of cryptography in SBo (=1.1.1) does not build on the latest current and it no longer worked after updating. Updating cryptography to the current stable version (=1.3) works fine.

You must be using 14.1 branch.
That package have been updated to 1.2.3 in master branch

Not sure what is going on, as I'm using the current branch from Ponce in sbopkg.conf and it has updated.

Anyway ignore if it has already been updated and builds.

are you following the instructions on how to use the repository you choose with sbopkg?
namely, do you sync by doing a
like written there?

Or, you can switch to GIT master branch via sbopkg (instructions)

I indeed follow this blog and normally sync by running "sbopkg -r" as suggested in that blog. That seems to both update and complete without errors. When I do the update this way it remains at the 1.1.1 version. Deleting the whole git-tree and then running "sbopkg -r" gives the expected version.

So somehow git got confused, but didn't give a clear indication. Bizarre to put it mildly.

that step it's necessary because the branch gets rebased and git doesn't know how to merge it.

if you do a "sbopkg -r" without deleting git spits trash and tells you that you are still at an older commit than the one you can see on github.

I edited the wiki page trying to make the thing clearer.

Could someone take a look at Pale Moon?

I have tried to use the SBo SlackBuild and the one from the ponce's GitHub repo to build Pale Moon 25.8.1 and 26.1.1 on a fresh full -current (Fri Apr 1 21:17:37 UTC 2016) but it will not launch. It has been like this since February sometime.

If I try to launch from a terminal all I get is:

Thanks.

*I'm going to run a memory test, but I highly doubt that it has to do with my hardware since I have 2 identical machines and it is failing on both of them.

@Skaendo: did you see this thread? http://www.linuxquestions.org/questi...nt-4175559604/ It gives me the impression that maybe it would be better to move on. But as I have never used it, this is just a hearsay.

I have been using 25.8.1 and 26.1.1, built (not from source, just repackaging) from SBo and only recently (February sometime) have I started having problems.

The patch that they are talking about for oxygen is easily avoided by using this (from KDE menu):
Though that is not needed for any other DE.

hi Skaendo, as David already wrote, no segfault here using the version on SBo.

could it be an issue with your theme? try creating a new user from scratch and use some gtk+2 theme from xfce (you can use xfce's settings if you are using that DE or, for example, lxappearance to easily switch the theme).

I am having the same issue on Cinnamon. I have the same issue on a full clean/reformat -current install. I will try XFCE but that will have to wait, I have begun building 26.1.1 from source using the SlackBuild that was in the thread Didier pointed to. Might take a while; 2GHz Core2Duo, 4 GB RAM.

I did an on-board diagnostic of my memory, nothing showed up.

*Nothing else have I changed since I began using Pale Moon. I've used the same launcher command, same KDE theme, etc.

I do have Pale Moon running on my main rig here, but I installed 26.1.1 some time ago, and been updating Slackware as usual. This only seems to be happening on a fresh install.

This issue leaded me to an interesting (although off-topic, sorry) article.