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
Hi folks! Sending this with fairly wide distribution in the hopes of
finding someone with appropriate configuration.
There's a proposed blocker bug for F33:
https://bugzilla.redhat.com/show_bug.cgi?id=1830343
which reports a hang in the GNOME Shell VPN auth flow when trying to
connect to an OpenC
On 4/19/19 4:48 PM, John Florian wrote:
Might this be related to why my console goes blank without 'nomodeset'
for my custom F29 live spins when I run them in QEMU? The problem just
turned up about 2 weeks ago. I don't see that message in the journal
and thus far have only seen the problem whe
Might this be related to why my console goes blank without 'nomodeset'
for my custom F29 live spins when I run them in QEMU? The problem just
turned up about 2 weeks ago. I don't see that message in the journal
and thus far have only seen the problem when I run the images with QEMU.
On 4/8/19
On Fri, 2019-04-12 at 14:32 -0500, Brandon Nielsen wrote:
> Desktop, UEFI, Z87 chipset, Intel Xeon E3-1230 v3, AMD R9 280X GPU -
> Fails, does not show the specified error instead journalctl shows:
>
> gnome-shell[1820]: Failed to create backend: No GPUs found with udev
This is actually expected
Desktop, UEFI, Z87 chipset, Intel Xeon E3-1230 v3, AMD R9 280X GPU -
Fails, does not show the specified error instead journalctl shows:
gnome-shell[1820]: Failed to create backend: No GPUs found with udev
Which is likely caused by (from dmesg):
[ 11.994228] [drm] VGACON disable radeon kerne
On Wed, Apr 10, 2019 at 8:40 PM Adam Williamson
wrote:
> On Wed, 2019-04-10 at 19:00 -0500, Richard Shaw wrote:
> > Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050
> >
> > I got to GDM just fine but there was some weird jerkiness when I moused
> > over the "Try Fedora / Install"
On Wed, 2019-04-10 at 19:00 -0500, Richard Shaw wrote:
> Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050
>
> I got to GDM just fine but there was some weird jerkiness when I moused
> over the "Try Fedora / Install" buttons but not when moving the mouse
> cursor over the desktop a
Tried on my Gigabyte AM4 X370 w/ AMD Ryzen 2600 and Nvidia GT1050
I got to GDM just fine but there was some weird jerkiness when I moused
over the "Try Fedora / Install" buttons but not when moving the mouse
cursor over the desktop area. I coped dmesg and journalctl to a separate
machine if it's n
I have a no boot, too. Reported in the Bugzilla.
L.
On Wed, Apr 10, 2019 at 6:41 PM Geoffrey Marr wrote:
> Have tried two machines so far, a MacBook
>
> 02:00.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
> Integrated Graphics Controller (primary) (rev 03)
>
> and a Dell Prec
Have tried two machines so far, a MacBook
02:00.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (primary) (rev 03)
and a Dell Precision M4600 with:
01:00.0 VGA compatible controller: NVIDIA Corporation GF106GLM [Quadro
2000M] (rev a1)
The MacBook
On Wed, Apr 10, 2019 at 3:21 PM Kamil Paral wrote:
> Then I tried with Thinkpad T450s. I had to boot in UEFI with CSM on,
> because CSM off or even SecureBoot on make the image unbootable (I'll
> report a separate bug about that).
>
https://bugzilla.redhat.com/show_bug.cgi?id=1698550
___
On Tue, Apr 9, 2019 at 3:03 AM Adam Williamson
wrote:
> Hi folks!
>
> A few weeks back we asked for testing of 'basic graphics mode' /
> nomodeset booting - the feedback from that was very helpful in
> establishing that we had a generic issue which dated back to Fedora 29,
> thanks a lot. We have
Hi folks!
A few weeks back we asked for testing of 'basic graphics mode' /
nomodeset booting - the feedback from that was very helpful in
establishing that we had a generic issue which dated back to Fedora 29,
thanks a lot. We have now established more or less what that initial
issue is, and work
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
Hi folks!
So as you may have read, F26 Beta was held up by a tricky bug which
causes upgrades to hang in some situations:
https://bugzilla.redhat.com/show_bug.cgi?id=1397087
https://bugzilla.redhat.com/show_bug.cgi?id=1394862
There are updates in F24, F25 and F26 at present which we hope should
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
Hi folks!
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
pretty bad. But we're not sure yet how many systems would be affected
by the bug. So we're looking for more feed
On Wednesday 21 October 2015 13:53:35 Adam Williamson wrote:
> At this point the most valuable testing would be to see if anyone can
> reproduce disappearing-cursor on KDE, and confirming the fix for the
> black screen bug with the updated cogl.
Another input, totally different environment, but st
On Wed, 2015-10-21 at 09:13 -0700, Adam Williamson wrote:
> Hi folks!
>
> So we're building 23 Final RC2 now, but we have a couple of
> outstanding
> proposed blocker bugs, and we could use some more data to evaluate
> them.
Update on this, folks: we believe we've found the cause of and a fix
for
On Oct 21, 2015 11:13 AM, "Adam Williamson"
wrote:
>
> Hi folks!
>
> So we're building 23 Final RC2 now, but we have a couple of outstanding
> proposed blocker bugs, and we could use some more data to evaluate
> them.
>
> The way to test is really simple:
>
> * Install F23 Final TC11 Workstation o
Hi folks!
So we're building 23 Final RC2 now, but we have a couple of outstanding
proposed blocker bugs, and we could use some more data to evaluate
them.
The way to test is really simple:
* Install F23 Final TC11 Workstation or KDE live[1]
* Create a user and log in
* Log out a bunch of times.
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
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 fails to start correctly but also does
not fall through (as it should) to GDM-
On Tue Jan 20 2015 at 3:20:41 AM Adam Williamson
wrote:
> It would be great if folks could, as a matter of urgency, test this
> update:
>
> https://admin.fedoraproject.org/updates/PackageKit-1.0.4-1.fc21,libhif-
> 0.1.8-1.fc21
>
> Please install the updated packages, reboot (or at least restart t
Hi, folks!
We recently found out that there were some significant problems with
PackageKit and things that use it (GNOME Software, Apper, gnome-
packagekit...) in Fedora 21, since the release of libhif-0.1.7 as an
update shortly after F21 came out. The initial bug people noticed was
offline upd
On Mon, 2014-11-03 at 11:12 -0800, Adam Williamson wrote:
> Hi, folks. We now have updates for fedup and systemd that approach the
> shutdown-after-15-minutes bug (that's
> https://bugzilla.redhat.com/show_bug.cgi?id=1159292 ) from different
> angles. We would like to get these marked as stable ASA
Hi, folks. We now have updates for fedup and systemd that approach the
shutdown-after-15-minutes bug (that's
https://bugzilla.redhat.com/show_bug.cgi?id=1159292 ) from different
angles. We would like to get these marked as stable ASAP (assuming we
find no problems with them, of course).
These are
On 19/04/13 01:50 PM, Chris Adams wrote:
Once upon a time, Chris Adams said:
The system is a Zotac Zbox nano AD10. I downloaded the image from the
above URL and put it on an SD card and did a UEFI boot. I don't have
anything current on the drive, so I chose not to preserve anything. I
tried
Once upon a time, Chris Adams said:
> The system is a Zotac Zbox nano AD10. I downloaded the image from the
> above URL and put it on an SD card and did a UEFI boot. I don't have
> anything current on the drive, so I chose not to preserve anything. I
> tried a minimal install; no problems up to
Once upon a time, Adam Williamson said:
> Hi folks - thanks for helping out with the last UEFI testing request, it
> was very helpful. If we could impose again, it would be really helpful
> if anyone with a UEFI-capable system could try a UEFI native install of
> Alpha RC3
On 16/04/13 09:27 AM, Alexander Bokovoy wrote:
On Mon, 15 Apr 2013, Adam Williamson wrote:
Hi folks - thanks for helping out with the last UEFI testing request,
it was very helpful. If we could impose again, it would be really
helpful if anyone with a UEFI-capable system could try a UEFI native
On Mon, 15 Apr 2013, Adam Williamson wrote:
Hi folks - thanks for helping out with the last UEFI testing request,
it was very helpful. If we could impose again, it would be really
helpful if anyone with a UEFI-capable system could try a UEFI native
install of Alpha RC3:
https
On Mon, Apr 15, 2013 at 09:32:53PM -0700, Adam Williamson wrote:
> https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/
I'll try Alpha RC3 tomorrow (I'm not near my UEFI hardware today), but I
have run into an interesting problem with the backup GPT label and I
wonder if anyone else has seen i
Hi folks - thanks for helping out with the last UEFI testing request, it
was very helpful. If we could impose again, it would be really helpful
if anyone with a UEFI-capable system could try a UEFI native install of
Alpha RC3:
https://dl.fedoraproject.org/pub/alt/stage/19-Alpha-RC3/
and
Sorry my bad am looking for a review
On Mon, May 14, 2012 at 3:19 AM, Matthias Runge wrote:
> On 14/05/12 03:35, Adrian Alves wrote:
> > Hello Guys,
> > Am looking for someone to test DrPython,
> ..
> > Regards, Adrian.-
>
> It is pretty unusual, to test a package before it's released. If you're
On 14/05/12 03:35, Adrian Alves wrote:
> Hello Guys,
> Am looking for someone to test DrPython,
..
> Regards, Adrian.-
It is pretty unusual, to test a package before it's released. If you're
looking for a reviewer,
I'd like to point you to
https://fedoraproject.org/wiki/Package_Review_Process#Cont
Hello Guys,
Am looking for someone to test DrPython,
https://bugzilla.redhat.com/show_bug.cgi?id=821296
Spec URL: http://alvesadrian.fedorapeople.org/drpython.spec
SRPM URL: http://alvesadrian.fedorapeople.org/drpython-3.11.1-1.fc16.src.rpm
Description: DrPython is a highly customizable, simple, an
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
Hello,
can anyone who have a real machine with Fedora 17 give a try to install
and run the current version of skychart?
I only have a virtual machine and I've just discovered that (for me) the
program freezes on startup... the strange is that I built a rpm of a
newer version for F17, but with
Hey, folks. There's a new livecd-tools build which needs testing:
https://admin.fedoraproject.org/updates/FEDORA-2012-2313/livecd-tools-17.6-1.fc17
It should fix two bugs I came across in Alpha testing:
https://bugzilla.redhat.com/show_bug.cgi?id=796419 - "F17 Alpha RC4 DVD
written to USB with l
Hey, folks. If anyone has a non-Intel BIOS RAID controller in a system
they can blow away for testing, can you please take a look at the
potential fix for:
https://bugzilla.redhat.com/show_bug.cgi?id=742226
you should be able to reproduce the bug just by trying to install F16
Final TC2 to a non-I
68 matches
Mail list logo
