There weren't any keyboard landings in OTA 14 either. While there
weren't any Mir landings, there was a qtmir landing in OTA 14, so I've
added that to the bug as a possible place to investigate as well.
** Also affects: qtmir
Importance: Undecided
Status: New
--
You received this bug
Since this number comes before the other, if it were a duplicate, it would be
the other way around.
While maybe related it is another bug related to ipv6 as far as I can read.
The pile of crap coming from changes in networkmanager, vpn, dnsmasq or
wherever they come from is horrible : I have
Public bug reported:
bhikkhusubhuti@Subhuntu:~$ lsb_release -rd
Description:Ubuntu 16.10
Release:16.10
bhikkhusubhuti@Subhuntu:~$ apt-cache policy alsa-base
alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
*** 1.0.25+dfsg-0ubuntu5 500
I hate to say this.. but "It works in Windows" (dual boot but nearly empty on
Windows).
Perhaps this is useful even though you do not like this phrase.
The Acer website has a 250 megabite Realtek driver for windows. I have
it downloaded but have not done anything with it. I am not sure if
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
** Patch added: "xenial_resolvconf-lp1649931.diff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4792030/+files/xenial_resolvconf-lp1649931.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
Impact
==
Some bugs in evolution-data-server (e-d-s) were causing daily limit errors
for those using Google services with evolution-data-server and apps that use it
(Evolution is a prominent example). Unfortunately, it looks like users using
older versions of
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
Yes.
$ apt-cache policy libpam-cgfs
libpam-cgfs:
Installed: 2.0.4-0ubuntu1~ubuntu16.04.1
Candidate: 2.0.4-0ubuntu1~ubuntu16.04.1
Version table:
*** 2.0.4-0ubuntu1~ubuntu16.04.1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
100
This bug was fixed in the package vim - 2:8.0.0095-1ubuntu2
---
vim (2:8.0.0095-1ubuntu2) zesty; urgency=medium
* ubuntu-series-support.patch: Drop vivid and wily from supported
list.
-- Adam Conrad Tue, 06 Dec 2016 03:03:48 -0700
** Changed in: vim
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
Ok, a bit more info, copying from
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c62
--
The internal Google OAuth2 authentication had been introduced in eds 3.20.0
(thus it's pretty new), for which I released eds 3.20.6 with all the yet-known
fixes recently, in a hope that distros which
The attachment "xenial_resolvconf-lp1649931.diff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1650022
Title:
We need a "close" action for killing
Please attach the container config file and show or attache the output
of the following commands:
- grep cgroup /proc/1/mountinfo
- cat /proc/self/cgroup
- ls -al /sys/fs/cgroup
- lxcfs --version
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
The real cause here is we rely on focusOut(In)Event to check for
activeFocus item. but the any check of ActiveFocus (hasActiveFocus or
window->activeFocusItem) inside focusout/in event give incorrect result.
when another item is focused(location bar), window->activeFocusItem()
return null not the
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
Related bugs:
* bug 1229458: grub2 needed changes
* bug 1621615: network not
@caribou
@rbasak
Let me share the work (since rbasak seems to like the approach) I've
done so far on my above recent proposal :
isc-dhcp-client: dhclient with DDNS functionality enabled
isc-dhcp-client-noddns : dhclient with DDNS functionality disabled
This is a working debdiff, I think
Hello,
I am fighting exactly with the same problem. Is there any workaround?
Thanks
BR
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1606600
Title:
Public bug reported:
Many times (around ~60% of them), resuming my laptop from suspend
results in a not-working keyboard.
Solution/Workaround is: close lid, let it suspend again, and try to
resume until keyboard gets working again.
Another solution is: plug an usb keyboard, and run something
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
This bug was fixed in the package mir - 0.25.0+17.04.20161203-0ubuntu1
---
mir (0.25.0+17.04.20161203-0ubuntu1) zesty; urgency=medium
* New upstream release 0.25.0 (https://launchpad.net/mir/+milestone/0.25.0)
- ABI summary:
. mirclient ABI unchanged at 9
.
** Description changed:
Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.
This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd
Completely broke my 16.04 to 16.10 upgrade. Really bad. Thankfully I
backed the VM up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1551623
Title:
package gconf2
Hello Stéphane, or anyone else affected,
Accepted lxc into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
i started the update my Lubuntu version to the latest version i waited
for the update to finish while i was doing a few other things.. i had
to get done to not disturb the computer... after the auto-restart .. i
went to the power menu to shut down .. both that and the reboot
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1650354
Title:
system error on login after a power button reboot becuase
Hello Stéphane, or anyone else affected,
Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.6-0ubuntu1~ubuntu16.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: resolvconf (Debian)
Status: New => Fix Committed
--
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/1636912
Title:
systemd-networkd runs too late for
** Patch added: "xenial-dns-before-online-target-lp1649931.debdiff"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+attachment/4792126/+files/xenial-dns-before-online-target-lp1649931.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
The Test Case is rather incomplete for an SRU. Could you add some
information about how the changes will be tested and we will ensure
there are no regressions?
Thanks!
** Changed in: mesa (Ubuntu Yakkety)
Status: Confirmed => Incomplete
--
You received this bug notification because you
** Changed in: gdb (Ubuntu)
Milestone: ubuntu-17.02 => None
** Changed in: gdb (Ubuntu)
Assignee: Matthias Klose (doko) => Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in
I've accepted a new version of open-iscsi in yakkety, but the SRU tools
barfed on modifying the bug.
** Changed in: open-iscsi (Ubuntu Yakkety)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello Stéphane, or anyone else affected,
Accepted lxc into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/lxc/1.0.9-0ubuntu1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This is blocked by the fact that 4.2.0 is stuck in zesty-proposed.
** Changed in: zeromq3 (Ubuntu Yakkety)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
I’m occasionally seeing that when I run webbrowser-app in a VirtualBox VM.
Never seen it on my work laptop, but that one has 16GB, which is plenty.
How much memory overall does your system have?
** Changed in: webbrowser-app (Ubuntu)
Status: New => Incomplete
--
You received this bug
This fix made it into Yakkety and Zesty, but not Xenial. I've uploaded
a fix to the Xenial SRU queue for review by the Ubuntu SRU team.
** Also affects: nano (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: nano (Ubuntu Xenial)
Status: New => In Progress
**
All non-MAAS remote rootfs -based test cases have been verified for
Yakkety now. Everything checks out. I will now do the last test case
remaining which is to do a standard (non-remote root) install and
upgrade to proposed packages to make sure standard installs aren't
broken.
** Description
Final review feedback has been incorporated into initramfs-tools, isc-
dhcp, and open-iscsi, and uploaded to zesty.
** Description changed:
initramfs' configure_networking function uses ipconfig to configure the
network.
ipconfig does not support dhcpv6. See:
Hello Ryan, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
resolvconf (1.79ubuntu4) zesty; urgency=medium
* debian/resolvconf.service: Add missing Wants=network-pre.target.
-- Martin Pitt Thu, 08 Dec 2016 10:21:12
+0100
resolvconf (1.79ubuntu3) zesty; urgency=medium
* debian/resolvconf.service: resolvconf service must
** Tags removed: unity-desktop
** Tags added: unity8-desktop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1650022
Title:
We need a "close" action for killing an app in a
Invalid for GTK. I have now reproduced the same bug using a pure Mir
demo (which is software rendered in case that's relevant):
$ mir_demo_client_progressbar 20 --desktop_file_hint=unity8
** Changed in: ubuntu
Status: Confirmed => Invalid
** Summary changed:
- [regression] resizing a
Also the bug does not exist in Mir demo servers.
This is just a QtMir/Unity8 bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1649662
Title:
[regression] resizing a some
Confirmed. The bug has now escaped proposed and is in zesty.
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Hello Ryan, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
while upgrading from ubuntu 16.04 LTS to 60.10
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: ca-certificates 20160104ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture:
On Thu, Dec 15, 2016 at 09:44:32PM -, Ryan Harper wrote:
> On Thu, Dec 15, 2016 at 10:27 PM, Brian Murray wrote:
> > How is this fixed in the development release?
> For systemd portion, we carry the
> systemd-networkd-resolvconf-update.service as a delta from Debian
I'm
** Changed in: isc-dhcp (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: initramfs-tools (Ubuntu Xenial)
Milestone: None => xenial-updates
** Changed in: initramfs-tools (Ubuntu Xenial)
Assignee: (unassigned) => Mathieu Trudel-Lapierre
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Summary changed:
- resizing a gtk+3/mir app makes it unusable - pixels get stretched and input
stops working
+ [regression] resizing a gtk+3/mir app makes it unusable - pixels get
stretched and input stops working
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alsa-driver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
>> For systemd portion, we carry the
>> systemd-networkd-resolvconf-update.service as a delta from Debian
> I'm not sure what you mean here; the systemd package in zesty is currently
> in sync with Debian.
Ok, it appears that post-16.04, systemd-networkd-resolvconf-
update.service is dropped
You can run the scope with U1_DEBUG=1 set, and it will spew more debug
info.
I doubt it's threads. We're not using QtDBus here really. The ubuntu-
download-manager code does use it, but we're no longer really using it
in the scope, only the client object gets created on startup, and then
never
zesty has 12.0.4, and 13.0.2 in proposed, closing
** Summary changed:
- Mesa 12.0.4 - multiple important fixes, stable branch
+ Mesa 12.0.5 - multiple important fixes, stable branch
** Description changed:
[Impact]
- Mesa 12.0.4 is now available as a point release in the stable branch. Mesa
** Also affects: bamf (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1650419
Title:
package ca-certificates
On Thu, Dec 15, 2016 at 09:43:48PM -, Ryan Harper wrote:
> I don't disagree (that saying few folks impacted means low).
> This portion was split out from the previous systemd SRU
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636912
> in which the changes were classified in the
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: resolvconf (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Description changed:
For some reason I often find that if I try to report a .crash (which the
GUI for some reason didn't alert me about) file this will happen (this
happens with all the Apport tools to report a crash, this just so
happens to be the apport-cli example):
-
*** Send
On 15/12/16 17:25, Steve Langasek wrote:
> This was a known limitation when the SRU went through, and it was
> allowed because the understood target for snapd on 14.04 was
> server/cloud environments, not desktops. Has that changed?
It's unexpected for me, and will be substantially difficult to
** No longer affects: ubuntu-gnome
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1649960
Title:
Apport fails to upload some crash reports
Status in Apport:
New
Status
sorry while upgrading from ubuntu 16.04 LTS to 16.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ca-certificates in Ubuntu.
https://bugs.launchpad.net/bugs/1650419
Title:
package ca-certificates 20160104ubuntu1 failed
1 - 100 of 167 matches
Mail list logo