Thanks for that.
It seems you are reporting multiple different issues here. The black
flickering on window resizing seems to be a new problem so I'll make
that the main bug.
The asymmetric artifacts seen when restoring from maximized is an old
bug
Apologies for misinterpreting this issue when initially triaging it - I
have re-marked it as Security. I notice from your linked bug report that
this was still happening with the upstream code as of September 2016 -
but upstream did not appear to engage on the issue. Can you confirm
whether this
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- [regression] Artifacts appears when windows are maximizing or minimizing
+ [regression] Artifacts appears when windows are maximizing or minimizing
(Intel Apollo Lake)
--
You received this bug
This sounds like a problem:
[ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control:
is tagged by udev as: Keyboard
[ 163.566] (II) event10 - Logitech G102 Prodigy Gaming Mouse System Control:
device is a keyboard
** Package changed: xorg (Ubuntu) =>
** Changed in: gnome-desktop
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iso-codes in Ubuntu.
https://bugs.launchpad.net/bugs/991002
Title:
Use the modern English name Bangla instead of
** Changed in: ibus
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iso-codes in Ubuntu.
https://bugs.launchpad.net/bugs/991002
Title:
Use the modern English name Bangla instead of Bengali for
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
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 1292398, so it is being marked as such. Please
** Bug watch added: github.com/ibus/ibus/issues #2104
https://github.com/ibus/ibus/issues/2104
** Also affects: ibus via
https://github.com/ibus/ibus/issues/2104
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch
** Bug watch added: gitlab.gnome.org/GNOME/gnome-desktop/issues #49
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49
** Also affects: gnome-desktop via
https://gitlab.gnome.org/GNOME/gnome-desktop/issues/49
Importance: Unknown
Status: Unknown
** No longer affects:
The xcb/xcb_bitops.h used to be part of xcb-util, but was dropped in
version 0.4.0 from that package and moved to xcb-util-image.
Unfortunately, the package fails to include the header, which can result
in e.g. compilation failures.
It is also affected by Ubuntu 19.04 disco. Compilation for xcb
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1835181
Title:
OpenLDAP LDAP_OPT_X_TLS_REQUIRE_CERT handling
** Package changed: ubuntu => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
Status in
You have been subscribed to a public bug:
"initramfs unpacking failed: Decoding failed", message appears on boot
up.
If I "update-initramfs" using gzip instead of lz, then boot up passes
without decoding failed message.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
This failure has not been due to Juju but rather the setup of the CI
environment. We have not seen any consecutive failures of this nature,
so the issue has been resolved.
I am closing this report.
** Changed in: juju
Status: Incomplete => Fix Released
** Changed in: dbus (Ubuntu)
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
The same problem
ontroller DC:85:DE:56:6C:C4 (public)
Name: dreasty
Alias: dreasty
Class: 0x003c010c
Powered: yes
Discoverable: no
Pairable: yes
On the same system on a different disk I have Ubuntu 18.04 Desktop
installed which does not have this issue.
--
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/1835585
Title:
Is there anything I can do to accelerate the resolution of this bug for
Xenial and Bionic?
I already posted a proposed solution for the specific symbol that I am
missing, but in theory fixing this should be as easy as running whatever
script the package mantainers used in the first place to
The third-party repository story is clearly defined how it should work:
For providers:
For single package repositories, a single .deb should be provided that
contains the program, the key in trusted.gpg.d, and a sources.list.d
snippet.
For multi-package repositories, a .deb should be provided
APT is maintained by 2 people, encouraging a discussion on every bug
report that will likely get ignored anyway would be madness. I think
closing the bug as Opinion is a much better choice than ignoring it for
10 years or so like most other bugs are.
* Various tools would be broken by such a
@juliank - *my suggestion is use variables in apt, which provides an
option. It's not forcing a design decision of how it must be done.
Fedora/RHEL is a good example of where it works and dispels your empty
argument that it causes a terrible user experience.
However, based on your comment, the
@juliank - my suggestion is use variables in apt provides an option.
It's not forcing a design decision of how it must be done. Fedora/RHEL
is a good example of where it works and has dispels your empty argument
that it causes a terrible user experience.
However, based on your comment, what
@Julian Andres,
Sorry for trouble. But I'm still getting HASH MISMATCH with apt-get update.
I don't know why but I think apt is downloading wrong file or repository has
filename with wrong hash. I don't know if it's ISP traffic mangling.
I have downloaded file located in by-hash/sha256 and check
This is your opinion, I don't agree with it. The proposed solution is
highly fragile and causes a terrible user experience.
** Changed in: apt (Ubuntu)
Status: New => Opinion
** No longer affects: apt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
apt sources conventionally use a fixed release name. But this causes
both adding repos as well as upgrading an unnecessarily painful
experience. For instance, adding a simple package requires adding the
keys with `apt-key` and then adding the repo, and then apt update/apt
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We understand the difficulties you
are facing, but
Hi Łukasz,
For disco, all autopkgtests are passing now.
For bionic, the only failing package is kdeconnect. These failures are
caused by OpenSSL update to 1.1.1, not by Qt update. Also, it is a bug
in tests, not in real code. It was fixed upstream yesterday in
26 matches
Mail list logo
