Just uploaded a new revision for SRU to trusty with the backported fixes
up to 3.19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469054
Title:
Unsupported kernel warning while running makedumpfile
** Description changed:
+ [SRU justification]
+ Newer trusty kernels trigger a supportability message from makedumpfile. The
upstream version used on the release do not support those kernels.
+
+ [Impact]
+ Warning message when running makedumpfile on kernels higher than 3.11
+
+ [Fix]
+ Cherr
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1469054
Title:
Unsupported kernel warning while running makedumpfile
To manage notifications about this bug go to:
https://bugs.laun
Second proposition of fix which exclude execution of the fix if grub-
pc/install_devices already holds a value
** Patch removed: "lp1491894_fix_lucid_debconf_empty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1491894/+attachment/4461329/+files/lp1491894_fix_lucid_debconf_empty
** Also affects: simplestreams (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: simplestreams (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
First proposition of fix for discussion
** Patch added: "lp1491894_fix_lucid_debconf_empty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1491894/+attachment/4461329/+files/lp1491894_fix_lucid_debconf_empty.debdiff
--
You received this bug notification because you are a member
** Also affects: autofs (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386869
Title:
-host in auto.master not mounting nfs exports
To man
Ok, just trying to be a bit clearer for my own good :
A system upgraded from Lucid to Precise will have the following debconf
setup :
* grub-pc/install_devices:
grub-pc/install_devices_failed_upgrade: true
* grub-pc/install_devices_empty: true
grub-pc/install_devices_failed: false
grub-pc/i
> High
** Changed in: grub2 (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491894
Title:
luci
** Changed in: network-manager-strongswan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1487183
Title:
Upgrade nm-strongswan to latest 1.3.1 with psk support
** Changed in: calibre (Ubuntu Trusty)
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282898
Title:
Broken Edit Metadata in B
I created a debdiff for the newest version.
It would be cool if it could still be included in wily.
** Patch added: "network-manager-strongswan_1.3.1-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/network-manager-strongswan/+bug/1487183/+attachment/4459363/+files/network-manager-s
I have the feeling that this portion of the grub-pc.postinst script is
causing the issue :
db_get grub-pc/install_devices
if [ -z "$RET" ]; then
# Reset the seen flag if the current answer is false, since
# otherwise we'll loop with no indication
** Description changed:
A system, initially installed on 10.04 Lucid then upgraded to 12.04
- precise, when upgraded to Trusty be not reboot following the end of the
+ precise, when upgraded to Trusty may not reboot following the end of the
do-release-upgrade command.
Reproduction steps
Well, it looks like the culprit could pretty well be a wrong setting of
the grub-pc/install_devices_empty variable.
Checking each context I find :
Lucid (initial) : grub-pc/install_devices_empty: true
Lucid (post reconf) : grub-pc/install_devices_empty: true
Whereas on a frech Preci
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491894
Title:
lucid to precise to trusty upgrade
** Changed in: grub2 (Ubuntu)
Status: New => Confirmed
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
** Description changed:
A system, initially installed on 10.04 Lucid then upgraded to 12.04
precise, when upgraded to Trusty be not reboot following the end of the
d
Public bug reported:
A system, initially installed on 10.04 Lucid then upgraded to 12.04
precise, when upgraded to Trusty be not reboot following the end of the
do-release-upgrade command.
Reproduction steps
Install a VM with 10.04.4-server ISO. When booted in 10.04, issue :
$
The upload triggered FTBS on i386 and powerpc. This is caused by
failure of test while running rsyslog testbench. The fix has been
forwarded upstream and added here to fix the FTBS.
** Patch added: "fix_i386_and_ppc_ftbs.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464201/
Hello pitti,
Following your advice, I did a new merge of 8.12 from debian. As it
turns out, it was beneficial in the sense that this very new 8.12 has
modification that I had sent upstream which required a specific patch.
I disabled the build of the kafka & mongo db packages in debian/rules as
su
** Also affects: e2fsprogs (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Precise)
Importance: Undecided
Status: New
** No longer affects: e2fsprogs (Ub
New debdiff for the merge with pitti's requests implemented.
** Patch added: "rsyslog_debian_to_ubuntu_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464201/+attachment/4453387/+files/rsyslog_debian_to_ubuntu_v2.debdiff
** Changed in: rsyslog (Ubuntu)
Status: Incom
Sorry for the noise, wrong bug :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1488830
Title:
FFE: merge rsyslog 8.9.0-3 from debian
To manage notifications about this bug go to:
https://bugs.lau
New debdiff for the merge with pitti's requests implemented.
** Patch added: "rsyslog_debian_to_ubuntu_v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1488830/+attachment/4453386/+files/rsyslog_debian_to_ubuntu_v2.debdiff
** Attachment removed: "rsyslog_8.9.0-3ubuntu1_amd64
** Patch removed: "rsyslog_debian_to_ubuntu.debdiff"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1464201/+attachment/4432446/+files/rsyslog_debian_to_ubuntu.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Hi pitti,
The binary packages were built from the debdiff produced using sbuild.
A VM with the latest Wily bits (as of 27/08) was used. The list of
files touched by the rsyslog package prior to upgrade was gathered with
:
root@WilyS-rsyslogmerge:~# ls -l $(dpkg -L rsyslog ) | awk '{print
$1"\t"
Works for me on Trusty
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282898
Title:
Broken Edit Metadata in Bulk commits 1.25.0
Wily's build log
** Attachment added: "rsyslog_8.9.0-3ubuntu1_amd64.build"
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1488830/+attachment/4452612/+files/rsyslog_8.9.0-3ubuntu1_amd64.build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Dear Release Team,
The request for a sponsor for the merge of rsyslog (LP: #1464201) has
not received attention prior to feature freeze. Given the fact that Wily
is the last release before LTS, it would be appropriate to have at least
one release with rsyslog 8.9.0-3 before t
debdiff of the fix
** Patch added: "lp1282898_fix_broken_edit_metadata.debdiff"
https://bugs.launchpad.net/calibre/+bug/1282898/+attachment/4451995/+files/lp1282898_fix_broken_edit_metadata.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Description changed:
- After editing fields in Edit Metadata in Bulk dialog, cannot commit the
- changes, with 1.25 binary on OS X 10.9.1. Got same error with various
- fields on Basic tab and Custom tab. Error message:
+ [SRU justification]
+ This patch is required in order to regain normal be
** Changed in: calibre (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282898
Title:
Broken Edit Metadata in Bulk commits 1.25.0
To manage not
Here is the upstream commit that fixes the issue :
https://github.com/kovidgoyal/calibre/commit/70d96e7a07cd8ee57603fae136c811f4642d6f0d
I will work on the SRU for Trusty hopefully soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
signed) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282898
Title:
Broken Edit Metadata in Bulk commits 1.25.0
To manage notifications about this bug go
Please view the document I uploaded for you using Google docs.
View Doc. just sign in with your email to view the document its very important.
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
A solution to this has been found thanks to https://support.mozilla.org
/en-US/questions/1077299. If the
.mozilla/firefox/**.default/prefs.js entry for gfx.xrender.enabled
is manually changed from false to true the window displays with content
and menus. Hopefully this will be useful to others
I have attached a copy of the /home/this-
user/.mozilla/firefox/console.log which may help the relevant developers
identify why the console is inoperative. It contains details of console
error conditions which seem to have only commenced after the update to
40.
** Attachment added: "Firefox conso
Using sysinfo I can see the computer this is occurring is also a 32 bit Intel
Pentium 4 CPU machine (family 15 model 2 stepping 9). It may be old but using
Xubuntu means it can do everything necessary (and more) that a modern Windows
machine does as fast, other than booting. Here is some additi
** Description changed:
Please do not ignore this bug report because it has not been submitted via
Apport. Due to the severe issue with Firefox 40 I cannot currently complete the
Apport submission process so am having to report this manually.
Firefox was upgraded from 39.0.3+build2-0ubuntu0.
** Description changed:
- Please do not ignore this bug report because it has not been submitted via
Apport. Due to the severe issue with Firefox 40 I cannot currently complete the
Apport submission process so am having to report this manually.
- Firefox was upgraded from 39.0.3+build2-0ubuntu0
Public bug reported:
Please do not ignore this bug report because it has not been submitted via
Apport. Due to the severe issue with Firefox 40 I cannot currently complete the
Apport submission process so am having to report this manually.
Firefox was upgraded from 39.0.3+build2-0ubuntu0.12.04.
Hey guys,
Is there someone from Muon or Ubuntu to solve this ?
This is quite long now since 2015-05-27.
It still happens today with Muon (discover and updater) versions 5.2.2 and
5.3.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fixed ifenslave-2.7 is now in Wily. Marking it fixed released. Next
step is to SRU to Trusty
** Changed in: ifenslave-2.6 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ifenslave-2.6 (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You re
Hello,
The Debian bug has been closed with 1:1.5.8-4, which has been
synchronized with Ubuntu Wily. Can you please test that the latest
version do fix this issue ?
I will add the well known 'verification-needed' tag to the bug that you
can change once verified.
** Tags added: sts verification-d
** Also affects: ifenslave-2.6 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ifenslave-2.6 (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: ifenslave-2.6 (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because y
** Changed in: python-glanceclient
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447193
Title:
Glance client fails with v2 API / Failed validating 'Type' in
schem
** Changed in: glance
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447215
Title:
Schema Missing kernel_id, ramdisk_id causes #1447193
To manage notifications abou
The bug is caused by a regression between 1.5.7-5 and 1.5.8-1 some
commits got dropped.
The debian bug for that issue is https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=793485.
I will get this uploaded at the beginning of next week in Debian so it
get synchronized to Wily automatically.
** B
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1475497
Title:
Unable to configure Firmware Assisted dump
To manage notifications about
Public bug reported:
Please merge ifenslave-2.7 (main) from debian unstable (main)
** Affects: ifenslave (Ubuntu)
Importance: Wishlist
Assignee: Louis Bouchard (louis-bouchard)
Status: In Progress
** Changed in: ifenslave (Ubuntu)
Status: New => In Progress
** Chan
Public bug reported:
Please merge ifenslave-2.7 (main) from debian unstable (main)
** Affects: ifenslave (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hello,
You are correct, the networked kernel dumping mechanism was introduced
in Utopic Unicorn (14.10). Being a major functionality upgrade, it
cannot be backported to the stable release as it would go against SRU
rules.
What I can offer is to request for a backport of the version in Vivid
into
** Changed in: makedumpfile (Ubuntu)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu)
Importance: Undecided => Low
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because
446/+files/rsyslog_debian_to_ubuntu.debdiff
** Changed in: rsyslog (Ubuntu)
Status: In Progress => Confirmed
** Changed in: rsyslog (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
rtance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: makedumpfile (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
** Also affects: pcre3 (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396768
Title:
pcre3 vulnerability CVE-2014, 2015
To manage notificat
** Also affects: nova (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Quick update : the fix is now in Debian ifenslave-2.7 . It needs to be
merged in Wily so we can backport the fix to trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326854
Title:
ambiguous err
** Also affects: ceilometer (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: ceilometer (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: ceilometer (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: ceilometer (Ubun
** Also affects: nova (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1459046
Title:
[SRU] nova-* services do not start if rsyslog is not ye
ools (Ubuntu)
Importance: Undecided => High
** Changed in: kexec-tools (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: kexec-tools (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Patch added:
"kexec-tools-trusty-Use-slurp_file_len-t
** Summary changed:
- kdump service fails to start
+ kdump service fails to start on Power8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461078
Title:
kdump service fails to start on Power8
To m
not a kernel patch after all but a kexec-tools one
** Package changed: linux (Ubuntu) => kexec-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461078
Title:
kdump service fails to sta
The cited patch that fixes the issue is a kernel patch on kexec. This
does not apply to makedumpfile.
** Package changed: makedumpfile (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I have just opened a bug on the debian ifenslave package :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791906 with a proposed
patch that seems to fix the issue.
Will wait to see if the maintainer responds.
** Bug watch added: Debian Bug tracker #791906
http://bugs.debian.org/cgi-bin/bugre
For info, the ambiguous message only appears when using ifenslave on a
bond that is already configured :
# ifconfig eth1 up
# ifconfig eth2 up
# ifconfig bond0 up
# ifenslave bond0 eth1 eth2 No error on the first execution
# ifenslave bond0 eth1 eth2
sh: echo: I/O error
eth1: could not add
As it turns out, this highlights a bug in the ifenslave script.
Starting with kernel 3.13 (commit
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=5831d66e8097aedfa3bc35941cf265ada2352317),
/sys/class/net/{bond}/slave_{ifname} (notice the slave_) no longer
exist.
I
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1326854
Title:
ambiguous error message "sh: echo: I/O error"
To manage noti
** Changed in: ifenslave-2.6 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: ifenslave-2.6 (Ubuntu)
Importance: Undecided => Medium
** Changed in: ifenslave-2.6 (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Tags added: sts
--
You received
** Also affects: pcre3 (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: pcre3 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: pcre3 (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because
** Also affects: autofs (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: autofs (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: autofs (Ubuntu Utopic)
Importance: Undecided
Status: New
--
You received this bug notification becaus
** Also affects: neutron (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification bec
-proposed upload tested positively on Trusty
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466013
Title:
kdump-tools does not
Public bug reported:
it warned me that without grub installed Pinguy might not be able to load.
If that can help, i did not choose the option to crypt the hard drive or my
user file.
I did not install updates with installing it but i did choose the option LVM.
Besides that everything is just perf
** Description changed:
+ [SRU justification]
+ The upstart job avoids the sysVinit scripts to be run while kdump-tools is
doing the kernel crash dump capture
+
+ [Impact]
+ Potential impossibility to capture a kernel crash dump
+
+ [Fix]
+ Add kdump-tools.conf upstart job
+
+ [Test Case]
+ Wi
** Changed in: makedumpfile (Ubuntu Trusty)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466013
Title:
kdump-tools does not have an upstart job
To manage n
: Undecided
Status: Invalid
** Affects: makedumpfile (Ubuntu Trusty)
Importance: Medium
Assignee: Louis Bouchard (louis-bouchard)
Status: Confirmed
** Also affects: ceph (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: ceph (Ubuntu Trusty
The upstart job has been uploaded to Debian and made available in
1:1.5.8-2
This is the related bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=788313
1:1.5.8-2 is now in Wily so the upstart job needs to be SRUed to Trusty
--
You received this bug notification because you are a member
Marking dev release as invalid since it relies on systemd
** Changed in: makedumpfile (Ubuntu)
Status: New => Invalid
** Bug watch added: Debian Bug tracker #788313
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788313
--
You received this bug notification because you are a member o
Hi, I don't know if that can be of any help, but I enable trace in the
openal library on the ubuntu touch to see what is going on and here is
the output (attachment). It look like OpenAL IS using Pulse, but the
system audio control still does not work.
** Attachment added: "OpenAL log"
https:/
** Also affects: lightdm (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification bec
Public bug reported:
saving of the kernel log messages relies on an upstart job which is no
longer triggered since the move to systemd. It needs to be migrated to
systemd to avoid systemd regression
** Affects: rsyslog (Ubuntu)
Importance: High
Assignee: Louis Bouchard (louis-bouchard
Public bug reported:
debian unstable has rsyslog-8.9.0-3. Ubuntu available version is quite
behind
** Affects: rsyslog (Ubuntu)
Importance: Wishlist
Assignee: Louis Bouchard (louis-bouchard)
Status: In Progress
** Changed in: rsyslog (Ubuntu)
Status: New => In Progr
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: libvirt (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification bec
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1462356
Title:
broadband connection establishes then drop after a few seconds
To
Public bug reported:
When connecting a cell phone to share the cell network connection, the
link gets established then drops after a few seconds. Doing the same on
Trusty works correctly.
Here is the end of a successful connection on Trusty :
==
Jun 5 14:1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456662
Title:
squid-deb-proxy fails to resolve dns entry : needs to be restarted
This is caused by the fact that Ceph OSDs are started by the following
udev rule : /lib/udev/rules.d/95-ceph-osd.rules. This rules emits the
ceph-osd signal that triggers the job to start.
The problem is not with ceph but with how kdump-tools relies on sysVinit
script ordering to run early.
--
Y
Marking the development release as Invalid since Wily uses systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461429
Title:
ceph-osd early start intefere with kdump-tools during kernel dump
To
ew
** Changed in: ceph (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: ceph (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: ceph (Ubuntu Trusty)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
** Changed in: ceph (Ubuntu)
Assignee: Louis Bou
** Changed in: ceph (Ubuntu)
Status: New => Confirmed
** Changed in: ceph (Ubuntu)
Importance: Undecided => Medium
** Changed in: ceph (Ubuntu)
Assignee: (unassigned) => Louis Bouchard (louis-bouchard)
--
You received this bug notification because you are a member of Ub
Public bug reported:
When a kernel crash dump occurs on a system with kdump-tools configured
and enabled, kexec triggers a reboot of the server which will start
kdump-tools to capture the kernel dump.
On systems running CEPH osd's, the configured osds will start even if
kdump-tools is setup to st
debdiff from the fix in Wily
** Patch added: "lp1456662_sru_upstart.debdiff"
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+attachment/4408486/+files/lp1456662_sru_upstart.debdiff
** Description changed:
+ [SRU justification]
+ In some race situation, squid-deb-proxy
As it turns out, mvo has just uploaded the fix along with some other bug
fix for this bug : http://bugs.debian.org/780083 to Debian this morning.
So I will pick up his changes from Wily and SRU it when it becomes
available
** Patch removed: "squid-deb-proxy-lp1456662_dns_race_fix.debdiff"
http
debdiff for the trusty fix
** Patch added: "squid-deb-proxy-lp1456662_dns_race_fix.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/squid-deb-proxy/+bug/1456662/+attachment/4405343/+files/squid-deb-proxy-lp1456662_dns_race_fix.debdiff
--
You received this bug notification because yo
debdiff for Trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456662
Title:
squid-deb-proxy fails to resolve dns entry : needs to be restarted
To manage notifications about this bug go to:
http
Using the same "start on " clause than for the squid3 job fixes the
problem (start on runlevel ...) :
# squid-deb-proxy - a proxy for deb packages
#
description "squid-deb-proxy"
start on runlevel [2345]
stop on runlevel [!2345]
I am going to prepare a debdiff with that modification
--
Public bug reported:
In some specific context that I currently cannot identify (i.e. happens
everytime on my server but never in VMs), after a reboot, squid-deb-
proxy fails to resolve DNS entries for URL that it needs to service. The
problem seems systematic on the hardware that I have.
Release
Still failed to install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268257
Title:
nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
failed to build, with only error: "objdump
901 - 1000 of 3841 matches
Mail list logo