May 2015 - desktop - Fedora mailing-lists

Anaconda wishlist
by Michael Catanzaro 04 Jun '15

04 Jun '15

Hi, I put together a desired installation experience wishlist. Let's discuss and consider forwarding this to the Anaconda developers as a request. * Remove the timezone selection spoke. This spoke is redundant with gnome-initial-setup. * Remove or simplify the network configuration spoke. In the live installer, this spoke allows setting only the system hostname, but it follows different rules for setting the hostname than GNOME/systemd. The spoke should either follow hostnamed's rules for pretty hostnames (i.e. allows capital letters, spaces, etc. without any complaint), or the spoke should be removed. If we keep it, it should allow the user to set a "computer name" (avoiding technical terminology like "hostname") and should not include the phrase "network configuration." * Remove root password configuration. It's confusing how this is different from the user's admin account password. Advanced users can set a root password after installation if desired. * Remove user account creation. This is redundant with gnome-initial -setup. * Remove hub and spokes: simply go straight to keyboard layout selection after language selection, then from there to disk layout, optionally from there to the hostname panel, and then to the installation progress panel. This last panel will need a bit of a redesign, since it will be pretty empty otherwise. Clearly this is mostly a list of things to remove, rather than things to add. The goal is to make installation as simple and easy as possible. Changes to gnome-initial-setup: Skip language and keyboard layout selection in user creation mode. These panels cannot reasonably be removed from Anaconda, so we should use them only in existing user mode (when a new user account is created after installation). They're redundant in user creation mode. This proposal leaves the disk layout spoke untouched, which is the most confusing portion of the installation experience, but it's more than enough changes for one release already. Thoughts?

10 23

Significant drop in ABRT reports in F22
by Jiri Eischmann 02 Jun '15

02 Jun '15

Hi, I regularly go through most frequent problems reported to ABRT retrace server because it helps me prioritize bugs in Fedora that are assigned to my team. I've noticed a significant drop in number of reports in Fedora 22. It's just two weeks before the final release when many early adopters are already running F22, but the difference in number of reports from F21 and F22 is huge: 64373:904. 12 days before F21 was released, we collected 16081 reports from this version. That's almost 18x more. I don't think we're experiencing such a huge drop in adoption, so I investigated more. I found out several things which I think are a cause of this: 1) I upgraded my machine, and the new Problem Reporting in Privacy Settings is set not to do automatic reporting, completely ignoring my settings in ABRT from F21. 2) I checked settings in ABRT and automatic settings was enabled, so I thought something was broken because my crashes were not reported automatically. Then (with the help of Jakub Filak) I found out that this had been overridden by the new settings in Privacy. 3) Users are no longer asked if they want to enable automatic reporting when the first crash happens. So unless despite complete lack of any hints they find their way into Privacy settings their crashes are not reported. I can no longer even make ureports manually by clicking on Report in notifications. To report it, I need to do the full BZ report. With such a decrease in number of reports, ABRT is much less useful to developers and I think we should fix it: * privacy settings should reflect my settings from ABRT after upgrade. * settings in ABRT and Control Center should be in sync, I understand that the Privacy is master settings overriding app's settings, but there is only one app reporting and it's very confusing for users. * users should be asked if they want to enable automatic reporting after the first crash like in the last. Jiri

11 13

root login via gdm
by Pete Travis 29 May '15

29 May '15

At one time, one could not log in to a GNOME session on Fedora as the root account. Now, you can, out of the box. For me, this seems like less of a "getting in the user's way" thing, and more of a common sense default security policy - especially given all the work done to make things work smoothly with polkit. Am I missing something? If not, what about going back to blocking root login to desktop environments? -- -- Pete

2 1

Re: VSYNC problems on Fedora 21/22 and Intel HD graphics...
by drago01 29 May '15

29 May '15

On Wed, May 27, 2015 at 10:01 PM, Chris Wilson <chris(a)chris-wilson.co.uk> wrote: > On Wed, May 27, 2015 at 03:37:29PM -0400, Alex G.S. wrote: >> Hello, >> First of all I love the new GNOME 3.16 release. The notifications and >> system tray icons (in the left) are great and productivity boosters. >> However, I'm having some issues with Intel HD graphics on X11 that make >> things very difficult. Though these problems are solved by the Wayland >> session it's still too unstable for me to use in production as a >> day-to-day desktop. >> Hardware: >> Intel® Core™ i5-4200M CPU @ 2.50GHz × 4 >> Intel® Haswell Mobile (HD 4600, i965) >> GNOME: >> Version 3.16.2 >> Kernel: >> 4.0.4-301.fc22.x86_64 >> Problem: >> [1]https://bugzilla.gnome.org/show_bug.cgi?id=741376 >> At work I use two external monitors in addition to the laptop screen. >> VSYNC often breaks when using either SNA or UXA at random intervals. It >> also breaks also when I fullscreen any application in any monitor. Even >> when I force VSYNC in both xorg.conf and drirc it doesn't seem to help. >> These are configurations for reference: >> /etc/environment: >> CLUTTER_VBLANK=True >> /etc/X11/xorg.conf.d/20-intel.conf >> Section "Device" >> Identifier "Intel Graphics" >> Driver "intel" >> Option "AccelMethod" "sna" >> Option "TearFree" "true" >> Option "SwapbuffersWait" "true" > > Try Option "DRI" "2" in conjunction to the above. We no longer default to DRI3 in F22.

4 6

Fedora runtimes and sandboxed desktop applications
by Alexander Larsson 29 May '15

29 May '15

I'm working on an application sandboxing system called xdg-app, and the surrounding echo-system. I won't go into details, but there are some links to technical details at the end of the mail[1]. The basic idea is that we have two sources (both ostree trees), one called the runtime (/usr), and one called the app (/app), which get combined in a container-like environment at launch time by xdg-app, with configurable degrees of sandboxing. There is also some interaction with the host system so that installed desktop files show up in the shell and dbus session services from apps work. xdg-app has two major goals, the first is to allow applications to run in a sandboxed environment with minimal access to the host. The second is to allow third parties to create and distribute applications that run on all distributions (and the sandboxing helps making this less risky). To facilitate and test this I've also created an upstream gnome runtime[2] that gnome applications can chose to use. I'm also working on various Portal APIs[3] that allow sandboxed applications to safely interact with the system. But, third party applications are a long way off in the future, and so are sandboxed applications (which need not only a fleshed out set of sandbox APIs, but also modifications to individual apps). In the meantime it is still interesting to run bundled applications. For instance in the context of an Atomic-based Fedora Workstation (with readonly /usr), or if you want to run older or newer versions of applications than your distribution is shipping. It would make a lot of sense to use the existing packages in Fedora for this. And in order to kickstart discussions about this I've created an initial sample of a possible Fedora runtime using rpm-ostree and the Fedora 22 repositories: https://github.com/alexlarsson/fedora-runtime Building this produces a repo with the main runtime (org.fedoraproject.Platform) and a sdk runtime (org.fedoraproject.Sdk) which has some additional tools for app creation and debugging. It also builds .Var subruntimes that contain /var with the rpm db for use when building apps. The current package set is mostly based on what is in the gnome one, so don't consider this official in any way. These runtimes are made to work with xdg-app 0.3.0 which are now in updates-testing for F21 and F22. You also need rpm-ostree from git master for the container support to build the fedra runtime. In order to test the runtime I've also created a firefox application bundle. Unfortunately it requires some hacks in order to be relocated to /app, and to work as a bundle. However, it works pretty well, running somewhat contained with only access to the Downloads xdg directory and with ~/.mozilla being redirected to the per-app persistant data directory (~/.var/app/org.fedoraproject.firefox). Note however, that I would not consider this properly sandboxed, as it uses X11 for rendering, which is not very secure. The scripts to build the firefox bundle is here: https://github.com/alexlarsson/fedora-apps I've also put up a xdg-app repository so that you can easily test this: (Run these commands as non-root, due to the --user args) xdg-app add-remote --user --no-gpg-verify fedora http://people.redhat.com/~alexl/repo xdg-app install-runtime --user fedora org.fedoraproject.Platform 22 xdg-app install-app --user fedora org.fedoraproject.firefox xdg-app run org.fedoraproject.firefox Once installed the desktop file will be exported to the session, so you should also be able to launch it from the shell. In theory this should work on any distro, but I've only tried it on F21. The question is, would the Fedora project be interested in supplying and maintaining a Fedora runtime like this, which allows us (and others) to create applications using the fedora base. And if we do, exactly what should be considered part of the basic platform. Defining a platform requires a lot of care. It is a balance between wanting as much as possible in it to share more maintainance and updates and make it easier to write apps and on the other hand trying to keep the basic platfrom small, maintained and of high quality. The ABI requirements for a platform is a bit different than a regular distro. The goal is to allow apps built against a particular platform to run for years to come, so it should only do security and very important bugfix updates, and *never* break ABI. On the other hand, its easy to break ABI in a later version of the runtime, because they are parallel installed. This is somewhat different than our current updates which revs libraries during the distro lifetime as long as it also updates all users of it. An added complexity is that anything in the runtime that relies on some kind of IPC to the host (say the pulseaudio client libraries, or something that uses a dbus interface on the host) requires the host side of that IPC to remain available and backwards compatible in future versions of the distro, so we should err on exposing a minimal set of IPC. There is also some changes that may be required in the distro to keep unnecessary dependencies out of the runtime. For instance anything related to hardware or system initialization is completely unnecessary. Luckily much of this is being fixed by similar needs from docker already. One thing that is different from docker however, is that we generally want translations/locales in the runtime. But these are pretty large, so we want to handle them in a smart way. xdg-app has a feature that allows splitting a runtime into a base and a set of optional extensions that are mounted in the sandbox only when they are installed. I use this in the gnome runtime to split out each locale. Unfortunately Fedora uses a single large locale-archive file for its locales, so its hard to do that. This needs some research to figure out how to do properly. There are also some custom configuration that a runtime needs. For instance, the build script for the fedora runtime above drops in a new fontconfig file that adds a /app/share/fonts fontdir for app-bundled fonts and configuration to include the host fonts (which xdg-app exposes in /run/host/fonts). This would be nicer if this was just a fontconfig subpackage we could pull in, and I'm sure there are more similar configuration options that would be needed. Creating applications from fedora packages is a bit more complicated. The primary reason is that they need to be relocated to /app. In the hacky script above I just extract the rpm contents to /app and then rewrite some rpaths and shell scripts. A less hacky approach is to rebuild the rpms with a different rpm %_prefix macro, or to use relocatable rpms. It is not really significantly different from creating rpms to use in software collections though, so we have some experience with this. Packaging an application also requires some changes other than the relocatability itself. First of all, all "exported" files from an application (such as icons, desktop files, dbus service files, or other files that are read from outside the app itself) must have the application id (which is a dbus/java-style reverse dns name) as a filename prefix. This is both for avoiding conflicts, and for security reasons, see [4]. However, it wouldn't necessarily be a problem if we just did such changes on the regular fedora packages too, as a regular fedora packaging policy. One issue is that as third party packagers of applications we should not use the "official" app ids for our builds, as they would conflict with upstream doing their own release. So, our package of org.gnome.gedit should probably be called org.fedoraproject.gedit, which may require some minor tweaks to the build (for instance, this affects the dbus name the app uses for dbus activated desktop files, as well as the name of the desktop file itself). There are clearly a lot of details here, but I'll stop here and throw this out as the start of a discussion. I'll gladly reply to any questions people may have. [1] More information: My devconf talk: https://www.youtube.com/watch?v=t-2a_XYJPEY gnome wiki: https://wiki.gnome.org/Projects/SandboxedApps xdg-app code: https://github.com/alexlarsson/xdg-app [2] Announcement of gnome runtime: https://blogs.gnome.org/alexl/2015/03/31/official-gnome-sdk-runtime-builds-… [3] https://wiki.gnome.org/Projects/SandboxedApps/DocumentPortal https://wiki.gnome.org/Projects/SandboxedApps/Sandbox [4] https://mail.gnome.org/archives/gnome-os-list/2015-February/msg00009.html -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl(a)redhat.com alexander.larsson(a)gmail.com He's a war-weary Republican vampire hunter on a search for his missing sister. She's a ditzy winged queen of the dead with the power to see death. They fight crime!

7 11

New Member of List
by William Best 28 May '15

28 May '15

Hello, My name is William Best. I am not sure if this is the right group to join for how I would like to contribute. My passion/career involves helping people with developmental disabilities get better access to technology. Over the past year or so, I have been experimenting with different Linux distributions to come up with a low-cost, stable, and robust solution for the disabled people I work with. I really like Fedora the best out of the bunch for a variety of reasons. My goal is to help get features/apps that would help disabled people access technology in a better way. Let me know if I am in the right group for this. Thanks! ~William Best

2 1

wired networking should work by default, even if not connected at install time
by Chris Murphy 28 May '15

28 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=963952 The gist of this bug is, if the user installs Fedora and doesn't have (wired) ethernet connected at the time of installation, onboot=no and therefore on any subsequent boot, the network does not come up. A separate GNOME bug is that even if the user manually turns on that wired connection, it isn't a sticky setting. So networking is off again the next reboot. The trick is to find the totally obscure and buried option for the wired device to connect automatically. This bug doesn't piss me off the way it did back in 2013 when I filed it, because I know the work around. But this is still a Top 10 Most Asinine Bug. Amusingly, wireless connections don't have this behavior, even though they're in the realm of 8000% more risky even when making a manual+conscious connection. Whereas when I take a physical plug and stick it into the jack, it's a considerable WTF moment when that connection doesn't work until I intervene further, and doesn't work yet again on a reboot until I intervene yet again. I can kinda sorta almost understand server folks differing on this (even though I find it specious for various reasons) but Workstation really shouldn't behave this way. It is not an easy work around, at all, when the user doesn't don't know about it. And in no sane world should they need to know about it. And even when they do know about it, it's always a *sigh* "oh yes, that" moment. So from every perspective I see it as a negative and no benefit. Thanks, -- Chris Murphy

2 1

Re: VSYNC problems on Fedora 21/22 and Intel HD graphics...
by Alex G.S. 27 May '15

27 May '15

> > Let's actually look at what debug information is available then rather > than just flailing in the dark here. The journal since booting should > help see where the lookups are coming from, at least let me know how the > system is configured. What's the best way to capture a log and where should I upload it to? On Wed, May 27, 2015 at 4:43 PM, Chris Wilson <chris(a)chris-wilson.co.uk> wrote: > On Wed, May 27, 2015 at 04:28:33PM -0400, Alex G.S. wrote: > > > Try Option "DRI" "2" in conjunction to the above. > > It worked momentarily but GNOME Shell locked up and crashed when I > had an > > application (Remmina) fullscreen in of the monitors. This happens > very > > frequently in my experience. GNOME just seems unstable on Intel HD > 4600. > > I even tried adding the following to my boot parameters but it didn't > > change anything: > > i915.semaphores=1 > > Let's actually look at what debug information is available then rather > than just flailing in the dark here. The journal since booting should > help see where the lookups are coming from, at least let me know how the > system is configured. > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre >

1 0

VSYNC problems on Fedora 21/22 and Intel HD graphics...
by Alex G.S. 27 May '15

27 May '15

Hello, First of all I love the new GNOME 3.16 release. The notifications and system tray icons (in the left) are great and productivity boosters. However, I'm having some issues with Intel HD graphics on X11 that make things very difficult. Though these problems are solved by the Wayland session it's still too unstable for me to use in production as a day-to-day desktop. Hardware: Intel® Core™ i5-4200M CPU @ 2.50GHz × 4 Intel® Haswell Mobile (HD 4600, i965) GNOME: Version 3.16.2 Kernel: 4.0.4-301.fc22.x86_64 Problem: https://bugzilla.gnome.org/show_bug.cgi?id=741376 At work I use two external monitors in addition to the laptop screen. VSYNC often breaks when using either SNA or UXA at random intervals. It also breaks also when I fullscreen any application in any monitor. Even when I force VSYNC in both xorg.conf and drirc it doesn't seem to help. These are configurations for reference: /etc/environment: CLUTTER_VBLANK=True /etc/X11/xorg.conf.d/20-intel.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" Option "SwapbuffersWait" "true" EndSection /etc/drirc <device screen="0" driver="i965"> <application name="Default"> <option name="force_s3tc_enable" value="true" /> <option name="no_rast" value="false" /> <option name="always_flush_batch" value="false" /> <option name="always_flush_cache" value="false" /> <option name="shader_precompile" value="true" /> <option name="hiz" value="true" /> <option name="clamp_max_samples" value="-1" /> <option name="bo_reuse" value="1" /> <option name="allow_glsl_extension_directive_midshader" value="false" /> <option name="force_glsl_extensions_warn" value="false" /> <option name="disable_throttling" value="false" /> <option name="disable_glsl_line_continuations" value="false" /> <option name="disable_blend_func_extended" value="false" /> <option name="vblank_mode" value="3" /> </application> I even have a GNOME extension I created that autoloads the following GNOME JS function: Meta.disable_unredirect_for_screen(global.screen) This still doesn't help at all. There is a bug report for this item and has been confirmed but I haven't heard anything and status is still NEW and not yet confirmed. Please, any help on this would be appreciated. Things like this should just work out of the box especially on Intel HD graphics. This is a bewildering problem as this is my work machine and I may end up switching to a Mac or Ubuntu Unity if this cannot be fixed. Thank you! Best, Alex

1 0

Workstation WG Recap 2015-May-27
by Paul W. Frields 27 May '15

27 May '15

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2015-05-27/workstation.2015… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2015-05-27/workstation.2015… Log: http://meetbot.fedoraproject.org/fedora-meeting/2015-05-27/workstation.2015… * * * ================================================== #fedora-meeting: Workstation WG (special timeslot) ================================================== Meeting started by stickster at 15:00:01 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-05-27/workstation.2015… . Meeting summary --------------- * Roll call (stickster, 15:00:08) * Special time slot (stickster, 15:03:18) * This slot will not be repeated; next meeting is Monday 2015-Jun-08 at 1300 UTC (stickster, 15:03:38) * F23/24 plans (stickster, 15:04:02) * LINK: https://fedorahosted.org/council/ticket/27 (stickster, 15:04:43) * IDEA: Can we work toward a better upgrade story in F23/24 (stickster, 15:26:58) * ACTION: mcatanzaro to propose update to PRD to clarify that developer focus does not compromise the goal to be a "polished and user friendly system that can appeal to a wide general audience" (mcatanzaro, 15:31:10) * LINK: https://lists.fedoraproject.org/pipermail/desktop/2015-May/012065.html (mcatanzaro, 15:33:13) * LINK: https://fedoraproject.org/wiki/Workstation/Tasklist (stickster, 15:55:27) * LINK: https://fedoraproject.org/wiki/Workstation/Tasklist (stickster, 15:55:47) * many people who could work on F23 improvements are bound up on immediate RHEL work (stickster, 15:56:34) * ACTION: mclasen will also review foregoing task list to see what's already up that could be completed for F23 (stickster, 15:56:42) * LINK: https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/so… (mclasen, 15:58:45) * ACTION: stickster pull together tasks from mclasen + update + anaconda requests into Council report for F23/24 (stickster, 15:59:29) * ACTION: stickster Set up whenisgood for WG + anaconda folks to discuss requests (stickster, 16:09:46) * stickster will carry over agenda items from mcatanzaro list so we can pick up at next meeting (stickster, 16:11:59) * Next meeting: 2015-Jun-08 UTC 1300 (stickster, 16:12:11) Meeting ended at 16:12:17 UTC. Action Items ------------ * mcatanzaro to propose update to PRD to clarify that developer focus does not compromise the goal to be a "polished and user friendly system that can appeal to a wide general audience" * mclasen will also review foregoing task list to see what's already up that could be completed for F23 * stickster pull together tasks from mclasen + update + anaconda requests into Council report for F23/24 * stickster Set up whenisgood for WG + anaconda folks to discuss requests Action Items, by person ----------------------- * mcatanzaro * mcatanzaro to propose update to PRD to clarify that developer focus does not compromise the goal to be a "polished and user friendly system that can appeal to a wide general audience" * mclasen * mclasen will also review foregoing task list to see what's already up that could be completed for F23 * stickster pull together tasks from mclasen + update + anaconda requests into Council report for F23/24 * stickster * stickster pull together tasks from mclasen + update + anaconda requests into Council report for F23/24 * stickster Set up whenisgood for WG + anaconda folks to discuss requests * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * stickster (99) * mclasen (33) * mcatanzaro (31) * cschalle (15) * otaylor (14) * dcantrell (13) * kalev (9) * zodbot (8) * jwb (8) * nirik (2) * rdieter (1) * pingou (1) * Kellin (1) * juhp (0) 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

1 0

Next meeting reschedule?
by Paul W. Frields 27 May '15

27 May '15

Our next meeting is scheduled for Monday, May 25. This is a USA holiday, and most folks here tend to celebrate it AFK. My bet is many people wouldn't be available for our meeting. (That includes Yrs. Truly.) WG members, should we reschedule this, or just cancel it? If we want to reschedule, I'd suggest a one-time-only return to the old time, Wed 2015-May-27 at either 1500 UTC (11am US/Eastern). The meeting would return to the regular timeslot on 2015-Jun-08. -- 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

3 7

Fixing express install for F23
by Paul W. Frields 19 May '15

19 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1178787 The removal of the separate Workstation DVD and netinst had some fallout with Boxes. It looks like this bug lay dormant after February, which is too bad because there was still time to fix things for F22 at that point. But we should see what to do about this situation for F23. My recollection is the WG opted for getting rid of the separate Workstation installation DVD and netinst in favor of the Live image only. But this causes issuses with Boxes/libosinfo express install of Fedora. One way to fix that would be to bring them back -- essentially go back to producing the images we offered before. That doesn't mean we need to advertise them on the website, though. What are the other alternatives for fixing? -- 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 13

Fedora 22 update security
by Thiyagarajan, Nethaji 19 May '15

19 May '15

Hello, I find that the update utility in Fedora is not like in their previous versions I have used (at least until Fedora 20). The system notifies that there are updates and when the user clicks ok to install the updates, it usually asks for the root or system administrator's password to authorize the update. However, it is strange to see in Fedora 22 that no such security is available. Any normal user could easily install the updates that include kernel, X11 and all system related installs without the need for the system administrator. This might disrupt or falsify if some settings are done by the system administrator. Is this bug going to be fixed or the Fedora community is going more toward Microsoft Windows OS like theme of installing the updates without the need for the system administrator. I hope that this is not the future of Fedora. Fedora is unique in its way and I see that it is adopting more like Microsoft Windows display theme including menus. Thanks Nethaji

15 43

Evolution and Fedora 21 or 22 Kernel 3.19 and above
by Nethaji 19 May '15

19 May '15

Hello, I use Evolution mail client and when I updated from Fedora 20 to 21 or did a fresh install of Fedora 21 workstation, I have problem with evolution restoring my backup file or reading local emails previously saved on the system. The folders are mounted from a remote location in cifs format using either autofs or fstab. There are two issues with this. 1. It mounts the remote path and displays the folder to be 0 size, but normally it shows 4096 for a directory. When I do 'ls -i' the inodes are shown properly. 2. The files prior to update or installation in these folders, especially evolution are not accessible even through 'vi' after mount the file system on a client. 3. I tested this with Debian and Ubuntu (the latest available OS for both) and see the same result, except for Ubuntu, which in evolution opens the saved emails properly. I think the problem is with the kernel version from 3.19.5-200.fc21.i686 +PAE, ignore PAE. It is the same with a non-PAE kernel. I tested on the following kernels and to that I put the commands that worked. Kernel - 3.19.5-200.fc21.i686+PAE (Fedora 21) Kernal - 4.0.0 or 4.0.1 or 4.0.2 (Fedora 22) Kernel - 2.6.32-358.23.2.el6.x86_64 (Redhat Enterprise Linux 6) Kernel - 3.2.0-4-486 (Debian) Kernel - 3.16.0-30-generic (Ubuntu 14.04 LTS) Evolution version - Ubuntu: 3.10, Fedora21: 3.12 Attached with this email are two snapshots of email display from Ubuntu and Fedora 21. The same effect is seen in Fedora 22. While Ubuntu can display the locally saved email, Fedora says permission denied or no such file or directory. The text file 'FedoraCIFSshare.txt' is a summary of what I get when I 'vi' or 'cat' on the saved emails. When I do the same in Ubuntu, Enterprise Linux or Debian, I can open the files using both the email client and text editors. This problem does not even let me to save any new mails into these folders (i.e. locally) as they cannot be seen again. This is the same for Drafts too. This only happens on a CIFS mounted folders and not on local folders (the folders on the system's harddrive). The cifs share is mounted using the command or using autofs mount -t cifs //server/home /home/user -o username=myname The same command is used in Debian, Ubuntu and Enterprise linux. Everything works as expected except on Fedora 21 and Fedora 22. Even on Fedora 20 with kernel 3.19 Thanks Nethaji

2 1

Council Engineering update
by Josh Boyer 18 May '15

18 May '15

Hi Workstation WG, As part of the on-going Council updates, I'm organizing a Fedora Engineering update. This includes the various WGs, rel-eng, infrastructure, and a few others. The idea behind this is to give a brief update of the work your group is doing towards the F23 and F24 releases. Think of this as a 5-10 minute "lightning talk" of the highlights you want to see in those releases. The meeting is July 7th. It would be excellent if you could have a volunteer present the update for your group and stay around to answer any questions. Worst case, please gather the information and send it to me and I can do the overview, but representation from the group is clearly preferred. If you have questions, please let me know. The idea and format are somewhat new, so we'll work through this as best we can. josh

1 0

hibernation unsupported by installer, but is default in gnome
by Chris Murphy 15 May '15

15 May '15

This combination is sufficiently incongruent to be utterly broken, and therefore looks a likely blocker in my opinion. a. It's the default behavior, rather than power off, when battery power is critical https://bugzilla.redhat.com/show_bug.cgi?id=1141345 b. Either systemd or the kernel isn't seeing the hibernation image, or isn't putting the system into hibernation mode, because it just reboots when the user hits the power button trying to resume. Therefore resume doesn't actually happen. https://bugzilla.redhat.com/show_bug.cgi?id=1199708 c. The installer doesn't configure systems for hibernation out of the box. Until b and c are addressed, the simple fix is to address bug a. -- Chris Murphy

2 2

2015-05-18 @ 1600 UTC Fedora Blocker Review Meeting
by Adam Williamson 15 May '15

15 May '15

# F22 Blocker Review meeting # Date: 2015-05-18 # Time: 1600 UTC # Location: #fedora-blocker-review on irc.freenode.net Time for blocker review once more on Monday! I will not be around to run the meeting as I'm on vacation; roshi will likely be running it. This is the final scheduled blocker review meeting before Go/No-Go, so please make sure any bugs you want discussed are nominated in time. As I write this, there are 5 proposed blockers and 1 proposed freeze exception. We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Official Fedora Survey 2015
by Diogo Campos 15 May '15

15 May '15

I have seen things like these recently: 1- https://blogs.gnome.org/uraeus/2015/05/07/summary-of-fedora-workstation-fee… 2- https://lists.fedoraproject.org/pipermail/desktop/2015-April/011897.html 3- https://lists.fedoraproject.org/pipermail/desktop/2015-April/011860.html 4- http://otroblogdegnu-linux.blogspot.com.br/2015/05/do-you-want-gnome-tweak-… 5- Someone (Mathew Miller?) saying that Fedora should have something like this: http://blog.brackets.io/2015/03/27/introducing-brackets-health-report/ (these are my words, can not find the original message). So, I was wondering... There is interest in a "Official Fedora Survey 2015" thing? Because I can (and I want to) do something about it. I am thinking in something to expose the concrete needs/difficulties/desires from real users (especially from those who care) about Fedora (and Linuxes, and OSes) in a useful, understandable, and more precise way. If yes, please, say it, so I can show/catch ideas and work on a demo. And, if not, please, say it too, because I kinda don't want to waste my time on an useless thing. Thanks.

10 15

Fedora Health Report
by Diogo Campos 15 May '15

15 May '15

Hi again. You've probably seen this: https://lists.fedoraproject.org/pipermail/desktop/2015-May/012069.html But we have to agree that, if useful, its usefulness is a bit limited. I also said in that e-mail, that there is mentions of desire (by someone, somewhere - can't remember, sorry) of a Fedora equivalent of this: http://blog.brackets.io/2015/03/27/introducing-brackets-health-report/ (my words). But I ignored this possibility, at first, because I thought that it was something way out of my skills. Turns out I realized that I know a bit of Node.js :P So, now, I'm kinda interested in making this too, but I am not really sure of how to do it :/ Probably the basic stuff can be covered by this: https://nodejs.org/api/os.html But beyond that, especially about (possible) Fedora specific details (like SELinux), I'm totally lost. So, in this e-mail, I am asking for confirmation that there is interest on this, and also asking for a bit of (general) technical advice. Could someone kindly provide me any of these?

2 5

Re: Testing request: gdm-on-Wayland on hybrid graphics laptops (esp. Macbooks)
by Adam Williamson 14 May '15

14 May '15

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 to keep things precise and clear so we don't confuse ourselves: is this a system with dual GPUs? When you say 'GDM issues', do you have the same symptom as Chris (boot to a black screen)? If you edit /etc/gdm/custom.conf and uncomment the line: #WaylandEnable=false and reboot, does it start working? Thanks! (same questions for all testers...) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Testing request: gdm-on-Wayland on hybrid graphics laptops (esp. Macbooks)
by Adam Williamson 14 May '15

14 May '15

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-X, leaving the user with a black screen and no obvious way to proceed. This is obviously a bad bug, but so far it has only been observed on one test system (a Macbook Pro 8,2) by one tester. A few other testers have tried to reproduce on other hybrid graphics systems, but have not been able to. It would be very helpful to get some more data here. If anyone has a hybrid graphics laptop and can spare some space (or perhaps attach an external drive) for a test F22 install, can you please try installing F22 Workstation TC3 and creating a user: https://dl.fedoraproject.org/pub/alt/stage/22_TC3/Workstation/x86_64/iso/Fe… Live-Workstation-x86_64-22-TC3.iso then boot the installed system, and see if GDM appears correctly? Thanks. Note there is a different bug which causes GDM-on-Wayland to flicker on some hardware: https://bugzilla.redhat.com/show_bug.cgi?id=1218688 that's something different, and is a bit further along in the diagnosis/fix process, so we probably don't need further reports of that one (though once a fix arrives, it'd be good to have folks test it). If you find you seem to be affected by the bug, please add your details to the report. If you test and find you're *not* affected by the bug - you see GDM properly - please reply to one of the mailing lists, so we can get some idea of the proportions of affected vs. non-affected testers. Thanks a lot for your help, folks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 2

should we always install updates by default at each shut down?
by Kalev Lember 14 May '15

14 May '15

Hi all, kparal pointed out on IRC today that in F22, gnome-shell's shutdown dialog has the "Install pending updates" check box always checked. I knew that we hadn't deliberately changed the default, so I did some digging. It turned out to be a fallout from https://github.com/hughsie/PackageKit/commit/0a7b6d67b98cd06cabe03176c02db8… that regressed the PackageKit DBus API that gnome-shell uses, basically flipping the default from "do not install updates by default" to "reboot and install updates". sgallagh asked me to seek guidance on the list here: Is it something that we should fix before the F22 release and flip the default back so that when someone hurriedly clicks through the shut down dialog, they don't accidentally go into a 15-minute offline update applying mode? -- Thanks, Kalev

13 26

Re: Fixing express install for F23
by Zeeshan Ali (Khattak) 14 May '15

14 May '15

Hi Paul, Thanks for bringing this up. > One way to fix that would be to bring them back -- essentially go back > to producing the images we offered before. That doesn't mean we need > to advertise them on the website, though. I think we do need to advertise them. Otherwise I don't see how else are users supposed to find them. If we only advertise live media for workstation, most users will simply download and try that and they'd be annoyed by lack of express installation option for an OS on which they are likely using Boxes. Besides, I really don't see a good use case for not advertising these media. As I pointed out to Christian yesterday, we have plenty of free space on the right side here for just one more ISO link: https://getfedora.org/en_GB/workstation/prerelease/ in comparison the server's download page looks more complete: https://getfedora.org/en_GB/server/prerelease/ > What are the other alternatives for fixing? As you can see on the discussion on the bug you linked in your mail, I was told that it'd be good if Boxes/libosinfo could support express install through netiso. I've spend quite a lot of hours getting that to work[1]. The final set of patches that will actually make it work are pending review on libosinfo list. However we still have some issues that I can't fix on my end: 1. There is still no plan to advertise an F22 workstation or generic netinstaller. 2. Live media (that is advertised) does not support kickstar AFAIKt: https://bugzilla.redhat.com/show_bug.cgi?id=947376 . This isn't really an issue if #1 is resolved. -- Regards, Zeeshan Ali (Khattak) ________________________________________ Befriend GNOME: http://www.gnome.org/friends/ [1] That included adding new mechanism in libosinfo to identify media through volume-size since we won't even ensure unique volume IDs on every ISO, a standard good practice even followed by certain big proprietary companies famous for not following standards (Yes, I'm ranting but I've been very patient about this until now).

1 0

The “Windows Just Works” BIG fallacy
by Diogo Campos 13 May '15

13 May '15

Hi. Yes, again. In this e-mail I just want to share a tiny bit of my personal experience with people and computers and operating systems. It applies to Windows XP and, especially, Windows 7. I don't know about Windows 8; haven't used; Nor OS X. FIRST THINGS FIRST: Normal people don't know how to install Windows. Period. Unless there is hardware coming with Fedora pre-installed, don't even dream about “compete with” or “compare” a pre-installed Windows with a Fedora that you have do download(!), boot(!) and install. Otherwise, the best you can try is to create a DAMN EASY installer and pray. And by “damn easy” I'm talking about a screen to select the language (or detect it automatically, somehow, and skip this step) and another screen with two big buttons saying “Erase everything and Install Fedora ” and “Install Fedora alongside existing OS and data”. No partitioning, ever (or, at least, let it hidden behind a tiny something); choose a filesystem, choose a layout, and make it work (great) on every workstation's disk scenarios out there. Prefer to expose the other needed steps (initial setup) after the system is already on the disk, so the “adventurer”, if scared, can't give up anymore. In another words: “Install Fedora” should be compared to “Install Windows”; “Pre-installed Windows” should be compared to “Pre-installed Fedora”. Also, really important, is to perceive that “someone installed Windows/Fedora on my computer” is way more common that “I installed Windows/Fedora on my computer”. THE FALLACY: Respecting the previous reasoning, never compare “customized Windows” with “stock Fedora”. So, below, I will compare “stock Windows” with “stock Fedora” (by “stock” I mean freshly installed from a official media; by “customized” I mean “stock” plus additional external work from someone - be individual, company, vendor, etc). # Codecs = MP3, AAC, H.264, H.265, Vorbis, Opus, VP8, VP9. Windows: Yes, Yes, Yes, Yes, No, No, No, No. Fedora: No, No, No, No, Yes, Yes, Yes,Yes. Conclusion: analyzing the 8 (4 audio, 4 video) current big codecs on the market, we have a tie! Is also worth noting that installing additional codecs on Windows is of a equivalent pain that on Fedora. # Office Stuff = xls(x), doc(x), ppt(x), ods, odt, odp. Windows: No, No, No, No, No, No. Fedora: Yes, Yes, Yes, Yes, Yes, Yes. Conclusion: in (Microsoft) Windows, even to open files from another Microsoft product (Office), you can't without additional work from you (or someone else). # Miscellaneous = PDF, torrent, common archives. Windows: No(!), No, No. Fedora: Yes, Yes(?), Yes (except RAR, for no reason). Conclusion: WTF Windows? No PDF?! # Graphic Cards = Intel, AMD, Nvidia. Windows: No, No, No. Fedora: Yes, Yes, Yes. Conclusion: Oh, boy! Windows without video drivers is pure garbage! You have to, at minimum, select to install the driver on Windows Update to have 2D (and 3D) acceleration! Sometimes even to have the correct resolution! On other hand, Fedora comes with all these preinstalled! Yay! # Other Hardware (drivers). Windows: maybe. Fedora: maybe. Conclusion: have luck, or have fun looking for drivers. On both systems. FINAL THOUGHTS: Fedora isn't the perfect OS. But Windows also isn't. A bunch of reasons in favor of Windows aren't technical merits. Maybe commercial, or social; but not technical. Fedora can do better, sure. And it will. Especially if it doesn't fall in such misconceptions. This also highlight the importance of the “pre-installed” (or “just works”) concept. Be OSes, apps, codecs, drivers, or whatever. As I showed to you, Windows without the “pre-installed” concept, simply doesn't shine at all. So, Fedora have to keep this always in mind: normal people don't know how to “install” things. I don't expect this to be agreed or disagreed. I just wanted to share a bit of my experience on the role of “IT guy” that I do to some normal people. Hope it helps, somewhat. Thanks.

12 12

Re: The “Windows Just Works” BIG fallacy
by Chris Murphy 13 May '15

13 May '15

re: codecs. So I had this experience the other day, mp4, and totem (Videos) gives me some message about how some codec plugins are missing. dnf search doesn't find them, adding RPM fusion and searching doesn't find them, I do google searches and I run into the Internet Doesn't Work (TM), or more specifically Google Search sucks because it doesn't present relevant results in the first two pages. So I gave up and booted OS X. re: document formats. I think it's a big pro to point out LibreOffice is included and provides both Office document format support, and *easily* enables the user to get out of that b.s. dependency. Closed document formats really piss me off, much more than closed proprietary codecs. Yay Document Liberation Project! re: Windows vs Fedora installation. First there are two kinds of Windows installations: -- official media from Microsoft offers a very straightforward installer that starts out with two options Upgrade and Custom. Neither suggests new installation, so that's confusing but there are only two paths you pick on and get it wrong and you pick the other option next time - not difficult. It's also uncommon, because this method is designed mainly for upgrades, not new installations. -- OEM recovery partition. In Windows 8 the options are reset (obliterate all data and reinstall the OS), and refresh (keep user data, but revert to a clean unupdated OS and new settings). This is very similar to how mobile devices reset. And similar to the systemd folks' idea of stateless systems. And the direction I think installs and resets on Fedora ought to go in, perhaps with a couple points of additional granularity. OS X's installer is point and shoot, it offers essentially no options. Apple and Microsoft don't spend squat on their installers. They're both largely unchanged in over a decade. I've never run into a bug with either of them. User confusion is minimized by the fact there are two or zero options. They definitely never ever crash. Anaconda is just a pile of feature sprawl and it's completely normal and understandable something that complicated is going to have x% of presentable bugs and regressions - and it does. Three years after newui, it still dominates blocker bugs. I consider it a misallocation of resources, but lovely that life is, it's not my decision or I'd rip out all of custom partitioning and marry it with blivet-gui. [1] re: graphics cards. This is terrible on Linux. It's not Fedora's fault. Regressions, dual-GPU suckage, crap power management, on and on. It's just awful, and I don't use Fedora when I'm on the road because of this - the battery life is just unworkable. OS X has completely seamless integrated and discrete graphics switching totally figured out, for years now. Of course, they cheat, controlling drivers and hardware, and sign all the super secret NDAs to have this functionality (because of course the world would end fucking tomorrow if anyone knew the super secret shit). [1] My idea installation scenario for Fedora Workstation in another dimension, is live media based on a Btrfs seed device, the user boots the media, and a minimal UI helps them add a drive (partition) and configure some things, including G-I-S starting, and then the system is usable. Behind the scenes, the defined drive is added to the seed device, the seed device is removed, all data on the live media is migrated to the user defined device and then the live media is ejectable. No reboot required. Between ostree, or revised offline updates atomically updating Btrfs snapshots, or Btrfs send/receive, both the double boot of current offline updates as well as even any compulsory reboot can be eliminated. -- Chris Murphy

1 0

talking points update
by Matthew Miller 13 May '15

13 May '15

I made a few changes to https://fedoraproject.org/wiki/Fedora_22_talking_points#Fedora_Workstation: * Merged the scrollbar change into "refined themes". While cool, I'm not sure it stands alone. * Combined the various app updates under "Application improvements". Do these make sense to the rest of you? Do we have applications beyond the GNOME base which might be valuable to highlight here? DevAssistant 0.11, maybe? How about Vagrant? I think that's a pretty big deal to some of our target audience. <https://fedoraproject.org/wiki/Changes/Vagrant> -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

2 1

Tweak Tool in Workstation?
by Paul W. Frields 13 May '15

13 May '15

Re: <https://bugzilla.redhat.com/show_bug.cgi?id=1220007> There seem to be a bunch of users asking for inclusion of the Tweak Tool in Workstation. On the one hand, I'm not sure this is coming from a solid use case perspective, beyond "I like to fiddle more settings in the GUI than the standard GNOME Settings allow." It seems to me that if someone knows what they want to tweak at that level, it would follow they're capable of installing a piece of software for this. On the other hand, this may be an opportunity to gather useful information on tweaks to GNOME. It would be nice not to close the BZ bug peremptorily. We should consider the request thoughtfully in the context of Workstation, and if possible, see what information we can glean from the reporters or interested parties, and see what action is worth taking. -- 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

19 70

LVM in default filesystem layout
by Chris Murphy 13 May '15

13 May '15

This is a consolidated post, responding to multiple parties. Pete Travis lists at petetravis.com Tue May 5 15:45:11 UTC 2015 > I've seen people get themselves into tricky partitioning layout situations > - especially on non-GPT systems - and the flexibility of LVM made it > possible for them to install Fedora. Sometimes they did it to themselves, > sometimes it's from the OEM. I suspect with admittedly no hard data that > LVM as default transparently handled many, many situations where without > LVM, relatively complex manual partitioning would be required. > For any preexisting 3 primary partition layout, the remaining MBR partition can become an extended partition, and Anaconda/GRUB can (and do) use only logical partitions. For capturing non-contiguous partitions and presenting them as one volume, either LVM or Btrfs would be needed. People get themselves into tricky partitioning layouts because Linux installers are explicitly designed let them do crazy things. This doesn't happen on Windows, OS X or mobile devices. It's one size fits all, you get what you get, no discussion. Yet despite the complexity of the installer's custom partitioning, it can't delete either LVM VG's or Btrfs volumes, instead this only happens once the user manually deletes all LVs or subvolumes first; and it requires the user manually create required partitions on UEFI. It's a task and knowledge not required for BIOS hardware for all of Fedora's history, and for no benefit. And yet it's not a bug. [6] As far as I know this is still a bug, it basically breaks boot of any prior OS using LVM because its LVs aren't made active during Fedora installation, therefore boot entries aren't created for it. Anaconda should run grub2-mkconfig when LVM devices are active https://bugzilla.redhat.com/show_bug.cgi?id=825236 *Josh Boyer* jwboyer at fedoraproject.org <desktop%40lists.fedoraproject.org?Subject=Re:%20Re%3A%20LVM%20in%20default%20filesystem%20layout&In-Reply-To=%3CCA%2B5PVA66dJ-KXe7k9SWNSgxEM7%2B2Pe8eOhVZQDFJTkhWNog8cA%40mail.gmail.com%3E>*Tue May 5 13:32:50 UTC 2015* > And it's a great example of why we don't immediately default to using > something shiny and new just because it exists. Btrfs is neither > shiny or new at this point, and we look at it every release and > discuss it with upstream and it still isn't ready to be default. > More correctly these days, Fedora isn't ready for Btrfs. Even if Btrfs were as stable as ext4 Fedora couldn't use it by default right now. The installer still has problems dealing with it [1], and installer team expects Btrfs development to be slim to none in the near future [2]. Grubby still doesn't support /boot on Btrfs [3]. For any other file system those would be blockers. Fedora release criteria considers Btrfs equal, without exceptions, to other file systems, but in practice at blocker reviews pretty much anything Btrfs gets a hand waive. GNOME Disks doesn't support resize, snapshots, subvolume creation or deletion, gnome-shell gets confused with multiple disk Btrfs when mounting and umounting, and understanding volume size [4]. But openSUSE ships GNOME with Btrfs by default, so obviously these bugs aren't show stoppers, but still no bueno. None of these are Btrfs kernel code or btrfs-progs related. The fact is, Btrfs is not a priority on Fedora, maybe not even of tertiary importance to either Fedora or Red Hat who have a pile of ext4, XFS, and LVM developers but no Btrfs developers. So to properly pin the tail on this donkey, it's at least as much Fedora's non-readiness and disinterest in Btrfs right now. Other things to consider: ext4 on LVM is not well suited for eventual conversion to Btrfs. It can be done, it should work, if it doesn't it's a bug. But it just adds complexity for no good reason. Presently (and I'll argue properly) the installer doesn't permit LVM + Btrfs. There's an open question on backups and Btrfs volumes especially in the context of snapshots. We could use a tool that leverages btrfs send/receive so everything can be backed up, not just mounted subvolumes. The LVM and file system question opens up a bunch of related things, and I think they all need an integrated big picture approach rather than it just being a list of LVM pros/cons being used to arrive at a decision. *Stephen Gallagher* sgallagh at redhat.com <desktop%40lists.fedoraproject.org?Subject=Re:%20Re%3A%20LVM%20in%20default%20filesystem%20layout&In-Reply-To=%3C1000897174.11637103.1430859296013.JavaMail.zimbra%40redhat.com%3E>*Tue May 5 20:54:56 UTC 2015* > This should probably be its own thread, but I'll note that the current > state of encryption on Workstation is less than ideal (speaking as someone > using it). Offline updates with encrypted partitions means re-entering the > password twice; once to enter the offline-update mode and once to boot > again afterwards. This is a bigger inconvenience than it sounds. > Offline updates requiring two reboots is asinine. Encryption by default just makes it more obvious. Windows likes to do these double reboots on updates from time to time too, so it's not completely foreign. But for the most part they quit the user session, do updates, and reboot once. That's what happens on OS X also. To do encryption by default, there needs to be a way for gnome-control-center>users>change password to also reset the KEK in LUKS, as well as to add keys when users are added. Right now, LUKS supports 8 key slots, which may be a problem for encryption by default. Otherwise I support the idea of encryption by default. [5] Chris Murphy [1] Can't resize btrfs https://bugzilla.redhat.com/show_bug.cgi?id=962143 Custom partitioning can't delete Btrfs volumes (manual full teardown of each subvolume must be done by the user) https://bugzilla.redhat.com/show_bug.cgi?id=1185117 [2] https://bugzilla.redhat.com/show_bug.cgi?id=585525#c5 [3] This single bug has had numerous side effect bugs related to kernel upgrades failing to boot, crashes due to the lack of an initramfs entry in the grub.cfg, install failures. It goes back to 2012, is 102 messages long, no sane person will click on this link. https://bugzilla.redhat.com/show_bug.cgi?id=864198 [4] https://bugzilla.gnome.org/show_bug.cgi?id=746769 https://bugzilla.gnome.org/show_bug.cgi?id=710156 https://bugzilla.gnome.org/show_bug.cgi?id=708786 [5] It's a drag there's no open source UEFI driver to enable FDE OPAL 2.0 support. Many SSDs (I think now all Samsung SSDs) come with OPAL support and already always encrypt the drive, but it's always unlocked by default so it appears to be unencrypted. [6] https://bugzilla.redhat.com/show_bug.cgi?id=1022316 -- Chris Murphy

1 0

2015-05-14 @ 1600 UTC Fedora Blocker Review Meeting
by Adam Williamson 13 May '15

13 May '15

# F22 Blocker Review meeting # Date: 2015-05-14 # Time: 1600 UTC # Location: #fedora-blocker-review on irc.freenode.net As I suggested in my earlier mail, let's do a special blocker review meeting to clear out the proposed blockers and FEs that have shown up since Monday! Let's make it Thursday to give people a bit of time. We'll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they're not fixed. Information on the release criteria for F22 can be found on the wiki [0]. For more information about the Blocker and Freeze exception process, check out these links: - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process And for those of you who are curious how a Blocker Review Meeting works - or how it's supposed to go and you want to run one - check out the SOP on the wiki: - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting Have a good weekend and see you Monday! [0] https://fedoraproject.org/wiki/Fedora_Release_Criteria -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

F22 blocker/freeze exception review: on-list? in-bug? special meeting?
by Adam Williamson 12 May '15

12 May '15

Hi, folks! We're now frozen for F22 Final, but a pile of blocker and FE nominations arrived after the review meeting, several with updates attached. It would be good to get these reviewed before next week. Especially of note, we have an FE request for https://bugzilla.redhat.com/show_bug.cgi?id=1211015 which would necessitate pulling in the KDE Frameworks 5.10.0 release: https://admin.fedoraproject.org/updates/kf5-plasma-5.10.0-2.fc22 which is obviously a significant change to the KDE spin. We also have GNOME 3.16.2 pending; they haven't filed that yet, but I'm expecting it today or tomorrow. If we're going to pull in a pair of significant desktop updates, we should do it as soon as possible. I really wish we could somehow stop having these situations where the desktop teams want to push big updates right after freeze points, as it seems to keep happening, but for right now we need to make a decision. So, I'd like to get sufficient votes on the proposed blockers and at least the significant proposed FEs as soon as possible. Would folks prefer voting on-list or in-bug, or having a special meeting, perhaps tomorrow (05-13) or Thursday (05-14) at the usual time (1600 UTC)? Please reply if you'd be willing to attend a special meeting. If you'd rather vote in-bug, feel free to do so - we can count those votes at a meeting if one occurs. Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Mouse capture issues when running in VMware (F22)
by Everaldo Canuto 12 May '15

12 May '15

Hello. Fedora 22 is not working well on VMware (Fusion or Workstation). Neither X11 or Wayland it working well and some of us still using Fedora virtualised for different reasons. Theres two bug reports about this but I don't know if someone is working on it. Also, I don't know how too found information about someone working on a bug report. Theses are reports: * https://bugzilla.redhat.com/show_bug.cgi?id=1214474 * https://bugzilla.redhat.com/show_bug.cgi?id=1204393 Is there someone looking at this bug reports? Isn't it a release breaker since it works well on Fedora 21? Cheers. -- Everaldo Canuto +55 11 981-141-805 | everaldo.canuto(a)gmail.com 01100101 01110110 01100101 01110010 01100001 01101100 01100100 01101111

1 0

Re: Why people are not switching to Fedora
by Norman L Smith 12 May '15

12 May '15

On Sun, 10 May 2015 11:41:13 -0500, Michael Catanzaro wrote: > We don't ship any system-config-* utilities anymore, and we will not > add any ever again (system configuration belongs in gnome-control > -center), so this isn't relevant to Workstation at all. This sounds > like a complaint for the KDE SIG. I agree system configuration belongs in gnome-control-center. I am not a gnome-shell hater. I use gnome-shell on all of my systems, but if things are replaced, they should be as good as what is replaced. system-config-printer is better than gnome-control-center with printers. The problem is the system-config-* utilities functions are not always completely replaced by the gnome-control-center. An example is you cannot share printers from gnome-control-center. Sharing printers is relevant to Workstation. A very popular solution from The Google is system-config-printer or Cups via localhost:631. See Gnome Bugzilla 692532 https://bugzilla.gnome.org/show_bug.cgi?id=692532 opened 2013-01-25, last comment 2013-02-15, last history entry 2013-04-19 "ui-review". It is interesting to read Red Hat Bugzilla 1136588 https://bugzilla.redhat.com/show_bug.cgi?id=1136588 in this context where there is a reference to localhost:631. I like the idea of Workstation. I have used Red Hat Linux and then Fedora since Apollo. I subscribed to this mailing list after reading about the new approach for Fedora. I get the impression from reading this list popularity as measured in number of users is a goal. A dubious goal... <with apologies for bluntness> A better goal is to be good at what you do. For me in the past Fedora has been very good to me. It is better to be good than popular. With all due respect, Norman

3 4

Why people are not switching to Fedora
by Christian Schaller 12 May '15

12 May '15

Hi, so a couple of weeks ago I blogged** about who Fedora Workstation is an integrated system, but also asking for feedback for why people are not migrating to Fedora Workstation, especially asking about why people would be using GNOME 3 on another distro. So I got about 140 comments on that post so I thought I should write up a summary and post here. There was of course a lot of things mentioned, but I will try to keep this summary to what I picked up as the recurring topics. So while this of course is a poll consisting of self selected commentators I still think the sample is big enough that we should take the feedback into serious consideration for our plans going forward. Some of them I even think are already handled by underway efforts. Release cadence Quite a few people mentioned this, ranging from those who wanted to switch us to a rolling release, a tick/tock release style, to just long release cycles. Probably more people saying they thought the current 6 Month cycle was just to harrowing than people who wanted rolling releases or tick/tock releases. 3rd Party Software This was the single most brought up item. With people saying that they stayed on other distros due to the pain of getting 3rd party software on Fedora. This ranged from drivers (NVidia, Wi-Fi), to media codecs to end user applications. Width of software available in general was also brought up quite a few times. If anyone is in any doubt that our current policy here is costing us users I think these comments clearly demonstrates otherwise. Optimus support Quite a few people did bring up that our Optimus support wasn't great. Luckily I know Bastien Nocera is working on something there based on work by Dave Arlie, so hopefully this is one we can check off soon. Upgrades Many people also pointed out that we had no UI for upgrading Fedora. HiDPI issues A few comments on various challenges people have with HiDPI screens, especially when dealing with non-GTK3 apps- Multimonitor support A few comments that our multimonitor support could be better SELinux is a pain A few comments about SELinux still getting in the way at times Better Android integration A few people asked for more/better Android device integration features Built in backup solution A few people requested we create some kind of integrated backup solution Also a few concrete requests in terms of applications for Fedora: http://www.mixxx.org http://www.vocalproject.net https://gnumdk.github.io/lollypop/ http://peterlevi.com/variety/ http://foldercolor.tuxfamily.org choqok for GNOME (microblogging client) ** URL - https://blogs.gnome.org/uraeus/2015/04/20/fedora-workstation-more-than-the-…

29 81

gnome-builder in the Featured section of gnome-software
by Elad Alfassa 11 May '15

11 May '15

Hi, Should we make gnome-builder a "featured" application in Workstation for F22? Builder, while still young, is already a very useful IDE for both C and Python from my experience, even when not working on GNOME apps/libraries. Additionally, right now when searching for "IDE" in gnome-software, IDEs like Code:Blocks and Anjuta rank higher in the search result. I'll send a patch upstream later to improve Builder's appdata and keywords to try to get it higher on the list. I really think Builder is something we should promote in Workstation, it is a very useful tool for our target audience. -- -Elad.

3 2

formal apology
by kendell clark 11 May '15

11 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all Boy, is this hard. I want to send out a formal apology to the mailing list for the ... less than helpful responses I've sent out, two in the last couple of minutes. My only excuse, poor as it is, is I've just had two beers last night before going to sleep, and I guess it affected my temper. That, and "windows just works" comments really irritate me. I should really try not to take it out on people, but I'm not good at that. Now that we're on the subject, suggestions on how I can avoid this in the future are welcome. I seem incapable of doing it myself. I'm all for using what you want, but sometimes I get carried away with what I use, and forget that other people use other distros. An obvious one, but shrug. Thanks Kendell clark Sent from Fedora GNU/Linux -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJVUR9mAAoJEGYgJ5/kqBTdDOAP/A/1fbzqYcIjG311AWAyovFn 7hzJJx7rBd3KYcMuL6opS2EBMRMHnf2xTl6BrIEmtNzG9B+Q7zphVNHjI++0Tz/s exEQV9xMaEAeB59BZ76dLjeSv5XjrxY3M4PKlwtDSaIMSSKmuQRg1jjUWFMVCQlE jU6bF3mToRng3pEx7jyrANlkJAGGTSku/NmETLTUccd5WYOg7Arv6m0eJ6IORC28 pP82W7ZFy6fnlU2nOk7xoc/W9eQBhdlci2CDCFc2crlSvdjt9uQfkj6Yfq2Kpgl3 Xy5CyMdiHh7x+MdSJj5uv5ne4E3ytVHx3noJb/cMusSSsL6RdqQjmGabkBL/PlEO HDNYQEHYFh00e3VIv3o8QIId/UhIDIfJu6qDWoNnTBsAN5aZBA7vGluuP4Ko+blm a75zPmFU1AJOEpVVpsK+60KGAKCNZ9X1X7EOXhu8yQwGOGlCEzcpPxk+a1DWJhJP ygVN7h7D5RHCaRcdlxwPobSUS6FwU4XJdsnPaDlRmmIHA1QRd43Hw5dOcC4gifWN EmMHqyMuHFeFDR5VzAiYVKF2eixxMRwb5UaQUbg4Y9fJ/QkAxk01RYPbB1ZxMXNO PaNw/v5MR2gpAYp/hPYNk58vB8FoqyJEGY64552PmZYQcyDSYUcwTk2vH/ajxYgV nfWyqHLddFXXJOmglxz2 =yb1N -----END PGP SIGNATURE-----

4 4

Workstation FESCo summary - draft
by Paul W. Frields 11 May '15

11 May '15

Stephen Gallagher kindly asked for a short summary of Workstation efforts and progress for FESCo's next meeting. I prepared a draft here that the WG (and Stephen) can review: https://fedoraproject.org/wiki/Workstation/Fedora_22_Workstation_FESCo_repo… I encourage direct edits, but I would also settle for critique or suggestions if you aren't good with the words. ;-) -- 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

3 3

Workstation WG Recap 2015-May-11
by Paul W. Frields 11 May '15

11 May '15

Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2015-05-11/workstation.2015… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2015-05-11/workstation.2015… Log: http://meetbot.fedoraproject.org/fedora-meeting/2015-05-11/workstation.2015… * * * ====================================== #fedora-meeting: Fedora Workstation WG ====================================== Meeting started by stickster at 13:00:10 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2015-05-11/workstation.2015… . Meeting summary --------------- * Roll call (stickster, 13:00:19) * Workstation report for FESCo (stickster, 13:03:49) * LINK: https://fedoraproject.org/wiki/Workstation/Fedora_22_Workstation_FESCo_repo… (stickster, 13:03:55) * F23/F24 Workstation planning (stickster, 13:05:56) * LINK: https://build.opensuse.org/package/show/SUSE:SLE-12:Update/gnome-shell (mcatanzaro, 13:17:22) * IDEA: Improvements to AD/FreeIPA domain behavior (integrate WS into mixed env) (stickster, 13:20:36) * IDEA: Container tools for developers to use on projects / integrate with DevAssistant (stickster, 13:20:52) * IDEA: Make home printers easier to access without admin authN (stickster, 13:21:12) * IDEA: Access to Active Directory printers and file-shares should be simplified (sgallagh, 13:23:03) * IDEA: Talk to purpleidea about packaging oh-my-vagrant as part of container tooling (stickster, 13:39:06) * ACTION: stickster assign people to each of the #idea parts to make sure we have a better defined problem (and maybe solution ideas?) for next meeting (stickster, 14:00:57) Meeting ended at 14:01:41 UTC. Action Items ------------ * stickster assign people to each of the #idea parts to make sure we have a better defined problem (and maybe solution ideas?) for next meeting Action Items, by person ----------------------- * stickster * stickster assign people to each of the #idea parts to make sure we have a better defined problem (and maybe solution ideas?) for next meeting * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * stickster (72) * sgallagh (39) * rdieter (32) * cschalle (30) * mcatanzaro (27) * mclasen_ (14) * pingou (9) * juhp_ (7) * zodbot (6) * kalev (5) * randomuser (4) * jwb (4) * bochecha (3) * number80 (3) * kwizart (2) * Capesteve (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

1 0

Re: Firefox crashing when trying to play youtube html5 videos
by Heiko Adams 08 May '15

08 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I figured out that "dnf remove gstreamer1-libav \*libva\*" seems to solve the problem. Reinstalling one of them makes firefox crashing again. Am 06.05.2015 um 14:05 schrieb Ankur Sinha: > On Wed, 2015-05-06 at 10:53 +0200, Heiko Adams wrote: > > Shouldn't be anything related to rpmfusion packages, should it? > Probably a FF issue? > - -- Regards, Heiko Adams -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVShu8AAoJED6DRcV6KbgxcPAP/1cih2cXOT64aP+5I5US4JJR edSlh9Y9t15qpRy6Pnwqylk9H0mx7qPRADs8/SAcNiB7f2BhYyS9iTycjHs6fpUF +ZG4WCvTGmAHWCwvQialCJ6WsyQ0dlZYKyCVqeHlSKSZXunxXlOmVFC6Wr999psS o9U8gRFNPbQAHBzctuPXCthAQmlnwwi2Ly3QXiDDl/cflWTMCNAQiZcObzT7EtKe QPM5n2j6xdYWy1mvp6K4pe7/7bQ8N2/QkD3+qqmCnr2O9MgEQwrW1t3r3dtqEoco jISEW6JrrhFbwyad2oX+ZXSeOHrPgfyOFxx+uMuooRKyTwyISj2jxRY43MeLFZn7 PeyQdJAK4uzvohpRclSjvPi4ujV0XRPGkQn51besi2ctGjdHhAD00tdzdL6UqEv8 XPeVjHNU2WRMmiIMm6iZ0OyzHz6/k7YxwmAa71ATVJ8uQ75pwX6gsvGicTZUlh/Q 8q/zcUCrqFenlPhC1QwfdPj39U9SBWg1NJ1yWe2PTlYH+qBJG4uEBXmQJWndetBq oc9uzJffqWC3Q3aEGoA+GCs8iK/Iy7kPiwvyL+samSKnFpMN8Qx1wJT76rEpgIM2 ovTE2x/MoX1vavqwkP3WcRdLleVkNXJtN32f0mu7FsMLnfLLjHw3dQj5nX9crcrn ylYoKFzKoZhok7ace0kb =DwBL -----END PGP SIGNATURE-----

3 3

Call for agenda for Workstation WG meeting 2015-May-11
by Paul W. Frields 08 May '15

08 May '15

Next meeting is Monday, 2015-May-11 at 1300 UTC/9:00am US-EDT. I'm specifically not encouraging additions to the agenda so we can discuss this important item we couldn't get to last time: F23/F24 Workstation planning: * What will we do to take developer experience to the next level? * What changes will we make to the PRD to specifically outline plans? -- 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

1 0

Problems "precision touchpad" Aspire E-11 series (clickpad type)
by Bastián Díaz 08 May '15

08 May '15

Fedora 22 (beta) rawhide Gnome 3.16.1 Aspire E-11 ES1-111M-C6NR Since I'm trying fedora 22, my laptop has presented problems in the recognition and functioning of the ClickPad. First, the ClickPad is not recognized by the system, which is easily solved by changing the BIOS settings to "basic touchpad" (advanced touchpad is defined by default), another solution is to add the line "i8042.nopnp" in GRUB . In either case, after a period of use the cursor goes crazy, moving across the screen. This problem is reported by other users and argue that the cause of the problem is software. The only solution is to turn off/on the Clickpad (fn + F7). This problem is very annoying and though I tried to resolve it with different configurations of Synaptics, I could not find answers to this problem. Does anyone know how to solve it ?, did not want to make a bug report about the ambiguity of the information and which is unable to detect the cause of the problem. I discard hardware problems because the laptop using Windows 8.1 with no problems with the ClickPad. Additional information (sites reporting the problem) http://blog.mdda.net/oss/2014/11/16/acer-e11-es1-111-c3nt-linux/ http://chakraos.org/forum/viewtopic.php?pid=83718%29%20*%20%28http://forums… https://bbs.archlinux.org/viewtopic.php?id=185329 http://community.linuxmint.com/tutorial/view/1361 Thanks Bastián Díaz

1 0

LVM in default filesystem layout
by Christian Schaller 06 May '15

06 May '15

Hi, So I just noticed that an a fresh install system I did of the latest FW22 beta the filesystem gets set up with LVM. I thought this was one of the changes we had done to the Workstation compared to the server image for instance, to not use LVM? If we haven't done so already I think we should since we don't really have any UI tools for editing LVM partitions (that said I realize it might be to big a change to push in last minute for 22, so at least for FW23. Christian

11 22

icon-masking in gnome
by Rudra Banerjee 06 May '15

06 May '15

Hi, I am a longtime fedora and gnome enduser. I want to propose icon masking facility for unthemed desktop icon, as it is very common in android. I talked to such a icon developer (Numix) and I was told that this is not supported in linux. Is there any work on this? Regards, RudraB

2 2

Firefox crashing when trying to play youtube html5 videos
by Heiko Adams 06 May '15

06 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, since yesterday firefox on Fedora 22 is repeatable crashing when trying to play youtube html5-videos. Any idea what's wrong? - -- Regards, Heiko Adams -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVSdaSAAoJED6DRcV6KbgxlX8P/1gHQTzrMzHHIPQlhLL+9/z3 OX8b1HGU0EQ7WQSCGZXhnu7PyV7CJw9zaJmsGNdcs79dzPwQR8gmcg9YLNXGjhrf ALkBQlZPJVEHwUytLeCD+MRnzoyFZy6vLjjWr1H6Pbev81YUiQsbhYZL4S+khQ3j 4jyFCeoWA2r/b4QX3gCrhSccxgrIJWLrOEOnZU/5cG5RcA1vRO2FThpJGD5LGw1E WOercQNOcLCc26LyxO+ADH5y8WuaGfmkOyfwN1DvTiagbUGYxDozcNmbY1/lqeRV XBzIxZM/QwLx4RS9q44aNyim2RIMYGJ2j6oI6BheB9QiiMwNHfG2vKXSwzlfM1uQ HlboP+sLrvDIthkevbiFQ23MQ/MeZ96qGAI5KlxzrAfhV2UDcOODU9vf63Cp0WLO RHsDZpd5G906ZGFvdh4nyFaeUZ4AZgbgMwattRbPzXyxn5WuZP4Fh7TJ3cakhtyN A+nJGGBtmSnGjk/VQNjuW/fHXNycxZ6gBBbc/Ktrs17UGTTZqZXAOzq6FzZMqF6A AkgIl9Gt+xRcLJ5A2jhlvcYJglL84R3jTKOAMn1Pzp9MgMOl2g5ScXgkMp2Z97Iq UAhgHS5bs7T7H8Q5+p/1kFe3UKDC5pZ0oXps316GGDIw0/IBNw620XqNZfud9hvo lBCejGzl1YD+oy9hJG5m =8xVb -----END PGP SIGNATURE-----

3 2

Re: LVM in default filesystem layout
by Norman L Smith 05 May '15

05 May '15

On Mon, May 4, 2015 at 10:24 PM, Christian Schaller <cschalle(a)redhat.com> wrote: > No it has been discussed and stayed as is ... and yes I agree that LVM > makes little to no sense on desktops or even laptops (the latter in > general only have one disc .. ). I think the number of disks does not matter. For a number of years, I have used a python application controlling rdiff-backup to perform unattended backups on several workstations and servers. The snapshot feature of LVM makes reliable backups possible with no manual effort. Most of my systems have mdadm raid encrypted physical volumes but LVM snapshots work fine on a single disk.

1 0

Report of F21 -> F22 package additions / removals
by Kalev Lember 05 May '15

05 May '15

Hi all, Here's a report of package changes between F21 and yesterday's F22 snapshot, comparing: Fedora-Live-Workstation-x86_64-21-1.iso Fedora-Live-Workstation-x86_64-22-20150504.iso Applications ============ Screenshots: F21, page 1: https://kalev.fedorapeople.org/applications-f21-page1.png F21, page 2: https://kalev.fedorapeople.org/applications-f21-page2.png F22, page 1: https://kalev.fedorapeople.org/applications-f22-20150504-page1.png F22, page 2: https://kalev.fedorapeople.org/applications-f22-20150504-page2.png New: org.gnome.Maps.desktop Renamed: gnome-terminal.desktop -> org.gnome.Terminal.desktop Packages ======== New leaf packages: adwaita-qt4 evince-browser-plugin fros-gnome gnome-maps google-android-emoji-fonts hyperv-daemons ibus-qt xorg-x11-drv-libinput New dependencies: abrt-addon-coredump-helper adwaita-qt-common anaconda-user-help bind99-libs bind99-license clucene09-core clutter-gst3 devassistant-cli devassistant-core devassistant-dap-c devassistant-dap-common_args devassistant-dap-cpp devassistant-dap-custom devassistant-dap-dap devassistant-dap-devassistant devassistant-dap-docker devassistant-dap-eclipse devassistant-dap-git devassistant-dap-github devassistant-dap-java devassistant-dap-nodejs devassistant-dap-perl devassistant-dap-php devassistant-dap-python devassistant-dap-ruby devassistant-dap-tito devassistant-dap-vim devassistant-gui dhcp-client dleyna-connector-dbus dleyna-core dleyna-server dnf-conf dnf-yum environment-modules f22-backgrounds-base f22-backgrounds-gnome firewalld-filesystem gc genisoimage ghostscript-core ghostscript-x11 gnome-documents-libs google-noto-fonts-common gsound gtk-update-icon-cache guile hplip-compat-libs hyperv-daemons-license hypervfcopyd hypervkvpd hypervvssd libblockdev libblockdev-btrfs libblockdev-crypto libblockdev-dm libblockdev-loop libblockdev-lvm libblockdev-mdraid libblockdev-mpath libblockdev-plugins-all libblockdev-swap libblockdev-utils libcryptui libfdisk libgltf libksba libpagemaker libphodav libpsl libusal lz4 NetworkManager-libnm NetworkManager-team npth openCOLLADA oxygen-icon-theme pinentry-gtk polkit-libs python2-firewall python3-chardet python3-cssselect python3-dapp python3-dnf python3-hawkey python3-humanize python3-iniparse python3-inotify python3-javapackages python3-jinja2 python3-libcomps python3-librepo python3-lxml python3-pillow python3-progress python3-PyGithub python3-pygpgme python3-PyXB python3-PyYAML python3-requests python3-six python3-sssdconfig python3-urllib3 python-dnf python-dnf-plugins-core python-dnf-plugins-extras-common python-dnf-plugins-extras-migrate python-pyudev rpm-plugin-systemd-inhibit rpm-python3 samba-client-libs samba-common-libs speech-dispatcher-espeak tcl timedatex volume_key-libs Removed packages: cryptsetup-python desktop-backgrounds-basic dhclient f21-backgrounds-base f21-backgrounds-gnome farstream festival festival-freebsoft-utils festival-lib festival-speechtools-libs festvox-slt-arctic-hts fftw-libs-double firewalld-config-workstation flite gnome-js-common gnome-packagekit google-noto-sans-meeteimayek-fonts gstreamer gstreamer-plugins-bad-free gstreamer-plugins-base gstreamer-plugins-espeak gstreamer-plugins-good gstreamer-tools gtkhtml3 libmpcdec liboath libofa libphodav-1.0 libtomcrypt libtommath opencc openjpeg-libs perl-Filter perl-Module-CoreList perl-version pinentry-qt pm-utils pth pyatspi pytalloc python-babel python-cssselect python-humanize python-inotify python-javapackages python-jinja2 python-lxml python-markupsafe python-nss python-progress python-pyblock python-PyGithub PyXB pyxdg PyYAML samba-libs seed sox sssd-libwbclient systemd-compat-libs xorg-x11-drv-modesetting yum-langpacks -- Kalev

2 2

Packaging differences for Workstation
by Paul W. Frields 04 May '15

04 May '15

A round of applause and thanks for Stephen Gallagher please! He recently got a packaging guideline approved that allows Fedora packages to vary by product/edition: https://fedoraproject.org/wiki/Packaging:Per-Product_Configuration I wanted to propagate here, since this might be of use for future package releases in F23. I would *not* recommend making any changes to Fedora 22 packages at this time, we're too close to F22 Final -- just Rawhide/F23. * * * P.S. Stephen advised there may be a minor technical change for upstreamability in systemd, but still, it's a Good Thing(tm). -- 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

1 0

Ascension - Open Source Game Launcher
by Diogo Campos 02 May '15

02 May '15

I think this is, at least, interesting: http://www.ibtimes.co.uk/reddit-users-want-replace-steam-open-source-game-l… Worth the read? Worth investigating? Worth contacting them? Worth encourage them? Worth helping them? Worth try to influencing them to something? Worth try to "merge" this effort with "GNOME Games"? Any other thoughts about this?

1 0

Clicking appointments in top notification bar doesn't open evolution calendar in F22?
by Ankur Sinha 01 May '15

01 May '15

Hi, IIRC, in F21, clicking events on the calendar in the top panel used to open up evolution in calendar mode (or was there a button to open calendar?). Nothing of this sort in F22 now? I think it was pretty handy :) -- Thanks, Regards, Ankur Sinha "FranciscoD" http://fedoraproject.org/wiki/User:Ankursinha

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop May 2015