I run Ubuntu 24.04 (gnome 46) and I would like to connect a microscope digital camera to my laptop. I am also looking to measure part of the images so I need a calibration system. I am aware of micro manager but it requires compiling from source. Any easier options?
Ever since I updated from 22.04 to 24.04 some programs have this double border. If you click the buttons on the outer frame it crashes the desktop. I've tried purging and re-installing Budgie Desktop and that didn't fix it.
Does anyone know what's going on?
I tried to type Punjabi language in Text editor and LibreOffice Writer. I am facing an issue with typing because some of words are not typed like they are typed in Windows OS. Some words are opposite language input types than they are in Windows when I try to type them using the Shift key.
My hp zbook refuses to boot from a bootable ssb, secure booting disabled. UEFI enabled. USB boot option. Boot disk made with rufus for ubuntu. Any ideas?
I'm using Ubuntu 24.04, and after a recent software update, Chrome started using colorized digits, #, and *, and also using an extra-wide space in certain parts of its UI, including:
I'm not sure which part of the update caused this problem. I'd slacked off on updating for a few months, and just ran apt update; apt upgrade and rebooted.
I've found that uninstalling the Noto Color Emoji font fixes this issue...
sudo apt remove fonts-noto-color-emoji
...but it results in emoji being monochrome or nonexistent in many places.
Prior to this update I'd had Noto Color Emoji installed for years, and never had this problem in Chrome.
Is this a known issue? How can I have Noto Color Emoji installed, but stop Chrome from using it for ASCII characters?
A partial upgrade ended up removing LibreOffice. I tried to install it and got this:
sudo apt install libreoffice
Solving dependencies... Error!
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
Unsatisfied dependencies:
libreoffice : Depends: libreoffice-base but it is not going to be installed
Depends: libreoffice-calc but it is not going to be installed
Depends: libreoffice-core (= 4:25.8.2-0ubuntu0.25.10.1) but it is not going to be installed
Depends: libreoffice-draw but it is not going to be installed
Depends: libreoffice-impress but it is not going to be installed
Depends: libreoffice-math but it is not going to be installed
Depends: libreoffice-report-builder-bin but it is not going to be installed
Depends: libreoffice-writer but it is not going to be installed
Depends: python3-uno but it is not going to be installed
Recommends: libreoffice-gnome but it is not going to be installed or
libreoffice-plasma but it is not going to be installed
Recommends: libreoffice-nlpsolver but it is not going to be installed
Recommends: libreoffice-report-builder but it is not going to be installed
Recommends: libreoffice-script-provider-bsh but it is not going to be installed
Recommends: libreoffice-script-provider-js but it is not going to be installed
Recommends: libreoffice-script-provider-python but it is not going to be installed
Recommends: libreoffice-sdbc-mysql but it is not going to be installed
Recommends: libreoffice-sdbc-postgresql but it is not going to be installed
Recommends: libreoffice-wiki-publisher but it is not going to be installed
Recommends: libreoffice-java-common (>= 4:25.8.2~) but it is not going to be installed
Error: Unable to satisfy dependencies. Reached two conflicting decisions:
1. libreoffice-core:amd64=4:25.8.2-0ubuntu0.25.10.1 Depends libreoffice-sal-private-abi (= 25.8.2)
but none of the choices are installable:
- libuno-sal3t64:amd64=4:25.8.2-0ubuntu0.25.10.1 is not selected for install
2. libreoffice-core:amd64=4:25.8.2-0ubuntu0.25.10.1 is selected for install because:
1. libreoffice:amd64=4:25.8.2-0ubuntu0.25.10.1 is selected for install
2. libreoffice:amd64=4:25.8.2-0ubuntu0.25.10.1 Depends libreoffice-core (= 4:25.8.2-0ubuntu0.25.10.1)
How do I fix this?
Ref:
Having read numerous postings on the how, why, and wherefore packages might be "kept back" - and many of the reasons are valid - one question remains:
When apt/apt-get holds back a package, WHY was this particular package "kept back" and how do I find out what that reason is?
The answers seem to fall into two broad categories:
You don't want to know, you don't need to know, go away and stop bothering me.
Run [some command] and that will install the kept-back packages. (Without my understanding if there might have been a good reason to avoid installing them.)
I prefer a third option: Tell me why and let me decide for myself.
This is not Windows nor is it Apple and I would like to get the information I need and decide for myself. (Oh, it will end up borking [name of essential application], guess I'll skip that one!)
So, how do I find out exactly WHY a package or packages was/were held back so I can decide for myself.
Edit:
It has been mentioned that this or that related entry at the top of the question provides the correct answer.
I disagree. As far as I understand from reading the referenced articles several times, these provide the guidance that the answer MIGHT be one of several possibilities, but no definitive way to determine exactly WHY a particular package(s) were kept back.
Ergo, this question.
If one of the referenced postings does, in fact, answer this with a definite answer, would you please clarify and explain it so that others like myself can learn from your wisdom?
I want to upgrade my already unsupported Ubuntu 20.04 lts release to 22.04 lts but I'm facing a deal with "updating your package information".
When I try to upgrade using the command: sudo do-release-upgrade, here are the complete screen prints:
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [833 B]
Get:2 Upgrade tool [1.267 kB]
Fetched 1.268 kB in 0s (0 B/s)
authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg'
extracting 'jammy.tar.gz'
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://ubuntu.unc.edu.ar/ubuntu focal-security InRelease
Hit http://ubuntu.unc.edu.ar/ubuntu focal InRelease
Hit http://ubuntu.unc.edu.ar/ubuntu focal-updates InRelease
Hit http://ubuntu.unc.edu.ar/ubuntu focal-backports InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
nvidia-driver-570
Checking for installed snaps
Calculating snap size requirements
Updating repository information
Third party sources disabled
Some third party entries in your sources.list were disabled. You can
re-enable them after the upgrade with the 'software-properties' tool
or your package manager.
To continue please press [ENTER]
Fetched 0 B in 0s (0 B/s)
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Invalid package information
After updating your package information, the essential package
'ubuntu-minimal' could not be located. This may be because you have
no official mirrors listed in your software sources, or because of
excessive load on the mirror you are using. See /etc/apt/sources.list
for the current list of configured software sources.
In the case of an overloaded mirror, you may want to try the upgrade
again later.
What I have done so far:
Before upgrading, I ran: sudo apt-get update, sudo apt-get upgrade, sudo apt-get remove and sudo reboot.
Also, I disable the third-party repositories unchecking the boxes in Other Software's tap in "Software & Updates".
Following this post "Invalid package information" error when upgrading to Ubuntu 20.04 I ran sudo RELEASE_UPGRADER_ALLOW_THIRD_PARTY=1 do-release-upgrade with same result.
I also deleted all files at /var/lib/apt/lists, and updated all packages again by running sudo apt-get update. Same result.
Any ideas to help me?
Thank you!
I am unable to remove/uninstall Chromium from Ubuntu 20.04 due to the error below.
error: snap "chromium" has "remove-snap" change in progress
How do you fix this error?
This error is reproduced with the following commands.
sudo snap remove chromium
sudo snap remove chromium --purge
The following solutions did not work.
Rebooted 5 times
snap abort ID
Uninstalling through the Ubuntu Software window
Emptying these directories.
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
sudo fc-cache -r -v
rm -rf ~/snap/chromium/common/.cache/fontconfig/
Changed my clock 45 days forward. I read sometimes snap has a 30 day snapshot or something like that, so I thought jumping forward might help.
Used: snap set core snapshots.automatic.retention=no
Additional output if it helps.
snap list chromium
Name Version Rev Tracking Publisher Notes
chromium 144.0.7524.0 3308 latest/edge canonical✓ disabled,held
snap abort does not work
Many solutions recommend finding the ID of any snap actions with Status=Error (see the output below of snap changes) and doing a snap abort ID. This did not work for me because no snap action has Status=Error.
snap changes
ID Status Spawn Ready Summary
211 Done yesterday at 12:27 PST yesterday at 12:28 PST Pre-download "chromium" for auto-refresh
212 Done yesterday at 13:23 PST yesterday at 13:24 PST Auto-refresh snap "chromium"
213 Done yesterday at 17:45 PST yesterday at 17:46 PST Refresh "chromium" snap from "latest/edge" channel
214 Undo yesterday at 17:46 PST - Remove "chromium" snap
Background
I was delaying the update of Chromium for a few weeks. Last night, I closed all the Chromium windows and Chromium went into self update mode. After the update, Chromium could no longer open, so I made attempts to remove and revert to an older version of Chromium. During this process, the error message started to appear.
I’m working on a Debian package migration and could use input on the upgrade and packaging process.
Background:
2.X.X to 3.X.X.new.deb, new-tools.deb, and new-core.deboldname.* to new.*, with references updated accordingly.
oldname-prefetch.service, oldname-prefetch.sh, oldname.config, and oldname.service were not renamed (aligns with rpms).Provides, Replaces, Breaks) was not enough.My specific questions:
new.deb, new-tools.deb, etc.) or only in the main new.deb package?/usr/lib/systemd/oldname.service from the transitional package via an override (e.g., override_dh_auto_install-oldname or override_dh_install), but it’s not having the expected effect. Should I specify individual files, or is there something I’m missing about override execution for this case?/usr/lib/systemd/oldname.service? (There is no oldname.install file, but oldname.service is referenced in new.install.)oldname to still install files named oldname, e.g., oldname.service, or to contain scripts/configs that reference the old name?apt not handling the upgrade as expected likely a local environment (testing) issue, or are there common pitfalls that might cause this on a fresh environment?Code
Control File:
Source: new
Section: admin
Priority: optional
Maintainer: <email>
Build-Depends: python3-all-dev, debhelper (>= 10), config-package-dev, lsb-release, ca-certificates, dh-python, asciidoc-base, docbook-xml, binutils-dev
Standards-Version: #.#.#
Package: new
Architecture: all
Pre-Depends: debconf
Depends: ${shlibs:Depends}, ${python3:Depends}, ${misc:Depends}, new-tools,
python3, python3-yaml,
uuid-runtime,
…
Provides: ${diverted-files}, new-oldname, oldname
Conflicts: ${diverted-files}, new-oldname, oldname (<< 3.0.0)
Breaks: oldname (<< 3.0.0)
Replaces: new-oldname (<< 3.0.0), oldname (<< 3.0.0)
Description: Title
Body
Package: new-tools
Architecture: all
Pre-Depends: debconf
Depends: ${shlibs: Depends}, ${python3:Depends}, new-core,
python3, python3-yaml,
uuid-runtime,
…
Replaces: oldname (<< 3.0.0), new (<< 3.0.0)
Description: Title
Body
Package: oldname
Depends: new, ${misc:Depends}
Architecture: all
Priority: optional
Section: oldlibs
Description: transitional package
This is a transitional package. It can be safely removed.
Rules file:
#!/usr/bin/make -f
export DEP_BUILD_MAINT_OPTIONS = harding=+all
export DEB_FIXPERMS_EXCLUDE = /usr/lib/oldname/new-*
export PYBUILD_NAME = new
export PYBUILD_DESTDIR_python3 = $(CURDIR)/debian/new-tools
%:
dh $@ --fail-missing --with python3,systemd
override_dh_auto_install:
dh_auto_install
rm -f debian/tmp/etc/init.d/foo
mkdir -p debian/new/usr/share/initramfs-tools/hooks
install -m 755 -D debian/new.initramfs.hooks debian/new/usr/share/initramfs-tools/hooks/new
install -m 755 -d debian/new/usr/share/keyrings
install -m 755 -d debian/new/usr/share/oldname
install -m 644 archive/new-new.list debian/new/usr/share/oldname/new.list
perl -I./new ./new/file-name --api-version > debian/new/usr/share/oldname/new-tools-api-version
# added this line to try to remove these from the transitional package:
rm -f debian/oldname/usr/lib/systemd/oldname.service
override_dh_install:
dh_install --fail-missing
install -m 755 -D scripts/cron debian/new/etc/cron.d/cron
line from new.install:
debian/oldname.service usr/lib/systemd/system
Is anyone's default X11 DISPLAY :0? Or is it :1 for Ubuntu (GNOME, GDM, 22.04, X11)?
Background: Our corporate IT wrote code targeted to Ubuntu (the only Linux distribution we deploy as a desktop environment) that hard-codes the DISPLAY to :0. But my DISPLAY, and my colleague's DISPLAY, and my other 24.04 desktop, and his 22.04 non-IT laptop, come up as DISPLAY=:1, which breaks a function, and IT seems to be caught flat-footed by this. ChatGPT says that :0 is the default. I am super-curious why all the systems I consult use :1 as the default display, but ChatGPT and IT think it should be :0.
Only one instance of Xorg is running:
$ ps ax | fgrep 'Xorg'
14421 tty2 Sl+ 1:45 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/645083918/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3
xrandr shows a Screen 0 and that's it. There are no references to displays anywhere in /etc/X11. GDM is running. Wayland is disabled. /etc/.X11-unix has X1 alone. No other users are running and no remote sessions are running. Reboots and logouts don't change the situation.
Steps to reproduce:
echo $DISPLAY:1I'm using Kubuntu 22.04. I try to find all tables with cms subname in my laravel projects (stored in /mnt/_work_sdb8/wwwroot/lar subdirectory) that are under migrations. To do so, I run:
grep -Hrn -A 5 'cms' --include="*database/migrations/*.php" /mnt/_work_sdb8/wwwroot/lar
... but it fails. Is my command incorrect?
I am new to Ubuntu and Linux in general, so I might not immediately get everything you're talking about.
My question is about the absence of the confirmation dialog when using the delete key on your keyboard, and more specifically how to enable it. I have searched everywhere and can not find a working answer.
Windows also defaults to not showing anything when deleting files, but at least there you've got the option to enable it again.
So, short of the devs adding the option into the OS again (please do!), what other way is there to enable the warning message?
(Ubuntu 24.04)my external monitor worked well at 144hz all these but today all of sudden, my external monitor is capped to 60hz. I tried everything like adding new mode, but nothing worked. I deleted the nvidia driver and suddenly after a reboot everything works well. But, I need nvidia driver for a project. I want to see if there is any to keep the nvidia driver and have it run at 144hz. (Nvidia running on my laptop dual booted with windows-primary and mok signed in for secure boot on)
I am a beginner in Ubuntu, I decided to stick to me current computer. Windows 11 told me to change it, but I won’t… It works just fine ! So I decided to change and learn from every steps, even the smallest, using Ubuntu now (Ubuntu 24.04.3 LTS).
Here is my problem. I get an AppImage of the app SuperSlicer. https://github.com/supermerill/SuperSlicer/releases/tag/2.5.59.13 Prior to downloading it, I decided to install the AppImageLauncher, as I read a recommendation for it (just to know it). Everything works fine in the app when running. Except... the icon in the task bar when I launch the SuperSlicer app. The pinned icon on the bar is correct.
But the icon of the app after launching is a kind of a generic one AND there is not this little red dot (or dots when the app is running multiple times) just right of the pinned icon (as for Firefox in this example). This should actually be the only mark indicating that the app is running looking at the bar and that is the behavior I am looking for.
Generic icon of the app when launched:
I read a bit about this problem and learn that it could come from the .desktop file. But I do not see any trouble in it. Below is the icons location I found and the .desktop file content.
Icons location:
.desktop content:
But now thanks to your help in comment the result is almost what I am expecting. Indeed I had to change the wmclass in the .desktop file.
The situation is now that. There is still 2 icons, but it is a bit better!
I updated to 25.10 on Monday after the update was offered to me by my Ubuntu 25.04 installation. The system was running on 25.04 since I updated to that from 24.10, I basically updated to every new version when it was released over the past few years which was working more or less without problems.
When I rebooted the PC after the update this time however I noticed that many of the programs are just not opening anymore. This includes both programs that I installed as well as software that is shipped with Ubuntu.
What I noticed was not working:
What I am still able to open:
I am not really able to figure out what the issue may be based on the affected list of programs.
What I did try out so far as it seemed most reasonable to me was changing the graphics driver. I was running the NVIDIA driver 570 and then switched to 580 using apt install. The software updater does show me the installed driver as well as the other options of version 580, but it won't let me switch (pk client error quark 303).
When I for example attempt to open the settings from terminal (running gnome-control-center) nothing is happening. The process does not finish in the terminal, but there aren't any messages or any windows opening. The process just seems to be stuck.
Does anybody have any ideas what that issue could be?
Illustration of the problem: enter image description here
I've taken that screenshot several minutes after starting all those commands. Only chrome is showing some errors messages at all when not using any more debug flags for output. For chrome the dash also shows a supposed welcome window, but its not visible on any screen or dashboard.
Firefox has not saved credit card numbers for me since I upgraded to the Snap version. When I try to save a credit card number I see messages like this in the syslog:
dbus-daemon[3656]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.6" pid=5121 label="snap.firefox.firefox" peer_pid=3655 peer_label="unconfined"
dbus-daemon[3656]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.Secret.Service" member="OpenSession" mask="send" name=":1.6" pid=5121 label="snap.firefox.firefox" peer_pid=3655 peer_label="unconfined"
I spent about an hour grepping in the AppArmor config files, Googling, and searching Stack Exchange to no avail. What's the secret method to enable this commonly used feature for the snap?
Firefox 144.0.2 Ubuntu 24.04.3 LTS
PS:I am aware of the .deb version, of which I was previously a user. I am hoping we can get the snap version, which Ubuntu is enthusiastically promoting, to work properly so I don't have to go back
The OS starts in software rendering mode. The only thing I've changed (and found in the logs) is installing the updates for sudo-rs and intel microcode via the Ubuntu Software Updater (which I don't suspect to be an issue, I hope, as I don't use an Intel CPU).
I've been using the kernel-provided mesa drivers.
Boot logs also include "not hardware accelerated" pops up.
vulkaninfo --summary outputDevices:
========
GPU0:
apiVersion = 1.4.318
driverVersion = 25.2.3
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 20.1.8, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 25.2.3-1ubuntu1 (LLVM 20.1.8)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3235-2e32-2e33-2d3175627500
driverUUID = 6c6c766d-7069-7065-5555-494400000000
lshw -c video output *-display
description: VGA compatible controller
product: Navi 48 [Radeon RX 9070/9070 XT/9070 GRE]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:0b:00.0
logical name: /dev/fb0
version: c0
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master cap_list fb
configuration: depth=32 latency=0 resolution=1024,768
resources: iomemory:780-77f iomemory:7c0-7bf memory:7800000000-7bffffffff memory:7c00000000-7c0fffffff ioport:e000(size=256) memory:fcd00000-fcd7ffff memory:fcd80000-fcd9ffff
./syslog-2025-11-11T21:48:50.613665+01:00 janitors-closet gnome-shell[2599]: Added device '/dev/dri/card0' (simpledrm) using a
tomic mode setting.
./syslog:2025-11-11T21:48:50.615750+01:00 janitors-closet gnome-shell[2599]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Not hardware accelerated
./syslog-2025-11-11T21:48:50.615811+01:00 janitors-closet gnome-shell[2599]: Created gbm renderer for '/dev/dri/card0'
./syslog-2025-11-11T21:48:50.615853+01:00 janitors-closet gnome-shell[2599]: Integrated GPU /dev/dri/card0 selected as primary
Anything I can do here to debug this more? I'd like to continue using the newer Kernel.
Huge thanks in advance!
How can I resolve the issue?
I described the approach that uses a 3rd party tool egpu-switcher because previously I had a success with that tool, but I don't mind using it or not using it.
On the same laptop where eGPU was functioning on Ubuntu 22.04, now disk was wiped out and 24.04 is installed then this issue started happening.
Upon booting when login window, screen is blacked out. Sometimes an underscore blinks at the top-left.
I basically follow a blog post on nvidia.com (posted in 2020) with a twist. Summarizing the steps:
sudo apt update && sudo apt dist-upgrade && sudo apt install nvidia-cuda-toolkitWayland by commenting out WaylandEnable=false in /etc/gdm3/custom.conf./usr/share/X11/xorg.conf.d/10-nvidia.conf
Option "AllowExternalGpus" "True"
/etc/default/grub. Then sudo update-grub && sudo shutdown --reboot./etc/default/grub to the default by removing “3” from GRUB_CMDLINE_LINUX_DEFAULT andsudo /usr/bin/egpu-switcher enable.sudo update-grub && sudo shutdown --reboot.Iff I skip the line that contains egpu-switcher enable, the issue doesn't happen, but also nvidia-smi command doesn't show the external GPU either.
nvidia-driver-575-open$ lspci | grep -i "nvidia"
03:00.0 3D controller: NVIDIA Corporation TU117GLM [T550 Laptop GPU] (rev a1)
22:00.0 VGA compatible controller: NVIDIA Corporation AD106 [GeForce RTX 4060 Ti 16GB] (rev a1)
22:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1)
Part of /var/log/syslog from one of the days the issue occurred on my cloud.
eGPU was detected AND functioning i.e. Login screen showed up, applications were able to utilize eGPU, nvidia-smi showed the used percentage of the external GPU.
$ sudo /usr/bin/egpu-switcher enable
[info] created egpu bootup service to autorun 'egpu-switcher switch'
[ok] setup successful
I think this generates the 2 files egpu.service, x11-template.conf.
$ sudo more /usr/share/egpu-switcher/egpu.service
# generated by egpu-switcher
[Unit]
Description=EGPU Service
Before=display-manager.service
After=bolt.service
[Service]
Type=oneshot
ExecStart=/usr/bin/egpu-switcher switch auto
[Install]
WantedBy=graphical.target
$ sudo more /usr/share/egpu-switcher/x11-template.conf
# autogenerated by egpu-switcher
{{if .Modesetting}}
Section "Module"
Load "modesetting"
EndSection
{{end}}
Section "Device"
Identifier "{{.Id}}"
Driver "{{.Driver}}"
BusID "{{.Bus}}"
Option "AllowEmptyInitialConfiguration"
Option "AllowExternalGpus" "True"
EndSection
The 2 services that are called within egpu.service.
$ locate display-manager.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/display-manager.service.wants
/etc/systemd/system/display-manager.service.wants/gpu-manager.service
/var/lib/systemd/deb-systemd-helper-enabled/display-manager.service.wants
/var/lib/systemd/deb-systemd-helper-enabled/display-manager.service.wants/gpu-manager.service
$ more /etc/systemd/system/display-manager.service
[Unit]
Description=GNOME Display Manager
# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service
# replaces plymouth-quit since it quits plymouth on its own
Conflicts=plymouth-quit.service
After=plymouth-quit.service
# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and plymouth-quit.service
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service
# Start after cloud init is done generating the system configuration
# otherwise we might end up getting the wrong locale for example
After=cloud-config.service
# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service
[Service]
ExecStartPre=/usr/share/gdm/generate-config
ExecStart=/usr/sbin/gdm3
KillMode=mixed
Restart=always
RestartSec=1s
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
EnvironmentFile=-/etc/default/locale
ExecReload=/usr/share/gdm/generate-config
ExecReload=/bin/kill -SIGHUP $MAINPID
KeyringMode=shared
$ find /usr/ -iname bolt.service
/usr/lib/systemd/system/bolt.service
$ more /usr/lib/systemd/system/bolt.service
[Unit]
Description=Thunderbolt system service
After=polkit.service
Documentation=man:boltd(8)
[Service]
Type=dbus
BusName=org.freedesktop.bolt
ExecStart=/usr/libexec/boltd
#Environment="G_MESSAGES_DEBUG=all"
Restart=on-failure
NotifyAccess=main
WatchdogSec=3min
MemoryDenyWriteExecute=yes
PrivateTmp=yes
ProtectControlGroups=yes
ProtectHome=yes
ProtectKernelModules=yes
ProtectSystem=full
RestrictAddressFamilies=AF_NETLINK AF_UNIX
RestrictRealtime=yes
ReadWritePaths=/var/lib/boltd
SystemCallFilter=~@mount
CapabilityBoundingSet=CAP_NET_ADMIN
#directory management
RuntimeDirectory=boltd
RuntimeDirectoryPreserve=yes
StateDirectory=boltd
I have noticed for a while now that my system seems to be using up my memory much more quickly than I would expect. When it gets like this, I do notice it slowing down a bit at time, and my fan starts to spin aggressively (though maybe this latter thing is a separate issue?). I have tried googling around to understand what is going on (for example, I came across High memory usage that cannot be traced to a service or application and https://www.linuxatemyram.com/), but I haven't yet found a satisfying answer. What are reasons that my computer would be using much more memory (close to 100% of RAM and swap) than is reported by the running applications?
Currently, free -m outputs
total used free shared buff/cache available
Mem: 15337 14538 386 14 411 454
Swap: 20480 15442 5038
A rough estimate of the amount of memory my running applications are using (computed with ps -o %mem ax | tail -n +2 | paste -sd+ | bc) is 47.6%. Also, if I open up System Monitor and try manually adding up the amounts in the Memory column, then I again don't get a value close to the total reported amount of used memory.
Running arcstat -a outputs
time hits miss read hit% miss% dhit dmis dh% dm% phit pmis ph% pm% mhit mmis mread mh% mm% arcsz size c mfu mru mfug mrug eskip el2skip el2cach el2el el2mfu el2mru el2inel mtxmis dread pread grow need free avail waste
13:14:22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 5.0K 5.0K 479M 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 830M 235M 0
The output of running arc_summary can be found here. I put it in pastebin since askubuntu limits the number of characters in this question.
I can't say I know how to parse all this output, but to my naive eyes, this doesn't seem to indicate much memory is being used by ARC caches (at least, the ARC size (current) row reports a small number). Also, zfs get comprresion produces no output.
Similarly, running df -hl -t"tmpfs" outputs the following, which again doesn't seem to account for much of my "missing" memory usage.
Filesystem Size Used Avail Use% Mounted on
tmpfs 1.5G 4.0M 1.5G 1% /run
tmpfs 7.5G 260K 7.5G 1% /dev/shm
tmpfs 5.0M 8.0K 5.0M 1% /run/lock
tmpfs 7.5G 0 7.5G 0% /run/qemu
tmpfs 1.5G 228K 1.5G 1% /run/user/1000
If it helps, cat /proc/meminfo outputs
MemTotal: 15705548 kB
MemFree: 672004 kB
MemAvailable: 838776 kB
Buffers: 2060 kB
Cached: 329484 kB
SwapCached: 258588 kB
Active: 3268524 kB
Inactive: 3574140 kB
Active(anon): 3095044 kB
Inactive(anon): 3439264 kB
Active(file): 173480 kB
Inactive(file): 134876 kB
Unevictable: 340 kB
Mlocked: 340 kB
SwapTotal: 20972540 kB
SwapFree: 4630972 kB
Zswap: 0 kB
Zswapped: 0 kB
Dirty: 452 kB
Writeback: 0 kB
AnonPages: 6253600 kB
Mapped: 191184 kB
Shmem: 22852 kB
KReclaimable: 194792 kB
Slab: 588360 kB
SReclaimable: 194792 kB
SUnreclaim: 393568 kB
KernelStack: 75888 kB
PageTables: 194976 kB
SecPageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 28825312 kB
Committed_AS: 46712256 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 231560 kB
VmallocChunk: 0 kB
Percpu: 19776 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 11380384 kB
DirectMap2M: 4728832 kB
DirectMap1G: 0 kB
The only other thing I can think to add is a screenshot of the resources tab of System Monitor.
Let me know if there is anything else I can do to help figure out what's going on.
I am trying to get my Ubuntu laptop to work with my new docking station, with passthrough of everything via just thunderbolt.
Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz)The docking station is working with everything except the external displays. I'm running into two separate issues.
Originally when attaching the hub with either monitor plugged into it the entire system would black screen and freeze until it was unplugged at which point it would give me a "could not set configuration for crtc 64". After googling around I ended up updating my kernel from 5.3.0 to 5.19.17 which put me in the state I mentioned above (so I can now try to debug a bit). This did not fully install correctly so I do plan/hope on being able to revert back to my original kernel version once I figure this out.
OS Stats:
### lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.6 LTS
Release: 18.04
Codename: bionic
### uname -r
5.19.17-051917-generic
### xrandr
Screen 0: minimum 320 x 200, current 4480 x 1440, maximum 16384 x 16384
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1920x1080 59.98*+ 59.97 59.96 59.93
1680x1050 59.95 59.88
1600x1024 60.17
1400x1050 59.98
1600x900 59.99 59.94 59.95 59.82
1280x1024 60.02
1440x900 59.89
1400x900 59.96 59.88
1280x960 60.00
1440x810 60.00 59.97
1368x768 59.88 59.85
1360x768 59.80 59.96
1280x800 59.99 59.97 59.81 59.91
1152x864 60.00
1280x720 60.00 59.99 59.86 59.74
1024x768 60.04 60.00
960x720 60.00
928x696 60.05
896x672 60.01
1024x576 59.95 59.96 59.90 59.82
960x600 59.93 60.00
960x540 59.96 59.99 59.63 59.82
800x600 60.00 60.32 56.25
840x525 60.01 59.88
864x486 59.92 59.57
800x512 60.17
700x525 59.98
800x450 59.95 59.82
640x512 60.02
720x450 59.89
700x450 59.96 59.88
640x480 60.00 59.94
720x405 59.51 58.99
684x384 59.88 59.85
680x384 59.80 59.96
640x400 59.88 59.98
576x432 60.06
640x360 59.86 59.83 59.84 59.32
512x384 60.00
512x288 60.00 59.92
480x270 59.63 59.82
400x300 60.32 56.34
432x243 59.92 59.57
320x240 60.05
360x202 59.51 59.13
320x180 59.84 59.32
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1-1 connected (normal left inverted right x axis y axis)
2560x1440 59.95 +
3840x2160 30.00 25.00 24.00 29.97 23.98
1920x1080 60.00 60.00 50.00 59.94 30.00 29.97
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94
DP-1-2 connected 2560x1440+1920+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 74.97*+
1920x1080 60.00 60.00 50.00 59.94 30.00 29.97
1280x720 60.00 50.00 59.94
1024x768 60.00
800x600 60.32
720x576 50.00
720x480 60.00 59.94
640x480 60.00 59.94
### lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 3ea0
### sudo X -version
X.Org X Server 1.20.8
X Protocol Version 11, Revision 0
Build Operating System: Linux 5.4.0-135-generic x86_64 Ubuntu
Current Operating System: Linux stephanie 5.19.17-051917-generic #202210240939 SMP PREEMPT_DYNAMIC Mon Oct 24 09:43:01 UTC 2022 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.19.17-051917-generic root=UUID=0f75530f-31a7-4e3e-b51a-a5767ee9a76b ro quiet splash vt.handoff=1
Build Date: 07 December 2022 02:15:34PM
xorg-server-hwe-18.04 2:1.20.8-2ubuntu2.2~18.04.9 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Since the kernel upgrade lshw is throwing a segmentation fault when run. Looking into how to resolve this but I can't get any info out of that command currently.
As another note I am still running Unity7 and not gnome, I don't believe this makes a difference since they both use X for the display server but thought I'd mention it in case.
I'm pretty sure that my laptop should be able to support dual monitors through its thunderbolt (looking at the external display section in the linked specs) so I am hoping this can be resolved. Any help would be super useful, please let me know if there is any additional information I can provide that would help debug this.
I installed nvidia-driver-455 via the runfile on Nvidia's website. It installs the driver plus several cuda packages.
After installing, the command apt list --installed *nvidia* will show nvidia-driver-455 indicating that it was installed through apt. After a few days and some Ubuntu updates, my second monitor stopped working and the command apt list --installed *nvidia* no longer shows nvidia-driver-455.
I've seen people suggest that I disable updates, but that sounds extremely unsafe if vulnerabilities aren't patched.
Edit: Ubuntu 20.04, not a live system
Edit 2: I checked /var/log/apt/history.log and it shows nvidia-driver-455 being installed, then purged on Nov 1, 2020 before I reinstalled it with the runfile linked above. It does not show it being reinstalled via the runfile and it does not show it being removed last night/this morning.
Edit 3: Edited again for length and clarity. Removed information that may have been irrelevant/misleading. The question is specifically focused on the disappearance of the graphics driver package nvidia-driver-455.
I want to know
I've been trying to fix this for about 4 hours now and I'm not 100% sure how to phrase the problem, so bear with me.
Background
I've been using my Laptop with Linux for a couple of months now and everything mostly went fine. It was running Mint, but I'm not going to ask you for help with a Mint system. Anyway, for some reason I decided that I had to reboot my System today and that's where the woes began. There were a lot of different errors, most of which I don't really recall, nor found a solution to. I still had access to my files so I decided to back them up and reinstall the OS, the latest Ubuntu this time. The initial installation went mostly fine, however here are some of the problems I've encountered:
Problems
After the initial installation and the first reboot (which went without a problem), the reboot after that however did not succeed.
I don't have the exact error message, but I believe there are enough threads around on this very problem.
I "solved" this by reinstalling it again and installing the official Nvidia Driver. As per standard, through the driver I selected the integrated GPU as standard, as the Nvidia one burns through my battery life quite quickly. Yadayadayada, next reboot:
This time I thought it was smart. I booted up ubuntu through my flashdrive, mounted the other installation and looked up how to edit the grub.cfg without breaking anything. I replaced "quiet splash" with "nomodeset" on all the launch options, and rebooted again:
This wasn't just a warning, the entire system refused to boot after displaying the message. I still couldn't get into the GRUB. I also found nothing on the message except for some threads on other distributions and completely different situations.
Status Quo
I reinstalled ubuntu again and made sure not to leave the Nvidia GPU option. It does reboot fine, however, I would very much like this problem solved and I have no idea how. I'm hesitant to put any data on the system when it could basically break on any reboot. Is my laptop cursed or is there any way to save it?
In windows I add to the routing table:
route add 159.182.151.0 MASK 255.255.255.0 159.182.152.110
How to add similar to ubuntu ?
thanks.
Today, I installed the software update from Ubuntu. Then on reboot, I never got to login screen. Something kept flashing on screen, but was too fast to see what it was saying.
Was able to ssh from another computer, dmesg says: "API mismatch: the client has the version 384.111, but this kernel module has the version 384.90. Please make sure that this kernel module and all NVIDIA driver components have the same version."
How could this mismatch happen, since my updates are via the software updater? Appears someone released a driver that the kernel wasn't expecting or some other error occurred.
How do I fix this?
Thanks.
I'm trying to set up my Ubuntu server 16.04 LTS Xenial to run a DHCP Server that provides the required information to a very specific device.
That device is a TV Decoder by Orange ISP (French vendor is Sagem), and it only works if the IP address is assigned by the Livebox 3 by Orange (TM) (same vendor). This restriction avoids having a different DHCP server than the one provided by Orange.
If I want to use my own DHCP server running in Ubuntu 16.04 to avoid the one running at the Livebox (it's crappy) I need to adapt my configuration.
Bootstrap Protocol (ACK) using TV Decoder and DHCP, both from Sagem
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x35139a37
Seconds elapsed: 0
Bootp flags: 0x8000, Broadcast flag (Broadcast)
Client IP address: 0.0.0.0
Your (client) IP address: 192.168.1.153
Next server IP address: 192.168.1.1
Relay agent IP address: 0.0.0.0
Client MAC address: Sagemcom_37:a1:9a (f0:82:61:37:a1:9a)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (ACK)
Length: 1
DHCP: ACK (5)
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: 192.168.1.1
Option: (51) IP Address Lease Time
Length: 4
IP Address Lease Time: (843s) 14 minutes, 3 seconds
Option: (58) Renewal Time Value
Length: 4
Renewal Time Value: (421s) 7 minutes, 1 second
Option: (59) Rebinding Time Value
Length: 4
Rebinding Time Value: (737s) 12 minutes, 17 seconds
Option: (1) Subnet Mask
Length: 4
Subnet Mask: 255.255.255.0
Option: (6) Domain Name Server
Length: 4
Domain Name Server: 192.168.1.1
Option: (15) Domain Name
Length: 4
Domain Name: home
Option: (28) Broadcast Address
Length: 4
Broadcast Address: 192.168.1.255
Option: (3) Router
Length: 4
Router: 192.168.1.1
Option: (125) V-I Vendor-specific Information
Length: 41
Enterprise: The Broadband Forum (formerly 'ADSL Forum') (3561)
Length: 36
Option 125 Suboption: (4) GatewayManufacturerOUI
Length: 6
GatewayManufacturerOUI: 307CB2
Option 125 Suboption: (5) GatewaySerialNumber
Length: 15
GatewaySerialNumber: AN16XXXXXXXXXX
Option 125 Suboption: (6) GatewayProductClass
Length: 9
GatewayProductClass: Livebox 3
Option: (255) End
Option End: 255
To emulate the same behavior from my own ISC DHCP Server in Ubuntu I had customized it, based on the found documentation and options.
Basically, the point is to send only to the TV decoder the following additional codes:
Based on the ISC DHCP server documentation, the three codes exist and they could be easily sent by adding the convinient options:
Firstly, I tried that way:
/etc/dhcp/dhcpd.conf
# Create an option namespace called orangetv
option space orangetv code width 1 length width 1;
option orangetv.GatewayManufacturerOUI code 4 = text;
option orangetv.GatewaySerialNumber code 5 = text;
option orangetv.GatewayProductclass code 6 = text;
# Linux Router
subnet 192.168.1.0 netmask 255.255.255.0 {
option domain-name-servers 192.168.1.1;
option broadcast-address 192.168.1.255;
option subnet-mask 255.255.255.0;
option routers 192.168.1.5;
range 192.168.1.100 192.168.1.199;
class "sagem-vendor-classes" {
match if substring(option vendor-class-identifier, 0, 5) = "sagem";
option domain-name "home";
option www-server 193.253.67.89;
vendor-options-space orangetv;
option orangetv.GatewayManufacturerOUI "307CB2";
option orangetv.GatewaySerialNumber "AN16XXXXXXXXXXX";
option orangetv.GatewayProductclass "Livebox 3";
}
}
Once the new config was saved, I checked the configuration syntax by running: sudo dhcpd -t -cf /etc/dhcp/dhcpd.conf
Then, I restarted the DHCP server to reload the new config (ISC DHCP 4.3 fails sometimes to restart and reload the new config. This is somehow related to the Apache2 server. Therefore I suggest forcing it):
sudo -i
service dhcp restart
service isc-dhcp-server restart
service isc-dhcp-server6 restart
service apache2 restart
Now, I rebooted the TV Decoded, and traced the network with Wireshark again. The result of the Bootstrap ACK was
Message type: Boot Reply (2)
Hardware type: Ethernet (0x01)
Hardware address length: 6
Hops: 0
Transaction ID: 0x70907f18
Seconds elapsed: 0
Bootp flags: 0x8000, Broadcast flag (Broadcast)
Client IP address: 0.0.0.0
Your (client) IP address: 192.168.1.153
Next server IP address: 192.168.1.5
Relay agent IP address: 0.0.0.0
Client MAC address: Sagemcom_37:a1:9a (f0:82:61:37:a1:9a)
Client hardware address padding: 00000000000000000000
Server host name not given
Boot file name not given
Magic cookie: DHCP
Option: (53) DHCP Message Type (ACK)
Length: 1
DHCP: ACK (5)
Option: (54) DHCP Server Identifier
Length: 4
DHCP Server Identifier: 192.168.1.5
Option: (51) IP Address Lease Time
Length: 4
IP Address Lease Time: (843s) 14 minutes, 3 seconds
Option: (1) Subnet Mask
Length: 4
Subnet Mask: 255.255.255.0
Option: (3) Router
Length: 4
Router: 192.168.1.5
Option: (6) Domain Name Server
Length: 4
Domain Name Server: 192.168.1.1
Option: (15) Domain Name
Length: 4
Domain Name: home
Option: (28) Broadcast Address
Length: 4
Broadcast Address: 192.168.1.255
Option: (72) Default WWW Server
Length: 4
Default WWW Server: 193.253.67.89
Option: (255) End
Option End: 255
Padding: 0000000000000000
As you notice, options 15 and 72 were correctly parsed by option 125 is missing. So, I tried to use the encapsulated vendor options as recommended in the manual. I Used
option vendor-encapsulated-options 7d:29:00:00:0d:XXXXXXXX:20:33
instead of the vendor-options-space method, but it failed again.
I used another workaround to send the code 125 as explained in [https://lists.isc.org/pipermail/dhcp-users/2012-July/015793.html][1]
/etc/dhcp/dhcpd.conf
# Create an option namespace called orangetv
option space orangetv code width 1 length width 1;
option orangetv.GatewayManufacturerOUI code 4 = text;
option orangetv.GatewaySerialNumber code 5 = text;
option orangetv.GatewayProductclass code 6 = text;
# Package the orangetv namespace into option 125
option space vivso code width 4 length width 1;
option vivso.orangetv code 3561 = encapsulate orangetv;
option vivso.iana code 0 = string;
option op125 code 125 = encapsulate vivso;
# Linux Router
subnet 192.168.1.0 netmask 255.255.255.0 {
option domain-name-servers 192.168.1.1;
option broadcast-address 192.168.1.255;
option subnet-mask 255.255.255.0;
option routers 192.168.1.5;
range 192.168.1.100 192.168.1.199;
class "sagem-vendor-classes" {
match if substring(option vendor-class-identifier, 0, 5) = "sagem";
option domain-name "home";
option www-server 193.253.67.89;
option vivso.iana 01:01:01;
option orangetv.GatewayManufacturerOUI "307CB2";
option orangetv.GatewaySerialNumber "AN16XXXXXXXXXXX";
option orangetv.GatewayProductclass "Livebox 3";
}
}
Despite these configurations, the DHCP server is not sending the code 125 win the vendor specifics.
Any other suggestions?
I recently (approx 6m) bought a refurbished laptop online, which had two hard disks installed. I installed Ubuntu on one of them and run the laptop as a dual-boot Windows/Linux machine - this has been working without significant issues. However, recently I encountered regular issues with the machine, where Ubuntu wanted to send operation system error messages to HQ, and a few applications just suddenly refused to load. I don't think it is a virus as I ran clamTK with no discoveries of infection. Hence I followed up with potential hardware issues and I encountered the below while trouble-shooting.
I don't quite understand the report -- is this hard drive in terminal decline, or are these tests failing simply because this is the Windows partition (and my laptop issue doesn't lie with the hard disk)?
I am an amateur Linux-user, this is my first machine running Linux.
I just read Meet Etcher, A Stylish Open-Source USB Image Writer Tool. It talks about downloading an AppImage.
Yes, Linux; the Linux packages are distributed as a .appimage for 32-bit and 64-bit distributions, and should run across all major Linux distributions without any issues. The team currently has no plan to provide a native .deb (or .rpm) installer.
What are AppImages? How do they differ from snaps?
I have some serious tearing problems and I dont like Compton. And compiz is too heavy. Is there any WM alternatives?
If you type this simple test command:
gnome-terminal -x bash -c "ls;sleep 3"
You will find that it returns immediately (the newly created terminal, of course, lingers for three seconds). This is in contrast to, say, rxvt (same command but with e).
If you want a blocking start, the historical consensus seems to have been to use --disable-factory. Unfortunately, this does not work anymore (tested 3.14.2).
So, how do I start the terminal in a non-asynchronous manner?
Bonus: konsole, lxterminal, and xfce4-terminal at least also have the same problem. Commands for those?