September 2018 - desktop - Fedora Mailing-Lists

[Fedocal] Reminder meeting : Silverblue APAC

by sinnykumari＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Silverblue APAC on 2018-09-18 from 05:30:00 to 06:00:00 UTC At fedora-meeting-1 The meeting will be about: Fedora Silverblue is an rpm-ostree-based Fedora desktop edition. This meeting has been kept in APAC friendly timezone for folks interested in working on making Silverblue better. Issue tracker - https://pagure.io/teamsilverblue/issues More information available at: [https://teamsilverblue.org/](https://teamsilverblue.org/) Source: https://apps.fedoraproject.org/calendar/meeting/9315/

5 years, 7 months

1
0
0 / 0

[Fedocal] Reminder meeting : Silverblue

by sanja＠redhat.com

Dear all, You are kindly invited to the meeting: Silverblue on 2018-09-17 from 09:00:00 to 10:00:00 US/Eastern At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora Silverblue IRC meeting in #fedora-meeting-2 on Freenode. Fedora Silverblue is an rpm-ostree-based Fedora desktop edition. Source: https://apps.fedoraproject.org/calendar/meeting/9304/

5 years, 7 months

1
0
0 / 0

Fedora update ghostscript-9.24-1.fc28.x86_64 needs to be reverted

by nls1729＠gmail.com

I ran a dnf update of Fedora 29 today and it killed cups-pdf printer. I traced the problem to an update of ghostscript. I downgraded ghostscript returning cups-pdf to life. ghostscript-9.24-1.fc28.x86_64 and/or its associated packages is the problem. ghostscript-9.23-1.fc28.x86_64 works fine. There 3 serious ghostscript bugs on Redhat Bugzilla (1628710, 1628875 and 1628943 reported on 9/14 and 9/13). Please go back to ghostscript-9.23-1.fc28.x86_64 until the bugs are cleared.

5 years, 7 months

3
2
0 / 0

Fedora 29 Talking Points

by Alberto Rodriguez Sanchez

Hello Teams, I'm Alberto from the Marketing team, I'm asking for help to complete the Fedora 29 Talking points[1]. Talking points are key highlights of the new release. There are different types of talking points for different types of people: general desktop users/everyone, developers, and sysadmins. They are meant to provide a short, effective answer to the question "What cool stuff is in the latest release of Fedora?" They are compelling, not necessarily comprehensive. Best Regards. [1] https://fedoraproject.org/wiki/Fedora_29_talking_points -- Alberto Rodriguez Sanchez <bt0dotninja(a)fedoraproject.org>

5 years, 7 months

1
0
0 / 0

2018-09-17 @ 16:00 UTC - Fedora 29 Blocker Review Meeting

by Adam Williamson

# F29 Blocker Review meeting # Date: 2018-09-17 # Time: 16:00 UTC # Location: #fedora-blocker-review on irc.freenode.net Hi folks! We have 2 proposed Beta blockers, 6 proposed Beta freeze exceptions and 8 proposed Final blockers to review, so let's have a review meeting on Monday (those numbers may change over the weekend). If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here: https://qa.fedoraproject.org/blockerbugs/ . 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 F29 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

5 years, 7 months

1
0
0 / 0

Call for participation: Fedora Flatpaks

by Owen Taylor

I'd like to invite Fedora contributors to start creating Flatpaks of graphical applications in Fedora. We're still working on putting the final pieces into place to have a complete story from end to end, but it's definitely close enough to get started. If you maintain a graphical application, please try creating a Flatpak of it. Your experience will vary - some applications are quite easy, but if your application, for example: * Uses qt5-qtwebengine * Uses many KDE libraries * Uses many Perl or Python packages * Uses texlive etc, then you may want to wait - we will eventually be creating shared builds to make bundling these easier. Also, if your application has a system service, installs a polkit policy, or otherwise is not self-contained, then it's not a good candidate for a Flatpak. Or you can pick one of 280+ applications that have been identfied as easy to Flatpak: https://fedoraproject.org/wiki/Flatpak:Easy and assist out the application package maintainer by creating a Flatpak of that. An introduction, draft tutorial and other documentation can be found at: https://fishsoup.net/misc/fedora-docs-flatpak/flatpak/ (The plan is to integrate this into docs.fedoraproject.org. For now, the documentation source is at: https://github.com/owtaylor/fedora-docs-flatpak) For help, please ask on #fedora-workstation on Freenode, or mail desktop(a)lists.fedoraproject.org. Owen

5 years, 7 months

2
4
0 / 0

system now hibernates automatically 3 hours after suspend ?

by Kamil Paral

Hello, a few days back I noticed that my F29 laptop is hibernated every morning even though I suspended it the previous evening. After some digging, it seems that there's a new "systemctl suspend-then-hibernate" command that does exactly this (with a 3 hour delay) and gnome seems to execute it automatically instead of the classic "systemctl suspend". On one hand, this is absolutely awesome, and I've been wanting this for ages. Windows can do it, general users are used to this, and are usually very surprised when they have a Fedora laptop that drains their battery to 0% during a few days long suspend (that's the case for my wife and my parents). On the other hand, I'm a bit concerned that the default behavior changed unannounced and doesn't even seem configurable. In gnome-control-center, my power button action is configured to "suspend", yet it clearly performs "suspend-then-hibernate". There seems to be no way to opt out of this and use just a classic suspend. Another question is what happens if hibernation/resuming is not configured properly (swap partition missing, resume= argument missing, etc). Have those edge cases been covered? So, my questions are - has this been a deliberate change or is it just some happy coincidence of some systemd+gnome interactions? Will there be some release notes for the users announcing the change? Do plan to make it configurable (allowing users to select between suspend and suspend-then-hibernate)? Should we focus on testing the corner cases? Thanks.

5 years, 7 months

14
28
0 / 0

GNOME 3.30.0 megaupdate

by Kalev Lember

Hi all, As many of you know, I've been gone half the summer. I'm back now since Monday though and just in time for GNOME 3.30.0 :) We are quite a bit behind with the builds, like half of GNOME is still at 3.28.x or at various stages of 3.29.x snapshots, so there's quite a bit of catching up to do. I just requested a f29-gnome side tag and will be commencing 3.30.0 builds shortly. When the builds are done, I'll try to collect all the builds in a single Bodhi megaupdate as usual. Please use 'fedpkg build --target f29-gnome' if you are helping with builds, and I'll pick up anything that is tagged with f29-gnome in koji. Dunno what to do wrt the ongoing freeze and getting final 3.30 in F29 Beta, I guess it may be too late for that. Any opinions from QA here? There's also a few 3.30.0 builds already submitted separately into Bodhi. I may try to collect those to the megaupdate as well, not sure yet. Let's see how things go :) Thanks, Kalev

5 years, 7 months

12
22
0 / 0

Workstation WG meeting recap 2018-Sep-10

by Kalev Lember

================================= #fedora-meeting-2: Workstation WG ================================= Meeting started by kalev at 13:01:38 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-2/2018-09-10/workstation... . Meeting summary --------------- * Roll call (kalev, 13:01:55) * GNOME 3.30.0 megaupdate (kalev, 13:07:47) * 3.30.0 megaupdate prepared and in updates-testing now (kalev, 13:09:52) * LINK: https://bodhi.fedoraproject.org/updates/FEDORA-2018-85d637c544 (kalev, 13:10:11) * LINK: https://fedoraproject.org/wiki/Releases/30/Schedule (mattdm, 13:21:52) * LINK: https://wiki.gnome.org/ThreePointThirtyone (mattdm, 13:21:59) * LINK: https://fedoraproject.org/wiki/Releases/30/Schedule (mattdm, 13:22:23) * LINK: https://wiki.gnome.org/ThreePointThirtyone (mattdm, 13:22:26) * AGREED: Workstation WG would like to see the GNOME 3.30.0 megaupdate land in F29 beta (+1:5, 0:0, -1:0) (kalev, 13:24:01) * ACTION: Kalev to ask for a 3.30.0 megaupdate freeze exception (kalev, 13:26:51) * ACTION: Kalev to file a 3.32 Change for Fedora 30 (kalev, 13:27:06) * Review F29 deliverables (kalev, 13:28:27) * LINK: https://pagure.io/fedora-workstation/issue/72 (kalev, 13:28:30) * AGREED: Workstation WG acknowledges the deliverables. No requirements have changed compared to F28. (kalev, 13:33:22) * Should we include NetworkMaanger-ppp by default? (kalev, 13:33:49) * LINK: https://pagure.io/fedora-workstation/issue/70 (kalev, 13:33:52) * kalev to add NM maintainers to ticket, revisit in two weeks (kalev, 13:35:04) * Decide whether to include gnome-shell-chrome (kalev, 13:36:04) * LINK: https://pagure.io/fedora-workstation/issue/66 (kalev, 13:36:07) * AGREED: Workstation WG agrees to include gnome-shell-chrome (+1:5, 0:0, -1:0) (kalev, 13:42:08) * Open Floor (kalev, 13:43:35) * LINK: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... (otaylor, 13:44:10) * otaylor has flatpak building working in koji (kalev, 13:44:32) * next meeting is on Monday Sep 24, chair is ryanlerch (kalev, 13:50:04) Meeting ended at 13:50:20 UTC. Action Items ------------ * Kalev to ask for a 3.30.0 megaupdate freeze exception * Kalev to file a 3.32 Change for Fedora 30 Action Items, by person ----------------------- * **UNASSIGNED** * Kalev to ask for a 3.30.0 megaupdate freeze exception * Kalev to file a 3.32 Change for Fedora 30 People Present (lines said) --------------------------- * kalev (85) * stickster (35) * otaylor (24) * mattdm (19) * sgallagh (18) * zodbot (15) * juhp (9) * cschalle (6) * ryanlerch (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

5 years, 7 months

1
0
0 / 0

install Vulkan drivers by default?

by Kamil Paral

I have installed a fresh F29 system and I was a bit surprised that Vulkan drivers weren't present on that system, I had to manually install them (mesa-vulkan-drivers). Vulkan is getting pretty popular lately, there are certain high-profile games on Linux that use Vulkan *exclusively* (you can't run them on OpenGL), and there are many other games which have Vulkan as an option, which might improve performance. The latest breaking news were Valve enabling Wine-based compatibility layer in Steam, that can be used to run many Windows-only games on Linux, and it's again relying on Vulkan. So Vulkan is definitely getting mainstream. In order to have Fedora Workstation appealing to general users, I believe it should be a good choice for gaming (Christian wrote on his blog about considering including gamemode by default, that also ties into this). Is there any reason why Vulkan drivers are not installed by default in Fedora Workstation? Is that something we can fix for F29? Thanks!

5 years, 7 months

6
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop September 2018