desktop October 2016

desktop@lists.fedoraproject.org

37 participants
26 discussions

Please test the latest f25-background update
by Luya Tshimbalanga 25 Oct '16

25 Oct '16

The winning 16 supplemental wallpapers are now included in the f25-backgrounds package for all available desktop environment. Please test them on https://bodhi.fedoraproject.org/updates/f25-backgrounds-25.1.0-1.fc25 and add karma to push to the stable release. -- Luya Tshimbalanga Graphic & Web Designer E: luya(a)fedoraproject.org W: http://www.coolest-storm.net

1 0

Re: Fedora Rawhide-20161025.n.0 compose check report
by Adam Williamson 25 Oct '16

25 Oct '16

On Tue, 2016-10-25 at 17:07 +0000, Fedora compose checker wrote: > Missing expected images: > > Workstation live i386 > Workstation live x86_64 > > Failed openQA tests: 8/90 (x86_64), 2/16 (i386), 1/2 (arm) > > New failures (same test did not fail in Rawhide-20161024.n.0): > > ID: 44083 Test: x86_64 Workstation-boot-iso install_default@uefi > URL: https://openqa.fedoraproject.org/tests/44083 This hit a failure in the g-s-d color plugin: Oct 25 06:17:35 localhost.localdomain gnome-shell[1592]: GNOME Shell started at Tue Oct 25 2016 09:17:31 GMT-0400 (EDT) Oct 25 06:17:54 localhost.localdomain pulseaudio[1619]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Oct 25 06:19:01 localhost.localdomain gnome-session[1543]: gnome-session-binary[1543]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Oct 25 06:19:01 localhost.localdomain gnome-session-binary[1543]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Oct 25 06:19:01 localhost.localdomain gnome-session-binary[1543]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop The same test passed on staging, though, so it doesn't look to be a completely reproducible bug. We can keep an eye out and see if it happens again... > ID: 44163 Test: x86_64 universal upgrade_2_kde_64bit > URL: https://openqa.fedoraproject.org/tests/44163 This timed out again, but I actually think there may be something wacky going on in the upgrade process to Rawhide: tests that time out don't seem to be running smoothly but just running out of time, they seem to actually get stuck at the same point for a long time until they time out. I haven't had time to look into this in detail yet, though. > Old failures (same test failed in Rawhide-20161024.n.0): > > ID: 44097 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload > URL: https://openqa.fedoraproject.org/tests/44097 Boot is failing here, somehow, and winding up in dracut emergency shell. Don't know what's wrong with it yet. Anyone have time to look into it? > ID: 44113 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller > URL: https://openqa.fedoraproject.org/tests/44113 ipa-server-install crashed. https://bugzilla.redhat.com/show_bug.cgi?id=1388640 > ID: 44156 Test: x86_64 universal upgrade_desktop_64bit > URL: https://openqa.fedoraproject.org/tests/44156 > ID: 44159 Test: x86_64 universal upgrade_desktop_encrypted_64bit > URL: https://openqa.fedoraproject.org/tests/44159 > ID: 44161 Test: x86_64 universal upgrade_2_desktop_64bit > URL: https://openqa.fedoraproject.org/tests/44161 > ID: 44164 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit > URL: https://openqa.fedoraproject.org/tests/44164 > ID: 44184 Test: i386 universal upgrade_desktop_32bit > URL: https://openqa.fedoraproject.org/tests/44184 > ID: 44185 Test: i386 universal upgrade_2_desktop_32bit > URL: https://openqa.fedoraproject.org/tests/44185 Aside from the 'getting stuck and timing out' problem there's a dep issue affecting a lot of these tests - looks like firebird- libfbembed requires a rebuild for an ICU soname bump. I haven't looked into the details yet (to see if anyone's tried to fix it). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

Wayland drag and drop question?
by Norman L Smith 23 Oct '16

23 Oct '16

Fedora Workstation 25 Beta... I have found a difference between Xorg and Wayland drag and drop behavior in Gnome Shell. In Wayland you cannot drag the icon through the hot corner and paste into an application in a different workspace. The Xorg drag and drop is intuitive. You hold the mouse button down through the entire operation until you reach the target and then release to drop. The Wayland drag and drop works but it is not obvious what to do. You must drag the object into the hot corner. When the Overview is displayed, move cursor into the Overview. The icon is detached from the cursor and remains at the corner. You then release the mouse button and move the cursor to the workspace with the target. Press and release the mouse button to select the target. The target will be moved from the workspace to the body of the Overview. Move the mouse button to the target and press and release the mouse button. The Overview will close and the icon appears and reconnects to the cursor. Click the target and the object will be dropped. I have placed a compressed file with two short videos of Xorg and Wayland drags from an application to an application in a different workspace at: https://drive.google.com/file/d/0B52Y4vnjoV74WDVaQ1F6TjlXSk0/view?usp=s haring My question: Is the Wayland behavior intended by design or should I report a bug? Thanks, Norman

5 5

Two new Wayland bugs proposed as blockers
by Chris Murphy 23 Oct '16

23 Oct '16

Mirroring doesn't work https://bugzilla.redhat.com/show_bug.cgi?id=1386204 Screenshots and screencasts don't work on Wayland with multiple monitors (regression) https://bugzilla.redhat.com/show_bug.cgi?id=1384482 I think it'd be helpful if one or more WG members could chime in on whether these should be blocked on. Strictly speaking they probably do, but as we're cutting Wayland some slack since X can be used as a fallback, it's not clear. My opinion at the moment is to not block on mirroring, but to block on screenshots. -- Chris Murphy

2 1

screen lock shield
by Chuck Anderson 21 Oct '16

21 Oct '16

When I lock the screen in Gnome Shell, a shield screen appears when I hit any key (including e.g. Shift). This is good. However, when the screen saver/monitor power save kicks in, but the lock is set to a higher timeout, e.g. 30 minutes, no shield screen appears after hitting a key. Instead, whatever key you typed is sent to the application that has focus, but you can't know what application that is ahead of time because the screen is in power save. I find myself accidentally typing my password into random windows because I assume the screen is fully "locked" but it is just in power save mode. I.e. it is hard to distinguish between these two cases. Proposal: invoke the shield screen even when the screen isn't fully "locked" yet, just in power save, to prevent keystrokes from being erroneously sent to applications when waking up the screen.

6 6

Atomic Workstation development work
by Colin Walters 18 Oct '16

18 Oct '16

Hey, so we've talked about this a lot, and there are now two change pages: https://fedoraproject.org/wiki/Changes/WorkstationOstree This is in Fedora release engineering, and the scope is basically rpm-ostree + flatpak https://fedoraproject.org/wiki/Workstation/AtomicWorkstation But I'd like to revisit this, since I want to argue strongly for adding Docker to the mix. I now use "pet" Docker containers for most of my random software building/hacking, and I think this use case is not really covered by flatpak, and installing build tools on the host system I believe should be an explicit anti-pattern. I've set up https://pagure.io/atomic-ws which is running in CentOS CI. This specifically configures Docker in a useful way (overlayfs), and starts by default. Basically, by adding Docker, I think this feels closer to Project Atomic, hence the rebranding. Besides the link on the pagure page, I copied a snapshot of the ISO here: https://fedorapeople.org/~walters/atomicws-installer-25.2016.61.iso There are hence a few things to do to merge this into Fedora: - Decide on tooling emphasis (and management; does PackageKit need to learn anything about docker?) - Decide on the branding - Merge in the partitioning changes I made in https://pagure.io/atomic-ws/blob/master/f/overlay.yml#_46 (switch to something similar to Server - xfs by default, no split /home, but overlayfs for docker) - Fix the ostree management in Fedora (right now at-most-once-a-day is far too slow for development and far too fast for most users, I think it could make sense to do a two-week cadence (+async security) as we're planning for Atomic Host). This will also enable static deltas and make the experience more pleasant; see https://fedorahosted.org/rel-eng/ticket/6313 In CentOS for Atomic Host we use a "promotion" model.

2 3

Fedora 25 Workstation Wayland-by-default Test Day report
by Adam Williamson 17 Oct '16

17 Oct '16

Hi folks! [Yesterday's Test Day][1] on Wayland-by-default was a great success! Here's the Test Day report. 49 testers combined ran a total of 341 tests and filed or referenced 35 bugs. 9 of those have since been closed as duplicates, leaving 26 open reports: * [#1299505][2] gnome-calculator prints "Currency LTL is not provided by IMF or ECB" in Financial mode * [#1330034][3] [abrt] calibre: QObject::disconnect() : python2.7 killed by SIGSEGV * [#1367846][4] Scrolling is way too fast in writer * [#1376471][5] global menu can't be used for 15-30 seconds, startup notification stuck, missing item in alt+tab (on wayland) * [#1379098][6] [Regression] Gnome-shell crashes on switching back from tty ([abrt] gnome-shell: wl_resource_post_event() : gnome-shell killed by SIGSEGV) * [#1383471][7] [abrt] WARNING: CPU: 3 PID: 12176 at ./include/linux/swap.h:276 page_cache_tree_insert+0x1cc/0x1e0 * [#1384431][8] activities screen shows applications and search results at the same time * [#1384440][9] dragging gnome dash application to a specific workplace doesn't open the application to this workspace (on wayland) * [#1384489][10] Music not recognizing/importing files * [#1384502][11] Recent tab not available * [#1384537][12] Opening a new gnome-software window creates a new entry without a proper icon * [#1384546][13] Removing application does not bring back the install icon immediately * [#1384551][14] Printing directions using maps do not show the marked path * [#1384560][15] Screenshot of gnome-maps does not show the map part at all * [#1384569][16] Places dropdown search does not function if weather is open on secondary monitor * [#1384570][17] gnome-initial-setup does not exit at the end * [#1384572][18] Places dropdown search does not function if clocks is open on secondary monitor * [#1384590][19] [abrt] gnome-photos: babl_get_name() : gnome-photos killed by SIGABRT * [#1384596][20] gnome-boxes: starting fails without any feedback * [#1384599][21] gnome-calculator currency conversion is hard to use * [#1384616][22] thumbnail "border" seems misaligned in activities overview * [#1384651][23] Selecting city should automatically be added on Clock Application * [#1384665][24] [abrt] authconfig-gtk: gdk_window_enable_synchronized_configure() : python2.7 killed by SIGSEGV * [#1384671][25] system-config-language does not work under Wayland * [#1384675][26] system-config-users does not work under Wayland * [#1384678][27] Missing top-left icon (and full application name) on Wayland Some of these are not Wayland bugs, but it's not a bad thing that people found some non-Wayland bugs as well while testing! We did find several new Wayland issues, but on the positive side, no really big bugs that weren't already known and on the radar for the final release. So the event looks like a success on all fronts: we found some new bugs to squish, but it also gives us a decent indication that the Workstation-on-Wayland experience is in a good enough condition for a first stable release. We also confirmed that the Workstation-on-X11 session is available as a fallback and that works properly, for anyone who can't use Wayland for any reason. Many thanks to all the testers for their hard work! [1]: https://fedoraproject.org/wiki/Test_Day:2016-10-13_Wayland [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1299505 [3]: https://bugzilla.redhat.com/show_bug.cgi?id=1330034 [4]: https://bugzilla.redhat.com/show_bug.cgi?id=1367846 [5]: https://bugzilla.redhat.com/show_bug.cgi?id=1376471 [6]: https://bugzilla.redhat.com/show_bug.cgi?id=1379098 [7]: https://bugzilla.redhat.com/show_bug.cgi?id=1383471 [8]: https://bugzilla.redhat.com/show_bug.cgi?id=1384431 [9]: https://bugzilla.redhat.com/show_bug.cgi?id=1384440 [10]: https://bugzilla.redhat.com/show_bug.cgi?id=1384489 [11]: https://bugzilla.redhat.com/show_bug.cgi?id=1384502 [12]: https://bugzilla.redhat.com/show_bug.cgi?id=1384537 [13]: https://bugzilla.redhat.com/show_bug.cgi?id=1384546 [14]: https://bugzilla.redhat.com/show_bug.cgi?id=1384551 [15]: https://bugzilla.redhat.com/show_bug.cgi?id=1384560 [16]: https://bugzilla.redhat.com/show_bug.cgi?id=1384569 [17]: https://bugzilla.redhat.com/show_bug.cgi?id=1384570 [18]: https://bugzilla.redhat.com/show_bug.cgi?id=1384572 [19]: https://bugzilla.redhat.com/show_bug.cgi?id=1384590 [20]: https://bugzilla.redhat.com/show_bug.cgi?id=1384596 [21]: https://bugzilla.redhat.com/show_bug.cgi?id=1384599 [22]: https://bugzilla.redhat.com/show_bug.cgi?id=1384616 [23]: https://bugzilla.redhat.com/show_bug.cgi?id=1384651 [24]: https://bugzilla.redhat.com/show_bug.cgi?id=1384665 [25]: https://bugzilla.redhat.com/show_bug.cgi?id=1384671 [26]: https://bugzilla.redhat.com/show_bug.cgi?id=1384675 [27]: https://bugzilla.redhat.com/show_bug.cgi?id=1384678 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

3 5

coredumpctl integration for F25
by Michael Catanzaro 14 Oct '16

14 Oct '16

Hi, Currently we have coredumpctl installed by default, but it doesn't work because core dumps are consumed by ABRT instead. I'd like to get coredumpctl working out-of-the-box. We can do this by changing our systemd presets [1] to disable abrt-ccpp.service. ABRT will continue to function thanks to the ABRT developers' work on coredumpctl integration via abrt-vmcore.service. There is a somewhat- reduced feature set, but I've been running this for several months happily and I haven't noticed any issues; my crashes are being reported to FAF, and I can manually report to Bugzilla. See [2] for details. This might be slightly controversial for two reasons. First, the big change here is that core dumps will appear in the magical and super- awesome coredumpctl tool in addition to ABRT, but would no longer be created in the cwd when ulimit is set appropriately (we would need to feature that in the release notes). This aligns us with upstream systemd behavior, but diverges from Debian and Ubuntu, which still create the old-style coredumps in the cwd. Second, my understanding is that the ABRT developers prefer to improve abrt-cli and tell people to use that rather than coredumpctl. But as coredumpctl is very mature (nicer) and cross-distro so it gets many more contributors, I definitely prefer to instruct people to use coredumpctl instead for C/C++ crashes. We could totally do this change for F24 as well as it should be just a one-line change, but in the spirit of beta freeze I figure it's probably best left for F25. Michael [1] https://pagure.io/fedora-release/blob/master/f/90-default.preset [2] https://github.com/abrt/abrt/issues/1108

8 21

Advancing PurpleEgg as a Fedora feature for F26
by Matthew Miller 13 Oct '16

13 Oct '16

Owen Taylor pointed me to this blog post https://blog.fishsoup.net/2016/08/24/summer-talks-purpleegg/ (and to his Flock talk https://www.youtube.com/watch?v=R1Na7oqEFdQ, which I unfortunately missed). This basically *nails* what I was talking about in a previous message about doing interesting innovative things for developers on Fedora. I'd love to see this advanced to the point where it can be a central part of our story, and possibly tie in with Fedora Atomic Host and our other container efforts for deploy platform. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

Reminder: Wayland test day today!
by Adam Williamson 13 Oct '16

13 Oct '16

Just a quick reminder, folks, today (2016-10-13) is Wayland-by-default test day - please do drop by #fedora-test-day on IRC and help with the testing if you can! Live image download and test instructions on the wiki page: https://fedoraproject.org/wiki/Test_Day:2016-10-13_Wayland thanks everyone! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

desktop October 2016