Because it darkens the rest of the screen and I cannot see the keyboard layout indicator. Right now my workflow is as follows:
This simple script runs correctly when launched manually:
#!/bin/sh
flatpak -y update 2>&1 >> ~/cron/cron-flatpak.log
When run with 00 07 * * * sh ~/cron/cron-flatpak.sh (same regular user, not root crontab), it produces the following:
Looking for updates…
1. org.chromium.Chromium.Codecs stable u flathub < 1.1 MB
2. org.chromium.Chromium.Locale stable u flathub < 112.8 kB (partial)
3. org.qbittorrent.qBittorrent stable u flathub < 8.3 MB
Updating 1/3…
Warning: Failed to get revokefs-fuse socket from system-helper: Flatpak system operation GetRevokefsFd not allowed for user
Updating 1/3… ██▌ 13% 41.1 kB/s
Updating 1/3… ████████████████████ 100% 674.8 kB/s
Updating 1/3… ████████████████████ 100% 674.8 kB/s
Updating 2/3…
Warning: Failed to get revokefs-fuse socket from system-helper: Flatpak system operation GetRevokefsFd not allowed for user
Updating 2/3… ████████████████████ 100% 592 bytes/s
Updating 3/3…
Warning: Failed to get revokefs-fuse socket from system-helper: Flatpak system operation GetRevokefsFd not allowed for user
Updating 3/3… ████████████████████ 100% 0 bytes/s
Updates complete.
Afterwards, the versions seem to match what's listed on flathub.io, but the script tries to update everything over and over again on each run. Any suggestions?
ETA: Okay people, I'll be testing the approaches you suggested and I will accept one answer or the other after I manage to make the thing work. Going to take a while since every single iteration requires a new app version rolled out on flathub.
TL;DR: The only clue I could find in the logs is that on a working system /var/log/syslog reports AptDaemon's transactions like this: queuing - simulating - processing - finished. On my system it stops on 'simulating'.
Long version
The problem manifested after the upgrade from 18.04 that had Xfce 4.12 to 20.04 with its Xfce 4.14. Since 20.04 also had Software Updater remade to include snaps, I can't attribute the issue to Xfce only.
Software Updater works fine with the standard Gnome 3 on Xorg, Gnome 3 on Wayland, Gnome Flashback - all on the same Ubuntu installation. On Xfce, the following happens:
Tried reinstalling this and that as suggested by Google; no dice. Of course, I can dance around it with the console. Would prefer to fix it, though.
ETA
Fixed by installing policykit-1-gnome. I'm still curious about the root cause.
Trying to follow these instructions: github, I get the following error in the log:
Checking for 'glib-2.0' >= 2.10
['/usr/bin/pkg-config', '--atleast-version=2.10', 'glib-2.0']
not found
from /home/zorath/xfce4-dockbarx-plugin-master: The configuration failed
The package appears to be present:
$ apt show libglib2.0-0
Package: libglib2.0-0
Version: 2.64.6-1~ubuntu20.04.3
Priority: important
Section: libs
Source: glib2.0
At first I thought the author could have written glib-2.0 instead of glib2.0, but the string appears in the script several times and I'm pretty sure it will fail somewhere down the road if I just remove the hyphen.
Any advice?
Tried to install flatpak Chromium, to no avail:
5. [✗] org.chromium.Chromium stable i flathub < 102.8 MB
Error: org.chromium.Chromium needs a later flatpak version
error: Failed to install org.chromium.Chromium: app/org.chromium.Chromium/x86_64/stable needs a later flatpak version (1.8.2)
Flatpak 1.8.2 is available starting with Groovy:
$ rmadison flatpak
flatpak | 0.11.3-3 | bionic/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x
flatpak | 1.0.8-0ubuntu0.18.04.1 | bionic-security/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x
flatpak | 1.0.9-0ubuntu0.1 | bionic-updates/universe | source, amd64, arm64, armhf, i386, ppc64el, s390x
flatpak | 1.6.3-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
flatpak | 1.6.5-0ubuntu0.1 | focal-updates/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
flatpak | 1.8.2-1 | groovy/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
flatpak | 1.8.4-1 | hirsute/universe | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
I guess I could remove the official Flatpak and use some PPA instead, but it would pretty much undermine the whole idea of getting your software from a trusted source. Snap Chromium is painfully slow on my system for some reason. (As well as snap Firefox.) So, any options left?
The first thing I realized after running apt autoremove and rebooting was that DockX no longer starts. A glance at /var/log/apt/term.log told me that the packages were indeed eradicated despite being in use right at the moment it happened:
Removing dockbarx (0.93+git20190103-1~ppa3) ...
Removing dockbarx-applet-appindicator (0.93+git20190103-1~ppa3) ...
Removing dockbarx-applet-clock (0.93+git20190103-1~ppa3) ...
Removing dockbarx-applet-hello-world (0.93+git20190103-1~ppa3) ...
Removing dockbarx-applet-volume-control (0.93+git20190103-1~ppa3) ...
Removing dockbarx-dockx (0.93+git20190103-1~ppa3) ...
My question is: Why did apt decide to remove these packages and how can I prevent this behaviour in the future?
Update
It was suggested that the packages were removed because they were dependencies of some other, already removed packages. This is not the case. I rolled back the VM anyway and now I can look at the state before the event, using dockbarx as an example:
~$ apt-rdepends -r dockbarx
Reading package lists... Done
Building dependency tree
Reading state information... Done
dockbarx
~$
This is it. There are no packages dependent on dockbarx.
I suspect the situation is somehow related to the fact that I installed these packages from a PPA that is no longer connected. Could there be a link?
Update 2
Checked the logs manually to find out that the dockbarx package was installed as a dependency of xfce4-dockbarx-plugin, a package my system is no longer aware of - most likely because of the disconnected PPA:
~$ apt show xfce4-dockbarx-plugin
N: Unable to locate package xfce4-dockbarx-plugin
N: Unable to locate package xfce4-dockbarx-plugin
E: No packages found
Which is why apt-rdepends gives wrong output for dockbarx. Overall, the answer below is correct and I am accepting it.
This was quite a detective story.
My ISP uses L2TP to connect users to the Internet. I have a working connection on Windows and now I'm trying to clone it to an Ubuntu VM. Of course, I'm getting the intermittent "service failed to start" and "service stopped unexpectedly" errors like any other guy.
The first hoop to jump through seems to be L2TP host name resolution. On Windows I have it written in domain name form; I guess it gets resolved via DHCP. On Ubuntu name resolution fails:
Started the VPN service, PID 7461
Saw the service appear; activating connection
VPN connection: (ConnectInteractive) reply received
VPN connection: failed to connect: 'couldn't look up L2TP VPN gateway IP address '
VPN plugin: state changed: stopped (6)
VPN service disappeared
If I resolve the name manually in Windows (with L2TP down!) and copy the IP address over to Ubuntu, this phase passes and connection fails further down the road. Pinging the L2TP host name with L2TP down works on Windows but fails on Ubuntu.
Hence I assume that Ubuntu fails to use my ISP's DHCP server. Any ideas what to do about it?
Ran into this one while investigating the crashes of a DockBarX plugin. apt gives me the following:
$ apt show xfce4-whiskermenu-plugin
Package: xfce4-whiskermenu-plugin
Version: 2.1.5-0ubuntu1
Priority: optional
Section: universe/xfce
Origin: Ubuntu
Maintainer: Xubuntu Developers <[email protected]>
Original-Maintainer: Debian Xfce Maintainers <[email protected]>
However, developer's site does not even list version 2.1.5. The oldest version mentioned in the release history is 2.3.0 (2018/09/30); 2.1.5 was probably 5+ years ago.
So, is version 2.1.5 in the Ubuntu repository guaranteed to be the 2.1.5 developer had long ago? Or is the Ubuntu repo using its own, unrelated numbering?
It goes like this: I press the shortcut and the caret disappears from the input field for several seconds. Sometimes it comes back on its own, sometimes I have to reach for the mouse to make the input field active again.
Tried various shortcuts. No difference. (Selecting the language with the mouse always works fine, though.) Happens in all apps but most often in Firefox - probably because of its high CPU load. Seems to be a Gnome issue exclusively; KDE switches languages with no weird side effects. Any suggestions?
I'm reading an Ubuntu security guide developed for the US Department of Defense, to be found here. Written for 16.04 but I don't think this particular item has changed much. The guide says,
Group ID (Vulid): V-75583
Group Title: SRG-OS-000480-GPOS-00227
Rule ID: SV-90263r2_rule
Severity: CAT II
Rule Version (STIG-ID): UBTU-16-010840
Rule Title: All world-writable directories must be group-owned by root, sys, bin, or an application group.
Vulnerability Discussion: If a world-writable directory has the sticky bit set and is not group-owned by a privileged Group Identifier (GID), unauthorized users may be able to modify files created by others.
I'm not getting the logic here. Sticky bit on a directory prevents deletion of files, not modification. My only guess is that they are talking not about modifying the file but about reading the file, deleting and then recreating it. This scheme works only if the file was world-readable in the first place, which it should have been not if it was any sensitive.
Overall, I'm lost. Does this rule make any sense at all?
A few weeks of experimentation with libinput led me to believe that many of its advanced mouse-related features are not (yet?) implemented. Most importantly to me, you cannot block the mouse wheel with it, nor can you emulate the mouse wheel system-wide with the middle button. My question is twofold:
libinput to evdev? Am I going to lose anything important, either immediately or in the long run?apt lists dozens of packages for both, some labeled hwe and some not. What should I remove and what should I install instead?
I'm trying to configure libinput according to the official documentation: http://manpages.ubuntu.com/manpages/bionic/man4/libinput.4.html. However, when I set the ScrollMethod property to button with xinput, it does not enable middle button scrolling system-wide. Instead, it blocks the middle button scrolling even in the browsers where it worked before.
How to reproduce this behavior:
$ xinput | grep -i mouse
⎜ ↳ VirtualBox mouse integration id=9 [slave pointer (2)]
⎜ ↳ ImExPS/2 Generic Explorer Mouse id=11 [slave pointer (2)]
$ xinput list-props 11 | grep -i scroll
libinput Natural Scrolling Enabled (266): 0
libinput Natural Scrolling Enabled Default (267): 0
libinput Scroll Methods Available (274): 0, 0, 1
libinput Scroll Method Enabled (275): 0, 0, 0
libinput Scroll Method Enabled Default (276): 0, 0, 0
libinput Button Scrolling Button (277): 2
libinput Button Scrolling Button Default (278): 2
libinput Horizontal Scroll Enabled (273): 1
$ xinput set-int-prop 11 275 8 0 0 1
$ xinput list-props 11 | grep -i scroll
libinput Natural Scrolling Enabled (266): 0
libinput Natural Scrolling Enabled Default (267): 0
libinput Scroll Methods Available (274): 0, 0, 1
libinput Scroll Method Enabled (275): 0, 0, 1
libinput Scroll Method Enabled Default (276): 0, 0, 0
libinput Button Scrolling Button (277): 2
libinput Button Scrolling Button Default (278): 2
libinput Horizontal Scroll Enabled (273): 1
So, what am I doing wrong? The answer "don't bother, it's bugged" will be accepted too.
This no-brainer has been running on my Windows systems since XP:
WheelUp::return
WheelDown::return
$NumpadSub::Send {WheelUp}
$NumpadAdd::Send {WheelDown}
Basically, it blocks the broken wheel of my ancient but otherwise serviceable mouse and allows me to use NumAdd and NumSub instead. What I tried to replace it on Ubuntu with:
xbindkeys + xdotool. Mouse wheel blocking works but mouse wheel emulation does not: 'clicks' emulated by xdotool get blocked by xbindkeys too.xmodmap. All kinds of weird side effects. People say it is deprecated and should not be used.xinput. Does not work at all, supposedly because of a conflict with libevent. Removing the latter as advised on this site disabled my keyboard and mouse completely.xkb but could not find any actionable documentation.Overall, I'm at a loss and thus request something like a solution. Ubuntu 18.04.3.
xinput says my mouse is id 11:
$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ VirtualBox mouse integration id=9 [slave pointer (2)]
⎜ ↳ ImExPS/2 Generic Explorer Mouse id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Sleep Button id=7 [slave keyboard (3)]
↳ Video Bus id=8 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
Setting buttons 4 and 5 to 0 works:
$ xinput --set-button-map 11 1 2 3 0 0 6 7 8 9
$ xinput --get-button-map 11
1 2 3 0 0 6 7 8 9
However, mouse wheel scrolling is not disabled. Any ideas what to do about it? Ubuntu 18.04.3.
ETA: Please note that the answer accepted in How to disable mouse wheel scroll in ubuntu 11.04 or 10.10? does not work, at least in my case.
ETA2: Added as per request:
$ xinput list-props 11
Device 'ImExPS/2 Generic Explorer Mouse':
Device Enabled (127): 1
Coordinate Transformation Matrix (129): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Natural Scrolling Enabled (266): 0
libinput Natural Scrolling Enabled Default (267): 0
libinput Scroll Methods Available (274): 0, 0, 1
libinput Scroll Method Enabled (275): 0, 0, 0
libinput Scroll Method Enabled Default (276): 0, 0, 0
libinput Button Scrolling Button (277): 2
libinput Button Scrolling Button Default (278): 2
libinput Middle Emulation Enabled (279): 0
libinput Middle Emulation Enabled Default (280): 0
libinput Accel Speed (281): 0.000000
libinput Accel Speed Default (282): 0.000000
libinput Accel Profiles Available (283): 1, 1
libinput Accel Profile Enabled (284): 1, 0
libinput Accel Profile Enabled Default (285): 1, 0
libinput Left Handed Enabled (270): 0
libinput Left Handed Enabled Default (271): 0
libinput Send Events Modes Available (249): 1, 0
libinput Send Events Mode Enabled (250): 0, 0
libinput Send Events Mode Enabled Default (251): 0, 0
Device Node (252): "/dev/input/event4"
Device Product ID (253): 2, 6
libinput Drag Lock Buttons (272): <no items>
libinput Horizontal Scroll Enabled (273): 1
There is lots of advice on how to make a program autostart, but the thing I need now is the opposite of that: I want to find out why a certain program starts on boot.
The use case is as follows: After some messing around with xbindkeys I decided to shut down Ubuntu, take a snapshot of the VM, and then make xbindkeys autostart. However, xbindkeys was running already after the boot. How do I find out why?
Tried systemctl, looked into ~/.bashrc and ~/.profile. Not there. pstree says xbindkeys descends directly from systemd.
Ubuntu 18.04.3 LTS.
It seems to be printing only the versions:
$ apt list --upgradable
Listing... Done
dpkg/bionic-updates 1.19.0.5ubuntu2.3 amd64 [upgradable from: 1.19.0.5ubuntu2.2]
file-roller/bionic-security 3.28.0-1ubuntu1.1 amd64 [upgradable from: 3.28.0-1ubuntu1]
libdpkg-perl/bionic-updates,bionic-updates 1.19.0.5ubuntu2.3 all [upgradable from: 1.19.0.5ubuntu2.2]
Tried using "1.19.0.5ubuntu2.3" or just "ubuntu", to no avail as expected:
$ apt show 1.19.0.5ubuntu2.3
N: Unable to locate package 1.19.0.5ubuntu2.3
N: Couldn't find any package by glob '1.19.0.5ubuntu2.3'
N: Couldn't find any package by regex '1.19.0.5ubuntu2.3'
N: Unable to locate package 1.19.0.5ubuntu2.3
N: Couldn't find any package by glob '1.19.0.5ubuntu2.3'
N: Couldn't find any package by regex '1.19.0.5ubuntu2.3'
E: No packages found
$ apt show ubuntu
N: Unable to locate package ubuntu
N: Unable to locate package ubuntu
E: No packages found
So, where are the actual package names? OS version reads Ubuntu 18.04.3 LTS.