[Bug 1611287] Re: provide canonical way to install templates and configuration files into $SNAP_* dirs
I think hack is an unnecessarily strong term. In the Cassandra snap, the config is copied into $SNAP_DATA at runtime (if not already present) [1]. Helper programs are provided for getting, setting, and environment variable lookup (for templating) [2]. Having native support for config will bring consistency with other snapped applications, but otherwise this works quite well. 1: https://github.com/evandandrea/cassandra-snap/blob/master/wrapper-cassandra 2: https://lists.ubuntu.com/archives/snapcraft/2016-July/000362.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611287 Title: provide canonical way to install templates and configuration files into $SNAP_* dirs To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1611287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Locally-reproducing package tests
Hi, In building the scalable replacement for package tests, the CI team was careful to ensure that local-reproducibility was maintained. If you would like to quickly iterate on tests, or closely mirror the production environment when debugging, we have provided some instructions: https://wiki.ubuntu.com/ProposedMigration#Reproducing_failures Please note that while this will block much unwarranted traffic, it does not completely replicate the production firewall rules. Only an upload to the archive will be able to tell you with certainty whether your test is free from attempts to access the Internet. Thanks -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
[Bug 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run
This will mean that tests in CI will negligibly skew the results, but I think we can live with that for now. I agree that this is low priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1389357 Title: whoopsie reuses CRASH_DB_IDENTIFIER on next run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1389357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266747] Re: emulator GL translator errors during autopilot tests
I'm also seeing this when running the emulator inside an openstack instance: sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glReadPixels:1610 error 0x500 That happens every time I try to capture the screen using mirscreencast or phablet-screenshot. GL seems to be wired up correctly: ubuntu@ev-testing:~$ xvfb-run --server-args=-screen 0 1024x768x24 +extension GLX glxinfo name of display: :99 display: :99 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.5, 256 bits) OpenGL version string: 3.0 Mesa 10.2.6 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_packed_pixels, GL_APPLE_vertex_array_object, GL_ARB_ES2_compatibility, GL_ARB_blend_func_extended, GL_ARB_clear_buffer_object, GL_ARB_color_buffer_float, GL_ARB_conservative_depth, GL_ARB_copy_buffer, GL_ARB_debug_output, GL_ARB_depth_buffer_float, GL_ARB_depth_clamp, GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_draw_buffers_blend, GL_ARB_draw_elements_base_vertex, GL_ARB_draw_instanced, GL_ARB_explicit_attrib_location, GL_ARB_fragment_coord_conventions, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_get_program_binary, GL_ARB_half_float_pixel, GL_ARB_half_float_vertex, GL_ARB_instanced_arrays, GL_ARB_internalformat_query, GL_ARB_invalidate_subdata, GL_ARB_map_buffer_alignment, GL_ARB_map_buffer_range, GL_ARB_multi_bind, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, GL_ARB_pixel_buffer_object, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_provoking_vertex, GL_ARB_robustness, GL_ARB_sampler_objects, GL_ARB_seamless_cube_map, GL_ARB_separate_shader_objects, GL_ARB_shader_bit_encoding, GL_ARB_shader_objects, GL_ARB_shader_texture_lod, GL_ARB_shading_language_100, GL_ARB_shading_language_420pack, GL_ARB_shading_language_packing, GL_ARB_shadow, GL_ARB_sync, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_compression_rgtc, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_float, GL_ARB_texture_mirror_clamp_to_edge, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_multisample, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_texture_rgb10_a2ui, GL_ARB_texture_storage, GL_ARB_texture_storage_multisample, GL_ARB_texture_swizzle, GL_ARB_timer_query, GL_ARB_transform_feedback2, GL_ARB_transform_feedback3, GL_ARB_transform_feedback_instanced, GL_ARB_transpose_matrix, GL_ARB_uniform_buffer_object, GL_ARB_vertex_array_bgra, GL_ARB_vertex_array_object, GL_ARB_vertex_attrib_binding, GL_ARB_vertex_buffer_object, GL_ARB_vertex_program, GL_ARB_vertex_shader, GL_ARB_vertex_type_10f_11f_11f_rev, GL_ARB_vertex_type_2_10_10_10_rev, GL_ARB_window_pos, GL_ATI_blend_equation_separate, GL_ATI_draw_buffers,
[Bug 1347737] [NEW] Kernel nested kvm support
Public bug reported: Before we go barking up the tree of the Ubuntu Touch emulator on bare metal using MAAS and Juju, I wanted to make sure we tried nested kvm. I heard rumors that this was known not to work well, and sure enough if I run the touch emulator inside an i386 2G RAM trusty instance on Canonistack, I get the occasional kernel panic or OOPS. If it's not something we care to support, that's fine, but getting a statement from the kernel team to this effect would be helpful. Begin: Running /scripts/init-bottom ... done. [9.97] init: ureadahead-touch main process (263) terminated with status 5 [ 46.67] init: /dev/hw_random not found [ 46.67] init: cannot open '/initlogo.rle' [ 47.00] init: /dev/hw_random not found [ 47.85] healthd: wakealarm_init: timerfd_create failed [ 48.22] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' [ 48.22] init: cannot find '/system/bin/ubuntuappmanager.disabled', disabling 'ubuntuappmanager' [ 49.37] Unable to handle kernel paging request at virtual address 8030c164 [ 49.37] pgd = bf9dc000 [ 49.37] [8030c164] *pgd=3fffe801, *pte=0030c0cf, *ppte=0030c21e [ 49.37] Internal error: Oops: 81f [#1] PREEMPT ARM [ 49.37] Modules linked in: [ 49.37] CPU: 0Not tainted (3.4.0-3-goldfish #17-Ubuntu) [ 49.37] PC is at __patch_text+0xc/0x24 [ 49.37] LR is at __jump_label_update+0x3c/0x58 [ 49.37] pc : [80413d0c]lr : [8009c6c4]psr: 80030013 [ 49.37] sp : be97df08 ip : 0900 fp : 001d [ 49.37] r10: 0004 r9 : 0001 r8 : bb875380 [ 49.37] r7 : 0001 r6 : 806217ac r5 : 805e8b7c r4 : 806204c8 [ 49.37] r3 : 8030c164 r2 : 805e8064 r1 : ea5b r0 : 8030c164 [ 49.37] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 49.37] Control: 10c5387d Table: 3f9dc059 DAC: 0015 [ 49.37] [ 49.37] PC: 0x80413c8c: [ 49.37] 3c8c e1a0200d ebf014ca e1a096ad e1a09689 e3a08000 eaefe8b6 e281c01c e5923060 [ 49.37] 3cac e8ac6ff0 ee0d3f70 e3a04000 ee0d4f50 e592700c e59f8020 e59771ec e1a05000 [ 49.37] 3ccc e282401c e59f0014 e3a01002 eb000553 e5887000 e1a5 e894aff0 805e8048 [ 49.37] 3cec 806270ac e320f000 e320f000 e320f000 e320f000 e59f2018 e92d4008 e1a03000 [ 49.37] 3d0c e4831004 e1a01003 e5922010 e12fff32 e8bd8008 805e8064 eaf5 e92d0fff [ 49.37] 3d2c e1ad ebf7 e1a0e000 e8bd0fff e1a0f00e e92d4037 e1a04000 e5903014 [ 49.37] 3d4c e59f20b4 e1530002 3a27 e59f20ac e1530002 3a22 ea23 e593 [ 49.37] 3d6c e1a01004 e28d3000 e5840030 e5a13034 eb0003e6 e351 0a03 3a18 [ 49.37] LR: 0x8009c644: [ 49.37] c644 3a02 93a0 83a1 e12fff1e e3e0 e12fff1e e5903000 e5902004 [ 49.37] c664 e353 e2020001 d3a03000 c3a03001 e1d32002 02233001 0003 13a1 [ 49.37] c684 e12fff1e e92d40f8 e1a05000 e1a04001 e1a06002 e1a07003 ea09 e594 [ 49.37] c6a4 e350 0a05 ebfe745a e350 0a02 e1a4 e1a01007 ebfdd73c [ 49.37] c6c4 e284400c e1540006 28bd80f8 e5943008 e1550003 0af0 e8bd80f8 e92d47f0 [ 49.37] c6e4 e1a05000 e5908004 e1a07001 ebff005a e3a0a00c e3c88001 e5954008 e1a06000 [ 49.37] c704 ea08 e5943008 e1a5 e5941004 e5932138 e5933134 e022329a e1a03007 [ 49.37] c724 ebd7 e5944000 e354 1af4 e356 15962138 13a0100c 15963134 [ 49.37] [ 49.37] SP: 0xbe97de88: [ 49.37] de88 0003 be97df08 76e4b000 800e94e8 800d95e0 bf90b5e8 be97df08 [ 49.37] dea8 80413d0c 80030013 be97def4 80413898 8030c164 ea5b [ 49.37] dec8 805e8064 8030c164 806204c8 805e8b7c 806217ac 0001 bb875380 0001 [ 49.37] dee8 0004 001d 0900 be97df08 8009c6c4 80413d0c 80030013 [ 49.37] df08 806204c8 8009c6c4 0001 805e8b7c 0001 7e973898 8009cb24 [ 49.37] df28 bfb00040 0001 802ffe90 be97df90 800cebc0 0041 c1b6 [ 49.37] df48 805e8a18 802fb078 0002 a1ec60e1 fff7 bb875380 0001 0004 [ 49.37] df68 001d 7e973898 be97c000 76e4b000 802fc4f8 0004 0001 [ 49.37] [ 49.37] R0: 0x8030c0e4: [ 49.37] c0e4 e59c200a e0202002 e1811002 e1d320b0 e1dc30b0 e0223003 e1811003 ea08 [ 49.37] c104 e351 1a06 e5941018 e1a02007 e5950094 e351 05941094 ebfcd253 [ 49.37] c124 e1a01000 e2711001 e5858028 33a01000 e5851024 e5955000 e355 1ad1 [ 49.37] c144 e1a01004 e1a6 ebfff8be e1a01004 e8bd41f0 eaae e92d4037 e1a04000 [ 49.37] c164 e1a0 ea06 e1c420d8 e1921003 1a03 e1ad ebf518a2 e1cd20d0 [ 49.37] c184 e1c420f8 e1a0 ea10 e5153008 e1a01004 e5150004 e12fff33 e4953008 [ 49.37] c1a4 e353 1af8 e1a0200d e3c23d7f
[Bug 1347737] Re: Kernel nested kvm support
+-+-+ | Property| Value | +-+-+ | status | ACTIVE | | updated | 2014-07-23T12:12:07Z | | OS-EXT-STS:task_state | None | | key_name| None | | image | ubuntu-released/ubuntu-trusty-14.04-i386-server-20140607.1-disk1.img (09c2032a-92cf-47a1-8e94-8c91f3675ab8) | | hostId | b06b04e83970a8abe48d9976ba3e5bd6372718da506955357f2bb416 | | OS-EXT-STS:vm_state | active | | flavor | m1.small (2) | | id | 5270c9f6-c07b-46da-af1f-97a53bce9de2 | | security_groups | [{u'name': u'juju-lcy'}, {u'name': u'juju-lcy-0'}] | | user_id | 7a636f4ea1914246a08fc84e60960134 | | name| juju-lcy-machine-0 | | created | 2014-07-23T12:11:52Z | | tenant_id | c0136db8dc454f2d8523d9326bca2d78 | | OS-DCF:diskConfig | MANUAL | | metadata| {} | | accessIPv4 | | | accessIPv6 | | | canonistack network | 10.55.61.111 | | progress| 0 | | OS-EXT-STS:power_state | 1 | | OS-EXT-AZ:availability_zone | nova | | config_drive| | +-+-+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347737 Title: Kernel nested kvm support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347737] Re: Kernel nested kvm support
ubuntu@juju-lcy-machine-0:~$ sudo lshw juju-lcy-machine-0 description: Computer product: OpenStack Nova () vendor: OpenStack Foundation version: 2013.1.5 serial: 33313934-3432-5a43-4339-353037544c37 width: 32 bits capabilities: smbios-2.4 dmi-2.4 smp-1.4 smp configuration: boot=normal cpus=1 uuid=5270C9F6-C07B-46DA-AF1F-97A53BCE9DE2 *-core description: Motherboard physical id: 0 *-firmware description: BIOS vendor: Bochs physical id: 0 version: Bochs date: 01/01/2007 size: 96KiB *-cpu description: CPU product: Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz vendor: Intel Corp. physical id: 401 bus info: cpu@0 version: 6.15.11 serial: -06FB---- slot: CPU 1 size: 2GHz capacity: 2GHz width: 64 bits capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx rdtscp x86-64 constant_tsc pni vmx ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm *-memory description: System Memory physical id: 1000 size: 2GiB capacity: 2GiB *-bank description: DIMM RAM physical id: 0 slot: DIMM 0 size: 2GiB width: 64 bits *-pci description: Host bridge product: 440FX - 82441FX PMC [Natoma] vendor: Intel Corporation physical id: 100 bus info: pci@:00:00.0 version: 02 width: 32 bits clock: 33MHz *-isa description: ISA bridge product: 82371SB PIIX3 ISA [Natoma/Triton II] vendor: Intel Corporation physical id: 1 bus info: pci@:00:01.0 version: 00 width: 32 bits clock: 33MHz capabilities: isa configuration: latency=0 *-ide description: IDE interface product: 82371SB PIIX3 IDE [Natoma/Triton II] vendor: Intel Corporation physical id: 1.1 bus info: pci@:00:01.1 version: 00 width: 32 bits clock: 33MHz capabilities: ide bus_master configuration: driver=ata_piix latency=0 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:c0e0(size=16) *-usb description: USB controller product: 82371SB PIIX3 USB [Natoma/Triton II] vendor: Intel Corporation physical id: 1.2 bus info: pci@:00:01.2 version: 01 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:11 ioport:c080(size=32) *-bridge UNCLAIMED description: Bridge product: 82371AB/EB/MB PIIX4 ACPI vendor: Intel Corporation physical id: 1.3 bus info: pci@:00:01.3 version: 03 width: 32 bits clock: 33MHz capabilities: bridge configuration: latency=0 *-display UNCLAIMED description: VGA compatible controller product: GD 5446 vendor: Cirrus Logic physical id: 2 bus info: pci@:00:02.0 version: 00 width: 32 bits clock: 33MHz capabilities: vga_controller configuration: latency=0 resources: memory:fc00-fdff memory:febf-febf0fff memory:febe-febe *-network description: Ethernet interface product: Virtio network device vendor: Red Hat, Inc physical id: 3 bus info: pci@:00:03.0 logical name: eth0 version: 00 serial: fa:16:3e:9d:ac:93 width: 32 bits clock: 33MHz capabilities: msix bus_master cap_list ethernet physical configuration: broadcast=yes driver=virtio_net driverversion=1.0.0 ip=10.55.61.111 latency=0 link=yes multicast=yes resources: irq:10 ioport:c0a0(size=32) memory:febf1000-febf1fff *-scsi:0 description: SCSI storage controller product: Virtio block device vendor: Red Hat, Inc physical id: 4 bus info: pci@:00:04.0 version: 00 width: 32 bits clock: 33MHz capabilities: scsi msix bus_master cap_list configuration: driver=virtio-pci latency=0 resources: irq:11 ioport:c000(size=64)
[Bug 1347737] Re: Kernel nested kvm support
Chris points out that we're doing armhf on i386. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347737 Title: Kernel nested kvm support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1347737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340604] Re: [phone] crash files are only uploaded on boot
Stellar work, guys. I do find it odd that this is causing whoopsie to sit around doing nothing, given that online_state defaults to true, but let's assume for a minute that dbus is indeed the problem. The upstart job doesn't have any non-runlevel service dependencies, so it could conceivably come up before the system bus is started. Coming up before Network Manager should be okay, thanks to dbus service activation. If we cannot talk to Network Manager, we assume Internet connectivity. This covers the case where NetworkManager or DBus have caught fire. Besides, if we cannot submit a crash file, we'll find out pretty quickly. However, this code was written before whoopsie was running on phones and I now worry we could end up in a situation where we're trying to send lots of large crash files on a 3G or paid connection. As much as it pains me to add runtime dependencies to whoopsie, perhaps we should solve this by putting 'start on started dbus' and 'stop on stopping dbus' in the upstart job. What do you guys think? Brian? Does this fix the bug for you, Paul and Joe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340604 Title: [phone] crash files are only uploaded on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1340604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307215] Re: destroy-environment fails to clear lxc containers
Correct. Attached is a juju-deployer config that reproduces the issue when used with the juju local provider and /var/lib/lxc in the host backed onto btrfs. If you deploy it and run juju destroy-environment --force -y local, it should fail. This is because Ceph sees that /srv/ceph is on btrfs and makes use of it. ubuntu@vagrant-local-machine-1:~$ mount /dev/sda2 on / type btrfs (rw) So you'll end up with lots of snapshots created by Ceph inside LXC. These will be visible by running `btrfs subvolume list /var/lib/lxc` in the host: (.venv-ubuntu)vagrant@vagrant-ubuntu-trusty-64:~$ sudo btrfs subvolume list /var/lib/lxc ID 256 gen 9268 top level 5 path @lxc ID 257 gen 8126 top level 256 path juju-precise-template/rootfs ID 285 gen 8006 top level 256 path juju-trusty-template/rootfs ID 762 gen 9208 top level 256 path vagrant-local-machine-25/rootfs ID 763 gen 9208 top level 256 path vagrant-local-machine-26/rootfs ID 764 gen 9208 top level 256 path vagrant-local-machine-27/rootfs ID 925 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/current ID 934 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/current ID 944 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/current ID 951 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4426 ID 954 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4483 ID 957 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4767 ID 958 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5753 ID 959 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4845 ID 960 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5754 ** Attachment added: object-storage.yaml https://bugs.launchpad.net/juju-core/+bug/1307215/+attachment/4154884/+files/object-storage.yaml -- 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/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+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 1307215] Re: destroy-environment fails to clear lxc containers
Correct. Attached is a juju-deployer config that reproduces the issue when used with the juju local provider and /var/lib/lxc in the host backed onto btrfs. If you deploy it and run juju destroy-environment --force -y local, it should fail. This is because Ceph sees that /srv/ceph is on btrfs and makes use of it. ubuntu@vagrant-local-machine-1:~$ mount /dev/sda2 on / type btrfs (rw) So you'll end up with lots of snapshots created by Ceph inside LXC. These will be visible by running `btrfs subvolume list /var/lib/lxc` in the host: (.venv-ubuntu)vagrant@vagrant-ubuntu-trusty-64:~$ sudo btrfs subvolume list /var/lib/lxc ID 256 gen 9268 top level 5 path @lxc ID 257 gen 8126 top level 256 path juju-precise-template/rootfs ID 285 gen 8006 top level 256 path juju-trusty-template/rootfs ID 762 gen 9208 top level 256 path vagrant-local-machine-25/rootfs ID 763 gen 9208 top level 256 path vagrant-local-machine-26/rootfs ID 764 gen 9208 top level 256 path vagrant-local-machine-27/rootfs ID 925 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/current ID 934 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/current ID 944 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/current ID 951 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4426 ID 954 gen 9208 top level 256 path vagrant-local-machine-26/rootfs/srv/ceph/snap_4483 ID 957 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4767 ID 958 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5753 ID 959 gen 9208 top level 256 path vagrant-local-machine-25/rootfs/srv/ceph/snap_4845 ID 960 gen 9208 top level 256 path vagrant-local-machine-27/rootfs/srv/ceph/snap_5754 ** Attachment added: object-storage.yaml https://bugs.launchpad.net/juju-core/+bug/1307215/+attachment/4154884/+files/object-storage.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307215] Re: destroy-environment fails to clear lxc containers
To further clarify, this isn't a juju bug. lxc should be smart enough to delete dependent subvolumes before it deletes the rootfs subvolume. I took a stab at this over the weekend, but ran out of time. btrfs_destroy(struct bdev *orig) is what you're after. ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- 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/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+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 1307215] Re: destroy-environment fails to clear lxc containers
To further clarify, this isn't a juju bug. lxc should be smart enough to delete dependent subvolumes before it deletes the rootfs subvolume. I took a stab at this over the weekend, but ran out of time. btrfs_destroy(struct bdev *orig) is what you're after. ** Also affects: lxc (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/1307215 Title: destroy-environment fails to clear lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319099] Re: whoopsie-upload-all does not upload RecoverableProblem reports
This is not by design. I don't know why it was written this way (and I don't /think/ I wrote it). We should definitely upload all crash types from the phone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1319099 Title: whoopsie-upload-all does not upload RecoverableProblem reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1319099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1269917] Re: Kernel GPF
** 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/1269917 Title: Kernel GPF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1269917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267774] [NEW] Apport does not handle corrupted crash files in all cases
Public bug reported: When whoopsie-upload-all is run over a partially-written crash file, it dies deep inside apport: https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke- click_image_tests/96/artifact/clientlogs/_usr_share_apport_whoopsie- upload-all.0.crash/*view*/ https://lists.launchpad.net/ubuntu-phone/msg05847.html I think apport should attempt to validate the .crash file before processing it further and raise a single exception that can be dealt with by consuming applications. ** Affects: apport (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/1267774 Title: Apport does not handle corrupted crash files in all cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1267774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261308] Re: Intel ivy bridge crash on a CI machine executing autopilot tests
** Tags added: ci-engineering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261308 Title: Intel ivy bridge crash on a CI machine executing autopilot tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253974] Re: glamor-egl 0.5.1-0ubuntu6 crashes when running autopilot tests
** Tags added: ci-engineering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253974 Title: glamor-egl 0.5.1-0ubuntu6 crashes when running autopilot tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glamor-egl/+bug/1253974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249162] Re: Devices lose adb connection after phablet-flash loop
** Tags added: ci-engineering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249162 Title: Devices lose adb connection after phablet-flash loop To manage notifications about this bug go to: https://bugs.launchpad.net/phablet-tools/+bug/1249162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233613] Re: Adb and mtp priority issue
I'm bumping the priority of this as it affects the CI infrastructure. Oliver, have you had a chance to look into this? ** Changed in: android-tools (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233613 Title: Adb and mtp priority issue To manage notifications about this bug go to: https://bugs.launchpad.net/mtp/+bug/1233613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1233613] Re: Adb and mtp priority issue
** Tags added: ci-engineering -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233613 Title: Adb and mtp priority issue To manage notifications about this bug go to: https://bugs.launchpad.net/mtp/+bug/1233613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Working with the CI team
Hi, You may from time to time need things from the Continuous Integration team. You have a couple of options: 1) For critical issues needing immediate attention, please continue to ask the vanguard in #ci and #ubuntu-ci-eng. 2) For specific issues or needs from our infrastructure, please file a bug here: https://bugs.launchpad.net/ubuntu-ci-services-itself/+filebug Thanks! -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1245524] Re: whoopsie fails to notice/process .crash files on touch images
** Changed in: whoopsie (Ubuntu) Importance: Undecided = Critical ** Changed in: whoopsie (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245524 Title: whoopsie fails to notice/process .crash files on touch images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1245524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235436] Re: /etc/init/apport-noui.conf is non-functional on the phone
** Changed in: apport (Ubuntu) Importance: High = Critical ** Changed in: apport (Ubuntu) Milestone: None = ubuntu-13.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235436 Title: /etc/init/apport-noui.conf is non-functional on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1235436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
[11:52:24] apw ok there are a continuious stream of updates from the kernel [11:52:37] apw becasue link level mappings are in the routing table, and they appear and dissapear [11:52:39] apw all the time [11:53:04] apw try sudo ip monitor [15:12:24] ev so basically this approach is bogus then? [15:13:46] apw well it needs consideration whether it is being selective enough [15:14:14] apw as as a naive user i look at the raw stream it changes whenever an arp entry appears or dissappears [15:14:30] apw now they mey be doing it 'righter' by trying to select specific subsets of [15:14:42] apw the messages, or not, one wuold need to emit the ones they keep/drop to see [15:14:52] apw it is possible they have not adapted to the new world order [15:16:41] ev new world order? [15:19:05] apw when the link level addresses got promoted from another separate cache into the [15:19:13] apw routing table, which sped things up [15:19:53] apw so ipv6 neibour discovery results, and ipv4 arp results get put in as a real 'host route' now [15:20:01] apw and then removed when they time out [15:20:09] apw which might mean things looking for route changes would see both [15:20:22] apw of those, and think networking changed, but you would need to shove a print in there [15:20:24] apw to be sure me thinks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: + Watching GNetworkMonitor's network-changed signal causes constant DNS + traffic. + + Unfortunately, we currently need this because checking NetworkManager's + state for CONNECTED_GLOBAL is not enough to know whether we're really + online since Ubuntu does not yet use the NetworkManager connectivity + check. + + The likely solution to this bug is a replacement for GNetworkMonitor in + whoopsie. + + Original report follows: + Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
** Description changed: Watching GNetworkMonitor's network-changed signal causes constant DNS traffic. Unfortunately, we currently need this because checking NetworkManager's state for CONNECTED_GLOBAL is not enough to know whether we're really online since Ubuntu does not yet use the NetworkManager connectivity - check. + check [1]. The likely solution to this bug is a replacement for GNetworkMonitor in whoopsie. + + 1: http://bazaar.launchpad.net/~daisy- + pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326 Original report follows: Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
** Description changed: Watching GNetworkMonitor's network-changed signal causes constant DNS traffic. - Unfortunately, we currently need this because checking NetworkManager's - state for CONNECTED_GLOBAL is not enough to know whether we're really - online since Ubuntu does not yet use the NetworkManager connectivity - check [1]. + Andy Whitcroft points out that the NETLINK_ROUTE socket set up by + GNetworkMonitor will fire events every time there an ARP entry appears + or disappears. + + Unfortunately, we currently need an additional layer of connectivity + checking because checking NetworkManager's state for CONNECTED_GLOBAL is + not enough to know whether we're really online. Ubuntu does not yet use + the NetworkManager connectivity check [1]. The likely solution to this bug is a replacement for GNetworkMonitor in whoopsie. 1: http://bazaar.launchpad.net/~daisy- pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326 Original report follows: Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com
** Description changed: Watching GNetworkMonitor's network-changed signal causes constant DNS traffic. Andy Whitcroft points out that the NETLINK_ROUTE socket set up by - GNetworkMonitor will fire events every time there an ARP entry appears - or disappears. + GNetworkMonitor will fire events every time an ARP entry appears or + disappears. Unfortunately, we currently need an additional layer of connectivity checking because checking NetworkManager's state for CONNECTED_GLOBAL is not enough to know whether we're really online. Ubuntu does not yet use the NetworkManager connectivity check [1]. The likely solution to this bug is a replacement for GNetworkMonitor in whoopsie. 1: http://bazaar.launchpad.net/~daisy- pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326 Original report follows: Every few seconds, I see a dns query for daisy.ubuntu.com. After removing whoopsie, the traffic goes away. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991481 Title: Constant dns traffic for daisy.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/991481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
** Changed in: touch-preview-images Status: Confirmed = 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/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
** No longer affects: glib2.0 (Ubuntu) ** Changed in: whoopsie Status: Confirmed = 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/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
Fixed in 0.2.23 ** Changed in: whoopsie (Ubuntu) Status: Confirmed = 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/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
Valgrind isn't showing anything particularly relevant. The uninitialised value error is present in all bzr revisions of whoopsie when using this version of libc (2.17-91ubuntu1 - probably earlier ones too as I just upgraded it). ** Attachment added: vgdump.txt https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1211417/+attachment/3772239/+files/vgdump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
We've just landed a new glib. Can you check to see if you have libglib2.0-0 2.37.5-1ubuntu1 installed, and whether downgrading to a version prior fixes the issue? Whoopsie isn't polling fds itself, so I suspect the problem lies a level below. I've been unable to trigger this on a Nexus 4 so far. If anyone has steps to reproduce the problem, I'd welcome them :) ** Changed in: whoopsie (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/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
Also, please attach `grep whoopsie /var/log/syslog` and the resultant /var/crash/*whoopsie*.crash file when you pkill -ABRT whoopsie. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
Alan's crash, retraced. ** Attachment added: whoopsie.crash https://bugs.launchpad.net/whoopsie/+bug/1211417/+attachment/3771116/+files/whoopsie.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
A better stack trace. This definitely looks like a glib problem. I'm still investigating, but I haven't been able to reproduce it since the first couple of times. ** Attachment added: whoopsie2.crash https://bugs.launchpad.net/whoopsie/+bug/1211417/+attachment/3771200/+files/whoopsie2.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1211417] Re: whoopsie takes 100% CPU on the phone
For what it's worth, I've been unable to reproduce this at all on an up- to-date system. That could just be that this is racy, but I would've expected to see it by now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1211417 Title: whoopsie takes 100% CPU on the phone To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210502] [NEW] Not possible to get the IMEI without a SIM
Public bug reported: I have a Nexus 4 (mako) without a SIM card. When I try to ask ofono for the SIM card, I don't get one back: root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-modems [ /ril_0 ] Features = Emergency = 0 Powered = 0 Lockdown = 0 Interfaces = Online = 0 Type = hardware It's definitely not busted though, as I can get it through other means: root@ubuntu-phablet:/# od -j 010 -N 16 -c /dev/mmcblk0p19 010 x x x x 3 6 0 5 8 3 6 x x x x \0 0100020 This is known: [13:16:43] rsalvetiev: it works fine, but you need a sim card atm [13:17:05] ev rsalveti: hmm, why? The IMEI isn't tied to a SIM. [13:17:16] rsalvetiev: I know, bug from our code [13:18:11] rsalvetidon't think we have one yet, we discussed it yesterday, and would need a few changes in ofono as we're not starting the modem if the sim card is not available (our current logic) ** Affects: ofono (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/1210502 Title: Not possible to get the IMEI without a SIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1210502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210502] Re: Not possible to get the IMEI without a SIM
** Description changed: I have a Nexus 4 (mako) without a SIM card. When I try to ask ofono for - the SIM card, I don't get one back: + the IEMI, I don't get one back: root@ubuntu-phablet:/# /usr/share/ofono/scripts/list-modems [ /ril_0 ] - Features = - Emergency = 0 - Powered = 0 - Lockdown = 0 - Interfaces = - Online = 0 - Type = hardware + Features = + Emergency = 0 + Powered = 0 + Lockdown = 0 + Interfaces = + Online = 0 + Type = hardware It's definitely not busted though, as I can get it through other means: root@ubuntu-phablet:/# od -j 010 -N 16 -c /dev/mmcblk0p19 010 x x x x 3 6 0 5 8 3 6 x x x x \0 0100020 This is known: [13:16:43] rsalveti ev: it works fine, but you need a sim card atm [13:17:05] evrsalveti: hmm, why? The IMEI isn't tied to a SIM. [13:17:16] rsalveti ev: I know, bug from our code [13:18:11] rsalveti don't think we have one yet, we discussed it yesterday, and would need a few changes in ofono as we're not starting the modem if the sim card is not available (our current logic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210502 Title: Not possible to get the IMEI without a SIM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1210502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] Re: Only attempts to retry the existing crash reports once, after two hours.
Hi Brian, I can't see why this would happen. Could you do me a favour and run the following in your quantal environment: sudo CRASH_DB_URL=http://localhost: G_DEBUG=fatal-criticals gdb --args whoopsie -f r bt full And attach the output here. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] Re: Only attempts to retry the existing crash reports once, after two hours.
** Description changed: process_existing_files is supposed to fire every two hours. However, because the function doesn't return a boolean value, glib stops processing the two hour timeout event after the first run. TEST CASE: Terminal 1: sudo stop whoopsie - sudo CRASH_DB_URL=http://nowhereville whoopsie -f + sudo CRASH_DB_URL=http://localhost: whoopsie -f Terminal 2: bash -c 'kill -SEGV $$' touch /var/crash/_bin_bash.1000.upload Every two hours there should be an attempt to upload the crash report in Terminal 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] Re: Only attempts to retry the existing crash reports once, after two hours.
** Changed in: whoopsie (Ubuntu Raring) Status: Confirmed = Fix Committed ** Changed in: whoopsie (Ubuntu Quantal) Status: Confirmed = 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/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] Re: Only attempts to retry the existing crash reports once, after two hours.
** Changed in: whoopsie (Ubuntu Precise) Status: Confirmed = Fix Committed ** Description changed: process_existing_files is supposed to fire every two hours. However, because the function doesn't return a boolean value, glib stops processing the two hour timeout event after the first run. + + TEST CASE: + + Terminal 1: + sudo stop whoopsie + sudo CRASH_DB_URL=http://nowhereville whoopsie -f + + Terminal 2: + bash -c 'kill -SEGV $$' + touch /var/crash/_bin_bash.1000.upload + + Every two hours there should be an attempt to upload the crash report in + Terminal 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] [NEW] Only attempts to retry the existing crash reports once, after two hours.
Public bug reported: process_existing_files is supposed to fire every two hours. However, because the function doesn't return a boolean value, glib stops processing the two hour timeout event after the first run. ** Affects: whoopsie (Ubuntu) Importance: Critical Assignee: Evan Dandrea (ev) Status: Fix Committed ** Affects: whoopsie (Ubuntu Precise) Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu Raring) Importance: Undecided Status: New ** Affects: whoopsie (Ubuntu Saucy) Importance: Critical Assignee: Evan Dandrea (ev) Status: Fix Committed ** Changed in: whoopsie (Ubuntu) Importance: Undecided = Critical ** Changed in: whoopsie (Ubuntu) Status: New = Confirmed ** Changed in: whoopsie (Ubuntu) Assignee: (unassigned) = Evan Dandrea (ev) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205374] Re: Only attempts to retry the existing crash reports once, after two hours.
** Also affects: whoopsie (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Saucy) Importance: Critical Assignee: Evan Dandrea (ev) Status: Confirmed ** Also affects: whoopsie (Ubuntu Raring) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Saucy) Status: Confirmed = 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/1205374 Title: Only attempts to retry the existing crash reports once, after two hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1205374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205394] Re: distupgrade fails in saucy because whoopsie-preferences _0.8_amd64.deb is trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-manager-control-c
** Changed in: whoopsie-preferences (Ubuntu) Importance: Undecided = High ** Changed in: whoopsie-preferences (Ubuntu) Assignee: (unassigned) = Evan Dandrea (ev) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205394 Title: distupgrade fails in saucy because whoopsie-preferences _0.8_amd64.deb is trying to overwrite '/usr/bin/whoopsie-preferences', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1205394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203067] Re: [MIR] whoopsie-preferences
I fixed the lintian errors as 0.6: https://launchpad.net/ubuntu/+source/whoopsie-preferences/0.6 ** Changed in: whoopsie-preferences (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/1203067 Title: [MIR] whoopsie-preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1203067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203042] [NEW] Clean up packaging for 0.9.8
Public bug reported: If https://code.launchpad.net/~ev/activity-log-manager/split-out- diagnostics-service/+merge/175820 gets merged, then 01_really_hide_automatic_reports.patch needs its paths changed and we need to drop etc from the install paths. ** Affects: activity-log-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: activity-log-manager_0.9.7-0ubuntu3_0.9.8-0ubuntu1.debdiff https://bugs.launchpad.net/bugs/1203042/+attachment/3742603/+files/activity-log-manager_0.9.7-0ubuntu3_0.9.8-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203042 Title: Clean up packaging for 0.9.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1203042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203042] Re: Clean up packaging for 0.9.8
We also need to depend on whoopsie-preferences :). I'll update the diff. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203042 Title: Clean up packaging for 0.9.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1203042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203067] [NEW] [MIR] whoopsie-preferences
Public bug reported: This is a main inclusion request for whoopsie-preferences, a DBus daemon to control the enabled flag in /etc/default/whoopsie and obtaining the system identifier (either the SHA512 of the system UUID or the MAC address of the first network interface) to form the final part of the URL that displays a system's error reports. This package will be used by activity-log-manager and ubuntu-system- settings. The code previously existed in activity-log-manager, which is already in main, but I've factored it out so that we could use it in ubuntu-system-settings. ~daisy-pluckers maintains it. ** Affects: whoopsie-preferences (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/1203067 Title: [MIR] whoopsie-preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1203067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203042] Re: Clean up packaging for 0.9.8
There's a MIR in progress for whoopsie-preferences here: https://bugs.launchpad.net/ubuntu/+source/whoopsie- preferences/+bug/1203067 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203042 Title: Clean up packaging for 0.9.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1203042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
Seth is correct, though this is only broken in saucy (I've just checked all the other versions). Working on a fix for saucy now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
Argh, so it is. Fixing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
Uploaded the raring-proposed fix as 2.9.2-0ubuntu8.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189253] Re: Upgrade to 0.9.5
This patch works well for me. ** Changed in: activity-log-manager (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189253 Title: Upgrade to 0.9.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1189253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
** Description changed: Kees has looked into setting /proc/sys/fs/setuid_dumpable to 2, which will enable core dumps for setuid binaries. This is now safe in all cases for kernels in raring and later. For quantal and earlier, a core pipe handler must be set when /proc/sys/fs/setuid_dumpable is set to 2. + + TEST CASE: + + passwd + # In another shell + killall -SEGV passwd + ls -la /var/crash/_usr_bin_passwd.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] [NEW] Create core dumps for setuid binaries
Public bug reported: Kees has looked into setting /proc/sys/fs/setuid_dumpable to 2, which will enable core dumps for setuid binaries. This is now safe in all cases for kernels in raring and later. For quantal and earlier, a core pipe handler must be set when /proc/sys/fs/setuid_dumpable is set to 2. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: apport (Ubuntu Precise) Importance: Undecided Status: New ** Affects: apport (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: apport (Ubuntu Raring) Importance: Undecided Status: 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/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
This was uploaded to quantal-proposed as 2.6.1-0ubuntu12. ** Changed in: apport (Ubuntu Quantal) Status: New = 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/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
This was uploaded to precise-proposed as 2.0.1-0ubuntu17.4. ** Changed in: apport (Ubuntu Precise) Status: New = 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/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
This was uploaded to Saucy as 2.10.2-0ubuntu3. ** Also affects: apport (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Raring) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Raring) Status: New = 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/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194541] Re: Create core dumps for setuid binaries
This was uploaded to raring-proposed as 2.9.2-0ubuntu8.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194541 Title: Create core dumps for setuid binaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1194541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: errors.ubuntu.com: mechanism on Server
On 17 June 2013 22:24, Scott Kitterman ubu...@kitterman.com wrote: On Friday, June 07, 2013 11:15:17 AM Evan Dandrea wrote: On 7 June 2013 10:00, Robie Basak robie.ba...@canonical.com wrote: On Thu, Jun 06, 2013 at 04:19:46PM -0400, Scott Kitterman wrote: Of course this should be defaulted to no.Given that the reports to e.u.c are treated as more sensitive than crash reports to Launchpad, it is at best counter-intuitive to expect that sending reports is a reasonable default. Actually, reports to Launchpad are not intended to be treated as any less sensitive. We've just been slow to move access to crash report data in Launchpad bugs over to the NDA. The same concern is there: without an NDA, there's absolutely no recourse to someone doing malicious things with the private data found in those reports, whether they be on errors.ubuntu.com or bugs.launchpad.net. ~ubuntu-bugcontrol was expedient and well-intentioned, but it's a gamble. Perhaps I'm misunderstanding what you're saying, Scott? I don't see how having the contract between our users and the developers wishing to look at that potentially sensitive data, laying out the terms for doing so, makes sending the reports an unreasonable default when compared against not having such an agreement in place. I don't understand why it's required for e.u.c, but no Launchpad. It doesn't make any sense to require it for one and not the other. I explained this above. We have every intention of requiring for access to error reports submitted to Launchpad. https://errors.ubuntu.com was done first because it has mountains more information than Launchpad bugs. I doubt the NDA gives Canonical much in the way of recourse in any case. I'm not sure we let you see bug reports so you can work on fixing our product for free would qualify as consideration sufficient to make the NDA an actual contract (IANAL, so who knows really). A lawyer knows. Seriously, there's no need to idly speculate on this one. It was drafted by myself and Canonical's legal department to give us recourse against those who would use the information in the Error Tracker database for nefarious purposes. Neither myself nor those talented individuals would be wasting our respective time if we didn't think that: A) There is a risk in giving people unencumbered access to a mountain of data that could possibly contain some sensitive information. B) It is therefore acceptable to place restrictions on this access via a legally binding agreement. C) This agreement, if violated, could be leveraged against the guilty party. Also, fixing our product for free? Come on, Scott. This is open source software. Have we ever had a problem with developers not treating crash reports with sufficient care? If not, I wonder why it's worth inhibiting access to useful data in order to solve a problem we aren't having. Should we wait until we do have a problem? I would like to leave the users of Ubuntu with a sense that we're doing everything we feasibly can to take care of the data they've entrusted us with. If a developer wants to remain anonymous and not agree to some fairly simple ground rules, that's their choice, but they will not get access to this potentially sensitive data. It's a more than fair arrangement. You'd also need to check what priority questions debconf is set to ask if you're going to default it to true (which I think is a mistake - I think people interested in contributing will flip the switch, while defaulting to true will cause people who don't care to contribute to have a negative opinion about Ubuntu Server). Depending on how the question priorities are set, your question may never get asked. If you're not fussed, by definition you're not going to take the time to read through a page of text and find a box to tick. If you do care, the heading is going to catch your eye. You'll read it and you'll make your decision. This matches the behaviour we already have in Ubuntu Desktop on millions and millions of machines for well over a year. Honestly, the only complaints I've heard are, can we show these less often and can I please just have it always send? The structure of the debconf question is an implementation detail. We'll make sure this page always gets shown when not preseeding, and that preseeding defaults to no thank you. P.S. Replying to all since apparently not everyone is subscribed to the server list That's fixed now. :) -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: errors.ubuntu.com: support for Server?
On 12 June 2013 22:01, Jorge O. Castro jo...@ubuntu.com wrote: On Fri, Jun 7, 2013 at 5:02 AM, Robie Basak robie.ba...@canonical.com wrote: I'm intimately familiar with preseeding, that being my former life and all, but I'm afraid I don't know what you mean by global level. I take it that's something related to MAAS? What I mean is that MAAS would have an option in its web UI that adjusts this preseed option for everything in one go, rather than the user having to customize preseeds manually. One thing we could also do is making an error submission subordinate charm that we can encourage people to use on their development and testing environments. That way people exploring certain stacks can enable the submissions via an option in the Juju GUI but still run clean in production. I like the idea. Let's work closely with the design team for juju to find the most usable way of exposing the error reporting toggle, then find an implementation to match. Jorge, last we spoke you were going to bring this up with the Juju GUI team. Shall we move this thread over to one of their lists? -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: errors.ubuntu.com: mechanism on Server
On 7 June 2013 10:00, Robie Basak robie.ba...@canonical.com wrote: On Thu, Jun 06, 2013 at 04:19:46PM -0400, Scott Kitterman wrote: Of course this should be defaulted to no.Given that the reports to e.u.c are treated as more sensitive than crash reports to Launchpad, it is at best counter-intuitive to expect that sending reports is a reasonable default. Actually, reports to Launchpad are not intended to be treated as any less sensitive. We've just been slow to move access to crash report data in Launchpad bugs over to the NDA. The same concern is there: without an NDA, there's absolutely no recourse to someone doing malicious things with the private data found in those reports, whether they be on errors.ubuntu.com or bugs.launchpad.net. ~ubuntu-bugcontrol was expedient and well-intentioned, but it's a gamble. Perhaps I'm misunderstanding what you're saying, Scott? I don't see how having the contract between our users and the developers wishing to look at that potentially sensitive data, laying out the terms for doing so, makes sending the reports an unreasonable default when compared against not having such an agreement in place. On Thu, Jun 06, 2013 at 12:44:47PM -0700, Clint Byrum wrote: Turning this on without explicit user authorization would be a breach of confidence in Ubuntu Server. More info: https://wiki.ubuntu.com/ServerTeam That was not suggested. This is not a default without consent. For the interactive case, the user has a section of text explaining the choice in front of them, with the default cursor position being on Yes, I would like to help make Ubuntu better by submitting error reports. This does not turn on something behind the backs of users who wouldn't want it, but it does make less work for the vast majority who would find the notion of Ubuntu getting better as result of sending a small amount of data a worthy proposition. Now, Alex makes a really good point: On 6 June 2013 20:01, Alex Muntada al...@alexm.org wrote: Though i understand that enabling it by default the number of reports will be much bigger, i'd prefer a more conservative approach and set the default to No. Even if one can set that value via preseed, it's difficult to make so unless one's aware of its existence first. And providing that many server installations are unattended nowadays, i see that the Yes default could raise many concerns about the privacy of the reports. We should definitely not do this. If the value is not preseeded, it should not default to true. We have not explained to those people what they'd be agreeing to. However, I believe it still makes sense to have the default action within an interactive d-i session to be yes. All of this is achievable in the debconf protocol. The error reporting system is nothing new. We have an excellent track record in being protective of the data submitted to this system from lots of desktop systems, giving data access only to those who can sign a legally-binding agreement to not misuse it, provide us with real world contact details, and demonstrate a valid use for their access. Abusers can and will be prosecuted, but we know our development community; these are good people. There have already been well documented cases of serious issues being discovered by https://errors.ubuntu.com that would've never been uncovered using the old developer-centric opt-in approach of apport reporting into Launchpad bugs. It is not a stretch to say there's a strong connection between the variety of reports we get and our further understanding of what the most important issues in Ubuntu are. On the desktop, we already present exactly this kind of question that's being proposed for d-i, with the default being to agree to send. To date, none of the owners of the millions of systems reporting into errors.ubuntu.com have burned my house down. So is it realistic to think when presented with an option of yes, I would like to make Ubuntu better (given I'm kind of relying on it for my computer to function) and no thanks, the negative response is the more likely choice? I think we're doing our users a disservice by being so pessimistic, assuming they're uninterested in participating in making the best operating system we can. Thanks for listening. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: errors.ubuntu.com: support for Server?
On 24 May 2013 17:20, Robie Basak robie.ba...@canonical.com wrote: On Thu, May 16, 2013 at 07:01:54AM -0700, Evan Dandrea wrote: What I mean is that data does not get uploaded without the user knowing about it. So in my terms, error reporting on the desktop _is_ opt-in. In the Desktop case, the user knows about it when the error reporting dialog pops up. In the Server case, this is more difficult to achieve, since there is not necessarily any UI available to prompt the user after an error. Ah, thank you for clarifying. I'd prefer that we kept with the existing model of not asking questions, as this has been core to the redesign of apport and the development of the error tracker. OK, but we do effectively ask a single question on the desktop, right? We do. By not asking questions I mean not asking any questions beyond what is absolutely necessary. So yes, at some point we need to ask for their consent in sending all error reports, with each one, or even some combination of both – saying no to automatic error reporting could still notify you via motd that you have reports to manually process. What I do not think we should do is ask questions beyond that. Historically they've been confusing to our audience, but more importantly they reduce the likelihood that someone will respond. It's extra work, and they might not have the time for it. There are better ways. We can use scale to our advantage and given a report that's missing some critical detail we didn't anticipate, programmatically tell the next reporter's system to attach additional information. This involves no additional human interaction and is theoretically as fast as a few seconds as opposed to the usual Launchpad bug response time of days or weeks, if ever. 2) Any extra bit of work you put between a user and submitting an error report will cause some of those users to not send the report. They'll be hesitant to send subsequent reports if the process was previously onerous. Agreed - we need to make sure that the UX is as simple as possible. Great! Production server operators may want to vet reports before agreeing to send them, so an interactive CLI like aa-logprof(8) or apport-cli(1) that allows users to see exactly what they are submitting would be useful. So essentially a CLI equivalent of the GUI error reporting dialog. The documentation for apport discusses one possible approach: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/README#L51 The problem I have with this is that it's a very manual step. I'm not convinced many people who would otherwise be okay with automatic reporting will actually notice the message and follow through. It also delays our knowing the frequency of serious issues by relying on server administrators to log in and process the reports. Could this be reasonable as one fallback position for those who ask d-i to turn off automatic uploads, or if we choose not to follow that path? Yes, I think unless the user explicitly disables the collection of reports (disabling apport in /etc/default/apport), we should still tell them what it's doing and how they can further process the results. So I would be very happy in taking that .bashrc chunk from apport and putting it in motd as a first step. So where do we go from here? It seems that we have two proposals: 0) I presume that with both proposals we have the option of choosing different defaults between stable and development releases? Yes, though do keep in mind that if we restrict ourselves to just development releases we are going to miss out on problems that would only crop up post-release. We've had serious ones with each new release of the desktop OS. 1) A d-i prompt asking about error reporting. Outcome: automatic uploads of error reports, or not. I understand that you want this to default to automatic uploads, and your reasons. Yes please. 2) The bash prompt modification at [1] by default. Yes please. :) For MAAS, I presume that we could make the d-i preseed configurable at a global level. I'm intimately familiar with preseeding, that being my former life and all, but I'm afraid I don't know what you mean by global level. I take it that's something related to MAAS? I'm not sure about juju without MAAS. Perhaps a configuration parameter for the environment could feed cloud-init? That's vaguely what I was thinking. Either using constraints or kindly requesting that a new environments.yaml option be added to represent error reporting. The benefit of the latter is that's it's more discoverable, even if disabled by default. We could automatically populate it into environments.yaml with a comment explaining what it does and asking them to help make Ubuntu better by turning it on. We should ask them directly though, perhaps as a separate discussion to this one. Thanks! -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
Re: errors.ubuntu.com: mechanism on Server
Sounds good to me :). Thanks Robie! -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
Re: errors.ubuntu.com: benefits on Server?
Hi Robie, On 6 June 2013 11:38, Robie Basak robie.ba...@canonical.com wrote: I thought I'd split this thread into two. One question is about what benefits error reporting on Server might bring, and that's what I'd like to discuss here. [Daviey] Just need to work out, *if* it is worth doing... Is it worth doing? What sorts of errors will we pick up on right now? Do these errors happen in the real world? With us diverting effort to this, are we going to neglect some category of errors that we currently won't pick up this way? Some categories of errors come to mind: I would be careful in extrapolating based off what you get right now from Launchpad bugs. This wont just produce the same set of issues in greater numbers. When you introduce post-release reporting and remove the barriers to sending reports (no SSO, no forms), you get a much broader view of what's out there. I honestly don't know if it's worth doing, but fortunately that's not entirely my call to make. I also don't think we'll know until we try. 1) Segfaults leading to core dumps. I don't see many bug reports of these at all. We do get the occasional excellent bug report though. My feeling is that segfaults on server are actually quite rare. You probably don't see reports of these because any process that drops privileges does not produce a core dump. I really want to turn this on, making the reports owned by root. Kees sounded okay with it about a year ago and was going to look into it (/proc/sys/kernel/setuid_dumpable to 2), but I don't think he ever found the time. I can bring this back up with the security team. 2) Maintainer script failures. We get lots of these reports. Most of them are due to local misconfiguration or sysadmin error in a way that I don't think it's possible or reasonable for us to fix. This is because most use cases of server packages involve sysadmin configuration file editing. Perhaps this can be fixed at a higher layer (eg. charms being careful to not introduce these kinds of errors). I think these reports aren't useful individually for this reason, but may be useful in aggregate to identify real bugs. So it seems to me that error reporting for these would be really useful. We've had some difficulty finding a good way of bucketing these together, so that you see them in aggregate. Martin, Brian, and I sat down at the client sprint and came up with what I hope is a better solution: https://lists.ubuntu.com/archives/raring-changes/2013-June/010150.html 3) Perhaps daemon start failures that aren't from maintainer script failures? This is subject to the same sysadmin misconfiguration problem above though; I'm not sure how useful this would be. What other kinds of errors will we initially pick up on? What categories have I missed, or does anyone disagree with my analysis above? Recoverable problems. We created /usr/share/apport/recoverable_problem for applications that can handle an exception, but would still like to know that it occurred. Often, this may be that the exception was handled but the experience is degraded as a result, so on the desktop is produces a popup as well. All developers have to do is feed it nul-separated key-value pairs over stdin, ensuring they provide a DuplicateSignature field. Right now it works off the ppid, but I believe Ted Gould was patching it to support the pid to trace being passed in. You could patch applications to use this, as Ted is doing with glib. -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
[Bug 958543] Re: ubiquity does not complete the installation
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958543 Title: ubiquity does not complete the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/958543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189486] [NEW] /usr/bin/gnome-shell:6:g_assertion_message:g_assertion_message_cmpnum:g_object_notify_by_pspec:clutter_actor_set_child_at_index:clutter_actor_has_overlaps
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/gnome- shell:6:g_assertion_message:g_assertion_message_cmpnum:g_object_notify_by_pspec:clutter_actor_set_child_at_index:clutter_actor_has_overlaps ** Affects: gnome-shell (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/1189486 Title: /usr/bin/gnome- shell:6:g_assertion_message:g_assertion_message_cmpnum:g_object_notify_by_pspec:clutter_actor_set_child_at_index:clutter_actor_has_overlaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1189486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1188881] [NEW] /usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun ** Affects: jackd2 (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/111 Title: /usr/bin/jackd:8:__udivdi3:Jack::JackFrameTimer::ResetFrameTime:Jack::JackEngineControl::NotifyXRun:Jack::JackEngine::NotifyXRun:Jack::JackDriver::NotifyXRun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1187146] [NEW] /usr/bin/xrandr-tool:TypeError:/usr/bin/xrandr-tool@82
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/xrandr- tool:TypeError:/usr/bin/xrandr-tool@82 ** Affects: xdiagnose (Ubuntu) Importance: Undecided Status: New ** Tags: raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187146 Title: /usr/bin/xrandr-tool:TypeError:/usr/bin/xrandr-tool@82 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdiagnose/+bug/1187146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186645] [NEW] /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:fill_contact_info_grid:request_contact_info_cb:g_simple_async_result_complete
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:fill_contact_info_grid:request_contact_info_cb:g_simple_async_result_complete ** Affects: gnome-control-center (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/1186645 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:fill_contact_info_grid:request_contact_info_cb:g_simple_async_result_complete To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1186645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186647] [NEW] /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186647 Title: /usr/bin/nautilus:6:g_assertion_message:g_assertion_message_expr:nautilus_bookmark_connect_file:nautilus_bookmark_connect_file:g_object_newv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1186647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Opening up errors.ubuntu.com
Happy Friday! https://errors.ubuntu.com provides us with a detailed view of the most pressing problems in Ubuntu. At a glance you can see what issues are going to give the greatest return and get detailed information to fix them. This helps us increase the stability of Ubuntu and, crucially, measure our progress. Up until now, most developers could not see past the front page, where detailed information about the problems and data on the instances of these problems live. Today we have a solution – Developers and QA analysts can now request access to the error data by filling out this short form: https://forms.canonical.com/reports/ === So, what can this thing do for me? === By logging in, the front page will switch to a view of the most common problems in the past day that are relevant to you: https://errors.ubuntu.com/?user=evperiod=day You can add additional packages to this list by clicking on Edit bug mail on any Ubuntu source package page, and adding a subscription: https://bugs.launchpad.net/ubuntu/+source/apport/+subscriptions The problem pages provide you with a graph of the rate of occurrences, the version-by-version and release-by-release breakdown, the Python traceback or binary stacktrace, and a table of links to the individual instances of the problem: https://errors.ubuntu.com/problem/f6435fc405ba7b68eae0ea2706a904f50cb77869 Let's say you released a new version of jockey, and want to see there are any problems in it that did not exist in previous versions. The API will give you this information (beta): https://errors.ubuntu.com/api/1.0/package-version-new-buckets/?package=jockeyprevious_version=0.9.7-0ubuntu7.7new_version=0.9.7-0ubuntu7.8format=json === Why all the process? === A non-disclosure agreement lets us take legal action on behalf of Ubuntu users against anyone abusing access to the error reports. Signing the agreement with your own personal details tells them you intend to respect the sensitivity of any personal information they have provided us. If you are responsible for fixing problems in Ubuntu software, I encourage you to sign up and explore. We'll do our best to ensure that you get access quickly, but please feel free to contact me personally if you have any trouble. === Further assistance === If you want to help make the Ubuntu Error Tracker better, please visit https://wiki.ubuntu.com/ErrorTracker. If you find a bug, please file it at https://launchpad.net/errors/+filebug. If you need a hand getting started, I can also be found on the Freenode IRC network as 'ev' in #ubuntu-devel. Thanks, and have a great weekend! -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
[Bug 1186388] [NEW] Crash due to Cairo-Pinguin: infinite loop in on_build_container_menu
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/cairo- dock:11:on_build_container_menu:on_build_container_menu:on_build_container_menu:on_build_container_menu:on_build_container_menu ** Affects: cairo-dock-plug-ins (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/1186388 Title: Crash due to Cairo-Pinguin: infinite loop in on_build_container_menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1186388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186419] [NEW] /usr/bin/gnome-control-center:11:get_graphics_data_glx_renderer:get_graphics_data:cc_info_panel_init:g_type_create_instance:g_object_constructor
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/gnome-control- center:11:get_graphics_data_glx_renderer:get_graphics_data:cc_info_panel_init:g_type_create_instance:g_object_constructor ** Affects: gnome-control-center (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/1186419 Title: /usr/bin/gnome-control- center:11:get_graphics_data_glx_renderer:get_graphics_data:cc_info_panel_init:g_type_create_instance:g_object_constructor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1186419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989819] Re: the signatures match code should probably consider the exception for python errors
** Changed in: daisy Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/989819 Title: the signatures match code should probably consider the exception for python errors To manage notifications about this bug go to: https://bugs.launchpad.net/daisy/+bug/989819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 944756] Re: Shows unpleasant Cannot connect to crash database instead of queuing for later
** Changed in: apport (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/944756 Title: Shows unpleasant Cannot connect to crash database instead of queuing for later To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/944756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 892386] Re: No shortcut available for forward button for Chinese during installation / oem-config
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/892386 Title: No shortcut available for forward button for Chinese during installation / oem-config To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/892386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775124] Re: Ubiquity should have a command line option to override the free space check
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: ubiquity (Ubuntu Oneiric) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: ubiquity (Ubuntu Precise) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775124 Title: Ubiquity should have a command line option to override the free space check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/775124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 754275] Re: Time zones map is wrong
** Changed in: libtimezonemap (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/754275 Title: Time zones map is wrong To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/754275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658865] Re: Install from USB fails: An attempt to configure apt to install additional packages from the CD failed
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658865 Title: Install from USB fails: An attempt to configure apt to install additional packages from the CD failed To manage notifications about this bug go to: https://bugs.launchpad.net/estobuntu/+bug/658865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 419194] Re: We have hardly any data on why people cancel installations
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/419194 Title: We have hardly any data on why people cancel installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/419194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 645818] Re: Unknown keyword in configuration file: gfxboot
** Changed in: usb-creator (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: usb-creator (Ubuntu Natty) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: usb-creator (Ubuntu Precise) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: usb-creator (Ubuntu Maverick) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: usb-creator (Ubuntu Oneiric) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/645818 Title: Unknown keyword in configuration file: gfxboot To manage notifications about this bug go to: https://bugs.launchpad.net/usb-creator/+bug/645818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 751666] Re: Restricted plugins selected at install didn't install
** Changed in: ubiquity (Ubuntu Natty) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) ** Changed in: ubiquity (Ubuntu Precise) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/751666 Title: Restricted plugins selected at install didn't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/751666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155115] Re: Apport gets stuck and sucks CPU
Easily confirmed by running the crash file through apport-cli on quantal. ** Changed in: apport (Ubuntu) Importance: Undecided = High ** Changed in: apport (Ubuntu) Status: New = Triaged ** Changed in: apport (Ubuntu) Assignee: (unassigned) = Evan Dandrea (ev) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155115 Title: Apport gets stuck and sucks CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1155115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155115] Re: Apport gets stuck and sucks CPU
** Changed in: apport (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155115 Title: Apport gets stuck and sucks CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1155115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 398614] Re: XStartupError: X server exited with return code 1
** Changed in: ubiquity (Ubuntu) Assignee: Evan Dandrea (ev) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/398614 Title: XStartupError: X server exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/398614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155115] Re: Apport gets stuck and sucks CPU
Ah, it just finished, after taking some significant amount of time: *** Invalid problem report This problem report applies to a program which is not installed any more. (/usr/bin/gwibber-service) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155115 Title: Apport gets stuck and sucks CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1155115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155115] Re: Apport gets stuck and sucks CPU
And it's probably worth noting that I actually processed that using the Raring version of apport, 2.9.2-0ubuntu8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155115 Title: Apport gets stuck and sucks CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1155115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177994] Re: Kernel Oops - Out of the blue segfault TogglDesktop - RIP at mem_cgroup_charge_statistics.isra.28+0x9/0x50
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: errors 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/1177994 Title: Kernel Oops - Out of the blue segfault TogglDesktop - RIP at mem_cgroup_charge_statistics.isra.28+0x9/0x50 To manage notifications about this bug go to: https://bugs.launchpad.net/errors/+bug/1177994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: errors.ubuntu.com: support for Server?
Hi Robie, Thanks for kicking off this discussion. On Thu, May 16, 2013 at 12:10 AM, Robie Basak robie.ba...@canonical.com wrote: that will cause us to misinterpret the results? Is there any need to categorise the reports at submission time (eg. perhaps ask the reporter a question)? I'd prefer that we kept with the existing model of not asking questions, as this has been core to the redesign of apport and the development of the error tracker. Two points on this: 1) We have been historically quite bad at understanding our audience when programmatically communicating with them. Thanks for reporting this bug. It seems you have unity running. Is the issue you are reporting is related to unity itself rather than compiz? What's Unity? What's Compiz? Even if I know what both of those are, how on Earth do I know which one is responsible for my bug? I'm just going to close this thing because I don't know what the correct answer is. 2) Any extra bit of work you put between a user and submitting an error report will cause some of those users to not send the report. They'll be hesitant to send subsequent reports if the process was previously onerous. What should the UX be? How should we protect privacy and avoid reports inadvertently being submitted by users who do not wish to submit them? Should we have different UX defaults between the development and production releases? If the system is opt-in (which I assume it will be), will we have enough users opting in for the system to be useful? Why do you assume an opt-in system? Error reporting on the desktop is not opt-in, and for good reason: our data would be heavily skewed to the types of people who already know that the error reporting functionality exists, can find the toggle to turn it on, and are so passionate about providing error data that they do turn it on. On the desktop, this is handled by a checkbox that's ticked by default with the heading: Send an error report to help fix this problem. I think we should find a solution with that balance in mind. I've suggested in the past that we do this at installation time with the default option being to enable error reporting. So in the case of debian-installer, a d-i component that asks whether you want to disable error reporting. In the case of juju and maas, I'm not sure. Some implmentation ideas: Production server operators may want to vet reports before agreeing to send them, so an interactive CLI like aa-logprof(8) or apport-cli(1) that allows users to see exactly what they are submitting would be useful. So essentially a CLI equivalent of the GUI error reporting dialog. The documentation for apport discusses one possible approach: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/README#L51 The problem I have with this is that it's a very manual step. I'm not convinced many people who would otherwise be okay with automatic reporting will actually notice the message and follow through. It also delays our knowing the frequency of serious issues by relying on server administrators to log in and process the reports. Or perhaps some kind of remote ssh enhancement to the existing GUI error reporting dialog, so users get the same UI on a desktop machine that connects to a server machine, picks up the crash reports there generates and sends reports via the local GUI? That assumes they're running Ubuntu everywhere. It's presumably confusing as you're suddenly getting error reports out of the blue. We've been bitten hard by this with the system internal error reports that pop up, confusing users who thought they hadn't actually done anything. But most importantly, it's extra work for the end-users to get going. Lets make the barrier to sending these reports as low as possible. An update-motd enhancement to notify server operators that crash reports are pending. This could provide the command to type to enter the interactive CLI to submit them and a reference to a manpage with more details on how to turn off local crash report collection. A bash prompt enhancement present only during development, which prompts users with a shorter version of the motd prompt. Or would this be too intrusive? I thought of it because I imagine users not logging in much to test servers, and so might not see the motd prompt (I rarely see the motd prompt when I test, since I use ssh shared connections and short-lived cloud instances). Other thoughts: Right now I feel that the information we get from users about Server quality is poor. As always, some bug reports are awesome, are from competent submitters, and highlight real problems which we need to fix. But many bugs filed appear to be automatic and in response to postinst failures due to local misconfigurations. I think this overrepresents the set of users who are experimenting and underrepresents the users who are using Server in production. I'm not sure we get any other real feedback about quality right now,
[Bug 1179853] [NEW] /usr/bin/pulseaudio:6:raise:abort:pa_hook_done:pa_bluetooth_discovery_unref:module_bluetooth_device_LTX_pa__done
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/bin/pulseaudio:6:raise:abort:pa_hook_done:pa_bluetooth_discovery_unref:module_bluetooth_device_LTX_pa__done ** Affects: pulseaudio (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/1179853 Title: /usr/bin/pulseaudio:6:raise:abort:pa_hook_done:pa_bluetooth_discovery_unref:module_bluetooth_device_LTX_pa__done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1179853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173249] [NEW] /usr/share/software-center/update-software-center:AttributeError:/usr/sbin/update-software-center@170:rebuild_database:get_pkg_info:/usr/share/software-center/softwarecenter/db/pkg
Public bug reported: During upgrade from Ubuntu 12.10 to Ubuntu 13.04, this can happen when update-software-center is run by triggers: Traceback (most recent call last): File /usr/sbin/update-software-center, line 170, in module result = rebuild_database(pathname) File /usr/share/software-center/softwarecenter/db/update.py, line 1108, in rebuild_database cache = get_pkg_info() File /usr/share/software-center/softwarecenter/db/pkginfo.py, line 240, in get_pkg_info from softwarecenter.db.pkginfo_impl.aptcache import AptCache File /usr/share/software-center/softwarecenter/db/pkginfo_impl/aptcache.py, line 30, in module from aptdaemon.client import AptClient File /usr/lib/python2.7/dist-packages/aptdaemon/client.py, line 70, in module class MemoizedMixInMeta(MemoizedTransaction, GObject.GObjectMeta): File /usr/lib/python2.7/dist-packages/gi/module.py, line 316, in __getattr__ return getattr(self._introspection_module, name) File /usr/lib/python2.7/dist-packages/gi/module.py, line 135, in __getattr__ self.__name__, name)) AttributeError: 'gi.repository.GObject' object has no attribute 'GObjectMeta' ** Affects: aptdaemon (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: pygobject (Ubuntu) Importance: Undecided Status: Triaged ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Affects: aptdaemon (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: pygobject (Ubuntu Quantal) Importance: Undecided Status: Invalid ** Affects: software-center (Ubuntu Quantal) Importance: Undecided Status: New ** Affects: aptdaemon (Ubuntu Raring) Importance: Undecided Status: Fix Released ** Affects: pygobject (Ubuntu Raring) Importance: Undecided Assignee: Iain Lane (laney) Status: Triaged ** Affects: software-center (Ubuntu Raring) Importance: Undecided Status: New ** Affects: aptdaemon (Ubuntu Saucy) Importance: Undecided Status: Fix Released ** Affects: pygobject (Ubuntu Saucy) Importance: Undecided Status: Triaged ** Affects: software-center (Ubuntu Saucy) 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/1173249 Title: /usr/share/software-center/update-software- center:AttributeError:/usr/sbin/update-software- center@170:rebuild_database:get_pkg_info:/usr/share/software- center/softwarecenter/db/pkginfo_impl/aptcache.py@30:/usr/lib/python2.7 /dist-packages/aptdaemon/client.py@70:__getattr__:__getattr__ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1173249/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172840] [NEW] /usr/lib/ubuntu-release-upgrader/check-new-release-gtk:gi._glib.GError:on_button_upgrade_now_clicked:__init__:__init__:function
Public bug reported: https://errors.ubuntu.com/bucket/?id=/usr/lib/ubuntu-release-upgrader /check-new-release- gtk:gi._glib.GError:on_button_upgrade_now_clicked:__init__:__init__:function ** Affects: ubuntu-release-upgrader (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/1172840 Title: /usr/lib/ubuntu-release-upgrader/check-new-release- gtk:gi._glib.GError:on_button_upgrade_now_clicked:__init__:__init__:function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1172840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172840] Re: /usr/lib/ubuntu-release-upgrader/check-new-release-gtk:gi._glib.GError:on_button_upgrade_now_clicked:__init__:__init__:function
*** This bug is a duplicate of bug 1094777 *** https://bugs.launchpad.net/bugs/1094777 ** This bug has been marked a duplicate of bug 1094777 Can't use c-n-r-gtk to initiate Quantal - Raring update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172840 Title: /usr/lib/ubuntu-release-upgrader/check-new-release- gtk:gi._glib.GError:on_button_upgrade_now_clicked:__init__:__init__:function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1172840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Intention to drop Wubi from 13.04 release
On Fri, Apr 19, 2013 at 2:38 PM, Dmitrijs Ledkovs dmitrij.led...@ubuntu.com wrote: I have pinged Evan, to publish a release and request the wubi.exe builds for Precise and Raring be signed such that we can release them. I am not sure how long the delay is but hopefully we will be able to release wubi for precise raring soon. http://people.canonical.com/~evand/wubi/precise/stable http://people.canonical.com/~evand/wubi/raring/stable We'll need signed copies, as you point out. Let me know if you want me to file an RT for that. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Coverity static analysis for C, C++ and Java code
A big +1 to this. Coverity has found a few interesting bugs in whoopsie that our other tools missed. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel