I don't see any release criteria for printing capabilities, local or
remote. Should there be? I just stumbled onto this:
I haven't tried to reproduce so I don't know what the scope is,
whether it's a network printer (built-in server of some kind) or a
CUPS managed remote printer. But the apparent combination of firewall
blocking IPP by default (and permitting it fixing this problem) and
Fedora 21 Workstation didn't ship firewall-config by default either,
seems to be a setup for bad UX. Hence, should there be some sort of
print related criterion? What should it be? And for which release?
Hi, just a reminder: we do have the adwaita-qt theme included in the
workstation for f22, and qt4 apps will pick it up automatically. Now
(or when the alpha appears) would be a great time to try out your
favourite qt apps and provide feedback on places where the theme needs
Absolutely loving the new style of the GNOME Shell theme (notably the
"pop-overs", like the calendar/notifications area). However, the new
grey colour of these are now make the topbar look a bit out of place (it
is still the solid black). Previously, the topbar and the popovers were
both black, and it kinda worked, now it looks a little off to me (IMHO).
Is there any plan to change the colour of the topbar at all? I note on
the lock screen, the topbar is slightly transparent, so it looks a
little closer to the grey of the pop-overs.
I have had 'rawhide' running in VirtualBox for some months. Recently an
upgrade renconfigured repos - as I understand in order to make it become
"Fedora 22"). So far, so good.
However, for a week I wasn't able to upgrade (using Yum Extender) with new
packages due to some signing problems with packages. Yesterday I finally
succedded to do so, But after the upgrades were installed and a reboot, the
VM halts when it should display the login screen. It hanged forever. I
noticed in another thread here that "the login screen will now use
Wayland". From yet another discussion I know that Wayland will not work in
VirtualBox, as it (VB) does not have drivers for the virtuaized hardware
in this environment (Wayland).
1st queston: is my understanding of the problem correct?
2nd question: was this considered when deciding to use Wayland for the
3rd question: will there be/is there a workaround of some kind?
If it matters, I am using the XFCE spin. Here I find it even more strange
to use Wayland for login.
I think you are shooting yourself in the foot by not allowing people to try
F22 in VirtualBox etc.
(besides new packets have arrived since yesterday that are not signed, it
Hilsen / Regards
In case anyone in or around the WG is interested in mentoring a
student under the Fedora GSoC umbrella:
----- Forwarded message from Stephen Gallagher <sgallagh(a)redhat.com> -----
Date: Wed, 18 Feb 2015 10:16:17 -0500
From: Stephen Gallagher <sgallagh(a)redhat.com>
Subject: Fedora Proposals for Google Summer of Code 2015 due *TOMORROW*
Sorry for the obscenely short-notice folks. This year's GSoC application
was left unintentionally untended. I've started putting together a
Proposal page at
If you are interested in mentoring a student this summer on your
project, please add your name and a description of the project no later
than tomorrow so I can submit the proposal on Friday.
announce mailing list
----- End forwarded message -----
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com