Re: [lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

2022-10-29 Thread Mateusz Konieczny
0:25, Fritz Hudnut wrote: > >>> Message: 2 >>> Date: Wed, 26 Oct 2022 11:34:21 +0200 >>> From: Nio Wiklund >>> To: Mateusz Konieczny , >>> lubuntu-users@lists.ubuntu.com >>> Subject: Re: [lubuntu-users] Discourse forum seems broken >

Re: [lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

2022-10-26 Thread Fritz Hudnut
. . but not in Lubuntu . . . . On Wed, Oct 26, 2022 at 7:25 AM Fritz Hudnut wrote: > > > > > Message: 2 > > Date: Wed, 26 Oct 2022 11:34:21 +0200 > > From: Nio Wiklund > > To: Mateusz Konieczny , > > lubuntu-users@lists.ubuntu.com > > Subject:

Re: [lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

2022-10-26 Thread uninvol...@outlook.com
untu.com Subject: Re: [lubuntu-users] Discourse forum seems broken Message-ID: <5e2cb8c8-639e-8230-bdf2-b57d16578...@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Den 2022-10-26 kl. 11:26, skrev Mateusz Konieczny: If I enter say my https://discourse.lubuntu.me/t/how-can-

[lubuntu-users] Discourse forum seems broken (Mateusz Konieczny) (Nio W)

2022-10-26 Thread Fritz Hudnut
> > Message: 2 > Date: Wed, 26 Oct 2022 11:34:21 +0200 > From: Nio Wiklund > To: Mateusz Konieczny , > lubuntu-users@lists.ubuntu.com > Subject: Re: [lubuntu-users] Discourse forum seems broken > Message-ID: <5e2cb8c8-639e-8230-bdf2-b57d16578...@gmail.com&

Re: [lubuntu-users] Discourse forum seems broken

2022-10-26 Thread Nio Wiklund
Den 2022-10-26 kl. 11:26, skrev Mateusz Konieczny: If I enter say my https://discourse.lubuntu.me/t/how-can-i-change-which-software-is-used-to-open-folders/3716 thread nothing on page is clickable or s

[lubuntu-users] Discourse forum seems broken

2022-10-26 Thread Mateusz Konieczny
If I enter say my https://discourse.lubuntu.me/t/how-can-i-change-which-software-is-used-to-open-folders/3716 thread nothing on page is clickable or scrollable Console log has "Content Security Policy: The page's settings blocked the loading of a resource at inline ("script-src"). Source: // T