Language Selection

English French German Italian Portuguese Spanish

Login and unlock in GNOME Shell 3.36

Filed under
GNOME

The upcoming GNOME 3.36 release includes a major update to the system login and unlock experience. The new design has been anticipated for a long time, and we’re excited that it has finally arrived!

GNOME’s existing login and unlock design has been largely unaltered since it was first introduced in GNOME 3.6, back in September 2012. That’s seven and a half years ago! It’s therefore no surprise that we’ve wanted to update the design for some time.

The initial round of design work for the new lock screen took place in 2017, at the GNOME UX hackfest in London. There, the GNOME design team, along with GNOME Shell developers, reviewed the goals and requirements, as well as the issues with the existing design, including the main areas of feedback that we’ve had.

Read more

GNOME Shares Sneak Peek at Login and Lock Screens in GNOME 3.36

  • GNOME Shares Sneak Peek at Login and Lock Screens in GNOME 3.36

    GNOME 3.36 is shaping up to be a great update for the open source desktop environment used by numerous GNU/Linux distribution by default, including Ubuntu and Fedora. One of the new features in the upcoming release is revamped lock and login screens.

    GNOME’s Allan Day shared today a sneak peek at the new design of the login and lock screen in GNOME 3.36, which have not seen a major update since the release of GNOME 3.6 in September 2012.

    The new login and lock screens, which you can see in action below, aim to reduce friction and make the login and unlock experience less frustrating for users.

First Look: What to Expect in GNOME 3.36

  • First Look: What to Expect in GNOME 3.36, Including New Lock Screen

    Well, in this post I round up the multitude of improvements, changes and features that GNOME 3.36 plans to ship with to distil them in to an easily scannable list — so be aware that spoilers follow!

    Do keep in mind that GNOME 3.36 is still in development at the time of writing. Some features highlighted below may change subtly (or substantially) prior to release, or maybe even miss the release entirely.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

IBM/Red Hat/Fedora Leftovers

  • Top tips for making your Call for Code submission stand out

    With the deadline for the 2020 Call for Code Global Challenge rapidly approaching (it’s Friday, July 31st at 11:59pm PDT), I have three last-minute tips and a checklist to review before you submit your entry.

  • IBM Cloud Pak for Applications in 2 minutes
  • Fedora Community Blog monthly summary: June 2020

    In May, we published 13 posts. The site had 3,753 visits from 1,736 unique viewers. Readers wrote 1 comment. 119 visits came from Fedora Planet, while 553 came from search engines. The most read post last month was Fedora 32 election results available, which published at the end of April.

  • Madeline Peck: Finished Storyboards!

    I also attended an executive talk this week which was really interesting to listen to. I believe it was by DeLisa Alexander (Executive Vice President and Chief People Officer) and hearing about her career track and how she encouraged working for cool places who actually took listened to your demands was an important thing to remember.

What’s the Difference Between Linux and Unix?

Linux is a free and open-source operating system. Unix is a commercial product, offered by a variety of vendors each with its own variant, usually dedicated to its own hardware. It’s expensive and closed source. But Linux and Unix do more or less the same thing in the same way, right? More or less, yes. The subtleties are slightly more complicated. There are differences beyond the technical and architectural. To understand some of the influences that have shaped Unix and Linux, we need to understand their backstories. Read more

Programming: Python, Perl/Raku and More

  • Understanding Virtual Environments in Python

    Most often than not, as a programmer, you will be required to work on different projects. These projects would also have different dependencies. Let's say you're building two Python application simultaneously. Each of these applications have their own set of dependencies of Python version and packages. One of them is a To-Do list app written in Python3 version and uses Django Rest Framework and another one is a Music Library written in Python2 version using Requests library and different/older version of Django to fetch music information from SoundCloud API.

  • CircuitPython Game Development (PewPew M4)

    Check out this open source CircuitPython game development platform based on the ARM M4 microcontroller. If you're looking to do some homebrew game development on a handheld platform, this is a great option. In this video I give an overview of the hardware itself and show how the CircuitPython programming environment works on it along with some basic programming examples.

  • PSF GSoC students blogs: Blog post for week 5: Polishing

    Last week was another week of code and documentation polishing. Originally I planned to implement duplicate filtering with external data sources, however, I already did that in week 2 when I evaluated the possibility of disk-less external queues (see pull request #2).

  • 2020.27 Advanced Beginning
           
             

    Vadim Belman has kicked off a series of blog posts about advanced Raku subjects, but for beginners! And what a kick off it was! With already three blog posts to savour:

  • Let's make a Teeny Tiny compiler, part 3

    We are finally here. It is time to create the emitter for our Teeny Tiny compiler, which will give us a the foundation to a working compiler. The fame and fortune is so close! Previously, we implemented the lexer (part 1) and the parser (part 2). The source code from this tutorial can be found in the GitHub repo.

    The emitter is the component that will produce the compiled code. In this case, our compiler will be producing C code. Luckily, we designed our parser in such a way that will make emitting C code quite easy! Since C is so ubiquitous, we will rely on your favorite C compiler (e.g., GCC or LLVM) to produce the executable for us. This means our compiler will be platform independent without dealing with assembly code or complex compiler frameworks.

    Back before I started coding this compiler, I wrote several fictitious examples of Teeny Tiny code and the corresponding C code that I think the compiler should generate. This was a good exercise to see which things translate nicely (i.e., one line of Teeny Tiny equals one line of C) and what doesn't.

  • A Go lesson learned: sometimes I don't want to use goroutines if possible

    One very simple metric is how long it takes to read a little file from every NFS filesystem we have mounted on a machine. As it happens, we already have the little files (they're used for another system management purpose), so all I need is a program to open and read each one while timing how long it takes. There's an obvious issue with doing this sequentially, which is that if there's a single slow filesystem, it could delay everything else.

  • [Old] How to fix the broken web as a site owner and web developer

    The web is broken. Behavioral tracking without consent, abuse of personal data, annoying walls, prompts and popups and a lot of disrespect to the web user in general.

    More technically savvy people use browser extensions and better browsers to avoid most of the noise and have a clean and distraction-free web experience. The “average” internet user on Chrome without extensions is browsing a very broken web and is regularly being taken advantage of.

    Here’s how you as a website owner and web developer can help fix this broken web so we don’t require hacks and extensions to make it usable and everyone can have a great experience.

  • Data Prep Still Dominates Data Scientists’ Time, Survey Finds

    Data cleansing – fixing or discarding anomalous or wrong numbers and otherwise ensuring the data is an accurate representation of the phenomenon it is meant to measure — accounts for more than a quarter of average day for data scientists, followed by 19% for data loading (the “L” in ETL), according to Anaconda’s annual survey.

    Data visualization tasks occupied for about 21% of their time, while model selection, model training and scoring, and model deployment each consume 11% to 12% of the day, the survey found.

  • Rcpp 1.0.5: Several Updates

    Right on the heels of the news of 2000 CRAN packages using Rcpp (and also hitting 12.5 of CRAN package, or one in eight), we are happy to announce release 1.0.5 of Rcpp. Since the ten-year anniversary and the 1.0.0 release release in November 2018, we have been sticking to a four-month release cycle. The last release has, however, left us with a particularly bad taste due to some rather peculiar interactions with a very small (but ever so vocal) portion of the user base. So going forward, we will change two things. First off, we reiterate that we have already made rolling releases. Each minor snapshot of the main git branch gets a point releases. Between release 1.0.4 and this 1.0.5 release, there were in fact twelve of those. Each and every one of these was made available via the drat repo, and we will continue to do so going forward. Releases to CRAN, however, are real work. If they then end up with as much nonsense as the last release 1.0.4, we think it is appropriate to slow things down some more so we intend to now switch to a six-months cycle. As mentioned, interim releases are always just one install.packages() call with a properly set repos argument away.

Security and DRM

     
  • Revealed: How home router manufacturers dropped the ball on security
                     
                       

    The June report by Fraunhofer-Institut fur Kommunikation (FKIE) extracted firmware images from routers made by Asus, AVM, D-Link, Linksys, Netgear, TP-Link, and Zyxel—127 in all. The report (as noted by ZDNet) compared the firmware images to known vulnerabilities and exploit mitigation techniques, so that even if a vulnerability was exposed, the design of the router could mitigate it.

                       

    No matter how you slice it, Fraunhofer’s study pointed out basic lapses in security across several aspects. At the most basic level, 46 routers didn’t receive any updates at all in the last year. Many used outdated Linux kernels with their own, known vulnerabilities. Fifty routers used hard-coded credentials, where a known username and password was encoded into the router as a default credential that asked the user to change it—but would still be there, accessible, if they did not.

    FKIE could not find a single router without flaws. Nor could the institute name a single router vendor that avoided the security issues.
  •                
  • [Attackers] Start Exploiting Recently Patched BIG-IP Vulnerability
                     
                       

    F5 informed customers last week that a BIG-IP configuration utility named Traffic Management User Interface (TMUI) is impacted by a critical remote code execution vulnerability whose exploitation can result in “complete system compromise.”

                       

    The flaw is tracked as CVE-2020-5902 and it was reported to F5 by cybersecurity firm Positive Technologies. The vendor has released patches for impacted versions.

  •                
  • Taiwan’s defense science institute entangled in security breach over Chinese cloud service
                     
                       

    A procurement flaw has been found at Taiwan’s military technology development institute, and critics say it may have jeopardized the country’s national security because it involved a Chinese cloud service.

                       

    For successful bidders for online storage server equipment in 2018, the National Chung-Shan Institute of Science and Technology (NCSIST) required that a Beijing-based cloud service provider, Baidu, be included on a list of cloud service software to be used for backup needs. The incident was first reported by Apple Daily on Monday (July 6).

                       

    The requirement meant NCSIST files would be synchronized automatically on the Baidu program. The revelation has stunned people in many quarters, as the leaking of Taiwanese military technology to China poses a grave national security threat, wrote iThome.

  • Bryan Quigley: Wrong About Signal

    A couple years ago I was a part of a discussion about encrypted messaging. - I was in the Signal camp - we needed it to be quick and easy to setup for users to get setup. Using existing phone numbers makes it easy. - Others were in the Matrix camp - we need to start from scratch and make it distributed so no one organization is in control. We should definitely not tie it to phone numbers. I was wrong. Signal has been moving in the direction of adding PINs for some time because they realize the danger of relying on the phone number system. Signal just mandated PINs for everyone as part of that switch. Good for security? I really don't think so. They did it so you could recover some bits of "profile, settings, and who you’ve blocked". [...] In summary, Signal got people to hastily create or reuse PINs for minimal disclosed security benefits. There is a possibility that the push for mandatory cloud based PINS despite all of the pushback is that Signal knows of active attacks that these PINs would protect against. It likely would be related to using phone numbers. I'm trying out the Riot Matrix client. I'm not actively encouraging others to join me, but just exploring the communities that exist there. It's already more featureful and supports more platforms than Signal ever did.

  • Your next BMW might only have heated seats for 3 months

    In a VR presentation streamed from Germany today, BMW ran through a series of digital updates to its cars, including more details on the new BMW digital key service announced with Apple at last week's WWDC and confirming that current model cars will be fully software upgradeable over the air, a la Tesla. The first such update will hit BMW Operating System 7 cars in July. Packages are said to be approximately 1GB in size and will take roughly 20 minutes to install.

    But, the most notable part of the day's presentation was the new plan to turn many options into software services. BMW mentioned everything from advanced safety systems like adaptive cruise and automatic high-beams to other, more discrete options like heated seats.