DebugPoint.com » Comments Feed

Comment on How to Install, Change, Autostart Screensaver in Ubuntu by Paul

Due to Wayland replacing X11, this unfortunately no longer works with Ubuntu 24.04 :-( Clicking on the Xscreensaver Settings icon causes this error to appear in /var/log/syslog: <em>xscreensaver-settings.desktop[5060]: xscreensaver-settings: 17:42:27: Gdk: gdk_x11_window_get_xid: assertion 'GDK_IS_X11_WINDOW (window)' failed</em> I really would like to get this running with Ubuntu 24.04, but apparently no one found a (simple) solution to this as yet...

ПОДРОБНЕЕ

Comment on 4 Simple Steps to Clean Your Ubuntu System by Andrew Shugg

This is getting very deep into the weeds, but I thought I'd contribute my own notes about Debian/Ubuntu system cleanups. Very little disk space is likely to be recovered, but if you're someone who strongly dislikes "mess" like leftover files and empty directories after a package has been removed, then this is for you. 1) Check for packages that can be safely purged because they've been removed (e.g. with apt-get autoremove) and just have empty directories and/or ephemeral files left on disk. These packages will have no files associated with them any more in the dpkg system, so their "list" file will be empty. <pre class="ql-syntax" spellcheck="false">find /var/lib/dpkg/info -type f -name '*.list' -size 0 -exec basename {} ';' | sed 's/.list$//' </pre> 2) If you got a lot of output, you might prefer to just know how many packages of this type there are. <pre class="ql-syntax" spellcheck="false">find /var/lib/dpkg/info -type f -name '*.list' -size 0 -exec basename {} ';' | sed 's/.list$//' | wc -l </pre> 3) Purge the removed/deconfigured packages: <pre class="ql-syntax" spellcheck="false">find /var/lib/dpkg/info -type f -name '*.list' -size 0 -exec basename {} ';' | sed 's/.list$//' | xargs -tr sudo dpkg --purge </pre> The -t flag for xargs will cause the command to be printed out before it is run, so that you can see what is happening. The -r flag will prevent xargs from running if there is no input (i.e. no packages were found). 4) You can also identify packages that aren't completely installed - perhaps they've been unpacked but the configuration failed, or something. (Far less likely these days than it was 25 years ago, when we were mucking about with dpkg directly.) <pre class="ql-syntax" spellcheck="false">dpkg -l | awk '(NR > 5 && $1 != "ii") { print $2 }' </pre> These can be removed in the same manner. <pre class="ql-syntax" spellcheck="false">dpkg -l | awk '(NR > 5 && $1 != "ii") { print $2 }' | xargs -tr sudo dpkg --purge </pre> Cheers! Andrew...

ПОДРОБНЕЕ