In case it's not clear, note that client openconnect supports multiple
VPN types, and they might behave differently (e.g. Global Protect, with
a different sort of authentication flow).
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe
On Fri, 2017-06-09 at 09:18 -0700, Adam Williamson wrote:
> On Fri, 2017-06-09 at 17:57 +0200, Dominik 'Rathann' Mierzejewski
> wrote:
> > On Sunday, 04 June 2017 at 19:09, Björn 'besser82' Esser wrote:
> > > Am 04.06.2017 um 18:44 schrieb Adam Williamson:
> > > > There are updates in F24, F25 and
On Fri, 2017-06-09 at 17:57 +0200, Dominik 'Rathann' Mierzejewski
wrote:
> On Sunday, 04 June 2017 at 19:09, Björn 'besser82' Esser wrote:
> > Am 04.06.2017 um 18:44 schrieb Adam Williamson:
> > > There are updates in F24, F25 and F26 at present which we hope should
> > > resolve this bug without c
On Sunday, 04 June 2017 at 19:09, Björn 'besser82' Esser wrote:
> Am 04.06.2017 um 18:44 schrieb Adam Williamson:
> > There are updates in F24, F25 and F26 at present which we hope should
> > resolve this bug without causing other problems, but the code in
> > question is quite sensitive so we want
Am 04.06.2017 um 18:44 schrieb Adam Williamson:
There are updates in F24, F25 and F26 at present which we hope should
resolve this bug without causing other problems, but the code in
question is quite sensitive so we want to be as sure as possible that
it's good to go.
The updates to -21 libdb
On Sat, Aug 20, 2016 at 10:16 AM, Andrew Lutomirski wrote:
> On Aug 20, 2016 4:50 PM, "Andrew Lutomirski" wrote:
>>
>
>>
>> How about ordinary earlyprintk to serial?
>>
>> Try booting with nokaslr, though. There was a bug, now fixed upstream (I
>> think) that broke AMD early microcode if kaslr w
On Aug 20, 2016 4:50 PM, "Andrew Lutomirski" wrote:
>
>
> How about ordinary earlyprintk to serial?
>
> Try booting with nokaslr, though. There was a bug, now fixed upstream (I
think) that broke AMD early microcode if kaslr was used. You would likely
trigger it only on systems for which an earl
On Aug 20, 2016 4:38 PM, "Chris Murphy" wrote:
>
> On Fri, Aug 19, 2016 at 11:16 PM, Luya Tshimbalanga
> wrote:
> > On 19/08/16 08:11 PM, Adam Williamson wrote:
> >> On Fri, 2016-08-19 at 18:53 -0700, Luya Tshimbalanga wrote:
> >>> On 19/08/16 12:58 AM, Kamil Paral wrote:
> > Possibly as I bo
On Fri, Aug 19, 2016 at 11:16 PM, Luya Tshimbalanga
wrote:
> On 19/08/16 08:11 PM, Adam Williamson wrote:
>> On Fri, 2016-08-19 at 18:53 -0700, Luya Tshimbalanga wrote:
>>> On 19/08/16 12:58 AM, Kamil Paral wrote:
> Possibly as I boot the livemedia from the plain old burned DVD for
> testi
On 19/08/16 08:11 PM, Adam Williamson wrote:
> On Fri, 2016-08-19 at 18:53 -0700, Luya Tshimbalanga wrote:
>> On 19/08/16 12:58 AM, Kamil Paral wrote:
Possibly as I boot the livemedia from the plain old burned DVD for
testing purpose. Perhaps doing the verification
check detect the p
On Fri, 2016-08-19 at 18:53 -0700, Luya Tshimbalanga wrote:
> On 19/08/16 12:58 AM, Kamil Paral wrote:
> >
> > >
> > >
> > > Possibly as I boot the livemedia from the plain old burned DVD for
> > > testing purpose. Perhaps doing the verification
> > > check detect the problem.
> > Just to make
On 19/08/16 12:58 AM, Kamil Paral wrote:
>>
>> Possibly as I boot the livemedia from the plain old burned DVD for
>> testing purpose. Perhaps doing the verification
>> check detect the problem.
> Just to make sure - have you just tried to boot the LiveCD, or have you
> installed it and booted the
> On 18/08/16 02:45 PM, Adam Williamson wrote:
> > On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote:
> >> On 18/08/16 12:07 PM, Adam Williamson wrote:
> >>> Hi folks!
> >>>
> >>> There is a bug nominated as a Fedora 25 Alpha blocker:
> >>>
> >>> https://bugzilla.redhat.com/show_bug.cgi?id
On 18/08/16 02:45 PM, Adam Williamson wrote:
> On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote:
>> On 18/08/16 12:07 PM, Adam Williamson wrote:
>>> Hi folks!
>>>
>>> There is a bug nominated as a Fedora 25 Alpha blocker:
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1367321
>> Inte
Will test tonight and report.
On Thu, Aug 18, 2016 at 5:45 PM Adam Williamson
wrote:
> On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote:
> > On 18/08/16 12:07 PM, Adam Williamson wrote:
> > >
> > > Hi folks!
> > >
> > > There is a bug nominated as a Fedora 25 Alpha blocker:
> > >
> > >
On Thu, 2016-08-18 at 14:19 -0700, Luya Tshimbalanga wrote:
> On 18/08/16 12:07 PM, Adam Williamson wrote:
> >
> > Hi folks!
> >
> > There is a bug nominated as a Fedora 25 Alpha blocker:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1367321
> Interesting. My desktop system has an identic
I am very busy in these weeks, but if you need other testing cases, I
have many AMD machines
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On 18/08/16 12:07 PM, Adam Williamson wrote:
> Hi folks!
>
> There is a bug nominated as a Fedora 25 Alpha blocker:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1367321
Interesting. My desktop system has an identical ASUS motherboard from
the reporter. The only difference is the cpu, a AMD Pheno
On Thu, 2016-08-18 at 17:13 -0300, Fernando Cassia wrote:
> On 8/18/16, Adam Williamson wrote:
>
> >
> > There is a bug nominated as a Fedora 25 Alpha blocker:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1367321
> >
> > on affected systems, it prevents boot entirely, which is obviously
Hello,
On 14/05/2015 20:01:21 GMT, Adam Williamson
> wrote:
>
>> Hi folks!
>>
>> We have a somewhat-worrying proposed blocker for F22:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1218787
>
>
I have some issues with two different laptops, one with an Intel/Nvidia
combo and one with an Intel/
On 14/05/2015 20:01:21 GMT, Adam Williamson wrote:
Hi folks!
We have a somewhat-worrying proposed blocker for F22:
https://bugzilla.redhat.com/show_bug.cgi?id=1218787
I have tested Workstation (x86_64) TC3 and TC4 on my HP laptop with
dual graphics (Intel and AMD):
00:02.0 VGA compatible co
On May 15, 2015 12:22 AM, "William" wrote:
>
>
> > >
> > > This has affected my MacbookPro 8,2 for about a year. I want to see
> > > this as a blocker, so that it is taken seriously as the issue has
> > > gone
> > > otherwise ignored. This affects straight Xorg, not just Wayland.
> >
> > Is this a
get logs that helps us understand
what is happening it is hard to fix.
Christian
- Original Message -
> From: "William"
> To: devel@lists.fedoraproject.org
> Sent: Thursday, May 14, 2015 7:39:10 PM
> Subject: Re: Testing request: gdm-on-Wayland on hybrid graphics
Shameful doublepost because I missed the link: I'm a fool. I'll try the new
spin once I get a chance to grab a stick to flash it.
On Fri, May 15, 2015 at 7:42 AM, Conan Kudo (ニール・ゴンパ)
wrote:
> I personally have a Mid 2014 MacBook Pro Retina with hybrid graphics. I
> did not observe this bug, tho
I personally have a Mid 2014 MacBook Pro Retina with hybrid graphics. I did
not observe this bug, though I did not have Wi-Fi or power control. I did
not dare keep Fedora running on my Mac for very long because it was getting
very hot very quickly. I have not tried with updated packages. I'd love t
> >
> > This has affected my MacbookPro 8,2 for about a year. I want to see
> > this as a blocker, so that it is taken seriously as the issue has
> > gone
> > otherwise ignored. This affects straight Xorg, not just Wayland.
>
> Is this an early or late 2011 MBP 8,2?
Pretty sure it's a late 201
On Thu, 2015-05-14 at 16:17 -0400, Paul Wouters wrote:
> I had gdm issues on my f19 to f22beta upgrade too. Startx worked.
> Worse, the lock screen cannot unlock. Claims wrong passwd. Killing
> Xorg just led to restarted locked screen. Only way out was init 1
Thanks for the report, but I'd like
On Thu, May 14, 2015 at 5:39 PM, William wrote:
> On Thu, 2015-05-14 at 13:01 -0700, Adam Williamson wrote:
>> Hi folks!
>>
>> We have a somewhat-worrying proposed blocker for F22:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1218787
>>
>> it appears that after a successful installation of Wo
On Thu, 2015-05-14 at 13:01 -0700, Adam Williamson wrote:
> Hi folks!
>
> We have a somewhat-worrying proposed blocker for F22:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1218787
>
> it appears that after a successful installation of Workstation on the
> affected system, GDM-on-Wayland fail
I had gdm issues on my f19 to f22beta upgrade too. Startx worked. Worse, the
lock screen cannot unlock. Claims wrong passwd. Killing Xorg just led to
restarted locked screen. Only way out was init 1
Sent from my iPhone
> On May 14, 2015, at 16:01, Adam Williamson wrote:
>
> Hi folks!
>
> We
Well, seems the problem isn't due to graphic drivers or to sqlite, but
to lazarus.
In fact, all applications compiled with lazarus 0.9.30 (the last version
available in repositories) are broken starting from F17 and higher!
Lazarus should be upgraded and patched to work with glib2 >= 2.31 so I
31 matches
Mail list logo
