Sorry for the noise, just had a look at the .dec file and the
https://launchpad.net/ubuntu/trusty/amd64/update-manager/1:0.196.23
where it looks as I expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Im seeing some issues with the package:
https://launchpad.net/ubuntu/+source/update-manager/1:0.196.23
Netinstaller can't find it currently from an official mirror.
Looking at the 16.04 compared to the 14.04 package:
16.04: https://launchpad.net/ubuntu/+source/update-manager/1:16.04.6
14.04: ht
Indeed, thanks a lot for very quick action.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644428
Title:
Unable to log in with AD account after update
To manage notifications about this bug go to:
>From a machine running 4.3.11+dfsg-0ubuntu0.14.04.3, I just tested
smbclient towards DFS shares / windows 10 share, cifs mount of DFS
share, sharing a local folder with ACL set (net usershare) and then
connecting to if from another machine running 16.04 with samba4 2:4.3.11
+dfsg-0ubuntu0.16.04.1.
Impressively fast guys, hats off for that!
"Please could someone affected by the regression introduced by 2:4.3.11
+dfsg-0ubuntu0.14.04.2 confirm that 2:4.3.11+dfsg-0ubuntu0.14.04.3 from
proposed fixes the regression?"
Just tested the trusty-proposed version (ubuntu0.14.04.3) and I can not
see th
Can confirm this, attached a log snippet on how the auth.log looks after
upgrading to this version.
..
Nov 24 11:02:12 thismachine sudo: PAM unable to dlopen(pam_winbind.so):
/lib/security/pam_winbind.so: cannot open shared object file: No such file or
directory
Nov 24 11:02:12 thismachine sudo:
+1 on this and see the exact same. Also its still seen in the 16.04
openssh-client 1:7.2p2-4ubuntu2.1. Any valid workarounds on this?
It does not seem to honor "ReKeyLimit 0G 1H" in my case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
The solution presented here: http://askubuntu.com/questions/452750
/reboot-after-shutdown-ubuntu-14-04-also-12-04-dell-latitude-e7440 was
found by an observant colleague and did the trick for me. After
disabling wake-on-(Lan/USB) the error seems gone.
Tested on 3.16.0-50 Trusty on a HP EliteBook 8
I can confirm this too.
My private key starts like this:
-BEGIN RSA PRIVATE KEY-
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,509FB430BEB25072
And I can add my pass phrase to network manager and it will apply without
issues. However, if i restart my machine, it will during the lightdm l
Could not verify the issues noted in comment #6, but the original issue
with the pty hangup was tested and confirmed fixed on 14.04
3.13.0-64-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397976
Title:
tty hangup regression in 3.13 kernel (trusty LTS)
To
Also a confirmation here, tested with both HP Elitebook 840G1 and 850
(both Intel i7 with integrated graphics). Both behaving the same,
rebooting instead of shutting down. Same results on both 3.13 and 3.16
kernels. Same results regardless of shutdown method.
--
You received this bug notification
** Changed in: linux-lts-trusty (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397976
Title:
tty hangup regression in 3.13 kernel (trusty LTS)
To manage no
** Description changed:
From https://lkml.org/lkml/2014/10/10/345
-
#
Commit f95499c3030f ("n_tty: Don't wait for buffer work in read() loop")
- introduces a race window where a pty master can be signalled that the
ptyslave was closed before all the data that the slave wrote is
del
Public bug reported:
>From https://lkml.org/lkml/2014/10/10/345
#
Commit f95499c3030f ("n_tty: Don't wait for buffer work in read() loop")
introduces a race window where a pty master can be signalled that the ptyslave
was closed before all the data that the slave wrote is delivered.Commit
Hi Joseph,
Unfortunately it does not seem to be fixed upstream:
$dpkg -l linux
ii linux-image-3.8.0-030800-generic 3.8.0-030800.201302181935
Linux kernel image for version 3.8.0 on 64 bit x86 SMP
ii linux-image-extra-3.8.0-030800-generic 3.8.0-030800.201302181935
apport-collect actuall dumps out:
xrealloc: realloc(-2147483648) failedCannot allocate memory
xrealloc: realloc(-2147483648) failedCannot allocate memory
(I would like to see the apport-collect before sending it, I don’t know
exactly what it sends)
Please get back to me if any more info is needed
Public bug reported:
On ubuntu 12.04.1 client with authorized Windows AD account (through
samba/winbind 3.6.3), there seems to be a bug when kernel 3.2.0-38 is
applied. ps or pgrep is causing a "cannot allocate memory" error and the
cpu is temporarily maxed out more or less.
An strace from ps run
18 matches
Mail list logo
