[Bug 1390223] Re: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel
smtp and qmgr suffer similar denials: kernel: [33252.627322] audit: type=1400 audit(1434961302.532:240): apparmor=DENIED operation=file_perm profile=lxc-container-default name=private/trace pid=11752 comm=qmgr requested_mask=r denied_mask=r fsuid=100104 ouid=0 kernel: [33252.626415] audit: type=1400 audit(1434961302.532:238): apparmor=DENIED operation=file_perm profile=lxc-container-default name=private/defer pid=3 comm=smtp requested_mask=r -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390223 Title: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1390223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
I think Tim is taking care of this - unsubscribing the main Ubuntu sponsors but add us back if necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
I tried rebuilding gnome-settings-daemon from the ppa sources, but deleted all the debian/patches files. then restarted gnome-settings- daemon and gnome-shell, but still had the same problem with keyboard shortcuts not working I did the same thing, but no luck. Maybe we have to rebuilt other packages without Debian related patches as well? Any hints or suggestions are appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467595] [NEW] cursor sometimes disappears on XPS 13 9343 and external monitor
Public bug reported: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor disappears (sometimes after screen lock, other times just normal usage). I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:19:40 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid ** Description changed: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. Occasionally, the mouse cursor - disappears. I saw something on stack exchange that said this might help: + disappears (sometimes after screen lock, other times just normal usage). + I saw something on stack exchange that said this might help: gsettings set org.gnome.settings-daemon.plugins.cursor active false I've done this and it sometimes helps and sometimes doesn't. I've also just seen the cursor come back on its own after a few minutes without doing anything. Trying to interact with the touch screen, then the mouse has no effect. Unplugging and replugging the mouse has no effect. Using the touchpad has no effect. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: - + ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins:
[Bug 1422131] Re: The export tool not remember the export path/filename
*** This bug is a duplicate of bug 1153829 *** https://bugs.launchpad.net/bugs/1153829 Linking as duplicate to bug #1153829 - the regression AFAICT effects both a) objects which had not been exported before (no export hints stored at all),as well as b) objects which already have an export-filename stored (which does not get updated as expected with 0.91) Feel free to add a comment here (bug #1422131) and to revert the duplicate status if you disagree. ** This bug has been marked a duplicate of bug 1153829 Export selection - won't remember last used file name -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422131 Title: The export tool not remember the export path/filename To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1422131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296364] Re: [browser] No option for deleting cache
** Description changed: The only way to do this is by deleting the respective files in /home/phablet/.local/share/webbrowser-app/. - -- SOLUTION -- Clearing the cache will be available from the settings screen, once this is implemented. https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00 + + [UX Comment] + Setting is present but a 'Clear Cache' confirmation dialogue required, as described here: + https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296364 Title: [browser] No option for deleting cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1296364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440438] Re: Mobile Broadband in Ubuntu GNOME 15.04
My mobile broadband also does not work. It is not visible. It used to work on 14.04 on the same Dell E7440. Sim card is build in, so not in a USB stick. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440438 Title: Mobile Broadband in Ubuntu GNOME 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1440438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467611] [NEW] unprivileged lxc containers broken
Public bug reported: Seems like I've hit the bug #1413927 but as requested in comments I'm filing new one. lxc-start -n asterisk -l debug -F --logfile /dev/stdout lxc-start 1434992414.067 INFO lxc_start_ui - lxc_start.c:main:264 - using rcfile /home/x/.local/share/lxc/asterisk/config lxc-start 1434992414.067 INFO lxc_utils - utils.c:get_rundir:483 - XDG_RUNTIME_DIR isn't set in the environment. lxc-start 1434992414.067 WARN lxc_confile - confile.c:config_pivotdir:1768 - lxc.pivotdir is ignored. It will soon become an error. lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type u nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 INFO lxc_confile - confile.c:config_idmap:1376 - read uid map: type g nsid 0 hostid 10 range 65536 lxc-start 1434992414.069 WARN lxc_log - log.c:lxc_log_init:316 - lxc_log_init called with log already initialized lxc-start 1434992414.075 WARN lxc_cgmanager - cgmanager.c:cgm_get:963 - do_cgm_get exited with error lxc-start 1434992414.076 WARN lxc_start - start.c:lxc_check_inherited:224 - inherited fd 7 lxc-start 1434992414.076 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - LSM security driver AppArmor lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .reject_force_umount # comment this to allow umount -f; not recommended. lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for reject_force_umount action 0 lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:parse_config_v2:438 - Adding non-compat rule bc nr1 == nr2 (-1, -1) lxc-start 1434992414.076 INFO lxc_seccomp - seccomp.c:do_resolve_add_rule:210 - Setting seccomp rule to reject force umounts lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .[all]. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .kexec_load errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for kexec_load action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (283, 246) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .open_by_handle_at errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for open_by_handle_at action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (342, 304) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .init_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for init_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (128, 175) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .finit_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for finit_module action 327681 lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (350, 313) lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:316 - processing: .delete_module errno 1. lxc-start 1434992414.077 INFO lxc_seccomp - seccomp.c:parse_config_v2:419 - Adding non-compat rule for delete_module action 327681 lxc-start 1434992414.078 INFO lxc_seccomp - seccomp.c:parse_config_v2:430 - Adding compat rule for delete_module action 327681 lxc-start 1434992414.078 INFO lxc_seccomp - seccomp.c:parse_config_v2:443 - Really adding compat rule bc nr1 == nr2 (129, 176)
[Bug 1452200] Re: suggested patches for lpfc driver for 15.04 SRU
Hi Brian, Any update on these patch set inclusion ? Thanks, Nikhith. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452200 Title: suggested patches for lpfc driver for 15.04 SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466938] Re: linux-lts-trusty: 3.13.0-57.95~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466938 Title: linux-lts-trusty: 3.13.0-57.95~precise1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413927] Re: user lxc containers fail to start under systemd: login name=systemd cgroup is not owned by user
I've made separate Bug #1467611 as requested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413927 Title: user lxc containers fail to start under systemd: login name=systemd cgroup is not owned by user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1413927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467542] Re: Add new userspace package 'opal-prd'
** Attachment added: skiboot_5.0.4-0ubuntu1.debian.tar.xz https://bugs.launchpad.net/ubuntu/+bug/1467542/+attachment/4418642/+files/skiboot_5.0.4-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467542 Title: Add new userspace package 'opal-prd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1467542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467542] Re: Add new userspace package 'opal-prd'
** Attachment added: skiboot_5.0.4-0ubuntu1.dsc https://bugs.launchpad.net/ubuntu/+bug/1467542/+attachment/4418641/+files/skiboot_5.0.4-0ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467542 Title: Add new userspace package 'opal-prd' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1467542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447834] Re: curtin doesn't support arm64-efi targets
** Description changed: - We need to add support to curtin for supporting UEFI-based ARM64 - systems. + [Impact] + Curtin doesn't support UEFI-based ARM64 systems. + + [Test Case] + Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS incorporating this MP: +https://code.launchpad.net/~newell-jensen/maas/uefi-arm64/+merge/260639 + + [Regression Risk] + 2/3 of the curtin changes are preventing code that was running on all aarch64 platforms to just running on non-UEFI aarch64 systems. Since we only supported non-UEFI systems before, that should be a low risk of regression. + + The only other change is adding the grub target name for arm64, which is + also pretty straightforward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447834 Title: curtin doesn't support arm64-efi targets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1447834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263181] Re: curtin discovers HP /dev/cciss/c0d0 incorrectly
** Description changed: + === Begin SRU Template === + + [Description] + Installing to an HP DL385, or any other system that has drives in a HP Smart Array will fail, showing: + lsblk: /dev/cciss!c0d0: not a block device + + This is due to curtin's fairly innocent understanding of device name + paths. + + The fix is both + - better parsing of /sys to get information on device names and partitions that are on them. + - specific handling of the very odd named '!ccis' devices. + + [Impact] + Installation via curtin can not be done on these systems. + + [Test Case] + Positive test case: + Install via maas and curtin onto a system with a HP Smart Array. + Successful installation and boot is success anything else is failure. + + Negative test case: + Install on a sytem without these devices and expect it to boot. + + [Regression Potential] + Curtin's understanding of /dev/ and /sys generally improved. However, there are possibly still corner cases. + It seems unlikely that anything that worked before would fail with these changes. + + [Other] + Related bugs: + * bug 1401190 : curtin makes assumptions about partition names on all devices + === End SRU Template === + Trying the MaaS fast-installer against an HP DL385, it fails to run one of the scripts with: lsblk: /dev/cciss!c0d0: not a block device This looks to be due to the way the device is reported to lsblk: lsblk --noheadings --bytes --pairs --out=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID --nodeps ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE= GROUP=root KNAME=cciss!c0d0 LABEL= LOG-SEC=512 MAJ:MIN=104:0 MIN-IO=512 MODE= MODEL=LOGICAL VOLUME MOUNTPOINT= NAME=cciss!c0d0 OPT-IO=0 OWNER=root PHY-SEC=512 RM=0 RO=0 ROTA=1 RQ-SIZE=128 SIZE=440432713728 STATE= TYPE=disk UUID= ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE= GROUP=cdrom KNAME=sr0 LABEL= LOG-SEC=512 MAJ:MIN=11:0 MIN-IO=512 MODE=brw-rw MODEL=CD-ROM TS-L162C MOUNTPOINT= NAME=sr0 OPT-IO=0 OWNER=root PHY-SEC=512 RM=1 RO=0 ROTA=1 RQ-SIZE=128 SIZE=1073741312 STATE=running TYPE=rom UUID= ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE=ext4 GROUP=disk KNAME=sda LABEL=cloudimg-rootfs LOG-SEC=512 MAJ:MIN=8:0 MIN-IO=512 MODE=brw-rw MODEL=VIRTUAL-DISK MOUNTPOINT=/media/root-ro NAME=sda OPT-IO=0 OWNER=root PHY-SEC=512 RM=0 RO=1 ROTA=1 RQ-SIZE=128 SIZE=1476395008 STATE=running TYPE=disk UUID=35938370-3a39-42a9-bf68-7ce0a75e4316 The device name should be /dev/cciss/c0d0 so I guess the device name parsing needs special treatment for HP cciss devices. Related bugs: - * bug 1401190 : curtin makes assumptions about partition names on all devices + * bug 1401190 : curtin makes assumptions about partition names on all devices -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1263181 Title: curtin discovers HP /dev/cciss/c0d0 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1263181/+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 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
I am experiencing network issues with my Dell 12 Gen system as well. My issues are with ssh. I have not tested for Toan's bug. Anyhow, every time I connect via ssh I get random Connection reset by peer errors. I have tried all the suggestion and fixes mention in this Bug report, but nothing seems to make the network connection stable or operational. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331513 Title: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1331513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720
I forgot to mention, I don't experience this bug using CentOS only Ubuntu and other Debian based distribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331513 Title: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1331513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467588] [NEW] Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:17035): GLib-
Public bug reported: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jun 22 16:56:16 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1854] InstallationDate: Installed on 2015-06-02 (20 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash SourcePackage: unity UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: dmi.bios.date: 06/13/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.3A dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3400HTV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088F130059160 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 15:28:27 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 845 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467588 Title: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1467588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466575] Re: linux: 3.2.0-87.125 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466575 Title: linux: 3.2.0-87.125 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463663] Re: [SRU] Enable setting property of type UTF8_STRING
Hello Alkis, or anyone else affected, Accepted x11-utils into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/x11-utils/7.6+4ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463663 Title: [SRU] Enable setting property of type UTF8_STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1463663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467604] [NEW] overlay scrollbar handle doesn't reveal itself on XPS 13 9343 with HiDPI
Public bug reported: I have a new Dell XPS 13 9343 with the HiDPI touch screen and am using an external display port monitor. This issue is present with or without the external monitor. While I can see the overlay scrollbars, if I hover the mouse over them, the handle does not pop up so I am unable to grab them and scroll. The only workaround I've found is to disable the overlay scrollbars in /etc/environment: LIBOVERLAY_SCROLLBAR=0 https://code.launchpad.net/~brandontschaefer/overlay-scrollbar/hidpi- support/+merge/214283 seems like it might be related, but I'm on 15.04 and the overlay scrollbars don't work correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 22 11:42:12 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-20-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0665] InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 10:53:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5153 vendor SHP xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467604 Title: overlay scrollbar handle doesn't reveal itself on XPS 13 9343 with HiDPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1467604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467611] Re: unprivileged lxc containers broken
That happens on x86_64 ubuntu 15.04 server btw. All the latest updates installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467611 Title: unprivileged lxc containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466855] Re: linux-ti-omap4: 3.2.0-1467.88 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466855 Title: linux-ti-omap4: 3.2.0-1467.88 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
This bug was fixed in the package python-tx-tftp - 0.1~bzr38-0ubuntu4 --- python-tx-tftp (0.1~bzr38-0ubuntu4) wily; urgency=medium * debian/patches/05_lp1317705.patch: Regonise error code 8, which is used to terminate a transfer due to option negotiation. See RFC 2347, TFTP Option Extension. (LP: #1317705) -- Andres Rodriguez andres...@ubuntu.com Mon, 22 Jun 2015 12:33:26 -0400 ** Changed in: python-tx-tftp (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+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 1351151] Re: [browser] Implement auto-suggest for the address bar
** Changed in: ubuntu-ux Status: Fix Committed = 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/1351151 Title: [browser] Implement auto-suggest for the address bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401190] Re: curtin makes assumptions about partition names on all devices
** Description changed: + == Begin SRU Template == + [Description] + Installing to a system with a NVM Express card/block device will fail, showing something to the effect of: + Could not stat /dev/nvme0n11 --- No such file or directory + + This is due to curtin's fairly innocent understanding of device name + paths. + + The fix is both + - better parsing of /sys to get information on device names and partitions that are on them. + - specific handling of the very odd named '!ccis' devices. + + [Impact] + Installation via curtin can not be done on these systems. + + [Test Case] + Positive test case: + Install via maas and curtin onto a system with a NVM Express card/block device. + Successful installation and boot is success anything else is failure. + + Negative test case: + Install on a sytem without these devices and expect it to boot. + + [Regression Potential] + Curtin's understanding of /dev/ and /sys generally improved. However, there are possibly still corner cases. + It seems unlikely that anything that worked before would fail with these changes. + + [Other] + Related bugs: + * bug 1263181: curtin discovers HP /dev/cciss/c0d0 incorrectly + == End SRU Template == + + When I do a curtin install via maas to some fancy flash hardware, i get: no partition found /dev/nvme0n11 Could not stat /dev/nvme0n11 --- No such file or directory The device apparently does not exist; did you specify it correctly? Unexpected error while running command. Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/nvme0n11'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'simple'] Exit code: 3 Reason: - Stdout: no partition found /dev/nvme0n11\nCould not stat /dev/nvme0n11 --- No such file or directory\n\nThe device apparently does not exist; did you specify it correctly?\nUnexpected error while running command.\nCommand: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/nvme0n11']\nExit code: 1\nReason: -\nStdout: ''\nStderr: ''\n Stderr: '' smoser: what i think is happening is this a.) curtin chooses nvme0n1 as the device to install on b.) curtin partitions nvme0n1 c.) curtin tries to mkfs on nvme0n11 (appending a '1' to the device name) when actually the name is 'nvme0n1p1' probably. device names are stupidly inconsistently named. and curtin is admittedly very stupid in its assumptions too This patch fixes it (for me, for this device): http://paste.ubuntu.com/9355100/ Related bugs: - * bug 1263181 : curtin discovers HP /dev/cciss/c0d0 incorrectly + * bug 1263181 : curtin discovers HP /dev/cciss/c0d0 incorrectly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1401190 Title: curtin makes assumptions about partition names on all devices To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1401190/+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 1401190] Re: curtin makes assumptions about partition names on all devices
** Description changed: + == Begin SRU Template == + [Description] + Installing to a system with a NVM Express card/block device will fail, showing something to the effect of: + Could not stat /dev/nvme0n11 --- No such file or directory + + This is due to curtin's fairly innocent understanding of device name + paths. + + The fix is both + - better parsing of /sys to get information on device names and partitions that are on them. + - specific handling of the very odd named '!ccis' devices. + + [Impact] + Installation via curtin can not be done on these systems. + + [Test Case] + Positive test case: + Install via maas and curtin onto a system with a NVM Express card/block device. + Successful installation and boot is success anything else is failure. + + Negative test case: + Install on a sytem without these devices and expect it to boot. + + [Regression Potential] + Curtin's understanding of /dev/ and /sys generally improved. However, there are possibly still corner cases. + It seems unlikely that anything that worked before would fail with these changes. + + [Other] + Related bugs: + * bug 1263181: curtin discovers HP /dev/cciss/c0d0 incorrectly + == End SRU Template == + + When I do a curtin install via maas to some fancy flash hardware, i get: no partition found /dev/nvme0n11 Could not stat /dev/nvme0n11 --- No such file or directory The device apparently does not exist; did you specify it correctly? Unexpected error while running command. Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/nvme0n11'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'simple'] Exit code: 3 Reason: - Stdout: no partition found /dev/nvme0n11\nCould not stat /dev/nvme0n11 --- No such file or directory\n\nThe device apparently does not exist; did you specify it correctly?\nUnexpected error while running command.\nCommand: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/nvme0n11']\nExit code: 1\nReason: -\nStdout: ''\nStderr: ''\n Stderr: '' smoser: what i think is happening is this a.) curtin chooses nvme0n1 as the device to install on b.) curtin partitions nvme0n1 c.) curtin tries to mkfs on nvme0n11 (appending a '1' to the device name) when actually the name is 'nvme0n1p1' probably. device names are stupidly inconsistently named. and curtin is admittedly very stupid in its assumptions too This patch fixes it (for me, for this device): http://paste.ubuntu.com/9355100/ Related bugs: - * bug 1263181 : curtin discovers HP /dev/cciss/c0d0 incorrectly + * bug 1263181 : curtin discovers HP /dev/cciss/c0d0 incorrectly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401190 Title: curtin makes assumptions about partition names on all devices To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1401190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466521] Re: ubuntu-mate-artwork 0.4.9 new nelease [debdiff attached]
This bug was fixed in the package ubuntu-mate-artwork - 0.4.9 --- ubuntu-mate-artwork (0.4.9) wily; urgency=medium [ Martin Wimpress ] * Add ubuntu-mate-wallpaper-common package. * Add ubuntu-mate-wallpaper-complete package. * Add community contributed wallpapers from David Chadderton. * Add community contributed wallpaper from João Pedro Coli. * Add missging files to debian/copyright. * Improve GTK3 progress bar color blending. * Align with ubuntu-themes 14.04+15.10.20150603.1-0ubuntu1. * Closes (LP: #1466521) [ Lars Uebernickel ] * Set :link color * Style under- and overshoot -- Martin Wimpress c...@flexion.org Thu, 18 June 2015 12:54:43 + ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466521 Title: ubuntu-mate-artwork 0.4.9 new nelease [debdiff attached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1466521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443542] Re: curtin race on vivid when /dev/sda1 doesn't exist
** Description changed: + === Begin SRU Template === + [Description] + Installation fails, with log information showing: + + Unexpected error while running command. + Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1'] + Exit code: 1 + Reason: - + Stdout: '' + Stderr: '' + Installation failed with exception: Unexpected error while running command. + Command: ['curtin', 'block-meta', 'simple'] + + This is a result of curtin having done: + a.) partition the disk + b.) invoke wipefs on the block device with an offset to where the partition started + + The intent of that was to ensure that there were no fileystem signatures + or other interesting metadata (lvm, raid) on the partition. + + The issue was two fold: + a.) wipefs always invokes rereadpt on the disk it wipes + b.) wipefs opened the block device, not the partition. + + Both of these things cause a flurry of udev events that may result in + the device having an open filehandle, and thus mkfs refusing to create a + filesystem on it. + + The solution is to replace 'wipefs' with our own 'wipe_partition' that + does not open the block device, but rather only the partition and does + not invoke rereadpt. + + [Impact] + Installation fails occasionally. + + [Test Case] + In the original bug-opener's environment it fails fairly reliably under heavy host load using vmware. He would do a deploy to several guests on the same host at the same time and this would reproduce. Unfortunately I was unable to come up with a test case in a less complex environment. + + [Regression Potential] + Not specifically a regression, but it is possible that we need additional 'udevadm settle' after the internal 'wipe_partition' + + === End SRU Template === + The file /dev/sda1 does not exist and no size was specified. Unexpected error while running command. Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'simple'] Exit code: 3 Reason: - Stdout: bThe file /dev/sda1 does not exist and no size was specified.\nUnexpected error while running command.\nCommand: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1']\nExit code: 1\nReason: -\nStdout: ''\nStderr: ''\n Stderr: '' This happened 4 out of 10 times when Ryan tested it. Could this be a race condition because /dev/sda1 hasn't had time to come into existence between when curtin partitions the disk and when curtin tries to create a filesystem on the partition? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1443542 Title: curtin race on vivid when /dev/sda1 doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1443542/+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 1402723] Re: [browser] No visual cue in the chrome after accepting a certificate error
** Changed in: ubuntu-ux Status: Fix Committed = 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/1402723 Title: [browser] No visual cue in the chrome after accepting a certificate error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1402723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1429013] Re: Inkscape crash when undo document changes
Not reproduced on Xubuntu 15.04 (64bit), with Inkscape 0.91-3ubuntu1 and Windows XP, Inkscape 0.91 and trunk rev. 14206. Can you give detailed steps to reproduce with the attached example file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1429013 Title: Inkscape crash when undo document changes To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1429013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351165] Re: [browser] Enable swipe gesture to delete a bookmark from the new tab view
** Changed in: ubuntu-ux Status: Fix Committed = 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/1351165 Title: [browser] Enable swipe gesture to delete a bookmark from the new tab view To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1365179] Re: [Browser] Top bar should overlay the page, not anchoring on top of it
** Changed in: ubuntu-ux Status: Fix Committed = 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/1365179 Title: [Browser] Top bar should overlay the page, not anchoring on top of it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1365179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665932] Re: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds
I agree with eddie-dunn that a UUID 29581fa0-3814-11e4-a7d0-0002a5d5c51b not found would help. Another thing would be to being able to disable uswsusp completely simply by editing files... Could we get info on that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665932 Title: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/665932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454253] Re: external usb breaks suspend
Ok, I've managed to track this down to bios setting regarding keep feeding electrivity to usb ports while in sleep. So apparently this is some quirk related to failed efi firmware or acpi tables for asus ux31a laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1454253 Title: external usb breaks suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1454253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466856] Re: linux-armadaxp: 3.2.0-1653.74 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466856 Title: linux-armadaxp: 3.2.0-1653.74 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467614] [NEW] package kdenlive (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7
Public bug reported: Tried using ppa-purge program to remove ppa:sunab/kdenlive-svn, and received this error while the terminal was executing action. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: kdenlive (not installed) ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Mon Jun 22 10:04:43 2015 DpkgTerminalLog: Preparing to unpack .../kdenlive_0.9.10-2ubuntu1_amd64.deb ... Unpacking kdenlive (0.9.10-2ubuntu1) over (15.04.0+git20150419.66e7120a-0ubuntu0~sunab~vivid1) ... dpkg: error processing archive /var/cache/apt/archives/kdenlive_0.9.10-2ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7120a-0ubuntu0~sunab~vivid1 DuplicateSignature: package:kdenlive:(not installed):trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7120a-0ubuntu0~sunab~vivid1 ErrorMessage: trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7120a-0ubuntu0~sunab~vivid1 InstallationDate: Installed on 2015-06-17 (5 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: kdenlive Title: package kdenlive (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7120a-0ubuntu0~sunab~vivid1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdenlive (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467614 Title: package kdenlive (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man1/kdenlive.1.gz', which is also in package kdenlive-data 15.04.0+git20150419.66e7120a- 0ubuntu0~sunab~vivid1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1467614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263181] Re: curtin discovers HP /dev/cciss/c0d0 incorrectly
** Description changed: + === Begin SRU Template === + + [Description] + Installing to an HP DL385, or any other system that has drives in a HP Smart Array will fail, showing: + lsblk: /dev/cciss!c0d0: not a block device + + This is due to curtin's fairly innocent understanding of device name + paths. + + The fix is both + - better parsing of /sys to get information on device names and partitions that are on them. + - specific handling of the very odd named '!ccis' devices. + + [Impact] + Installation via curtin can not be done on these systems. + + [Test Case] + Positive test case: + Install via maas and curtin onto a system with a HP Smart Array. + Successful installation and boot is success anything else is failure. + + Negative test case: + Install on a sytem without these devices and expect it to boot. + + [Regression Potential] + Curtin's understanding of /dev/ and /sys generally improved. However, there are possibly still corner cases. + It seems unlikely that anything that worked before would fail with these changes. + + [Other] + Related bugs: + * bug 1401190 : curtin makes assumptions about partition names on all devices + === End SRU Template === + Trying the MaaS fast-installer against an HP DL385, it fails to run one of the scripts with: lsblk: /dev/cciss!c0d0: not a block device This looks to be due to the way the device is reported to lsblk: lsblk --noheadings --bytes --pairs --out=ALIGNMENT,DISC-ALN,DISC-GRAN,DISC-MAX,DISC-ZERO,FSTYPE,GROUP,KNAME,LABEL,LOG-SEC,MAJ:MIN,MIN-IO,MODE,MODEL,MOUNTPOINT,NAME,OPT-IO,OWNER,PHY-SEC,RM,RO,ROTA,RQ-SIZE,SIZE,STATE,TYPE,UUID --nodeps ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE= GROUP=root KNAME=cciss!c0d0 LABEL= LOG-SEC=512 MAJ:MIN=104:0 MIN-IO=512 MODE= MODEL=LOGICAL VOLUME MOUNTPOINT= NAME=cciss!c0d0 OPT-IO=0 OWNER=root PHY-SEC=512 RM=0 RO=0 ROTA=1 RQ-SIZE=128 SIZE=440432713728 STATE= TYPE=disk UUID= ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE= GROUP=cdrom KNAME=sr0 LABEL= LOG-SEC=512 MAJ:MIN=11:0 MIN-IO=512 MODE=brw-rw MODEL=CD-ROM TS-L162C MOUNTPOINT= NAME=sr0 OPT-IO=0 OWNER=root PHY-SEC=512 RM=1 RO=0 ROTA=1 RQ-SIZE=128 SIZE=1073741312 STATE=running TYPE=rom UUID= ALIGNMENT=0 DISC-ALN=0 DISC-GRAN=0 DISC-MAX=0 DISC-ZERO=0 FSTYPE=ext4 GROUP=disk KNAME=sda LABEL=cloudimg-rootfs LOG-SEC=512 MAJ:MIN=8:0 MIN-IO=512 MODE=brw-rw MODEL=VIRTUAL-DISK MOUNTPOINT=/media/root-ro NAME=sda OPT-IO=0 OWNER=root PHY-SEC=512 RM=0 RO=1 ROTA=1 RQ-SIZE=128 SIZE=1476395008 STATE=running TYPE=disk UUID=35938370-3a39-42a9-bf68-7ce0a75e4316 The device name should be /dev/cciss/c0d0 so I guess the device name parsing needs special treatment for HP cciss devices. Related bugs: - * bug 1401190 : curtin makes assumptions about partition names on all devices + * bug 1401190 : curtin makes assumptions about partition names on all devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263181 Title: curtin discovers HP /dev/cciss/c0d0 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1263181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303688] Re: SRU bug-fix microrelease 2.0.8.1 in Trusty
OK I made up a package and I've uploaded it. If accepted you'll get a message to test it with further instructions - please follow them. ** Changed in: lyx (Ubuntu) Status: Triaged = Fix Released ** Also affects: lyx (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lyx (Ubuntu Trusty) Status: New = In Progress ** Changed in: lyx (Ubuntu Trusty) Assignee: (unassigned) = Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303688 Title: SRU bug-fix microrelease 2.0.8.1 in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lyx/+bug/1303688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466938] Re: linux-lts-trusty: 3.13.0-57.95~precise1 -proposed tracker
All builds are complete, packages in this bug can be copied to -proposed. ** Changed in: kernel-sru-workflow/prepare-package Status: New = Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) = Luis Henriques (henrix) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New = Confirmed ** Changed in: kernel-sru-workflow/package-testing Status: New = Confirmed ** Description changed: This bug is for tracking the 3.13.0-57.95~precise1 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 19. June 2015 17:03 UTC - kernel-stable-phase:Prepare - kernel-stable-phase-changed:Friday, 19. June 2015 17:03 UTC kernel-stable-master-bug:1466592 + kernel-stable-phase:CopyToProposed + kernel-stable-Prepare-package-end:Monday, 22. June 2015 17:01 UTC + kernel-stable-Promote-to-proposed-start:Monday, 22. June 2015 17:01 UTC + kernel-stable-phase-changed:Monday, 22. June 2015 17:01 UTC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466938 Title: linux-lts-trusty: 3.13.0-57.95~precise1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466937] Re: linux-keystone: 3.13.0-32.49 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-32.49 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 19. June 2015 17:01 UTC kernel-stable-master-bug:1466592 kernel-stable-Certification-testing-end:Monday, 22. June 2015 01:01 UTC kernel-stable-Security-signoff-end:Monday, 22. June 2015 01:01 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Monday, 22. June 2015 06:01 UTC kernel-stable-Promote-to-proposed-start:Monday, 22. June 2015 06:01 UTC kernel-stable-phase-changed:Monday, 22. June 2015 06:01 UTC + kernel-stable-Promote-to-proposed-end:Monday, 22. June 2015 17:32 UTC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466937 Title: linux-keystone: 3.13.0-32.49 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466592] Re: linux: 3.13.0-57.95 -proposed tracker
** Description changed: This bug is for tracking the 3.13.0-57.95 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Thursday, 18. June 2015 17:21 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Friday, 19. June 2015 17:04 UTC kernel-stable-Promote-to-proposed-start:Friday, 19. June 2015 17:04 UTC kernel-stable-phase-changed:Friday, 19. June 2015 17:04 UTC + kernel-stable-Promote-to-proposed-end:Monday, 22. June 2015 17:31 UTC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466592 Title: linux: 3.13.0-57.95 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466792] Re: linux: 3.16.0-43.58 -proposed tracker
** Description changed: This bug is for tracking the 3.16.0-43.58 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-stable-Prepare-package-start:Friday, 19. June 2015 09:34 UTC kernel-stable-phase:CopyToProposed kernel-stable-Prepare-package-end:Friday, 19. June 2015 20:03 UTC kernel-stable-Promote-to-proposed-start:Friday, 19. June 2015 20:03 UTC kernel-stable-phase-changed:Friday, 19. June 2015 20:03 UTC + kernel-stable-Promote-to-proposed-end:Monday, 22. June 2015 17:31 UTC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466792 Title: linux: 3.16.0-43.58 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448180] Re: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone
Any updates on this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448180 Title: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443542] Re: curtin race on vivid when /dev/sda1 doesn't exist
** Description changed: + === Begin SRU Template === + [Description] + Installation fails, with log information showing: + + Unexpected error while running command. + Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1'] + Exit code: 1 + Reason: - + Stdout: '' + Stderr: '' + Installation failed with exception: Unexpected error while running command. + Command: ['curtin', 'block-meta', 'simple'] + + This is a result of curtin having done: + a.) partition the disk + b.) invoke wipefs on the block device with an offset to where the partition started + + The intent of that was to ensure that there were no fileystem signatures + or other interesting metadata (lvm, raid) on the partition. + + The issue was two fold: + a.) wipefs always invokes rereadpt on the disk it wipes + b.) wipefs opened the block device, not the partition. + + Both of these things cause a flurry of udev events that may result in + the device having an open filehandle, and thus mkfs refusing to create a + filesystem on it. + + The solution is to replace 'wipefs' with our own 'wipe_partition' that + does not open the block device, but rather only the partition and does + not invoke rereadpt. + + [Impact] + Installation fails occasionally. + + [Test Case] + In the original bug-opener's environment it fails fairly reliably under heavy host load using vmware. He would do a deploy to several guests on the same host at the same time and this would reproduce. Unfortunately I was unable to come up with a test case in a less complex environment. + + [Regression Potential] + Not specifically a regression, but it is possible that we need additional 'udevadm settle' after the internal 'wipe_partition' + + === End SRU Template === + The file /dev/sda1 does not exist and no size was specified. Unexpected error while running command. Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'simple'] Exit code: 3 Reason: - Stdout: bThe file /dev/sda1 does not exist and no size was specified.\nUnexpected error while running command.\nCommand: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1']\nExit code: 1\nReason: -\nStdout: ''\nStderr: ''\n Stderr: '' This happened 4 out of 10 times when Ryan tested it. Could this be a race condition because /dev/sda1 hasn't had time to come into existence between when curtin partitions the disk and when curtin tries to create a filesystem on the partition? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443542 Title: curtin race on vivid when /dev/sda1 doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1443542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1433900] Re: STC830: pNV is reporting DASD FRU and PN swapped
** Branch linked: lp:debian/iprutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1433900 Title: STC830: pNV is reporting DASD FRU and PN swapped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iprutils/+bug/1433900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464742] Re: Fix FTBFS due to renamed click package on ubuntu
Thanks Johan, I've uploaded this now. ** Changed in: python-snuggs (Ubuntu) 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/1464742 Title: Fix FTBFS due to renamed click package on ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-snuggs/+bug/1464742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466047] Re: Install in UEFI mode installs grub-pc
And here's the screen with the warning message. I pressed continue which the text implies to me will continue with UEFI install. ** Attachment added: GUEFI3.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418696/+files/GUEFI3.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466047 Title: Install in UEFI mode installs grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412732] Re: [browser] visuals for multi-select mode in history view need update
** Description changed: Multi-select mode in the history view was implemented as part of bug #1351167. But the visuals do not match the visual spec exactly. Spec: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 Screenshot: https://launchpadlibrarian.net/195323251/browser- multiselect.png In particular, padding and spacing need to be adjusted. The buttons at the top should have a label, too. + + [UX Comment] + All appears correct other than a back chevron () being shown for cancel instead of the cancel icon (X) + + See: + https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412732 Title: [browser] visuals for multi-select mode in history view need update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1412732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465322] Re: regression: df: `/sys/kernel/debug': Function not implemented with 3.2.0-85.122
Agesp: In response to your question about whether or not this impacts
other software, I can tell you that it affects our Ruby on Rails app in
production. I'm not sure what is triggering it -- it may be IRB, rails,
or a gem that we have, but there is a constant stream of these messages
on stderr when the rails console ('rails c') is loaded:
deploy@ip-10-0-0-41:/var/www/current$ rails c
Loading production environment (Rails 4.1.10)
20150622025515(production) df: `/sys/kernel/debug': Function not implemented
df: `/sys/kernel/debug': Function not implemented
df: `/sys/kernel/debug': Function not implemented
df: `/sys/kernel/debug': Function not implemented
...
I get a message every few seconds without any user interaction.
Obviously there is a simple workaround here -- 'rails c 2/dev/null`.
But it would be nice to have stderr back at some point. :)
Thanks,
Andy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465322
Title:
regression: df: `/sys/kernel/debug': Function not implemented with
3.2.0-85.122
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463663] Re: [SRU] Enable setting property of type UTF8_STRING
** Branch linked: lp:ubuntu/precise-proposed/x11-utils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463663 Title: [SRU] Enable setting property of type UTF8_STRING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1463663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
** Branch linked: lp:ubuntu/wily-proposed/python-tx-tftp -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+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 1466592] Re: linux: 3.13.0-57.95 -proposed tracker
Promoted to proposed: linux| 3.13.0-57.95 | trusty-proposed | source linux-meta | 3.13.0.57.64 | trusty-proposed | source linux-signed | 3.13.0-57.95 | trusty-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed 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/1466592 Title: linux: 3.13.0-57.95 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467616] [NEW] problem report each time I log in
Public bug reported: , my netbook is aod270 and this problem first showed up when I tried to install some drivers that were suggested to me by OS (Ubuntu 12. 04) , installation failed and now there is this problem report eatch time I log in ProblemType: Package DistroRelease: Ubuntu 12.04 Package: cedarview-drm 20120717-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.0.1-0ubuntu17.9 Architecture: i386 DKMSKernelVersion: 3.11.0-26-generic Date: Sun Jun 21 01:38:23 2015 InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) MarkForUpload: True PackageVersion: 20120717-0ubuntu1 SourcePackage: cedarview-drm-drivers Title: cedarview-drm 20120717-0ubuntu1: cedarview-drm kernel module failed to build UpgradeStatus: Upgraded to precise on 2015-06-20 (1 days ago) modified.conffile..etc.lightdm.lightdm.conf: [SeatDefaults] user-session=ubuntu-2d greeter-session=unity-greeter autologin-user=delic mtime.conffile..etc.lightdm.lightdm.conf: 2015-06-21T14:00:45.527648 ** Affects: cedarview-drm-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467616 Title: problem report each time I log in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cedarview-drm-drivers/+bug/1467616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466792] Re: linux: 3.16.0-43.58 -proposed tracker
Promoted to proposed: linux| 3.16.0-43.58 | utopic-proposed | source linux-meta | 3.16.0.43.43 | utopic-proposed | source linux-signed | 3.16.0-43.58 | utopic-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed 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/1466792 Title: linux: 3.16.0-43.58 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466937] Re: linux-keystone: 3.13.0-32.49 -proposed tracker
Promoted to proposed: linux-keystone | 3.13.0-32.49 | trusty-proposed | source linux-meta-keystone | 3.13.0.32.30 | trusty-proposed | source ** Changed in: kernel-sru-workflow/promote-to-proposed 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/1466937 Title: linux-keystone: 3.13.0-32.49 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447834] Re: curtin doesn't support arm64-efi targets
** Description changed: - We need to add support to curtin for supporting UEFI-based ARM64 - systems. + [Impact] + Curtin doesn't support UEFI-based ARM64 systems. + + [Test Case] + Use Curtin to install an ARM64-UEFI system. We did this testing with MAAS incorporating this MP: +https://code.launchpad.net/~newell-jensen/maas/uefi-arm64/+merge/260639 + + [Regression Risk] + 2/3 of the curtin changes are preventing code that was running on all aarch64 platforms to just running on non-UEFI aarch64 systems. Since we only supported non-UEFI systems before, that should be a low risk of regression. + + The only other change is adding the grub target name for arm64, which is + also pretty straightforward. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1447834 Title: curtin doesn't support arm64-efi targets To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1447834/+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 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: + === Begin SRU Information === + [Description] + When curtin installs to a system that has multipath devices, it does not recognize this and enable them. + The result is that a system that has multipath devices installed will have Ubuntu installed to one of the non-multipath paths. The end user is then confused because they see root installed on /dev/sda1 and another device /dev/sdg1 (or other name) that has the same content as /dev/sda1. In addition to this confusion, if the user decides to use /dev/sdg1 and format it, they'll have shot themselves in the foot by destroying their root partition. + + The general solution is to install multipath-tools-boot when the system is detected to have multipath devices. To do this, curtin does: + curtin currently does: + a.) installs multipath-boot *only* when multipath devices are found, avoiding bug 1463046. + b.) writes /etc/multipath.conf to use user_friendly_names, avoiding bug 1432062. + c.) writes /etc/multipath/bindings file to provide a consistent named /dev/mapper/mpath name (solving bug 1429327) + + [Impact] + Without this fix, most power 8 systems will install to /dev/sda1 and let the user modify /dev/sdg1 (or whatever device name that multipath device appears as). This is not very user friendly, and quite confusing. + + [Test Case] + Positive case: + a.) install system that has multipath + b.) verify that multipath-tools-boot is installed. + c.) verify that system is booted with root=/dev/mapper/mpath0-part2 + + Negative case: + a.) install system with 2 disks without multipath + b.) verify that no multipath-tools-boot is installed. + + [Regression Potential] + The regression potential falls into 2 places: + a.) a system with multipath that installed without multipath fails to install or work after this + this is really a bug in multipath in kenrel or the package if we get here. We've done fairly significant testing to show that we're reliably installing. + + b.) a system without multipath is identified as multipath + The detection of multipath basically consists of looking for 2 devices that have a filesystem with the same UUID on them after creating a filesystem with that UUID. This is essentially not more than a check for a random sequence of bytes on all disks rather than a fully determinable identification of multipath. So, the failure case is: + 1.) we install to system and 'mkfs' the root partition + 2.) we find 2 disks that have the same UUID as the root device (the root device and one other) + In all likelyhood, that would mean that a filesytem with this UUID already existed on the system. That seems quite unlikley. + + In the event that the user does not have multipath systems and just wants to disable multipath to avoid that scenario, they can do so by config in maas setting the following in /etc/maas/preseeds/curtin_userdata will disable multipath and boot quite reliably without multipath. + multipath: + mode: false + + [Other] + Related bugs: + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + + === End SRU Information === + + === Original bug report === $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. - - Related bugs: - * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
** Branch linked: lp:ubuntu/wily-proposed/python-tx-tftp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242417] Re: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio)
** Changed in: grub2 (Ubuntu Precise) Assignee: (unassigned) = chyurik (kamysh23) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1242417 Title: UEFI install broken when GRUB_DISTRIBUTOR!=Ubuntu (e.g. Kubuntu/UbuntuStudio) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1464853] Re: Sync libjsoncpp 0.10.2-3 (universe) from Debian unstable (main)
** Changed in: libjsoncpp (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464853 Title: Sync libjsoncpp 0.10.2-3 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1464853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467611] Re: unprivileged lxc containers broken
Btw, cgmanager is started and keep reporting junk which I fail to interpret: systemctl status cgmanager ● cgmanager.service - Cgroup management daemon Loaded: loaded (/lib/systemd/system/cgmanager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2015-06-22 16:57:30 CEST; 2h 25min ago Main PID: 589 (cgmanager) Memory: 724.0K CGroup: /system.slice/cgmanager.service ‣ 589 /sbin/cgmanager -m name=systemd Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/hugetlb/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/hugetlb/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/memory/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/memory/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/net_cls/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/net_cls/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/perf_event/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/perf_event/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager: Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-server.service/lxc/asterisk Jun 22 19:22:39 xnode cgmanager[589]: cgmanager:per_ctrl_move_pid_main: Invalid path /run/cgmanager/fs/none,name=systemd/system.slice/lsh-server.se...c/asterisk Hint: Some lines were ellipsized, use -l to show in full. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467611 Title: unprivileged lxc containers broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317705] Re: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs
This bug was fixed in the package python-tx-tftp - 0.1~bzr38-0ubuntu4 --- python-tx-tftp (0.1~bzr38-0ubuntu4) wily; urgency=medium * debian/patches/05_lp1317705.patch: Regonise error code 8, which is used to terminate a transfer due to option negotiation. See RFC 2347, TFTP Option Extension. (LP: #1317705) -- Andres Rodriguez andres...@ubuntu.com Mon, 22 Jun 2015 12:33:26 -0400 ** Changed in: python-tx-tftp (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/1317705 Title: Commissioning x86_64 node never completes, sitting at grub prompt, pserv py tbs To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1317705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467376] Re: Stuttering looping sound when not touching mouse/keyoard
Audio stuttering appears only when CPU load very small. If there are some task taking busy CPU there are no problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467376 Title: Stuttering looping sound when not touching mouse/keyoard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361139] Re: Orca Screen Reader operation interface cannot show on screen.
This is simply fantastic. Bug excists almost ONE YEAR and no one has fixed it yet!!!??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361139 Title: Orca Screen Reader operation interface cannot show on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1361139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465798] Re: linux: 3.13.0-56.93 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Chris J Arges (arges) = Canonical Kernel SRU Team (canonical-kernel-sru-team) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465798 Title: linux: 3.13.0-56.93 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1465798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371634] Re: block devices appear twice [install does not use multipath]
** Description changed: + === Begin SRU Information === + [Description] + When curtin installs to a system that has multipath devices, it does not recognize this and enable them. + The result is that a system that has multipath devices installed will have Ubuntu installed to one of the non-multipath paths. The end user is then confused because they see root installed on /dev/sda1 and another device /dev/sdg1 (or other name) that has the same content as /dev/sda1. In addition to this confusion, if the user decides to use /dev/sdg1 and format it, they'll have shot themselves in the foot by destroying their root partition. + + The general solution is to install multipath-tools-boot when the system is detected to have multipath devices. To do this, curtin does: + curtin currently does: + a.) installs multipath-boot *only* when multipath devices are found, avoiding bug 1463046. + b.) writes /etc/multipath.conf to use user_friendly_names, avoiding bug 1432062. + c.) writes /etc/multipath/bindings file to provide a consistent named /dev/mapper/mpath name (solving bug 1429327) + + [Impact] + Without this fix, most power 8 systems will install to /dev/sda1 and let the user modify /dev/sdg1 (or whatever device name that multipath device appears as). This is not very user friendly, and quite confusing. + + [Test Case] + Positive case: + a.) install system that has multipath + b.) verify that multipath-tools-boot is installed. + c.) verify that system is booted with root=/dev/mapper/mpath0-part2 + + Negative case: + a.) install system with 2 disks without multipath + b.) verify that no multipath-tools-boot is installed. + + [Regression Potential] + The regression potential falls into 2 places: + a.) a system with multipath that installed without multipath fails to install or work after this + this is really a bug in multipath in kenrel or the package if we get here. We've done fairly significant testing to show that we're reliably installing. + + b.) a system without multipath is identified as multipath + The detection of multipath basically consists of looking for 2 devices that have a filesystem with the same UUID on them after creating a filesystem with that UUID. This is essentially not more than a check for a random sequence of bytes on all disks rather than a fully determinable identification of multipath. So, the failure case is: + 1.) we install to system and 'mkfs' the root partition + 2.) we find 2 disks that have the same UUID as the root device (the root device and one other) + In all likelyhood, that would mean that a filesytem with this UUID already existed on the system. That seems quite unlikley. + + In the event that the user does not have multipath systems and just wants to disable multipath to avoid that scenario, they can do so by config in maas setting the following in /etc/maas/preseeds/curtin_userdata will disable multipath and boot quite reliably without multipath. + multipath: + mode: false + + [Other] + Related bugs: + * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers + * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell + * bug 1462530 : multipath errors on vivid, wily kernel + * bug 1463046 : installation of multipath-tools-boot can break boot + * bug 1447167 : [d-i] multipath-install: Installing with multipath enabled does not install multipath-tools + * bug 1429327 : Boot from an unique, stable, multipath-dependent symlink + + === End SRU Information === + + === Original bug report === $ sudo blkid /dev/sr0: LABEL=Ubuntu-Server 14.04 LTS ppc64el TYPE=iso9660 /dev/sda2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sda3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdb2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdb3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap /dev/sdg2: UUID=795a6e14-ea4e-4718-9e98-c6df3696920c TYPE=ext4 /dev/sdg3: UUID=0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4 TYPE=swap /dev/sdh2: UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 TYPE=ext4 /dev/sdh3: UUID=9c228177-d65c-4d19-a462-db1891e9781e TYPE=swap I'm not sure what exactly those block devices are (as in if they're raided in hardware or they actually represent physical spinning disks). But I do know that writing data to sda causes that data to be readable from sdg. The same is true: sda - sdg sdb - sdh That is what causes those UUIDs to be similar. Everything is functional, you just have to know that if your root device is /dev/sdg that you should probably not write data to /dev/sda thinking you can use it as a disk. - - Related bugs: - * bug 1432062 : multipath-tools-boot: support booting without user_friendly_names on devices with spaces in identifiers - * bug 1463043 : some SM15K systems fail to boot after deployment - drop into initramfs shell - * bug
[Bug 1466768] Re: /usr/sbin/aa-status:PermissionError:/usr/sbin/aa-status@194:cmd_verbose:get_profiles
** Branch linked: lp:apparmor/2.9 ** Branch linked: lp:apparmor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466768 Title: /usr/sbin/aa-status:PermissionError:/usr/sbin/aa- status@194:cmd_verbose:get_profiles To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1466768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403133] Re: curtin should retry fetching from archives after transient failure
** Description changed: - We run into transient network issues where index files fail to download. - The deployment ends up being marked as failed. Then subsequent - deployment succeeds but test has already failed. Curtin should be able - to retry when such error happens. + === Begin SRU Template === + [Description] + During installation, curtin will run 'apt-get update' on in the target root. That is done as a requirement to installing new packages in the target. + + 'apt-get update' is widely known to fail as a result of transient + network failures. This is commonly worked around by simply sleeping and + re-trying the operation. + + The solution implemented is to improve the 'subp' (subprocess) helper in curtin/util to take a 'retries' argument. + If provided that is a iterator that contains a time to sleep before trying again. If no retries is provided, then only one try is done. + Then, the curtin/util.py helper apt_update invokes subp with retries=(1, 2, 3). + + [Impact] + Installation fails when a simple retry of 'apt-get update' would have succeeded. + + [Test Case] + As this is a transient failure, it is hard to catch and hard to test for. + + Installation should be more reliable now, with any 'apt-get update' + operation that returned non-zero being retried 3 times. + + [Regression Potential] + The only really likely regression path here would be retrying 'apt update' on its successful return. That seems fairly unlikely as the code in subp to check exit status has not changed. + + [Other] + Related bugs: + * bug 972077: apt repository disk format has race conditions + === End SRU Template === + + + We run into transient network issues where index files fail to download. The deployment ends up being marked as failed. Then subsequent deployment succeeds but test has already failed. Curtin should be able to retry when such error happens. Here's console output: Get:28 http://archive.ubuntu.com trusty-security/multiverse Translation-en [587 B] Get:29 http://archive.ubuntu.com trusty-security/restricted Translation-en [2266 B] Get:30 http://archive.ubuntu.com trusty-security/universe Translation-en [41.5 kB] Fetched 13.8 MB in 5s (2426 kB/s) W: Failed to fetch http://archive.ubuntu.com//ubuntu/dists/trusty-updates/universe/i18n/Translation-en Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. Unexpected error while running command. Command: ['chroot', '/tmp/tmp8mxme7/target', 'apt-get', 'update', '--quiet'] Exit code: 100 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'curthooks'] Exit code: 3 Reason: - Stdout: Ign http://archive.ubuntu.com trusty InRelease\nIgn http://archive.ubuntu.com trusty-updates InRelease\nIgn http://archive.ubuntu.com trusty-security InRelease\nGet:1 http://archive.ubuntu.com trusty Release.gpg [933 B]\nGet:2 http://archive.ubuntu.com trusty-updates Release.gpg [933 B]\nGet:3 http://archive.ubuntu.com trusty-security Release.gpg [933 B]\nGet:4 http://archive.ubuntu.com trusty Release [58.5 kB]\nGet:5 http://archive.ubuntu.com trusty-updates Release [62.0 kB]\nGet:6 http://archive.ubuntu.com trusty-security Release [62.0 kB]\nGet:7 http://archive.ubuntu.com trusty/main amd64 Packages [1350 kB]\nGet:8 http://archive.ubuntu.com trusty/restricted amd64 Packages [13.0 kB]\nGet:9 http://archive.ubuntu.com trusty/universe amd64 Packages [5859 kB]\nGet:10 http://archive.ubuntu.com trusty/multiverse amd64 Packages [132 kB]\nGet:11 http://archive.ubuntu.com trusty/main Translation-en [762 kB]\nGet:12 http://archive.ubuntu.com trusty/multiverse Translation-en [102 k B]\nGet:13 http://archive.ubuntu.com trusty/restricted Translation-en [3457 B]\nGet:14 http://archive.ubuntu.com trusty/universe Translation-en [4089 kB]\nGet:15 http://archive.ubuntu.com trusty-updates/main amd64 Packages [384 kB]\nGet:16 http://archive.ubuntu.com trusty-updates/restricted amd64 Packages [8861 B]\nGet:17 http://archive.ubuntu.com trusty-updates/universe amd64 Packages [228 kB]\nGet:18 http://archive.ubuntu.com trusty-updates/multiverse amd64 Packages [9356 B]\nGet:19 http://archive.ubuntu.com trusty-updates/main Translation-en [179 kB]\nGet:20 http://archive.ubuntu.com trusty-updates/multiverse Translation-en [4719 B]\nGet:21 http://archive.ubuntu.com trusty-updates/restricted Translation-en [2266 B]\nGet:22 http://archive.ubuntu.com trusty-updates/universe Translation-en [117 kB]\nGet:23 http://archive.ubuntu.com trusty-security/main amd64 Packages [181 kB]\nGet:24 http://archive.ubuntu.com trusty-security/restricted amd64 Packages [8861 B]\nGet:25 http://archive. ubuntu.com trusty-security/universe amd64 Packages [76.0 kB]\nGet:26 http://archive.ubuntu.com trusty-security/multiverse amd64
[Bug 1460012] Re: Context is opened twice when receiving an MMS
This bug was fixed in the package nuntium - 1.4+15.10.20150615-0ubuntu1 --- nuntium (1.4+15.10.20150615-0ubuntu1) wily; urgency=medium [ Alfonso Sanchez-Beato (email Canonical) ] * Fix LP: #1461107 and make PDU decoding more robust * Fix LP: #1460012 (context opened twice on rx) * Wait between retries when opening an IP context * Set ofono's Preferred property when a context is known to work -- CI Train Bot ci-train-...@canonical.com Mon, 15 Jun 2015 08:52:13 + ** Changed in: nuntium (Ubuntu) Status: In Progress = 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/1460012 Title: Context is opened twice when receiving an MMS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1460012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467112] Re: New Homebank release with important features and bugfixes available since February 2015, please update
** Changed in: homebank (Debian) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467112 Title: New Homebank release with important features and bugfixes available since February 2015, please update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/homebank/+bug/1467112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440180] Re: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (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/1440180 Title: package initscripts 2.88dsf-41ubuntu18 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1440180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463077] Re: DLPAR - Memory add operation fails
Right, Steve. We now need to fix it on 14.04, as you already started to track. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463077 Title: DLPAR - Memory add operation fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerpc-ibm-utils/+bug/1463077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467151] Re: 60-persistent-storage.rules fails to create by-uuid links to Xen virtual disks (xvd)
** Package changed: udev (Ubuntu) = systemd (Ubuntu) ** Changed in: systemd (Ubuntu) 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/1467151 Title: 60-persistent-storage.rules fails to create by-uuid links to Xen virtual disks (xvd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1467151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466937] Re: linux-keystone: 3.13.0-32.49 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) = Chris J Arges (arges) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466937 Title: linux-keystone: 3.13.0-32.49 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1466937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467561] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1467561 Title: IPsec VTI functionality broken in 3.16.0-39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460120] Re: Please sync from debian unstable 1.2.13-1
OK, if it needs to do stuff before shutdown then we should do this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1460120 Title: Please sync from debian unstable 1.2.13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1460120/+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 1351177] Re: Suggestions improvements
** Changed in: ubuntu-ux Status: Fix Committed = 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/1351177 Title: Suggestions improvements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460120] Re: Please sync from debian unstable 1.2.13-1
OK, if it needs to do stuff before shutdown then we should do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460120 Title: Please sync from debian unstable 1.2.13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1460120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467557] Re: virtualbox-dkms 4.3.26-dfsg-2ubuntu2: virtualbox kernel module failed to build
Simple, do not use development kernels. ** Changed in: virtualbox (Ubuntu) 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/1467557 Title: virtualbox-dkms 4.3.26-dfsg-2ubuntu2: virtualbox kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1467557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351157] Re: [browser] Update visual design of the new tab page
** Description changed: The visual design of the new tab page doesn’t fully match the visual spec: - - the see more / see less actions for bookmarks should be in the section header - - the layout should be different when in landscape mode + - the see more / see less actions for bookmarks should be in the section header + - the layout should be different when in landscape mode + + [UX Comment] + Fix Released Partial - Correct UX/visuals for portrait working as per spec, but same UX/visuals also present in landscape mode (landscape has different UX visuals): + + https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354ad9a19_026 + (Page 14 of visual spec) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351157 Title: [browser] Update visual design of the new tab page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467583] [NEW] PROBLEM
Public bug reported: --- ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jun 22 17:56:13 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-15-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-21-generic, x86_64: installed tp-smapi, 0.41, 3.19.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00ea] InstallationDate: Installed on 2015-06-20 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Apple Inc. MacBookAir4,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic.efi.signed root=UUID=69f19b32-45d5-4cae-a423-e9801940319b ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B0F.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C08A6BB70A942AC2 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C08A6BB70A942AC2 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2: dmi.product.name: MacBookAir4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Mon Jun 22 17:41:56 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40179 vendor APP xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467583 Title: PROBLEM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1467583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1460120] Re: Please sync from debian unstable 1.2.13-1
This bug was fixed in the package keepalived - 1:1.2.13-1 Sponsored for Bryan Quigley (bryanquigley) --- keepalived (1:1.2.13-1) unstable; urgency=medium * [1e9c32b] Imported Upstream version 1.2.11 * [bac64d6] Imported Upstream version 1.2.13 - keep retry in case of early TCP failures in checks (Closes: #626466 #504069) - Add To header for SMTP alerts. (Closes: #627169) - handle passwords up to 8 characters (Closes: #614562) - modprobe handling fixed (Closes: #714377) - Support more than 31 interfaces (Closes: #723106) - Fix ipv6 realserver handling (Closes: #740258) - extend ip parser to support default and default6 (Closes: #740573) * [65d5b11] Add pkg-config to build-deps * [af497e7] Disable obsolete patches * [4761254] Bump standards version (no changes) -- Alexander Wirt formo...@debian.org Wed, 28 May 2014 09:01:38 +0200 keepalived (1:1.2.9-1) unstable; urgency=low * [8cd7bad] Imported Upstream version 1.2.9 -- Alexander Wirt formo...@debian.org Mon, 11 Nov 2013 22:45:58 +0100 keepalived (1:1.2.8-1) unstable; urgency=low * [b25f231] Patch configure.in instead of configure * [aa70432] Fix configure * [3a728cd] Enable sha1 support * [e257779] Add Homepage field * Allow providing of daemon args via /etc/defaul/keepalived Closes: #693877 * Import upstream version 1.2.8 (Closes: #721966) - Fix reload handling (Closes: #652260) -- Alexander Wirt formo...@debian.org Fri, 13 Sep 2013 08:54:19 +0200 ** Changed in: keepalived (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1460120 Title: Please sync from debian unstable 1.2.13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1460120/+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 1460120] Re: Please sync from debian unstable 1.2.13-1
This bug was fixed in the package keepalived - 1:1.2.13-1 Sponsored for Bryan Quigley (bryanquigley) --- keepalived (1:1.2.13-1) unstable; urgency=medium * [1e9c32b] Imported Upstream version 1.2.11 * [bac64d6] Imported Upstream version 1.2.13 - keep retry in case of early TCP failures in checks (Closes: #626466 #504069) - Add To header for SMTP alerts. (Closes: #627169) - handle passwords up to 8 characters (Closes: #614562) - modprobe handling fixed (Closes: #714377) - Support more than 31 interfaces (Closes: #723106) - Fix ipv6 realserver handling (Closes: #740258) - extend ip parser to support default and default6 (Closes: #740573) * [65d5b11] Add pkg-config to build-deps * [af497e7] Disable obsolete patches * [4761254] Bump standards version (no changes) -- Alexander Wirt formo...@debian.org Wed, 28 May 2014 09:01:38 +0200 keepalived (1:1.2.9-1) unstable; urgency=low * [8cd7bad] Imported Upstream version 1.2.9 -- Alexander Wirt formo...@debian.org Mon, 11 Nov 2013 22:45:58 +0100 keepalived (1:1.2.8-1) unstable; urgency=low * [b25f231] Patch configure.in instead of configure * [aa70432] Fix configure * [3a728cd] Enable sha1 support * [e257779] Add Homepage field * Allow providing of daemon args via /etc/defaul/keepalived Closes: #693877 * Import upstream version 1.2.8 (Closes: #721966) - Fix reload handling (Closes: #652260) -- Alexander Wirt formo...@debian.org Fri, 13 Sep 2013 08:54:19 +0200 ** Changed in: keepalived (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1460120 Title: Please sync from debian unstable 1.2.13-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1460120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462139] Re: curtain fails with Device is busy error during unmount
** Description changed: + === Begin SRU Template === + [Description] + A race condition can occur when invoking grub-install inside the target environment. + The failure case shows logs like this: + | Installing for i386-pc platform. + | Installation finished. No error reported. + | umount: /tmp/tmpM4R1dI/target/dev: device is busy. + | (In some cases useful info about processes that use + | the device is found by lsof(8) or fuser(1)) + | Unexpected error while running command. + | Command: ['umount', '/tmp/tmpM4R1dI/target/dev'] + | Exit code: 1 + | Reason: - + | Stdout: '' + | Stderr: '' + | Installation failed with exception: Unexpected error while running command. + | Command: ['curtin', 'curthooks'] + + This is believed to be because some process (likely spawned by udev) has + open filehandles on /dev when curtin went to clean up the target mounts. + + The solution is to run 'udevadm settle' before unmounting '/dev/' from + the target. + + [Impact] + The impact is transient failure to install. This race condition is very rarely seen on hardware, but was somewhat easily reproduced in a heavily loaded vmware environment. + + [Test Case] + In the original bug-opener's environment it fails fairly reliably under heavy host load using vmware. He would do a deploy to several guests on the same host at the same time and this would reproduce. Unfortunately I was unable to come up with a test case in a less complex environment. + + [Regression Potential] + Regression potential should be very low here. The most likely fallout is just additional time for the install as a result of running 'udevadm settle'. A system that did not exhibit this bug will install a small fraction of a second slower. + + $ sudo bash -c 'time for x in $@; do udevadm settle; done' -- $(seq 1 100) + real 0m0.214s + user 0m0.012s + sys 0m0.008s + + As shown above, that is likely to be on the order of 1/100th of a + second. + + === End SRU Template === + + Here's the relevant part of the curtin output: Installing for i386-pc platform. Installation finished. No error reported. umount: /tmp/tmpM4R1dI/target/dev: device is busy. - (In some cases useful info about processes that use - the device is found by lsof(8) or fuser(1)) + (In some cases useful info about processes that use + the device is found by lsof(8) or fuser(1)) Unexpected error while running command. Command: ['umount', '/tmp/tmpM4R1dI/target/dev'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'curthooks'] I spoke with Scott Moser on IRC about this, and he suggested the attached patch, which fixed the problem 100%. I checked the installation output of a few of my MAAS nodes, and didn't see any lsof output. So I assume the udevadm settle command is the fix. (Thanks Scott! I hope we can land this in time for MAAS 1.8.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462139 Title: curtain fails with Device is busy error during unmount To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1462139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467533] Re: [SRU] icehouse 2014.1.5 point release
** Also affects: nova (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: glance (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: heat (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467533 Title: [SRU] icehouse 2014.1.5 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1467533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1338706] Re: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12
In the meantime instead of modifying your boot command line you could test the 3.13 ppa that contains the fix that will eventually make it into the updated kernel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/comments/34 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1338706 Title: Samsung SSD 840 failed to get NCQ Send/Recv Log Emask 0x1 failed to set xfermode (err_mask=0x40) on upstream kernels = 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462139] Re: curtain fails with Device is busy error during unmount
** Description changed: + === Begin SRU Template === + [Description] + A race condition can occur when invoking grub-install inside the target environment. + The failure case shows logs like this: + | Installing for i386-pc platform. + | Installation finished. No error reported. + | umount: /tmp/tmpM4R1dI/target/dev: device is busy. + | (In some cases useful info about processes that use + | the device is found by lsof(8) or fuser(1)) + | Unexpected error while running command. + | Command: ['umount', '/tmp/tmpM4R1dI/target/dev'] + | Exit code: 1 + | Reason: - + | Stdout: '' + | Stderr: '' + | Installation failed with exception: Unexpected error while running command. + | Command: ['curtin', 'curthooks'] + + This is believed to be because some process (likely spawned by udev) has + open filehandles on /dev when curtin went to clean up the target mounts. + + The solution is to run 'udevadm settle' before unmounting '/dev/' from + the target. + + [Impact] + The impact is transient failure to install. This race condition is very rarely seen on hardware, but was somewhat easily reproduced in a heavily loaded vmware environment. + + [Test Case] + In the original bug-opener's environment it fails fairly reliably under heavy host load using vmware. He would do a deploy to several guests on the same host at the same time and this would reproduce. Unfortunately I was unable to come up with a test case in a less complex environment. + + [Regression Potential] + Regression potential should be very low here. The most likely fallout is just additional time for the install as a result of running 'udevadm settle'. A system that did not exhibit this bug will install a small fraction of a second slower. + + $ sudo bash -c 'time for x in $@; do udevadm settle; done' -- $(seq 1 100) + real 0m0.214s + user 0m0.012s + sys 0m0.008s + + As shown above, that is likely to be on the order of 1/100th of a + second. + + === End SRU Template === + + Here's the relevant part of the curtin output: Installing for i386-pc platform. Installation finished. No error reported. umount: /tmp/tmpM4R1dI/target/dev: device is busy. - (In some cases useful info about processes that use - the device is found by lsof(8) or fuser(1)) + (In some cases useful info about processes that use + the device is found by lsof(8) or fuser(1)) Unexpected error while running command. Command: ['umount', '/tmp/tmpM4R1dI/target/dev'] Exit code: 1 Reason: - Stdout: '' Stderr: '' Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'curthooks'] I spoke with Scott Moser on IRC about this, and he suggested the attached patch, which fixed the problem 100%. I checked the installation output of a few of my MAAS nodes, and didn't see any lsof output. So I assume the udevadm settle command is the fix. (Thanks Scott! I hope we can land this in time for MAAS 1.8.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to curtin in Ubuntu. https://bugs.launchpad.net/bugs/1462139 Title: curtain fails with Device is busy error during unmount To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1462139/+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 1467533] Re: [SRU] icehouse 2014.1.5 point release
** Also affects: nova (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: glance (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ceilometer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: heat (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer in Ubuntu. https://bugs.launchpad.net/bugs/1467533 Title: [SRU] icehouse 2014.1.5 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1467533/+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 1467608] [NEW] cursor position sometimes off with HiDPI screen
Public bug reported: Sometimes the cursor tracking is wrong when using chromium-browser as in the pointer on the screen is pointing to one place but chromium sees it in another. If I move the cursor outside of chromium, other applications track it fine. Most of the time things are ok with chromium, but when this happens the text in the web page also goes slightly fuzzy. Thankfully, a workaround is simply to resize the window (it doesn't seem to matter how much). After which, the text is no longer fuzzy and the mouse is tracked correctly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: chromium-browser 43.0.2357.81-0ubuntu0.15.04.1.1170 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity DRM.card0.DP.1: edid-base64: AP///wAQrL1ATFY4QQ4ZAQSlPCJ4OiiVp1VOoyYPUFSlSwDRANHAswCpQIGAgQBxTwEBTdAAoPBwPoAwIDUAVVAhAAAa/wAzMlIxRjU0MUE4VkwK/ABERUxMIFAyNzE1UQog/QAdSx+MNgEKICAgICAgAYcCAx3xUBAfIAUUBBMSEQMCFhUHBgEjCR8HgwEAAFZeAKCgoClQMCA1AFVQIQAAGgI6gBhxOC1AWCwlAFVQIQAAHgEdAHJR0B4gbihVAFVQIQAAHgAAQA== dpms: On modes: 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1920x1080 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 720x400 enabled: enabled status: connected DRM.card0.HDMI.A.1: edid-base64: dpms: On modes: enabled: disabled status: disconnected DRM.card0.eDP.1: edid-base64: AP///wBNECEUADIYAQSlHRF4Dt5Qo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBzZGAoMAINHAwIDUAJqUQAAAYEAAA/gAwNVA3SIVMUTEzM1oxAAACQQMoABIAAAsBCiAgABs= dpms: On modes: 3200x1800 enabled: enabled status: connected Date: Mon Jun 22 11:48:38 2015 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg' '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/' Env: 'None' 'None' InstallationDate: Installed on 2015-06-13 (8 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) Load-Avg-1min: 0.41 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq quiet splash vt.handoff=7 SourcePackage: chromium-browser UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0310JH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'firefox %u\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'firefox %u\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b'compiz\n'/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n' modified.conffile..etc.default.chromium.browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467608 Title: cursor position sometimes off with HiDPI screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1467608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278780] Re: [Ubuntu-phone] BQ r23 total off and unwilling to react
On Mon, Jun 22, 2015 at 02:48:01PM +0200, Oliver Grawert wrote: seems that whoopsie refuses to send your report because you are not on wifi, perhaps it should check for this earlier and not even run the collection, not sure ... The only part that should be running when not on wifi is the crash collection. We certainly *should* be running that when not on wifi; you don't get a second chance to run the kernel crash handler, and we want to know about crashes that only happen when not on wifi (including, possibly, crashes that happen /because/ you're not on wifi). On Mon, Jun 22, 2015 at 02:19:10PM +0100, Alan Pope wrote: Also, related to the discussion:- https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1278780 The trouble is that, until the crash handler has finished consuming the core file from the kernel and exited, the original process is blocked. So the shell can't know that the process has died and move on until the crash handler has finished running. (The same is true on the desktop, it's just less impactful because the app is usually not full screen and blocking the UI at the time.) We have already taken steps to minimize the amount of processing done on the core file as part of the apport crash handler, in favor of post-processing the crash file from a queue. It's not clear what further optimization of the crash handler is possible. On Mon, Jun 22, 2015 at 02:39:04PM +0200, Oliver Grawert wrote: hi, Am Montag, den 22.06.2015, 14:28 +0200 schrieb Marco F: Who decided that collection of debug information is the task with highest priority on a phone which wishes to be used by the public? i think it already runs at a very low prio (obviously still to high for the phone though ... ) Running it with a low priority would NOT improve the user experience. It would just cause the app to hang longer in an unkillable, memory-consuming state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278780 Title: apport takes too long to write crash report, appears to lock up phone To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1278780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1461107] Re: nuntium crashes when parsing a notification indication
This bug was fixed in the package nuntium - 1.4+15.10.20150615-0ubuntu1 --- nuntium (1.4+15.10.20150615-0ubuntu1) wily; urgency=medium [ Alfonso Sanchez-Beato (email Canonical) ] * Fix LP: #1461107 and make PDU decoding more robust * Fix LP: #1460012 (context opened twice on rx) * Wait between retries when opening an IP context * Set ofono's Preferred property when a context is known to work -- CI Train Bot ci-train-...@canonical.com Mon, 15 Jun 2015 08:52:13 + ** Changed in: nuntium (Ubuntu) Status: In Progress = 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/1461107 Title: nuntium crashes when parsing a notification indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1461107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311827] Re: UEFI installation overrides firmware PXE-boot settings
** Description changed: + === Begin SRU Template === + [Description] + Installing a node configured to boot in EFI/UEFI mode results in Ubuntu registering GRUB with the firmware, thus overriding the node's original PXE-boot setting. This can be seen via efibootmgr after the node has been started by running 'efibootmgr -v'. + + The solution is to invoke grub-install with '--no-nvram'. That + instructs grub to not update the PXE boot setting. + + Curtin code detects if the --no-nvram flag is available and uses it if + it is. + + [Impact] + MAAS generally works by expecting a system to always request boot from the network. MAAS then instructs it to boot from the local disk when it is installed, and feeds it network boot information for install or commissioning or enlistment. + + The issue here is that we would install to the system and configure the + system to boot from the local disk. The end result is that installation + works once, but when the system is returned to maas, a subsequent + installation will fail. + + [Test Case] + a.) enlist a EFI/UEFI system into maas with network boot configured + b.) acquire and start system to install 14.04 + c.) release system + d.) acquire and start system to install 14.04 + + Currently step 'd' will boot from local disk. After fix is applied, + system will boot from network and perform install correctly. + + [Regression Potential] + Seems fairly unlikely for regression. I can't think of a specific case that would fail that previously succeeded. + + [Other] + As grub in 12.04 does not support the --no-nvram flag, installation of 12.04 will still cause this failure path. + + === End SRU Template === + Installing a node configured to boot in EFI/UEFI mode results in Ubuntu registering GRUB with the firmware, thus overriding the node's original PXE-boot setting. This can be seen via efibootmgr after the node has been started: $ sudo efibootmgr -v BootCurrent: 0006 Timeout: 0 seconds BootOrder: 0006,000E,0007,0008,0009,000A,000B,000C,000D - Boot Setup - Boot0001 Boot Menu - Boot0002 Diagnostic Splash Screen - Boot0003 Lenovo Diagnostics - Boot0004 Startup Interrupt Menu - Boot0005 ME Configuration Menu + Boot Setup + Boot0001 Boot Menu + Boot0002 Diagnostic Splash Screen + Boot0003 Lenovo Diagnostics + Boot0004 Startup Interrupt Menu + Boot0005 ME Configuration Menu Boot0006* ubuntu HD(1,800,10,2017753f-1b99-424d-811b-91c2e8c3c816)File(\EFI\ubuntu\shimx64.efi) Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55 Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49 Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35401 Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600 Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f601 Boot000C* ATA HDD2 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f602 Boot000D* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803 Boot000E* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803 Boot000F* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0) Boot0010* IDER BOOT FloppyACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0) Boot0012 Rescue and Recovery Note that the system's BootOrder is set to load \EFI\ubuntu\shimx64.efi (which in turn launches GRUB; item Boot0006) from the hard disk, and to PXE-boot (item Boot000E) second. When the process began, it was set to PXE-boot first. This works fine for bringing up a node initially, but it's different from the way a BIOS-mode installation works, in which the system is left PXE-booting by default. The UEFI approach will result in an inability to delete the node and re-enlist it, or even to stop the node and then re- start it and have Ubuntu re-installed, without either manually running efibootmgr or delete the file or partition to which the boot manager entry points. I'm attaching my MAAS log files. The UEFI-booting system is 192.168.0.56. Here's the MAAS server version information: $ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===--=== ii maas 1.5+bzr2252-0ubuntu1
[Bug 1466047] Re: Install in UEFI mode installs grub-pc
Mathieu I did get the popup about a non-UEFI system and thought I had chosen the correct option for UEFI. Will include when I create screen shots for Phillip. I believe I created an ESP. Screen shots to follow. I've tried Ubuntu and Ubuntu-Gnome with the same result. Debian 8 seemed to work OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466047 Title: Install in UEFI mode installs grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466047] Re: Install in UEFI mode installs grub-pc
Philip I agree the partman log seems to show no EFI partition yet the parted list shows one their and it is mounted. I've now done an Ubuntu build with screenshots for you. Here is the partitioning screen. ** Attachment added: GUEFI1.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418694/+files/GUEFI1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466047 Title: Install in UEFI mode installs grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311827] Re: UEFI installation overrides firmware PXE-boot settings
** Description changed: + === Begin SRU Template === + [Description] + Installing a node configured to boot in EFI/UEFI mode results in Ubuntu registering GRUB with the firmware, thus overriding the node's original PXE-boot setting. This can be seen via efibootmgr after the node has been started by running 'efibootmgr -v'. + + The solution is to invoke grub-install with '--no-nvram'. That + instructs grub to not update the PXE boot setting. + + Curtin code detects if the --no-nvram flag is available and uses it if + it is. + + [Impact] + MAAS generally works by expecting a system to always request boot from the network. MAAS then instructs it to boot from the local disk when it is installed, and feeds it network boot information for install or commissioning or enlistment. + + The issue here is that we would install to the system and configure the + system to boot from the local disk. The end result is that installation + works once, but when the system is returned to maas, a subsequent + installation will fail. + + [Test Case] + a.) enlist a EFI/UEFI system into maas with network boot configured + b.) acquire and start system to install 14.04 + c.) release system + d.) acquire and start system to install 14.04 + + Currently step 'd' will boot from local disk. After fix is applied, + system will boot from network and perform install correctly. + + [Regression Potential] + Seems fairly unlikely for regression. I can't think of a specific case that would fail that previously succeeded. + + [Other] + As grub in 12.04 does not support the --no-nvram flag, installation of 12.04 will still cause this failure path. + + === End SRU Template === + Installing a node configured to boot in EFI/UEFI mode results in Ubuntu registering GRUB with the firmware, thus overriding the node's original PXE-boot setting. This can be seen via efibootmgr after the node has been started: $ sudo efibootmgr -v BootCurrent: 0006 Timeout: 0 seconds BootOrder: 0006,000E,0007,0008,0009,000A,000B,000C,000D - Boot Setup - Boot0001 Boot Menu - Boot0002 Diagnostic Splash Screen - Boot0003 Lenovo Diagnostics - Boot0004 Startup Interrupt Menu - Boot0005 ME Configuration Menu + Boot Setup + Boot0001 Boot Menu + Boot0002 Diagnostic Splash Screen + Boot0003 Lenovo Diagnostics + Boot0004 Startup Interrupt Menu + Boot0005 ME Configuration Menu Boot0006* ubuntu HD(1,800,10,2017753f-1b99-424d-811b-91c2e8c3c816)File(\EFI\ubuntu\shimx64.efi) Boot0007* USB CD 030a2400d23878bc820f604d8316c068ee79d25b86701296aa5a7848b66cd49dd3ba6a55 Boot0008* USB FDD 030a2400d23878bc820f604d8316c068ee79d25b6ff015a28830b543a8b8641009461e49 Boot0009* ATAPI CD0 030a2500d23878bc820f604d8316c068ee79d25baea2090adfde214e8b3a5e471856a35401 Boot000A* ATA HDD0 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f600 Boot000B* ATA HDD1 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f601 Boot000C* ATA HDD2 030a2500d23878bc820f604d8316c068ee79d25b91af625956449f41a7b91f4f892ab0f602 Boot000D* USB HDD 030a2400d23878bc820f604d8316c068ee79d25b33e821aaaf33bc4789bd419f88c50803 Boot000E* PCI LAN 030a2400d23878bc820f604d8316c068ee79d25b78a84aaf2b2afc4ea79cf5cc8f3d3803 Boot000F* IDER BOOT CDROM ACPI(a0341d0,0)PCI(16,2)ATAPI(0,1,0) Boot0010* IDER BOOT FloppyACPI(a0341d0,0)PCI(16,2)ATAPI(0,0,0) Boot0012 Rescue and Recovery Note that the system's BootOrder is set to load \EFI\ubuntu\shimx64.efi (which in turn launches GRUB; item Boot0006) from the hard disk, and to PXE-boot (item Boot000E) second. When the process began, it was set to PXE-boot first. This works fine for bringing up a node initially, but it's different from the way a BIOS-mode installation works, in which the system is left PXE-booting by default. The UEFI approach will result in an inability to delete the node and re-enlist it, or even to stop the node and then re- start it and have Ubuntu re-installed, without either manually running efibootmgr or delete the file or partition to which the boot manager entry points. I'm attaching my MAAS log files. The UEFI-booting system is 192.168.0.56. Here's the MAAS server version information: $ dpkg -l '*maas*'|cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===--=== ii maas 1.5+bzr2252-0ubuntu1
[Bug 1445436] Re: Segmentation faults in libapt-pkg.so.4.12.0
Then please mark this bug as affecting you. ** Changed in: apt (Ubuntu) Status: New = Confirmed ** Tags added: amd64 ** Also affects: linuxmint 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/1445436 Title: Segmentation faults in libapt-pkg.so.4.12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1445436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466047] Re: Install in UEFI mode installs grub-pc
When the install completed grub-pc was installed, not grub-efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466047 Title: Install in UEFI mode installs grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466047] Re: Install in UEFI mode installs grub-pc
Here's the screen just before committing the changes. ** Attachment added: GUEFI2.png https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+attachment/4418695/+files/GUEFI2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466047 Title: Install in UEFI mode installs grub-pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1466047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876713] Re: Soap bind always tries IPV6_V6ONLY on bind and fails with Protocol not available
Any word if this fix will be applied to 14.04 (trusty)? Or should I assume since the last post is a year old that it won't be applied? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876713 Title: Soap bind always tries IPV6_V6ONLY on bind and fails with Protocol not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsoap/+bug/876713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
