[Bug 1917409] Re: neutron-l3-agents won't become active
*** This bug is a duplicate of bug 1883089 *** https://bugs.launchpad.net/bugs/1883089 As the fix this was a duplicate of has been abandoned, can this still be addressed somehow? Is there anything I can do to move this forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917409 Title: neutron-l3-agents won't become active To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1917409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680286] [NEW] MAAS DNS doesn't handle non /24 subnets well
Public bug reported: We currently have a maas 1.9.5 setup on trusty that has 4 subnets defined in it under 10.x.0.0, one /24, 2 /23s and a /21. With the latest version of maas installed it appears that it is writing out two zones configs for x.10.in-addr.arpa in the named.conf.maas file, which is causing bind to error out. After a bit of debugging, I've confirmed that it is being passed one DNSForwardZoneConfig (for the maas zone) and 2 DNSReverseZoneConfigs (for the x.10.in-addr.arpa zones). Given the zones will overlap in the x.10.in-addr.arpa, it seems there needs to be a way to handle that in the code. Please let me know if you need any further information. Versions: $ dpkg-query -W maas maas1.9.5+bzr4599-0ubuntu1~14.04.1 $ lsb_release -dc Description:Ubuntu 14.04.5 LTS Codename: trusty ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680286 Title: MAAS DNS doesn't handle non /24 subnets well To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1680286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
I've had this occur on another system, and this time I could debug it a little more freely. This is an interesting output: # dpkg --purge --simulate systemd dpkg: dependency problems prevent removal of systemd: snapd depends on systemd (>= 204-5ubuntu20.20); however: Package systemd is to be removed. dpkg: error processing package systemd (--purge): dependency problems - not removing Errors were encountered while processing: systemd Now, why snapd was installed I'm not sure, but I guess that's what installed systemd, since the snapd package depends on systemd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
> Sidenote) the 18GB of /var/lib/juju/db (with backups, of backups, of backups) > was not helpful, I'll need to talk to sosreport people about that. This is > what made the report so huge. I did notice that, but I figured getting you all of the data was better than fiddling around trying to not include that part, and maybe missing bits. It'd be nice to have better control over it so we don't have to throw the juju state db around if we don't need to. > 1) It appears that deputy systemd was installed on the machine and > subsequently upgraded: > 2017-02-12 01:30:24 upgrade systemd:amd64 204-5ubuntu20.22 204-5ubuntu20.24 > However, there are no logs available as to what/who/why 20.22 deputy systemd > was installed. Interesting. I don't really know why it would have been installed. > 2) Have you tried to use snapd on trusty on that host? Has anything else > tried to do that? (e.g. juju manual provider or some such?!) No, I don't believe anyone has, I don't see any evidence of that. > 3) To recover the system, you should $ apt remove systemd; and reboot. > However that is the workaround Ok, I'll organise removing the package and rebooting it. > 4) Is this nested lxc? or errors inside the instances? > E.g. from logs I see failures to start lxc instances, but I don't see logs > for failing to start instances for some reason. This is LXCs on a KVM. The errors are in /var/log/lxc, its odd that the sosreport didn't include it. > 5) Why was lxc downgraded/upgraded/downgraded multiple times? We were trying to work out if LP#1656280 was related somehow, the errors were occuring before we did that. > 6) Are the error messages from this machine? Whilst I do see that systemd is > installed, and dsystemd cgroup is mounted, I am failing to find the logs for > any lxc failures related to starting them. The errors are in /var/log/lxc - see the next reply. > Is there /var/log/lxc or some such that you could share privately? for > some reason it was not part of the sosreport. I've uploaded it to https://private- fileshare.canonical.com/~bradm/lp1668123/lp1668123-var-log-lxc.tar.gz > cgmanager should not be interracting with dsystemd. > systemd should not be present on this system (as hwe kernel is not in use, > nor is snapd). > lxc should work irrespective of dsystemd. Its odd that stopping and starting cgmanager would let LXC work then. > I will setup trusty, with GA kernel, lxc1, deploy any charm (e.g. ubuntu), > and install deputy systemd to try to reproduce this test case. > I wonder if upstart systemd job should be neutered, unless snapd is present, > and we are booted with hwe kernel. It does sound like a good idea if we're going to have failures like what we saw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
It's uploading slowly to https://private- fileshare.canonical.com/~bradm/lp1668123/, once you see the .md5 file in place and the sosreport is 7.7G, it'll be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] Re: lxc fails to start with cgroup error
I've generated a sosreport, but its 7.7G. How would you like me to get this to you? The interesting part is that all this was deployed via juju, so I don't know how we got into this state. It also appears to be the only node in this state, so its a bit confusing as to how it got to be this way. Is there anything I can check configuration wise to see why its using deputy systemd? Its certainly not something we've explicitly picked as far as I know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668123] [NEW] lxc fails to start with cgroup error
Public bug reported: After rebooting a KVM instance hosting LXCs, we get the following error: $ sudo lxc-ls --fancy lxc: cgmanager.c: lxc_cgmanager_escape: 331 call to cgmanager_move_pid_abs_sync(name=dsystemd) failed: invalid request and the LXCs won't start up. In the error logs it showed: lxc-start 1487906073.534 ERRORlxc_cgfs - cgfs.c:lxc_cgroupfs_create:873 - Could not find writable mount point for cgroup hierarchy 11 while trying to create cgroup. The only way I could get the lxcs started was to stop and start cgmanager, just a simple restart wasn't sufficient. Please let me know if you need any further information. $ lsb_release -a Description:Ubuntu 14.04.5 LTS Release:14.04 $ dpkg-query -W systemd systemd 204-5ubuntu20.24 $ dpkg-query -W cgmanager cgmanager 0.24-0ubuntu7.5 $ dpkg-query -W lxc lxc 1.0.9-0ubuntu2 $ uname -a Linux infra 3.13.0-110-generic #157-Ubuntu SMP Mon Feb 20 11:54:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1668123 Title: lxc fails to start with cgroup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602090] [NEW] nova-compute process killed after libc-bin upgrade
Public bug reported: nova-compute process across 2 Openstack deployments died around the same time as the recent libc-bin upgrade: 2016-07-12 00:59:26 status half-configured libc-bin:amd64 2.19-0ubuntu6.9 2016-07-12 00:59:26 status installed libc-bin:amd64 2.19-0ubuntu6.9 Digging into the logs showed it was possibly related to ceph: common/ceph_crypto.cc: In function 'void ceph::crypto::init(CephContext*)' thread 7fbbdb76a740 time 2016-07-12 00:59:37.195100 common/ceph_crypto.cc: 73: FAILED assert(crypto_context != __null) ceph version 0.94.6 (e832001feaf8c176593e0325c8298e3f16dfb403) 1: (()+0x11d2ab) [0x7fbb693b92ab] 2: (()+0x16ad60) [0x7fbb69406d60] 3: (()+0x1372e9) [0x7fbb693d32e9] 4: (()+0x1347b0) [0x7fbb693d07b0] 5: (()+0x6704f) [0x7fbb6930304f] 6: (ffi_call_unix64()+0x4c) [0x7fbbd9447cce] 7: (ffi_call()+0x308) [0x7fbbd9447738] 8: (_ctypes_callproc()+0x48e) [0x7fbbd8e745fe] 9: (()+0x15f9e) [0x7fbbd8e75f9e] 10: (PyObject_Call()+0x36) [0x505f96] 11: (PyEval_EvalFrameEx()+0x1dfa) [0x49b07a] 12: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 13: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 14: /usr/bin/python() [0x4a1c9a] 15: (PyObject_Call()+0x36) [0x505f96] 16: (PyEval_EvalFrameEx()+0x1dfa) [0x49b07a] 17: /usr/bin/python() [0x4a1c9a] 18: (PyEval_CallObjectWithKeywords()+0xf6) [0x4dca56] 19: (()+0x392c) [0x7fbbda44b92c] 20: (()+0x3276) [0x7fbbda44b276] 21: (()+0x3dc6) [0x7fbbda44bdc6] 22: (PyEval_EvalFrameEx()+0x3259) [0x49c4d9] 23: /usr/bin/python() [0x4a1c9a] 24: /usr/bin/python() [0x4dfe94] 25: (PyObject_Call()+0x36) [0x505f96] 26: /usr/bin/python() [0x4dddad] 27: (PyEval_EvalFrameEx()+0x965) [0x499be5] 28: (PyEval_EvalFrameEx()+0xc72) [0x499ef2] 29: /usr/bin/python() [0x4a1c9a] 30: /usr/bin/python() [0x4dfe94] 31: (PyEval_CallObjectWithKeywords()+0x6b) [0x4dc9cb] 32: (()+0x392c) [0x7fbbda44b92c] 33: (()+0x3276) [0x7fbbda44b276] 34: /usr/bin/python() [0x5d9538] NOTE: a copy of the executable, or `objdump -rdS ` is needed to interpret this. terminate called after throwing an instance of 'ceph::FailedAssertion' $ dpkg-query -W nova-compute nova-compute2:12.0.3-0ubuntu1~cloud0 $ dpkg-query -W ceph ceph0.94.7-0ubuntu0.15.10.1~cloud0 $ dpkg-query -W libc-bin libc-bin2.19-0ubuntu6.9 Please let us know if you need any further information. ** Affects: nova-compute (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602090 Title: nova-compute process killed after libc-bin upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova-compute/+bug/1602090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599681] [NEW] ceph-osd process hung and blocked ps listings
Public bug reported: We ran into a situation over the past couple of days where we had 2 different ceph-osd nodes crash in such a way that they caused ps listing to hang when enumerating the process. Both had a call trace associated with them: Node 1: Jul 4 07:46:15 provider-cs-03 kernel: [4188396.493011] ceph-osdD 882029a67b90 0 5312 1 0x0004 Jul 4 07:46:15 provider-cs-03 kernel: [4188396.590564] 882029a67b90 881037cb8000 8820284f3700 882029a68000 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.688603] 88203296e5a8 88203296e5c0 0015 8820284f3700 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.789329] 882029a67ba8 817ec495 8820284f3700 882029a67bf8 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.891376] Call Trace: Jul 4 07:46:16 provider-cs-03 kernel: [4188396.939271] [] schedule+0x35/0x80 Jul 4 07:46:16 provider-cs-03 kernel: [4188396.989957] [] rwsem_down_read_failed+0xea/0x120 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.041502] [] call_rwsem_down_read_failed+0x14/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.092616] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.141510] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.189877] [] ? down_read+0x20/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.237513] [] __do_page_fault+0x398/0x430 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.285588] [] do_page_fault+0x22/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.332936] [] page_fault+0x28/0x30 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.379495] [] ? __clear_user+0x25/0x50 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.426400] [] copy_fpstate_to_sigframe+0x118/0x1d0 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.474904] [] get_sigframe.isra.7.constprop.9+0x12d/0x150 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.563204] [] do_signal+0x1e8/0x6d0 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.609783] [] ? __sys_sendmsg+0x42/0x80 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.656633] [] ? handle_mm_fault+0x250/0x540 Jul 4 07:46:16 provider-cs-03 kernel: [4188397.703785] [] exit_to_usermode_loop+0x59/0xa2 Jul 4 07:46:17 provider-cs-03 kernel: [4188397.751367] [] syscall_return_slowpath+0x4e/0x60 Jul 4 07:46:17 provider-cs-03 kernel: [4188397.799369] [] int_ret_from_sys_call+0x25/0x8f Node 2: [733869.727139] CPU: 17 PID: 1735127 Comm: ceph-osd Not tainted 4.4.0-15-generic #31-Ubuntu [733869.796954] Hardware name: Dell Inc. PowerEdge R730/0H21J3, BIOS 1.3.6 06/03/2015 [733869.927182] task: 881841dc6e00 ti: 8810cc0a task.ti: 8810cc0a [733870.059139] RIP: 0010:[] [] task_numa_find_cpu+0x2cd/0x710 [733870.192753] RSP: :8810cc0a3bd8 EFLAGS: 00010257 [733870.260298] RAX: RBX: 8810cc0a3c78 RCX: 0012 [733870.389322] RDX: RSI: RDI: 8810210a0e00 [733870.517883] RBP: 8810cc0a3c40 R08: 0006 R09: 013e [733870.646335] R10: 03b4 R11: 001f R12: 881018118000 [733870.774514] R13: 0006 R14: 8810210a0e00 R15: 0379 [733870.902262] FS: 7fdcfab03700() GS:88203e60() knlGS: [733871.031347] CS: 0010 DS: ES: CR0: 80050033 [733871.097820] CR2: 7fdcfab02c20 CR3: 001029204000 CR4: 001406e0 [733871.223381] Stack: [733871.282453] 8810cc0a3c40 811f04ce 88102f6e9680 0012 [733871.404947] 0077 008f 00016d40 0006 [733871.527250] 881841dc6e00 8810cc0a3c78 01ac 01b8 [733871.649648] Call Trace: [733871.707884] [] ? migrate_page_copy+0x21e/0x530 [733871.770946] [] task_numa_migrate+0x43e/0x9b0 [733871.832808] [] ? page_add_anon_rmap+0x10/0x20 [733871.893897] [] numa_migrate_preferred+0x79/0x80 [733871.954283] [] task_numa_fault+0x7f4/0xd40 [733872.013128] [] handle_mm_fault+0xbc0/0x1820 [733872.071309] [] ? do_futex+0x120/0x500 [733872.128149] [] ? __fget_light+0x25/0x60 [733872.184044] [] __do_page_fault+0x197/0x400 [733872.239300] [] do_page_fault+0x22/0x30 [733872.293001] [] page_fault+0x28/0x30 [733872.345187] Code: d0 4c 89 f7 e8 95 c7 ff ff 49 8b 84 24 d8 01 00 00 49 8b 76 78 31 d2 49 0f af 86 b0 00 00 00 4c 8b 45 d0 48 8b 4d b0 48 83 c6 01 <48> f7 f6 4c 89 c6 48 89 da 48 8d 3c 01 48 29 c6 e8 de c5 ff ff [733872.507088] RIP [] task_numa_find_cpu+0x2cd/0x710 [733872.559965] RSP [733872.673773] ---[ end trace aec37273a19e57dc ]--- In the ceph logs for node 1 there is: ./include/interval_set.h: 340: FAILED assert(0) ceph version 0.94.7 (d56bdf93ced6b80b07397d57e3fa68fe68304432) 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x8b) [0x56042ebdeceb] 2: (()+0x4892b8) [0x56042e9512b8] 3:
[Bug 1524635] Re: haproxy syslog configuration causes double logging
I've just tried upgrading a system to the haproxy from your PPA, and it now only logs to /var/log/syslog. The rsyslog.d file has disappeared completely, and its no longer logging to /var/log/haproxy.log. Is that the intended outcome from this? Or should it be logging to just /var/log/haproxy.log? I also tried installing the new haproxy by hand, and it still had /etc/rsyslog.d/haproxy.conf file, and was only logging to /var/log/syslog. Please let me know if you need any more information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524635 Title: haproxy syslog configuration causes double logging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1524635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572320] Re: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova-consoleauth stopped
This just occured on another cloud, this time with nova-consoleauth 1:2015.1.4-0ubuntu2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572320 Title: nova-consoleauth (2:12.0.2-0ubuntu1~cloud0) upgrade leaves nova- consoleauth stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1572320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
I've upgraded systemd across my cluster to 229-4ubuntu6, removed all my custom tweaks to systemd settings, reloaded the daemon and both rabbitmq and mysql appear to be working fine on my openstack cluster. I'll be throwing a bit more load at it, but usually by this point mysql has fallen over, so I'd say this is a success. ** 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/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579586] [NEW] ppc64el node maas install failing talking to mpath0
Public bug reported: I'm trying to install a PPC64EL node with Xenial via MAAS 1.9.2 using Juju 1.25.5 and it seems to be failing due to a possible multipath issue. The node is setup in maas with a default single partition. The boot logs show: Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... lvmetad is not active yet, using direct activation during sysinit Volume group "mpath0" not found Cannot process volume group mpath0 done. and then multiple repeats of: Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... lvmetad is not active yet, using direct activation during sysinit Volume group "mpath0" not found Cannot process volume group mpath0 done. To finally fail with: Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mapper/mpath0-part2 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument $ dpkg-query -W maas maas1.9.2+bzr4568-0ubuntu1~trusty1 $ dpkg-query -W juju-core juju-core 1.25.5-0ubuntu1~14.04.2~juju1 Kernel version booting on the PPC64EL node is Linux version 4.4.0-21-generic. Please let me know what further information you require to debug this. Thanks, Brad ** Affects: multipath-tools (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579586 Title: ppc64el node maas install failing talking to mpath0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1579586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578080] Re: percona cluster hits resource limits in HA Openstack cloud with xenial
FWIW I'm also seeing limits hit in other areas, rabbitmq-server seems to be a common one. I'm also randomly seeing: Failed to allocate directory watch: Too many open files on the command line. I suspect its related to the percona and rabbitmq services hitting limits, but I'm not exactly sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578080 Title: percona cluster hits resource limits in HA Openstack cloud with xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/percona-xtradb-cluster-5.6/+bug/1578080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1567807] [NEW] nova delete doesn't work with EFI booted VMs
Public bug reported: I've been setting up a Mitaka Openstack using the cloud archive running on Trusty, and am having problems working with EFI enabled instances on ARM64. I've done some work with wgrant and gotten things to a stage where I can boot instances, using the aavmf images. However, when I tried to delete a VM booted like this, I get an error: libvirtError: Requested operation is not valid: cannot delete inactive domain with nvram I've included the full traceback at https://paste.ubuntu.com/15682718/. Thanks to a suggestion from wgrant again, I got it working by editing nova/virt/libvirt/guest.py in delete_configuration() and replacing self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE) with self._domain.undefineFlags(libvirt.VIR_DOMAIN_UNDEFINE_MANAGED_SAVE | libvirt.VIR_DOMAIN_UNDEFINE_NVRAM). I've attached a rough patch. Once that's applied and nova-compute restarted, I was able to delete the instance fine. Could someone please investigate this and see if its the correct fix, and look at getting it fixed in the archive? This was done on a updated trusty deployment using the cloud-archives for mitaka. $ dpkg-query -W python-nova python-nova 2:13.0.0~b2-0ubuntu1~cloud0 Please let me know if you need any further information. ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Attachment added: "nova-libvirt-fix-delete.patch" https://bugs.launchpad.net/bugs/1567807/+attachment/4628612/+files/nova-libvirt-fix-delete.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567807 Title: nova delete doesn't work with EFI booted VMs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1567807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
Note these are freshly bootstrapped clouds, as per an irc conversation with alexisb and anastasiamac_. I took a working juju environment deploying to canonistack, just changed the default series, did a juju bootstrap and then a juju deploy local:xenial/ubuntu --to lxc:0, and got an error as above. I also confirmed that the bootstrap node had lxc installed when I first could log into it, before trying to deploy LXC to it: dpkubuntu@juju-bradm-lcy01-machine-0:~$ dpkg --list | grep lxc ii liblxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (library) ii lxc 2.0.0~rc10-0ubuntu2 all Transitional package for lxc1 ii lxc-common 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools ii lxcfs2.0.0~rc5-0ubuntu1 amd64 FUSE based filesystem for LXC ii python3-lxc 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (Python 3.x bindings) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
Note these are freshly bootstrapped clouds, as per an irc conversation with alexisb and anastasiamac_. I took a working juju environment deploying to canonistack, just changed the default series, did a juju bootstrap and then a juju deploy local:xenial/ubuntu --to lxc:0, and got an error as above. I also confirmed that the bootstrap node had lxc installed when I first could log into it, before trying to deploy LXC to it: dpkubuntu@juju-bradm-lcy01-machine-0:~$ dpkg --list | grep lxc ii liblxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (library) ii lxc 2.0.0~rc10-0ubuntu2 all Transitional package for lxc1 ii lxc-common 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (common tools) ii lxc-templates2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (templates) ii lxc1 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools ii lxcfs2.0.0~rc5-0ubuntu1 amd64 FUSE based filesystem for LXC ii python3-lxc 2.0.0~rc10-0ubuntu2 amd64 Linux Containers userspace tools (Python 3.x bindings) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] [NEW] xenial juju 1.25.3 unable to deploy to lxc containers
Public bug reported: There appears to be some issue with deploying to lxc containers using juju 1.25.3 on Xenial. When deploying with xenial to canonistack-lcy02: bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0 Added charm "local:xenial/ubuntu-2" to the environment. ERROR adding new machine to host unit "ubuntu/1": cannot add a new machine: machine 0 cannot host lxc containers When deploying with trusty to canonistack-lcy02, the only change I made was to change the default-series from xenial to trusty: bradm@serenity:~/src/juju$ juju deploy local:trusty/ubuntu --to lxc:0 Added charm "local:trusty/ubuntu-1" to the environment. Versions used to deploy: $ juju --version 1.25.3-xenial-amd64 $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Please let me know if you need any further information. ** Affects: juju-core (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.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557345] [NEW] xenial juju 1.25.3 unable to deploy to lxc containers
Public bug reported: There appears to be some issue with deploying to lxc containers using juju 1.25.3 on Xenial. When deploying with xenial to canonistack-lcy02: bradm@serenity:~/src/juju$ juju deploy local:xenial/ubuntu --to lxc:0 Added charm "local:xenial/ubuntu-2" to the environment. ERROR adding new machine to host unit "ubuntu/1": cannot add a new machine: machine 0 cannot host lxc containers When deploying with trusty to canonistack-lcy02, the only change I made was to change the default-series from xenial to trusty: bradm@serenity:~/src/juju$ juju deploy local:trusty/ubuntu --to lxc:0 Added charm "local:trusty/ubuntu-1" to the environment. Versions used to deploy: $ juju --version 1.25.3-xenial-amd64 $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 Please let me know if you need any further information. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1557327] [NEW] kvm-ok script gives syntax error when running on kvm
Public bug reported: While debugging something, I ran the kvm-ok script on a VM running on openstack, and got an interesting error: ubuntu@juju-bradm-lcy02-machine-0:~$ sudo kvm-ok INFO: /dev/kvm does not exist HINT: sudo modprobe kvm_intel INFO: Your CPU supports KVM extensions /usr/sbin/kvm-ok: 120: /usr/sbin/kvm-ok: Syntax error: "else" unexpected (expecting "then") ubuntu@juju-bradm-lcy02-machine-0:~$ echo $? 2 The code in question just needs a ; then added at the end of it. Please let me know if you need any further information. $ dpkg-query -W cpu-checker cpu-checker 0.7-0ubuntu6 $ lsb_release -d Description:Ubuntu Xenial Xerus (development branch) ** Affects: cpu-checker (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557327 Title: kvm-ok script gives syntax error when running on kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1557327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524635] [NEW] haproxy syslog configuration causes double logging
Public bug reported: The current rsyslogd configuration as provided by the rsyslogd package causes double logging to occur. Steps to Reproduce: 1) Install haproxy via whatever normal means (apt-get etc) 2) Configure it to listen on at least one port, even just the stats port 3) Visit the URL configured You'll see logs generated in both /var/log/syslog (via /etc/rsyslogd.d/50-default.conf) and /var/log/haproxy.log (via /etc/rsyslog.d/haproxy.conf). Steps to fix: 1) mv /etc/rsyslog.d/haproxy.conf 49-haproxy.conf # This could be any number less than 50, to have it read before the default.conf 2) Restart rsyslog. 3) Access the provided service This will cause the entries to be written out to only /var/log/haproxy.log. The testing was done on a Ubuntu 14.04 server (trusty) with haproxy 1.4.24-2ubuntu0.3 installed: $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 $ dpkg-query -W haproxy haproxy 1.4.24-2ubuntu0.3 Please let me know if you have any further questions. ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1524635 Title: haproxy syslog configuration causes double logging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1524635/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1524635] [NEW] haproxy syslog configuration causes double logging
Public bug reported: The current rsyslogd configuration as provided by the rsyslogd package causes double logging to occur. Steps to Reproduce: 1) Install haproxy via whatever normal means (apt-get etc) 2) Configure it to listen on at least one port, even just the stats port 3) Visit the URL configured You'll see logs generated in both /var/log/syslog (via /etc/rsyslogd.d/50-default.conf) and /var/log/haproxy.log (via /etc/rsyslog.d/haproxy.conf). Steps to fix: 1) mv /etc/rsyslog.d/haproxy.conf 49-haproxy.conf # This could be any number less than 50, to have it read before the default.conf 2) Restart rsyslog. 3) Access the provided service This will cause the entries to be written out to only /var/log/haproxy.log. The testing was done on a Ubuntu 14.04 server (trusty) with haproxy 1.4.24-2ubuntu0.3 installed: $ lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 $ dpkg-query -W haproxy haproxy 1.4.24-2ubuntu0.3 Please let me know if you have any further questions. ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524635 Title: haproxy syslog configuration causes double logging To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1524635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] Re: Broken juju LXC deployments
This does indeed appear to work correctly, I've deployed a container using juju: ubuntu@apollo:~$ dpkg-query -W lxc lxc 1.0.8-0ubuntu0.3 ubuntu@apollo:~$ sudo lxc-ls --fancy NAME STATEIPV4IPV6 AUTOSTART -- juju-machine-0-lxc-0 RUNNING x.y.z.171 - YES juju-trusty-lxc-template STOPPED - - NO ubuntu@apollo:~$ sudo lxc-attach -n juju-machine-0-lxc-0 root@juju-machine-0-lxc-0:~# Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515463] Re: Broken juju LXC deployments
This does indeed appear to work correctly, I've deployed a container using juju: ubuntu@apollo:~$ dpkg-query -W lxc lxc 1.0.8-0ubuntu0.3 ubuntu@apollo:~$ sudo lxc-ls --fancy NAME STATEIPV4IPV6 AUTOSTART -- juju-machine-0-lxc-0 RUNNING x.y.z.171 - YES juju-trusty-lxc-template STOPPED - - NO ubuntu@apollo:~$ sudo lxc-attach -n juju-machine-0-lxc-0 root@juju-machine-0-lxc-0:~# Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] Re: Broken juju LXC deployments
FWIW and a totally expected result, I just downgraded the LXC packages on these hosts and redeployed, and things came up ok. $ dpkg-query -W lxc lxc 1.0.7-0ubuntu0.10 I don't think this changes anything, but just putting it here for completeness. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1515463] Re: Broken juju LXC deployments
FWIW and a totally expected result, I just downgraded the LXC packages on these hosts and redeployed, and things came up ok. $ dpkg-query -W lxc lxc 1.0.7-0ubuntu0.10 I don't think this changes anything, but just putting it here for completeness. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515463 Title: Broken juju LXC deployments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] [NEW] Broken juju LXC deployments
Public bug reported:
I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
>From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
>From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1515463
Title:
Broken juju LXC deployments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515463] [NEW] Broken juju LXC deployments
Public bug reported:
I've just tried using juju to deploy to a container with trusty-proposed
repo enabled, and I get an error message about 'failed to retrieve the
template to clone'. The underlying error appears to be:
tar --numeric-owner -xpJf
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;
This seems to be fairly obvious, trying to use xz on a tar.gz file is
never going to work.
The change appears to be from
https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
it assumes everything passed into it will be a .tar.xz file.
This appears to be a conflict between the template expecting a .tar.xz
file, and juju providing it a .tar.gz file. You can see what juju is
providing from:
$ ubuntu-cloudimg-query trusty released amd64 --format %{url}
https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz
>From the juju deployed host:
$ apt-cache policy lxc-templates
lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
*** 1.0.8-0ubuntu0.1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64
Packages
100 /var/lib/dpkg/status
>From the host running juju:
$ apt-cache policy juju-core
juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
1.25.0-0ubuntu1~14.04.1~juju1 0
500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64
Packages
*** 1.22.8-0ubuntu1~14.04.1 0
400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64
Packages
100 /var/lib/dpkg/status
All machine involved are running trusty:
$ lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
Please let me know if you need any more information.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1515463
Title:
Broken juju LXC deployments
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1515463/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1507471] [NEW] nagios3 crashes with livestatus and downtimed checks
Public bug reported: Issue --- When nagios3 is configured to have livestatus from check-mk-livestatus as a broker module, and checks have a downtime applied to them it will crash when the logs rotate. This shows up in /var/log/nagios3/nagios.log as: [1445238000] Caught SIGSEGV, shutting down... Steps to reproduce - * Install nagios3 and check-mk-livestatus * Edit /etc/nagios3/nagios.cfg to enable livestatus: broker_module=/usr/lib/check_mk/livestatus.o /var/lib/nagios3/livestatus/socket * To speed up testing, edit /etc/nagios3/nagios.cfg to set: log_rotation_method=h This will cause log rotation to occur hourly, rather than weekly or daily. * Restart nagios to apply these fixes. * Apply a downtime on any host or service to last until the top of the next hour * Wait until that time, and see that nagios crashes with the SIGSEGV error. Solution - After some searching around I found a patch at http://lists.mathias-kettner.de/pipermail/checkmk-en/2013-December/011087.html which I have applied to nagios source and thrown up into a PPA at ppa:brad-marshall/nagios for testing. Reproducing the steps above but with the upgraded package means it no longer crashes. The testing was done with latest patched Trusty, specifically: $ lsb_release -d Description:Ubuntu 14.04.3 LTS $ dpkg-query -W nagios3 nagios3 3.5.1-1ubuntu1 $ dpkg-query -W check-mk-livestatus check-mk-livestatus 1.2.2p3-1 Please let us know if you need any further information, or any testing done. ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507471 Title: nagios3 crashes with livestatus and downtimed checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1507471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507471] [NEW] nagios3 crashes with livestatus and downtimed checks
Public bug reported: Issue --- When nagios3 is configured to have livestatus from check-mk-livestatus as a broker module, and checks have a downtime applied to them it will crash when the logs rotate. This shows up in /var/log/nagios3/nagios.log as: [1445238000] Caught SIGSEGV, shutting down... Steps to reproduce - * Install nagios3 and check-mk-livestatus * Edit /etc/nagios3/nagios.cfg to enable livestatus: broker_module=/usr/lib/check_mk/livestatus.o /var/lib/nagios3/livestatus/socket * To speed up testing, edit /etc/nagios3/nagios.cfg to set: log_rotation_method=h This will cause log rotation to occur hourly, rather than weekly or daily. * Restart nagios to apply these fixes. * Apply a downtime on any host or service to last until the top of the next hour * Wait until that time, and see that nagios crashes with the SIGSEGV error. Solution - After some searching around I found a patch at http://lists.mathias-kettner.de/pipermail/checkmk-en/2013-December/011087.html which I have applied to nagios source and thrown up into a PPA at ppa:brad-marshall/nagios for testing. Reproducing the steps above but with the upgraded package means it no longer crashes. The testing was done with latest patched Trusty, specifically: $ lsb_release -d Description:Ubuntu 14.04.3 LTS $ dpkg-query -W nagios3 nagios3 3.5.1-1ubuntu1 $ dpkg-query -W check-mk-livestatus check-mk-livestatus 1.2.2p3-1 Please let us know if you need any further information, or any testing done. ** Affects: nagios3 (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios3 in Ubuntu. https://bugs.launchpad.net/bugs/1507471 Title: nagios3 crashes with livestatus and downtimed checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios3/+bug/1507471/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1500739] [NEW] CPU lockup on HP Proliant DL380 Gen9 servers
Public bug reported: Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9 servers lock up with a similar looking cpu lockup bug. All 3 of these servers are nova-compute nodes in an OpenStack cluster, with a reasonable amount of load on them. The symptoms are the load shoots up into the hundreds, and ps stops returning. I've attached lspci -vnvn and 3 sets of syslog message traces that we grabbed on each of the 3 times it has crashed. $ cat /proc/version_signature Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Please let us know if you need any further information. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: canonical-bootstack ** Attachment added: "lspci-vnvn output" https://bugs.launchpad.net/bugs/1500739/+attachment/4478311/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers
The first of the lockups. These all required us to hard reset the servers via the ilo. ** Attachment added: "CPU Lockup 1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478312/+files/cpu-lockup-1.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers
2nd of the lockups. ** Attachment added: "CPU Lockup 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478313/+files/cpu-lockup-2.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers
3rd of the lockups ** Attachment added: "CPU Lockup 3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+attachment/4478314/+files/cpu-lockup-3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers
Unfortunately we're unable to test the latest upstream kernel in this situation. These servers are running a production system, and as they use bcache we need a kernel that supports it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479438/+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/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479437/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479444/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479445/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479442/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479441/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479439/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479440/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479436/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] Re: CPU lockup on HP Proliant DL380 Gen9 servers
apport information ** Tags added: apport-collected trusty uec-images ** Description changed: Over the past 3-ish weeks we've had 3 seperate HP Proliant DL380 Gen9 servers lock up with a similar looking cpu lockup bug. All 3 of these servers are nova-compute nodes in an OpenStack cluster, with a reasonable amount of load on them. The symptoms are the load shoots up into the hundreds, and ps stops returning. I've attached lspci -vnvn and 3 sets of syslog message traces that we grabbed on each of the 3 times it has crashed. $ cat /proc/version_signature Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 Please let us know if you need any further information. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Sep 29 06:47 seq + crw-rw 1 root audio 116, 33 Sep 29 06:47 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.14.1-0ubuntu3.15 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=c2111986-9219-44f2-ad09-8d367ce8b30b + MachineType: HP ProLiant DL380 Gen9 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic root=UUID=038cefb6-3559-4104-9754-5308497961f5 ro console=tty0 console=ttyS1,115200 BOOTIF=01-3c:a8:2a:23:f5:00 quiet + ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15 + RelatedPackageVersions: + linux-restricted-modules-3.16.0-49-generic N/A + linux-backports-modules-3.16.0-49-generic N/A + linux-firmware 1.127.15 + RfKill: Error: [Errno 2] No such file or directory + Tags: trusty uec-images + Uname: Linux 3.16.0-49-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout libvirtd lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/06/2015 + dmi.bios.vendor: HP + dmi.bios.version: P89 + dmi.chassis.type: 23 + dmi.chassis.vendor: HP + dmi.modalias: dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr: + dmi.product.name: ProLiant DL380 Gen9 + dmi.sys.vendor: HP ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479435/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1500739] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1500739/+attachment/4479443/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1500739 Title: CPU lockup on HP Proliant DL380 Gen9 servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1500739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356392] Re: lacks sw raid1 install support
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1356392 Title: lacks sw raid1 install support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1356392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1356392] Re: lacks sw raid1 install support
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1356392 Title: lacks sw raid1 install support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1356392/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1186662] Re: isc-dhcp-server fails to renew lease file
** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432493] [NEW] ntp dhcp hook doesn't check if ntp.conf has been updated
Public bug reported: /etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has been updated since the last time dhclient ran. A simple addition of a check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp, and if so letting it add the servers would be sufficient. This is occuring on a Trusty host with ntp version 1:4.2.6.p5+dfsg- 3ubuntu2.14.04.2. Please let me know if you need any further information. $ dpkg-query -W ntp ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.2 $ lsb_release -d Description:Ubuntu 14.04.2 LTS ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1432493 Title: ntp dhcp hook doesn't check if ntp.conf has been updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1432493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432493] [NEW] ntp dhcp hook doesn't check if ntp.conf has been updated
Public bug reported: /etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has been updated since the last time dhclient ran. A simple addition of a check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp, and if so letting it add the servers would be sufficient. This is occuring on a Trusty host with ntp version 1:4.2.6.p5+dfsg- 3ubuntu2.14.04.2. Please let me know if you need any further information. $ dpkg-query -W ntp ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.2 $ lsb_release -d Description:Ubuntu 14.04.2 LTS ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Tags added: canonical-bootstack -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1432493 Title: ntp dhcp hook doesn't check if ntp.conf has been updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1432493/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1421075] [NEW] Typo with dynamically removing port forward in ssh
Public bug reported: When using ssh and managing ssh port forwards with ~C to remove a forward that doesn't exist, the following occurs: user@host:~$ ssh -KD12345 Unkown port forwarding. ie, the mispelling of the work Unknown as 'Unkown'. This occurs at least on a server running on trusty: $ dpkg --list | grep openssh ii openssh-client 1:6.6p1-2ubuntu2 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:6.6p1-2ubuntu2 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:6.6p1-2ubuntu2 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines Please let me know if you need any more information. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1421075 Title: Typo with dynamically removing port forward in ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1421075/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1421075] [NEW] Typo with dynamically removing port forward in ssh
Public bug reported: When using ssh and managing ssh port forwards with ~C to remove a forward that doesn't exist, the following occurs: user@host:~$ ssh -KD12345 Unkown port forwarding. ie, the mispelling of the work Unknown as 'Unkown'. This occurs at least on a server running on trusty: $ dpkg --list | grep openssh ii openssh-client 1:6.6p1-2ubuntu2 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:6.6p1-2ubuntu2 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server 1:6.6p1-2ubuntu2 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines Please let me know if you need any more information. ** Affects: openssh (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.net/bugs/1421075 Title: Typo with dynamically removing port forward in ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1421075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392583] Re: bluetooth mouse frequently times out
Hi, Brad Marshall, could you please test the latest mainline kernel (3.18-rc5) and advise to the results? Done, roughly the same results - still timeouts, still having to reset the bluetooth service to get things going again sometimes. Also, did this issue not occur in a release prior to Utopic? As mentioned in a previous comment, it did occur, just seemingly not as frequently. Please let me know if you need any further information. Thanks, Brad ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392583 Title: bluetooth mouse frequently times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392583] Re: bluetooth mouse frequently times out
Hi, Brad Marshall, which previous release(s) specifically did it occur in? As well, could you please quantify how much less frequently? I did my initial install on Raring, and I've upgraded across every release since then. I do remember it happening occasionally on the earlier ones - maybe a couple of times a week or so. It feels like its been increasing in frequency over time, but maybe thats just me getting more annoyed at it over time. I'm seeing it multiple times a day now, sometimes it takes a while to restart, sometimes I see the timeout in the messages. I don't have any data to say how many times per week on earlier releases, and will be unable to get it - I don't particuarly want to reinstall my laptop to get that data. Please let me know if you have any further questions. Thanks, Brad ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392583 Title: bluetooth mouse frequently times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392583] Re: bluetooth mouse frequently times out
If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? Done, and it doesn't seem to change anything. If it doesn't, could you please both specify what happened Er, how can I specify what happened when its not changed? :) I'm still seeing timeouts, its still behaving the same. and provide the output of the following terminal command: $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date A10 08/28/2013 Please let me know if you need anything else. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392583 Title: bluetooth mouse frequently times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392583] Re: bluetooth mouse frequently times out
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Yes, it occured in previous versions, just not as frequently I think. Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.18 kernel[0]. Done, I tested with linux-image-3.18.0-031800rc4-generic. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If anything, the bug is worse in upstream, as it was a lot harder to get the mouse to start responding again. Please let me know if you need any further information or debugging done. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392583 Title: bluetooth mouse frequently times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1392583] [NEW] bluetooth mouse frequently times out
Public bug reported: I'm using a Razor Orochi 2013 mouse with my Dell XPS13 laptop via bluetooth on Ubuntu 14.10, and have noticed a seeming increase in the frequency of the timeouts I'm seeing. The symptoms are when I don't use my mouse for a while, it seems to go to sleep, and reasonably frequently when I go to use it again, it won't wake up for a while, and I see the following in my kernel logs: [Nov14 14:33] Bluetooth: hci0 command 0x0405 tx timeout The solution I've ended up using to get it working again is to stop the bluetooth service, rmmod the appropriate modules (btusb, hidp, bluetooth etc), reload them and then restart bluetooth. Sometimes even this isn't sufficient and it takes a bit to recover. Please let me know if you need any further information. Kernel version: $ uname -r 3.16.0-24-generic Ubuntu version: $ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-24-generic 3.16.0-24.32 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bradm 4079 F pulseaudio CurrentDesktop: Unity Date: Fri Nov 14 14:31:33 2014 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=18b9df48-fd12-4eb7-a0e6-351c4ca43c83 InstallationDate: Installed on 2013-08-19 (451 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.16.0-24-generic N/A linux-backports-modules-3.16.0-24-generic N/A linux-firmware 1.138 SourcePackage: linux UpgradeStatus: Upgraded to utopic on 2014-10-10 (35 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1392583 Title: bluetooth mouse frequently times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379629] [NEW] cinder charm doesn't have nrpe-external-master interface
Public bug reported: The cinder charm (and pretty much every other openstack charm) doesn't provide a nrpe-external-master interface, making monitoring it awkward. To fix this it simply needs the following added to the provides section of the metadata.yaml: nrpe-external-master: interface: nrpe-external-master scope: container I've got a branch at lp:~brad- marshall/charms/trusty/cinder/add-n-e-m-interface with the change in it. ** Affects: swift (Ubuntu) Importance: Undecided Status: New ** Affects: ceilometer (Juju Charms Collection) Importance: Undecided Status: New ** Affects: ceph (Juju Charms Collection) Importance: Undecided Status: New ** Affects: ceph-osd (Juju Charms Collection) Importance: Undecided Status: New ** Affects: cinder (Juju Charms Collection) Importance: Undecided Status: New ** Affects: glance (Juju Charms Collection) Importance: Undecided Status: New ** Affects: heat (Juju Charms Collection) Importance: Undecided Status: New ** Affects: keystone (Juju Charms Collection) Importance: Undecided Status: New ** Affects: mongodb (Juju Charms Collection) Importance: Undecided Status: New ** Affects: neutron-api (Juju Charms Collection) Importance: Undecided Status: New ** Affects: nova-cloud-controller (Juju Charms Collection) Importance: Undecided Status: New ** Affects: openstack-dashboard (Juju Charms Collection) Importance: Undecided Status: New ** Affects: percona-cluster (Juju Charms Collection) Importance: Undecided Status: New ** Affects: quantum-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Affects: swift-storage (Juju Charms Collection) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Also affects: ceilometer (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: ceph (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: ceph-osd (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: glance (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: heat (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: keystone (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: percona-cluster (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: neutron-api (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nova-cloud-controller (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: openstack-dashboard (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: quantum-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: swift (Ubuntu) Importance: Undecided Status: New ** Also affects: swift-storage (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: mongodb (Juju Charms Collection) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1379629 Title: cinder charm doesn't have nrpe-external-master interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1379629/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1379629] [NEW] cinder charm doesn't have nrpe-external-master interface
Public bug reported: The cinder charm (and pretty much every other openstack charm) doesn't provide a nrpe-external-master interface, making monitoring it awkward. To fix this it simply needs the following added to the provides section of the metadata.yaml: nrpe-external-master: interface: nrpe-external-master scope: container I've got a branch at lp:~brad- marshall/charms/trusty/cinder/add-n-e-m-interface with the change in it. ** Affects: swift (Ubuntu) Importance: Undecided Status: New ** Affects: ceilometer (Juju Charms Collection) Importance: Undecided Status: New ** Affects: ceph (Juju Charms Collection) Importance: Undecided Status: New ** Affects: ceph-osd (Juju Charms Collection) Importance: Undecided Status: New ** Affects: cinder (Juju Charms Collection) Importance: Undecided Status: New ** Affects: glance (Juju Charms Collection) Importance: Undecided Status: New ** Affects: heat (Juju Charms Collection) Importance: Undecided Status: New ** Affects: keystone (Juju Charms Collection) Importance: Undecided Status: New ** Affects: mongodb (Juju Charms Collection) Importance: Undecided Status: New ** Affects: neutron-api (Juju Charms Collection) Importance: Undecided Status: New ** Affects: nova-cloud-controller (Juju Charms Collection) Importance: Undecided Status: New ** Affects: openstack-dashboard (Juju Charms Collection) Importance: Undecided Status: New ** Affects: percona-cluster (Juju Charms Collection) Importance: Undecided Status: New ** Affects: quantum-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Affects: swift-storage (Juju Charms Collection) Importance: Undecided Status: New ** Tags: canonical-bootstack ** Also affects: ceilometer (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: ceph (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: ceph-osd (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: glance (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: heat (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: keystone (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: percona-cluster (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: neutron-api (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: nova-cloud-controller (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: openstack-dashboard (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: quantum-gateway (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: swift (Ubuntu) Importance: Undecided Status: New ** Also affects: swift-storage (Juju Charms Collection) Importance: Undecided Status: New ** Also affects: mongodb (Juju Charms Collection) 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/1379629 Title: cinder charm doesn't have nrpe-external-master interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swift/+bug/1379629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Re: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX
Unfortunately I no longer have this hardware in a workable state, and have upgraded to a new laptop, so I am unable to provide any further debugging information. I suspect we may have to close off this bug unless someone else is having the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228970] Re: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
I had plugged it in before, but for some reason now its detecting it - perhaps I had some upgrades or something between testing that resolved it. I've attached the Pulse Audio verbose logging I get now when I plug my headset in. ** Attachment added: pulseverbose-working-headset.log https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+attachment/3839857/+files/pulseverbose-working-headset.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228970] Re: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
Hi, seem your subsystem Id did not have any entry for the headset Mic in alc269_fixup_tbl So whats the fix here? Is there a work around I can temporarily use to get mine working while a longer term fix is put in place? Brad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228970] Re: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
there are two models and you need to find out the pin detect of headphone or MicJack is used when headset is pluuged using hda-jack-sense-test I'm a bit confused here, because while getting hda-jack-sense-test going, the headphones suddenly started working. I get: $ hda-jack-sense-test Pin 0x15 (Black HP Out): present = Yes Pin 0x18 (Black Mic): present = Yes and the headphones are now working. I don't believe I made any config changes, nor do I think I did anything different. The only thing it could possibly be is perhaps I somehow plugged the headphones in slightly differently and it got a connection this time. THe headphones working seems repeatable, every time I plug them in now it is working. I can hear a slight fuzzy background noise when there's no sound, or the volume is low, but its definately useable. Thanks, Brad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228970] [NEW] [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
Public bug reported: Hi, After upgrading my Dell XPS13 laptop to Saucy, I am unable to hear any useful sound out of the headphone jack. When I plug my headphones into the jack I can see the Built-in Audio for the Speakers briefly flick over to Headphones and then either flick back to Speakers most of the time or occasionally it will stay on headphones, but any sound output is extremely crackly and useless. On the times that it won't stay as headphones I can force it by running: $ pactl set-sink-port alsa_output.pci-_00_1b.0.analog-stereo analog- output-headphones This just forces it into the crackly output state as above. I've attached a verbose pulse log from attaching the headphones as pulseverbose.log. Please let me know if you need any more information. Thanks, Brad ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bradm 3486 F pulseaudio /dev/snd/pcmC0D0c: bradm 3486 F...m pulseaudio Date: Mon Sep 23 09:13:26 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-19 (34 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bradm 3486 F pulseaudio /dev/snd/pcmC0D0c: bradm 3486 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to saucy on 2013-09-13 (9 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-09-23T09:09:56.448103 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: pulseverbose.log https://bugs.launchpad.net/bugs/1228970/+attachment/3835509/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228970] Re: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
the icon near the Jack indicate it is a headset jack (headphone with Mic) http://www.dell.com/us/dfh/p/xps-13-l321x-mlk/pd Yes, that is correct. are you using headphone (TRS) or headset (TRRS) connector Its a headset that I use successfully with my Android phone, one of the Logitech UE range. I'm not 100% sure of the model, it might have been a UE200vi. I seem to get the same result if I use normal, non-headset headphones though. post result of hda-jack-sense-test when headset is plugged and unplugged I tried installing hda-jack-sense-test from ppa:diwic/ppa but there doesn't appear to be any saucy repos there. Where is the best place to get this tool from for Saucy? Thanks, Brad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215282] [NEW] Possible puppet performance regression with 2.7.11-1ubuntu2.4
Public bug reported: We appear to have a performance regression with puppet 2.7.11-1ubuntu2.4 that we recently upgraded to, particularly on our more heavily loaded puppet master. When we're running 2.4, many of our puppet clients get the following: err: Could not retrieve catalog from remote server: execution expired and the load on the puppet master is higher than with 2.3. When we revert back to 2.3, the load is much lower (around 20 rather than around 40), and most of the puppet clients can retrieve the catalog without a problem. Is there any further information you need, or any debugging we can assist with finding out what the issue is here? OS Version: Ubuntu 12.04.3 LTS $ dpkg-query -W puppet puppet 2.7.11-1ubuntu2.4 ** Affects: puppet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1215282 Title: Possible puppet performance regression with 2.7.11-1ubuntu2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1215282/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1215282] [NEW] Possible puppet performance regression with 2.7.11-1ubuntu2.4
Public bug reported: We appear to have a performance regression with puppet 2.7.11-1ubuntu2.4 that we recently upgraded to, particularly on our more heavily loaded puppet master. When we're running 2.4, many of our puppet clients get the following: err: Could not retrieve catalog from remote server: execution expired and the load on the puppet master is higher than with 2.3. When we revert back to 2.3, the load is much lower (around 20 rather than around 40), and most of the puppet clients can retrieve the catalog without a problem. Is there any further information you need, or any debugging we can assist with finding out what the issue is here? OS Version: Ubuntu 12.04.3 LTS $ dpkg-query -W puppet puppet 2.7.11-1ubuntu2.4 ** Affects: puppet (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.net/bugs/1215282 Title: Possible puppet performance regression with 2.7.11-1ubuntu2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1215282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163800] Re: launcher, dash, hud etc all fail to start
Hi Chris, No, I have a hybrid ATI/Intel card in my laptop, not Nvidia. I didn't try clearing out my configs piecemeal, I just moved the whole lot, so I'm not sure which subset of my config was busted. I'm fine with marking it Won't Fix if thats what you'd prefer since I found a work around and there's no obvious bug other than something in my config being messed up. Thanks, Brad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163800 Title: launcher, dash, hud etc all fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163800] Re: launcher, dash, hud etc all fail to start
This appears to have been something in my personal config - a test user didn't replicate the issue, and after moving all relevant directories out of the way (.compiz, .config, .dbus, .gconf, .gnome2* and .local), I was able to get a clean unity session up. There must be some kind of cruft in my config from quantal to raring which caused this - it would probably be nice to figure out, but could be tricky to diagnose with the lack of information given by the system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163800 Title: launcher, dash, hud etc all fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163800] [NEW] launcher, dash, hud etc all fail to start
Public bug reported: After logging into a ubuntu session in lightdm it fails to provide a usable interface of any sort. After logging in and seeing the dash appear briefly, the launcher, hud, dock, top menu or any interface at all does not appear. If I fire up a terminal when the dash briefly appears it has a normal appearance - close, minimize, maximize buttons, scroll bars etc. Before upgrading to raring, unity was running fine. My hardware is a HP Inspirion DV6-3030TX, with an externally connected 23 LCD monitor which does appear to be working correctly at least as far as X is concerned. I see the following in my .xsession errors, which implies that my hardware supports compiz and unity: compiz (core) - Info: Unity is fully supported by your hardware. Testing GLX, it appears to be running fine: $ glxinfo name of display: :0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 $ lsb_release -rd Description:Ubuntu Raring Ringtail (development branch) Release:13.04 $ apt-cache policy unity unity: Installed: 6.12.0daily13.04.01-0ubuntu1 Candidate: 6.12.0daily13.04.01-0ubuntu1 Version table: *** 6.12.0daily13.04.01-0ubuntu1 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status Please let me know if you need any more information regarding this. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Apr 3 18:42:26 2013 InstallationDate: Installed on 2010-07-02 (1006 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-03-21 (12 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163800 Title: launcher, dash, hud etc all fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Re: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX
apport information ** Tags added: apport-collected regression single-occurrence ** Description changed: After upgrading from qantal to raring on a HP Pavillion DV6-3030TX, using the open source radeon drivers, X fails to start. Once I reboot the machine it asks me if I want to start a failsafe X session to see if I can debug the issue. All the logs required should be attached, please let me know what I can do to help resolve this issue, and if you require any more information. What you expected to happen: Get a working Unity X session What happened instead: Given the option to log into a failsafe once off X session $ lsb_release -rd Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 $ dpkg-query -W xserver-xorg-video-radeon xserver-xorg-video-radeon 1:7.1.0-0ubuntu2 $ dpkg-query -W xserver-xorg-video-ati xserver-xorg-video-ati1:7.1.0-0ubuntu2 $ sudo lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Madison [Radeon HD 5000M Series] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-radeon 1:7.1.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.9.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 22 10:49:03 2013 DistUpgraded: 2013-03-21 20:54:37,262 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.1.16, 3.2.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:144a] Advanced Micro Devices [AMD] nee ATI Madison [Radeon HD 5000M Series] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:144a] InstallationDate: Installed on 2010-07-02 (993 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=0c0ea442-d3be-4905-bf58-8e2d4c4ac6d7 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: Upgraded to raring on 2013-03-21 (0 days ago) dmi.bios.date: 03/10/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 144A dmi.board.vendor: Hewlett-Packard dmi.board.version: 65.16 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.03:bd03/10/2010:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049F102430102:rvnHewlett-Packard:rn144A:rvr65.16:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049F102430102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.9~daily13.03.20-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Fri Mar 22 10:41:21 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu3 xserver.video_driver: intel + --- + .tmp.unity.support.test.0: + + ApportVersion: 2.9.2-0ubuntu4 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: compiz + CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' + CompositorUnredirectFSW: true + DistUpgraded: 2013-03-21 20:54:37,262 DEBUG enabling apt cron job + DistroCodename: raring + DistroRelease: Ubuntu 13.04 + DistroVariant: ubuntu + DkmsStatus: vboxhost, 4.1.16, 3.2.0-30-generic, x86_64: installed + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) +
[Bug 1158590] Re: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX
This latest set of apport data is from logging into a unity session after todays upgrades - I get a working x session, but no dash, launcher, hud etc starts up. If I start any application from the console displaying to :0 it does start up as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] xserver.outputs.txt
apport information ** Attachment added: xserver.outputs.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597209/+files/xserver.outputs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] xserver.devices.txt
apport information ** Attachment added: xserver.devices.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597208/+files/xserver.devices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597207/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] make.log.txt
apport information ** Attachment added: make.log.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597206/+files/make.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597205/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597204/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597203/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597202/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597201/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597200/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597199/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597198/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] MonitorsUser.xml.txt
apport information ** Attachment added: MonitorsUser.xml.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597196/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597197/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597195/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597193/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597194/+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/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] LightdmGreeterLogOld.txt
apport information ** Attachment added: LightdmGreeterLogOld.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597192/+files/LightdmGreeterLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] LightdmGreeterLog.txt
apport information ** Attachment added: LightdmGreeterLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597191/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] LightdmDisplayLog.txt
apport information ** Attachment added: LightdmDisplayLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597190/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597189/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597188/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597186/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158590] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1158590/+attachment/3597187/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158590 Title: X server fails to start after upgrading to raring on a HP Pavillion DV6-3030TX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1158590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
