Plan to organize the Wayland-by-default effort
by Kevin E Martin
We are working toward enabling the GNOME desktop on Wayland as the
default for the Fedora Workstation project. The question is: What
features do we have to complete in order to make this switch? Everyone
seems to have their own ideas of what is required, and a systematic
approach is needed to organize the effort.
Over the years, many features have been developed for the traditional
X11-based GNOME desktop, and we are bringing these features over to the
Wayland-based version. Quite a few of these features have already been
implemented for the Wayland-based desktop and we already have highly
functional desktop experience that everyone can use, but it is not yet
complete. In order for us to enable it by default we need to both
implement the missing features and fix the bugs in features that are
already complete.
For the bugs, we simply need to fix them. However, the situation with
features is more complex. We each have our own list of features that we
believe need to be implemented, but we lack a complete list of all the
missing features and a clear way to determine when we have implemented
enough of them to enable the Wayland-based GNOME desktop by default.
Toward that goal, we are consolidating all of the various feature lists
in the following Fedora wiki page:
https://fedoraproject.org/wiki/Wayland_features
We are putting this on the Fedora wiki (instead of a GNOME, Wayland,
kernel, Freedesktop or other wiki) since this is a Fedora decision on
when we feel the Wayland-based GNOME desktop is ready to be the default
for our Fedora Workstation project.
The initial step is to list all features for the Wayland-based GNOME
desktop. Olivier Fourdan, who has been heavily involved in the upstream
Wayland development and also involved in GNOME development activities,
has agreed to maintain this page. If you have ideas for what features
should be included, please add them to the wiki page and discuss them on
this list.
What we need for each missing or incomplete feature is a descriptive
name and what stage of development it is in. Links to other pages where
more detailed description of the feature status and implementation
details are also welcomed. For the development stages, there are
kernel, supporting libraries, Wayland protocol, XWayland, mutter, gtk+
and application levels. For example, tablet support is currently
implemented in the kernel and supporting libraries. The protocol has
been proposed and is under discussion. Once the protocol has been
accepted, there will be additional development needed at higher levels.
This feature will remain on the list until it is complete at all levels.
The next step is determining which of these features must be implemented
before we can enable Wayland by default in Fedora Workstation. The plan
is to form a small group of people deeply involved in the Wayland, GNOME
and/or Fedora development to prioritize the list of features and then
draw a line in this prioritized list above which all features must be
complete before we will enable the GNOME desktop on Wayland by default
in our Fedora Workstation project. We can then evaluate this list
during the Fedora 24 development cycle to determine if we are ready to
enable Wayland by default in the alpha, beta and final releases.
7 years, 9 months
eclipse in gnome-software
by Matthias Clasen
I had occasion to look up how eclipse is presented in gnome-software
today. Arguably one of the flagship applications for a developer
workstation, sadly, the presentation can be improved.
Things I noticed:
- It shows up as '3rd party' in the list. We really need to fix this so
that the only stuff that gets a 3rd party label is actually 3rd party.
In its current form, it is too unreliable to be used.
- The details page lists a number of interesting plugins in the
description, and there is a list of add-ons that gnome-software offers
to install. Sadly, the overlap between these two lists is very small.
Why is that ? Just one example, CDT: Installing eclipse-cdt on the the
commandline works just fine, but it does not show up in the list of
available add-ons. Why is that, and can we fix it ?
7 years, 10 months
Workstation WG call for agenda 2015-Jan-20
by Paul W. Frields
The Workstation WG meeting is scheduled for this Wednesday,
2015-Jan-20 at 1500 UTC (10:00 EST, 16:00 CEST). This agenda is open
for additions/corrections; please send by tomorrow at 1200 UTC.
(Holding open longer because I was late sending this out.)
* i686 Workstation images -- Does the WG want to keep producing these?
(See list for full discussion.)
* Are there any remaining Changes to file for F24?
* F24 Test Days -- Do we want any dedicated for F24?
--
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
7 years, 10 months
Workstation WG meeting recap 2015-Jan-20
by Paul W. Frields
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2016-01-20/workstation.20...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2016-01-20/workstation.20...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2016-01-20/workstation.20...
* * *
===============================
#fedora-meeting: Workstation WG
===============================
Meeting started by stickster at 15:01:32 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2016-01-20/workstation.20...
.
Meeting summary
---------------
* Roll call (stickster, 15:01:38)
* i686 Workstation images (stickster, 15:07:50)
* i686 Workstation images (stickster, 15:08:46)
* Quorum in attendance was not really happy with idea to drop i686
images outright; there may be technical issues as well; lack of
clear support means we will stick with status quo for now.
(stickster, 15:55:05)
* ACTION: stickster let sgallagh know about uncertain status of F24
Change for Server i686 droppage (stickster, 15:57:08)
* Changes for F24 (stickster, 15:58:12)
* ACTION: kalev create F24 Change page for GNOME 3.20 (stickster,
16:01:05)
* ACTION: stickster revive Test Day discussion on list (stickster,
16:01:34)
Meeting ended at 16:01:48 UTC.
Action Items
------------
* stickster let sgallagh know about uncertain status of F24 Change for
Server i686 droppage
* kalev create F24 Change page for GNOME 3.20
* stickster revive Test Day discussion on list
Action Items, by person
-----------------------
* kalev
* kalev create F24 Change page for GNOME 3.20
* sgallagh
* stickster let sgallagh know about uncertain status of F24 Change for
Server i686 droppage
* stickster
* stickster let sgallagh know about uncertain status of F24 Change for
Server i686 droppage
* stickster revive Test Day discussion on list
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (63)
* mclasen___ (28)
* kalev (23)
* mcatanzaro (15)
* dgilmore (11)
* jwb (10)
* zodbot (7)
* otaylor (6)
* kparal (2)
* bowlofeggs (2)
* sgallagh (1)
* Southern_Gentlem (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
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
7 years, 10 months
Re: Fedora 23 KDE spin / XEN / virt-manager and
vmlinuz-4.3.3-301.fc23.x86_64
by Cole Robinson
On 01/19/2016 10:42 AM, Outback Dingo wrote:
>
>
> On Tue, Jan 19, 2016 at 4:32 PM, Cole Robinson <crobinso(a)redhat.com
> <mailto:crobinso@redhat.com>> wrote:
>
> On 01/18/2016 03:05 PM, Outback Dingo wrote:
> > So my environment
> >
> > Fedora 23 KDE spin
> > XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using
> > virt-manager to manage vms under XEN, all is good.
> >
> > a recent update installed kernel-4.3.3 so i reset the xen efi configuration,
> > booted got into the desktop no problems. The issue arises when trying to
> > launch vms from virt-manager, it always throws a virt-manager viewer
> > connection to hypervisor host got refused or disconnected.
> >
> > however, if i go back to using kernel 4.2.8 it all works fine. So there in
> > lies the question, whats changed that is now preventing virt-manager from
> > aunching vms properly.
> >
> > Sorry for the cross post, just trying to find the answer. thanks in advance
> >
> >
>
> I suggest filing a bug against xen. See if there's any different output in
> dmesg, attach /var/log/libvirt/libxl/$your-vm-name.log, attach virt-manager
> --debug output when reproducing
>
>
> Id be more inclined to think this is a kernel build issue and not a XEN issue,
> however... filing a bug with debug data attached could be helpful.
Xen has many of its own specific bits in the kernel. Filing against the xen
component is the best way to get xen guys to take a look, they will move it to
the kernel if necessary.
- Cole
7 years, 10 months
Re: Fedora 23 KDE spin / XEN / virt-manager and
vmlinuz-4.3.3-301.fc23.x86_64
by Cole Robinson
On 01/18/2016 03:05 PM, Outback Dingo wrote:
> So my environment
>
> Fedora 23 KDE spin
> XEN-4.5.2 and kernel 4.2.8 booted via EFI where everything works fine using
> virt-manager to manage vms under XEN, all is good.
>
> a recent update installed kernel-4.3.3 so i reset the xen efi configuration,
> booted got into the desktop no problems. The issue arises when trying to
> launch vms from virt-manager, it always throws a virt-manager viewer
> connection to hypervisor host got refused or disconnected.
>
> however, if i go back to using kernel 4.2.8 it all works fine. So there in
> lies the question, whats changed that is now preventing virt-manager from
> aunching vms properly.
>
> Sorry for the cross post, just trying to find the answer. thanks in advance
>
>
I suggest filing a bug against xen. See if there's any different output in
dmesg, attach /var/log/libvirt/libxl/$your-vm-name.log, attach virt-manager
--debug output when reproducing
- Cole
7 years, 10 months
help with bluetooth adaptor wanted
by kendell clark
hi all
I'm sorry if This is the wrong place to post this, but I wasn't sure
which of the fedora lists was appropriate. I just bought myself a
bluetooth usb adaptor, since i got some really nice bluetooth headphones
for christmas. I plugged it into my fedora box and all seemed to go
well. The bluetooth icon showed up, I connected to the headset and ...
no sound.
I've done the following troubleshooting steps. I checked dmesg, and the
error I got was, hci0: autoload firmware brcm/bcm20702a1.hcd failed with
error -2. So this bluetooth adaptor, which said nothing about this on
the box, has a broadcom chip in it. If the firmware couldn't be loaded,
how could the device function? Does the linux btbcm module not require
it? I've also checked pulseaudio's config to see if maybe the bluetooth
modules weren't loaded, but in /etc/pulse/daemon.conf I see ifexists
module-bluetooth-discover.so
load-module module-bluetooth-discover.so. Same for bluetooth-policy, and
bluetooth-device.
I've read up on this, and saw that I also need to load
module-bluez5-device.so, but attempting this with pacmd gets me module
load failed. So I'm stumped. Linux seems to support this device, or the
bluetooth icon in gnome wouldn't have appeared. It can connect to the
headset, there's just no sound.
i've verified that the a2dp profile is set in gnome's sound settings.
I'm using fedora 23, completely up to date as of five minutes ago, with
a reboot to see if that helps. One quirk of this dongle is that it
doesn't seem to work until I unplug and replug. Until I do, the text in
gnome's bluetooth settings reads as, available as "bastian's computer
and available for bluetooth file transfers. Transferred files are placed
in the downloads folder". Once I plug the device in, it changes to
"available as tigger and available for bluetooth file transfers.
Transferred files are placed in the downloads folder" Is this a quirk of
gnome or the device?
I've done some research, and saw some posts on the linux kernel mailing
list where another person was having the same problem with a different
device with the same broadcom chip, a bcm20702a1, although it was a
different vid and pid. Support for all broadcom bluetooth usb chips was
supposed to be in kernel since kernel 3.2. I've already posted this to
the manjaro mailing lists, and was instructed by phil to download a
firmware file from amazon s3, place it in /lib/firmware/brcm, but it
didn't help. I'm completely stumped.
Anyone have any advice, help, etc?
Thanks for reading
Kendell clark
7 years, 10 months
Case against Firefox in FESCo
by Jiri Eischmann
Hi,
there is currently a case against Firefox discussed in FESCo:
https://fedorahosted.org/fesco/ticket/1518
The problem in short: The last release of Firefox doesn't allow the
user to install add-ons which are not signed by Mozilla by default, in
the next version, you won't even be able to disable this behavior. This
means that a couple of add-ons that are packaged by Fedora won't work.
In my opinion, this problem has an impact on a relatively small number
of users while suggested solutions will have an impact on majority of
Workstation users. The author of the original ticket recommends Firefox
is removed altogether if Mozilla doesn't change their plan, another
suggestion is to switch to ESR which would mean that Fedora would have
as conservative approach to Firefox updates as RHEL.
Firefox is probably the most important desktop app in Fedora, so I
wonder whether the Workstation working group should voice its opinion
in this before any decision is made.
Jiri
7 years, 10 months
