Wow, this time upstream actually added it even if it is not the default
and requires a scary "AllowRiskyCriticalPowerAction=true" setting.
Making it the default after HybridSleep and Hibernate but before
PowerOff would make a lot more sense but at least this doesn't require
the users to manually
I've attached a patch already. I've been running for over a year now
with no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be supported
To
I've once again lost my open session because upower has decided a
shutdown is a sensible thing to do instead of just suspending and
allowing me to just find a charger. Please consider this an actual bug
and not just a "Wishlist" item. It's something that deeply frustrates
users continuously.
You may also want to consider just having Suspend be a fallback option
before PowerOff. These days users are much more likely to have a laptop
that suspends properly and prefer that to happen and just quickly grab a
charger and continue instead of having their computer do a full
poweroff.
**
Please include at least this patch on the package. It allows setting
Suspend as the action but does nothing if the user hasn't explicitly
done that.
** Patch added: "Patch that keeps the defaults unchanged but allows the setting
in the config file"
Thanks for pursuing this. I tried those settings and my paused VM now
uses less than 1% CPU when before it used around 3%. So although I
haven't been able to reproduce the ~30% CPU usage of before it was still
an improvement. It's still odd to me that a paused VM consumes any CPU
at all but at
Annoyingly (for solving the bug but not for me) I haven't been able to
reproduce this in quite a while, which is why I never posted any more
information. I was hoping it was fixed but apparently it's just hard to
reproduce.
It seems odd that the problem could be on the Windows side. I'm assuming
Public bug reported:
I can 100% reliably crash nautilus when running under a sway session.
The steps to reproduce it are simple:
1. Connect an external drive and mount it by browsing to it in nautilus
2. Open a terminal and cd into the drive mount
3. Press the unmount icon for the drive in
Public bug reported:
I use a text-scaling-factor on my 1440p screen to make the fonts
slightly larger. I use this:
$ gsettings set org.gnome.desktop.interface text-scaling-factor 1.3
Audacity will respond to this by scaling up the fonts of the GTK
controls and not the rest. This leads to an
By the way the actual discussion seems to be this one:
https://gitlab.freedesktop.org/upower/upower/issues/59
And this is the unmerged PR with the simple patch:
https://gitlab.freedesktop.org/upower/upower/merge_requests/11
** Bug watch added: gitlab.freedesktop.org/upower/upower/issues #59
Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing
to take the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852911
Title:
CriticalPowerAction=Suspend should be
Public bug reported:
The action to take when the battery is critical can only be one of the
following:
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
Adding Suspend to that list makes perfect sense. My laptop is currently
powering off on low power which is useless as I'll be losing
As far as I can tell qemu will stay at 30% indefinitely in these
situations. I'll produce more diagnostics when I can reproduce it again.
One possible clue is that this may be happening when the VM is waiting
for network responses. I'm not certain of that but it definitely doesn't
happen just
Unpausing the VM, letting it get to a lower level of CPU usage and then
pausing again brings qemu to the more usual ~2% of continuous CPU usage.
Which still seems high but isn't as bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's an example where the VM was at 100% CPU when I paused it to not
have it consume as much CPU as I wasn't using it. After pausing it is
now at 30% CPU usage continuously even though it's paused.
** Attachment added: "qemu-stats"
I can't replicate this on demand. Doing it now only gave me 3% CPU
usage. I'll keep an eye on this and run this diagnostic when it's
happening again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I run a Windows 10 VM for work and sometimes pause it when I'm not using
it. However even when paused it keeps using ~15% of CPU. I'm running it
with virt-manager and that's what I'm using to pause it.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: qemu-system-x86
It turns out this was a hardware issue. Main board has been replaced and
everything seems to be back to working fine.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The BIOS update probably made no difference. I just had the computer
suspend and then be stuck suspended with the glowing light but no way to
resume. The lid open did not wake it and neither did pressing the power
button. A hard reset (long press power) was needed.
--
You received this bug
Public bug reported:
In one of the recent updates suspend is now sometimes broken on the
Lenovo T460s. I've updated the BIOS to the latest but the problem
remains. Sometimes suspend works correctly and other times it just fails
completely. Before the BIOS update it seemed to be stuck on resume
This is most likely a vlc bug and should be reassigned to it. I am
experiencing it in VLC under sway so unless the same bug exists across
sway and mutter it's probably a vlc thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see the tooltip and context menu issue repeatedly. I'm now on a fresh
install of Ubuntu 19.04 on Wayland and running Firefox 66.0.4. So it
doesn't seem to be anything too specific to my install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
When I install the show-ip extension gnome shell no longer works. I
login and am sent back to the login screen after a little while.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-show-ip (not installed)
ProcVersionSignature: Ubuntu
Public bug reported:
The extension installs and shows up in the tweak list but it doesn't do
anything when enabled.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-move-clock 1.01-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic
Public bug reported:
The extension installs and shows up in the tweak list but it doesn't do
anything when enabled.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell-extension-system-monitor 36-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic
Here's a simple way to replicate this bug for me. In both cases I have
the Light theme selected:
$ GTK_THEME="Adwaita:dark" firefox
(firefox runs and the Find box has white text on white background)
$ GTK_THEME="Adwaita:light" firefox
(firefox runs and the Find box has the correct black text on
I seem to have e10s enabled:
Multiprocess Windows1/1 Enabled by default
and have set Adwaita:light:
widget.content.gtk-theme-override;Adwaita:light
I still get white text on white background on the Find textbox within
webpages.
--
You received this bug notification because you are a
** Attachment added: "dmesg output right after initial boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821383/+attachment/5254295/+files/initial_dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
To workaround bug #924648 I've installed the following:
$ cat /etc/udev/rules.d/10-trackpoint.rules
ACTION=="add|change",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="250",
ATTR{device/speed}="250",
While this works I now sometimes get
Public bug reported:
Sometimes when resuming from suspend pulseaudio is broken and only the
dummy output is available. After "pulseaudio -k" audio again works.
Here's what I found in the logs:
$ journalctl --since "1 day ago" | grep pulseaudio
Mar 17 19:40:51 coulson pulseaudio[9447]: W:
I have "Use System Colors" unchecked, `widget.content.gtk-theme-
override` set to `Adwaita` and the Light theme selected. And yet even
then the Ctrl-F input has white text over white background.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm also using Ubuntu 18.04 but using the vanilla GNOME session (that
uses Wayland) with the dark Adwaita theme selected. Could you please
test with that to see if you get the same result?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried:
- Booting 18.04.2 from a usb disk
- The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of
other bugs)
- The 18.04 default Ubuntu Xorg session
all of them seem to be showing reasonable <1% gnome-shell CPU usage
*** This bug is a duplicate of bug 924648 ***
https://bugs.launchpad.net/bugs/924648
I'm not sure if this is a duplicate of it's actually a bug in the
underlying driver and not GNOME.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Another strange thing that happens is that sometimes after
suspend/resume the pointer speed is changed. Right now, using that
250/250 udev rule I was before having just enough speed at maximum
setting. Today after a suspend/resume cycle I now had to set the
trackpoint speed to around 40% to get a
This is another important bug that makes the current Xorg gnome-shell
session noticeably broken when viewing fullscreen video in VLC:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126
The tearing is extremely noticeable when watching videos. I submitted
these two bugs to mutter but
Currently the settings are just barely usable at max speed. Is there any
upstream I can coordinate with to try and get this solved? This is a
really annoying issue. Using these same laptops in Windows has a much
faster pointer.
--
You received this bug notification because you are a member of
Note that vlc is also broken on gnome-shell with Xorg:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809880
The unity session in the previous LTS was a bit clunky in places but it
wasn't nearly as buggy as the current LTS.
--
You received this bug notification because you are a member
The error seems to be that sometimes the driver isn't found at all.
That's why I was suspecting some kind of locking issue. But I should
probably move back to Xorg, there are other Wayland specific bugs as
well in gnome-shell/mutter.
--
You received this bug notification because you are a member
Public bug reported:
When viewing a list of videos and skipping quickly to the next one it's
common for vlc to skip one or several videos with libva errors. I've
only seen this happen on Wayland. Here's an example of a set of videos:
VLC media player 3.0.4 Vetinari (revision 3.0.4-0-gf615db6332)
I hit this bug today by choosing the dark Adwaita theme in Gnome 3.28
and Firefox 65.0. It's amazing that this is an 18 year old bug. I found
it surprising the system theme did anything to webpages and had two
consecutive surprises:
- First setting the system theme to Adwaita-dark changed the
This is probably the same bug as the one I submitted against mutter:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775637
Title:
This seems to at least help:
https://extensions.gnome.org/extension/1445/fix-fullscreen-tearing/
Maybe something like that should be shipped by default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Recently I've had gnome-shell be completely broken on resume from
suspend. The screen contents show the apps with broken positions and
missing decorations and the top bar is shown twice, once in 200% once in
100%. The screen lock is not in place so screen contents are
That will only come out with newer gnome versions, so this would only be
fixed in 20.04 if you're using LTS releases. I'm running the original
patch with no issues, so maybe it would be nice to just add that to the
current package?
--
You received this bug notification because you are a member
I've ran the patch for a few months now with no issues. A new update has
now reverted that so I have to go back and reapply it. Could the patch
just be added to the ubuntu package and be done with it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811902
Title:
Echo cancelation should be enabled by default
To manage notifications about this bug go to:
I don't agree that it's just a Firefox issue. There should be a simple
way to enable this in the normal sound UI, at least as default for
everything and ideally per-app.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree with your point so won't be opening a bug to change the
defaults. But it should be easy to enable somewhere in the GUI sound
settings at least for specific applications. Video conferencing like
appear.in is only really usable with headphones because of this.
Adjusting text config files is
Public bug reported:
Echo cancellation is a basic feature for anything where you are using a
video or audio conference. According to instructions like these:
https://bugs.launchpad.net/elementaryos/+bug/1682253
Public bug reported:
When watching videos in VLC on an external screen there is extremely
visible screen tearing. But it's likely that the external screen only
makes the problem worse as this website shows a lot of vsync issues in
both Firefox and Chromium even with just the single screen:
Public bug reported:
There seems to be a bug, which I assume is in mutter, when viewing
multiple vlc videos fullscreen. The steps to reproduce are simple:
1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a
directory full of video files
2. Press N to move to the next
Bug submitted here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1499336
I searched the related bugs and while there are a bunch of positioning
bugs none seemed to be this one. The firefox subreddit only turned up
one other person with a vaguely similar issue:
I haven't been able to replicate it in a Unity session but I can't
replicate this at will in gnome-shell either so it's hard to confirm
it's a gnome-shell issue. I wouldn't be surprised though as it's been
extremely buggy so far.
--
You received this bug notification because you are a member of
I tested this package:
$ sha1sum light-themes_16.10+18.04.20181005-0ubuntu1_all.deb
d05d75088b41c7594bf3e4e32879d8950983caec
light-themes_16.10+18.04.20181005-0ubuntu1_all.deb
And the bug is indeed fixed for me in virt-manager.
--
You received this bug notification because you are a member
This bug doesn't exist on Wayland. It does seem like GNOME developers
don't care about Xorg anymore and these kinds of bugs won't get fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774177
This happens to me 100% of the time now and is extremely annoying.
Issues like this have made the 18.04 GNOME transition a clear step back
in desktop polish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is an extremely annoying bug which creates quite a lot of lack of
polish of the desktop. Should I be submitting it upstream or something?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1780790
Yeah, I don't really know how to help then. Maybe it's a locale issue
that makes the sorting different? I seem to have everything set to
"en_US.UTF-8" though but am not sure that was the case on initial
install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This was not Incomplete as far as I know. I provided the requested
information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779621
Title:
chrony exits unexpectedly
To manage notifications about
Public bug reported:
Gedit uses Ctrl-Alt-PgUp/PgDown for tab switching when others just use
Ctrl-PgUp/PgDown. That's what gedit should use to be consistent with for
example gnome-terminal and firefox. It also makes sense that Ctrl-Alt is
reserved for more global actions like workspace switching
Since upstream doesn't seem to want to commit the fix could the ubuntu
package add this as a patch? I've rebuilt the package with the patch
from the upstream bug (attached) and it seems to work fine as verified
by other users in the upstream bug.
I couldn't get dpkg-source to actually apply it
So you need me to open a new bug or is this one enough to track the
ubuntu-themes issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785083
Title:
Weird behavior of the VM shutdown dropdown
To
Thanks for all the pointers. Drivers I've been able to get done,
everything is now virtio/QXL and working ok. I meant more things like
hardware setup to avoid BSOD and which are the best versions of windows
to run. I'll probably try and run Windows 10 at some point to see if it
works better. But
I assume it's still a theme as virt-manager didn't stop being a GTK app
because you run KDE, or does it have a Qt replacement UI for KDE?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785083
Title:
I get this on all VMs if they're on. If they're off the dropdown is just
disabled completely and I can't even open it (which makes sense). The
greying out is probably a theming issue, you seem to be using a totally
different one. I've attached a screenshot. Do you not get the inability
to close
Changing the CPU didn't help and it seems changing to q35 will BSOD on
startup as expected. Need to figure out if there's a simple way to
repair the install without reinstalling. I may just need to get a
Windows 10 image instead if that's more compatible in general. But I
wonder about video
Public bug reported:
When a VM is paused and then resumed the clock is then not advanced and
that delta will stay until it's rebooted. I've tested this on both
Windows and Ubuntu VMs, both with qemu-guest-agent installed. I've
verified that I can set the clock manually by doing "virsh domtime
It seems virt-manager doesn't have a way to change that architecture
easily. I'll have to fiddle with the XML to see if I can get it to work.
For now I've tried changing the CPU to be the same as the host to see if
that helps in any way. It's not that much of a hassle though.
--
You received
Public bug reported:
I get a blue screen crash on Windows 7 after resuming it from saved
state. This is a VM that I've ran without issues in virtualbox until now
and have recently moved to virt-manager instead. I don't know what kind
of information is needed to diagnose this.
ProblemType: Bug
Public bug reported:
The VM window includes a shutdown button with a dropdown button next to
it. I've noticed two weird things about it that seem like simple GTK
bugs:
- The dropdown doesn't close just by clicking the dropdown button again
- All the items in the dropdown are greyed out as if
virgl was more of a secondary point, as that requires guest support that
doesn't even really exist in most cases. The QXL default does seem
broken though. At least in Ubuntu 16.04 guests that leads to a broken
display if you change the resolution. I guess that's a bug in the 16.04
xserver QXL
In my case it's almost surely the group membership issue. I found that
online and just rebooted in case there was something else that needed to
be brought up properly. Better safe then sorry. At the very least the
error message should be better but there should be a way to actually fix
this. It's
Public bug reported:
Virt-manager on Ubuntu 18.04 will use QXL as the video device for Ubuntu
16.04 guests (for example). At least with a 16.04 guest this results in
a frozen screen when changing resolution. Switching to virtio drivers
works better but GL enablement doesn't seem to work saying
Public bug reported:
Right after installing virt-manager running it results in an error about
not being able to access the system daemon. This is fixed after a
reboot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: virt-manager 1:1.5.1-0ubuntu1
ProcVersionSignature: Ubuntu
Here's the upstream issue:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/455
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774498
Title:
Windows flash by external screen on workspace change
>As part of that animation, windows from the old workspace fly out and
windows from the new workspace fly in.
This makes perfect sense but there's no reason for that flying to happen
over the external screen as that one isn't changing at all. None of
those windows will ever stop in that space so
Of course "Workspaces span displays" fixes it as everything moves at
once. Putting the external screen on the left or right also fixes it.
But that just shows how the animation is broken. When the screen is on
top and doesn't span displays there's no reason for the contents of the
internal screen
I've disabled all extensions and recorded a video. Here's the output of
lspci:
$ lspci -k
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev
08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor
Host Bridge/DRAM Registers
Kernel
This is the upstream bug report:
https://www.virtualbox.org/ticket/12851
** Bug watch added: Virtualbox Trac #12851
http://www.virtualbox.org/ticket/12851
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I hadn't seen this for a while and it happened again today. The
dumpkeys/loadkeys workaround fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710637
Title:
Input falls through to gdm3 and
** Attachment added: "Example screenshot of the second issue where the URL bar
is consistently misplaced in certain screen/window configurations"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+attachment/5167938/+files/FirefoxWrongPlacement.png
--
You received this bug
Public bug reported:
When viewing multiple videos fullscreen in sequence the image sometimes
block. Here are the steps to reproduce:
1. Create a folder with multiple videos in any format
2. Launch vlc by running something like "vlc *.mp4"
3. Make the video fullscreen by pressing F
4. Skip
$ lspci -k
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev
08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor
Host Bridge/DRAM Registers
Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation HD
Public bug reported:
Today my gnome-shell instance did something extremely strange. Suddenly
around 2/3 of the letters, randomly scattered, were missing from the
interface. I've attached a screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
$ find /etc/systemd/system/ -name "*.conf" | wc -l
0
$ find /etc/systemd/system/ -name "*.service" | wc -l
69
Nothing but service files. Considering how I enabled chrony with puppet
instead of manually maybe that did something else differently?
--
You received this bug notification because you
On the channel we discussed a potential systemd feature of having a
ConflictsDisabled= line that chrony could set that would disable
timesyncd if chrony was enabled. That would fix this issue while also
fixing that one where actively uninstalling timesyncd on chrony install
leaves you without a
Public bug reported:
I've noticed a few problems with misplaced elements in firefox UI that I
am not sure are all the same bug:
- In what appears to be random chance tooltips and menus are often misplaced on
screen. It's common but not fully reproducible. What I see is right-clicking an
Found the issue. I installed libgstreamer-plugins-bad1.0-0 but what I
needed was gstreamer1.0-plugins-bad
** Changed in: gst-plugins-bad1.0 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After installing libgstreamer-plugins-bad1.0-0 the h264parse element is
not available for use:
$ gst-inspect-1.0 h264parse
No such element or plugin 'h264parse'
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer-plugins-bad1.0-0 1.14.1-1ubuntu1~ubuntu18.04.1
After some more discussion it seems that the package needs to guarantee
that timesyncd is disabled to make sure chrony is used. I suggest
changing the title of the bug report to "Chrony install should
automatically disable timesyncd".
--
You received this bug notification because you are a
I talked about this issue in #systemd on freenode and things work like I
suspected from the docs. Just enabling chrony and having that Conflicts
line is not enough to guarantee that chrony and not timesyncd is started
on startup. That just XORs between the two.
--
You received this bug
I've fixed it with puppet anyway so I'm in no hurry. It does seem more
like a systemd bug or usage issue than something specific to chrony.
Maybe someone with systemd expertise would actually be the ideal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "chrony.service"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+attachment/5160221/+files/chrony.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779621
The setup looks like the same:
$ find /lib/systemd/ -name 'chrony.service' -ls -o -name
'systemd-timesyncd.service' -ls
924954 4 -rw-r--r-- 1 root root 1342 Apr 20 17:55
/lib/systemd/system/systemd-timesyncd.service
952832 4 -rw-r--r-- 1 root root
** Attachment added: "systemd-timesyncd.service"
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1779621/+attachment/5160222/+files/systemd-timesyncd.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You're right. I haven't gotten used to journalctl yet. The other day I
used it for the first time and ended doing -r to get reverse to paired
it with head. Here's the correct output:
$ sudo journalctl -o short-monotonic -u systemd-timesyncd.service -u
chrony.service | tail -n 20
[23363.712342]
Reenabled systemd-timesyncd and am back to chrony not starting on boot
so at least I can reproduce at will. Here are the outputs:
$ sudo systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed
Seems like it's a systemd bug if anything then. I only got chrony to
work by disabling timesyncd but apparently you can make this work
without doing that.
The docs don't make it very clear that using conflicts will work
properly:
"""
Conflicts=
A space-separated list of unit names.
*** This bug is a duplicate of bug 1711101 ***
https://bugs.launchpad.net/bugs/1711101
There are two reasons I wonder if it's a duplicate:
- bug 1711101 mentions that "We now have autoswitching on connect in 17.10, but
not on disconnect". This is not the behavior I'm seeing. Autoswitching
1 - 100 of 383 matches
Mail list logo
