Hello Timo, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Timo, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Lawrence, or anyone else affected,
Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for dnsmasq has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
The current installed version is: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1732172
Title:
[CVE] Security Vulnerabilities in
The machine I was using has been redeployed without LVM. If I get a
chance to redeploy I'll grab the requested logs. It's fairly trivial to
trigger if you have a machine available to deploy with lvm boot as
described above.
--
You received this bug notification because you are a member of Ubuntu
Long and boring root-cause and psuedo-fix on
https://github.com/MirServer/mir/pull/18
--
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/1728574
Title:
Xwayland fails to
** Package changed: maas (Ubuntu) => maas
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1573982
Title:
LVM boot problem - volumes not activated after upgrade to Xenial
This is a deliberate change in binutils-2.29, which changes how the ADR
instruction works with Thumb function symbols:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commit;h=52a86f843b6dee1de9977293da9786649b146b05
There are some changes in openssl which work around this:
I've run across this today and it affects MAAS.
MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)
Configuring an LVM based drive with a raid on top of it for the root
partition will trigger this. Deploying the default kernel / OS will fail
due to inactive volume groups.
The fix as expected:
status wontfix
I think we've decided that the Wayland support is where we'll direct
new development, so I don't expect more feature development on
libmirclient.
** Changed in: mir
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
I also verified that with this workaround for the first instruction, the
non-NEON path passes the test, by removing this block from
sha256-armv4.S:
#if __ARM_MAX_ARCH__>=7 && !defined(__KERNEL__)
ldr r12,.LOPENSSL_armcap
ldr r12,[r3,r12]@ OPENSSL_armcap_P
I stepped through 2 builds side-by-side in gdb - one good build built
with gcc 7.1, and one bad build, built with gcc 7.2. I managed to narrow
it down to a bug in sha256_block_data_order.
One of the first differences I spotted was that the good build branches
almost immediately to a NEON code
Continuing debugging the broken build, if we look at the first few
instructions of sha256_block_data_order:
0x004160c0 <+0>: subwr3, pc, #3
0x004160c4 <+4>: ldr.w r12, [pc, #-36] ; 0x4160a4
0x004160c8 <+8>: ldr.w r12, [r3, r12]
This looks similar to before - the
The incorrect instruction at the start of sha256_block_data_order comes
from the ADR pseudo-instruction in sha256-armv4.S:
.global sha256_block_data_order
.type sha256_block_data_order,%function
sha256_block_data_order:
#if __ARM_ARCH__<7
sub r3,pc,#8@
On the broken build, the first thing to notice is that when entering
sha256_block_data_order, we are running in Thumb mode, as bit 5 of the
status register is set:
(gdb) info registers
r0 0x4b7558 4945240
r1 0x4b7580
Changing the start of sha256_block_data_order in sha256-armv4.S to avoid
the use of the ADR pseudo-instruction like this:
global sha256_block_data_order
.type sha256_block_data_order,%function
sha256_block_data_order:
#ifdef __thumb2__
sub r3,pc,#4@
Hello Pieter, or anyone else affected,
Accepted iproute2 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/3.12.0-2ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Pieter, or anyone else affected,
Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Also affects: resolvconf (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Know problem with Kernel 4.13.
4.13.8 works for me.
** Description changed:
Ubuntu 17.10
wpasupplicant 2.4-0ubuntu10
System shutdown hangs because wpa_supplicant is not stopping itself.
Test with:
$ sudo systemctl stop wpa_supplicant
Journal shows:
11:37:32
Public bug reported:
Ubuntu 17.10
wpasupplicant 2.4-0ubuntu10
System shutdown hangs because wpa_supplicant is not stopping itself.
Test with:
$ sudo systemctl stop wpa_supplicant
Journal shows:
11:37:32 systemd[1]: Stopping WPA supplicant...
11:37:32 wpa_supplicant[941]: nl80211: deinit
vious that unlocking doesn't actually
require a password (i.e. removing the password box from the lock
screen when auto-login is enabled).
Thanks,
Chris
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1706770/+subscriptions
--
Mailing list: https://
. It seems like either unlocking should always require a
password (otherwise what's the point of locking in the first place) or
it should be made totally obvious that unlocking doesn't actually
require a password (i.e. removing the password box from the lock
screen when auto-login is enabled).
This problem seems to be the same as in the following two Ubuntu
stackexchange posts:
https://askubuntu.com/questions/768463/laptop-headphone-jack-produces-no-sound
https://askubuntu.com/questions/219342/no-sound-output-from-headphone-jack-ubuntu12-04/859931
A temporary solution mentioned in
I am also having this problem on a Dell Precision 5520 (which is similar
hardware to both the Dell XPS 15 and Dell XPS 13).
Headphone output worked initially since install and then stopped working
mid-session after unplugging and re-plugging the headphones. I was
adjusting the "Alert volume"
ad.net/bugs/1722300
>
> Title:
> Boot times since artful upgrade have increased 4 fold
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/
> 1722300/+subscriptions
>
--
Chris Gregan
Quality Assurance Manager
Field
690ms snapd.service
567ms dev-mapper-ubuntu\x2d\x2dvg\x2droot.device
374ms dev-loop8.device
353ms dev-loop9.device
340ms dev-loop10.device
312ms dev-loop4.device
Syslog shows:
chris@Thermia:~$ cat /var/log/syslog | grep
systemd
374ms dev-loop8.device
353ms dev-loop9.device
340ms dev-loop10.device
312ms dev-loop4.device
Syslog shows:
chris@Thermia:~$ cat /var/log/syslog | grep systemd-networkd-wait-online.service
Oct 6 13:56:57 Thermia systemd[1]: systemd-networkd-wait-online.service: Main
Please add SRU information to the bug:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
--
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/1713747
Title:
Hello Mathieu, or anyone else affected,
Accepted isc-dhcp into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.5-3ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Robin, or anyone else affected,
Accepted dkms into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu1.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robin, or anyone else affected,
Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chris 1657 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Mon Oct 2 12:37:39 2017
My system was doing the same thing. It went from working properly one
minute then broken for no reason. Very high CPU usage for pulseaudio,
polkitd, dbus-daemon. PulseAudio sound was stuttering. Trying to edit
the sound settings in the volume control was impossible because it kept
losing the
** Bug watch added: github.com/systemd/systemd/issues #6908
https://github.com/systemd/systemd/issues/6908
** Also affects: systemd via
https://github.com/systemd/systemd/issues/6908
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
The nvidia binary kernel driver now creates /dev/dri/card? nodes.
When switching between the nvidia and intel drivers on a hybrid system,
all holders of the DRI node need to relinquished so that the nvidia
driver can be unloaded so that bbswitch can turn the card off.
In
I should note that the above is while using the regular packaged
versions of idevicepair / ifuse.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libimobiledevice in
Ubuntu.
https://bugs.launchpad.net/bugs/1623666
Title:
For whatever reason while trying to backup an iPhone 6s+ 10.3.3 before
upgrading to 11.0 I can't see the photo mount in mate fuse at all but if
I use idevicepair and ifuse from the command line it lets me copy the
files. I'm not sure if this is related to the issue others have reported
above.
--
** Description changed:
This happens in Ubuntu 17.04 booted directly from the distribution live-
CD.
When the scaling factor (Display > Scale for menus and titlebars) is set
to a value other than 1.0, then the monitor turns off due to timeout
(Brightness & Lock > Turn screen off when
Public bug reported:
This happens in Ubuntu 17.04 booted directly from the distribution live-
CD.
When the scaling factor (Display > Scale for menus and titlebars) is set
to a value other than 1.0, then the monitor turns off due to timeout
(Brightness & Lock > Turn screen off when inactive for),
I have "reopened" this bug as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718897 , as it
still fails for me (a month later).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
Hello Jarno, or anyone else affected,
Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.90ubuntu0.8 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
The verification of the Stable Release Update for ntp has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I see the same in my Ubuntu 16.04.3
(gnome-shell:3000): GLib-CRITICAL **: Source ID 3572546 was not found
when attempting to remove it
Kernel 4.10.0-33-generic
apt-cache policy gnome-shell
gnome-shell:
Installed: 3.18.5-0ubuntu0.3
Candidate: 3.18.5-0ubuntu0.3
--
You received this bug
The verification of the Stable Release Update for apparmor has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
An upload of python3.5 to xenial-proposed has been rejected from the
upload queue for the following reason: "Bug# 1682934 is missing SRU
testcase/impact/regresison potential; all bugs are missing a Zesty
upload which is requried before we could release the Xenial update.".
--
You received this
An upload of python3.5 to xenial-proposed has been rejected from the
upload queue for the following reason: "Bug# 1682934 is missing SRU
testcase/impact/regresison potential; all bugs are missing a Zesty
upload which is requried before we could release the Xenial update.".
--
You received this
Public bug reported:
Not a lot,really - a massive number of packages upgraded in Artful,
rebooted with systemctl,then this happened after logging in and before
firing anything else up.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libglib2.0-0 2.53.6-1ubuntu1
ProcVersionSignature:
Hello Diana, or anyone else affected,
Accepted binutils into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.5 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Is there a fix required for zesty as well?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1539209
Title:
pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
Hello MrRomanze, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello TBS, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello bikram, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello errors.ubuntu.com, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 in a
few hours, and then in the -proposed repository.
Please help us by testing this new
Hello dominix, or anyone else affected,
Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mark, or anyone else affected,
Accepted cups into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.1.3-4ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
An upload of cups to xenial-proposed has been rejected from the upload
queue for the following reason: "Please re-upload including the
changelog from the not-released-from-proposed 2.1.3-4ubuntu0.2 in the
_changes file. This is needed for SRU tracking.".
--
You received this bug notification
Already have done: https://github.com/karelzak/util-linux/pull/492 ☺
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1708635
Title:
Valgrind reports " Uninitialised
** Changed in: util-linux (Ubuntu)
Assignee: (unassigned) => Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1708635
Title:
Valgr
My workaround above (calling "goa-daemon --replace" on login) isnt
working all the time, sadly. On occasion, I am ending up with 3 or 4
instances of goa-daemon per user (I guess --replace isnt able to kill
the previous instance?). Multiple instances results in high CPU usage.
I have also seen
Public bug reported:
The attached apport file was created from a segfault/core-dump observed
while using wget to try to audit a large number of websites to determine
which ones were online, which were redirects and where they redirected
to, etc.
The exact command-line attempts a considerable
-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: chris 7755 F pulseaudio
/dev/snd/controlC1: chris
It may not be flatpak on its own, but the machine I installed (and later
removed and purged) flatkpak on this problem exists. (So a correlation
does seem to exist) It might have something to do with other PPAs or how
packages you install from external PPAs affect the system. The only
major changes
I also have this problem running Ubuntu 17.04 with a TrendNet TEW-644UB
USB WiFi stick (ID 148f:2770 Ralink Technology, Corp. RT2770 Wireless
Adapter).
The symptoms are that it sees the networks but won't connect, even if
unencrypted.
The workaround in #1 also works for me.
Many thanks, Jesse.
The verification of the Stable Release Update for util-linux has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Hello Fabien, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Dustin, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mary, or anyone else affected,
Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've accepted this SRU to xenial-proposed.
Can I confirm that this bug is already fixed in yakkety and zesty? If
not, could you please upload fixes for those releases, too. We need to
ensure that upgrades don't regress.
--
You received this bug notification because you are a member of Ubuntu
Hello Timo, or anyone else affected,
Accepted mesa into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.0.7-0ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Ike, or anyone else affected,
Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Ike, or anyone else affected,
Accepted util-linux into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.29-1ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
Hello Ike, or anyone else affected,
Accepted util-linux into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/util-
linux/2.28.2-1ubuntu1.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for logrotate has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Also validated on Yakkety.
** Tags added: verification-done-yakkety
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
I have validated the trusty version works as expected! Thanks
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
Public bug reported:
does not update
Shows Error: BrokenCount >0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
So, the problem here is going to be the EGL platform detection - it's
failing to detect Mir, and is instead trying (and failing) to connect to
an X server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
share/bleachbit/bleachbit/Command.py", line 131, in execute
func_ret = self.func()
File "/usr/share/bleachbit/bleachbit/Unix.py", line 383, in apt_autoremove
raise RuntimeError(line)
RuntimeError: E: Sub-process /usr/bin/dpkg returned an error code (1)
Delete 1.1MB
** Tags added: sts
--
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/1627950
Title:
Stopped (with error) ... messages on encrypted LVM shutdown
Status in systemd:
Unknown
** Also affects: systemd via
https://github.com/systemd/systemd/issues/1620
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The verification of the Stable Release Update for openssl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Hello errors.ubuntu.com, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Michał, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Balint, or anyone else affected,
Accepted mir into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+17.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Balint, or anyone else affected,
Accepted mir into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Michał, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Michał, or anyone else affected,
Accepted mir into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Alan, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Balint, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello errors.ubuntu.com, or anyone else affected,
Accepted mir into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.04.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello errors.ubuntu.com, or anyone else affected,
Accepted mir into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mir/0.26.3+16.10.20170605-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
I found the bug described and confirmed on redhat, where I also found the
solution. (although they have the goa-demon in the /usr/libexec/ folder)
https://bugzilla.redhat.com/show_bug.cgi?id=1340203
As a work-around, for each user account I created a new file in
~/.config/autostart/ called
Public bug reported:
Bug seen in Evolution - fails to connect to my google accounts on second
log-in. Accounts are set up fine, but after a log out then log back in,
they fail.
Error reported in Evolution is:
"Failed to authenticate: Failed to obtain an access token for
901 - 1000 of 2665 matches
Mail list logo
