Ghostscript unable to write to non-boot volume after update to 25.10 https://askubuntu.com/questions/1560219/ghostscript-unable-to-write-to-non-boot-volume-after-update-to-25-10

I'm having a hard time figuring out the best place to ask this question, but starting here since the problem started when I updated Ubuntu from 25.04 to 25.10 last month. In a nutshell, I have two physical volumes in my laptop, and after updating 25.10, Ghostscript can no longer write PDFs to one of them (but only one of them).

My hardware setup is as follows:

  • Boot drive that includes $HOME (i.e., /home/user).

  • Second physical drive, symlinked from $HOME to store the bulk of my data. My main documents directory, therefore, is physically located at /mnt/data/user/Documents, though user@machine~/Documents$ pwd returns /home/user/Documents.

I am using Ghostscript, and particularly the ps2pdf script, as part of a LaTeX workflow for a document I update every month. I use TeXLive 2025 and my document makes heavy use of pstricks, so pdflatex is not a good option for me (and yes, I realize there may be options for working around Ghostscript, but I occasionally use it for other purposes so would like it to work regardless).

Here is the now-problematic workflow for a small, two-page test document when I execute it in ~/Documents (but I run into the same error regardless of the document):

$ latex test.tex
...
Output written on test.dvi (2 pages, 436 bytes)
...

$ dvips test.dvi
...
[1] [2]

$ ps2pdf test.ps
GPL Ghostscript 10.05.0: **** Could not open the file test.pdf .
**** Unable to open the initial device, quitting.

I also tried skipping the ps2pdf script and using a simple Ghostscript command directly, with the same result:

$ gs -sDEVICE=pdfwrite -sOutputFile=test.pdf test.ps
GPL Ghostscript 10.05.0: **** Could not open the file test.pdf .**** Unable to open the initial device, quitting.

This happens no matter which subdirectory of ~/Documents I use, and also in other directories that are physically located on /mnt/data (e.g., ~/Pictures). However, if I run it in $HOME (or subdirectory of $HOME that is physically located on my boot drive), the PDF is produced without error as it has been every month for the last 6 years. Hence my conclusion that the problem is related to the physical volume somehow.

What I have tried:

  • Reinstalling ghostscript.

  • Checking directory owners and permissions.

    • $HOME: drwxr-xr-x 52 user user

    • /mnt/data/user: drwxrwxrwx 11 user user

    • /mnt/data/user/Documents: drwxrwxr-x 56 user user

    • Owners and permissions for all subdirectories of /mnt/data/user appear to be the same as for /mnt/data/user/Documents.

  • Running sudo ps2pdf test.ps, which gives the same error as when running as user.

  • Providing the full path to the input file, both as ps2pdf /mnt/data/user/Documents/test.ps and ps2pdf ~/Documents/test.ps, which gives the same error.

Ghostscript is the only application for which I have experienced this problem, and only since the update to Ubuntu 25.10. I believe, but am not 100% sure, that the Ghostscript version was 10.05.0 for both 25.04 and 25.10, but I think it could have been 10.03.1 on 25.04.

VLC fails network stream in Ubuntu 22.04 https://askubuntu.com/questions/1560218/vlc-fails-network-stream-in-ubuntu-22-04

I use VLC to monitor a DVR via RTSP. Suddenly it stopped connecting. I have tried everything I can find, but it still fails to connect. Any help most welcome.

How to run a command in a terminal only if the previous commands succeed? https://askubuntu.com/questions/1560213/how-to-run-a-command-in-a-terminal-only-if-the-previous-commands-succeed

I want to open a terminal and automatically open a folder and run a command within it

For this, I have the following:

:~$ gnome-terminal --working-directory=/home/project -- code .

This runs code . (opens VSCode in the current folder) after it opens the terminal in /home/project.

  1. Is this behaviour guaranteed that it will navigate to the working directory and then run code .

    I ask because I do not want code . to run in the current directory from where the command is issued and then the terminal opens in the working directory.

  2. This seems to work fine if the working directory exists. But if /home/project does not exist, I want the entirety of the above command to fail. At present, it still runs code . if the working directory does not exist in the current folder from the above command is issued.

Bluetooth can not be turned on after login with new laptop and fresh installed 24.04. upgrade to the latest 25.xx. issue still presents https://askubuntu.com/questions/1560212/bluetooth-can-not-be-turned-on-after-login-with-new-laptop-and-fresh-installed-2

behaviour is following:

  • on the login screen. the Bluetooth is toggled on, BT device are visible. seems working
  • after login (entering PW and get into Ubuntu), the Bluetooth button is gray, and can not be turn on.

only solution for me now, is each time to "rmmod btusb btintel && modprobe btusb btintel". but once the laptop is log out and back, the BT icon can not be turned on again.

Ubuntu 24.04 VM on KVM takes 20–25 minutes to boot with direct GPU passthrough https://askubuntu.com/questions/1560210/ubuntu-24-04-vm-on-kvm-takes-20-25-minutes-to-boot-with-direct-gpu-passthrough

I have an Ubuntu 24.04 virtual machine running on a KVM hypervisor, and I’m noticing that it takes around 20–25 minutes to boot up completely.

Environment details:

  • Hypervisor: KVM (host OS: Ubuntu 24.04]
  • Guest OS: Ubuntu 24.04 server
  • VM resources: 4 vCPUs, 8 GB RAM, 1 GPU passthrough (NVIDIA H100 & H200)
  • Storage: QCOW2 on SSD
  • GPU passthrough: Yes
  • Boot type: UEFI

Issue: Boot time is extremely slow — it takes around 20–25 minutes for the system to reach the login prompt. Once it’s running, performance seems normal.

What We’ve tried:

  • Checked journalctl -b on baremetal hosts for errors — some “waiting for device” messages appear.
  • Disabled unnecessary services via systemctl.
  • Updated all packages (sudo apt update && sudo apt upgrade).
  • Verified disk performance on the host (seems normal).

Questions:

  1. How can we identify what’s causing the delay during boot?
  2. Are there known issues with Ubuntu 24.04 boot times under KVM with GPU passthrough?
  3. Any tools or logs you recommend checking for slow boot diagnosis?
alternative to wmctrl in wayland https://askubuntu.com/questions/1560207/alternative-to-wmctrl-in-wayland

I noticed that in wayland wmctrl doesn't work. To close an app it seems that the only way is pkill (or killall), that could be more dangerous.

There is way to close gently an app (Firefox) in wayland?

I have KDE Neon (last release).

Thank you!

EDIT

This command (as suggested here) works:

kill `ps -ej | grep -v grep | grep firefox | head -1 | awk '{print $1}'`

And no error messages re-opening FF. But it could be considered totally sure?

Ubuntu 24.04 lts and tracker using 100%cpu https://askubuntu.com/questions/1560206/ubuntu-24-04-lts-and-tracker-using-100cpu

I see a long history around questions on how to make this tracker-process NOT constantly use lots of CPU. I find that all suggestions - done in the past - fail on 24.04 LTS. The design seems based on the false assumption that everyone has CPU-power in abundance. Can anyone please suggest a method to make tracker use far less than 100% CPU? Otherwise I will have to abandon Ubuntu

Hibernate Ubuntu 24 on ASUS ExpertBook B1500CEPE https://askubuntu.com/questions/1560205/hibernate-ubuntu-24-on-asus-expertbook-b1500cepe

I am struggling to apply a hibernation capability for Ubuntu 24 Server + Minimal Desktop, after several tries following different routes and troubleshooting.

It has the latest firmware.

Has anyone done it, any advice? Will @Ubuntu solve this at some point?

I learnt that ASUS is very Windows oriented. Next time I get a Lenovo.

Root Filesystem Optimization for Xilinx MPSoC https://askubuntu.com/questions/1560200/root-filesystem-optimization-for-xilinx-mpsoc

We are planning to migrate from PetaLinux to Ubuntu on our custom board based on the Xilinx MPSoC. We have successfully brought up the custom board using the certified minimal Ubuntu Desktop 22.04 image provided by AMD and Canonical (https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1413611532/Canonical+Ubuntu), along with the required custom kernel changes, however we observed that the Ubuntu root filesystem size is quite large (approximately 7.2 GB total with about 4.7 GB used):

osboxes@osboxes:/mnt/shared$ df -h /tmp/rootfs 
Filesystem      Size  Used Avail Use% Mounted on 
/dev/loop0      7.0G  4.7G  2.0G  71% /tmp/rootfs

This appears to be due to the certified image being a minimal Desktop variant, which still includes GUI components, snap services, and other packages that are not required for our target platform.

For our custom board, we do not need the GUI or snap packages, and we would like to further reduce the rootfs footprint. We would appreciate your support in achieving this. We have the following questions:

  1. Can we further optimize the certified Ubuntu Desktop image? Specifically, which packages (e.g., GUI, snap) can be safely removed?

  2. Alternatively, should we use an Ubuntu Base image and add only the necessary components on top of it? If so, please advise which required packages should be included for a Xilinx MPSoC platform based on the certified Xilinux eval board, e.g. ZCU102.

Is the Snapdragon X Elite (ARM) ready for a daily web dev driver (LAMP stack, Node, Git) on Ubuntu 24.10/25.04? [duplicate] https://askubuntu.com/questions/1560199/is-the-snapdragon-x-elite-arm-ready-for-a-daily-web-dev-driver-lamp-stack-no

I am looking to purchase a new laptop and am considering a device with the Snapdragon X Elite (or Plus) ARM-based processor. My primary OS is Ubuntu, and I need to know if the current state of Ubuntu on this hardware is stable enough for a daily-driver web development workflow.

My specific questions are:

Hardware Support: I've read about the "Ubuntu Concept" builds for the X Elite. Is the support for things like WiFi, Audio, and Suspend/Resume reliable enough for daily use yet, or should I wait for the 25.04 release?

Dev Stack Compatibility: I work with the following tools daily. Do these run natively (ARM64) and perform well, or will I be forced to use x86 emulation?

  • LAMP Stack: Apache, MySQL, PHP (and PHPMyAdmin)
  • Node.js: NPM and Node ecosystem
  • Git

Browsers: I know Chromium has a native ARM build, but what is the current status of Google Chrome on Ubuntu ARM? Do I have to run the x86 version via emulation, and if so, is the performance acceptable for debugging heavy web apps?

VLC: Does hardware-accelerated video decoding work on these chips in Ubuntu yet?

I am comfortable troubleshooting minor Linux issues, but I cannot afford a system where my core development tools (servers and databases) are unstable or slow due to emulation.

Error message for downloading wireless drivers for MacBook Pro 2012 https://askubuntu.com/questions/1560198/error-message-for-downloading-wireless-drivers-for-macbook-pro-2012

I entered sudo apt-get install firmware-b43-installer and got this after a while (sorry copy paste from a screenshot.

A card known to work was found.
Unknown device(s) found: PCI id
Trying to install latest firmware 6.30.163.46 •
--2025-11-27 22:23:15-. https://www.lwfinger.com/b43-firmware/broadcom-wl-6.30.163.46. tar.bz2
Resolving www.lwfinger.com (www.lwfinger.com)... 104.21.94.197, 172.67.168.164, 2606:4700:30
0:: ac43:a804, ..•
Connecting to www.lwfinger.com (www.lwfinger.com) |104.21.94.197|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently Location: https://blueprintmegaways.com/ [following]
-- 2025-11-27 22:23:15-- https://blueprintmegaways.com/
Resolving blueprintmegaways.com (blueprintmegaways.com)... 172.67.176.218, 104.21.96.104, 26
6:4700:3036::6815:6068,...
Connecting to blueprintmegaways.com (blueprintmegaways.com) |172.67.176.218| :443... connected.
HTTP request sent, awaiting response... 200 0K
Length: unspecified [text/html]
Saving to: "broadcom-wl-6.30.163.46.tar.bz2" broadcom-wl -6.30.16
[<=
1 57.37K
-- . -KB/s
in 0.002s
2025-11-27 22:23:16 (23.8 MB/s) - 'broadcom-wl -6.30.163.46. tar.bz2' saved [58745]
broadcom-wl -6.30.163.46. tar.bz2: FAILED
sha512sum: WARNING: 1 computed checksum did NOT match /var/lib/dpkg/info/firmware-b43-installer postinst: 
Downloaded firmware did not match known SHA512 checksum, aborting.
dpkg: error processing package firmware-b43-installer (--configure):
installed firmware-b43-installer package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.12.0-4build2) •••
Errors were encountered while processing: firmware-b43- installer
E: Sub-process /us/bin/dpkg returned an error code (1)
How can I enable macOS-style keyboard shortcuts on a MacBook running Ubuntu as its only OS https://askubuntu.com/questions/1560191/how-can-i-enable-macos-style-keyboard-shortcuts-on-a-macbook-running-ubuntu-as-i

I would like to install Ubuntu 25.10 as the exclusive OS on a old MacBook and would like to use macOS-style keyboard shortcuts — for example Command+C for copy, Command+V for paste, and Command+Tab to switch apps. Is there a way to make the Command () key behave like Ctrl system-wide in Ubuntu? Ideally a simple solution that works across all applications.

How can I revert a config file back to the originally installed? [duplicate] https://askubuntu.com/questions/1559199/how-can-i-revert-a-config-file-back-to-the-originally-installed

In this post: How can I revert a config file back to the originally installed version after I have edited it? Someone said

Because the other options in dpkg doesn't work well.

Is there a Bug reference in Ubuntu database describing these issues ? I am trying to overwrite changes to config files when installing a package, and although I installed with -o DPkg::Options::="--force-confnew", local changes to config file are NOT overwriten.

I am running an Ubuntu jammy, currently installed packages versions are:

linux-image-generic 5.15.0.161.157
dpkg 1.21.1ubuntu2.6
apt 2.4.14

From reading previous mentioned thread, I understood that I should try using these options for it to work as expected: -o DPkg::Options::="--force-confnew" -o DPkg::Options::="--force-confask" [-o DPkg::Options::="--force-confmiss"]

I tested with all 3 options (--force-confnew, --force-confask, --force-confmiss"). And local changes to my config file are still NOT overwritten !

Copying logs with dpkg debug activated (the modified config file that should have been rewritten is utl-infra.conf):

# apt-get -o APT::Get::Allow-Downgrades="true" -o APT::Get::Assume-Yes="true" -o Dpkg::Options="--force-confnew" -o Dpkg::Options="--force-confmiss" -o Dpkg::Options="--force-confask" install x-ntp=1.5-2804-5248a1af
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  x-ntp
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 14.1 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://mesta-repo.epod.idemia.com/mestafocus branches/main/main amd64 x-ntp all 1.5-2804-5248a1af [14.1 kB]
Fetched 14.1 kB in 0s (342 kB/s)  
Beginning to order
Done ordering
  SmartUnPack x-ntp:amd64 (replace version 1.3-20250918111734 with 1.5-2804-5248a1af)
  PreDepends order for x-ntp:amd64
  Found ok package x-fusion-base:amd64
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 90641 files and directories currently installed.)
Preparing to unpack .../x-ntp_1.5-2804-5248a1af_all.deb ...
got from dpkg 'processing: upgrade: x-ntp'
D000200: process_archive conffile '/etc/bashrc.d/60-x-ntp' in package x-ntp:all - conff ?
D000020: process_archive conffile '/etc/bashrc.d/60-x-ntp' package=x-ntp:all same hash=3225b8adf1b814da634112c9856b88a0
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-common.conf' in package x-ntp:all - conff ?
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-common.conf' in package x-ntp:all - conff ? not '/etc/bashrc.d/60-x-ntp'
D000020: process_archive conffile '/etc/chrony/x-ntp/utl-common.conf' package=x-ntp:all same hash=e3e8002d5fb4764a34c26dda7978eb3f
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-image.conf' in package x-ntp:all - conff ?
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-image.conf' in package x-ntp:all - conff ? not '/etc/bashrc.d/60-x-ntp'
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-image.conf' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-common.conf'
D000020: process_archive conffile '/etc/chrony/x-ntp/utl-image.conf' package=x-ntp:all same hash=252b05ab52bf6802cd61d2a47a6d5890
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-infra.conf' in package x-ntp:all - conff ?
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-infra.conf' in package x-ntp:all - conff ? not '/etc/bashrc.d/60-x-ntp'
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-infra.conf' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-common.conf'
D000200: process_archive conffile '/etc/chrony/x-ntp/utl-infra.conf' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-image.conf'
D000020: process_archive conffile '/etc/chrony/x-ntp/utl-infra.conf' package=x-ntp:all same hash=9e55a85dead233239a86f204453ed488
D000200: process_archive conffile '/etc/sudoers.d/x-ntp' in package x-ntp:all - conff ?
D000200: process_archive conffile '/etc/sudoers.d/x-ntp' in package x-ntp:all - conff ? not '/etc/bashrc.d/60-x-ntp'
D000200: process_archive conffile '/etc/sudoers.d/x-ntp' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-common.conf'
D000200: process_archive conffile '/etc/sudoers.d/x-ntp' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-image.conf'
D000200: process_archive conffile '/etc/sudoers.d/x-ntp' in package x-ntp:all - conff ? not '/etc/chrony/x-ntp/utl-infra.conf'
D000020: process_archive conffile '/etc/sudoers.d/x-ntp' package=x-ntp:all same hash=54913e6a346cc0b8326f062f346a95ea
D000200: pkg_conffiles_mark_old '/etc/bashrc.d/60-x-ntp' namenode '/etc/bashrc.d/60-x-ntp' flags 5
D000200: pkg_conffiles_mark_old '/etc/chrony/x-ntp/utl-common.conf' namenode '/etc/chrony/x-ntp/utl-common.conf' flags 5
D000200: pkg_conffiles_mark_old '/etc/chrony/x-ntp/utl-image.conf' namenode '/etc/chrony/x-ntp/utl-image.conf' flags 5
D000200: pkg_conffiles_mark_old '/etc/chrony/x-ntp/utl-infra.conf' namenode '/etc/chrony/x-ntp/utl-infra.conf' flags 5
D000200: pkg_conffiles_mark_old '/etc/sudoers.d/x-ntp' namenode '/etc/sudoers.d/x-ntp' flags 5
got from dpkg 'status: x-ntp: half-configured'
(parsed from dpkg) pkg: x-ntp:amd64 action: half-configured (expected: 'half-installed' 0 of 4)
                                                                                                                                             got from dpkg 'status: x-ntp: unpacked'
                                                                                                                                                                                    (parsed from dpkg) pkg: x-ntp:amd64 action: unpacked (expected: 'half-installed' 0 of 4)
                                                                                     got from dpkg 'status: x-ntp: half-installed'
                                                                                                                                  (parsed from dpkg) pkg: x-ntp:amd64 action: half-installed (expected: 'half-installed' 0 of 4)
Unpacking x-ntp (1.5-2804-5248a1af) over (1.3-20250918111734) ...
D000200: conffderef in='/etc/bashrc.d/60-x-ntp' current working='/etc/bashrc.d/60-x-ntp'
D000020: conffderef in='/etc/bashrc.d/60-x-ntp' result='/etc/bashrc.d/60-x-ntp'
D000020: tarobject FNNF_NEW_CONFF deref='/etc/bashrc.d/60-x-ntp'
D000200: tarobject conffile extracted
D000200: conffderef in='/etc/chrony/x-ntp/utl-common.conf' current working='/etc/chrony/x-ntp/utl-common.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-common.conf' result='/etc/chrony/x-ntp/utl-common.conf'
D000020: tarobject FNNF_NEW_CONFF deref='/etc/chrony/x-ntp/utl-common.conf'
D000200: tarobject conffile extracted
D000200: conffderef in='/etc/chrony/x-ntp/utl-image.conf' current working='/etc/chrony/x-ntp/utl-image.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-image.conf' result='/etc/chrony/x-ntp/utl-image.conf'
D000020: tarobject FNNF_NEW_CONFF deref='/etc/chrony/x-ntp/utl-image.conf'
D000200: tarobject conffile extracted
D000200: conffderef in='/etc/chrony/x-ntp/utl-infra.conf' current working='/etc/chrony/x-ntp/utl-infra.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-infra.conf' result='/etc/chrony/x-ntp/utl-infra.conf'
D000020: tarobject FNNF_NEW_CONFF deref='/etc/chrony/x-ntp/utl-infra.conf'
D000200: tarobject conffile extracted
D000200: conffderef in='/etc/sudoers.d/x-ntp' current working='/etc/sudoers.d/x-ntp'
D000020: conffderef in='/etc/sudoers.d/x-ntp' result='/etc/sudoers.d/x-ntp'
D000020: tarobject FNNF_NEW_CONFF deref='/etc/sudoers.d/x-ntp'
D000200: tarobject conffile extracted
D000200: pkg_remove_old_files: removing conffile '/etc/bashrc.d/60-x-ntp' for x-ntp:all?
D000200: pkg_remove_old_files: removing conffile '/etc/chrony/x-ntp/utl-common.conf' for x-ntp:all?
D000200: pkg_remove_old_files: removing conffile '/etc/chrony/x-ntp/utl-image.conf' for x-ntp:all?
D000200: pkg_remove_old_files: removing conffile '/etc/chrony/x-ntp/utl-infra.conf' for x-ntp:all?
D000200: pkg_remove_old_files: removing conffile '/etc/sudoers.d/x-ntp' for x-ntp:all?
got from dpkg 'status: x-ntp: unpacked'
(parsed from dpkg) pkg: x-ntp:amd64 action: unpacked (expected: 'unpacked' 1 of 4)
                                                                                                                         Setting up x-ntp (1.5-2804-5248a1af) ...
got from dpkg 'processing: configure: x-ntp'
got from dpkg 'status: x-ntp: unpacked'
                                                                                   (parsed from dpkg) pkg: x-ntp:amd64 action: unpacked (expected: 'half-configured' 2 of 4)
                                                                                                                                                                            D000200: conffderef in='/etc/bashrc.d/60-x-ntp' current working='/etc/bashrc.d/60-x-ntp'
D000020: conffderef in='/etc/bashrc.d/60-x-ntp' result='/etc/bashrc.d/60-x-ntp'
D000020: deferred_configure '/etc/bashrc.d/60-x-ntp' (= '/etc/bashrc.d/60-x-ntp') useredited=-1 distedited=-1 what=2
D000200: conffderef in='/etc/chrony/x-ntp/utl-common.conf' current working='/etc/chrony/x-ntp/utl-common.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-common.conf' result='/etc/chrony/x-ntp/utl-common.conf'
D000020: deferred_configure '/etc/chrony/x-ntp/utl-common.conf' (= '/etc/chrony/x-ntp/utl-common.conf') useredited=-1 distedited=-1 what=2
D000200: conffderef in='/etc/chrony/x-ntp/utl-image.conf' current working='/etc/chrony/x-ntp/utl-image.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-image.conf' result='/etc/chrony/x-ntp/utl-image.conf'
D000020: deferred_configure '/etc/chrony/x-ntp/utl-image.conf' (= '/etc/chrony/x-ntp/utl-image.conf') useredited=-1 distedited=-1 what=2
D000200: conffderef in='/etc/chrony/x-ntp/utl-infra.conf' current working='/etc/chrony/x-ntp/utl-infra.conf'
D000020: conffderef in='/etc/chrony/x-ntp/utl-infra.conf' result='/etc/chrony/x-ntp/utl-infra.conf'
D000020: deferred_configure '/etc/chrony/x-ntp/utl-infra.conf' (= '/etc/chrony/x-ntp/utl-infra.conf') useredited=1 distedited=0 what=2
D000200: conffderef in='/etc/sudoers.d/x-ntp' current working='/etc/sudoers.d/x-ntp'
D000020: conffderef in='/etc/sudoers.d/x-ntp' result='/etc/sudoers.d/x-ntp'
D000020: deferred_configure '/etc/sudoers.d/x-ntp' (= '/etc/sudoers.d/x-ntp') useredited=-1 distedited=-1 what=2
got from dpkg 'status: x-ntp: half-configured'
(parsed from dpkg) pkg: x-ntp:amd64 action: half-configured (expected: 'half-configured' 2 of 4)
                                                                                                                                              got from dpkg 'status: x-ntp: installed'

And I am pretty sure file is detected as a conffile, and has been localy modified:

# dpkg --status x-ntp | grep utl-infra.conf; md5sum /etc/chrony/x-ntp/utl-infra.conf
 /etc/chrony/x-ntp/utl-infra.conf 9e55a85dead233239a86f204453ed488
c95324d1befd427a7e4c9686fc86a5cd  /etc/chrony/x-ntp/utl-infra.conf

I did an additional test to compare results of following 2 commands (the first one does not overwrite conffile changes, the second does):

  1. apt-get ... -o Dpkg::Options="--force-confnew" -o Dpkg::Options="--force-confmiss" -o Dpkg::Options="--force-confask" install x-ntp=1.3-20250918111734

  2. dpkg -i --force-confnew --force-confmiss --force-confask ./x-ntp_1.3-20250918111734_all.deb

Only noticeable differences in dpkg debug logs are on line

with apt: D000020: deferred_configure '/etc/chrony/x-ntp/utl-infra.conf' (= '/etc/chrony/x-ntp/utl-infra.conf') useredited=1 distedited=0 what=2

with dpkg: D000020: deferred_configure '/etc/chrony/x-ntp/utl-infra.conf' (= '/etc/chrony/x-ntp/utl-infra.conf') useredited=1 distedited=0 what=3

Note that this 'x-ntp' package is a proprietary package that we developped internaly. But is has nothing special, it just installs a couple of files to /etc and /usr, it does not have any: pre/postinst, pre/postrm, service, triggers, diverts ... . It is successfully installed and files copied to /etc are correctly detected by dpkg as conffiles, so I do not think the issue is anywhere inside this package (unless something special needs to be declared for config files if you need them to be correctly overwritten when using --force-confnew).

Canon printer driver cnijfilter2-5.90-1-deb fails to install on 25.10 with dependecy on libxml2 https://askubuntu.com/questions/1558980/canon-printer-driver-cnijfilter2-5-90-1-deb-fails-to-install-on-25-10-with-depen

I have a brand new Xubuntu 25.10 system. Canon printer driver cnijfilter2-5.90-1-deb fails to install with dependency on libxml2.

The install.sh script says it wants libxml2 >= 2.7.4 But dpkg appears to show libxml2 2.14.5+dfsg-0.2 which is higher than 2.7.4

This worked on all earlier versions of *ubuntu that I've tried. 25.04, 24.10, even 16.04.

Typescript from the installation is below.

If anyone can suggest a solution, I'd appreciate any hints or tips.

Thank you for reading this

leon
# cat /etc/os-release
PRETTY_NAME="Ubuntu 25.10"
 . . .

# cd cnijfilter2-5.90-1-deb

# ./install.sh
==================================================

Canon Inkjet Printer Driver
Version 5.90
Copyright CANON INC. 2001-2019

==================================================
Command executed = sudo dpkg -iG ./packages/cnijfilter2_5.90-1_amd64.deb
Selecting previously unselected package cnijfilter2.
 . . .
Preparing to unpack .../cnijfilter2_5.90-1_amd64.deb ...
Unpacking cnijfilter2 (5.90-1) ...
dpkg: dependency problems prevent configuration of cnijfilter2:
 cnijfilter2 depends on libxml2 (>= 2.7.4); however:
  Package libxml2 is not installed.

dpkg: error processing package cnijfilter2 (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 cnijfilter2
Command executed = sudo dpkg -P cnijfilter2
 . . .
Removing cnijfilter2 (5.90-1) ...
Purging configuration files for cnijfilter2 (5.90-1) ...
Processing triggers for libc-bin (2.42-0ubuntu3) ...

# dpkg -l | grep --colour=never xml2
ii  libxml-libxml-perl                       2.0207+dfsg+really+2.0207-0ubuntu6         amd64        Perl interface to the libxml2 library
ii  libxml2-16:amd64                         2.14.5+dfsg-0.2                            amd64        GNOME XML library
ii  libxml2-utils                            2.14.5+dfsg-0.2                            amd64        GNOME XML library - utilities
ii  python3-libxml2                          2.14.5+dfsg-0.2                            amd64        GNOME XML library - Python3 bindings
ii  python3-lxml:amd64                       6.0.1-1                                    amd64        pythonic binding for the libxml2 and libxslt libraries
kerneloops, chrome-gnome-shell, policykit-1 packages are not available in 25.04 https://askubuntu.com/questions/1547844/kerneloops-chrome-gnome-shell-policykit-1-packages-are-not-available-in-25-04

After upgrading my system from Ubuntu 24.10 to 25.04, the command:

$ pro security-status --unavailable

lists (among the known, manually installed packages by me) the following packages too: kerneloops, chrome-gnome-shell, and policykit-1.

I get the same list using the command:

$ apt --installed list | grep ,local

Doing a search in https://packages.ubuntu.com/ reveals also that these are not available in plucky.

What is the recommended action?


Comments for @heynnema :

The package policykit-1 is still installed on my system:

$ apt --installed list | grep -i policykit

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

policykit-1-gnome/plucky,now 0.105-8 amd64 [installed,automatic]
policykit-1/now 124-2ubuntu1.24.10.2 amd64 [installed,local]
policykit-desktop-privileges/plucky,plucky,now 0.22 all [installed]

And I have the following:

$ systemctl status polkit.service 
● polkit.service - Authorization Manager
     Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
     Active: active (running) since Tue 2025-07-22 10:55:44 +03; 1h 5min ago
 Invocation: cb0b9ba7d5cb46f68bc1d20b6dee8298
       Docs: man:polkit(8)
   Main PID: 1686 (polkitd)
     Status: "Processing requests..."
      Tasks: 4 (limit: 27937)
     Memory: 6.9M (peak: 7.7M)
        CPU: 762ms
     CGroup: /system.slice/polkit.service
             └─1686 /usr/lib/polkit-1/polkitd --no-debug --log-level=notice

Jul 22 10:55:44 xxx polkitd[1686]: Error opening rules directory: Error opening directory “/run/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /usr/local/share/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Error opening rules directory: Error opening directory “/usr/local/share/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /usr/share/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Finished loading, compiling and executing 16 rules
Jul 22 10:55:44 xxx systemd[1]: Started polkit.service - Authorization Manager.
Jul 22 10:55:44 xxx polkitd[1686]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jul 22 10:55:49 xxx polkitd[1686]: Registered Authentication Agent for unix-session:c2 (system bus name :1.59 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent,>
Jul 22 10:55:58 xxx polkitd[1686]: Registered Authentication Agent for unix-session:3 (system bus name :1.103 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent,>
Jul 22 10:56:05 xxx polkitd[1686]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.59, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) >


$ journalctl -t polkitd -b0
Jul 22 10:55:44 xxx polkitd[1686]: Started polkitd version 126
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /etc/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /run/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Error opening rules directory: Error opening directory “/run/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /usr/local/share/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Error opening rules directory: Error opening directory “/usr/local/share/polkit-1/rules.d”: No such file or directory (g-file-error-quark, 4)
Jul 22 10:55:44 xxx polkitd[1686]: Loading rules from directory /usr/share/polkit-1/rules.d
Jul 22 10:55:44 xxx polkitd[1686]: Finished loading, compiling and executing 16 rules
Jul 22 10:55:44 xxx polkitd[1686]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jul 22 10:55:49 xxx polkitd[1686]: Registered Authentication Agent for unix-session:c2 (system bus name :1.59 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 22 10:55:58 xxx polkitd[1686]: Registered Authentication Agent for unix-session:3 (system bus name :1.103 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Jul 22 10:56:05 xxx polkitd[1686]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.59, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)


Note: Upgrading to 25.10 from 25.04 did not change anything mentioned above.

Screen problem on Ubuntu 24.04.1 LTS https://askubuntu.com/questions/1540735/screen-problem-on-ubuntu-24-04-1-lts

I have a fresh install of Ubuntu 24.04 LTS on computer with internal RocketLake-S GT1 [Intel UHD Graphics 730]. (I tried Ubuntu 22.04 from USB flash with the same result).

The problem is that after ~5 seconds of idle, the screen (even login screen) begin to blink until I move a mouse or begin to type. It looks like screen changes the refresh rate to unsupported one and loose the Sync.

In Settings/Display I have three options: 60, 59.93 and 50 Hz. First two works fine, but 50Hz results in the same blinking (that's why I think about switching refresh rate).

Could anyone help?

I tried to make a *.conf file in /etc/X11/xorg.conf.d/ but without visible effect (may be I did something wrong). And I don't understand why Settings/Display suggests 50Hz, while xrandr do not display such frequency?

I also tried to add "nomodeset i915.enable_dc=0 intel_idle.max_cstate=2" to GRUB_CMDLINE_LINUX_DEFAULT in grub - without result

Installer keeps disappearing on dual boot installation https://askubuntu.com/questions/1534661/installer-keeps-disappearing-on-dual-boot-installation

When installing the latest download of Ubuntu Desktop 24.04.1 on a machine that already has a Windows 10 installation, during filling in the installation wizard with the information, on the left suddenly mounted disks appear and the installer disappears. This makes it impossible to install Ubuntu 24.04.1.

The windows 10 installation is GPT, fast boot is disabled and UEFI enabled. Installing Ubuntu 22.04 works just fine but installing an older version and updating it to 24.04 is not my preferred way of installing.

Any help would be appreciated.

dotnet7 in Noble? https://askubuntu.com/questions/1511585/dotnet7-in-noble

I'm looking for dotnet7 or dotnet-sdk-7.0 in my (just installed, release build of) 24.04 repositories, so far apt-get tells me "Unable to locate package..."

How can I get dotnet7 in Noble?

Thanks,

dotnet complaining that libhostpolicy.so doesn't exist, even though it does https://askubuntu.com/questions/1480656/dotnet-complaining-that-libhostpolicy-so-doesnt-exist-even-though-it-does

When I try to run a program using dotnet I get this error:

> dotnet OmniSharp.exe
A fatal error was encountered. The library 'libhostpolicy.so' required to execute the application was not found in 'path/to/exe'.
Failed to run as a self-contained app.

I found the file libhostpolicy.so in /usr/lib/dotnet/shared/Microsoft.NETCore.App/7.0.9/libhostpolicy.so, so I have no idea why dotnet can't access it.

I read on here that doing this will solve it:

sudo chown -R yourusername:yourusername /path/to/exe
sudo setfacl -R -d -m u:yourusername:rwx,g:yourusername:rwx,o::r /path/to/exe

but I still get the same error.

.sh executable asking for definition for INSTALL4J_JAVA_HOME path to jvm https://askubuntu.com/questions/1370461/sh-executable-asking-for-definition-for-install4j-java-home-path-to-jvm

I want to run a .sh executable to install software but when I try to execute the file using ./<fileName> in my terminal, following error message appears:

No suitable Java Virtual Machine could be found on your system. The version of the JVM must be 1.8. Please define INSTALL4J_JAVA_HOME to point to a suitable JVM.

  1. How does one check the JVM version on the device?
  2. If the JVM isn't version 1.8, how can one install JVM 1.8?
  3. How does one define INSTALL4J_JAVA_HOME to point to the JVM?
lm-sensors not showing information https://askubuntu.com/questions/1254919/lm-sensors-not-showing-information

After running sensors-detect and using all default settings, when running sensors I do not get a lot of information:

schoolbusesc2@desktop:~$ sensors
enp4s0-pci-0400
Adapter: PCI adapter
PHY Temperature:  +45.9°C  

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:        +44.0°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +55.8°C  (high = +70.0°C)
Tctl:         +55.8°C  

How will I be able to find the:

  • Fan speed
  • Voltages
  • CPU clock speed
  • Etc.

Please tell me if you need more information.

Thanks,
Owen

EDIT:
Here is sensors-detect:

schoolbusesc2@desktop:~$ sudo sensors-detect
[sudo] password for schoolbusesc2: 
# sensors-detect version 3.6.0
# Board: ASUSTeK COMPUTER INC. ROG CROSSHAIR VIII FORMULA
# Kernel: 5.4.0-40-generic x86_64
# Processor: AMD Ryzen 7 3700X 8-Core Processor (23/113/0)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Nuvoton NCT6798D Super IO Sensors'                   Success!
    (address 0x290, driver `nct6775')
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): 
Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus

Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0)
Do you want to scan it? (YES/no/selectively): 
Client found at address 0x1a
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `ST STTS424'...                                 No
Probing for `ST STTS424E'...                                No
Probing for `ST STTS2002'...                                No
Probing for `ST STTS3000'...                                No
Probing for `NXP SE97/SE97B'...                             No
Probing for `NXP SE98'...                                   No
Probing for `Analog Devices ADT7408'...                     No
Probing for `IDT TS3000/TSE2002'...                         No
Probing for `IDT TSE2004'...                                No
Probing for `IDT TS3001'...                                 No
Probing for `Maxim MAX6604'...                              No
Probing for `Microchip MCP9804'...                          No
Probing for `Microchip MCP9808'...                          No
Probing for `Microchip MCP98242'...                         No
Probing for `Microchip MCP98243'...                         No
Probing for `Microchip MCP98244'...                         No
Probing for `Microchip MCP9843'...                          No
Probing for `ON CAT6095/CAT34TS02'...                       No
Probing for `ON CAT34TS02C'...                              No
Probing for `ON CAT34TS04'...                               No
Probing for `Atmel AT30TS00'...                             No
Probing for `Giantec GT30TS00'...                           No
Client found at address 0x1b
Probing for `ST STTS424'...                                 No
Probing for `ST STTS424E'...                                No
Probing for `ST STTS2002'...                                No
Probing for `ST STTS3000'...                                No
Probing for `NXP SE97/SE97B'...                             No
Probing for `NXP SE98'...                                   No
Probing for `Analog Devices ADT7408'...                     No
Probing for `IDT TS3000/TSE2002'...                         No
Probing for `IDT TSE2004'...                                No
Probing for `IDT TS3001'...                                 No
Probing for `Maxim MAX6604'...                              No
Probing for `Microchip MCP9804'...                          No
Probing for `Microchip MCP9808'...                          No
Probing for `Microchip MCP98242'...                         No
Probing for `Microchip MCP98243'...                         No
Probing for `Microchip MCP98244'...                         No
Probing for `Microchip MCP9843'...                          No
Probing for `ON CAT6095/CAT34TS02'...                       No
Probing for `ON CAT34TS02C'...                              No
Probing for `ON CAT34TS04'...                               No
Probing for `Atmel AT30TS00'...                             No
Probing for `Giantec GT30TS00'...                           No
Client found at address 0x52
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Client found at address 0x77
Probing for `Asus Mozart-2'...                              No

Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA GPU I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): 

Next adapter: NVIDIA i2c adapter 1 at a:00.0 (i2c-3)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x2a
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM96080'...             No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Nuvoton NCT7802Y'...                           No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Analog Devices ADM1021'...                     No
Probing for `Analog Devices ADM1021A/ADM1023'...            No
Probing for `Maxim MAX1617'...                              No
Probing for `Maxim MAX1617A'...                             No
Probing for `Maxim MAX1668'...                              No
Probing for `Maxim MAX1805'...                              No
Probing for `Maxim MAX1989'...                              No
Probing for `Maxim MAX6655/MAX6656'...                      No
Probing for `TI THMC10'...                                  No
Probing for `National Semiconductor LM84'...                No
Probing for `Genesys Logic GL523SM'...                      No
Probing for `Onsemi MC1066'...                              No
Probing for `Maxim MAX1618'...                              No
Probing for `Maxim MAX1619'...                              No
Probing for `National Semiconductor LM82/LM83'...           No
Probing for `Maxim MAX6654'...                              No
Probing for `Maxim MAX6690'...                              No
Probing for `Maxim MAX6680/MAX6681'...                      No
Probing for `Maxim MAX6695/MAX6696'...                      No
Probing for `Texas Instruments TMP400'...                   No
Probing for `Texas Instruments TMP421'...                   No
Probing for `Texas Instruments TMP441'...                   No
Probing for `National Semiconductor LM95231'...             No
Probing for `National Semiconductor LM95233'...             No
Probing for `National Semiconductor LM95241'...             No
Probing for `Analog Devices ADM1029'...                     No
Probing for `ITE IT8712F'...                                No

Next adapter: NVIDIA i2c adapter 3 at a:00.0 (i2c-4)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: NVIDIA i2c adapter 5 at a:00.0 (i2c-5)
Do you want to scan it? (yes/NO/selectively): yes
Client found at address 0x58
Probing for `Analog Devices ADT7462'...                     No
Probing for `Andigilog aSC7512'...                          No
Client found at address 0x5c
Probing for `Analog Devices ADT7462'...                     No
Probing for `SMSC EMC1072'...                               No
Probing for `SMSC EMC1073'...                               No
Probing for `SMSC EMC1074'...                               No

Next adapter: NVIDIA i2c adapter 6 at a:00.0 (i2c-6)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: NVIDIA i2c adapter 7 at a:00.0 (i2c-7)
Do you want to scan it? (yes/NO/selectively): yes

Next adapter: NVIDIA i2c adapter 8 at a:00.0 (i2c-8)
Do you want to scan it? (yes/NO/selectively): yes


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `k10temp' (autoloaded):
  * Chip `AMD Family 17h thermal sensors' (confidence: 9)

Driver `nct6775':
  * ISA bus, address 0x290
    Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
nct6775
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)yes
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK

schoolbusesc2@desktop:~$ 
Microdia webcam not seen on Dell Laptop https://askubuntu.com/questions/1245009/microdia-webcam-not-seen-on-dell-laptop

Using Xubuntu 18.04 on a Dell laptop that does not have a web camera. I bought an external webcam that advertised as being compatible with ubuntu. Plugged in, lsusb sees it, but it will not show an image on cheese.

Bus 002 Device 013: ID 0c45:6366 Microdia 

I think the video driver for the camera is not present.

How do I get/make the appropriate service to use the web camera?
Or is these some other solution to the problem?

Screen flickering on dual boot Ubuntu https://askubuntu.com/questions/1179229/screen-flickering-on-dual-boot-ubuntu

I have dual boot setting (Ubuntu 16.04 + Windows 10) on my notebook (using nouveau driver). Originally there was no major issues, but when I changed my BIOS configuration, my Ubuntu started to have screen flickering after boot in GRUB menu. All other things function properly in Ubuntu GUI, but the screen keeps flickering that I can hardly navigate. I encountered the same screen-flickering issue when booting in live USB. On windows side, everything is still fine and I can switch between integrated graphics card and my discrete graphics card.

I didn't find any similar situation as mine on my first attempt of internet search. Do anyone have any idea how to fix it?

Hardware specs:

  • Lenovo Legion Y740
  • Integrated Graphics Card: UHD Intel Graphics 630
  • GeForce RTX 2070 Max-Q
  • Both Ubuntu 16.04 and Windows installed in C:\

BIOS Configuration** (Updated in 12/10/2019):

In my first dual boot attempt, I navigate to BIOS settings via "UEFI Firmware settings" in Windows "Advanced Startup" (attached below). The change I made on the BIOS configuration are the following:

  • Secure Boot: Disabled (default is enabled)
  • Storage mode: AHCI mode (default is RST mode)
  • Graphics: default is "Discrete Graphics". I stuck with default "Discrete Graphics" in my first dual boot. No screen flickering appear on fresh installation. But when I set to "Switchable Graphics" after the installation, I was greeted with screen flickering in my Ubuntu side (everything is fine on Windows side)

UEFI Firmware Settings:

UEFI Firmware Settings Screenshot

[Update: 07/10/2019]
After a few study, I added "nomodeset" on grub configuration file and it temporarily settles the issue, but it is not desirable in the long run because such configuration disables brightness adjustment on screen and HDMI connection. I will keep looking for a more sustainable solution.

[Update: 12/10/2019 - 1]

I replaced Ubuntu 16.04 with Ubuntu 18.04. On fresh installation, screen flickering still existed but setting "nomodeset" in grub configuration file temporarily settles the issue. After I installed proprietary NVIDIA driver, screen flickering still persist and in this case setting "nomodeset" in grub config didn't solve the problem. But a good news is I finally escaped the black screen nightmare and infinite login loop nightmare this time. However, screen flickering is still an annoying issue to be settled.
I tried blacklist nouveau and setting nvidia_drm modeset = 1. But the issues still persist. I will keep trying different solutions to settle that.

[Update: 12/10/2019 - 2]

On Ubuntu side, my current state is that I have uninstalled proprietary nvidia driver by the following:

sudo apt-get purge nvidia  
sudo apt autoremove  
sudo apt autoclean  

I also blacklisted nouveau drive in /etc/modprobe.d/blacklist-nvidia-nouveau.conf with the following lines:

blacklist nouveau  
options nouveau modeset=0  

With such state, screen flickering issue existed and HDMI connection didn't work. And then, I followed David suggestion to set graphics mode back to default "Discrete Graphics" in BIOS configuration. Screen flickering issue disappear. I then proceed to install proprietary NVIDIA driver again by the following steps:

  1. setting "Main Server" in software updates
  2. execute sudo apt-get update (sudo add-apt-repository ppa:graphics-drivers/ppa has been executed a few days ago)
  3. install proprietary nvidia driver 435 in "Additional Drivers" tab. (as shown below)

After the Nvidia driver installation, I didn't encounter any screen flickering issue after Ubuntu reboot, also HDMI connection seems working. HOWEVER, I got stuck in a purple screen after login page, as shown below. I can navigate to tty by Alt + Ctrl + F6. When I execute nvidia-smi, my GPU device can be detected (as shown below)

Additional Drivers tab (showing how I installed the Nvidia driver:

1. Additional Driver Tab (showing how I install nvidia driver)

After nvidia driver installation, I got stuck in purple screen after login, the picture also shows HDMI works after the installation.

2. After nvidia driver installation, I got stuck in purple screen after login, the picture also shows HDMI works after the installation

When I got stuck at a purple screen, I tried to press Ctrl + Alt + F7, I then got to a black screen.

3. When I got stuck at a purple screen, I tried to press Ctrl + Alt + F7, I then got to a black screen.

nvidia-smi can detect my GPU (in execute this in my TTY mode.

4. nvidia-smi can detect my GPU (in execute this in my tty mode)

[Update: 12/10/2019 - 3]

Stuck in post-login for a few times, I tried to install KDE desktop in tty mode (by sudo apt-get install kubuntu-desktop). After rebooting I could finally get into desktop, but the screen flickering problem came again when I got into KDE desktop, however the screen flickering issue in KDE didn't appear as serious as the one in GNOME.
I tried changing a few configurations in System Setting -> Hardware > Display and Monitor -> Compositor. It is suggested from Flickering in KDE Plasma 5.4, but it didn't help.

bionic: dpkg options does not work using apt-get dist-upgrade https://askubuntu.com/questions/1102783/bionic-dpkg-options-does-not-work-using-apt-get-dist-upgrade

The options force-confdef and force-confold that worked fine in 14.04 and 16.04 seems not to work in 18.04 any more. Neither apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" dist-upgrade -y nor setting the options in /etc/apt/apt.conf.d/local or /etc/dpkg/dpkg.cfg are working.

/etc/apt/apt.conf.d/local:

Dpkg::Options {
  "--force-confdef";
  "--force-confold";
};

/etc/dpkg/dpkg.cfg:

force-confdef
force-confold

There is always a dialog popping up which makes any kind of automation impossible. Is there an other way for doing that? Is it a bug?

18.04, Slow boot and black screen on boot before reaching login splash https://askubuntu.com/questions/1053531/18-04-slow-boot-and-black-screen-on-boot-before-reaching-login-splash

Xubuntu 18.04, 4.15.0-24-generic, ThinkPad T430. Uses Intel HD iGPU graphics (nvidia dGPU disabled in BIOS).

Recently started having this issue with a slow boot, where the boot process hangs on a black screen for an indefinite period of time before finally displaying the normal login splash screen.

Process looks like:

  • OEM Bios select screen
  • blank, black screen (< 1 sec)
  • Blue Xubuntu title splash (< 2 sec)
  • Some grub printout (< 1 sec)
  • A black screen that has a blinking white cursor block (< 1 sec)
  • A blank, black screen with nothing on it (approx. 10 sec)
  • Finally, login splash screen

No idea why it started doing this. Was working fine before. The only thing I've noticed, which may be a red herring or irrelevant, is that there have been a bunch of updates to the mesa package lately when I apt update and upgrade.

Most other posts I've seen related to a hanging black screen on boot are either ancient (12.04) or unrelated (stuck on grub, or the flashing-cursor screen instead of blank). Though it seems like most of those posts are related to editing the grub file (/etc/default/grub line GRUB_CMDLINE_LINUX_DEFAULT).

Any ideas?

For reference, my grub file reads:

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nouveau.runpm=0"
GRUB_CMDLINE_LINUX=""

and the relevant output of lscpi -k

lspci -k
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
Subsystem: Lenovo 3rd Gen Core processor Graphics Controller
Kernel driver in use: i915
Kernel modules: i915

Things I've tried:

  • change GRUB_CMDLINE_LINUX_DEFAULT to "quiet splash instead of "quiet splash nouveau.runpm=0"
  • GRUB_TIMEOUT=0 instead of 10
  • updating mesa, xserver-xorg-video-intel packages, both already installed and current
  • updating kernel (was already at latest, 4.15.0-24-generic)

Update:

Unfortunately was not able to figure out the source of the issue. I tried nearly every permutation of grub settings, but that did not end up changing the hanging boot issue. My guess it is probably related to the 4.15.0-24-generic. Decided to reinstall Xubuntu 16.04 for this issue and a few more I've had with 18.04.

If anyone else is experiencing this hanging boot issue and solved the issue, please provide your solution for others (and possibly me if I decide to roll the dice again when Xubuntu 18.04.1 drops).

Firefox very slow to start https://askubuntu.com/questions/853863/firefox-very-slow-to-start

I have a new computer with Ubuntu 16.04 LTS installed.

When launching firefox, I have to wait several minutes for the start page to appear. I just have this:

enter image description here

Once I'm finally on the start page, the navigation is perfectly normal. I tried to reinstall firefox and to run it on safemode, but none of these solved my problem. I first thought it was a connection problem, but it's not, since Chromium works just fine.

Unable to load mod_alias in apache https://askubuntu.com/questions/679672/unable-to-load-mod-alias-in-apache

Runing the command sudo service apache2 restart output :

 * Restarting web server apache2                                         [fail] 

* The apache2 configtest failed.

Output of config test was:
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/alias.load: Cannot load /usr/lib/apache2/modules/mod_alias.so into server: /usr/lib/apache2/modules/mod_alias.so: cannot open shared object file: No such file or directory
Action 'configtest' failed.
The Apache error log may have more information.

How to solve it?

Fix the USB error "There is no disk in the drive. Please insert a disk into drive X" https://askubuntu.com/questions/651611/fix-the-usb-error-there-is-no-disk-in-the-drive-please-insert-a-disk-into-driv

I have a 32GB USB Pen Drive which has gone dead (USB drive unusable, unformattable, and reporting 0 bytes capacity). It is not accessible through any OS. When I insert it into my Windows machine and try to open it, it pops up the following message

"There is no disk in the drive. Please insert a disk into drive X."

I've tried almost everything, but can't fix it. What I've tried until now:

  1. Change Drive Letter and Path - http://www.verbatim.com/index/support.php?cat=14&action=support_questions&pid=5467&aid=165
  2. Re-installed the USB Controllers in windows
  3. Tried changing the DisableOnSoftRemove vale in regedit - https://support.microsoft.com/en-us/kb/2830154
  4. Tried a number of software utilities for windows that helps in force formatting a pen drive.

Further, I tried using the Disks program from the dash as well (in Ubuntu 14.04 LTS). It shows up my USB Flash drive when I plug it in, but I can't format it or mount it anyhow. Here are the screenshots for the same:- enter image description here enter image description here When I Click on the Edit Mount Options, the following Windows pops up: enter image description here

Is there any way I can recover my Pen Drive back?

PS:- I do not want the contents, just I want to make my USB drive work again.

How to show (raise) all windows of an application? https://askubuntu.com/questions/446521/how-to-show-raise-all-windows-of-an-application

I have an application using multiple windows. How can I quickly bring all the windows of that application to the foreground?

When I scroll through the applications with the scroll-wheel it only shows one window. When going to the next window, the last window is brought to the background again.

When I click on the application icon, I get a full-screen overview of all the windows. I have to select each window manually and move my mouse across half the screen several times.

My best solution so far is minimizing all windows (Ctrl+Super+D) and then show the windows of my application using the scroll-wheel.

Is there a better solution?

Nicer FTP client than FileZilla? https://askubuntu.com/questions/109000/nicer-ftp-client-than-filezilla

FileZilla is really kind of "meh," when it comes to user interface. I'm wondering if there's something simpler/cleaner/slicker out there?