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
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:
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
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.
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
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
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
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
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,
** 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
** 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
> 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
** 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
** 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
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
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.
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,
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
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
** 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
[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
[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
[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
[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
[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
[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
[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.
[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.
[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
[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
[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
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:
[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
[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
[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.
** 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 =>
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:
** 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
*** 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
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
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:
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
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
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
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
** 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
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
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
.
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
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.
** 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
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:
** 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
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
Override component to main
ubuntu-settings-components 0.8+16.10.20160809-0ubuntu1 in yakkety:
universe/misc -> main
qtdeclarative5-ubuntu-settings-components 0.8+16.10.20160809-0ubuntu1 in
yakkety amd64: universe/misc/optional/100% -> main
qtdeclarative5-ubuntu-settings-components
Override component to main
libqdjango-dev 0.6.2-2 in yakkety amd64: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety arm64: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in yakkety armhf: universe/libdevel/optional/100% -> main
libqdjango-dev 0.6.2-2 in
Public bug reported:
After coming out of suspend mode, network-manager starts having problems
with the wifi. the area wifi networks disappear after coming out of
suspend. Also after coming out of suspend 2 or 3 times the vpn
connections disappear and only return after a reboot.
ProblemType:
tests ran: 2, 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_00-31-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
It becomes quite common while first snapping an application to add
something like:
apps:
shell:
command: bash
parts:
bash:
plugin: dump
source: /bin/bash
[ this might not be exactly correct, just wanted to document the idea
before EOD ]
*** This bug is a duplicate of bug 1550950 ***
https://bugs.launchpad.net/bugs/1550950
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 1550950, so it is being marked as such. Please
tests ran: 10, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-36.55/onibi__4.4.0-36.55__2016-08-19_23-57-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:
Actually, my fault. Nobody reverted commit which broke it, but commit
which solved it back in 2012 is present in current ubuntu kernel. Hm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504909
1 - 100 of 726 matches
Mail list logo
