<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ubuntu on Development notes</title>
    <link>https://dev-pages.info/tags/ubuntu/</link>
    <description>Recent content in ubuntu on Development notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sat, 17 Jul 2021 22:02:49 +0300</lastBuildDate><atom:link href="https://dev-pages.info/tags/ubuntu/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to fix Permission denied (publickey) error</title>
      <link>https://dev-pages.info/how-to-fix-permission-denied-publickey-error/</link>
      <pubDate>Sat, 17 Jul 2021 22:02:49 +0300</pubDate>
      
      <guid>https://dev-pages.info/how-to-fix-permission-denied-publickey-error/</guid>
      <description>&lt;p&gt;This blog post describes how to fix &amp;ldquo;Permission denied (publickey)&amp;rdquo; error while logging in via ssh using a public key.&lt;/p&gt;
&lt;p&gt;Ensure you have access to the server via Web console, like Quemu Terminal on Digital Ocean, or have physical access to the server.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Ubuntu: How to fix the error &#39;essential package ubuntu-minimal could not be located&#39;</title>
      <link>https://dev-pages.info/ubuntu-fix-essential-package-error/</link>
      <pubDate>Mon, 07 Jun 2021 00:26:44 +0300</pubDate>
      
      <guid>https://dev-pages.info/ubuntu-fix-essential-package-error/</guid>
      <description>&lt;p&gt;I got the error related to the &lt;code&gt;Invalid package information. the essential package &#39;ubuntu-minimal&#39; could not be located&lt;/code&gt; while upgrading Ubuntu 16.04 to the next version.&lt;/p&gt;
&lt;p&gt;This blog post describes how to fix such an error on the Digital Ocean droplet.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Ubuntu: How to fix Virtual Box Vboxdrv Error</title>
      <link>https://dev-pages.info/ubuntu-how-to-fix-virtual-box-vboxdrv-error/</link>
      <pubDate>Thu, 09 Apr 2020 22:26:53 +0300</pubDate>
      
      <guid>https://dev-pages.info/ubuntu-how-to-fix-virtual-box-vboxdrv-error/</guid>
      <description>&lt;p&gt;While running &lt;code&gt;sudo /sbin/vboxconfig&lt;/code&gt; the following error may occur:&lt;/p&gt;
&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-bash&#34; data-lang=&#34;bash&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;vboxdrv.sh: Stopping VirtualBox services.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;vboxdrv.sh: Starting VirtualBox services.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;vboxdrv.sh: Building VirtualBox kernel modules.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;There were problems setting up VirtualBox.  To re-start the set-up process, run
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;  /sbin/vboxconfig
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;as root.  If your system is using EFI Secure Boot you may need to sign the
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;kernel modules &lt;span style=&#34;color:#f92672&#34;&gt;(&lt;/span&gt;vboxdrv, vboxnetflt, vboxnetadp, vboxpci&lt;span style=&#34;color:#f92672&#34;&gt;)&lt;/span&gt; before you can load
&lt;/span&gt;&lt;/span&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt; them. Please see your Linux system&lt;span style=&#34;color:#960050;background-color:#1e0010&#34;&gt;&amp;#39;&lt;/span&gt;s documentation &lt;span style=&#34;color:#66d9ef&#34;&gt;for&lt;/span&gt; more information.
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;To fix it, run the following command:&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Tuxguitar No Sound</title>
      <link>https://dev-pages.info/tuxguitar-no-sound/</link>
      <pubDate>Fri, 21 Jun 2019 21:36:27 +0300</pubDate>
      
      <guid>https://dev-pages.info/tuxguitar-no-sound/</guid>
      <description>In case if there is no sound in TuxGuitar in linux, do the following
1 Install package tuxguitar-jsa
sudo apt install tuxguitar-jsa 2 Update MIDI port into TuxGuitar settings
Go to Tools -&amp;gt; Settings. A new window with TexGuitar configs will be opened. Find Sound section and change MIDI port to Gervill:
Close Settings window and verify everything works fine.</description>
    </item>
    
    <item>
      <title>Linux: how to make Bluetooth working</title>
      <link>https://dev-pages.info/ubuntu-bluetooth/</link>
      <pubDate>Mon, 06 Nov 2017 13:00:49 +0000</pubDate>
      
      <guid>https://dev-pages.info/ubuntu-bluetooth/</guid>
      <description>This post describes step by step solution of how to make Bluetooth working on Lenovo V580c in linux distributions: Ubuntu 17.10 and Manjero 2017. My Lenovo laptop uses BCM43142 chipset.
Find bluetoth chipset and device ID First of all we need to make sure that we have appropriate Chipset. Open terminal and enter the following command:
lsusb | grep Bluetooth The output will look like:
Bus 001 Device 004: ID 105b:e065 Foxconn International, Inc.</description>
    </item>
    
  </channel>
</rss>
