On Wed, 2016-11-16 at 10:36 +0100, Jiri Eischmann wrote: > Hi, > I was going through most frequent crashers in Fedora 25 and vino is in > TOP10. When I looked at it I realized it crashed on Wayland because for > screen sharing you need X. [1] > It's a bit unfortunate that we have vino, which by default doesn't > work, in the default installation and its functionality is exposed in > Control Center. I wonder if it'd make a sense to patch the sharing > module in the control center to check if the session is running on > Wayland and if so, to disable the dialog. > > My understanding is that screen sharing is moving to the compositor or > Pinos [2] and vino will be deprecated, but in the meantime we shouldn't > expose its functionality on Wayland. Yes, please do something like this. If we'd found it earlier I would actually nominate it as a blocker as violation of 'All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.', but I don't think I'm going to rock the boat and do it now. Having it as a 0-day update would be very good, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
