Hi Timo,
on 17 Dec 17 at 03:14:53 PM +, Timo Myyrä
wrote:
Hmm,
It indeed seems that the setting causing this is icon_position
in the config
file. When its not off, the icons are enabled and the dlopen
occurs.
What do you think about following patch, it adds
"T.Lux" writes:
> On 15 October 2017 at 16:26 GMT, Sebastien Marie wrote:
>
>> On Sun, Oct 15, 2017 at 11:56:31AM -0400, T.Lux wrote:
>>> On 15 October 2017 at 05:19 GMT, Sebastien Marie wrote:
>>>
>>> > 2) recompile the port with debugging symbol, and extract the >
>>>
Sebastien Marie writes:
> On Sun, Oct 15, 2017 at 11:56:31AM -0400, T.Lux wrote:
>
>> On 15 October 2017 at 05:19 GMT, Sebastien Marie wrote:
>>
>> > 2) recompile the port with debugging symbol, and extract the backtrace
>> > of the failure with gdb ?
>> >
>> > $ cd
On 15 October 2017 at 16:26 GMT, Sebastien Marie wrote:
On Sun, Oct 15, 2017 at 11:56:31AM -0400, T.Lux wrote:
On 15 October 2017 at 05:19 GMT, Sebastien Marie wrote:
> 2) recompile the port with debugging symbol, and extract the
> backtrace
> of the failure with gdb ?
>
> $ cd
On Sun, Oct 15, 2017 at 11:56:31AM -0400, T.Lux wrote:
> On 15 October 2017 at 05:19 GMT, Sebastien Marie wrote:
>
> > 2) recompile the port with debugging symbol, and extract the backtrace
> > of the failure with gdb ?
> >
> > $ cd /usr/ports/x11/dunst
> > $ make FETCH_PACKAGES=yes CFLAGS=-g
>
debug_dunst.tar.gz
Description: Binary data
On 15 October 2017 at 05:19 GMT, Sebastien Marie wrote:
could you provide more debugging information ?
1) run the program with ktrace -di
$ ktrace -di dunst
Abort trap (core dumped)
$ kdump
(mostly the 100-last lines of kdump)
Attached file
On Sat, Oct 14, 2017 at 09:41:17PM -0400, Thierry wrote:
>
> On 14 October 2017 at 19:14 GMT, Theo Buehler wrote:
> > On Sat, Oct 14, 2017 at 02:29:41PM -0400, Thierry wrote:
> > >
> > > Hi,
> > >
> > > Since revision 1.1 dunst stopped working and produced coredumps
> > > related to "syscsall
On 14 October 2017 at 19:14 GMT, Theo Buehler wrote:
On Sat, Oct 14, 2017 at 02:29:41PM -0400, Thierry wrote:
Hi,
Since revision 1.1 dunst stopped working and produced coredumps
related to "syscsall 197 'protexec'". The latter indicated that
pledge(2) detected an unauthorized system call not
On Sat, Oct 14, 2017 at 02:29:41PM -0400, Thierry wrote:
>
> Hi,
>
> Since revision 1.1 dunst stopped working and produced coredumps
> related to "syscsall 197 'protexec'". The latter indicated that
> pledge(2) detected an unauthorized system call not defined in the
> promises list. Below is a
Hi,
Since revision 1.1 dunst stopped working and produced coredumps
related to "syscsall 197 'protexec'". The latter indicated that
pledge(2) detected an unauthorized system call not defined in the
promises list. Below is a proposed fix which is running fine under
OpenBSD 6.2 GENERIC.MP#0 amd64
10 matches
Mail list logo