GNOME 3.31.1 Released As The First Step Towards GNOME 3.32

[phoronix]

Phoronix: GNOME 3.31.1 Released As The First Step Towards GNOME 3.32

GNOME 3.31.1 was released on Thursday as the first step towards the GNOME 3.32 desktop update due out in March...

http://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.31.1-Released

[My8th]

You missed stating that it's Nvidia's proprietary drivers that'll have Wayland disabled for now in the gdm.

[Veske]

The suspend/hibernate changes... is this the reason why my sleeping computer now shuts down after 3 hours of sleep? Quite an annoying thing as it has broken my boot partition 2 times already.

[uid313]

I would like to see Evince packaged as a sandboxed Flatpak application with read-only (no write) access. File access only, no network access.
Maybe scope it to ~/Downloads/ and ~/Documents/

I find the default icon size in Nautilus to be excessively huge. Luckily its configurable to be more sane.

[johanb]

You missed stating that it's Nvidia's proprietary drivers that'll have Wayland disabled for now in the gdm.

Not sure if he has edited the post, it's mentioned in the article

GDM disables Wayland on the proprietary NVIDIA driver for now,

[SpyroRyder]

I would like to see Evince packaged as a sandboxed Flatpak application with read-only (no write) access. File access only, no network access.
Maybe scope it to ~/Downloads/ and ~/Documents/

I find the default icon size in Nautilus to be excessively huge. Luckily its configurable to be more sane.

Do you forget the part where some PDFs have editable fields and that there are multiple occaisions when you want to save those edits

[uid313]

Do you forget the part where some PDFs have editable fields and that there are multiple occaisions when you want to save those edits

Good point.
Yes, I did forget about that.

[Guest]

I would like to see Evince packaged as a sandboxed Flatpak application with read-only (no write) access. File access only, no network access.
Maybe scope it to ~/Downloads/ and ~/Documents/

What if I want to read documentation pdf files in /usr/share/doc/? And what if I want to read pdf files on network shares?

[uid313]

What if I want to read documentation pdf files in /usr/share/doc/? And what if I want to read pdf files on network shares?

Hmm, good point.
Maybe it could be have a scope that includes /usr/share/doc.
Or maybe it shouldn't be file system scoped. Maybe that wasn't a good idea.
Either way it would be nice to have it sandboxed so it doesn't have access webcam, microphone, etc.

[Guest]

I think any pdf related security mitigation should really happen in poppler. For example, handling ill-created files, etc...