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
** 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
Touch seeded packages, which is subscribed to evolution
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-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
Touch seeded pa
** 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
Touch seeded packages, which i
** 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
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
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
** Branch linked: lp:~ci-train-bot/syncevolution/syncevolution-ubuntu-
yakkety-landing-089
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syncevolution in Ubuntu.
https://bugs.launchpad.net/bugs/1613405
Title:
syncevolutio
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
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
** Branch linked: lp:~ci-train-bot/syncevolution/syncevolution-ubuntu-
yakkety-landing-098
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syncevolution in Ubuntu.
https://bugs.launchpad.net/bugs/1613405
Title:
syncevolutio
** 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
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1
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 yak
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 0.8+16.10.20160
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: Bug
Public bug reported:
lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
# apt-cache policy libgtk-3-dev
libgtk-3-dev:
Installed: 3.18.9-1ubuntu3.1
Candidate: 3.18.9-1ubuntu3.1
Version table:
*** 3.18.9-1ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports xe
A simple way to fix this would be to deploy a newer version of virtuoso-
nepomuk for Trusty (or for Xenial, depending on the order of upgrades),
with a fixed content in /etc/init.d/virtuoso-nepomuk (the only necessary
change is to add the "### END INIT INFO" line).
Another approach would be to be
Public bug reported:
Hi I am using the BQ M10 with OTA 12 update. When using the tablet via
wifi to an EE home 4G router, the M10 wifi drops out every so often,
even when my Meizu MX4 (with OTA 12) is still connected to the same
router. This is not a wifi range problem as it happens even when you
Thank you Konrad!
Eagerly waiting for OTA13.
--
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/1539158
Title:
Unable to pair with in-car hands-free system after OTA-9 update
S
Public bug reported:
The latest update from the Xenial InRelease repository makes the
following processes consume 100% CPU:
thermald(1.5-2ubuntu2)
imap(Dovecot 1:2.2.22-1ubuntu2)
imap-login (Dovecot 1:2.2.22-1ubuntu2)
and eventualy (after 1-2 minutes) render the system c
Hardware works fine under Windows 10.
Checked levels in alsa-mixer.
Problem was the same under 14.04 LTS.
Problem is the same when booting a 16.04 system from a live disk.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to als
Public bug reported:
every time you want to restart your computer crashes and forced touching
off and sometimes freezes while I'm switching between windows.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Li
Hi kiko,
It a fresh install of Lubuntu 16.04 xenial.
Linux vlubfs1 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu
Public bug reported:
No sound at all, neither in headphones nor in speakers.
Have tried without success:
jack-retask
latest alsa drivers with DKMS
various options set in /etc/modprobe.d/alsa-base.conf
Codec seems to be supported:
grep "Codec:" /proc/asound/card*/codec*
/proc/asound/card0/codec
** Summary changed:
- Samsung printer automatically diabled; cannot print
+ Samsung printer automatically disabled; cannot print
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/
Thanks, understood. Now is this is a fresh install or an upgrade,
eproust?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1186662
Title:
isc-dhcp-server fails to renew le
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1615126
Title:
package fontconfig-config 2.11.94-0ubuntu1 failed to install/upgrade
Public bug reported:
Unknown.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig-config 2.11.94-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia wl
ApportVersion: 2.20.1-0
- Can we get a team bug subscriber? Maybe unity-ui-team?
- No tests? :(
Seems fine otherwise.
** Changed in: qtubuntu (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in U
Public bug reported:
Error received when upgrading from 16.04 to 16.10
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
I'm game.
1. $ head -n 1 /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
2. In /usr/share/doc/keyboard-configuration/README.Debian, I see this:
"While it will be safe to edit directly the configuration files
(/etc/default/keyboard and /etc/default/console-se
Here it is, all I found.
OTA-12, STABLE, MEIZU-PD.EN
** Attachment added: "Meizu Pro5 Bluetooth logs,"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4724139/+files/Logs.zip
--
You received this bug notification because you are a member of Ubuntu
Touch see
This bug was fixed in the package ubuntu-touch-session -
0.108+16.10.20160817.1-0ubuntu1
---
ubuntu-touch-session (0.108+16.10.20160817.1-0ubuntu1) yakkety; urgency=medium
[ Łukasz 'sil2100' Zemczak ]
* Modify the add_custom_to_xdg_data.sh profile.d hook to not modify
the XDG_
Interesting that noone reacted on the bug.
I was able to circumenvent the problem with the proprietary nvidia
drivers. Actually I wanted to avoid this on a new installation, but I'm
unable to work if the system freezes randomly if I enter a webpage with
a video or launch a video podcast :-(
--
Y
OK approved, but for safety's sake: archive admins, can you please only
promote libqdjango-dev and libqdjango-db0? That's all we care about
right now.
** Changed in: qdjango (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubu
Questions:
- Tests aren't being run, do we know why?
- This is apparently abandoned upstream. And we don't share the package
with Debian. It doesn't seem to need much maintenance, but do we have
resources paying attention to this? There are no open bugs in LP, which
encourages but shocks me.
N
Confirmed this locally. strace shows:
socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 3
connect(3, {sa_family=AF_INET, sin_port=htons(514),
sin_addr=inet_addr("192.168.15.71")}, 16) = 0
[...]
socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 1
connect(1, {sa_family=AF_LOCAL, sun_path="/dev/log"}, 110) =
Public bug reported:
LXC upstream released LXC 2.0.4 as a bugfix release with following changelog:
- core: Add a prefix to the lxc.pc
- core: Add flag in mount_entry to skip NODEV in case of a
persistent dev entry
- core: Add missing cgroup namespace to ns_info struct
- core:
For those affected by this in xenial, I have created a PPA with fips
removed from the openssl binaries.
See it here.
https://launchpad.net/~chiluk/+archive/ubuntu/openssl+nofips
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
This bug was fixed in the package location-service -
3.0.0+16.10.20160811-0ubuntu1
---
location-service (3.0.0+16.10.20160811-0ubuntu1) yakkety; urgency=medium
[ Alberto Mardegan ]
* Don't sent last known position to new sessions (LP: #1604446)
[ Scott Sweeny ]
* Enable runni
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: messaging-app (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
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/bug
Public bug reported:
Using an internal 4k display. Upon resume from sleep or hibernate, the
back light does not turn back on.
I can enter terminal commands blind to reboot the machine or get other
confirmation that the system is on and working.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Packag
@Anupam: with OTA-12 you already have the fix for bug #1596329. The
other one will come with OTA-13. Until we know what the cause is though,
which many people have been trying to identify, it'll be very difficult
to make sure that it's fixed. I appreciate your patience as we try and
figure this out
There is a potential security issue here.
Whenever a legitimate program is seen asking for a password as the
result of an automatic operation people come to think of it as normal.
This undermines the suspicion that we would otherwise encourage in
people to help them avoid scams and malicious softw
*** This bug is a duplicate of bug 1301120 ***
https://bugs.launchpad.net/bugs/1301120
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1301120, so is being marked as such.
** Also affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1585278
Title:
Browser window does not f
** Changed in: syncevolution (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to syncevolution in Ubuntu.
https://bugs.launchpad.net/bugs/1613405
Title:
syncevolution FTBFS on yakkety:
I concur with @GTriderXC. Exactly the same behaviour! Many times I leave
my phone untouched except a few calls, Telegram messages, and casual
web-browsing sessions (can't avoid these, as I mentioned before this
phone is my daily driver), but then 1-2 days later again the same no-
SMS-sound-issue. I
Please provide any extra information you can to reproduce and debug this
issue. I can't reproduce it. If both IPv4 and IPv6 are set to not take
the default route, things are behaving correctly here; just like the DNS
settings are correctly configured when no split-tunnelling is in use at
all.
Also
not an xorg bug anyway if a bug at all
** Package changed: xorg (Ubuntu) => nautilus (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/1610059
Title:
no icons on deskt
the logs look perfectly fine so explain what's wrong?
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
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/1614726
Titl
Thank you for your report.
This looks like a local configuration problem, rather than a bug in
Ubuntu.
You can find pointers to get help for this sort of problem here:
http://www.ubuntu.com/support/community
Since we use this bug tracker to track bugs in Ubuntu, rather than
configuration problem
>From log:
/etc/ssh/sshd_config: line 89: Bad configuration option: AllowUser
Your sshd_config file has an invalid configuration option. It should be
"AllowUsers" (note the 's' at the end).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which i
** Changed in: six (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1613880
Title:
package python-six 1.10.0-3 failed to install/upgrad
Public bug reported:
This shows up when I open a terminal:
compaudit:148: unknown group
Don't know how to fix this.
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- This shows up when I open a terminal.
+ This shows up when I open a terminal:
** Branch linked: lp:~ubuntu-desktop/evolution/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1613291
Title:
Update evolution stack to 3.22
Status in
This bug was fixed in the package systemd - 231-4
---
systemd (231-4) unstable; urgency=medium
* Revert "pid1: reconnect to the console before being re-executed"
This unbreaks consoles after "daemon-reexec". (Closes: #834367)
-- Martin Pitt Thu, 18 Aug 2016 07:03:13 +0200
*
** Branch linked: lp:~ubuntu-desktop/evolution-data-server/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1613291
Title:
Update evolution stack to 3.2
** Branch linked: lp:~willcooke/ubuntu-themes/hidpiicons
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1549490
Title:
low resolution checkbox icons
Status in ubunt
This bug was fixed in the package unity8 -
8.14+16.10.20160811.1-0ubuntu1
---
unity8 (8.14+16.10.20160811.1-0ubuntu1) yakkety; urgency=medium
[ Albert Astals Cid ]
* Take into account carousel selectedItemScaleFactor when setting card
fixedArtShapeSize (LP: #1599238)
* Remov
This bug was fixed in the package unity8 -
8.14+16.10.20160811.1-0ubuntu1
---
unity8 (8.14+16.10.20160811.1-0ubuntu1) yakkety; urgency=medium
[ Albert Astals Cid ]
* Take into account carousel selectedItemScaleFactor when setting card
fixedArtShapeSize (LP: #1599238)
* Remov
This bug was fixed in the package unity8 -
8.14+16.10.20160811.1-0ubuntu1
---
unity8 (8.14+16.10.20160811.1-0ubuntu1) yakkety; urgency=medium
[ Albert Astals Cid ]
* Take into account carousel selectedItemScaleFactor when setting card
fixedArtShapeSize (LP: #1599238)
* Remov
This bug was fixed in the package unity8 -
8.14+16.10.20160811.1-0ubuntu1
---
unity8 (8.14+16.10.20160811.1-0ubuntu1) yakkety; urgency=medium
[ Albert Astals Cid ]
* Take into account carousel selectedItemScaleFactor when setting card
fixedArtShapeSize (LP: #1599238)
* Remov
This bug was fixed in the package unity8 -
8.14+16.10.20160811.1-0ubuntu1
---
unity8 (8.14+16.10.20160811.1-0ubuntu1) yakkety; urgency=medium
[ Albert Astals Cid ]
* Take into account carousel selectedItemScaleFactor when setting card
fixedArtShapeSize (LP: #1599238)
* Remov
1 - 100 of 258 matches
Mail list logo
