<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sávio Eduardo Silva</title>
    <description>The latest articles on DEV Community by Sávio Eduardo Silva (@savioedu03).</description>
    <link>https://dev.to/savioedu03</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3910606%2F8022330f-3eef-4ab0-ba76-81b20774ac6e.jpg</url>
      <title>DEV Community: Sávio Eduardo Silva</title>
      <link>https://dev.to/savioedu03</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/savioedu03"/>
    <language>en</language>
    <item>
      <title>How to Set Up the Windows + Shift + S Screenshot Shortcut on Ubuntu</title>
      <dc:creator>Sávio Eduardo Silva</dc:creator>
      <pubDate>Thu, 07 May 2026 15:16:08 +0000</pubDate>
      <link>https://dev.to/savioedu03/how-to-fix-screenshot-shortcut-conflicts-in-ubuntu-2604-resolute-2i93</link>
      <guid>https://dev.to/savioedu03/how-to-fix-screenshot-shortcut-conflicts-in-ubuntu-2604-resolute-2i93</guid>
      <description>&lt;p&gt;If you’ve recently migrated from Windows to Ubuntu, you probably miss the &lt;code&gt;Win + Shift + S&lt;/code&gt; shortcut for quick area captures. In modern Ubuntu (GNOME 42+), the best way to achieve this is by &lt;strong&gt;reassigning native shortcuts&lt;/strong&gt; instead of creating custom ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Reassign Instead of Creating New?
&lt;/h2&gt;

&lt;p&gt;The GNOME Shell has a built-in interactive capture tool. By remapping the native settings, you avoid priority conflicts with the &lt;strong&gt;Super (Windows) key&lt;/strong&gt; and ensure that your captures are sent to both the clipboard and your &lt;code&gt;Pictures/Screenshots&lt;/code&gt; folder simultaneously.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step-by-Step Configuration
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;strong&gt;Settings&lt;/strong&gt; &amp;gt; &lt;strong&gt;Keyboard&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Click on &lt;strong&gt;View and Customize Shortcuts&lt;/strong&gt; &amp;gt; &lt;strong&gt;Screenshots&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Reassign the options to match the following workflow:&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Optimized Workflow Configuration
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;System Action&lt;/th&gt;
&lt;th&gt;Shortcut Key&lt;/th&gt;
&lt;th&gt;Description&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Take a screenshot interactively&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Super + Shift + S&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Opens the area selector (Just like Windows).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Record a screencast interactively&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Print&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Uses the physical Print key to start screen recording.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Take a screenshot&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Shift + Print&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Instantly captures the entire screen.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Take a screenshot of a window&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;Alt + Print&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Captures only the currently focused window.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; When you set &lt;code&gt;Super + Shift + S&lt;/code&gt;, the system might show a conflict warning. Simply click &lt;strong&gt;Replace&lt;/strong&gt; or &lt;strong&gt;Reassign&lt;/strong&gt; to confirm the new mapping.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  The Result
&lt;/h2&gt;

&lt;p&gt;With this setup, you get the best of both worlds:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Productivity:&lt;/strong&gt; Your muscle memory from &lt;code&gt;Win + Shift + S&lt;/code&gt; stays intact for quick snips.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Convenience:&lt;/strong&gt; The isolated &lt;code&gt;PrintScreen&lt;/code&gt; key becomes a quick trigger for recording videos (Screencasts), which is great for tutorials or bug reporting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native Stability:&lt;/strong&gt; No need to install third-party apps that might fail or lag on the Wayland protocol.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Your screenshots will be automatically saved in &lt;code&gt;Pictures/Screenshots&lt;/code&gt; and will also be ready to paste anywhere with &lt;strong&gt;Ctrl + V&lt;/strong&gt;.&lt;/p&gt;

</description>
      <category>ubuntu</category>
      <category>shortcuts</category>
      <category>linux</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Fixing VS Code Installation Error on Ubuntu 26.04 (Resolute) via Terminal</title>
      <dc:creator>Sávio Eduardo Silva</dc:creator>
      <pubDate>Thu, 07 May 2026 15:03:52 +0000</pubDate>
      <link>https://dev.to/savioedu03/fixing-vs-code-installation-error-on-ubuntu-2604-resolute-via-terminal-2m1</link>
      <guid>https://dev.to/savioedu03/fixing-vs-code-installation-error-on-ubuntu-2604-resolute-via-terminal-2m1</guid>
      <description>&lt;h2&gt;
  
  
  The Problem: &lt;code&gt;apt-key&lt;/code&gt; is Deprecated and Repository is Unsigned
&lt;/h2&gt;

&lt;p&gt;When trying to install &lt;strong&gt;Visual Studio Code&lt;/strong&gt; on the new &lt;strong&gt;Ubuntu 26.04 LTS (Resolute)&lt;/strong&gt; using old tutorial methods, you will likely hit two roadblocks:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;code&gt;sudo: 'apt-key': command not found&lt;/code&gt; (The tool has been removed for security reasons).&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;The following signatures couldn't be verified... NO_PUBKEY EB3E94ADBE1229CF&lt;/code&gt; (Public key error).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This happens because Ubuntu now requires GPG keys (digital signatures) to be stored in standalone files within the &lt;code&gt;/etc/apt/keyrings/&lt;/code&gt; directory to ensure system integrity.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Solution: Manual Repository Configuration
&lt;/h2&gt;

&lt;p&gt;Follow these steps to correctly configure the Microsoft GPG key and repository.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Add the GPG Key
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;
bash
# Download the official Microsoft key and convert it to .gpg format
wget -qO- [https://packages.microsoft.com/keys/microsoft.asc](https://packages.microsoft.com/keys/microsoft.asc) | gpg --dearmor &amp;gt; packages.microsoft.gpg

# Move the key to the system's secure keyring folder
sudo install -D -o root -g root -m 644 packages.microsoft.gpg /etc/apt/keyrings/packages.microsoft.gpg

# Remove the temporary file
rm -f packages.microsoft.gpg
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

</description>
      <category>linux</category>
      <category>ubuntu</category>
      <category>vscode</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
