[Bug 1870758] Re: [nvidia] Display scaling results in monitor power save state
** Tags added: champagne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821961] Re: Fix for dual Intel NVMes
Hey there, tested the proposed -48 kernel. Did 15 reboot cycles and everything started every time. Last time it succeeded approximately 90% of the time. That is whey I went to 15 this time. Seems good. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821961 Title: Fix for dual Intel NVMes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816170] Re: KVM instances fail at creation with: Failed to get shared "write" lock Is another process using the image?
** Changed in: juju Status: New => Triaged ** Changed in: juju Importance: Undecided => High ** Changed in: juju Assignee: (unassigned) => Richard Harding (rharding) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816170 Title: KVM instances fail at creation with: Failed to get shared "write" lock Is another process using the image? To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1816170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Yes I intend to test the mainline kernel when I'm back home from the sprint On 20/02/19 2:59 AM, Kai-Heng Feng wrote: > Hi Tim, > > Would it be possible for you to test mainline kernel [1]? It probably > requires more commits to be backported. But first let's make sure it's > fully fixed in mainline kernel. > > [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc7/ > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
It seems my install was missing the linux-generic package. After installing that I was able to get linux-generic 4.15.0.46.48 from bionic-proposed. Installing this removed the windows boot option from my grub config. Rebooting 12 times, 10 times were good, twice I got dumped into initramfs. Photo attached. ** Attachment added: "photo of screen" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+attachment/5239348/+files/2019-02-18%2011.22.08.jpg ** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Will this fix make its way back into the bionic-updates? Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
got the packages installed in the end, and so far has booted every time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
hit the following error installing the test kernel tim@terry:~/Downloads$ ls *.deb linux-headers-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb linux-modules-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb linux-modules-extra-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb tim@terry:~/Downloads$ sudo dpkg -i *.deb (Reading database ... 214537 files and directories currently installed.) Preparing to unpack linux-headers-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb ... Unpacking linux-headers-4.15.0-43-generic (4.15.0-43.46+lp1811755) over (4.15.0-43.46+lp1811755) ... dpkg: regarding linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb containing linux-image-unsigned-4.15.0-43-generic: linux-image-unsigned-4.15.0-43-generic conflicts with linux-image-4.15.0-43-generic linux-image-4.15.0-43-generic (version 4.15.0-43.46) is present and installed. dpkg: error processing archive linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb (--install): conflicting packages - not installing linux-image-unsigned-4.15.0-43-generic Preparing to unpack linux-modules-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb ... Unpacking linux-modules-4.15.0-43-generic (4.15.0-43.46+lp1811755) over (4.15.0-43.46+lp1811755) ... Preparing to unpack linux-modules-extra-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb ... Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46+lp1811755) over (4.15.0-43.46+lp1811755) ... Setting up linux-headers-4.15.0-43-generic (4.15.0-43.46+lp1811755) ... Setting up linux-modules-4.15.0-43-generic (4.15.0-43.46+lp1811755) ... Setting up linux-modules-extra-4.15.0-43-generic (4.15.0-43.46+lp1811755) ... Processing triggers for linux-image-4.15.0-43-generic (4.15.0-43.46) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic /etc/kernel/postinst.d/zz-update-grub: Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.15.0-43-generic Found initrd image: /boot/initrd.img-4.15.0-43-generic Adding boot menu entry for EFI firmware configuration done Errors were encountered while processing: linux-image-unsigned-4.15.0-43-generic_4.15.0-43.46+lp1811755_amd64.deb tim@terry:~/Downloads$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811755] Re: X1 Extreme: only one of the two SSDs is loaded
Yes, I can boot into the 512G disk approximately 50% of the time :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811755] [NEW] X1 Extreme: only one of the two SSDs is loaded
Public bug reported: I bought a new Thinkpad X1 Extreme, and had it come with two SSDs, one 256G and the other 512G with the intention of keeping the windows on the 256G disk and using the 512G for linux. When dealing with the installer, it only ever saw one of the SSDs. I did manged to get bionic installed on the 512, but on boot, sometimes it doesn't find the 512G disk and I just get a blank screen. After a hard power-off, and reboot, it drops into the grub selector, and choosing linux, it failed again, but this time dropped into a VT. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tim2003 F pulseaudio /dev/snd/controlC0: tim2003 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 18:53:34 2019 InstallationDate: Installed on 2019-01-14 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Beta amd64 (20190109) MachineType: LENOVO 20MFCTO1WW ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=9254da2f-0220-4b41-8770-ae4b0df0d114 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811755 Title: X1 Extreme: only one of the two SSDs is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727355] Re: Juju attempts to bootstrap bionic by default
** Changed in: juju-core Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727355 Title: Juju attempts to bootstrap bionic by default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1727355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729127] Re: storage: No available machine matches constraints
** Changed in: juju Milestone: None => 2.3.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729127 Title: storage: No available machine matches constraints To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1729127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729127] Re: storage: No available machine matches constraints
** Changed in: juju Milestone: 2.3.0 => 2.3-beta3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729127 Title: storage: No available machine matches constraints To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1729127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708058] Re: machine locks up - completely non-responsive
This appears to be happening once or twice a day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708058 Title: machine locks up - completely non-responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1708058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708058] Re: machine locks up - completely non-responsive
Added above stacktrace to pastebin for easier reading: http://pastebin.ubuntu.com/25223455/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708058 Title: machine locks up - completely non-responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1708058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708058] [NEW] machine locks up - completely non-responsive
Public bug reported: Starting a few days ago, machine will just lock up. After the most recent lock up, I looked in /var/log/syslog, and found the following: Aug 2 12:17:01 elwood kernel: [58062.900931] BUG: unable to handle kernel NULL pointer dereference at 0018 Aug 2 12:17:01 elwood kernel: [58062.900996] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915] Aug 2 12:17:01 elwood kernel: [58062.901018] PGD 0 Aug 2 12:17:01 elwood kernel: [58062.901019] Aug 2 12:17:01 elwood kernel: [58062.901032] Oops: 0002 [#1] SMP Aug 2 12:17:01 elwood kernel: [58062.901043] Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs scsi_transport_iscsi nvram msr rfcomm xt_conntrack ip t_REJECT nf_reject_ipv4 binfmt_misc veth ebtable_filter ebtables ip6table_filter ip6_tables xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment iptab le_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c bridge stp llc iptable_filter ip_tables x_tables bbswitch(OE) bnep zfs(PO) zunicode(PO) zavl(PO) zcom mon(PO) znvpair(PO) spl(O) snd_hda_codec_hdmi uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core btusb btrtl videodev media nls_iso8859_1 hid_multitouch dell_le d i2c_designware_platform i2c_designware_core snd_hda_codec_realtek snd_hda_codec_generic dell_wmi mxm_wmi intel_rapl Aug 2 12:17:01 elwood kernel: [58062.901247] x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_intel crct10dif_pclmul snd_hda_codec crc32_pclmul snd_hda_core snd_hwdep ghash_cl mulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event aesni_intel aes_x86_64 crypto_simd dell_laptop glue_helper snd_rawmidi cryptd dell_smbios dcdbas snd_seq intel_cstate brcmfmac snd_seq_device snd_timer intel_rapl_perf brcmutil joydev snd cfg80211 input_leds mei_me serio_raw soundcore mei rtsx_pci_ms memstick idma64 virt_dma hci_uart btbcm btqca processor_th ermal_device intel_pch_thermal intel_lpss_pci btintel shpchp intel_soc_dts_iosf bluetooth acpi_als int3403_thermal int3402_thermal kfifo_buf int3400_thermal wmi intel_lpss_acpi intel_ hid int340x_thermal_zone dell_smo8800 acpi_thermal_rel industrialio intel_lpss mac_hid sparse_keymap acpi_pad Aug 2 12:17:01 elwood kernel: [58062.901446] kvm_intel kvm irqbypass parport_pc ppdev lp parport autofs4 hid_generic usbhid rtsx_pci_sdmmc i915 i2c_algo_bit drm_kms_helper syscopyar ea psmouse sysfillrect sysimgblt fb_sys_fops nvme drm ahci nvme_core rtsx_pci libahci i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes [last unloaded: nvidia] Aug 2 12:17:01 elwood kernel: [58062.901530] CPU: 1 PID: 19684 Comm: chrome Tainted: P OE 4.10.0-27-generic #30~16.04.2-Ubuntu Aug 2 12:17:01 elwood kernel: [58062.901556] Hardware name: Dell Inc. XPS 15 9550/0N7TVV, BIOS 1.2.25 05/07/2017 Aug 2 12:17:01 elwood kernel: [58062.901577] task: 88e19427c500 task.stack: 9f567d71 Aug 2 12:17:01 elwood kernel: [58062.901608] RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x124/0x270 [i915] Aug 2 12:17:01 elwood kernel: [58062.901643] RSP: 0018:9f567d713878 EFLAGS: 00010246 Aug 2 12:17:01 elwood kernel: [58062.901659] RAX: 88e1da35bfc0 RBX: 0003 RCX: 0003 Aug 2 12:17:01 elwood kernel: [58062.901679] RDX: RSI: 88e3f979 RDI: 88e4a0d6 Aug 2 12:17:01 elwood kernel: [58062.901699] RBP: 9f567d7138d8 R08: 0018 R09: Aug 2 12:17:01 elwood kernel: [58062.901719] R10: R11: ce5cca7af020 R12: 88e1de90a000 Aug 2 12:17:01 elwood kernel: [58062.901739] R13: 88e226573810 R14: fff87000 R15: 8000 Aug 2 12:17:01 elwood kernel: [58062.901762] FS: 7fcb4ab00a80() GS:88e4bdc4() knlGS: Aug 2 12:17:01 elwood kernel: [58062.901785] CS: 0010 DS: ES: CR0: 80050033 Aug 2 12:17:01 elwood kernel: [58062.901801] CR2: 0018 CR3: 0001a1952000 CR4: 003406e0 Aug 2 12:17:01 elwood kernel: [58062.901822] DR0: DR1: DR2: Aug 2 12:17:01 elwood kernel: [58062.901849] DR3: DR6: fffe0ff0 DR7: 0400 Aug 2 12:17:01 elwood kernel: [58062.901871] Call Trace: Aug 2 12:17:01 elwood kernel: [58062.901893] gen8_alloc_va_range_3lvl+0xf3/0x9b0 [i915] Aug 2 12:17:01 elwood kernel: [58062.901920] gen8_alloc_va_range+0x23e/0x490 [i915] Aug 2 12:17:01 elwood kernel: [58062.901949] i915_vma_bind+0x6a/0x170 [i915] Aug 2 12:17:01 elwood kernel: [58062.901975] __i915_vma_do_pin+0x2a5/0x450 [i915] Aug 2 12:17:01 elwood kernel: [58062.902002] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] Aug 2 12:17:01 elwood kernel: [58062.902032] i915_gem_execbuffer_reserve.isra.32+0x388/0x3b0 [i915] Aug 2 12:17:01 elwood kernel: [58062.902062] i915_gem_do_execbuf
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** No longer affects: juju -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475260] Re: instances cannot resolve their own hostname
Is at least fixed on 2.1.3 ** Changed in: juju Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516989] Re: juju status broken
WARNING: don't use the script in comment #16, but instead use this one: http://pastebin.ubuntu.com/24186473/ This is a copy of the earlier script but adds in the txn-revno and txn- queue fields that are required for when juju wants to update the status to something new. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1516989 Title: juju status broken To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1516989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
Pull request up for the upstream project: https://github.com/go- yaml/yaml/pull/241. Juju patching the upstream for its builds: https://github.com/juju/juju/pull/6983 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
** Changed in: juju Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju Status: Triaged => In Progress ** Changed in: juju Milestone: 2.2.0 => 2.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
Having to push this off the 2.1 milestone due to the dependent library not supporting this use case. ** Changed in: juju Milestone: 2.1.0 => 2.2.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543660] Re: juju needs to fix the yaml parser
https://github.com/go-yaml/yaml/issues/157 has been closed, but the PR mentioned doesn't fix this issue. Juju is being updated, but until go-yaml fixes it, we still have a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543660 Title: juju needs to fix the yaml parser To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1543660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026088] Re: HUD should support applications using both gmenus and standard gtkmenus
** Changed in: indicator-appmenu (Ubuntu) Assignee: Tim Penhey (thumper) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026088 Title: HUD should support applications using both gmenus and standard gtkmenus To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1026088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Juju MIR resposne
This is an answer to some of the questions Seth asked > In 1339770, in May 2015, it was mentioned that 1.18 was end-of-life and no > further updates could be prepared for it. 1.18.0 was released just 13 > months earlier and 1.18.1 had been included in 14.04 LTS. Why was the 1.18 > infrastructure torn down so shortly after including 1.18 in a release with > five-year support? I believe that this change was primarily brought about by the change from using bzr to git. The build and test infrastructure had to be re-tooled to make this work. > Have there been any similar changes in process that > would prevent or delay issuing an update to the currently supported > versions of juju already in the archive? We are unlikely to change from git. > It is currently impossible to upgrade from 14.04 LTS to 15.04 due to > incorrect version numbers. Has anyone else noticed this yet? When will > this be fixed? Are there any changes in process needed to ensure this > doesn't happen in the future? The older versions of Juju were not very good at handling unknown series. I have targeted a previously created bug to address this: https://bugs.launchpad.net/juju-core/+bug/1403689 There are work-arounds that have been used by IS to upgrade older environments. We do test a number of upgrade combinations, and I'm curious as to why you say it is impossible to upgrade? What exactly is the situation you are attempting? > Will the juju team be asking for an MRE? Is it anticipated that new series > (e.g., the 1.18 to 1.22 change) would be included as an MRE? What > processes are in place to test updates before including updates into the > archive? What processes are available to the security team to test > updates that we would prepare? There are CI tests around upgrading from older versions to the current tested release. I believe that one of these tests includes going from 1.18 to the current tested release. > I had more trouble reading the Juju code this review cycle than last > review cycle -- the Facade indirection mechanism makes code navigating > harder. I'm worried about it for a few reasons: > - Strings to reference method names are brittle and can't be checked at > compile time. What methods are in place to ensure that these aren't > typoed? There are unit tests in place that test both the client and server side of every call, and in addition to that there are full feature tests that make sure all the parts align. > - Generic args and return types defeat type checking. What ensures types > being returned or accepted have the desired properties? The specified unit and feature tests. > - Java has had significant problems with their Reflection mechanism, > probably dozens of issues per year. At what points of a process > lifetimes is the Facade mechanism dynamic? During the low level RPC call from the client to the API server. > Here's a few issues I found: > > - ./apiserver/apiserver.go logs passwords when tracing is enabled -- this > is fine IFF this is loudly documented somewhere obvious. Is it? It'd be > best to filter out passwords regardless. I have created a bug to address this more completely: https://bugs.launchpad.net/juju-core/+bug/1500298 > - Chown() doesn't quote the user or group In which cases is this really necessary? All the chowns that the Juju code base does is to either ubuntu, syslog or adm. Other chowns copy the uid/gid directly from the source. > - ./api/client.go WatchDebugLog() claims to read a line but looks like it > may read up to 4096 bytes -- is this correct? The first line returned in the WatchDebugLog is a serialized error, and only a serialized error. The size of the error is always less than 200 bytes, but 4k is a nice block size. Once this initial error has been returned, the websocket is used as a stream. > - significant number of TODO comments; is there a method in place to find > unowned comments and assign them somewhere? is there a process in place > to ensure they get revisited? I don't believe we have a formal process at this stage. New TODO comments are expected to have an associated bug, and a date. > - Which versions of the client work with which versions of the servers? > Where's that described? All clients from 1.18 on should work with any API server. This is the expected behaviour until at least Juju 2.0. > - ./api/keyupdater/authorisedkeys.go AuthorisedKeys(), > WatchAuthorisedKeys() expects exactly one authorized key, this seems > fragile I believe it expects one string, which may be multi-line, and each key is on a different line. > - Is -static-libgo still being used? No idea sorry. > I'm concerned with how previous issues have been handled -- the three > referenced bug reports have combined to represent the single most > expensive consequence I've personally seen and all were known issues five > months earlier. So I need reassurance that the Juju team will help the > security team maintain Juju in our supported re
[Bug 1393825] Re: Juju testsuite fails in random ways
Dave has done some testing, and we are pretty sure that this is due to lack of memory. Can you confirm please the amount of memory on the machine or VM running these tests, and the memory use of the test process? We were not able to reproduce these problems on a VM running with 8gig or ram. ** Changed in: gccgo-go (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393825 Title: Juju testsuite fails in random ways To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-go/+bug/1393825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1328958] Re: Local provider fails when an unrelated /home/ubuntu directory exists
** Also affects: juju-core/1.21 Importance: Undecided Status: New ** Changed in: juju-core Milestone: 1.21-beta4 => 1.22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1328958 Title: Local provider fails when an unrelated /home/ubuntu directory exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304754] Re: gccgo has issues when page size is not 4kB
Gah, must have looked at the page size of my laptop instead:
ubuntu@rockne-02:~$ juju status
environment: local
machines:
"0":
agent-state: down
agent-state-info: (started)
agent-version: 1.18.4.1
dns-name: localhost
instance-id: localhost
series: trusty
services: {}
ubuntu@rockne-02:~$ uname -a
Linux rockne-02 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:41:16 UTC 2014
ppc64le ppc64le ppc64le GNU/Linux
ubuntu@rockne-02:~$ getconf PAGESIZE
65536
** 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/1304754
Title:
gccgo has issues when page size is not 4kB
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304754] Re: gccgo has issues when page size is not 4kB
However rockne-02 has a 4k page :-( ** Tags removed: 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/1304754 Title: gccgo has issues when page size is not 4kB To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304754] Re: gccgo has issues when page size is not 4kB
I can verify that with the above package from trusty-proposed, I was able to bootstrap a local juju environment on rockne-02. ** 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/1304754 Title: gccgo has issues when page size is not 4kB To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348386] Re: lxc template fails to stop
Tested on a precise lxc container I have: it seems we could try with -L (or even better --console-log) and fall back to -c (or --console) if that fails with exit code 1 (we could even check the output for "invalid option". ubuntu@clean-precise:~$ lxc-start -n foo -L omg lxc-start: invalid option -- 'L' Usage: lxc-start --name=NAME -- COMMAND lxc-start start COMMAND in specified container NAME Options : -n, --name=NAME NAME for name of the container -d, --daemon daemonize the container -f, --rcfile=FILELoad configuration file FILE -c, --console=FILE Set the file output for the container console -C, --close-all-fds If any fds are inherited, close them If not specified, exit with failure instead Note: --daemon implies --close-all-fds -s, --define KEY=VAL Assign VAL to configuration variable KEY Common options : -o, --logfile=FILE Output log to FILE instead of stderr -l, --logpriority=LEVEL Set log priority to LEVEL -q, --quiet Don't produce any output -?, --help Give this help list --usage Give a short usage message Mandatory or optional arguments to long options are also mandatory or optional for any corresponding short options. See the lxc-start man page for further information. ubuntu@clean-precise:~$ echo $? 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348386 Title: lxc template fails to stop To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1348386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: non-default lxc-dir breaks local provider
Gah, I should read the entire description before changing things. This was a different problem to me that had exactly the same error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: template container contains user log mount in error
I found that the code was committed back in march to not mount the log dir in the container. My juju-precise-template lxc container had a line that include a mount to /home/tim/.juju/local/log, which caused cgroups to complain when logged in as my other local user. Removing the juju-precise-template and getting juju to recreate it fixed the problem for me. My template container was created about a week before the code landed in trunk. @pitti, can I get you to take a look inside the config file for the lxc container to see if you have a similar problem? ** Changed in: juju-core Assignee: Tim Penhey (thumper) => (unassigned) ** Changed in: juju-core Importance: High => Low ** Changed in: juju-core Milestone: next-stable => None ** Summary changed: - template container contains user log mount in error + non-default lxc-dir breaks local provider -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: non-default lxc-dir breaks local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Summary changed: - fails to start container with local provider with non-default LXC path + template container contains user log mount in error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: template container contains user log mount in error To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
** Changed in: juju-core Milestone: None => next-stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290920] Re: fails to start container with local provider with non-default LXC path
It seems to me that the bug isn't in the different container directory, but the way that the log directory is mounted. I have just hit this same problem locally, and I don't have a non- default directory. What I do have though is two different users locally. When the juju conatiner template is created, the log mount points are added. What this means is that other users on the same machine will not be able to mount the log directory as specified in the container lxc config file, and the cgroup setting will fail. One solution to this is to have a template container per user rather than a shared one. ** Tags added: local lxc regression ** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290920 Title: fails to start container with local provider with non-default LXC path To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1290920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208430] Re: mongodb runs as root user
Critical is a "stop the line" type bug. No one is being assigned to it right now, so it isn't Critical. ** Changed in: juju-core Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208430 Title: mongodb runs as root user To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1208430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Can someone please test this? lp:~thumper/juju-core/maas-no-restart-networking I don't have a MAAS setup to hand, but according to the code above, this *should* work. Now we go ifdown eth0 before messing with the network config, and ifup eth0 ifup br0 after, and no 'restart networking' ** Branch linked: lp:~thumper/juju-core/maas-no-restart-networking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages
** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293549 Title: Filesystem mount from lxc template causes filesystem permission breakages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1293549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291088] Re: Doesn't unlock when coming back from the greeter
I have two users on my laptop, in an attempt to have different sessions for different work. Switching from one user to another takes me to the greeter to enter my password, but when the new session starts, it immediately takes me to the new lockscreen and requests the password again. This is very annoying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291088 Title: Doesn't unlock when coming back from the greeter To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292353] Re: juju must install the libgo.so.5 library when required
Marking as fix committed for trunk developers. We should also make sure the build commands for the package are updated. ** Branch linked: lp:~thumper/juju-core/power-static-link-make ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Changed in: juju-core Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292353 Title: juju must install the libgo.so.5 library when required To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1292353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages
or a chown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293549 Title: Filesystem mount from lxc template causes filesystem permission breakages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1293549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages
Shouldn't aufs catch a chmod to a directory that isn't in the delta and copy it across? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293549 Title: Filesystem mount from lxc template causes filesystem permission breakages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1293549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages
@Serge, while it may be a work around for some, it certainly is going to be a problem in the big picture. We are running code written by others (juju hooks). I'm going to submit a branch to juju to disable aufs by default, but enable the setting so people can try it out. ** Branch linked: lp:~thumper/juju-core/local-provider-aufs-default-off ** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293549 Title: Filesystem mount from lxc template causes filesystem permission breakages To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1293549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** Changed in: juju-core Status: In Progress => Fix Released ** Changed in: juju-core Milestone: 1.20.0 => 1.17.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
I've made a branch out of the patches (well, manually did it). @dann can I get you to give the diff a once over? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1276909] Re: error detecting hardware characteristics: unrecognised architecture: aarch64
** Branch linked: lp:~thumper/juju-core/arm64-identification -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1276909 Title: error detecting hardware characteristics: unrecognised architecture: aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1276909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** Changed in: juju-core Assignee: Tim Penhey (thumper) => Jesse Meek (waigani) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
hallyn: has the autostart behaviour for lxc changed in trusty? thumper: yes, stgraber's new autostart setup may be in now. certainly in the ppa hallyn: yep, it landed with beta2 last week hallyn: hmm... managed to break juju's behaviour hallyn: can you explain the change? juju uses autostart? thumper: yes, autostart settings are now upstream and use the container's config instead hallyn: yep, thumper: I believe I already told someone this morning wrt juju thumper: use "lxc.start.auto = 1" in the container config stgraber: don't expect us to talk to each other :-) stgraber: remind me, is there any attempt at auto-conversion for /etc/lxc/auto/ users? hallyn: yes, there's migration code, but it won't do them much good for new juju containers heh yah any container on the system at the time of the upgrade to beta2 should have been automatically converted (symlink removed, /etc/lxc/auto removed and lxc.start.auto = 1 added to the container config) stgraber: is this lxc going into the cloud archive? stgraber: for precise? is there a way we can work out if this is supported? thumper: maybe hallyn knows, I usually ignore the existence of that external archive entirely -*- thumper nods thumper: rule of thumb would be, if /etc/lxc/auto exists, use it, if not, use lxc.start.auto = 1 stgraber: that makes sense... should be able to handle that pretty easily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271941] Re: lxc container creation fails on trusty host service units
** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271941 Title: lxc container creation fails on trusty host service units To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1043562] Re: [gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000001 IPEHR: 0x60020100
I am currently running saucy, and on a different laptop. No longer experiencing this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043562 Title: [gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0001 IPEHR: 0x60020100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1043562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240709] Re: local provider fails to start
** Changed in: juju-core (Ubuntu Saucy) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240709 Title: local provider fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1240709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting
** Changed in: juju-core Status: In Progress => Fix Committed ** Changed in: juju-core/1.16 Status: In Progress => Fix Committed ** Summary changed: - apparmor blocks cgroup-lite from mounting + local provider deploys fail with 'install hook failed' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: local provider deploys fail with 'install hook failed' To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting
** Branch linked: lp:~thumper/juju-core/fix-local-lxc-install-1.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: apparmor blocks cgroup-lite from mounting To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting
** Also affects: juju-core/1.16 Importance: Undecided Status: New ** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core/1.16 Milestone: None => 1.16.3 ** Changed in: juju-core/1.16 Importance: Undecided => High ** Changed in: juju-core/1.16 Status: New => In Progress ** Changed in: juju-core/1.16 Assignee: (unassigned) => Tim Penhey (thumper) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: apparmor blocks cgroup-lite from mounting To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting
cgroups doesn't come in with build-essential, but it is being brought in by mistake because the lxc package was being installed by mistake in the local provider machines. ** Branch linked: lp:~thumper/juju-core/local-provider-machines-no-lxc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: apparmor blocks cgroup-lite from mounting To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247299] Re: apparmor blocks cgroup-lite from mounting
** Also affects: juju-core Importance: Undecided Status: New ** Changed in: juju-core Status: New => Triaged ** Changed in: juju-core Importance: Undecided => High ** Tags added: local-provider ** Changed in: juju-core Milestone: None => 1.17.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247299 Title: apparmor blocks cgroup-lite from mounting To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1247299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246556] Re: lxc containers broken with maas
** Branch linked: lp:~thumper/juju-core/maas-lxc-trunk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246556 Title: lxc containers broken with maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1246556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: [maas] juju destroy-environment also destroys nodes that are not controlled by juju
** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Milestone: None => 2.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** Changed in: juju-core Milestone: 1.15.0 => 1.15.1 ** Changed in: juju-core Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210054 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219879] Re: [FFe] juju-core 1.16 for Ubuntu 13.10
1.16 will also fix the local provider, which is broken on saucy with 1.14 due to changes in upstart and lxc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219879 Title: [FFe] juju-core 1.16 for Ubuntu 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1219879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1229275] Re: juju destroy-environment also destroys nodes that are not controlled by juju
** Tags added: maas ** Summary changed: - juju destroy-environment also destroys nodes that are not controlled by juju + [maas] juju destroy-environment also destroys nodes that are not controlled by juju ** Changed in: juju Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1229275 Title: [maas] juju destroy-environment also destroys nodes that are not controlled by juju To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1229275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204302] Re: fails to bootstrap, returns error: no reachable servers
** Changed in: juju-core Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204302 Title: fails to bootstrap, returns error: no reachable servers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1204302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210054] Re: juju terminate-machine with local provider doesn't destroy machine
** Changed in: juju-core Status: Triaged => In Progress ** Changed in: juju-core Assignee: (unassigned) => Tim Penhey (thumper) ** Changed in: juju-core Milestone: None => 1.15.0 ** Branch linked: lp:~thumper/juju-core/lxc-stopping -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210054 Title: juju terminate-machine with local provider doesn't destroy machine To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1210054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210431] [NEW] syslog stops logging when lxc containers autostart
Public bug reported: I noticed that my syslog file was empty, and some cursory googling suggested that it may be libvirt. I had a juju local environment set up which had some containers autostarting. Destroying this environment, and making sure there were no autostart containers, followed by a reboot fixed this problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lxc 0.9.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Fri Aug 9 09:06:45 2013 InstallationDate: Installed on 2012-04-26 (469 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to raring on 2013-02-22 (168 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1210431 Title: syslog stops logging when lxc containers autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1210431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078213] Re: juju-machine-agent.log/logs are not logrotated
** Tags added: logging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: juju-machine-agent.log/logs are not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1078213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1164754] Re: No appearance settings available in System Settings
On 10/04/13 03:01, Brian Murray wrote: > Tim the log files from your upgrade may still be helpful in sorting out > why this did not get installed. Which files do you want to see? $ ll /var/log/dist-upgrade/20130222-1012/ total 436 drwxr-xr-x 2 root root 4096 Feb 22 10:12 ./ drwxr-xr-x 5 root root 4096 Feb 22 13:36 ../ -rw-r--r-- 1 root root 49230 Feb 7 08:53 apt.log -rw-r- 1 root adm 190969 Feb 7 08:53 apt-term.log -rw-r--r-- 1 root root 131242 Feb 7 08:53 history.log -rw-r--r-- 1 root root 52933 Oct 25 19:06 main.log -rw-r--r-- 1 root root 78 Oct 25 19:05 xorg_fixup.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164754 Title: No appearance settings available in System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1164754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1164754] Re: No appearance settings available in System Settings
On 09/04/13 06:02, Brian Murray wrote: > gnome-control-center-unity is part of the following tasks: > > Task: ubuntu-desktop, ubuntu-usb, edubuntu-desktop, edubuntu-usb $ apt-cache policy gnome-control-center-unity gnome-control-center-unity: Installed: (none) Candidate: 1.2daily13.04.01-0ubuntu1 Version table: 1.2daily13.04.01-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages Yep, that is missing $ apt-cache policy ubuntu-desktop ubuntu-desktop: Installed: 1.298 Candidate: 1.298 Version table: *** 1.298 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status So the question becomes, why isn't gnome-control-center-unity installed when I should be brought in by ubuntu-desktop? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164754 Title: No appearance settings available in System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1164754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164753] Re: boots to a black screen with a cursor
Here is the log file. The first time I restarted everything worked as expected. The second time I got the blank screen, so it seems like a race condition somewhere. ** Attachment added: "lightdm.log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164753/+attachment/3622192/+files/lightdm.log ** Changed in: lightdm (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/1164753 Title: boots to a black screen with a cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164755] [NEW] the sync indicator is not showing
Public bug reported: I have indicator-sync installed, and U1 sync is running, but I have no indicator, and no idea why. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-sync 12.10.5daily13.03.28.1-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 Date: Fri Apr 5 11:36:37 2013 InstallationDate: Installed on 2012-04-26 (343 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-sync UpgradeStatus: Upgraded to raring on 2013-02-22 (41 days ago) ** Affects: indicator-sync (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/1164755 Title: the sync indicator is not showing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sync/+bug/1164755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164754] [NEW] No appearance settings available in System Settings
Public bug reported: In quantal I used to have an "Appearance" settings button in the "Personal" section of the System Settings. Since upgrading to raring I have not had one there. It was suggested on IRC that I was missing gnome-backgrounds, which I was, and installed, but it made no difference. I still have no Appearance settings. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-desktop 1.298 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 Date: Fri Apr 5 11:30:09 2013 InstallationDate: Installed on 2012-04-26 (343 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to raring on 2013-02-22 (41 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164754 Title: No appearance settings available in System Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1164754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164753] [NEW] boots to a black screen with a cursor
Public bug reported: After the splash screen on boot, I get taken to a black screen which has an active cursor. I have to switch to tty1 (or another tty) and run the following: sudo service lightdm restart Then I get taken to the lightdm login screen. I'm not sure why it isn't starting properly, happy to help diagnose though. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.5.3-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 Date: Fri Apr 5 11:25:51 2013 InstallationDate: Installed on 2012-04-26 (343 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to raring on 2013-02-22 (41 days ago) ** Affects: lightdm (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/1164753 Title: boots to a black screen with a cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1164753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026088] Re: HUD should support applications using both gmenus and standard gtkmenus
** Changed in: indicator-appmenu (Ubuntu Quantal) Assignee: Tim Penhey (thumper) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026088 Title: HUD should support applications using both gmenus and standard gtkmenus To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1026088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955379] Re: cmake hangs with qemu-arm-static
Peter, if you try to run the cmake file for lp:unity you should hit it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955379 Title: cmake hangs with qemu-arm-static To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/955379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955379] Re: cmake hangs with qemu-arm-static
I am also having this issue with latest qemu on quantal using an armhf chroot. cmake will occasionally finish, but mostly it just hangs, most often in the pkg_check bits. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955379 Title: cmake hangs with qemu-arm-static To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/955379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 750386] Re: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free()
On 18/10/12 08:59, Joey Stanford wrote: > some updates... > > I've attached two valgrind logs. The problem I had though was gnome- > session was grabbing compiz.bin and executing directly when the crashes > occurred so the valgrind logs I do have don't cover that exact case. > However, they do show a bunch of errors. > > I took a video of what's happening currently: > http://socialcam.com/v/SC5Pte9r?type=email > > Now I need to figure out how to stop gnome-session from directly > executing compiz.bin (which is compiz just renamed because compiz is now > a shell script wrapper for valgrind). > > > ** Attachment added: "valgrind logs" > > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/750386/+attachment/3401910/+files/valgrind.tar.gz > what PPAs do you have? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750386 Title: compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/750386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045965] Re: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***
Slightly frustrated there is no stacktrace, I get this every time logging in. Interestingly though, if I switch to a vt and start unity manually, all is fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045965 Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1045965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045965] Re: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***
** Also affects: compiz 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/1045965 Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1045965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045965] Re: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f516ea0fe84 ***
** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045965 Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1045965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1048957] Re: compiz crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048957 Title: compiz crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1048957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055002] Re: compiz crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055002 Title: compiz crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1055002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055049] Re: compiz crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055049 Title: compiz crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1055049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058253] Re: compiz crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058253 Title: compiz crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1058253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059068] Re: compiz crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059068 Title: compiz crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1059068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059847] Re: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x00007f885b958e84 ***
*** This bug is a duplicate of bug 1045965 *** https://bugs.launchpad.net/bugs/1045965 ** This bug is no longer a duplicate of bug 750386 compiz crashed with SIGABRT in raise() from abort() from __libc_message() from malloc_printerr() from _int_free() ** This bug has been marked a duplicate of bug 1045965 compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f516ea0fe84 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059847 Title: compiz assert failure: *** glibc detected *** compiz: free(): invalid pointer: 0x7f885b958e84 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054074] Re: [regression] [Unity 6.6] compiz crashed with SIGSEGV in nux::WindowThread::GetTimerHandler() from nux::NuxTimerTickSource::~NuxTimerTickSource()() from unity::UnityScreen::~UnityScre
** Changed in: nux Status: New => Invalid ** Changed in: nux/3.0 Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054074 Title: [regression] [Unity 6.6] compiz crashed with SIGSEGV in nux::WindowThread::GetTimerHandler() from nux::NuxTimerTickSource::~NuxTimerTickSource()() from unity::UnityScreen::~UnityScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1054074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1043562] Re: [gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000001 IPEHR: 0x60020100
On 20/09/12 21:43, Timo Aaltonen wrote: > sorry, should be 'Option "Accelmethod" "sna"' instead.. This seems to have fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043562 Title: [gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0001 IPEHR: 0x60020100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1043562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824902] Re: alt-down keypress is not passed on to apps
No longer an issue. ** Changed in: unity Status: Confirmed => Invalid ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824902 Title: alt-down keypress is not passed on to apps To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/824902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 606277] Re: Allow dynamic Lens loading
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/606277 Title: Allow dynamic Lens loading To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/606277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 607796] Re: Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/607796 Title: Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627195] Re: Window management - Apps raised from indicators sometimes dont have the focus
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/627195 Title: Window management - Apps raised from indicators sometimes dont have the focus To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/627195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 639633] Re: Design and implement workspace creation and removal
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/639633 Title: Design and implement workspace creation and removal To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/639633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 654988] Re: Unity doesn't mirror its interface for RTL locales.
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/654988 Title: Unity doesn't mirror its interface for RTL locales. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/654988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667545] Re: Dash - rename files in the dash
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667545 Title: Dash - rename files in the dash To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/667545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 670364] Re: compiz / g_main_loop integration test application
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/670364 Title: compiz / g_main_loop integration test application To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/670364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676453] Re: Launcher - Add 'installing' animation for when app is installed via drag & drop
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676453 Title: Launcher - Add 'installing' animation for when app is installed via drag & drop To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/676453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 676579] Re: Launcher - Develop launcher touch interactions
** Tags added: exbacklog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/676579 Title: Launcher - Develop launcher touch interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/676579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
