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-
12 matches
Mail list logo
