{"id":9187,"date":"2026-09-17T11:32:34","date_gmt":"2026-09-17T06:02:34","guid":{"rendered":"https:\/\/www.veeble.com\/kb\/?p=9187"},"modified":"2026-09-17T11:32:34","modified_gmt":"2026-09-17T06:02:34","slug":"fix-dpkg-frontend-lock-read-only-file-system","status":"publish","type":"post","link":"https:\/\/www.veeble.com\/kb\/fix-dpkg-frontend-lock-read-only-file-system\/","title":{"rendered":"Fix “Unable to Open\/Create dpkg Frontend Lock: Read-only File System” on Ubuntu and Debian"},"content":{"rendered":"\n
\"\"<\/a><\/figure>\n\n\n\n

When you install, update, or configure packages on Ubuntu or Debian, you may encounter an error similar to:<\/p>\n\n\n\n

dpkg: error: unable to open\/create dpkg frontend lock for directory \/var\/lib\/dpkg: Read-only file system<\/code><\/pre>\n\n\n\n
This error is different from the usual dpkg<\/code> lock error caused by another apt<\/code> process.<\/p>\n\n\n\n
In this case, dpkg<\/code> cannot create or modify its lock file because the filesystem containing \/var\/lib\/dpkg<\/code> is mounted as read-only.<\/p>\n\n\n\n
The filesystem may have been mounted read-only intentionally, or Linux may have changed it to read-only after detecting filesystem or storage errors. <\/p>\n\n\n
Before You Start<\/h2>\n\n\n
You should have:<\/p>\n\n\n\n
    \n
  • Root or sudo access<\/li>\n\n\n\n
  • A backup or VPS snapshot where possible<\/li>\n\n\n\n
  • Console or rescue access if this is a remote server<\/li>\n\n\n\n
  • Enough information to identify the affected filesystem<\/li>\n<\/ul>\n\n\n\n
    If this is a VPS or remote server, make sure you have access to the provider’s console before rebooting or repairing the filesystem. Filesystem recovery can make the server temporarily inaccessible through SSH.<\/p>\n\n\n
    Step 1: Check Which Filesystem Contains \/var\/lib\/dpkg<\/code><\/h2>\n\n\n
    Run:<\/p>\n\n\n\n
    findmnt -T \/var\/lib\/dpkg -o TARGET,SOURCE,FSTYPE,OPTIONS<\/code><\/pre>\n\n\n\n
    findmnt<\/code> can identify the filesystem containing a specific path and show its mount options.<\/p>\n\n\n\n
    Example:<\/p>\n\n\n\n
    TARGET SOURCE    FSTYPE OPTIONS\n\/      \/dev\/vda2 ext4   ro,relatime,errors=remount-ro<\/code><\/pre>\n\n\n\n
    Look at the OPTIONS<\/code> column.<\/p>\n\n\n\n
    If you see:<\/p>\n\n\n\n
    ro<\/code><\/pre>\n\n\n\n
    the filesystem is mounted read-only.<\/p>\n\n\n\n
    A normal writable filesystem should normally show:<\/p>\n\n\n\n
    rw<\/code><\/pre>\n\n\n\n
    Also note the SOURCE<\/code> and FSTYPE<\/code> values. You may need them later.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    SOURCE: \/dev\/vda2\nFSTYPE: ext4<\/code><\/pre>\n\n\n\n
    On an LVM-based server, the source may instead look similar to:<\/p>\n\n\n\n
    \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/code><\/pre>\n\n\n\n
    Do not run repair commands yet. First determine why the filesystem became read-only.<\/p>\n\n\n
    Step 2: Check for Filesystem and I\/O Errors<\/h2>\n\n\n
    Check recent kernel messages:<\/p>\n\n\n\n
    sudo dmesg -T | grep -Ei 'I\/O error|EXT4-fs|XFS|BTRFS|read-only|aborted journal|filesystem error' | tail -100<\/code><\/pre>\n\n\n\n
    You can also check the kernel journal:<\/p>\n\n\n\n
    sudo journalctl -k -b --no-pager | grep -Ei 'I\/O error|EXT4-fs|XFS|BTRFS|read-only|aborted journal|filesystem error' | tail -100<\/code><\/pre>\n\n\n\n
    Pay particular attention to messages such as:<\/p>\n\n\n\n
    EXT4-fs error<\/code><\/pre>\n\n\n\n
    Remounting filesystem read-only<\/code><\/pre>\n\n\n\n
    I\/O error<\/code><\/pre>\n\n\n\n
    Aborting journal<\/code><\/pre>\n\n\n\n
    These messages indicate that the read-only state may be a protection mechanism rather than a simple mount configuration problem.<\/p>\n\n\n\n
    For ext4, the filesystem can be configured to remount itself read-only after an error is detected.<\/p>\n\n\n\n
    If you see repeated I\/O errors, filesystem corruption, or an aborted journal, do not immediately continue installing packages. Skip to the filesystem repair section below.<\/p>\n\n\n
    Step 3: Check Whether the Filesystem Can Safely Be Remounted Read\/Write<\/h2>\n\n\n
    If the filesystem is read-only but the kernel logs do not show filesystem corruption or storage I\/O errors, you can try remounting it as read\/write.<\/p>\n\n\n\n
    First check the mount point again:<\/p>\n\n\n\n
    findmnt -no TARGET -T \/var\/lib\/dpkg<\/code><\/pre>\n\n\n\n
    On most Ubuntu and Debian installations, this will return:<\/p>\n\n\n\n
    \/<\/code><\/pre>\n\n\n\n
    In that case, run:<\/p>\n\n\n\n
    sudo mount -o remount,rw \/<\/code><\/pre>\n\n\n\n
    The remount,rw<\/code> option tells Linux to change an already mounted filesystem to read\/write mode.<\/p>\n\n\n\n
    If \/var\/lib\/dpkg<\/code> is on a separate \/var<\/code> filesystem, use its actual mount point instead:<\/p>\n\n\n\n
    sudo mount -o remount,rw \/var<\/code><\/pre>\n\n\n\n
    Do not blindly use \/var<\/code>. Use the mount point reported by findmnt<\/code>.<\/p>\n\n\n\n
    Check the result:<\/p>\n\n\n\n
    findmnt -T \/var\/lib\/dpkg -o TARGET,SOURCE,FSTYPE,OPTIONS<\/code><\/pre>\n\n\n\n
    If the options now contain:<\/p>\n\n\n\n
    rw<\/code><\/pre>\n\n\n\n
    the filesystem is writable again.<\/p>\n\n\n\n
    You can then continue to the section Repair the Interrupted dpkg Operation<\/strong>.<\/p>\n\n\n
    If the Remount Fails<\/h3>\n\n\n
    You may receive an error similar to:<\/p>\n\n\n\n
    mount: \/: cannot remount \/dev\/vda2 read-write, is write-protected<\/code><\/pre>\n\n\n\n
    or the filesystem may continue to show ro<\/code>.<\/p>\n\n\n\n
    Do not repeatedly force the remount.<\/p>\n\n\n\n
    Check the kernel logs again. A filesystem that refuses to return to read\/write mode may require an offline filesystem check, or the underlying storage may have a problem.<\/p>\n\n\n
    Step 4: Check \/etc\/fstab<\/code><\/h2>\n\n\n
    A filesystem may also be intentionally configured as read-only.<\/p>\n\n\n\n
    View the active entries in \/etc\/fstab<\/code>:<\/p>\n\n\n\n
    grep -Ev '^[[:space:]]*(#|$)' \/etc\/fstab<\/code><\/pre>\n\n\n\n
    Look at the entry for the affected filesystem.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    UUID=xxxx-xxxx \/ ext4 defaults 0 1<\/code><\/pre>\n\n\n\n
    A normal root filesystem generally should not be explicitly configured with the ro<\/code> option for regular operation.<\/p>\n\n\n\n
    If you find an unexpected ro<\/code> option, verify why it was added before changing it.<\/p>\n\n\n\n
    Do not modify \/etc\/fstab<\/code> simply because the filesystem became read-only after an error. If the kernel changed the filesystem to read-only because of corruption, changing \/etc\/fstab<\/code> will not repair it.<\/p>\n\n\n
    Step 5: Repair an ext4 Filesystem<\/h2>\n\n\n
    If the logs show ext4 filesystem errors, or the filesystem cannot be remounted read\/write, an offline filesystem check may be required.<\/p>\n\n\n\n
    First identify the filesystem again:<\/p>\n\n\n\n
    findmnt -T \/var\/lib\/dpkg -o TARGET,SOURCE,FSTYPE,OPTIONS<\/code><\/pre>\n\n\n\n
    Suppose it shows:<\/p>\n\n\n\n
    \/dev\/vda2<\/code><\/pre>\n\n\n\n
    with:<\/p>\n\n\n\n
    ext4<\/code><\/pre>\n\n\n\n
    Do not run fsck.ext4<\/code> against the mounted root filesystem.<\/p>\n\n\n\n
    The official e2fsck<\/code> documentation warns that checking a mounted ext2, ext3, or ext4 filesystem is generally unsafe and that its results may not be valid while the filesystem is mounted.<\/p>\n\n\n
    Option 1: Use Ubuntu Recovery Mode<\/h3>\n\n\n
    If GRUB recovery mode is available:<\/p>\n\n\n\n
      \n
    1. Reboot the server or computer.<\/li>\n\n\n\n
    2. Open the GRUB menu.<\/li>\n\n\n\n
    3. Select Advanced options for Ubuntu<\/strong>.<\/li>\n\n\n\n
    4. Select a kernel entry marked recovery mode<\/strong>.<\/li>\n\n\n\n
    5. Choose the filesystem check option.<\/li>\n<\/ol>\n\n\n\n
      Ubuntu’s recovery environment provides an fsck<\/code> option specifically for checking the filesystem.<\/p>\n\n\n\n
      For a VPS, the hosting provider’s rescue environment or recovery console may be easier to use.<\/p>\n\n\n
      Option 2: Use a Rescue or Live Environment<\/h3>\n\n\n
      Boot the server using a rescue system or live environment.<\/p>\n\n\n\n
      Confirm that the affected filesystem is not mounted.<\/p>\n\n\n\n
      Then run the filesystem check against the correct device.<\/p>\n\n\n\n
      For example:<\/p>\n\n\n\n
      sudo fsck.ext4 -f \/dev\/vda2<\/code><\/pre>\n\n\n\n
      Replace \/dev\/vda2<\/code> with the actual device shown by findmnt<\/code>.<\/p>\n\n\n\n
      For an LVM filesystem, it may look similar to:<\/p>\n\n\n\n
      sudo fsck.ext4 -f \/dev\/mapper\/ubuntu--vg-ubuntu--lv<\/code><\/pre>\n\n\n\n
      fsck.ext4<\/code> will inspect the filesystem and ask before repairing detected problems.<\/p>\n\n\n\n
      Do not copy a device name from an example. Running filesystem repair against the wrong partition can damage data.<\/p>\n\n\n
      Avoid Using -y<\/code> Unless Necessary<\/h3>\n\n\n
      You may see guides recommending:<\/p>\n\n\n\n
      fsck.ext4 -f -y \/dev\/vda2<\/code><\/pre>\n\n\n\n
      The -y<\/code> option automatically answers yes to all repair questions.<\/p>\n\n\n\n
      Although this can be useful in some recovery situations, it removes your ability to review the changes. Ubuntu’s filesystem troubleshooting documentation warns that non-interactive repairs can be potentially dangerous and recommends having a backup where possible.<\/p>\n\n\n
      What If the Filesystem Is XFS?<\/h2>\n\n\n
      Check the filesystem type:<\/p>\n\n\n\n
      findmnt -no FSTYPE -T \/var\/lib\/dpkg<\/code><\/pre>\n\n\n\n
      If the result is:<\/p>\n\n\n\n
      xfs<\/code><\/pre>\n\n\n\n
      do not use fsck.ext4<\/code>.<\/p>\n\n\n\n
      XFS uses xfs_repair<\/code>.<\/p>\n\n\n\n
      From a rescue environment with the filesystem unmounted:<\/p>\n\n\n\n
      sudo xfs_repair \/dev\/vda2<\/code><\/pre>\n\n\n\n
      Replace \/dev\/vda2<\/code> with the actual XFS device.<\/p>\n\n\n\n
      The XFS documentation requires the filesystem to be unmounted before using xfs_repair<\/code>.<\/p>\n\n\n\n
      If the filesystem is Btrfs or another filesystem type, use the repair procedure designed specifically for that filesystem. Do not run ext4 or XFS repair tools against it.<\/p>\n\n\n
      Step 6: Reboot and Verify the Filesystem<\/h2>\n\n\n
      After repairing the filesystem, boot the server normally.<\/p>\n\n\n\n
      Check the mount again:<\/p>\n\n\n\n
      findmnt -T \/var\/lib\/dpkg -o TARGET,SOURCE,FSTYPE,OPTIONS<\/code><\/pre>\n\n\n\n
      Confirm that the affected filesystem now contains:<\/p>\n\n\n\n
      rw<\/code><\/pre>\n\n\n\n
      instead of:<\/p>\n\n\n\n
      ro<\/code><\/pre>\n\n\n\n
      Check the kernel logs again:<\/p>\n\n\n\n
      sudo dmesg -T | grep -Ei 'I\/O error|EXT4-fs|XFS|BTRFS|read-only|aborted journal|filesystem error' | tail -100<\/code><\/pre>\n\n\n\n
      If filesystem or I\/O errors immediately return, stop package operations and investigate the underlying storage.<\/p>\n\n\n\n
      Repeated filesystem corruption can indicate a storage device, virtual disk, RAID, filesystem, or host infrastructure problem.<\/p>\n\n\n\n
      On a VPS, recurring I\/O errors may require investigation from the hosting provider because the physical storage is normally managed by the host system.<\/p>\n\n\n
      Step 7: Repair the Interrupted dpkg<\/code> Operation<\/h2>\n\n\n
      Once the filesystem is confirmed writable, repair any packages that were left partially configured.<\/p>\n\n\n\n
      Run:<\/p>\n\n\n\n
      sudo dpkg --configure -a<\/code><\/pre>\n\n\n\n
      The --configure -a<\/code> option tells dpkg<\/code> to configure packages that have been unpacked but are still waiting to be configured.<\/p>\n\n\n\n
      Next, repair broken package dependencies:<\/p>\n\n\n\n
      sudo apt-get -f install<\/code><\/pre>\n\n\n\n
      The -f<\/code> or --fix-broken<\/code> option asks APT to attempt to correct broken dependencies.<\/p>\n\n\n\n
      Then refresh the package lists:<\/p>\n\n\n\n
      sudo apt update<\/code><\/pre>\n\n\n\n
      Finally, check the package state:<\/p>\n\n\n\n
      sudo apt-get check<\/code><\/pre>\n\n\n\n
      If these commands complete without the read-only error, the dpkg<\/code> problem has been resolved.<\/p>\n\n\n\n
      You can now retry the installation or upgrade that originally failed.<\/p>\n\n\n
      Do Not Delete the dpkg Lock File for This Error<\/h2>\n\n\n
      A common solution for package-manager lock problems is to remove files such as:<\/p>\n\n\n\n
      \/var\/lib\/dpkg\/lock<\/code><\/pre>\n\n\n\n
      or:<\/p>\n\n\n\n
      \/var\/lib\/dpkg\/lock-frontend<\/code><\/pre>\n\n\n\n
      That is not the correct first response to:<\/p>\n\n\n\n
      Read-only file system<\/code><\/pre>\n\n\n\n
      The lock file is not the root cause.<\/p>\n\n\n\n
      If the filesystem is mounted read-only, dpkg<\/code> cannot write to \/var\/lib\/dpkg<\/code> regardless of whether the lock file exists.<\/p>\n\n\n\n
      Removing lock files also carries additional risk if another package-management process is genuinely running.<\/p>\n\n\n\n
      If your error instead says:<\/p>\n\n\n\n
      Unable to acquire the dpkg frontend lock<\/code><\/pre>\n\n\n\n
      or:<\/p>\n\n\n\n
      Permission denied<\/code><\/pre>\n\n\n\n
      without the Read-only file system<\/code> message, that is a different problem and should be diagnosed as a normal package-manager lock or permission issue.<\/p>\n\n\n
      Troubleshooting<\/h2>\n\n
      The Root Filesystem Shows rw<\/code>, but dpkg Still Says Read-only<\/h3>\n\n\n
      Do not check only \/<\/code>.<\/p>\n\n\n\n
      Run:<\/p>\n\n\n\n
      findmnt -T \/var\/lib\/dpkg -o TARGET,SOURCE,FSTYPE,OPTIONS<\/code><\/pre>\n\n\n\n
      \/var<\/code>, \/var\/lib<\/code>, or another parent directory may be located on a separate filesystem that is still read-only.<\/p>\n\n\n\n
      Diagnose the filesystem that actually contains \/var\/lib\/dpkg<\/code>.<\/p>\n\n\n
      mount -o remount,rw \/<\/code> Does Not Work<\/h3>\n\n\n
      Check:<\/p>\n\n\n\n
      sudo dmesg -T | tail -100<\/code><\/pre>\n\n\n\n
      and:<\/p>\n\n\n\n
      sudo journalctl -k -b --no-pager | tail -100<\/code><\/pre>\n\n\n\n
      If you see filesystem or I\/O errors, perform an offline filesystem check instead of repeatedly attempting the remount.<\/p>\n\n\n
      fsck<\/code> Says the Filesystem Is Mounted<\/h3>\n\n\n
      Stop, do not force a repair against the mounted root filesystem.<\/p>\n\n\n\n
      Boot into recovery mode, a rescue environment, or a live system so the affected filesystem can be checked while unmounted.<\/p>\n\n\n
      The Filesystem Becomes Read-only Again After Reboot<\/h3>\n\n\n
      This normally means the original problem has not been resolved.<\/p>\n\n\n\n
      Check for:<\/p>\n\n\n\n
        \n
      • I\/O errors<\/li>\n\n\n\n
      • Filesystem corruption<\/li>\n\n\n\n
      • Failed or unstable storage<\/li>\n\n\n\n
      • RAID problems<\/li>\n\n\n\n
      • Virtual disk or hypervisor storage issues<\/li>\n\n\n\n
      • Unexpected shutdowns<\/li>\n<\/ul>\n\n\n\n
        Take a current backup before continuing if the filesystem is still readable.<\/p>\n\n\n
        There Are No Filesystem Errors, but the Disk Is Full<\/h3>\n\n\n
        A full filesystem normally produces errors such as:<\/p>\n\n\n\n
        No space left on device<\/code><\/pre>\n\n\n\n
        rather than:<\/p>\n\n\n\n
        Read-only file system<\/code><\/pre>\n\n\n\n
        Check disk space with:<\/p>\n\n\n\n
        df -h<\/code><\/pre>\n\n\n\n
        and inode usage with:<\/p>\n\n\n\n
        df -i<\/code><\/pre>\n\n\n\n
        Treat a full disk as a separate problem instead of assuming it caused the filesystem to become read-only.<\/p>\n\n\n
        Conclusion<\/h2>\n\n\n
        The error:<\/p>\n\n\n\n
        dpkg: error: unable to open\/create dpkg frontend lock for directory \/var\/lib\/dpkg: Read-only file system<\/code><\/pre>\n\n\n\n
        is primarily a filesystem problem, not a dpkg<\/code> lock problem.<\/p>\n\n\n\n
        First identify the filesystem containing \/var\/lib\/dpkg<\/code>, confirm whether it is mounted read-only, and check the kernel logs for filesystem or I\/O errors. A simple remount may be enough if the filesystem is healthy, but filesystem errors should be repaired offline using the correct tool for the filesystem type.<\/p>\n\n\n\n
        Only after the filesystem is writable again should you repair the interrupted package state with:<\/p>\n\n\n\n
        sudo dpkg --configure -a\nsudo apt-get -f install<\/code><\/pre>\n\n\n\n
        This fixes the package state after addressing the actual cause of the error.<\/p>\n\n\n\n
        <\/p>\n","protected":false},"excerpt":{"rendered":"
        When you install, update, or configure packages on Ubuntu or Debian, you may encounter an error similar to: This error is different from the […]<\/p>\n","protected":false},"author":15,"featured_media":9192,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[5],"tags":[116,114,113,117,120,67,119,115,98],"class_list":["post-9187","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux","tag-apt","tag-debian","tag-dpkg","tag-dpkg-frontend-lock","tag-fsck","tag-linux","tag-package-manager","tag-read-only-file-system","tag-ubuntu"],"uagb_featured_image_src":{"full":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1.jpg",1672,941,false],"thumbnail":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1-150x150.jpg",150,150,true],"medium":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1-300x169.jpg",300,169,true],"medium_large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1-768x432.jpg",768,432,true],"large":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1-1024x576.jpg",1024,576,true],"1536x1536":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1-1536x864.jpg",1536,864,true],"2048x2048":["https:\/\/www.veeble.com\/kb\/wp-content\/uploads\/2026\/09\/Unable-to-OpenCreate-dpkg-Frontend-Lock-1.jpg",1672,941,false]},"uagb_author_info":{"display_name":"Nasarul Naseer","author_link":"https:\/\/www.veeble.com\/kb\/author\/nasarulnaseer\/"},"uagb_comment_info":0,"uagb_excerpt":"When you install, update, or configure packages on Ubuntu or Debian, you may encounter an error similar to: This error is different from the […]","_links":{"self":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9187","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/users\/15"}],"replies":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/comments?post=9187"}],"version-history":[{"count":5,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9187\/revisions"}],"predecessor-version":[{"id":9194,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/posts\/9187\/revisions\/9194"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media\/9192"}],"wp:attachment":[{"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/media?parent=9187"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/categories?post=9187"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.veeble.com\/kb\/wp-json\/wp\/v2\/tags?post=9187"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}