Differences

This shows you the differences between two versions of the page.

--- linux [2018/05/16 18:15] – [Linux notes] rfile
+++ linux [2018/05/29 11:49] (current) – [youtube downloader] rfile
@@ Line 392: / Line 392: @@
 https://www.asus.com/US/support/faq/1013998/
-===== Laptop =====
-Acer-Extensa-5620Z-Laptop
+===== fedora robotics =====
-Intel Pentium Dual Core T2330
+Notes for later from live iso
-https://www.notebookcheck.net/Intel-Pentium-Dual-Core-Processor.14045.0.html
+https://fedoraproject.org/wiki/Robotics
-https://www.notebookcheck.net/Intel-Graphics-Media-Accelerator-X3100.2176.0.html
+===== youtube downloader =====
-<note tip>
-from [[http://distro.ibiblio.org/fatdog/web/faqs/intel-graphics.html|fat dog faq]]
-Desktop takes a long time to show up after booting up
+[[https://lubuntuhowto.blogspot.co.id/2017/11/how-to-install-youtube-dl-on-lubuntu-1710.html| youtube downloader]]
-On certain machines with old Intel graphic chips, it may take a relatively long time (can be up to a few minutes) for the desktop to show up, after an apparently successful text-mode boot up.
-There are many possible causes for this, but one of the most frequent one is because the kernel driver is trying to activate the S-VIDEO interface, which in reality may not even be connected to anything in your machine.
+===== dpkg lock =====
-To fix this, you need to tell the kernel to disable S-VIDEO interface. This is done by putting the following **boot parameter: video=SVIDEO-1:d**
-in your boot loader entry.</note>
-https://bugs.freedesktop.org/show_bug.cgi?id=93782
-http://distro.ibiblio.org/fatdog/web/faqs/intel-graphics.html
-<note>
-errors from laptop
-[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:35:plane B] flip_done timed out
-[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:41:pipe B] flip_done timed out
-Then add the kernel boot parameter: video=SVIDEO-1:d, so it will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"
-note that the above seems to have worked... 5-16-18
-</note>
-===== fedora robotics =====
-Notes for later from live iso
-https://fedoraproject.org/wiki/Robotics
+look for it:
+<code bash>
+sudo lsof /var/lib/dpkg/lock
+</code>
+kill it:
+<code bash>
+kill -9 <PID> (get <PID> from lsof output
+</code>
+[[https://help.ubuntu.com/community/PackageManagerTroubleshootingProcedure|package manager troubleshooting]]