Hi David,
> I'm having some weird problems with ipv6 on my box.
It'll never catch on. :-)
> but w3m via ipv6 doesn't:
> [darose@darsys12 ~]$ w3m -6 -dump ipv6.google.com
> ... hangs forever ...
I suspect the difference between how well your network/ISP is copying
with TCP and UDP; HTTP connect
On 07/23/2018 10:02 AM, Andy Pieters wrote:
> Has anyone seen this behaviour before and know of a durable fix short
> of scripting plasma startup with a delayed kill+restart of
> kglobalaccel5?
Andy,
It is unclear what exactly is happening. It almost sounds like there is
something in your profi
Done
Em julho 23, 2018 14:14 David Rosenstrauch escreveu:
Makes some sense. I'll take a look on my router and see if perhaps I'm
inadvertently blocking some ICMP packets.
That said, one thing doesn't quite seem to fit with this explanation:
Why would "curl -6 ipv6.google.com" while "w3m -6 -dum
On 07/23/2018 12:42 PM, Giancarlo Razzolini via arch-general wrote:
Em julho 23, 2018 12:46 David Rosenstrauch escreveu:
I'm really stumped as to how ipv6 could partially fail like this only
on specific apps. Seems like it should either completely work or
completely fail.
Anyone have a
Em julho 23, 2018 12:46 David Rosenstrauch escreveu:
I'm really stumped as to how ipv6 could partially fail like this only on
specific apps. Seems like it should either completely work or
completely fail.
Anyone have any idea what might be happening here and/or how to fix?
Hi David,
If
I'm having some weird problems with ipv6 on my box.
My ISP is set up for ipv6, my router and server both seem to have valid
ipv6 addresses, and ipv6 connectivity seems to (nominally) be working:
[darose@darsys12 ~]$ ping ipv6.google.com
PING ipv6.google.com(lga25s63-in-x0e.1e100.net
(2607:f8b
Hi
Every time I start my computer, plasma does not properly
detect/respond to global hotkeys, in particular, WIN+anything
combination.
After I open a terminal from inside plasma, kill the kglobalaccel5
program and launch it again, all the WIN+ hotkeys work again.
During the time that it is not w
Am 23.07.2018 um 10:53 schrieb Levente Polyak via arch-general:
On 07/23/2018 10:43 AM, Ralf Mardorf wrote:
[1]
4.17.8 still in Core allegedly also contains it.
$ grep pkg.e.= linux/repos/core-x86_64/PKGBUILD
pkgver=4.17.8
pkgrel=1
$ grep SALSA linux/repos/core-x86_64/config
CONFIG_CRYPTO_SALSA
Am 23.07.2018 um 10:58 schrieb Ralf Mardorf:
PS:
You wrote that with the downgraded kernel it works again.
I don't know in which way
CONFIG_CRYPTO_SALSA20=m
and
CONFIG_CRYPTO_SALSA20_X86_64=m
are related to each other, perhaps it's correct that
CONFIG_CRYPTO_SALSA20_X86_64 isn't shown by th
On Mon, 2018-07-23 at 10:53 +0200, Levente Polyak wrote:
> No, it won't come back. The reason for the mismatch is that the config
> in the checkout is not regularly updated/synced for every minor kernel
> bump and removed options will remain there while the effective config at
> the end (which you
PS:
You wrote that with the downgraded kernel it works again.
I don't know in which way
CONFIG_CRYPTO_SALSA20=m
and
CONFIG_CRYPTO_SALSA20_X86_64=m
are related to each other, perhaps it's correct that
CONFIG_CRYPTO_SALSA20_X86_64 isn't shown by the config of the build
kernel.
What's the outpu
On 07/23/2018 10:43 AM, Ralf Mardorf wrote:
> [1]
> 4.17.8 still in Core allegedly also contains it.
>
> $ grep pkg.e.= linux/repos/core-x86_64/PKGBUILD
> pkgver=4.17.8
> pkgrel=1
> $ grep SALSA linux/repos/core-x86_64/config
> CONFIG_CRYPTO_SALSA20=m
> CONFIG_CRYPTO_SALSA20_X86_64=m
>
> I unins
Am 23.07.2018 um 10:23 schrieb Ralph Corderoy:
Hi Peter,
Checked .config in linux-headers-4.9-1-x86_64.pkg.tar.xz (latest
version I could find in the archive)
Search more carefully.
$ seq 9 10 | sort
10
9
$
$ curl -sSg https://archive.archlinux.org/packages/l/linux/
On Mon, 23 Jul 2018 10:27:45 +0200, Peter Nabbefeld wrote:
>Tried to get that file from testing but couldn't find out how. Just
>activating the repo didn't help, probably I'd have to use some other
>mirror.
Did you run pacman -Syu?
If so, then the mirror perhaps isn't already synced, since it just
Am 23.07.2018 um 09:59 schrieb Ralf Mardorf:
On Mon, 23 Jul 2018 08:47:51 +0200, Peter Nabbefeld wrote:
CONFIG_CRYPTO_SALSA20_X86_64=m
I don't know if this helps. 4.17.9-1 moved from Staging to Testing and
at least the version from Staging contains CONFIG_CRYPTO_SALSA20.
$ uname -rm; zgrep SA
Hi Peter,
> Checked .config in linux-headers-4.9-1-x86_64.pkg.tar.xz (latest
> version I could find in the archive)
Search more carefully.
$ seq 9 10 | sort
10
9
$
$ curl -sSg https://archive.archlinux.org/packages/l/linux/ |
> egrep -o '\ sort -V | uniq -c |
> pr -t3
On Mon, 23 Jul 2018 08:47:51 +0200, Peter Nabbefeld wrote:
>CONFIG_CRYPTO_SALSA20_X86_64=m
I don't know if this helps. 4.17.9-1 moved from Staging to Testing and
at least the version from Staging contains CONFIG_CRYPTO_SALSA20.
$ uname -rm; zgrep SALSA /proc/config.gz
4.17.9-1-ARCH x86_64
CONFI
19 matches
Mail list logo
