hello evrybdy i have old 3rd gen Asus k55vj laptop with core i5 3rd gen, intel 4000 hd graphics with 8 gb ram and a gt 635 m dgpu ...i want to install ubuntu 25.10 as windows is unable to detect my dgpu and the laptop fans r spinning at max speed even though there is no processes or cpu stress...but during installation of ubuntu i get stucked on the welcome wallpaper not even getting the option of choosing he language ..i again restarted in safe mode and successfully installed ubuntu in safe mode but after installation it asked me to remove the drive and press enter but failed to start the newly installed ubuntu 25.10...how to resolve this i know the dgpu of mine is failed card as it is old pls do help me to get rid of fan noise save my laptop ????

Attention! Some of your past questions have not been well-received. You're in danger of being blocked from asking any more..

For help formulating a clear, useful question, see: How do I ask a good question?

Also, edit your previous questions to improve formatting and clarity.

Very RUDE! Go ahead and block me. Why would I ask for your help?

I thought something felt off in my Hardware Info when I was writing this, but I couldn't pin down what until I looked at an older question with my info on it. Somehow and I don't know how but, I'd assume it's not helping (if it isn't the main cause for overheating all the sudden), my graphics have gone from listing "AMD Radeon RX 7900 XT" and "AMD Ryzen 7 7800X3D" to only listing "Software Rendering". If anyone knows what could cause this and how to fix it, I would be grateful.

Nothing has changed much since I got my computer up and running for the semester. The only thing I can think of is that I let it run an update a day or so ago, but all of the sudden my computer is running so hot doing things like browsing the web and checking my Discord notifications that I can't use it for more than 30 minutes at a time without one of the sensors hitting an ALARM (HIGH) report when running sensors in the terminal.

Basic specs are below and the current temperature at the moment. Usually it'd go to +70° C but I've taken off one of the PC's side panels just to vent the heat. It's a small form factor, so I do expect hit to get pretty hot, but never before for just regular day-to-day use. Help is much appreciated, as I'd like to not worry about her overheating and causing permanent damage while in college.

spd5118-i2c-2-51  
Adapter: SMBus PIIX4 adapter port 0 at 0b00 
temp1:         +56.8 degrees C (low = +0.0 degrees C, high = +55.0 degrees C) ALARM (HIGH) 
                               (crit low = +0.0 degrees C, crit = +85 degrees C)

I'm also unsure if it'd help, but here's a look at the System Monitor at the moment.

The CPU seems that it isn't be overloaded (I've had an issue with that before, but it appeared to be a power issue possibly, as moving and using a different plug made that problem disappear), with the most CPU usage being the Gnome Shell, so I'm unsure what's going on that's causing it to overheat.

I have tried to format it, but all the buttons are gray and using the cmd prompt isn't working either. I followed someone else's guide and it did nothing.

In the last week, after some update, either firmware or Ubuntu update, the backspace and Enter buttons don't work after I open the lip of the laptop. I can't figure out the incantation that will make those buttons work so that I can login.

Sometimes Fn+F7 makes it work, sometimes just waiting 2 minutes, sometimes it's Ctrl+F7, etc. I've tried a few and mostly can repeat the sequence. The buttons work perfectly after logging in or after a reboot, so something in the suspend or resume is locking up these keys. Do you have any idea on how to diagnose this so I can reply with better detail, or ideas on how to fix it?

I wanted to reset my computer to my old Windows image but both boot and bios ask for a password. The only password that I had to set for Ubuntu fails, and I have never previously seen any mention of passwords in either menu during Windows use. I tried Ubuntu having seen so many reports of it revitalising old computers, being less taxing than Windows and suitable for my Steam games. Nope, nope and nope. Windows was laggy but things actually opened and worked, for a while at least. A new pc is/was pending, regardless, but whereas the old one could have been used with Windows to some degree, it seems now to be a paperweight. I got excited about joining the exodus, but now I'm really sad that I'll be funding killy Billy again....

Hi everyone,

I’m currently running Ubuntu 22.04 LTS and the system is prompting me to upgrade to 24.04.3. Before I proceed, I’d like to gather some feedback, especially regarding compatibility with my graphics setup. My GPU is an NVIDIA GeForce GTX 660 (GK106), identified by lspci as: 23:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] (rev a1) I use two monitors connected to this card, and it’s crucial for me that both continue to work seamlessly after the upgrade.

My questions:

Are the NVIDIA drivers (proprietary or open-source) for this GPU well-supported on Ubuntu 24.04.3? Are there any known issues with multi-monitor setups on this version, particularly with NVIDIA cards of this generation? Does the upgrade bring significant improvements to justify the switch, or should I stick with 22.04 LTS to avoid potential compatibility issues? Thanks in advance for your advice and experiences!

Trying to create a cron job to do weekly backups, but I'm creating simple test to make sure the cron job works before I put in the actual commands.

This is what I added to crontab:

*/2 * * * * /etc/cron.weekly/Backup.sh

The contents of /etc/cron.weekly/Backup.sh is:

#!/bin/bash

echo "Hello cruel world!" >> home/chris/Desktop/Output.txt 2>&1  

Backup.sh is executable

grep CRON /var/log/syslog produces the following (I've included the relevant lines):

2026-01-17T08:14:01.997430-05:00 Goliath CRON\[2747194\]: (root) CMD (/etc/cron.weekly/Backup.sh)

2026-01-17T08:14:01.997976-05:00 Goliath CRON\[2747195\]: (chris) CMD (/etc/cron.weekly/Backup.sh)

I'm expecting a text file to appear on my desktop with either the words "Hello, cruel world!" or some kind of error message added to it every 2 minutes. Instead I get nothing.

I have a dashboard from Home Assistant and would like it to be shown as the desktop wallpaper/background using some web web browser (Firefox, Chromium) in kiosk mode.

How would I tell my Ubuntu 24.04/Wayland/Gnome to automatically start that browser upon user login and run it as desktop wallpaper?

I checked gnome dynamic wallpaper resources and found:

• https://itsfoss.gitlab.io/post/add-dynamic-wallpapers-to-your-gnome-desktop/ only allows to display images
• https://extensions.gnome.org/extension/1040/random-wallpaper/ only allows to display images
• https://github.com/jeffshee/gnome-ext-hanabi only allows to display a video
• https://linuxconfig.org/how-to-create-gnome-dynamic-wallpapers only allows to display images

I remember years before Gnome came up it was possible to start application such that they would run in the root or desktop window - such as xearth, xroach and xsnow used to do.

On Software Updater's 'Software & Updates', under 'updates', I've selected 'never*' on the 'subscribe to', but security updates still keep popping up and often lock up the computer while I'm in the middle of something processor intensive, requiring holding down the power button.

I made a script to kill packagekitd (sudo systemctl stop packagekit.service), but it will reload itself and I still have to keep launching the script until it finally just quits and I can move on. It seems things like apt-check, etc. keep triggering it.

I would rather just manually do updates say once every week or two, maybe just once a month - all updates - the serious ones, security ones, and all.

Is there any way to just make it do all updates manually, other than uninstall the Software Updater app and just open terminal to use command like apt-get update, apt-get upgrade, etc.?

/etc/apt/apt.conf.d/50unattended-upgrades:

// Automatically upgrade packages from these (origin:archive) pairs
//
// Note that in Ubuntu security updates may pull in new dependencies
// from non-security sources (e.g. chromium). By allowing the release
// pocket these get automatically pulled in.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps: ${distro_codename}-apps-security";
"${distro_id}ESM: ${distro_codename}-infra-security";
//  "${distro_id}:${distro_codename}-updates";
//  "${distro_id}:${distro_codename}-proposed";
//  "${distro_id}:${distro_codename}-backports";
};

// Python regular expressions, matching packages to exclude from upgrading
Unattended-Upgrade::Package-Blacklist {
// The following matches all packages starting with linux-
//  "linux-";

// Use $ to explicitely define the end of a package name. Without
// the $, "libc6" would match all of them.
//  "libc6$";
//  "libc6-dev$";
//  "libc6-i686$";

// Special characters need escaping
//  "libstdc\+\+6$";

// The following matches packages like xen-system-amd64, xen-utils-4.1,
// xenstore-utils and libxenstore3.0
//  "(lib)?xen(store)?";

// For more information about Python regular expressions, see
// https://docs.python.org/3/howto/regex.html};

// This option controls whether the development release of Ubuntu will be
// upgraded automatically. Valid values are "true", "false", and "auto".
Unattended-Upgrade::DevRelease "auto";

// This option allows you to control if on a unclean dpkg exit
// unattended-upgrades will automatically run 
//   dpkg --force-confold --configure -a
// The default is true, to ensure updates keep getting installed
//Unattended-Upgrade::AutoFixInterruptedDpkg "true";

// Split the upgrade into the smallest possible chunks so that
// they can be interrupted with SIGTERM. This makes the upgrade
// a bit slower but it has the benefit that shutdown while a upgrade
// is running is possible (with a small delay)
//Unattended-Upgrade::MinimalSteps "true";

// Install all updates when the machine is shutting down
// instead of doing it in the background while the machine is running.
// This will (obviously) make shutdown slower.
// Unattended-upgrades increases logind's InhibitDelayMaxSec to 30s.
// This allows more time for unattended-upgrades to shut down gracefully
// or even install a few packages in InstallOnShutdown mode, but is still a
// big step back from the 30 minutes allowed for InstallOnShutdown previously.
// Users enabling InstallOnShutdown mode are advised to increase
// InhibitDelayMaxSec even further, possibly to 30 minutes.
//Unattended-Upgrade::InstallOnShutdown "false";

// Send email to this address for problems or packages upgrades
// If empty or unset then no email is sent, make sure that you
// have a working mail setup on your system. A package that provides
// 'mailx' must be installed. E.g. "user@example.com"
//Unattended-Upgrade::Mail "";

// Set this value to one of:
//    "always", "only-on-error" or "on-change"
// If this is not set, then any legacy MailOnlyOnError (boolean) value
// is used to chose between "only-on-error" and "on-change"
//Unattended-Upgrade::MailReport "on-change";

// Remove unused automatically installed kernel-related packages
// (kernel images, kernel headers and kernel version locked tools).
//Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

// Do automatic removal of newly unused dependencies after the upgrade
//Unattended-Upgrade::Remove-New-Unused-Dependencies "true";

// Do automatic removal of unused packages after the upgrade
// (equivalent to apt-get autoremove)
//Unattended-Upgrade::Remove-Unused-Dependencies "false";

// Automatically reboot *WITHOUT CONFIRMATION* if
//  the file /var/run/reboot-required is found after the upgrade
//Unattended-Upgrade::Automatic-Reboot "false";

// Automatically reboot even if there are users currently logged in
// when Unattended-Upgrade::Automatic-Reboot is set to true
//Unattended-Upgrade::Automatic-Reboot-WithUsers "true";

// If automatic reboot is enabled and needed, reboot at the specific
// time instead of immediately
//  Default: "now"
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";

// Use apt bandwidth limit feature, this example limits the download
// speed to 70kb/sec
//Acquire::http::Dl-Limit "70";

// Enable logging to syslog. Default is False
// Unattended-Upgrade::SyslogEnable "false";

// Specify syslog facility. Default is daemon
// Unattended-Upgrade::SyslogFacility "daemon";

// Download and install upgrades only on AC power
// (i.e. skip or gracefully stop updates on battery)
// Unattended-Upgrade::OnlyOnACPower "true";

// Download and install upgrades only on non-metered connection
// (i.e. skip or gracefully stop updates on a metered connection)
// Unattended-Upgrade::Skip-Updates-On-Metered-Connections "true";

// Verbose logging
// Unattended-Upgrade::Verbose "false";

// Print debugging information both in unattended-upgrades and
// in unattended-upgrade-shutdown
// Unattended-Upgrade::Debug "false";

// Allow package downgrade if Pin-Priority exceeds 1000
// Unattended-Upgrade::Allow-downgrade "false";

// When APT fails to mark a package to be upgraded or installed try adjusting
// candidates of related packages to help APT's resolver in finding a solution
// where the package can be upgraded or installed.
// This is a workaround until APT's resolver is fixed to always find a
// solution if it exists. (See Debian bug #711128.)
// The fallback is enabled by default, except on Debian's sid release because
// uninstallable packages are frequent there.
// Disabling the fallback speeds up unattended-upgrades when there are
// uninstallable packages at the expense of rarely keeping back packages which
// could be upgraded or installed.
// Unattended-Upgrade::Allow-APT-Mark-Fallback "true";

/etc/apt/apt.conf.d/10periodic:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";

/etc/apt/apt.conf.d/20auto-upgrades:

APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Download-Upgradeable-Packages "0";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";

...the Software Updater has an option to select 'NEVER' for Automatically Check for Updates, but not for When there are Security Updates ~ the ONLY choices are 'DISPLAY...' or 'DOWNLOAD...'... and it does so right in the middle of my work :-(

Unlike Can only boot Ubuntu 20.04.1 LTS when holding shift, I have Ubuntu 24.04.3 running on a HDD with the CPU being an AMD Ryzen 5 7600X.

Going into GRUB and then into Recovery Mode, seems to be the only way to boot all the way to desktop consistently.

Latest Recovery had black sections before I moved the selected options over them. Maybe it works is also related to how the resolution becomes 1024 x 768.

And even when I get GRUB, rarely, using the "Ubuntu" option boots fine. Holding down Shift during the boot logo might actually do something useful, or might just be me making a false cause fallacy.

Unlike the linked question's answer, my sudo nano /etc/default/grub reads:

> GRUB_DEFAULT=0  
GRUB_TIMEOUT_STYLE=hidden  
GRUB_TIMEOUT=0  
GRUB_DISTRIBUTOR=`( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu`  
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"  
GRUB_CMDLINE_LINUX=""

Is it because I have quad boot options on my GRUB? Ubuntu, Advanced, Memory Tests, then Windows 10, XP, and another XP spread out over 3 HDDs. They're all on Legacy, but I'm always just trying to boot into Ubuntu.

I bet it's more due to graphics related stuff that flickers my screen as the boot logo screen adjusts to fit my monitor. My card and monitor are really old, (NVIDIA GT 220 connecting to a Hanns.G HG-216D), but it does that no matter if I go to GRUB, although the screen doesn't tear if I actually get to see the GRUB menu.

It seems even just getting to GRUB isn't a total fix. Did a sudo shutdown -r now from a successful boot to get to GRUB, left it on GRUB for a while while typing most of this out, picked Ubuntu, and the screen didn't tear, but there's still a black screen after the boot logo.

A mention of VGA GPU in the boot logs of the "failed" boot clued me in to take a guess, and it seems like it works after unplugging the VGA.

Or at least it worked once, and then not again-ish. Still probably a graphics issue, but gnome / Ubuntu just can't seem to settle on always using HDMI, even when it's the only display output plugged in? At least Recovery Mode still works.

The log line in question being:

gnome-shell: Boot VGA GPU /dev/dri/card1 selected as primary

Appears in all "failed" boots.

But my monitor doesn't report "no HDMI video signal", emphasis mine, it just gives a black screen.

I've read some pdf documents throughout a long period of time and I'd like to backup the last known position where I stopped reading/last read page of each document.

I hope I'm explaining my self properly. Another way to put it is that I'd like to back up the data that saves my last read page on a series of pdf documents .

Every time I open a pdf that I read previously my system opens the last known page . Is it possible to back up such data ? It must be saved somewhere as it is accessible every time I open a old read pdf .

Basic timeline:

• I chose the "upgrade" option from the gui pop-up letting me know there was a newer version available.

• That ran for a bit, then gave me a message that it failed (I don't remember any details of the message, I mentally categorized it as "deal with that later")

• I noticed something was wrong with my internet, and the setting was missing from the quick menu

• I rebooted to see if that would resolve it

• It wouldn't boot into a gui, only into the terminal

• I started exploring in the terminal, and quickly found that I in fact don't have internet connectivity (eg, any install attempt of any package results in "failed to fetch")

• I booted from a 24.04 usb, which worked fine

• I was able to mount the old partition, explore files, etc; it's all still there

• I used the option, from the usb stick, to install 24.04 side-by-side

• That install went fine, and I now have two (relevant) partitions, one with 22.04 and one with 24.04. 24.04 works as expected but has none of my installed software, files, etc, and 22.04 boots into the terminal and has no internet connectivity

I would like to actually repair and upgrade the 22.04 installation and go back to using that partition as primary, but I'm not sure how to go about doing so. Fixing the internet on that partition seems like my first priority.

Output of ip link show when booted on the 22.04 partition:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

Output of ip link show when booted on the 24.04 partition:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

I'm way out of practice on network config via cli and haven't had much luck googling to try to figure out how to get the internet up and running, but I imagine that if I can get online, so that I can manually upgrade/install packages using apt, I probably could manage to get the system repaired from there.

Edit to add additional outputs:

sudo lshw -C network:

  *-network DISABLED
       description: Wireless interface
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       logical name: wlp0s20f3
       version: 01
       serial: b0:dc:ef:02:43:10
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=6.16.3-76061603-generic firmware=89.4d42c933.0 so-a0-gf-a0-89.uc latency=0 link=no multicast=yes wireless=IEEE 802.11
       resources: irq:17 memory:be390000-be393fff
  *-network DISABLED
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:0c:00.0
       logical name: enp12s0
       version: 15
       serial: d4:93:90:2d:0e:56
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical
       configuration: broadcast=yes driver=r8169 driverversion=6.16.3-76061603-generic latency=0 link=no multicast=yes
       resources: irq:17 ioport:d000(size=256) memory:be504000-be504fff memory:be500000-be503fff

sudo lspci -vnn | awk -vRS= '/\[02[08]0\]/':

00:14.3 Network controller [0280]: Intel Corporation Device [8086:51f1] (rev 01)
    Subsystem: Intel Corporation Device [8086:0094]
    Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 7
    Memory at be390000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [c8] Power Management version 3
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
    Capabilities: [100] Latency Tolerance Reporting
    Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
    Kernel driver in use: iwlwifi
    Kernel modules: iwlwifi
0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
    Subsystem: CLEVO/KAPOK Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1558:7755]
    Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 14
    I/O ports at d000 [size=256]
    Memory at be504000 (64-bit, non-prefetchable) [size=4K]
    Memory at be500000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
    Capabilities: [170] Latency Tolerance Reporting
    Capabilities: [178] L1 PM Substates
    Kernel driver in use: r8169
    Kernel modules: r8169

ip link show after sudo ip link set wlp0s20f3 up (verified with ping that this did not bring internet back):

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether d4:93:90:2d:0e:56 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether b0:dc:ef:02:43:10 brd ff:ff:ff:ff:ff:ff

Update as of 1/17/2026: I finally had time to poke at this some more today. Here's the additional info I was able to gather:

• Connecting via ethernet appears unhelpful; while in chroot, I can ping 8.8.8.8 just fine with or without ethernet, but DNS is not resolving (shame on me for pinging a url instead of an IP previously)
• However, ethernet does not get internet connectivity when booted directly into the old partition. enp12s0 shows as down with ip link show, and while sudo ip link set enp12s0 up does change its status to up, pinging 8.8.8.8 still does not work ("network is unreachable").
• Using chroot from the working installation does not let me interact with services (I attempted this to try to get dns resolution back online); it wants (and fails) to interact with the main system services (which makes sense, I'm not truly running on the old partition when using chroot).
• Unfortunately, since I can't get internet connected while truly booted into the old partition, and apt-offline is not already installed, I think it's at a dead end, and I'm going to need to just move what I need over to the new partition and delete/displace the old one to reclaim the space. I'm not going to get rid of the old partition just yet, so I'm all ears if anyone has other ideas that might get past this hurdle, but otherwise, I'm considering this closed.

I get a notification on login saying "Language support is incomplete, additional packages are required", but I don't get an option to install it.

What is missing? I've searched the internet. but the posts offer nothing that has worked.

I’m trying to dual boot Ubuntu and Windows 11 on an HP Spectre x360 16 from 2024, however when I turn on my computer it boots directly into Windows. When I check my boot menu, I only have the option to boot into Windows unless I manually tell it to boot into the Grub EFI file. When I check the BIOS settings, it doesn’t see the Ubuntu partition, just the Windows one. I have Secure Boot turned off. What should I do?

Now, the latest version of Node is 20.11.0. However, every time I tried to install Node, it installed the 12.22.9 version.

This commands is not working, every time it installed the same version 12.22.9

curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -

sudo apt install nodejs

Error description

I have an existing Conda environment with Python 3.8.16, and I have tried to install Spyder with: conda install spyder as well as with conda install -c conda-forge spyder, (not simultaneously) which installs Spyder 5.4.3.

Running spyder however outputs:

Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Aborted (core dumped)

Running it from Anaconda navigator gives:

Exit code: 134

N.B. Running Spyder from Anaconda navigator in base environment works fine! It also works fine in the problematic environment but on my laptop with Ubuntu 20.04.6, with the same Spyder version but conda 23.9.0.

I have found several related issues:

Rstudio fails to open with error "...could not find or load the Qt platform plugin "xcb""

Cannot open qcreator qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""

Could not find or load the Qt platform plugin "xcb": TexMaker

OpenCOR, "could not find or load the Qt platform plugin "xcb""

Could not find or load the Qt platform plugin "xcb"

“Failed to load platform plugin ”xcb“ ” while launching qt5 app on linux without qt installed

https://github.com/NVlabs/instant-ngp/discussions/300

https://discuss.pixls.us/t/solved-could-not-load-the-qt-platform-plugin-xcb-in-even-though-it-was-found/17677/7

None of which have solved my issue. Most of them have users finding the solution to be installing a large variety of libxcb*packages.

I have tried:

sudo apt install libxcb1
sudo apt install libx11-xcb1
sudo apt install xcb
sudo apt install libxcb-*

I have also tried:

export QT_QPA_PLATFORM=minimal

as well as xcb, dxcb and vnc and setting it to "".

Setting:

export QT_DEBUG_PLUGINS=1

also gives no new additional information. Also, on my laptop, echoing any of these variables gives nothing, yet it works there.

At first glance, the issue seems to be that the path where it looks for xcb is "", but I don't know what variable to change. After some searching, I tried:

export QT_QPA_PLATFORM_PLUGIN_PATH=/usr/lib/x86_64-linux-gnu/qt5/plugins

since echoing that variable gave nothing. However, echoing that in base also gives nothing, yet it works there.

This just resulted in the error:

Could not load the Qt platform plugin "xcb" in "/usr/lib/x86_64-linux-gnu/qt5/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

Aborted (core dumped)

Update 1: Now, however, setting export QT_DEBUG_PLUGINS=1 shows a whole lot, where the last perhaps relevant lines are:

Got keys from plugin meta data ("xcb")
QFactoryLoader::QFactoryLoader() checking directory path "/home/lord/anaconda3/envs/tir-top/bin/platforms" ...
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: (/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: undefined symbol: _ZNK15QXcbIntegration28createPlatformVulkanInstanceEP15QVulkanInstance, version Qt_5_PRIVATE_API)
QLibraryPrivate::loadPlugin failed on "/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so" : "Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: (/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libdxcb.so: undefined symbol: _ZNK15QXcbIntegration28createPlatformVulkanInstanceEP15QVulkanInstance, version Qt_5_PRIVATE_API)"
Could not load the Qt platform plugin "xcb" in "/usr/lib/x86_64-linux-gnu/qt5/plugins" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: dxcb, xcb, eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx.

Aborted (core dumped)

But I don't even know whether this is the correct path to set, and again, it seems these variables aren't even needed on my laptop.

Update 2: Creating a new environment and installing spyder there with

conda create -n spyd-test python=3.8.16
conda activate spyd-test
conda install spyder

works!

But for some reason, in my already existing environment with the same python version, it does not.

Other sys specs:

Ubuntu 22.04.3
spyder 5.4.3
spyder-kernels 2.4.4
conda 23.9.0
qt5dxcb-plugin (5.0.46+git20220314-1)

$ conda list | grep qt
pyqt                      5.15.9           py38hffdaa6c_5    conda-forge
pyqt5-sip                 12.12.2          py38h17151c0_5    conda-forge
pyqtwebengine             5.15.6                   pypi_0    pypi
pyqtwebengine-qt5         5.15.2                   pypi_0    pypi
qt-main                   5.15.8              h01ceb2d_12    conda-forge
qt-webengine              5.15.8               h27f4a20_2    conda-forge
qtawesome                 1.2.2            py38h06a4308_0  
qtconsole                 5.4.4                    pypi_0    pypi
qtpy                      2.4.0                    pypi_0    pypi
sphinxcontrib-qthelp      1.0.3              pyhd3eb1b0_0

conda list | grep spyder
pyls-spyder               0.4.0              pyhd3eb1b0_0  
spyder                    5.4.3            py38h06a4308_1  
spyder-kernels            2.4.4            py38h06a4308_0

Any help would be highly appreciated!

I have a QNAP NAS with NFS shares on my LAN and am trying to mount them on my mostly vanilla Ubuntu 22.04 install.

Running showmount on the client shows the NFS shares:

~$ showmount -e nas.localdomain
Export list for nas.localdomain:
/Videos   *
/Public   *
/Games    *
/Download *

The mount command completes successfully...

~$ sudo mount -t nfs nas.localdomain:/ /mnt/nas

... however trying to do anything in the mounted directory hangs (e.g. ls). Nautilus shows the top-level shared directories, but also hangs on trying to access them.

Oddly enough I have 2 other laptops, one running Ubuntu 21.04 and another one running Manjaro, and they both can mount the NAS shares with the exact same command without any problem, so the issue is most likely not with the NFS server but rather the client.

Any idea on how to solve this?

My laptop is an ASUS FX505DY. I bought it without any OS and installed Ubuntu 19.10, then upgraded to 20.04 a few months later (no dual-boot).

From time to time, the system doesn't boot normally and goes into "emergency mode" (it's actually the 3rd time after about 1 year of use). Each time the cause is fsck failing to check /home partition. journalctl gives me:

oct. 30 12:19:44 poulpito systemd-fsck[624]: fsck failed with exit status 4.
oct. 30 12:19:44 poulpito systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/91e9d404-4089-4b8d-af58-5aebcd76b5a0.

I can easily fix it with: fsck.ext4 -v /dev/sda4. I hit enter to every questions and then I can reboot and enjoy an OS running normally. But I feel uneasy with the problem recurring and I would like to fix it permanently.

So my questions are:

1. Why file system get corrupted on this partition? Could it be a hardware problem? Do I need to change some parameters or configuration or switch to ext3? I've run smartctl -t short /dev/sda4 in recovery mode and no error were reported.

2. /home is on a sata HDD where I also have /var, /tmp and swap partitions. I never get any fsck check problem for these. Perhaps because the boot sequence just doesn't check these partitions? Or corruptions really happen just on /home?

3. The last time I had to run fsck.ext4, I got these questions:

• pass 1: inode <inode id> seems to contain garbage and inode <inode id> passes checks, but checksum does not match inode, actually 16 messages of these kinds with contiguous inode numbers

• pass 2: entry '<filename>' in <path> (<inode id>) has deleted/unused inode <inode id> (inode numbers suggest that it is a mere consequence of inodes cleared during pass 1

• pass 4: inode <inode id> ref count is <count>, should be <count> (again, seems to be just a consequence of pass 2)

• pass 5: inode and block bitmap differences, free inodes/free blocks/directories count wrong

  Does this mean that I lose some data? Since all impacted inodes are related to application files in $HOME/.config/ or $HOME/.local/, I don't see directly the effect of a missing or corrupted file...

4. How do I prevent the file system to be corrupted?

Thanks!

Gilles

EDIT 1: Here is a screenshot of SMART data window in Disks app.

smartctl gives roughly the same data in english:

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   050    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0027   100   100   001    Pre-fail  Always       -       1350
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       670
  5 Reallocated_Sector_Ct   0x0033   100   100   050    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x000b   100   100   050    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   050    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0032   095   095   000    Old_age   Always       -       2224
 10 Spin_Retry_Count        0x0033   113   100   030    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       509
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       48
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       10
193 Load_Cycle_Count        0x0032   098   098   000    Old_age   Always       -       24418
194 Temperature_Celsius     0x0022   100   100   000    Old_age   Always       -       34 (Min/Max 19/42)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   200   253   000    Old_age   Always       -       0
220 Disk_Shift              0x0002   100   100   000    Old_age   Always       -       0
222 Loaded_Hours            0x0032   096   096   000    Old_age   Always       -       1931
223 Load_Retry_Count        0x0032   100   100   000    Old_age   Always       -       0
224 Load_Friction           0x0022   100   100   000    Old_age   Always       -       0
226 Load-in_Time            0x0026   100   100   000    Old_age   Always       -       263
240 Head_Flying_Hours       0x0001   100   100   001    Pre-fail  Offline      -       0
254 Free_Fall_Sensor        0x0032   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      2218         -

EDIT 2: and another screenshot for gparted.

EDIT 3: As suggested, I've upgraded my BIOS firmware. Well, the upgrade went fine and didn't break anything. For sure, it's better to have firmware up-to-date in any case. But I must confess that I don't understand how the BIOS could be responsible of FS corruptions on a single partition of my HDD and I can't see any way to verify that the problem is really solved. I give up for now and I'll update this post if the problem happen again. UPDATE: the same error occurred again about two months after original post and BIOS update.

EDIT 4: More details, as requested by @heynnema

$ free -h
              total       utilisé      libre     partagé tamp/cache   disponible
Mem:          7,7Gi       2,3Gi       3,8Gi        49Mi       1,5Gi       5,0Gi
Partition d'échange:        15Gi          0B        15Gi

sudo lshw -C memory https://paste.ubuntu.com/p/Sq9qy9kxVb/

zgrep -i gnome-software /var/log/syslog* https://paste.ubuntu.com/p/Qqy99YnFvC/

$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=cbee80f8-6637-44e3-8dbd-7f710be58e54 /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=E06D-1632  /boot/efi       vfat    umask=0077      0       1
# /home was on /dev/sda4 during installation
UUID=91e9d404-4089-4b8d-af58-5aebcd76b5a0 /home           ext4    defaults        0       2
# /tmp was on /dev/sda2 during installation
UUID=51e800d3-f199-490a-bb7a-d2f49635e71c /tmp            ext4    defaults        0       2
# /var was on /dev/sda3 during installation
UUID=da892f2f-b8d2-47f5-a5e7-30e779fe9d2c /var            ext4    defaults        0       2
# swap was on /dev/sda1 during installation
UUID=7317598f-60e6-475e-a7d0-38503bac42fc none            swap    sw              0       0

WIRELESS USB DONGLE - BLUETOOTH USB DONGLE - MINI 5.0 - VERSION 5.48 - 0a12:0001

So lately I bought a Bluetooth USB dongle - model no: MLT-5.0-MiNi

I'm using Ubuntu 20.04.1 LTS.

1. After I connected the adapter into USB port, I checked the port typing in terminal lsusb and I got the following:

Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

2. hciconfig -a gave the following:

hci0:   Type: Primary  Bus: USB
        BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
        DOWN
        RX bytes:574 acl:0 sco:0 events:30 errors:0
        TX bytes:368 acl:0 sco:0 commands:30 errors:0
        Features: 0xff 0xff 0x87 0xfa 0xdb 0xbf 0x7b 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT

3. hcitool dev:

Devices:

So it seemed that my PC didn't have the driver installed.

4. bluetoothctl --version:

bluetoothctl: 5.53

5. rfkill:

ID TYPE      DEVICE      SOFT      HARD
0  bluetooth hci0   unblocked unblocked

6. And finally btmon:

Bluetooth monitor ver 5.53
Failed to bind channel: Operation not permitted

I found this YouTube video to solve the problem.

1. First of all, I had to install the app "Ubuntu Mainline Kernel Installer" to update until the lastest kernel version, so I typed:

sudo add-apt-repository ppa:cappelikan/ppa
sudo apt-get update
sudo apt-get install mainline

2. Then, before updating to the last kernel version, I had to check what the running kernel version is:

User@PC:~$ uname -r

5.4.0-48-generic

User@PC:~$ uname -sr

Linux 5.4.0-48-generic

3. Later I went to the website of KERNEL and checked what the last Kernel version that's stable is, for example: 5.8.13

After all, I opened the app Ubuntu Mainline Kernel Installer and clicked the last kernel version that is stable, for example: 5.8.13. Finally clicked the button Install.

4. After the installation and reboot, I checked again:

User@PC:~$ uname -r

5.8.13-050813-generic

User@PC:~$ uname -sr

Linux 5.8.13-050813-generic

I saw that it was successful, and the bluetooth USB DONGLE 5.0 is working.

BUT THERE IS ONE PROBLEM TO CONNECT AFTER PAIRING: After pairing Ubuntu with my speaker 5.0, it cannot connect, then after pairing Ubuntu with my smartphone LG, I couldn't send any pictures to smartphone from Ubuntu nor vice versa.

1. I typed systemctl status bluetooth and entered.

● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-10-03 19:02:12 -05; 10min ago
       Docs: man:bluetoothd(8)
   Main PID: 2173 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 4649)
     Memory: 2.2M
     CGroup: /system.slice/bluetooth.service
             └─2173 /usr/lib/bluetooth/bluetoothd

oct 03 19:02:11 PC systemd[1]: Starting Bluetooth service...
oct 03 19:02:12 PC bluetoothd[2173]: Bluetooth daemon 5.53
oct 03 19:02:12 PC systemd[1]: Started Bluetooth service.
oct 03 19:02:12 PC bluetoothd[2173]: Starting SDP server
oct 03 19:02:12 PC bluetoothd[2173]: Bluetooth management interface 1.17 initialized
oct 03 19:02:13 PC bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)
oct 03 19:02:14 PC bluetoothd[2173]: Endpoint registered: sender=:1.75 path=/MediaEndpoint/A2DPSink/sbc
oct 03 19:02:14 PC bluetoothd[2173]: Endpoint registered: sender=:1.75 path=/MediaEndpoint/A2DPSource/sbc
oct 03 19:02:14 PC bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)

I see that there is a problem:

bluetoothd[2173]: Failed to set mode: Blocked through rfkill (0x12)

2. rfkill list:

1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

3. hciconfig -a:

hci0:   Type: Primary  Bus: USB
    BD Address: 00:1A:7D:DA:71:11  ACL MTU: 679:9  SCO MTU: 48:16
    UP RUNNING PSCAN ISCAN 
    RX bytes:1174 acl:0 sco:0 events:65 errors:0
    TX bytes:1046 acl:0 sco:0 commands:65 errors:0
    Features: 0xff 0xff 0x87 0xfa 0xdb 0xbf 0x7b 0x83
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
    Link policy: RSWITCH HOLD SNIFF PARK 
    Link mode: SLAVE ACCEPT 
    Name: 'Daniel-MS-7529'
    Class: 0x1c0104
    Service Classes: Rendering, Capturing, Object Transfer
    Device Class: Computer, Desktop workstation
    HCI Version: 5.0 (0x9)  Revision: 0x810
    LMP Version: 5.0 (0x9)  Subversion: 0x2312
    Manufacturer: Cambridge Silicon Radio (10)

I see that everything is OK.

4. btmon:

Bluetooth monitor ver 5.53
Failed to bind channel: Operation not permitted

5. sudo dmesg | grep -i bluetooth:

[  132.146271] Bluetooth: Core ver 2.22
[  132.146302] Bluetooth: HCI device and connection manager initialized
[  132.146308] Bluetooth: HCI socket layer initialized
[  132.146310] Bluetooth: L2CAP socket layer initialized
[  132.146314] Bluetooth: SCO socket layer initialized
[  132.515401] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds...
[  133.859424] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  133.859426] Bluetooth: BNEP filters: protocol multicast
[  133.859431] Bluetooth: BNEP socket layer initialized
[  135.263551] Bluetooth: RFCOMM TTY layer initialized
[  135.263561] Bluetooth: RFCOMM socket layer initialized
[  135.263570] Bluetooth: RFCOMM ver 1.11
[ 1017.955624] Bluetooth: hci0: inquiry failed: status 0x0c
[ 1023.331631] Bluetooth: hci0: inquiry failed: status 0x0c
[ 3305.392256] Bluetooth: hci0: CSR: Unbranded CSR clone detected; adding workarounds...

There is one more problem:

Bluetooth: hci0: inquiry failed: status 0x0c

6. Another time, I typed on the terminal hcidump -X and entered and then I went to the setting of Bluetooth to try to pair and connect the speaker and I got the following results on the terminal:

HCI sniffer - Bluetooth packet analyzer ver 5.53
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff

[several lines related to HCI Event]

> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2744 class 0x240404 rssi -25
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 24:FC:E5:6E:53:5B mode 1 clkoffset 0x18bd class 0x08043c rssi -71
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 24:FC:E5:6E:53:5B mode 1 clkoffset 0x18bd class 0x08043c rssi -98
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Random Address (0x08|0x0005) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Parameters (0x08|0x000b) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Disconnect (0x01|0x0006) status 0x00 ncmd 1
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Disconn Complete (0x05) plen 4
    status 0x00 handle 128 reason 0x16
    Reason: Connection Terminated by Local Host
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -25
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Random Address (0x08|0x0005) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Parameters (0x08|0x000b) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Complete (0x0e) plen 4
    LE Set Scan Enable (0x08|0x000c) ncmd 1
    status 0x00
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -27
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -27
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -23
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -24
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -23
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data
> HCI Event: Extended Inquiry Result (0x2f) plen 255
    bdaddr 88:D0:39:7C:24:61 mode 1 clkoffset 0x2745 class 0x240404 rssi -22
    Complete local name: 'Soundcore Flare+'
    Unknown type 0xff with 9 bytes data

Soundcore Flare+ is the speaker's model. I see there is one another problem:

Unknown type 0xff with 9 bytes data

The Bluetooth USB 5.0 works fine on Windows 10 but on Ubuntu 20.04, it doesn't work. So Ubuntu needs drivers for Bluetooth 5.0.

On 5.8.14 Kernel, Ubuntu really displays devices to pair and connect, but the pairing and connecting don't work.

So, could anyone help me to solve this problem of pairing and connecting with devices from Ubuntu?

I found the problem solved for Linux in this website but I don't know how to compile and patch on Ubuntu 20.04, it can work only for Kernel's version 5.8.

When I turn on my laptop, everything seems to boot normally and I enter my decryption key to decrypt my hard drive. Then I'm taken to my login page, but when I try to type in my password, none of my keys work and I can't move my mouse. Why is this happening?

Earlier I had a problem where I would get a black screen of death whenever I turned on my laptop and I resolved this by going into recovery mode and reinstalling Nvidia drivers. Now I have the problem mentioned above and whenever I go into the root terminal in recovery mode, I find that I'm not able to install any packages. I can't even do a simple sudo apt-get update.

What is happening?

I have a process for an application which needs to run, but ends up using far too much IO usage for what it does. And really crashes my computer, making it impossible to do anything else whilst it is running.

So I was wondering if there is a way to limit IO usage, RAM and CPU for a given process? And its sub-processes of course.

This is on my Ubuntu 18.04 LTS system.

Ethernet does not resume after suspend.

sudo service network-manager restart

does not work. Only restart solves problem.

I have installed Wine stable and development from the Ubuntu Store but neither is appearing. I am trying to run a screensaver .exe file but cannot. Please recommend either how to get Wine to work or an alternative (PlayOnLinux doesn't work either).

I'm trying to uninstall boost library:

sudo apt-get purge libboost-all-dev
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package 'libboost-all-dev' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 219 not upgraded.

But apt list --installed | grep boost command shows me it still here.

WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

libboost-atomic1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-atomic1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-chrono1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-chrono1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-context1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-context1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-date-time1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-date-time1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-exception1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-filesystem1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-filesystem1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-graph-parallel1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-graph-parallel1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-graph1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-graph1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-iostreams1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-iostreams1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-locale1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-locale1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-math1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-math1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-mpi-python1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-mpi-python1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-mpi1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-mpi1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-program-options1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-program-options1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-python1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed]
libboost-python1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-random1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-random1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-regex1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-regex1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-serialization1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-serialization1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-signals1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-signals1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-system1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-system1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-test1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-test1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-thread1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed]
libboost-thread1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-timer1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-timer1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-wave1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost-wave1.54.0/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost1.54-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]
libboost1.54-tools-dev/trusty-updates,now 1.54.0-4ubuntu3.1 amd64 [installed,automatic]

This command shows nothing:

dpkg -L libboost-dev
dpkg-query: package 'libboost-dev' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

And one more method:

ldconfig -p | grep boost
    libboost_wserialization.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_wserialization.so.1.56.0
    libboost_wserialization.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_wserialization.so.1.54.0
    libboost_wserialization.so (libc6,x86-64) => /usr/local/lib/libboost_wserialization.so
    libboost_wserialization.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_wserialization.so
    libboost_wave.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_wave.so.1.56.0
    libboost_wave.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_wave.so.1.54.0
    libboost_wave.so (libc6,x86-64) => /usr/local/lib/libboost_wave.so
    libboost_wave.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_wave.so
    libboost_unit_test_framework.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_unit_test_framework.so.1.56.0
    libboost_unit_test_framework.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so.1.54.0
    libboost_unit_test_framework.so (libc6,x86-64) => /usr/local/lib/libboost_unit_test_framework.so
    libboost_unit_test_framework.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_unit_test_framework.so
    libboost_timer.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_timer.so.1.56.0
    libboost_timer.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_timer.so.1.54.0
    libboost_timer.so (libc6,x86-64) => /usr/local/lib/libboost_timer.so
    libboost_timer.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_timer.so
    libboost_thread.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_thread.so.1.56.0
    libboost_thread.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.54.0
    libboost_thread.so (libc6,x86-64) => /usr/local/lib/libboost_thread.so
    libboost_thread.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_thread.so
    libboost_system.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_system.so.1.56.0
    libboost_system.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_system.so.1.54.0
    libboost_system.so (libc6,x86-64) => /usr/local/lib/libboost_system.so
    libboost_system.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_system.so
    libboost_signals.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_signals.so.1.56.0
    libboost_signals.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_signals.so.1.54.0
    libboost_signals.so (libc6,x86-64) => /usr/local/lib/libboost_signals.so
    libboost_signals.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_signals.so
    libboost_serialization.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_serialization.so.1.56.0
    libboost_serialization.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_serialization.so.1.54.0
    libboost_serialization.so (libc6,x86-64) => /usr/local/lib/libboost_serialization.so
    libboost_serialization.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_serialization.so
    libboost_regex.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_regex.so.1.56.0
    libboost_regex.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_regex.so.1.54.0
    libboost_regex.so (libc6,x86-64) => /usr/local/lib/libboost_regex.so
    libboost_regex.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_regex.so
    libboost_random.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_random.so.1.56.0
    libboost_random.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_random.so.1.54.0
    libboost_random.so (libc6,x86-64) => /usr/local/lib/libboost_random.so
    libboost_random.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_random.so
    libboost_python.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_python.so.1.56.0
    libboost_python.so (libc6,x86-64) => /usr/local/lib/libboost_python.so
    libboost_python-py34.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py34.so.1.54.0
    libboost_python-py34.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py34.so
    libboost_python-py27.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.54.0
    libboost_python-py27.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py27.so
    libboost_program_options.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_program_options.so.1.56.0
    libboost_program_options.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_program_options.so.1.54.0
    libboost_program_options.so (libc6,x86-64) => /usr/local/lib/libboost_program_options.so
    libboost_program_options.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_program_options.so
    libboost_prg_exec_monitor.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_prg_exec_monitor.so.1.56.0
    libboost_prg_exec_monitor.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_prg_exec_monitor.so.1.54.0
    libboost_prg_exec_monitor.so (libc6,x86-64) => /usr/local/lib/libboost_prg_exec_monitor.so
    libboost_prg_exec_monitor.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_prg_exec_monitor.so
    libboost_mpi_python-py34.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi_python-py34.so.1.54.0
    libboost_mpi_python-py34.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi_python-py34.so
    libboost_mpi_python-py27.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi_python-py27.so.1.54.0
    libboost_mpi_python-py27.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi_python-py27.so
    libboost_mpi.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi.so.1.54.0
    libboost_mpi.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_mpi.so
    libboost_math_tr1l.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_tr1l.so.1.56.0
    libboost_math_tr1l.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1l.so.1.54.0
    libboost_math_tr1l.so (libc6,x86-64) => /usr/local/lib/libboost_math_tr1l.so
    libboost_math_tr1l.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1l.so
    libboost_math_tr1f.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_tr1f.so.1.56.0
    libboost_math_tr1f.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1f.so.1.54.0
    libboost_math_tr1f.so (libc6,x86-64) => /usr/local/lib/libboost_math_tr1f.so
    libboost_math_tr1f.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1f.so
    libboost_math_tr1.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_tr1.so.1.56.0
    libboost_math_tr1.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1.so.1.54.0
    libboost_math_tr1.so (libc6,x86-64) => /usr/local/lib/libboost_math_tr1.so
    libboost_math_tr1.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_tr1.so
    libboost_math_c99l.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_c99l.so.1.56.0
    libboost_math_c99l.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99l.so.1.54.0
    libboost_math_c99l.so (libc6,x86-64) => /usr/local/lib/libboost_math_c99l.so
    libboost_math_c99l.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99l.so
    libboost_math_c99f.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_c99f.so.1.56.0
    libboost_math_c99f.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99f.so.1.54.0
    libboost_math_c99f.so (libc6,x86-64) => /usr/local/lib/libboost_math_c99f.so
    libboost_math_c99f.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99f.so
    libboost_math_c99.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_math_c99.so.1.56.0
    libboost_math_c99.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99.so.1.54.0
    libboost_math_c99.so (libc6,x86-64) => /usr/local/lib/libboost_math_c99.so
    libboost_math_c99.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_math_c99.so
    libboost_log_setup.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_log_setup.so.1.56.0
    libboost_log_setup.so (libc6,x86-64) => /usr/local/lib/libboost_log_setup.so
    libboost_log.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_log.so.1.56.0
    libboost_log.so (libc6,x86-64) => /usr/local/lib/libboost_log.so
    libboost_locale.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_locale.so.1.56.0
    libboost_locale.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_locale.so.1.54.0
    libboost_locale.so (libc6,x86-64) => /usr/local/lib/libboost_locale.so
    libboost_locale.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_locale.so
    libboost_iostreams.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_iostreams.so.1.56.0
    libboost_iostreams.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.54.0
    libboost_iostreams.so (libc6,x86-64) => /usr/local/lib/libboost_iostreams.so
    libboost_iostreams.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so
    libboost_graph_parallel.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_graph_parallel.so.1.54.0
    libboost_graph_parallel.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_graph_parallel.so
    libboost_graph.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_graph.so.1.56.0
    libboost_graph.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_graph.so.1.54.0
    libboost_graph.so (libc6,x86-64) => /usr/local/lib/libboost_graph.so
    libboost_graph.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_graph.so
    libboost_filesystem.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_filesystem.so.1.56.0
    libboost_filesystem.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.54.0
    libboost_filesystem.so (libc6,x86-64) => /usr/local/lib/libboost_filesystem.so
    libboost_filesystem.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_filesystem.so
    libboost_date_time.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_date_time.so.1.56.0
    libboost_date_time.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.54.0
    libboost_date_time.so (libc6,x86-64) => /usr/local/lib/libboost_date_time.so
    libboost_date_time.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_date_time.so
    libboost_coroutine.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_coroutine.so.1.56.0
    libboost_coroutine.so (libc6,x86-64) => /usr/local/lib/libboost_coroutine.so
    libboost_context.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_context.so.1.56.0
    libboost_context.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_context.so.1.54.0
    libboost_context.so (libc6,x86-64) => /usr/local/lib/libboost_context.so
    libboost_context.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_context.so
    libboost_container.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_container.so.1.56.0
    libboost_container.so (libc6,x86-64) => /usr/local/lib/libboost_container.so
    libboost_chrono.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_chrono.so.1.56.0
    libboost_chrono.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.54.0
    libboost_chrono.so (libc6,x86-64) => /usr/local/lib/libboost_chrono.so
    libboost_chrono.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_chrono.so
    libboost_atomic.so.1.56.0 (libc6,x86-64) => /usr/local/lib/libboost_atomic.so.1.56.0
    libboost_atomic.so.1.54.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.54.0
    libboost_atomic.so (libc6,x86-64) => /usr/local/lib/libboost_atomic.so
    libboost_atomic.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_atomic.so

I don't remembe how boost was installed and my OS is Ubuntu 14.04.

So my questions are:

1. What method should be used to detect presence of library in the system?

2. How to completely remove boost library?

UPDATE:

Seems I managed to do it like here, but not sure if it's good way and apt list --installed | grep boost, ldconfig -p | grep boost still show presence of boost:

rm /usr/local/lib/libboost*
sudo rm -r /usr/local/include/boost

I was upgrading Ubuntu 12.04.1 to 12.04.05 and the kernel upgrade from 3.8.0.29 to 3.8.0.44 using dist-upgrade. The system won't boot back in to the new kernel as I cannot find the rootvg.

Here is the message I get.

Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
 - Check root delay = (did the system wait long enough?) 
 - Check root= (did the system wait for the right device?)
- Missing Modules (cat /proc/modules; ls /dev)
Alert! /dev/mapper/rootvg-root does not exist. Dropping to a shell

(initramfs)

I tried using a live CD to boot the system and did the below tasks

1. Boot live CD.
2. mount /dev/mapper/rootvg-root /newroot
3. chroot /newroot
4. Tried to reinstall lvm2 and it said it was successful and recreated initrd.img
5. update-initramfs -u

It won't reboot. Can you throw me some pointers about what could be happening?

I have been trying to install Canon Printer LBP6030w. I downloaded the driver, tried the generic driver, tried Synaptic package manager, downloaded all the updates from Canon, but none of these works.

Any ideas how to install and make it work on Ubuntu 14.04 LTS? Thanks for your help and advice.

I have setup disk encryption with LUKS and configure it to auto mount when the system boots up. So now as it supposed, it prompts me a passphrase when the system boots up. If i enter the correct passphrase it continuous the system.

So in some cases I want to escape from typing my passphrase. Is there a way to do that?

I would like to use CUDA on my Ubuntu machine with the graphics card NVIDIA Geforce 9600 GT. Installing CUDA is no problem but in order to run any CUDA code I need to install the proprietary NVIDIA driver as well.

I did so by choosing an appropriate one (for example, 331) from the list popping up in the "Additional drivers" menu. The installation works just fine but whenever I reboot the system all I see is a black screen with a blinking cursor.

After purging all NVIDIA related stuff (sudo apt-get remove --purge nvidia*), I'm able to use the system again after rebooting.

I read somewhere that this problem might be related to the fact that I have to use DVI instead of VGA as there are no other output ports on the card. However, switching from one DVI output port to another doesn't help either.

Any help is greatly appreciated.

OS: Ubuntu 12.04LTS

bonding is in /etc/modules for automatic loading at boot

The bonding configuration works in bond-mode 0 but not bond-mode 6

--

When the system boots bond0 comes up with only eth0 as slave

eth1 is not up at all in ifconfig but can be brought up ifconfig eth1 up

However, even after it is brought up, it is not enslaved to bond0

Attempting to use ifenslave bond0 eth1 results in Master 'bond0', Slave 'eth1': Error: Enslave failed

syslog reports that bonding: bond0: Error: dev_set_mac_address of dev eth1 failed!

However, I am able to use ifconfig eth1 hw ether 123456789abc to set the mac address on the adapter (works on both eth0 and eth1)

bond0     Link encap:Ethernet  HWaddr <mac address>
          inet addr:10.3.0.1  Bcast:10.255.255.255  Mask:255.0.0.0
          inet6 addr: fe80::222:68ff:fe39:83c0/64 Scope:Link
          UP BROADCAST MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:10519 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9444 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2179485 (2.1 MB)  TX bytes:1158406 (1.1 MB)

eth0      Link encap:Ethernet  HWaddr 34:56:78:9a:bc:de     <-- set using ifconfig
          UP BROADCAST SLAVE MULTICAST  MTU:1500  Metric:1
          RX packets:10519 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9444 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2179485 (2.1 MB)  TX bytes:1158406 (1.1 MB)
          Interrupt:17 

eth1      Link encap:Ethernet  HWaddr 12:34:56:78:9a:bc    <-- set using ifconfig
          inet6 addr: fe80::1034:56ff:fe78:9abc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3417 errors:0 dropped:0 overruns:1 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:689886 (689.8 KB)  TX bytes:28363 (28.3 KB)
          Interrupt:20 Base address:0xe800 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:306 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:76193 (76.1 KB)  TX bytes:76193 (76.1 KB)

lo:1      Link encap:Local Loopback  
          inet addr:172.16.1.1  Mask:255.255.255.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

Here is my /etc/network/interfaces:

auto lo lo:1 br0
iface lo inet loopback

auto he-ipv6
iface he-ipv6 inet6 v4tunnel
  endpoint 209.51.161.14
  address 2001:470:1f06:4ca::2
  gateway 2001:470:1f06:4ca::1
  netmask 64
  local 10.3.0.1
  up ip -6 route add default dev he-ipv6
  down ip -6 route del default dev he-ipv6

iface lo:1 inet static
  address 172.16.1.1
  netmask 255.255.255.0
  network 172.16.1.0

auto eth0
  iface eth0 inet manual
  bond-master bond0

auto eth1
  iface eth1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet static
  address 10.3.0.1
  netmask 255.0.0.0
  gateway 10.0.0.1
  bond-mode 6
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves none

ethtool ethX output:

Settings for eth0:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Half 1000baseT/Full 
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Half 1000baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: No
    Speed: 100Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: pg
    Wake-on: g
    Current message level: 0x000000ff (255)
                   drv probe link timer ifdown ifup rx_err tx_err
    Link detected: yes


Settings for eth1:
    Supported ports: [ TP MII ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                         100baseT/Half 100baseT/Full 
    Link partner advertised pause frame use: Symmetric
    Link partner advertised auto-negotiation: Yes
    Speed: 100Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 24
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: g
    Wake-on: d
    Current message level: 0x00000001 (1)
                   drv
    Link detected: yes