>Synopsis: panic: malloc: allocation too large, type = 33, size =
>292057776136
>Category: kernel
>Environment:
System : OpenBSD 6.4
Details : OpenBSD 6.4 (GENERIC.MP) #1: Mon Nov 26 10:18:14 CET 2018
xlock shows a custom *.xpm picture once enabled. I'm using spectrwm call
for xlock program.
# cat ~/.spectrwm.conf
...
program[lock] = /usr/X11R6/bin/xlock -mode image -bitmap
/etc/X11/xenodm/pixmaps/OpenBSD_custom.xpm -count 1
...
The same issue is present with
On Sat, Dec 08, 2018 at 10:46:31AM +0300, Denis wrote:
> Five times of ten getting Segmentation fault when exit from xlock
> program. Tested on X.org -current with xenodm Display Manager (startx
> -current cause the same problem also with xlock exit).
>
> The machine is on SoC AMD GX-420CA with
On 8 Dec 2018, at 10:33, Theo de Raadt wrote:
> how funny. You still don't get it. Noone cares because noone believe you!
OK. Thanks.
Arrigo
>Theo, honestly, I actually pay m:tier Platinum support for myself and
>my clients, I am a fervent OpenBSD supporter and I opened what is a
>bug.
We don't CARE.
M:tier is not OpenBSD.
Antoine Jacoutot does not work for M:tier
You sent an email and you ignored the replies. And kept talking!
On 8 Dec 2018, at 10:15, Theo de Raadt wrote:
> If you cannot respect the people who write the software, you probably
> shouldn't run the software.
>
> Just go away.
>
> You are acting like a gigantic dickhead.
Theo, honestly, I actually pay m:tier Platinum support for myself and my
clients,
Klemens Nanni wrote:
> On Tue, Dec 04, 2018 at 10:19:55AM +0100, Solene Rapenne wrote:
> >
> > ssh(1) doesn't seem to resolve a ProxyJump hostname using /etc/hosts when
> > the
> > hostname is a fqdn.
> No comment (yet) on whether this should be changed or not, but a general
> advise below.
>
>On 8 Dec 2018, at 09:50, Theo de Raadt wrote:
>[...]
>> So please take your arrogance elsewhere.
>
>Thank you pot!
>
>Arrigo=20
>
>P.S. just a warning which returns a fail return code is a bug
>Contempt does not make it magically return 0 nor does it make the behaviour
>correct. Neither does
On 8 Dec 2018, at 09:50, Theo de Raadt wrote:
[...]
> So please take your arrogance elsewhere.
Thank you pot!
Arrigo
P.S. “just a warning” which returns a fail return code is a bug. Contempt does
not make it magically return 0 nor does it make the behaviour correct. Neither
does doing a c
>Theo, thank you for your wonderful use of language.
>
>I have taken note of your pearls of wisdom along with the innate perfection
>which you exhale with every breath.
>
>I will strive to reach your masterful superior intellect.
Wow.
>In the meantime I'll check that indeed syspatch fails safe
On 8 Dec 2018, at 08:25, Theo de Raadt wrote:
> Will you start paying attention??
>
> You have been told repeatedly that it is not an error. It is simply a
> message.
>
> Please stop assuming the worst!
Theo, thank you for your wonderful use of language.
I have taken note of your pearls of
11 matches
Mail list logo
