Re: Alpha 1.6 workstation live might be DOA

2016-03-20 Thread Joachim Frieben
Flickering Wayland guests are a known issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1266484 .

Despite this you can still navigate with the keyboard and thus log in. If you 
chose the GNOME on Xorg session, then you get a usable desktop. You can also 
disable Wayland for GDM altogether in /etc/gdm/custom.conf.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
http://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org

Reopen bugs closed with resolution ERRATA?

2016-09-21 Thread Joachim Frieben
The page BugZappers/BugStatusWorkFlow displays the work flow which applies to a 
Fedora bug. However, no policy is given about reopening a closed bug. At the 
bottom of the page, the reader is referred to "A Bug's Life Cycle" for further 
information. Here, we read

"CLOSED 
This bug fix has been resolved by the Assigned Engineer. The CLOSED state 
includes the resolution field which describes why a bug report is closed. See 
Resolution descriptions. If the CLOSED resolution ERRATA is set, the bug report 
cannot be reopened. Instead, enter a new bug report for a new problem."

The expression "cannot be reopened" is ambiguous. Now, some of my bugs closed 
with resolution ERRATA have been reopened by other users. Is this procedure 
allowed or should indeed a new bug be created instead which is what I was doing 
in the past?
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Reopen bugs closed with resolution ERRATA?

2016-09-21 Thread Joachim Frieben
Unfortunately, I still ignore the current policy for reopening a closed bug, in 
particular those resolved as ERRATA. The documentation page "BugStatusWorkFlow" 
should get really amended in this respect.
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org


Re: Just checking…

2016-06-11 Thread Joachim Frieben
In current rawhide, there is an SELinux issue which prevents GDM/GNOME to start 
up:

https://bugzilla.redhat.com/show_bug.cgi?id=1339761 .

Boot your system in permissive mode and see what happens. I have an AMD 
graphics card, too, but this workaround helped indeed.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://lists.fedoraproject.org/admin/lists/test@lists.fedoraproject.org