** 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.
** 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
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
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
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
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
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
The only custom config I have is to comment out the makestep line. Other
than that I configure things through puppet in a very straightforward
way:
class ntp {
package {"openntpd":
ensure => purged,
}
package {"ntpdate":
ensure => purged,
}
package {"ntp":
ensure =>
I don't think these are crashes at all. The title of the bug needs to be
changed. It seems that systemd is just not starting chrony on boot even
though it does say it's enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It does seem to happen on every boot and it seems timesyncd is the
problem:
$ systemctl is-enabled systemd-timesyncd
enabled
Seems more natural for the opposite to be the default. If
chrony/ntp/openntpd is installed then the systemd version is disabled.
Need to figure out how to disable this
*** This bug is a duplicate of bug 1711101 ***
https://bugs.launchpad.net/bugs/1711101
I don't think this is a duplicate. My laptop does switch from HDMI most
of the time, just not always. And today I just noticed something very
strange. I booted the computer and the audio got set to HDMI
It does seem to happen on every boot and it seems timesyncd is the
problem:
$ systemctl is-enabled systemd-timesyncd
enabled
This did the trick then:
service {"systemd-timesyncd":
ensure => stopped,
enable => false,
hasstatus => true,
}
Seems more natural for the
Public bug reported:
I use the trackpoint on my Lenovo T460s almost exclusively. Even in the
fastest setting on a 2560x1440 screen it is much too slow. I've had to
add the following udev rule to get it to be usable:
ACTION=="add",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
I don't agree this is an invalid bug. It may be hard to fix but it's
still a bug. Editing xml files to get a reasonable user experience is
not a polished desktop. There are already settings (like wifi) that
apply system-wide so there's no reason for mouse and screen settings to
not be the same.
Issue submitted here:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779096
Title:
Mouse speed settings not used on the login screen
How is this different from Wifi and keyboard settings that I'm already
setting system wide? And how does this compromise the security of the
system? The gdm user doesn't need to be able to change my settings. All
it needs is to be able to read some settings to use them instead of the
defaults if
I only see this on Xorg. The wayland session seems to work properly. In
Xorg with 4 fixed virtual desktops the behaviour is the following with a
fullscreen virtualbox instance:
- I start it on desktop 4 and put it fullscreen
- On the virtual desktop list it's on desktop 4 only
- When switching
Public bug reported:
When I'm running a dual-screen setup I sometimes want to put the virtual
machine in the external screen. In gnome-shell+Xorg this works fine by
moving the window to the external screen and then doing Host+F. On
Wayland the same thing causes the virtual machine to always go
Public bug reported:
The login screen doesn't use the mouse hardware settings. In particular
it doesn't seem to use the mouse speed settings. This gives an
inconsistent feeling between the login screen and the desktop if you're
not using the default speed in the desktop. In my case I need to make
Submitted here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/380
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778983
Title:
Resume from suspend on Wayland breaks window positioning
To
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
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
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:
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
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
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.
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:
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:
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
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:
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
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
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
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 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
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
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
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
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:
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:
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
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.
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
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
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
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
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'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
** 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.
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.
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
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
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
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
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
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.
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
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.
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
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
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"
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.
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
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
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
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
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"
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
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
301 - 383 of 383 matches
Mail list logo
