Public bug reported:
apt-get install synaptic and synaptic will not run from unity dash. Need
to use sudo or sudo -H from terminal
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-4
ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15
Uname: Linux 4.4.0-9134-generic x86_64
A
Public bug reported:
After install mono-runtime I expect a adding "Mono Runtime" entry to
“Open With” menu but this isn't appear.
OS: Ubuntu 16.04.1 LTS
[FIX] modify line "Exec=mono" in file
/usr/share/applications/mono-runtime-common.desktop:
Exec=mono %F
** Affects: mono (Ubuntu)
Importa
** Description changed:
- I am in need of doing some diagnostics work with "xdiagnose", however
- when searching for it in the Activities Overview, and then clicking on
- it, absolutely nothing happens, when in the past it would ask me for my
- password so that I could run it as root.
+ Impact
+ =
This bug was fixed in the package livecd-rootfs - 2.429
---
livecd-rootfs (2.429) yakkety; urgency=medium
* live-build/auto/build: Fix typo in netplan policy snippet.
*brown paperbag* (LP: #1615180)
-- Martin Pitt Sat, 20 Aug 2016 06:56:37
+0200
** Changed in: livecd-rootfs
** Changed in: evolution-data-server (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: evolution (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Also affects: gnome-shell (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: xdiagnose (Ubuntu Xenial)
Importance: Undecided
Status: New
** No longer affects: gnome-shell (Ubuntu Xenial)
** Changed in: xdiagnose (Ubuntu Xenial)
Status: New => Triaged
Where is the fix. I still experience it in 16.04. Using 2.0.1* version.
2 monitors, black screen, 100% CPU Usage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426664
Title:
After booting to light
May be related to bug #1577137
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613027
Title:
Network scanner not detected by xsane after upgrade to 16.04
To manage notifications about this bug go to
I'm also having the same or similar problem with my Epson WF-3520. Worked find
at 15.10, nothing after 16.04 upgrade. I was a little confused about which set
up some of the comments described here. Mine is a printer / scanner directly
connected to the router and accessed wirelessly. So in theory
The verification for 2.15 failed on xenial, so 2.15.1 was released with
a few small fixes.
I tested it in an up-to-date xenial virtual machine with kvm.
I installed snapcraft, snapcraft-examples and snapcraft-parser, version
2.14. Then enabled proposed and updated those packages to 2.15.1.
Then
tests ran: 136, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_04-46-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612305
Title:
lin
Public bug reported:
Each time I restart Rhythmbox, it deletes my list of music and it also
refuses to re-import it too.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x8
Nothing that depends on ubuntu-push has yet been seeded in main. Re-
demoting until this is done.
** Changed in: ubuntu-push (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Nothing that depends on ubuntu-settings-components has yet been seeded
in main. Re-demoting until this is done.
** Changed in: ubuntu-settings-components (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Nothing that depends on network-manager-openvpn has yet been seeded in
main. Re-demoting until this is done.
** Changed in: network-manager-openvpn (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Nothing that depends on indicator-transfer has yet been seeded in main.
Re-demoting until this is done.
** Changed in: indicator-transfer (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Nothing that depends on indicator-transfer-buteo has yet been seeded in
main. Re-demoting until this is done.
** Changed in: indicator-transfer-buteo (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
aodh is not seeded in main and has no reverse-dependencies in main.
Demoting these packages again until this happens.
** Changed in: python-cotyledon (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: python-setproctitle (Ubuntu)
Status: Fix Released => Fix Committed
--
** Branch linked: lp:livecd-rootfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615180
Title:
Still no networking in Ubuntu GNOME yakkety daily iso after livecd-
rootfs 2.428
To manage notifica
This package was promoted to main without being seeded or added as a
dependency to any package in main. Demoting again until this is done.
** Changed in: aodh (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: livecd-rootfs (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615180
Title:
Still no networking in Ubuntu GNOME yakkety daily iso a
** Changed in: xdiagnose (Ubuntu)
Status: Invalid => Triaged
** Changed in: ubuntu-gnome
Status: Confirmed => In Progress
** Changed in: ubuntu-gnome
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
> OpenStack Mitaka requires the barbican package.
There is no package in main which depends on barbican. It has been
promoted to main, but now is listed in components-mismatches as
requiring demotion.
http://people.canonical.com/~ubuntu-archive/component-mismatches-
proposed
What is meant to be
** Attachment added: "Epson scan utility cannot communicate with device, while
printer utility communicates."
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1608604/+attachment/4724437/+files/ScanVsPrinter%20setting6.png
--
You received this bug notification because you are a member of U
** Attachment added: "Simple scan properties is confused over the device."
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1608604/+attachment/4724436/+files/ScanVsPrinter%20setting3.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Screenshots shows how the printer module and scan module is confused
over the same device. Printer module identifies the printer but the scan
module is confused. Please help. see attached photos which shows the
problem.
** Attachment added: "Xsane screen showing confusion and correct printer
pro
The general logic in livecd-rootfs is now fine -- there is an
/etc/netplan/01-network-manager-all.yaml, but the generator fails as
there is a typo in it (missing ':'). Argh!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Interestingly, I still get the partial vertical line drawn even now that
nautilus doesn't draw the screen background on startup (I have to
manually run it from the launcher to get the screen background). There
are a bunch of other things that don't run anymore, eg the the system
load indicator, the
Public bug reported:
Whenever I reboot, if there are drivers mounted with corresponding
folders in /media (whether internal or external, btfrs, ntfs, or ext4),
after the reboot the original folder is still present and the drives re-
mount in a new folder. (Note that I mount drives in /media instea
Public bug reported:
This morning's updates broke both the screen lock (it never auto-locks
now) and dpms (if you manually lock the screen, it doesn't turn off any
more).
"xset dpms force off" still works to turn the screen off and "gnome-
screensaver-command -l" still locks the screen, so it pro
** Branch linked: lp:~ci-train-bot/syncevolution/syncevolution-ubuntu-
yakkety-landing-089
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613405
Title:
syncevolution FTBFS on yakkety: cannot convert
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579918
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559805
T
[Expired for indicator-applet (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: indicator-applet (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: unity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508529
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567781
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571786
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554077
T
[Expired for php-memcached (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: php-memcached (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1500183
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550304
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592585
T
tests ran: 20, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_02-40-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612305
Title:
lin
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593874
T
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577440
T
[Expired for linux (Ubuntu Xenial) because there has been no activity
for 60 days.]
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Importance: High => Critical
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubun
tests ran: 26, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-36.55/onza__4.4.0-36.55__2016-08-19_23-44-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612305
Title:
linu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615183
Title:
package snap (not installed) failed to install/upgrade:
'/usr/share/man/man1/snap.1.gz'의 덮어쓰기를 시도
** Changed in: partman-auto (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1418706
Title:
UEFI: blank drive incorrectly detected as existing BIOS-mode install
Public bug reported:
This is on an upgrade from 14.04.4LTS to 16.04.1LTS. I'm using the same
configuration file as before. Nothing was changed. When starting the
clamav-daemon by using sudo service clamav-daemon start or by sudo
/etc/init.d/clamav-daemon start the clamd.pid and clamd.socket files
*** This bug is a duplicate of bug 1593048 ***
https://bugs.launchpad.net/bugs/1593048
Thank you for taking the time to report this bug.
This is a duplicate of bug 1593048 and has been fixed in version
16.10.6.
https://launchpad.net/ubuntu/+source/ubuntu-mate-artwork/16.10.6
** This bug has
Public bug reported:
i don't know why snap package isn't installed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: snap (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
snap: Insta
May I piggy-back here to ask how I gain ownership of that file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583578
Title:
kimchi Installation freeze during configure on 16.04
To manage notificat
Public bug reported:
The most recent daily image for Ubuntu GNOME was built with livecd-
rootfs 2.428 but still doesn't have networking (I tested with yakkety's
VirtualBox which exposes a virtual ethernet connection).
https://launchpad.net/ubuntu/+source/livecd-rootfs/2.428
https://launchpad.net
Some hints for using Ubuntu 16.04 machines that can't be rebooted to
work around this bug:
1) You can keep your SSH logins a secret from systemd-logind by adding
`UsePAM no` to /etc/ssh/sshd_config; this will avoid the ~25 second
delay.
2) `UsePAM no` requires unlocked accounts (passwd -u) with a
slangasek gave the ok for this to be synced since it has to be reviwed
by ~ubuntu-archive before being accepted into Ubuntu anyway. So I synced
to Ubuntu's new queue.
** Changed in: cassbeam (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615176
Title:
package makehuman-data 1.0.0~alpha6-5ubuntu3 failed to
install/upgrade: trying to overwrite
'/u
Public bug reported:
Error happened while upgrading to 16.04
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: makehuman-data 1.0.0~alpha6-5ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39
Uname: Linux 3.13.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Archi
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
This bug was fixed in the package mir - 0.24.0+16.10.20160815.3-0ubuntu1
---
mir (0.24.0+16.10.20160815.3-0ubuntu1) yakkety; urgency=medium
* New upstream release 0.24.0 (https://launchpad.net/mir/+milestone/0.24.0)
- ABI summary:
. mirclient ABI unchanged at 9
. mir
Public bug reported:
Notification on restart after rhythmbox-plugins failed to install during
dist-upgrade.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: rhythmbox-plugins 3.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
ApportV
tests ran: 65, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-36.55~14.04.1/dwalin__4.4.0-36.55~14.04.1__2016-08-20_01-43-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612
** Branch linked: lp:~ci-train-bot/syncevolution/syncevolution-ubuntu-
yakkety-landing-098
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613405
Title:
syncevolution FTBFS on yakkety: cannot convert
tests ran: 20, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-20_00-36-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612305
Title:
lin
** Summary changed:
- cupds cause apparmor denials for /etc/ld.so.preload
+ cupsd cause apparmor denials for /etc/ld.so.preload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571531
Title:
cupsd ca
Ok, since you don't seem to believe this, here are 2 videos: the first
is using the Vivid xorg stack, YouTube fullscreen on Chromium. The
second video is the same, under the Xenial stack.
Vivid: https://youtu.be/Ykhp2L_pf7Y
Xenial: https://youtu.be/p7FvXTzlIa0
The regression is patent, and it was
1 - 100 of 700 matches
Mail list logo
