[Bug 1331081] Re: please split libvirt-driver apparmor abstraction for qemu and containers
Quoting Serge Hallyn: > This was only released for 14.10. Since 14.04 has been released, only > bugfixes may be introduced there per SRU policy, not new features. Bug 1331081 was reported against 14.04, but was closed as being a duplicate of this. Not fixing the defect reported in 1331081 in 14.04 is not satisfactory for LTS users. It prevents destroying LXC instances which was previously possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331081 Title: please split libvirt-driver apparmor abstraction for qemu and containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1331081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500398] Re: Vtech Kidizoom camera USB doesn't mount
This fix is included upstream in util-linux 2.19.1, so will be fixed with the release of Oneric. ** Changed in: util-linux (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/500398 Title: Vtech Kidizoom camera USB doesn't mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/500398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136940] Re: should allow opening non-removable partitions (port to Gio)
Although it may not be default in 11.04, it was included and part of the default panel configuration for earlier Xubuntu releases, so anyone upgrading to 11.04 will be met with the error message. This is a functionality regression for existing Xubuntu users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/136940 Title: should allow opening non-removable partitions (port to Gio) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783063] Re: Places plugin can't mount or umount removeable devices
The upstream bug (which includes a patch) is https://bugzilla.xfce.org/show_bug.cgi?id=6663 ** Bug watch added: Xfce Bugzilla #6663 http://bugzilla.xfce.org/show_bug.cgi?id=6663 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783063 Title: Places plugin can't mount or umount removeable devices -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500398] Re: Vtech Kidizoom camera USB doesn't mount
I have had a patch accepted upstream to util-linux which means that blkid will recognize the filesystem correctly, and it will then mount. http://git.kernel.org/?p=utils/util-linux/util- linux.git;a=commit;h=20f5be46ec57af3f21913c487000d69fb8857e18 ID_FS_LABEL=VTech_1070 ID_FS_LABEL_ENC=VTech\x201070 ID_FS_SEC_TYPE=msdos ID_FS_TYPE=vfat ID_FS_USAGE=filesystem ID_FS_UUID=2004-1014 ID_FS_UUID_ENC=2004-1014 ID_FS_VERSION=FAT16 ** Package changed: gvfs (Ubuntu) => util-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500398 Title: Vtech Kidizoom camera USB doesn't mount -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500398] Re: Vtech Kidizoom camera USB doesn't mount
The kernel change is not a fix for the real problem. All the kernel patch above does is correctly identify the correct storage capacity (and not spit out error messages as it attempts to access beyond the end of the device). The real problem is that the identification of the partition fails due to the number of heads not being set in the FAT superblock (see #15). I don't seem to be able to change the status. Can somebody please change the status back to "New". I believe the affected package should be "libblkid". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500398 Title: Vtech Kidizoom camera USB doesn't mount -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500398] Re: Vtech Kidizoom camera USB doesn't mount
I have found the cause for this defect, and a workaround. The cause is that the FAT16 superblock on the camera does not set the number of heads, and so the partition type is not detected correctly. You get no output from the following command: # blkid -p /dev/disk/by-id/usb- VTech_Kidizoom_123456789ABCDEF-0:0-part1 The kernel is able to mount the partition when mounted manually in the workaround above because it does not enforce the non-zero heads requirement. In "fat/inode.c" there is the following comment: /* * Earlier we checked here that b->secs_track and b->head are nonzero, * but it turns out valid FAT filesystems can have zero there. */ This means that I suspect the defect is in util-linux. In superblocks/vfat.c it will discount a superblock with a zero value for heads: if (ms->ms_heads == 0) return 0; I was able to confirm this, and provide a workaround by setting the number of heads in the superblock to be 63: echo -n "?" | dd of=/dev/disk/by-id/usb- VTech_Kidizoom_123456789ABCDEF-0:0-part1 seek=26 bs=1 count=1 conv=notrunc Now the partition is detected successfully by blkid. # blkid -p /dev/disk/by-id/usb-VTech_Kidizoom_123456789ABCDEF-0\:0-part1 /dev/disk/by-id/usb-VTech_Kidizoom_123456789ABCDEF-0:0-part1: SEC_TYPE="msdos" LABEL="VTech 1070" UUID="2004-1014" VERSION="FAT16" TYPE="vfat" USAGE="filesystem" The next time the camera is plugged in it becomes available as "VTech 1070". ** Attachment added: "Superblock of Kidizoom internal disk" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/500398/+attachment/1803713/+files/kidizoom.sb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500398 Title: Vtech Kidizoom camera USB doesn't mount -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315591] Re: LD_LIBRARY_PATH set in ~/.profile doesn't stick
As a workaround, I just comment out "use-ssh-agent" in /etc/X11/Xsession.options. As I use Xubuntu, the XFCE startup launches "ssh-agent" anyway, I am still able to use "ssh-add" with no loss of functionality. -- LD_LIBRARY_PATH set in ~/.profile doesn't stick https://bugs.launchpad.net/bugs/315591 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 389783] Re: after signing in in pidgin chat, it does not connect but appears as "INVISIBLE/AVAILABLE CONNECTING"
The Pidgin support page (http://www.pidgin.im/support/) has a link to "Pidgin cannot connect to Yahoo!" (http://www.celticwolf.com/useful- information/faqs/26-pidgin-yahoo). Yahoo! appears to be upgrading their servers to a new version of their software. This new version requires a new authentication method. The latest version of Pidgin, 2.5.6, does not support this new authentication method. The next version, 2.6.0, will, but it has not yet been released. -- after signing in in pidgin chat, it does not connect but appears as "INVISIBLE/AVAILABLE CONNECTING" https://bugs.launchpad.net/bugs/389783 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156814] Keyboard shortcut "Control-Escape" no longer functions
Public bug reported: Binary package hint: xfce4-mcs-plugins I am using the default keyboard shortcuts "/usr/share/xfce-mcs- plugins/shortcuts/default.xml", which includes the setting: I can also see this setting when I open "Keyboard Settings" from the "Settings Menu". After upgrading from Feisty Fawn to Gutsy Gibbon, hitting "Control+Escape" no longer displays the XFCE menu. If I run the command "xfce4-popup-menu" directly, the XFCE menu is working, so the fault appears to be the recognition of the keyboard shortcut. ** Affects: xfce-mcs-plugins (Ubuntu) Importance: Undecided Status: New -- Keyboard shortcut "Control-Escape" no longer functions https://bugs.launchpad.net/bugs/156814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111042] Re: ipw3945d not started at boot
Marking as "Rejected", as this is not a problem with the package, but with my particular installation. ** Changed in: linux-restricted-modules-2.6.20 (Ubuntu) Status: Unconfirmed => Rejected -- ipw3945d not started at boot https://bugs.launchpad.net/bugs/111042 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111042] Re: ipw3945d not started at boot
I've looked into this further, and found the cause of the problem. The ipw3945 module is not loaded by the initrd as I originally suspected, but by udevtrigger from "/etc/rcS.d/S10udev". At this point "/" is mounted read-only. The daemon was failing to start, due to not being able to write "/var/run/ipw3945d.pid". I had installed Feisty with "/var" as a separate partition, so there was no "/var/run" directory on the root filesystem, so "/var/run" did not get mounted as a writeable tmpfs mount. I corrected this by creating the "/var/run" directory on the root filesystem, and now the regulatory daemon is started at boot. -- ipw3945d not started at boot https://bugs.launchpad.net/bugs/111042 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111042] ipw3945d not started at boot
Public bug reported: Binary package hint: linux-restricted-modules-2.6.20-15-generic The regulatory daemon /sbin/ipw3945d-$(uname -r) is not started when the machine (Dell D620) is booted although the kernel module ipw3945.ko is loaded. This means that the wireless adaptor does not work. I either have to rmmod/modprobe the ipw3945 kernel module, or manually start the daemon. I suspect that the reason for this problem is that the kernel module is loaded by the "initrd", and the daemon is not available to start at that time. I previously had 6.10 installed, and did not need to start the daemon by hand. However, I don't know if this is due to the upgrade, or to the fact that I am now using "cryptroot". ** Affects: linux-restricted-modules-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- ipw3945d not started at boot https://bugs.launchpad.net/bugs/111042 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
