@sil2100, where can I take a look at those?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1781597
Title:
[SRU] WoWLAN settings are not supported
Status in
Can confirm that installing kernel 5.0-rc1 using UKUU that sound from
the speakers and earphones now work on my Zenbook UX391UA.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Here is the content of /var/log/cups/error_log:
E [06/Jan/2019:21:05:26 -0800] [cups-deviced] PID 15777 (gutenprint52+usb)
stopped with status 1!
E [06/Jan/2019:21:05:44 -0800] [CGI] Unable to create PPD file: Printer does
not support required IPP attributes or document formats.
E
Can you explain in more detail what you were doing when the machine
stops responding?
Next time it happens, please reboot, log in again and run:
journalctl -b-1 > prevboot.txt
and then send us the file 'prevboot.txt'.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Package
Please run this command to send us more information about the system:
apport-collect 1810861
** Summary changed:
- Speakers dont show or make audio
+ USB type C audio adapter (from a Pixel 3) doesn't produce any sound
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Also
** Tags removed: rls-dd-incoming
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1805857
Title:
network-manager dep8 failure blocks dnsmasq
Also, disabling bluetooth seems to be done entirely at the
rfkill/systemd/kernel level. BlueZ is not involved, and bluetoothd stays
active regardless. bluetoothd just loses access to the hardware when
it's disabled.
** Package changed: bluez (Ubuntu) => ubuntu
--
You received this bug
It appears the state is stored by rfkill, in:
/var/lib/systemd/rfkill/*
Maybe Budgie isn't setting it (indirectly) properly...
John, can you please run this command and send us the output (after
disabling Bluetooth)?
grep . /var/lib/systemd/rfkill/*
Also, what is the name of the tool you
** Changed in: libreoffice-dictionaries (Debian)
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to hunspell-en-us in Ubuntu.
https://bugs.launchpad.net/bugs/1718869
Title:
Migrate to
I'm not sure what you mean by init scripts. Init scripts have long been
replaced by systemd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1809783
Title:
Bluetooth always
** No longer affects: gnome-translate (Ubuntu)
** Also affects: gnome-vfs (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
libgnome has been removed from Debian Testing and will not be included
in the Debian 10 "Buster" release. We should do the same. If we do it
** Changed in: libgnome-keyring (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgnome-keyring in
Ubuntu.
https://bugs.launchpad.net/bugs/1771036
Title:
Please remove
Not myself, no. That was just to cover duplicate bug 1809856. If that's
incorrect, feel free to remove it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
This bug was fixed in the package cowdancer - 0.88
---
cowdancer (0.88) unstable; urgency=medium
[ Mattia Rizzolo ]
* Fix bash completion to work with a dynamic _have() instead of the static
have(). LP: #1792835
* Bump debhelper compat level to 12, using the new
This is related to the usrmerge transition. On a freshly debootstrapped
disco environment, /lib is a symlink to /usr/lib, which means the
canonical path for the debug symbols as looked for by valgrind is
/usr/lib/debug/usr/lib/x86_64-linux-gnu/ld-2.28.so which does not exist;
only
Public bug reported:
I use a logitech z200 that works fine, i use it with a usb type c
adapter that came with my pixel 3, my speakers arent shown at all in the
settings or make sound, its not the usb c adapter because it works fine
on my windows dual boot and has worked at one point on ubuntu,
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546
Is there really any reason why keyboard-configuration.postinst passes
--force to setupcon?
In Debian we do this in the Debian installer because it is running
within a bterm and thus can't detect it's running
As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch.
** Attachment added: "proposed fix"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch
--
You received
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-cosmic verification-done-xenial
--
You received this bug notification because you are a member of
The new package version numbers do not appear in the bucket at
https://errors.ubuntu.com/problem/b13c9466e8741d31ba6c9934365589f383a60650,
additionally there are no other crashes re software-properties which are
the result of an AttributeError in on_driver_selection changed so there
isn't a new
Public bug reported:
After ticking the checkbox for whoopsie to automatically always send
crash reports, I get the following error dialog (screenshot attached):
*Can't remember send report status settings*
Saving crash report state failed. Can't set auto or never reporting mode.
Command
** Description changed:
[Impact]
software-properties-gtk is crashing regularly for users of Ubuntu stable
releases.
[Test Case]
We aren't sure what exactly is causing the crash but we don't need to be
given that there is a bucket in the Error Tracker with a large number of
crashes.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
systemd. This problem was most recently seen with package version
239-7ubuntu10, the problem page at
https://errors.ubuntu.com/problem/c29cf98f06b61108620dd3741feb677ab845b9db
contains more
"reporting bugs to the effect that a no-change update should finish
instantly."
By definition, if the on-disk copy is corrupt, there is an change-update
available.
The algorithm for update should look like this:
- does the local copy exist? No -> update available
- is the local copy valid
I did some more poking this morning and followed up to the thread. A
change in 2.80 has made this start happening. I'm hoping that someone
upstream will understand what's going on enough to propose a fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Package changed: ubuntu => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1809819
Title:
Ubuntu will not unlock non-root LUKS devices when booting
You have been subscribed to a public bug:
Ubuntu will not unlock non-root LUKS devices (with the same passphrase)
when booting without "splash" kernel argument.
Please see the video I've recorded (in VirtualBox)
https://my.nixaid.com/s/epxpwHckGipcB6D
It feels like systemd-ask-password-plymouth
The bluetooth status should be store/restored by the bluez init scripts
** No longer affects: gnome-shell (Ubuntu)
** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
You have been subscribed to a public bug:
Bluetooth works properly but it's always turned on on startup and I have
to turn it off manually
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux
Public bug reported:
aprendo le pagine il computer va in blocco e non risponde piu ai comandi
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
.tmp.unity_support_test.0:
Note that the file we have in lists/ is not what we downloaded as we
have downloaded a highly compressed version of the content (e.g. xz),
but store it either uncompressed (for which we have a checksum) or
lightly compressed (e.g. lz4 for which we have no checksum and can not
as different versions
** Changed in: gnome-boxes (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: gnome-boxes (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Sorry for the late reply - I've been on vacation over the Christmas
period.
The problem seems to have disappeared with 7.3.0-2 that is now in the
release pocket. It might have been fixed by "Fix check for
rl_completion_matches in readline extension" that seems to exist in
src:php7.3 7.3.0-2 but
** Changed in: ubuntu-power-systems
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764628
Title:
incorrect hypervisor and virtualization
Public bug reported:
Hello,
I have hosts with short-leaved DHCP leases.
Every time a lease is renewed systemd-resolved gets restarted and the
daemons attempting to resolve names get permanent errors.
gethostbyname returns NO_RECOVERY and that leads to more or less severe
failures.
That would
I agree.
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1809174
Title:
apt doesn't detect file corruption in
Daniel,
Do you observe this on 9370?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1654448
Title:
Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
Status in
That were quite some updates, but it shows
- the fix in >=Cosmic came in via systemd
- (at least atm) I do not intend to fix it in Bionic Qemu
- gnome-boxes in Bionic is affected and could get a fix (the suggested
auto-adding of users to
group kvm if you want that)
--
You received this bug
Hi - Jeremy yes, not in qemu at least.
IMHO this is
a) a user configurable change (add user to kvm group) (so it isn't very high
severity)
b) a fix in older versions is limited to gnome-boxes which
It makes no sense to do (b) for qemu as it works without it just fine.
The latter changes I
I was picturing scenario (1); if there are updates or the checksum on
the existing doesn't match, download the index.
apt has trained users to "apt update" before doing anything else, so
this would be okay.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
So, 0.166s is very expensive in the sense that we can't do it every time
we open the cache. We're literally optimizing every 10ms we can get
there - apt-cache show would be twice as fast.
There are two more points where we could do those checks, though:
(1) in update - we can check if the lists
Filesystem is ext4
ubuntu@T00-tx2b:~$ mount
/dev/mmcblk0p1 on / type ext4 (rw,relatime,data=ordered)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1809174
Title:
apt
The problem with deferring the situation to the clean command is that
the system appears to be working properly with no problem, and the user
will have to _guess_ that cleanup is required.
Running md5sum on the packages is not expensive:
ubuntu@T00-tx2b:/var/lib/apt/lists$ time md5sum
thanks for pointing out
could you suggest how to reduce and/or disable this backup numbers?
3 versions make 90% usage of my /boot and very often next update fails
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
Added hplip to the affects list for this bug because hpijs-ppds appears
to only be installing a few fax PPDs, not the full array of available
HPLIP PPDs.
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I was having this problem on Ubuntu 18.10 (WOW, THIS PROBLEM HAS BEEN
AROUND FOR A VERY LONG TIME) with my HP LaserJet 500 color M551 printer.
When I tried to install it, the driver that kept getting selected was
"HP LaserJet 500 color M551, driverless, cups-filters 1.21.3". This,
despite the fact
$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage
2>/dev/null
-37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon
2018-09-10 08:05:57 CEST
Archived and active journals take up 1.8G in the file system.
My interpretation is my systems' situation is that
This seems to be working correctly, you have your current kernel, and 2
backup kernels.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Hi We are brother printer technical support provider who provide best
Brother Printer Customer Service For Usa brother Printer customer. Dial
1800-436-0509 to help or Visit>> https://www.printertollfreenumber.com
/brother-printer-support
--
You received this bug notification because you are a
Verifying the checksums in normal operation is too expensive. I think it
would be reasonable to make the clean command do that, and remove broken
files.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
I'm just curious, but what filesystem are those filesystems on? My
understanding is that 0 byte files should not happen on ext4 at least.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
hello
as suggested by /usr/bin/purge-old-kernels
filing a bug
1)
lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2)
apt-cache policy apt
apt:
Installed: 1.6.6
3)
Expected:
uname -a
Linux 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018
And I do not know if it changes something but I have this workaround
active too: http://iam.tj/prototype/enhancements/Windows-acpi_osi.html
Plus, I have tried the fixes in your first post with no more luck for the
crackling sound.
* `options snd-hda-intel position_fix=1` in
Verification done with OCI and KVM instances for 18.04 and 16.04.
Working as expected and no regressions found.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You
For me the steps from this tutorial https://era86.github.io/2017/10/03
/asus-zenbook-3-volume-controls.html have done the trick in order to
control the internal speaker volume. But unfortunately it is more a
workaround than a real fix since I still have crackling sound... :'(
--
You received
*** This bug is a duplicate of bug 1773700 ***
https://bugs.launchpad.net/bugs/1773700
@vanvugt: the gif is relevant in order to understand well the bug I
think, I mean it may show the correct way of handling some devices but
as I said in my case changing PCM volume is the only way to get
This bug was fixed in the package ca-certificates - 20170717~14.04.2
---
ca-certificates (20170717~14.04.2) trusty; urgency=medium
* Add ca-certificates udeb package (LP: #1807023)
-- Mauricio Faria de Oliveira Thu, 06 Dec 2018
16:20:55 -0200
** Changed in: debian-installer
What packages and package version have been used for verification? We
need at least the basic info regarding the verification performed as
part of the SRU.
** Changed in: mountall (Ubuntu Trusty)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a
This bug was fixed in the package debian-installer -
20101020ubuntu451.27
---
debian-installer (20101020ubuntu451.27) xenial; urgency=medium
* build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS
without d-i/allow_unauthenticated_ssl in stock initramfs image
as in
This bug was fixed in the package debian-installer -
20101020ubuntu318.45
---
debian-installer (20101020ubuntu318.45) trusty; urgency=medium
* build/pkg-lists/base: add ca-certificates-udeb to enable HTTPS
without d-i/allow_unauthenticated_ssl in stock initramfs image
as in
This bug was fixed in the package ca-certificates - 20170717~16.04.2
---
ca-certificates (20170717~16.04.2) xenial; urgency=medium
* Add ca-certificates udeb package (LP: #1807023)
-- Mauricio Faria de Oliveira Thu, 06 Dec 2018
16:20:55 -0200
** Changed in: ca-certificates
I'm not sure if it's related but you seem to have an Nvidia driver
installed, despite only having an Intel GPU...
DkmsStatus:
nvidia, 390.87, 4.15.0-42-generic, x86_64: installed
nvidia, 390.87, 4.15.0-43-generic, x86_64: installed
Can you please explain in more detail what problem you see?
** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1810050
Title:
screen glitch in dock
Status
*** This bug is a duplicate of bug 1773700 ***
https://bugs.launchpad.net/bugs/1773700
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1773700, so it is being marked as such. Please
** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
+ [UX390UAK, Realtek ALC295, Speaker, Internal] very loud and crackling
*** This bug is a duplicate of bug 1773700 ***
https://bugs.launchpad.net/bugs/1773700
The animation in volume-issue.gif doesn't seem to show any bug that I
can see.
My working system has the same behaviour, so I don't think the gif is
relevant.
--
You received this bug notification
Please run this command and send us the output:
grep . /sys/class/drm/*/enabled
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch
** Tags added: radeon
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1810165
Title:
Some black colors are shown in orange
Status in xorg package in Ubuntu:
Invalid
Bug
** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1351531
Title:
[HP Pavilion 15 Notebook PC, Realtek
** Summary changed:
- External mic not detected and/or used trrs jack ALC283
+ [Aspire V3-572PG] External mic not detected and/or used trrs jack ALC283
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
> I was trying unsuccessfully to load gpsim at the time the bug came to
my attention
What do you mean by "the bug came to my attention"? What did you see?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug
They kernel says it is using the Nvidia driver:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS 310]
[10de:107d] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GF119 [NVS 310] [10de:1154]
...
Kernel driver in use: nvidia
And
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1810574
Title:
Audio is low
Next time a freeze happens:
1. Reboot.
2. Run this command to collect the log from the previous frozen boot:
journalctl -b-1 > prevboot.txt
3. Attach the file 'prevboot.txt' here.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Package changed: xorg (Ubuntu) => ubuntu
--
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since there isn't enough information in your report to differentiate between a
local configuration problem and a bug in Ubuntu, I'm marking this bug as
Incomplete.
If indeed this is a local configuration
Your resolution is incorrect because you have booted with the
'nomodeset' option:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=2d93d825-1bcb-4155-aad5-cfdb5dce95ab ro quiet splash nomodeset
So it is correct for the normal resolutions to be missing in that case.
To fix
Can you please run this command:
dpkg -l > allpackages.txt
and then attach the resulting file 'allpackages.txt'?
** Tags added: cosmic
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks Pawel!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1784485
Title:
[ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Status in alsa-driver
Can you please try editing /etc/gdm3/custom.conf and uncommenting this
line:
#WaylandEnable=false
Then reboot, but make sure you're not rebooting into recovery mode
again.. Does that fix it?
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Summary changed:
- XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
+ XPS 13 9350, 9360 and 9370 headphone audio hiss
** Summary changed:
- XPS 13 9350, 9360 and 9370 headphone audio hiss
+ Dell XPS 13 9350, 9360 and 9370 headphone audio hiss
--
You received this bug
*** This bug is a duplicate of bug 1654448 ***
https://bugs.launchpad.net/bugs/1654448
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1654448, so it is being marked as such. Please
If the mouse is moving and nothing else works, and if you're using a
Xorg session, then that means gnome-shell has frozen.
If you have any extensions installed then please start by uninstalling
those and tell us if the problem still happens.
** Package changed: xorg (Ubuntu) => gnome-shell
*** This bug is a duplicate of bug 1760849 ***
https://bugs.launchpad.net/bugs/1760849
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1760849, so it is being marked as such. Please
Can you please attach a screenshot or photo of the problem?
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch
Sounds related to bug 1518677.
** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
The Xwayland binary comes from source package 'xorg-server' so
reassigning to that.
** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu)
** Tags added: amdgpu
** Summary changed:
- Small windows output corrupted in XWayland clients
+ [amdgpu] Small windows output corrupted in XWayland
This bug was fixed in the package libgweather - 3.28.2-1~ubuntu18.04.1
---
libgweather (3.28.2-1~ubuntu18.04.1) bionic; urgency=medium
[ Marco Trevisan (Treviño) ]
* Backport from unstable to bionic
- New upstream release: 3.28.2 (LP: #1803487)
* debian/control:
- use
The verification of the Stable Release Update for libgweather has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gnome-shell - 3.28.3-0ubuntu0.18.04.4
---
gnome-shell (3.28.3-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/ibus-set-content-type-no-holdKeyboard.patch:
- Cherry-pick upstream commit to prevent focus stealing on password fields
The verification of the Stable Release Update for gnome-shell has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu1.18.10.2
---
gnome-shell (3.30.1-2ubuntu1.18.10.2) cosmic; urgency=medium
* debian/gbp.conf: Specify the right packaging branch
* Cherry-pick upstream commit to prevent focus stealing on password fields
in firefox
Seeing that no reports have been sent so far, I consider Daniel's
sanity-check in comment #58 as a sufficient verification for cosmic.
** Tags removed: verification-needed verification-needed-cosmic
** Tags added: verification-done verification-done-cosmic
--
You received this bug notification
There is a series of systemd related autopkgtest regressions listed for
this upload. At first glance those seem to be unrelated as the test
suite is generally flaky, but I'd like someone to take a look at those
and double confirm before we release this to the world.
--
You received this bug
This bug was fixed in the package alsa-lib - 1.1.6-1ubuntu1.2
---
alsa-lib (1.1.6-1ubuntu1.2) cosmic; urgency=medium
* d/p/0013-configure-Fix-forgotten-ucm-entry.patch
- enable line-out on the Dell WD Dock stations (LP: #1806532)
alsa-lib (1.1.6-1ubuntu1.1) cosmic;
The verification of the Stable Release Update for alsa-lib has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package pango1.0 - 1.42.4-3ubuntu1
---
pango1.0 (1.42.4-3ubuntu1) cosmic; urgency=medium
* Backport the emoji & Unicode 11 updates from pango 1.43 (LP:
#1808075)
-- Jeremy Bicha Sat, 15 Dec 2018 12:14:09 -0500
** Changed in: pango1.0 (Ubuntu Cosmic)
1 - 100 of 102 matches
Mail list logo
