I can confirm there is a bug in 17.10. It's probably another bug but has
the same symptom: LUKS passphrase is prompted in qwerty and not with
user defined keymap.
This is a "new" bug in 17.10, it worked in previous release.
A workaround is to copy /etc/console-setup/cached_UTF-8_del.kmap.gz (or
s
If the verification apply also on 16.04, it does fix the issue.
We had a server that triggered the bug at least once a day (I suspect
unattended-upgrade run every morning to trigger it). Since the upgrade -
2 days and half ago - the server had no issue.
--
You received this bug notification beca
Public bug reported:
After a Systemd reload & any service restart, docker top no longer show process
of containers:
To reproduce this issue, do the following step:
# docker run -d --name test busybox sleep 1d
# docker top test
UID PID PPIDC
** Attachment added: "lspci + software version"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401636/+files/pierref-system-info.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "Kernel panic when suspending"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401634/+files/pierref-crash.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "Kernel panic when suspending"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880/+attachment/4401633/+files/pierref-crash.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I have null pointer exception on a XPS 13 (9343) which trigger a kernel
panic when I suspend the laptop. I can reproduce the issue nearly all
times (3 / 4 tries), for this I need to generate network traffic
(looking a video on Internet seem to be enough).
After applying the patch mentioned above,
I see that trusty has now a kernel with the fix included:
$ cat changelog.Debian
linux (3.13.0-21.43) trusty; urgency=low
[...]
[ Tetsuo Handa ]
* SAUCE: kthread: Do not leave kthread_create() immediately upon SIGKILL.
[...]
After a apt-get dist-upgrade to this kernel, I've successfully boot
I've tested this new kernel, it boot without issue on the server (as
usual, I booted three time the kernel to make it always works well).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Joseph,
kernel freeze is planed in 7 days, which will arrive very fast. Do you
think we could have a fix committed before this deadline ?
I still didn't tested the firmware upgrade. I didn't tested it to keep a
machine which exhibit the bug... upgrading firmware is okay with a local
machine, but
I've tested with kernel from comment #56.
The kernel generated too much logs for IPMI serial console (which
generated too much garbage), so I switched to a real serial console (and
at 115kbauds).
I've attached a archive with 3 runs (the last run it the most
interesting I think):
First run with s
Applied patch on tag v3.14-rc6 (fa389e2), run kernel 4 four times, all
worked.
We seen on output (full output attached):
[5.537193] mousedev: PS/2 mouse device common for all mice
[ [9.776032] floppy0: no floppy controllers found
[ 36.823538] Ignored SIGKILL by systemd-udevd
[ 38.3560
I've tested the final patch againt both 786235ee and tag v3.14-rc6
(fa389e22). It still works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E
Yes, it is working!
With this new patch applied (on 786235ee), server boot without any
issue.
I've attached the console ouput (which show no error).
As for other test, I've booter 5 times on this kernel to be sure it was
not by luck that it work.
Thanks for this fix.
** Attachment added: "Cons
** Attachment added: "Console output with kthread-defer-leaving patch applied
on 786235ee"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/4026609/+files/serial-ouput-patch-kthread-defer-leaving.txt
--
You received this bug notification because you are a member of Ub
I've tested the following:
* v3.14-rc6-trusty from comment #38 : still fail with same error.
* Kernel 786235eeba0e1e85e5cbbb9f97d1087ad03dfa21 with patch check-sigkill :
still got the fail to spawn thread. I will attach full output from serial
console.
* Kernel 786235eeba0e1e85e5cbbb9f97d1087ad0
With few hopes, I've tried the latest kernel from:
* trusty: linux 3.13.0-16.36 (linux-image-3.13.0-16-generic)
* trusty-proposed (downloaded from launchpad directly) : linux 3.13.0-17.37
Both still have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
If it help, I've done another change (against git hash 786235ee):
diff --git a/kernel/kthread.c b/kernel/kthread.c
index b5ae3ee..25a4780 100644
--- a/kernel/kthread.c
+++ b/kernel/kthread.c
@@ -298,7 +298,7 @@ struct task_struct *kthread_create_on_node(int
(*threadfn)(void *data),
I've done the following thing to be sure the patch fix the issue:
* backported trusty version (2.4.31-1+nmu2ubuntu5) on precise. Run this
version, problem still occur
* backported trusty + patch (e.g. the 2.4.31-1+nmu2ubuntu5 + the debdiff
attached) on precise: Run this version, slapd start suc
I've attached the debdiff patch for trusty.
I'm building a backport for precise to test if slapd can start with this
patch applied (the server on which the issue occure is running precise).
** Patch added: "lp1287730.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1287730/+at
I've attached the debdiff patch for trusty.
I'm building a backport for precise to test if slapd can start with this
patch applied (the server on which the issue occure is running precise).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
We have setup a LDAP master-master replication using delta-sync. On the
2-node cluster, one server fail to restart with a segfault immediately
after the startup.
Every time we restart the server, it fail with:
/# slapd -u openldap -g openldap -d stats -f /etc/ldap/slapd.conf
By more testing, you just mean reboot several time on this kernel to
check that the isssue do not appear sometime ?
During my bisect, I always booted 3 times on good kernel to make sure it
was not by "luck" that the kernel worked. I also booted three time the
kernel from comment #28.
To double ch
Any update ?
If i can help for something tell me, but I don't know kernel and can't do
debuging of it by myself.
I've tried to identify which ENOMEM cause the issue by added the printk
(one before the first ENOMEM, one before the second ENOMEM, one after
both ENOMEM)... but with just this change
Yes, this version is working:
Linux version 3.13.0-12-generic (root@gomeisa) (gcc version 4.8.2
(Ubuntu 4.8.2-15ubuntu3) ) #32 SMP Mon Feb 24 18:50:37 UTC 2014 (Ubuntu
3.13.0-12.32-generic 3.13.4)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Bisect finished. The first bad commit is
786235eeba0e1e85e5cbbb9f97d1087ad03dfa21. It seem more likely as this
commit concerne kthread (and the first error is "scsi4: error handler
thread failed to spawn, error = -12").
I also attach my bisect log if needed.
** Attachment added: "bisect.log"
Ok, I've restarted a bisect without limitation on driver/scsi (git
bisect start v3.13-rc1 v3.12).
Git tell me it's 13 steps, will took some time, but during middle of
next week we should have the bad commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can not test this kernel, it was only build for i386. The server is
installed with amd64 :(
Because of timezone difference we can only test one kernel per day, to speed up
the bisect, I've done one by myself, the result is the following:
$ git bisect log
# bad: [6ce4eac1f600b34f2f7f58f9cd8f0
This kernel version is also good:
Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131403 SMP Thu Feb 13
19:04:57 UTC 2014
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
This one is good, it is working:
[...]
Linux version 3.12.0-031200rc5-generic (jsalisbury@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402131150 SMP Thu Feb 13 16:54:49 UTC 2014
[...]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Tested this kernel. It is NOT working, it has the issue.
Extract of console log:
[...]
Linux version 3.12.0-031200-generic (jsalisbury@gomeisa) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201402101715 SMP Thu Feb 13 14:58:01 UTC 2014
[...]
[ 42.455969] scsi4: error handler thread fail
Yes, I confirm that 3.12-saucy works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
To manage notifications about this bug
None of them worked. All had the same issue.
Tested:
* v3.13-rc3
* v3.13-rc2
* v3.13-rc1 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc1-trusty/)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
It still occure with 3.14.0-031400rc1-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276705
Title:
Kernel 3.13 fail to boot with LSI SAS1068E (Dell SAS 6/iR)
To manage notifications about
I booted kernel with following common option : "ro console=tty0
console=ttyS1,57600".
When booted with rootdelay, it's "rootdelay=45".
The result are the following:
* 3.13.0-7-generic, rootdelay => error
* 3.13.0-7-generic, no rootdelay => Ok
* 3.6, rootdelay => Ok
* 3.12, rootdelay => Ok, t
** Attachment added: "dmesg from a running system (no rootdelay, press
control-d in initramfs)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970066/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
We have recently upgraded an Dell R300 server to Trusty (was running
fine in precise), and after upgrade it fail to boot.
It is an issue with the SAS controller during the initilisation. It fail
to detect the disk, we have the following error in console log:
[ 36.539955] s
** Attachment added: "lspci -vnn on the server"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705/+attachment/3970067/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12767
I tested on our server with a logrotate whose copytruncate is replaced
with nocreate. It work as expected: file is moved and not re-created,
thus carbon detect the logrotate and write to new log file (without a
bunch of NUL ascii character).
I attached the new debdiff with the nocreate option set.
Removing "copytruncate" wasn't enough ... missed that
/etc/logrotate.conf enable "create" by default. Also "sharedscripts"
imply "create"
Currently logfile are only moved and carbon continue to write in that
file (i.e. it write in query.log.1, console.log.1).
I'm trying with explicit "nocreate" a
Tested on Debian unstable and reported bug on Debian BTS : #733856.
** Bug watch added: Debian Bug tracker #733856
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733856
** Also affects: graphite-carbon (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733856
Importance: Unk
Debdiff for trusty
** Patch added: "lp1264971.debdiff"
https://bugs.launchpad.net/ubuntu/+source/graphite-carbon/+bug/1264971/+attachment/3937733/+files/lp1264971.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
Current logrotate script use "copytruncate" mode, but carbon-cache do
not behave well with such mode : after rotation logfile will start with
huge hole full of NULL character.
To reproduce, you can:
* install package (tested with 0.9.12-1 on Ubuntu "saucy" 13.10)
* Start gra
*** This bug is a duplicate of bug 1103260 ***
https://bugs.launchpad.net/bugs/1103260
Yes, the root cause is the same (nova-dhcpbridge init which sent already
expired lease). The fix proposed in bug #1103260 should fix this issue.
** This bug has been marked a duplicate of bug 1103260
fix
** Patch added: "add "updated" (models.FixedIp.updated_at) in data returned by
db.api.network_get_associated_fixed_ips, and use this time when generating the
leases."
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1104915/+attachment/3499727/+files/patch2.diff
--
You received this bug
I see two way for fixing the issue. The first one don't change the
db/api, but it's the a very nice fix. The second one seems to be the
correct way to fix this issue.
patch1.diff : always use time.time() + lease_time to set expiry in
nova/network/linux_net.py
patch2.diff : add "updated" (models.F
Public bug reported:
TL; DR;
nova-dhcpbridge init generated leases file with instance updated_at
instead of fixed_ips updated_at, causing every leases to be expired for
several month. So everytime dnsmasq is restarted will sent DHCPNAK the
first time a client ask for renew its lease.
Long versio
** Attachment added: "script used to show the problem on my workstation"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+attachment/3386619/+files/ntpd_loop.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Attachment added: "gdb "info stack" during deadlock (with packaged ntpd)"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1063806/+attachment/3386609/+files/gdb-stack.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
Software version:
* Description:Ubuntu 12.04.1 LTS
* arch : x86_64
* ntp 1:4.2.6.p3+dfsg-1ubuntu3.1
* libc6 2.15-0ubuntu10.2
We hit a strang behavious on some machine, where ntp refuse to quit if
stopped right after startup:
When running the following command: /etc/ini
I confirm the version in proposed fix the issue:
* before installing proposed version, on fully updated precises : I still
reproduce the bug
* after installing slapd from proposed : I can't reproduce the bug.
Also on this machine, LDAP is used for local authentication, which still
work after upd
Great. Thanks for your quick reactivity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023025
Title:
[SRU] search fail with get_ctrls : controls require LDAPv3
To manage notifications about this b
debdiff for quantal.
** Patch added: "lp-1023025-quantal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1023025/+attachment/3228408/+files/lp-1023025-quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
debdiff for precise sru.
** Patch added: "lp1023025.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1023025/+attachment/3228396/+files/lp1023025.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
nss_ldap, when running in a loop "id pierref", you
- may sometime have fewer group that you would normally have. And few
- seconds later, everything go back to normal.
+ * Any client connecting in LDAPv3 and using v3 specific feature may fail
+ * This include libnss-ldap (so id user may not re
I have found an upstream ticket which seems to be exactly our issue:
ITS#7107 [1].
It's fixed on upstream, but was fixed after the release of 2.4.28. It's
a one line fix, see git commit [2].
I don't have tested if it effectivelly fix our issue, but description
seem very close to our problem.
[1]
I can reproduce this issue with a simple ldapsearch:
ldapsearch -h ldap-1 -b ou=people,o=company -x
"(&(&(objectClass=posixAccount)(uid=*))(uid=pierref))" -M -v
Note: I think the exact query filter doesn't matter, only the -M switch
is important.
The result when it fa
** Attachment added: "Configuration of slapd on "slave""
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1023025/+attachment/3218626/+files/slapd-2.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "Configuration of slapd on "master""
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1023025/+attachment/3218625/+files/slapd-1.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Attachment added: "Log on one of slapd server when bug occure"
https://bugs.launchpad.net/bugs/1023025/+attachment/3218612/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023025
Tit
Public bug reported:
On precise, the slapd daemon return "error code 2 - controls require
LDAPv3" to client search. I don't see any reason why this would occure,
because if you run the same command few seconds later, it (may) work.
For example, using nss_ldap, when running in a l
Thanks for the patch, with this patch I can't reproduce the bug.
I toke the patch, applied it on fresh apt-get source. builded it with a
pbuilder, installed the result. With that I was unable to reproduce the problem.
Got back to karmic release of openssh and I can reproduce the bug.
So the patc
Forget to tell the version affected:
This was tester on jaunty (with the killall -s SIGHUP).
The server is on hardy.
So hardy and jaunty are affected.
--
sshd stop on two SIGHUP
https://bugs.launchpad.net/bugs/497781
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
When you send two SIGHUP to sshd (to reload it configuration), sshd
simply die.
How to reproduce:
1)start an sshd server
if you do killall -s SIGHUP sshd. The server restart successfully.
2) To kill sshd with SIGHUP, run "killall -s SIGHUP sshd & killall -s SIGHUP
sshd"
i
I had the same problem here:
host running on hardy, 64bits with kvm version 1:62+dfsg-0ubuntu8.2
kernel 2.6.24-24-server
Memory: 16 Gb
guest running on hardy, 32bits
kernel 2.6.24-24-virtual.
Memory: 3Gb
guest dmesg contains nothing special, host dmesg contains lots of :
[183668.247232] WARNING:
+1
Also work for me.
Thanks
--
[SRU] fail2ban fails to start after reboot
https://bugs.launchpad.net/bugs/222804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Public bug reported:
Binary package hint: ejabberd
I'm using dapper and I have installed ejabberd.
I see that ejabber store password in plaintext on this file :
/var/lib/ejabberd/passwd.DCD (this seems "normal" and it's not the subjet of
this bug report)
But the permision of this file and the
67 matches
Mail list logo
