[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: openvswitch (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  Fix Committed
Status in edk2 source package in Focal:
  Fix Committed
Status in libslirp source package in Focal:
  Fix Committed
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  Fix Committed
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  Fix Committed
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  Fix Committed
Status in spice source package in Focal:
  Fix Committed
Status in spice-protocol source package in Focal:
  Fix Committed
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  Fix Committed
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  Won't Fix
Status in openvswitch source package in Jammy:
  Fix Committed
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: dpdk (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: libvirt-python (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: openvswitch (Ubuntu Focal)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  Fix Committed
Status in edk2 source package in Focal:
  Fix Committed
Status in libslirp source package in Focal:
  Fix Committed
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  Fix Committed
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  In Progress
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  Fix Committed
Status in spice source package in Focal:
  Fix Committed
Status in spice-protocol source package in Focal:
  Fix Committed
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  Fix Committed
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  Won't Fix
Status in openvswitch source package in Jammy:
  Fix Committed
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: edk2 (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: libslirp (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: seabios (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: spice (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: spice-protocol (Ubuntu Focal)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  Fix Committed
Status in libslirp source package in Focal:
  Fix Committed
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  Fix Committed
Status in spice source package in Focal:
  Fix Committed
Status in spice-protocol source package in Focal:
  Fix Committed
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  Fix Committed
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  Won't Fix
Status in openvswitch source package in Jammy:
  Fix Committed
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: dpdk (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: openvswitch (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  Fix Committed
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  Won't Fix
Status in openvswitch source package in Jammy:
  Fix Committed
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: meson (Ubuntu Jammy)
   Status: New => Won't Fix

** Changed in: openvswitch (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: spice-protocol (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: virglrenderer (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: virt-manager (Ubuntu Jammy)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  Won't Fix
Status in openvswitch source package in Jammy:
  In Progress
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  Fix Committed
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  Fix Committed
Status in virt-manager source package in Jammy:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: spice-vdagent (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Changed in: virt-manager (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  Fix Committed
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  In Progress

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: rdma-core (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: spice-vdagent (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  Fix Committed
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  In Progress
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  New

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: edk2 (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: spice (Ubuntu Jammy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  Fix Committed
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  New
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  Fix Committed
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  New
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  New

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Changed in: dpdk (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: libslirp (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: libvirt (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: libvirt-python (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: qemu (Ubuntu Jammy)
   Status: New => Fix Committed

** Changed in: seabios (Ubuntu Jammy)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  In Progress
Status in edk2 source package in Jammy:
  New
Status in libslirp source package in Jammy:
  Fix Committed
Status in libvirt source package in Jammy:
  Fix Committed
Status in libvirt-python source package in Jammy:
  Fix Committed
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  Fix Committed
Status in rdma-core source package in Jammy:
  New
Status in seabios source package in Jammy:
  Fix Committed
Status in spice source package in Jammy:
  New
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  New
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  New

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1875669] Re: autopkgtest failures

[Bryce Harrington]

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1875669

Title:
  autopkgtest failures

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  [impact]

  gvfs autopkgtests are highly flaky and fail across different
  releases/archs for multiple different reasons.  It's unclear if the
  failures are actual package bugs, or just testcase bugs.

  [test case]

  look at the autopkgtest results:
  http://autopkgtest.ubuntu.com/packages/gvfs

  [regression potential]

  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1875669/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1713098] Re: Frequent DEP8 test failures related to ftp

[Bryce Harrington]

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1713098

Title:
  Frequent DEP8 test failures related to ftp

Status in gvfs package in Ubuntu:
  Fix Committed

Bug description:
  There are somewhat constant, but intermittent, DEP8 test failures in the gvfs 
package. They seem to always be around ftp:
  tp:// anonymous (API with flag) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_api_user (__main__.Ftp)
  ftp:// anonymous (API with user) ... ok
  test_anonymous_cli_option (__main__.Ftp)
  ftp:// anonymous (CLI with option) ... Error mounting location: Location is 
already mounted
  ERROR

  - dbus stdout -

  - dbus stderr -

  
  test_anonymous_cli_user (__main__.Ftp)
  ftp:// anonymous (CLI with user) ... ok
  test_authenticated_api (__main__.Ftp)
  ftp:// authenticated (API) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  test_authenticated_cli (__main__.Ftp)
  ftp:// authenticated (CLI) ... FAIL

  - dbus stdout -

  - dbus stderr -

  
  Here is a link: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/g/gvfs/20170825_135452_c32a9@/log.gz

  This bug is to investigate these ftp tests, determine why they are
  flaky, and fix them if possible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF

[Bryce Harrington]

** Summary changed:

- Backport packages from mantic to server-backports PPA for focal and jammy
+ Backport packages from noble(-devel) to server-backports PPA for focal and 
jammy, post-FF

** Changed in: dpdk (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.02

** Changed in: dpdk (Ubuntu)
Milestone: ubuntu-24.02 => ubuntu-24.03

** Changed in: libslirp (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: libvirt (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: libvirt-python (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: meson (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: openvswitch (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: qemu (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: rdma-core (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: seabios (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: spice (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: spice-protocol (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: spice-vdagent (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: virglrenderer (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: virt-manager (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

** Changed in: edk2 (Ubuntu)
Milestone: ubuntu-23.11 => ubuntu-24.03

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2040472

Title:
  Backport packages from noble(-devel) to server-backports PPA for focal
  and jammy, post-FF

Status in dpdk package in Ubuntu:
  New
Status in edk2 package in Ubuntu:
  New
Status in libslirp package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New
Status in libvirt-python package in Ubuntu:
  New
Status in meson package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  New
Status in rdma-core package in Ubuntu:
  New
Status in seabios package in Ubuntu:
  New
Status in spice package in Ubuntu:
  New
Status in spice-protocol package in Ubuntu:
  New
Status in spice-vdagent package in Ubuntu:
  New
Status in virglrenderer package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  New
Status in dpdk source package in Focal:
  New
Status in edk2 source package in Focal:
  New
Status in libslirp source package in Focal:
  New
Status in libvirt source package in Focal:
  New
Status in libvirt-python source package in Focal:
  New
Status in meson source package in Focal:
  New
Status in openvswitch source package in Focal:
  New
Status in qemu source package in Focal:
  New
Status in rdma-core source package in Focal:
  New
Status in seabios source package in Focal:
  New
Status in spice source package in Focal:
  New
Status in spice-protocol source package in Focal:
  New
Status in spice-vdagent source package in Focal:
  New
Status in virglrenderer source package in Focal:
  New
Status in virt-manager source package in Focal:
  New
Status in dpdk source package in Jammy:
  New
Status in edk2 source package in Jammy:
  New
Status in libslirp source package in Jammy:
  New
Status in libvirt source package in Jammy:
  New
Status in libvirt-python source package in Jammy:
  New
Status in meson source package in Jammy:
  New
Status in openvswitch source package in Jammy:
  New
Status in qemu source package in Jammy:
  New
Status in rdma-core source package in Jammy:
  New
Status in seabios source package in Jammy:
  New
Status in spice source package in Jammy:
  New
Status in spice-protocol source package in Jammy:
  New
Status in spice-vdagent source package in Jammy:
  New
Status in virglrenderer source package in Jammy:
  New
Status in virt-manager source package in Jammy:
  New

Bug description:
  Backport the following packages to the server-backports PPA for
  noble:* ['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-
  python', 'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice',
  'spice-protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2039460] Re: Please merge network-manager-applet 1.34.0-1 from Debian unstable

[Bryce Harrington]

Hi Nathan,

In your changelog entry, it shows 'UNRELEASED' as the distro, but that should 
be 'noble' now. 
It would also be worthwhile to mention this bug # in the changelog, so it 
should look like:


+network-manager-applet (1.34.0-1ubuntu1) noble; urgency=medium
+
+  * Merge with Debian (LP: #2039460). Remaining changes:
+- d/control:
+  + Build-Depend on on dh-sequence-translations


I would also recommend that you set up a PPA and upload the package
there, to verify the build against Noble.

Please re-subscribe sponsors once this is fixed up.  Thanks!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2039460

Title:
  Please merge network-manager-applet 1.34.0-1 from Debian unstable

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Builds successfully in Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2039460/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2040472] [NEW] Backport packages from mantic to server-backports PPA for focal and jammy

[Bryce Harrington]

Public bug reported:

Backport the following packages to the server-backports PPA for noble:*
['meson', 'dpdk', 'edk2', 'libslirp', 'libvirt', 'libvirt-python',
'openvswitch', 'qemu', 'rdma-core', 'seabios', 'spice', 'spice-
protocol', 'spice-vdagent', 'virglrenderer', 'virt-manager']

** Affects: dpdk (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: edk2 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: libslirp (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: libvirt (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: libvirt-python (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: meson (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: openvswitch (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qemu (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: rdma-core (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: seabios (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: spice (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: spice-protocol (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: spice-vdagent (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: virglrenderer (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: virt-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: dpdk (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: edk2 (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: libslirp (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: libvirt (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: libvirt-python (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: meson (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: openvswitch (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: qemu (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: rdma-core (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: seabios (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: spice (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: spice-protocol (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: spice-vdagent (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: virglrenderer (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: virt-manager (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: dpdk (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: edk2 (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: libslirp (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: libvirt (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: libvirt-python (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: meson (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: openvswitch (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: qemu (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: rdma-core (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: seabios (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: spice (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: spice-protocol (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: spice-vdagent (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: virglrenderer (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: virt-manager (Ubuntu Jammy)
 Importance: Undecided
 Status: New


** Tags: needs-ppa-backport

** Changed in: dpdk (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: edk2 (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: libslirp (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: libvirt (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: libvirt-python (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: meson (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: openvswitch (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: qemu (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: rdma-core (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: seabios (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: spice (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: spice-protocol (Ubuntu)
Milestone: None => ubuntu-23.11

** Changed in: spice-vdagent (Ubuntu)
Milestone: None => ubuntu-23.11

** 

[Desktop-packages] [Bug 2037695] Re: Backport packages to server-backports PPA from lunar

[Bryce Harrington]

** Changed in: openvswitch (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: dpdk (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to spice-vdagent in Ubuntu.
https://bugs.launchpad.net/bugs/2037695

Title:
  Backport packages to server-backports PPA from lunar

Status in dpdk package in Ubuntu:
  Fix Committed
Status in edk2 package in Ubuntu:
  Fix Committed
Status in libslirp package in Ubuntu:
  Fix Committed
Status in libvirt package in Ubuntu:
  Fix Committed
Status in libvirt-python package in Ubuntu:
  Fix Committed
Status in meson package in Ubuntu:
  Fix Committed
Status in openvswitch package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Fix Committed
Status in rdma-core package in Ubuntu:
  Fix Committed
Status in seabios package in Ubuntu:
  Fix Committed
Status in spice package in Ubuntu:
  Fix Committed
Status in spice-protocol package in Ubuntu:
  Fix Committed
Status in spice-vdagent package in Ubuntu:
  Fix Committed
Status in virglrenderer package in Ubuntu:
  Fix Committed
Status in virt-manager package in Ubuntu:
  Fix Committed

Bug description:
  Backport the following packages to the server-backports PPA from
  lunar:

  * dpdk
  * edk2
  * libslirp
  * libvirt
  * libvirt-python
  * openvswitch
  * qemu
  * rdma-core
  * seabios
  * spice
  * spice-protocol
  * spice-vdagent
  * virglrenderer
  * virt-manager

  The following build dependencies for the above will also require
  backporting:

  * meson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2037695/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 2037695] [NEW] Backport packages to server-backports PPA from lunar

[Bryce Harrington]

Public bug reported:

Backport the following packages to the server-backports PPA from lunar:

* dpdk
* edk2
* libslirp
* libvirt
* libvirt-python
* openvswitch
* qemu
* rdma-core
* seabios
* spice
* spice-protocol
* spice-vdagent
* virglrenderer
* virt-manager

The following build dependencies for the above will also require
backporting:

* meson

** Affects: dpdk (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: In Progress

** Affects: edk2 (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: libslirp (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: libvirt (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: libvirt-python (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: meson (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: openvswitch (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: In Progress

** Affects: qemu (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: rdma-core (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: seabios (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: spice (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: spice-protocol (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: spice-vdagent (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: virglrenderer (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed

** Affects: virt-manager (Ubuntu)
 Importance: Wishlist
 Assignee: Bryce Harrington (bryce)
 Status: Fix Committed


** Tags: needs-ppa-backport

** Changed in: dpdk (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: edk2 (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: libslirp (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: libvirt (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: libvirt-python (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: meson (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: openvswitch (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: qemu (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: rdma-core (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: seabios (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: spice (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: spice-protocol (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: spice-vdagent (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: virglrenderer (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: virt-manager (Ubuntu)
Milestone: None => ubuntu-23.05

** Changed in: dpdk (Ubuntu)
   Importance: Undecided => High

** Changed in: dpdk (Ubuntu)
   Status: New => In Progress

** Changed in: dpdk (Ubuntu)
Milestone: ubuntu-23.05 => ubuntu-23.10

** Changed in: dpdk (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: edk2 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: edk2 (Ubuntu)
   Status: New => Fix Committed

** Changed in: edk2 (Ubuntu)
Milestone: ubuntu-23.05 => ubuntu-23.10

** Changed in: edk2 (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: libslirp (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: libslirp (Ubuntu)
   Status: New => Fix Committed

** Changed in: libslirp (Ubuntu)
Milestone: ubuntu-23.05 => ubuntu-23.10

** Changed in: libslirp (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: libvirt (Ubuntu)
   Importance: Undecided => Low

** Changed in: libvirt (Ubuntu)
   Status: New => Fix Committed

** Changed in: libvirt (Ubuntu)
Milestone: ubuntu-23.05 => ubuntu-23.10

** Changed in: libvirt (Ubuntu)
 Assignee: (unassigned) => Bryce Harrington (bryce)

** Changed in: libvirt-python (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: libvirt-python (Ubuntu)
   Status: New => Fix Committed

** Changed in: libvirt-python (Ubuntu)
Milestone: ubuntu-23.05 => ubuntu-23.10

** Changed in: libvirt-python (Ubuntu

[Desktop-packages] [Bug 2003833] [NEW] colord migration blocked by impossible depends on argyll

[Bryce Harrington]

Public bug reported:

colord recently re-enabled argyll support. Unfortunately since argyll is
in universe and colord is in main, this is causing an 'impossible
depends' migration error for colord.

colord-sensor-argyll/amd64 in main cannot depend on argyll in universe
Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64

colord (1.4.6-2) unstable; urgency=medium

  * debian/control:
- Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355)
- Bump Standards-Version to 4.6.1 (no changes needed)
  * debian/rules:
  * debian/control:
  * debian/not-installed:
- Re-enable Argyll support. Argyll no longer appears in danger of
  being removed from the archive.
  * debian/copyright:
- Fix misspelling of Richard Hughes' name
- Drop no-longer-necessary Files: stanzas
- Include full license details of data/profiles

 -- Christopher James Halse Rogers  Tue, 01 Nov 2022
11:02:35 +0100

There is a MIR for argyll (LP: #821883) which could be a solution for
this issue.

** Affects: colord (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuses

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/2003833

Title:
  colord migration blocked by impossible depends on argyll

Status in colord package in Ubuntu:
  New

Bug description:
  colord recently re-enabled argyll support. Unfortunately since argyll
  is in universe and colord is in main, this is causing an 'impossible
  depends' migration error for colord.

  colord-sensor-argyll/amd64 in main cannot depend on argyll in universe
  Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64

  colord (1.4.6-2) unstable; urgency=medium

    * debian/control:
  - Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355)
  - Bump Standards-Version to 4.6.1 (no changes needed)
    * debian/rules:
    * debian/control:
    * debian/not-installed:
  - Re-enable Argyll support. Argyll no longer appears in danger of
    being removed from the archive.
    * debian/copyright:
  - Fix misspelling of Richard Hughes' name
  - Drop no-longer-necessary Files: stanzas
  - Include full license details of data/profiles

   -- Christopher James Halse Rogers  Tue, 01 Nov 2022
  11:02:35 +0100

  There is a MIR for argyll (LP: #821883) which could be a solution for
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/2003833/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 821883] Re: [MIR] argyll

[Bryce Harrington]

colord recently re-enabled argyll support.  Unfortunately since argyll
is in universe and colord is in main, this is causing an 'impossible
depends' migration error for colord.

colord-sensor-argyll/amd64 in main cannot depend on argyll in universe 
Impossible Depends: colord -> argyll/2.3.1+repack-1ubuntu1/amd64 

colord (1.4.6-2) unstable; urgency=medium

  * debian/control:
- Build-Depend on polkitd. Fixes FTBFS (Closes: #1022355)
- Bump Standards-Version to 4.6.1 (no changes needed)
  * debian/rules:
  * debian/control:
  * debian/not-installed:
- Re-enable Argyll support. Argyll no longer appears in danger of
  being removed from the archive.
  * debian/copyright:
- Fix misspelling of Richard Hughes' name
- Drop no-longer-necessary Files: stanzas
- Include full license details of data/profiles

 -- Christopher James Halse Rogers   Tue, 01 Nov 2022
11:02:35 +0100

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/821883

Title:
  [MIR] argyll

Status in argyll package in Ubuntu:
  Incomplete
Status in colord package in Ubuntu:
  New

Bug description:
  Note this MIR is for both argyll and libicc2 (both packages are
  currently in Universe). With the most recent argyll package the binary
  packages of argyll and libicc2 are now all produced by the argyll
  source package. We followed Debian to unsplit here as the upstream
  source for both is argyll. The libicc2 source package in Universe can
  get dropped.

  Availability: Currently available in Universe, building on all
  currently supported architectures, see
  https://launchpad.net/ubuntu/+source/argyll

  Rationale: In Oneiric we want to introduce ICC-based color management
  on the operating system level, using the same architecture as Fedora
  does. argyll (support for color calibration) and libicc2 (ICC handling
  library) are part of this architecture. Therefore we need them in
  Main. This MIR is a work item of the following Blueprint:

  https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-icc-color-
  management

  According to the Blueprint additional demand on CD space for the whole
  introduction of color management is around 300K only.

  Security: No security vulnerabilities known at CVE and Secunia for the
  current version (1.3.3), vulnerabilities of older versions are all
  fixed, no SUID components, no daemons.

  Quality assurance: Installs without debconf questions. The package is
  maintained upstream as new releases occur regularly and they get
  packaged for Debian by Roland Mas (see debian/changelog).

  UI standards: The package are a library and command line utilities.
  The complete upstream documentation is available in
  /usr/share/doc/argyll/. Each command shows a help page by calling it
  without parameters.

  Dependencies: Depends only on standard libraries for X and images.
  They are all in Main.

  Maintenance: See "Quality assurance".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/821883/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 821883] Re: [MIR] argyll

[Bryce Harrington]

** Also affects: colord (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/821883

Title:
  [MIR] argyll

Status in argyll package in Ubuntu:
  Incomplete
Status in colord package in Ubuntu:
  New

Bug description:
  Note this MIR is for both argyll and libicc2 (both packages are
  currently in Universe). With the most recent argyll package the binary
  packages of argyll and libicc2 are now all produced by the argyll
  source package. We followed Debian to unsplit here as the upstream
  source for both is argyll. The libicc2 source package in Universe can
  get dropped.

  Availability: Currently available in Universe, building on all
  currently supported architectures, see
  https://launchpad.net/ubuntu/+source/argyll

  Rationale: In Oneiric we want to introduce ICC-based color management
  on the operating system level, using the same architecture as Fedora
  does. argyll (support for color calibration) and libicc2 (ICC handling
  library) are part of this architecture. Therefore we need them in
  Main. This MIR is a work item of the following Blueprint:

  https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-icc-color-
  management

  According to the Blueprint additional demand on CD space for the whole
  introduction of color management is around 300K only.

  Security: No security vulnerabilities known at CVE and Secunia for the
  current version (1.3.3), vulnerabilities of older versions are all
  fixed, no SUID components, no daemons.

  Quality assurance: Installs without debconf questions. The package is
  maintained upstream as new releases occur regularly and they get
  packaged for Debian by Roland Mas (see debian/changelog).

  UI standards: The package are a library and command line utilities.
  The complete upstream documentation is available in
  /usr/share/doc/argyll/. Each command shows a help page by calling it
  without parameters.

  Dependencies: Depends only on standard libraries for X and images.
  They are all in Main.

  Maintenance: See "Quality assurance".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argyll/+bug/821883/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1398805] Re: redshift fails to start geoclue provider after resuming network connection / hangs for 25s

[Bryce Harrington]

This link suggests redshift may now require installing geoclue-2:
https://askubuntu.com/questions/752406/is-it-possible-to-workaround-the-redshift-geoclue-bug?rq=1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue in Ubuntu.
https://bugs.launchpad.net/bugs/1398805

Title:
  redshift fails to start geoclue provider after resuming network
  connection / hangs for 25s

Status in geoclue package in Ubuntu:
  Confirmed
Status in redshift package in Ubuntu:
  Confirmed

Bug description:
  `redshift -l geoclue -p` hangs after resuming network operation.

  This happens after resuming from hibernation, but can be reproduced by
  disabling and re-enabling the network via network-manager.

  strace shows:

  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\1\1\214\0\0\0\2\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\10\0\0\0AddMatch\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 144}, 
{"\207\0\0\0type='signal',sender='org.freedesktop.Geoclue.Master',path='/org/freedesktop/Geoclue/Master',interface='org.freedesktop.Geoclue.Master'\0",
 140}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 284
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\1\1\256\0\0\0\3\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\10\0\0\0AddMatch\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 144}, 
{"\251\0\0\0type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Geoclue.Master'\0",
 174}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 318
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\0\1#\0\0\0\4\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\f\0\0\0GetNameOwner\0\0\0\0\10\1g\0\1s\0\0",
 144}, {"\36\0\0\0org.freedesktop.Geoclue.Master\0", 35}], msg_controllen=0, 
msg_flags=0}, MSG_NOSIGNAL) = 179
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\0\1\0\0\0\0\5\0\0\0\207\0\0\0\1\1o\0\37\0\0\0/org/freedesktop/Geoclue/Master\0\6\1s\0\36\0\0\0org.freedesktop.Geoclue.Master\0\0\2\1s\0\36\0\0\0org.freedesktop.Geoclue.Master\0\0\3\1s\0\6\0\0\0Create\0\0",
 152}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 152
  poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}])
  recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{"l\2\1\1\n\0\0\0\3\0\0\0=\0\0\0\6\1s\0\6\0\0\0:1.411\0\0\5\1u\0\4\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\5\0\0\0:1.43\0",
 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 90
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  recvmsg(3, 0x7fffcd24f170, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource 
temporarily unavailable)
  poll([{fd=3, events=POLLIN}], 1, 25000

  # Here it hangs

  ) = 0 (Timeout)
  open("/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  fstat(2, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 56), ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f3d2998c000
  write(2, "Unable to obtain master client: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.\n", 243Unable to obtain master client: Did 
not receive a reply. Possible causes include: the remote application did not 
send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  ) = 243
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f3d2998b000
  read(5, "# Locale name alias data base.\n# Copyright (C) 
1996-2001,2003,2007 Free Software Foundation, Inc.\n#\n# This program is free 
software; you can redistribute it and/or modify\n# it under the terms of the 
GNU General Public License as published by\n# the Free Software Foundation; 
either version 2, or (at your option)\n# any later version.\n#\n# This program 
is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; 
without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.  See the\n# GNU General Public License for more 
details.\n#\n# You should have received a copy of the GNU General Public 
License\n# along with this program; if not, write to the Free Software\n# 
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.\n\n# 
The format of this file is the 

[Desktop-packages] [Bug 1690836] Re: libnl-genl-3.0 memory leak

[Bryce Harrington]

Xenial and trusty have reached end of standard support

** Changed in: libnl3 (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

** Changed in: libnl3 (Ubuntu Xenial)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1690836

Title:
  libnl-genl-3.0 memory leak

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Won't Fix
Status in libnl3 source package in Xenial:
  Won't Fix

Bug description:
  It seems that there is a memory leak in the libnl-genl-3.0 library.
  The memory-leak can be seen when the function genl_ctrl_resolve() fails.

  It seems that this function copy a buffer and forget to deallocate it 
properly:
    258 cb = nl_cb_clone(orig); // buffer copied not freed

  -
  The following attached source-code can help you to reproduce this behavior on 
Ubuntu 14.04.
  It forces an issue on the genl_ctrl_resolve by asking an unknown 
netlink-family.

  To compile program:
  g++ -std=c++11 main.cpp $(pkg-config --cflags --libs libnl-3.0 
libnl-genl-3.0) -o main

  To detect memory-leak using Valgrind:
  valgrind --leak-check=full ./main

  -
  Executing it on Debian 8.0 shows "no memory leak":
  sylvain@debian:~/test$ lsb_release -rd
  Description:  Debian GNU/Linux 8.8 (jessie)
  Release:  8.8

  sylvain@debian:~/test$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs 
libnl-3.0 libnl-genl-3.0) -o main
  sylvain@debian:~/test$ valgrind --leak-check=full ./main
  ==26390== Memcheck, a memory error detector
  ==26390== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
  ==26390== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
  ==26390== Command: ./main
  ==26390==
  start test
  error: can't retrieve the netlink-family id
  end test
  ==26390==
  ==26390== HEAP SUMMARY:
  ==26390== in use at exit: 0 bytes in 0 blocks
  ==26390==   total heap usage: 13 allocs, 13 frees, 22,142 bytes allocated
  ==26390==
  ==26390== All heap blocks were freed -- no leaks are possible
  ==26390==
  ==26390== For counts of detected and suppressed errors, rerun with: -v
  ==26390== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

  -
  Executing it on Ubuntu 14.04 shows a memory leak:
  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  ubuntu@ubuntu:~$ g++ -std=c++11 main.cpp $(pkg-config --cflags --libs 
libnl-3.0 libnl-genl-3.0) -o main
  ubuntu@ubuntu:~$ valgrind --leak-check=full ./main
  ==37377== Memcheck, a memory error detector
  ==37377== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
  ==37377== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
  ==37377== Command: ./main
  ==37377==
  start test
  error: can't retrieve the netlink-family id
  end test
  ==37377==
  ==37377== HEAP SUMMARY:
  ==37377== in use at exit: 224 bytes in 1 blocks
  ==37377==   total heap usage: 13 allocs, 12 frees, 22,142 bytes allocated
  ==37377==
  ==37377== 224 bytes in 1 blocks are definitely lost in loss record 1 of 1
  ==37377==at 0x4C2CC70: calloc (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
  ==37377==by 0x5048FAA: nl_cb_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
  ==37377==by 0x504CB1E: nl_socket_alloc (in 
/lib/x86_64-linux-gnu/libnl-3.so.200.16.1)
  ==37377==by 0x4012E3: A::Init() (in /home/ubuntu/main)
  ==37377==by 0x401189: main (in /home/ubuntu/main)
  ==37377==
  ==37377== LEAK SUMMARY:
  ==37377==definitely lost: 224 bytes in 1 blocks
  ==37377==indirectly lost: 0 bytes in 0 blocks
  ==37377==  possibly lost: 0 bytes in 0 blocks
  ==37377==still reachable: 0 bytes in 0 blocks
  ==37377== suppressed: 0 bytes in 0 blocks
  ==37377==
  ==37377== For counts of detected and suppressed errors, rerun with: -v
  ==37377== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  Thanks,
  Sylvain Trinquet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1690836/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

That's true that it works fine in jammy, but the breakage does still
occur sometimes on focal.  In case others run across this issue on
focal, probably worth keeping this bug report open for reference.

** Also affects: libsoup2.4 (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  Fix Released
Status in libsoup2.4 source package in Focal:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
_read, _written, 
);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1869734] Re: openjade segfaults on all arch

[Bryce Harrington]

** Changed in: pgpool2 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openjade in Ubuntu.
https://bugs.launchpad.net/bugs/1869734

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Fix Released
Status in pgpool2 package in Ubuntu:
  Fix Released
Status in openjade package in Debian:
  Fix Released

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

hinted for now:

https://git.launchpad.net/~ubuntu-release/britney/+git/hints-
ubuntu/commit/?id=90bbdc608590c7b01f81619dae973bd8c26dd5b7

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
_read, _written, 
);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

As can be seen here, the package doesn't pass its own tests even when
triggered against only itself:

https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/amd64/libs/libsoup2.4/20211004_230503_77208@/log.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
_read, _written, 
);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
_read, _written, 
);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1945713] [NEW] Flaky test brotli/basic on focal amd64?

[Bryce Harrington]

Public bug reported:

The brotli/basic test case periodically fails.  It appears that a few
retriggers can result in a pass:

https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

The failures look like this in autopkgtest logs:

ERROR:../tests/brotli-decompressor-test.c:59:test_brotli: assertion
failed ((char*)out_bytes->data == contents): ("***\nU" == "***\n")

I've replaced most of the text with '***' to highlight the difference is
a 'U' character appended.

The test case is essentially doing a decompression of 'brotli-
data/compressed.br' and comparing that it matches 'brotli-
data/uncompressed.txt'.  I've done this manually using the brotli cli,
and the files do indeed have the same content.  I've also built the
package and run the test case locally in a focal lxc container on amd64:

$ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
$ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

I left that to run several hundred cycles but no failures reported at
all.

There are a bunch of instances of this failure, here's a few for
reference:


https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz

https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz

https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

That last link is the earliest instance I've been able to find.

You'll notice in the second two links they also have a failure "not ok 2
/ssl/tls-interaction", but the first link shows only the brotli failure.

Interestingly, I've not found instances of this failure against other
architectures than amd64, nor have I seen it on releases other than
focal.  No dice from googling for bug reports or other reports of test
failures with libsoup2.4 + brotli.

The test's code is doing this, basically:

SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
do {
result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
  _read, _written, 
);
g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
length -= bytes_read;

} while (result == G_CONVERTER_CONVERTED);

soup_brotli_decompressor's code is here:

https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
decoder/soup-brotli-decompressor.c

But I'm not spotting anything that would obviously cause a 'U' to be
randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

There are some interesting bug reports in GNOME about brotli in
libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
match this.

** Affects: libsoup2.4 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first 

[Desktop-packages] [Bug 1939065] Re: autopkgtest failure in 0002-benchmark test

[Bryce Harrington]

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1939065

Title:
  autopkgtest failure in 0002-benchmark test

Status in dbus-cpp package in Ubuntu:
  New

Bug description:
  From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks
  like the build failed on all architectures except armhf, and on armhf
  there was a test failure:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz

  autopkgtest [17:31:26]: test 0002-benchmark: [---
  DBus daemon: 
unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670

  (dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to 
start process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to 
execute child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No 
such file or directory)
  task-0: Shutting down
  DBus daemon: Shutdown
  autopkgtest [17:31:29]: test 0002-benchmark: ---]
  0002-benchmark   FAIL non-zero exit status 253

  
  Debian is seeing the same test failures in their CI framework:

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz
  
https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1939067] [NEW] FTBFS 5.0.3-2 due to missing symbols

[Bryce Harrington]

Public bug reported:

Most architectures are failing to build 5.0.3-2.
I've reproduced failure locally:

dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libdbus-cpp5/DEBIAN/symbols doesn't match 
completely debian/libdbus-cpp5.symbols
--- debian/libdbus-cpp5.symbols (libdbus-cpp5_5.0.3-2_amd64)
+++ dpkg-gensymbolse5FPkP   2021-08-05 21:54:51.508307074 +
@@ -218,10 +218,10 @@
  
_ZTSZN4core4dbus7Fixture7Private6SystemC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base
 5.0.1
  
_ZTSZN4core4dbus7Fixture7Private7SessionC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base
 5.0.1
  _ZTSZN4core4dbus7Message7PrivateC4EP11DBusMessagebEUlS4_E_@Base 5.0.1
- _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1
- _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1
- _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1
- 
_ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base
 5.0.1
+#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1
+#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1
+#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1
+#MISSING: 5.0.3-2# 
_ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base
 5.0.1
  _ZTVN4core4dbus7FixtureE@Base 5.0.1
  _ZZN4core4dbus4DBus21GetConnectionUnixUser4nameB5cxx11EvE1s@Base 5.0.1
  _ZZN4core4dbus4DBus26GetConnectionUnixProcessID4nameB5cxx11EvE1s@Base 5.0.1
mv debian/.debhelper/generated/libdbus-cpp5/triggers.new 
debian/.debhelper/generated/libdbus-cpp5/triggers
rm -f debian/dbus-cpp-bin/DEBIAN/shlibs
rm -f debian/libdbus-cpp-dev/DEBIAN/shlibs
rm -f debian/dbus-cpp-dev-examples/DEBIAN/shlibs
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:16: binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
blame: ./dbus-cpp_5.0.3-2.dsc
badpkg: rules build failed with exit code 2
autopkgtest [21:54:51]: ERROR: erroneous package: rules build failed with exit 
code 2

---

This release includes this modification to the symbols file:

diff --git a/debian/libdbus-cpp5.symbols b/debian/libdbus-cpp5.symbols
index d96a2d8..f84a0c5 100644
--- a/debian/libdbus-cpp5.symbols
+++ b/debian/libdbus-cpp5.symbols
@@ -1,5 +1,6 @@
 # SymbolsHelper-Confirmed: 5.0.1 amd64 armel armhf i386 m68k mipsel x32
 libdbus-cpp.so.5 libdbus-cpp5 #MINVER#
+* Build-Depends-Package: libdbus-cpp-dev
  
_ZN4core4dbus14ServiceWatcherC1ESt10shared_ptrINS0_6ObjectEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN$
  
_ZN4core4dbus14ServiceWatcherC2ESt10shared_ptrINS0_6ObjectEERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEN$
  _ZN4core4dbus3Bus12remove_matchERKNS0_9MatchRuleE@Base 5.0.1

However, reverting this change has no effect; the build still fails the
same way.

** Affects: dbus-cpp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuses

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1939067

Title:
  FTBFS 5.0.3-2 due to missing symbols

Status in dbus-cpp package in Ubuntu:
  New

Bug description:
  Most architectures are failing to build 5.0.3-2.
  I've reproduced failure locally:

  dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libdbus-cpp5/DEBIAN/symbols doesn't match 
completely debian/libdbus-cpp5.symbols
  --- debian/libdbus-cpp5.symbols (libdbus-cpp5_5.0.3-2_amd64)
  +++ dpkg-gensymbolse5FPkP 2021-08-05 21:54:51.508307074 +
  @@ -218,10 +218,10 @@

_ZTSZN4core4dbus7Fixture7Private6SystemC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base
 5.0.1

_ZTSZN4core4dbus7Fixture7Private7SessionC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcUlSB_SB_E_@Base
 5.0.1
_ZTSZN4core4dbus7Message7PrivateC4EP11DBusMessagebEUlS4_E_@Base 5.0.1
  - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1
  - _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1
  - _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1
  - 
_ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base
 5.0.1
  +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnedE@Base 5.0.1
  +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors12AlreadyOwnerE@Base 5.0.1
  +#MISSING: 5.0.3-2# _ZTVN4core4dbus3Bus6Errors8NoMemoryE@Base 5.0.1
  +#MISSING: 5.0.3-2# 
_ZTVN4core4dbus5types10ObjectPath6Errors37InvalidObjectPathStringRepresentationE@Base
 5.0.1
_ZTVN4core4dbus7FixtureE@Base 5.0.1
_ZZN4core4dbus4DBus21GetConnectionUnixUser4nameB5cxx11EvE1s@Base 5.0.1
_ZZN4core4dbus4DBus26GetConnectionUnixProcessID4nameB5cxx11EvE1s@Base 5.0.1
mv 

[Desktop-packages] [Bug 1939065] [NEW] autopkgtest failure in 0002-benchmark test

[Bryce Harrington]

Public bug reported:

>From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks
like the build failed on all architectures except armhf, and on armhf
there was a test failure:

https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz

autopkgtest [17:31:26]: test 0002-benchmark: [---
DBus daemon: 
unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670

(dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to start 
process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to execute 
child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No such file 
or directory)
task-0: Shutting down
DBus daemon: Shutdown
autopkgtest [17:31:29]: test 0002-benchmark: ---]
0002-benchmark   FAIL non-zero exit status 253


Debian is seeing the same test failures in their CI framework:

https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz
https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz

** Affects: dbus-cpp (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1939065

Title:
  autopkgtest failure in 0002-benchmark test

Status in dbus-cpp package in Ubuntu:
  New

Bug description:
  From https://launchpad.net/ubuntu/+source/dbus-cpp/5.0.3-2, it looks
  like the build failed on all architectures except armhf, and on armhf
  there was a test failure:

  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/d/dbus-cpp/20210708_173150_9b648@/log.gz

  autopkgtest [17:31:26]: test 0002-benchmark: [---
  DBus daemon: 
unix:abstract=/tmp/dbus-r1vtLBVT2b,guid=9e9dc7c56358b39bba3cf32260e73670

  (dbus-test-runner:1285): libdbustest-WARNING **: 17:31:28.819: Unable to 
start process '/usr/lib/*/dbus-cpp/examples/benchmark/benchmark': Failed to 
execute child process ?/usr/lib/*/dbus-cpp/examples/benchmark/benchmark? (No 
such file or directory)
  task-0: Shutting down
  DBus daemon: Shutdown
  autopkgtest [17:31:29]: test 0002-benchmark: ---]
  0002-benchmark   FAIL non-zero exit status 253

  
  Debian is seeing the same test failures in their CI framework:

  
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/dbus-cpp/14056784/log.gz
  
https://ci.debian.net/data/autopkgtest/unstable/arm64/d/dbus-cpp/14058472/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1939058] [NEW] autopkgtest failure "stacking/override-redirect.metatest" on armhf

[Bryce Harrington]

Public bug reported:

https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz


Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x43
not ok 18 stacking/override-redirect.metatest
   15: stacking: expected='1/2 | 1/1', actual='| 1/1 1/2'

>From the test history on armhf, it appears this particular test case
intermittently passes or fails about half the time.  Other architectures
have been passing all tests reliably without errors.

Presumably the stacking order is non-deterministic on armhf for some
reason?

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuse

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1939058

Title:
  autopkgtest failure "stacking/override-redirect.metatest" on armhf

Status in mutter package in Ubuntu:
  New

Bug description:
  https://autopkgtest.ubuntu.com/results/autopkgtest-
  impish/impish/armhf/m/mutter/20210805_091629_afb25@/log.gz

  
  Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a 
timestamp of 0 for 0x43
  not ok 18 stacking/override-redirect.metatest
 15: stacking: expected='1/2 | 1/1', actual='| 1/1 1/2'

  From the test history on armhf, it appears this particular test case
  intermittently passes or fails about half the time.  Other
  architectures have been passing all tests reliably without errors.

  Presumably the stacking order is non-deterministic on armhf for some
  reason?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939058/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1929246] Re: terminator crashed with SIGSEGV _PyEval_EvalCodeWithName () in libvte-2.91.so.0

[Bryce Harrington]

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1929246

Title:
  terminator crashed with SIGSEGV _PyEval_EvalCodeWithName () in
  libvte-2.91.so.0

Status in terminator package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  I think this crash was not triggered by user activity; I was simply
  editing some python files in emacs like I always do.  The system
  appears to be otherwise fine so it doesn't seem to be a resource
  limitation issue.  Hopefully the stack trace has some clues...

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: terminator 1.91-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94
  Uname: Linux 5.4.0-70-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May 21 12:26:09 2021
  ExecutablePath: /usr/share/terminator/terminator
  InstallationDate: Installed on 2019-12-18 (520 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/terminator
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  SegvAnalysis:
   Segfault happened at: 0x7f321c0259fc:mov0x8(%rax),%rdx
   PC (0x7f321c0259fc) ok
   source "0x8(%rax)" (0x400076) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: terminator
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
   () at /lib/x86_64-linux-gnu/libvte-2.91.so.0
  Title: terminator crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev root sambashare 
sudo
  mtime.conffile..etc.apport.crashdb.conf: 2021-03-30T13:36:30.851500
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1929246/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1869734] Re: openjade segfaults on all arch

[Bryce Harrington]

Unless I've misunderstood, from the last few comments it sounds like this is 
now fixed for hirsute thanks to the sync'd package.
Please reopen if there is any followup work needed.

** Changed in: openjade (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to openjade in Ubuntu.
https://bugs.launchpad.net/bugs/1869734

Title:
  openjade segfaults on all arch

Status in openjade package in Ubuntu:
  Fix Released
Status in pgpool2 package in Ubuntu:
  New
Status in openjade package in Debian:
  Fix Released

Bug description:
  cpaelzer: fun, openjade segfaulting on focal/arm64
  I beg your pardon for my ignorance of the ecosystem, but how is 
this related to postgresql-apt
  for doc generation?
  cpaelzer: the postgresql-9.5 and -9.6 builds fail during doc 
generation on focal/arm64
  everything else (other archs, other dists) is fine
  
https://pgdgbuild.dus.dg-i.net/job/postgresql-9.5-binaries/architecture=arm64,distribution=focal/55/console

  Myon: only on arm64?
  only there, yes

  ./configure && make -C doc/src/sgml all  should reproduce it
  clone and build this branch ? 
https://github.com/postgres/postgres/tree/REL9_5_STABLE
  the crash is in /usr/lib/libostyle.so.1 from libostyle1c2
  here it is
  segfault

  I have this now http://paste.debian.net/1136839/
  https://paste.ubuntu.com/p/CfzrfWkqzs/

  well I wanted to get -O0 to see more int he debugger
  my build worked as well now
  the -O0 openjade installed doesn't segfault
  oh so like my -O0 then
  so maybe we should just always -O0 openjade then?
  TBH who cares about optimization in that
  But its usage is mostly build time and not runtime
  maybe -O0 on arm64 only
  I'm rebulding -O2 again to recheck if that really is it
  and then -O1 to check the in between
  it might "just" need a rebuild

  -O2 re-build segfault
  -O1 (for completeness) rebuild ... seems to hang?
  probably not really relevant
  agreed, but I want to rebuild -O0 again just to see it builds 
and then works
  -O0 on arm64 really seems to be a good choice

  I can try if rebuilding makes it fail on sid
  cpaelzer: recompiling openjade in arm64/sid doesn't make it 
segfault
  so it seems this needs a focal-only fix
  cpaelzer: the openjade segfault is also present in pgpool2, so 
not just in ancient PostgreSQL :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjade/+bug/1869734/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf

[Bryce Harrington]

Thanks Han, that makes sense that the issue is actually in the volume
monitor's (lack of) handling for autofs' transitory nature.  I'll
reassign to that package for further investigation.

** Package changed: autofs (Ubuntu) => gvfs (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1855318

Title:
  autofs tries to find .xdg-volume-info and autorun.inf

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  # automount -f -v
  Starting automounter version 5.1.5, master map /etc/auto.master
  using kernel protocol version 5.05
  mounted indirect on /home//mnt with timeout 300, freq 75 seconds
  attempting to mount entry /home//mnt/.xdg-volume-info
  key ".xdg-volume-info" not found in map source(s).
  failed to mount /home//mnt/.xdg-volume-info
  attempting to mount entry /home//mnt/autorun.inf
  key "autorun.inf" not found in map source(s).
  failed to mount /home//mnt/autorun.inf

  /etc/auto.master:
  +dir:/etc/auto.master.d

  /etc/auto.master.d:
  -rw-r--r-- 1 root root   38 Dez  5 19:10 mnt.autofs

  /etc/auto.master.d/mnt.autofs:
  /home//mnt   file:/etc/auto.mnt

  /etc/auto.mnt:
  G   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sg
  L   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///apps
  M   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///gs
  O   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///media
  P   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///pb
  T   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///ALLG
  V   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///SW2
  W   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sw
  X   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///depot
  Y   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///sct-muc
  Z   -fstype=cifs,multiuser,cruid=$UID,sec=krb5i :///z

  
  Could not find any file "autorun.inf" or ".xdg-volume-info" anywhere on my 
system. Where do these come from?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: autofs 5.1.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Dec  5 19:12:38 2019
  InstallationDate: Installed on 2019-09-09 (87 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   LANGUAGE=de_DE
   TERM=screen
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: autofs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1855318/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

[Bryce Harrington]

>From the upstream bug report, the failure in OsLookupColor() is just a
common point where the system falls over once it's run out of graphics
memory.  There could be a number of reasons why the memory got exhausted
in the first place (e.g. video drivers leaking memory, misc. bugs in GL
apps, ...) which would be the root cause of the problem.

(Fwiw, I stumbled across this bug report because I also got a crash in
/usr/lib/xorg/Xorg (OsLookupColor+0x13c), but this was with radeon_drv,
unrelated to any GL errors.  So, likely a different underlying bug than
the OP, just that the crash looks similar.)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1853266

Title:
  Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from
  glamor_get_pixmap_texture() from glamor_create_gc()

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg-server package in Fedora:
  Won't Fix

Bug description:
  Recently, my the xserver on my system has started randomly crashing
  due to a segmentation fault. As far as I can tell, this segmentation
  fault occurs as a result of libglamoregl encountering a
  GL_OUT_OF_MEMORY error (see attached Xorg.log). I have had a hard time
  reproducing this bug reliably, but it mostly happens when I have been
  using Inkscape for a while.

  This appears to be the same bug that has been reported here

  https://bugs.freedesktop.org/show_bug.cgi?id=110500
  https://bugs.freedesktop.org/show_bug.cgi?id=110714

  In those bug reports, the usual recommendation is to switch from the
  -modesetting video driver to the -nouveau video driver. By default,
  Ubuntu is not configured in this way, so this bug probably needs to be
  addressed in some other way.

  My graphics card is listed as follows:

   *-display 
 description: VGA compatible controller
 product: GK208B [GeForce GT 710]
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:65:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
 configuration: driver=nouveau latency=0
 resources: irq:69 memory:d700-d7ff memory:c800-cfff 
memory:d000-d1ff ioport:b000(size=128) memory:d800-d807

  Please let me know if you need any additional information.

  More information:

  Release of Ubuntu: 19.04

  Installed package versions:
  xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed]
  xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed]
  xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed]
  inkscape/disco,now 0.92.4-3 amd64 [installed]

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1853266/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

[Bryce Harrington]

It sort of sounds like there is a race condition going on in the
consumption of the key sequence.  I don't want to guess exactly what the
problem is in this particular case, but just as general X info (which
you probably already know...):

Keyboard input is processed through several levels... hardware, kernel,
X server, input manager, window manager, and applications.  And
virtualization adds another layer in there too.  Each layer does some
translation, such as from hardware key events into key id's, id's
translated into language-specific key symbols, key symbols like [ctrl,
v] into key combos/sequences like ^v, sequences into commands like
"paste", etc.  At any of these layers, an input event can be "consumed",
making it not available to other things later in the layers.

Comment #2 in particular seems to do a good job of narrowing where the
issue occurs.  Using screenkey to verify the key events are reaching the
guest rules out hardware layer through virtualization.  Reproducing the
bug in GNOME as well as KDE seems to rule out window manager.  So...  my
guess would be to look at what applications (or services) might also be
trying to consume the key sequence.

GNOME (and KDE) coordinate the key handling by applications, so that
would be a first thing to check.  Is it also possible there is a non-GTK
/non-Qt service, process, or app that is skipping that (X can be a bit
overly permissive...)

A couple tools that can be useful for probing/debugging keyboard
handling issues are `xev` and `xdotool`.  The former shows you debug
information as you hit keys, the latter lets you synthetically create
them.  For example:

xdotool mousedown --clearmodifiers 2
xdotool mouseup 2
xdotool keyup alt
xdotool keyup ctrl
xdotool keyup shift

xev should be pretty self explanatory.


On a different note...  You probably already know about Linux's primary and 
secondary clipboards.  Sometimes confusion derives from things getting copied 
to the other clipboard than intended, which can be tested.  Other times it 
seems some app gets a lock on one clipboard or puts it into some sort of mode 
so nothing can copy into it; you may run into this with firefox or other 
non-GNOME/non-KDE apps used in a GNOME or KDE environment.

So, see if you can rule out whether the problem can be localized to the
handling of the key events, or if it is specific to the copying, or the
pasting behavior.  And examine what processes are running, and in
particular note any non-KDE/non-GNOME things that may be inserting
themselves.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1872527

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in mutter package in Ubuntu:
  New
Status in virt-manager package in Ubuntu:
  Invalid

Bug description:
  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1580451] Re: mutter does not remember position of extra displays

[Bryce Harrington]

I am not reproducing this bug on latest stable mutter.

mutter:
  Installed: 3.34.3-1ubuntu1
01:00.0 VGA compatible controller:
  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] (rev 87)

I'm running a 6-head system on focal-devel, with gnome-shell/mutter and
a radeon card.  I do have troubles getting all the monitors working
properly, and invariably am having to rejigger the positions of the
extra screens.  However, merely powering the monitor on and off does not
trigger this behavior, at least not for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1580451

Title:
  mutter does not remember position of extra displays

Status in Mutter:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=747529

  If you have a laptop where you irregularly use the external monitor,
  mutter will forget the position when you turn off/on the monitor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1580451/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set

[Bryce Harrington]

I'm able to reproduce the faulty on bionic (not upgraded from xenial),
with GTK_IM_MODULE=xim and an empty .xinputrc.

Can also confirm the workaround suggested by Heiko L seems to fix this
issue, by changing /usr/share/themes/Ambiance/gtk-3.20/gtk.css to this:

> textview text {
>background-color: white;
> }
> scrollbar {
>background-color: white;
> }
> @import url("gtk-main.css");

This worked immediately after restarting gnome-calculator (installed
from deb, not snap) and gedit, no other system changes were required.


** Package changed: gtk+3.0 (Ubuntu) => ubuntu

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1760818

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

Status in Ubuntu:
  Confirmed
Status in im-config package in Ubuntu:
  Confirmed

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1760818/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1826438] Re: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files

[Bryce]

I've inferred that the reporting process itself possibly interferes with the 
misbehaviour. After submitting this report (before the terminal session was 
closed, however) (began through a terminal session and not the Alt-F2 launcher, 
using ubuntu-bug [PID of nautilus]) the reported behaviour is present again. 
The behaviour is identical to that recorded in the attached webm.
To confirm this interference I am beginning a second report, which won't be 
submitted. Using the Alt-F2 method to begin the reporting process doesn't 
interfere with the misbehaviour; beginning the process again through a terminal 
session did not reproduce the interference.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1826438

Title:
  Extra Bottom Edge Padding in RMB Context Menu for Folder, but not
  files

Status in nautilus package in Ubuntu:
  New

Bug description:
  I've recently upgraded from 18.10 to 19.04.
  When I right-click on any folder the context menu has extra padding on the 
bottom edge, below the 'properties' item. Performing the same action on files 
doesn't produce the problem.
  Strangely, while reporting this bug the noted (and recorded) behaviour 
doesn't occur, when minutes before reporting process began the observed 
behaviour was still observed following a cold boot (I witnessed and recorded 
the behaviour last night, and this morning).
  Attached is a recording of the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 11:45:34 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'260'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 
'starred']"
  InstallationDate: Installed on 2018-12-30 (116 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1826438] [NEW] Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files

[Bryce]

Public bug reported:

I've recently upgraded from 18.10 to 19.04.
When I right-click on any folder the context menu has extra padding on the 
bottom edge, below the 'properties' item. Performing the same action on files 
doesn't produce the problem.
Strangely, while reporting this bug the noted (and recorded) behaviour doesn't 
occur, when minutes before reporting process began the observed behaviour was 
still observed following a cold boot (I witnessed and recorded the behaviour 
last night, and this morning).
Attached is a recording of the behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: nautilus 1:3.32.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 11:45:34 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'260'
 b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 
'date_modified']"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 
'starred']"
InstallationDate: Installed on 2018-12-30 (116 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: nautilus
UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
usr_lib_nautilus:

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

** Attachment added: "Recording of extra padding in nautilus context menu of 
folders."
   
https://bugs.launchpad.net/bugs/1826438/+attachment/5259083/+files/19.04%20Disco%20Dingo%20-%20Folder%20RMB%20Vertical%20Padding.webm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1826438

Title:
  Extra Bottom Edge Padding in RMB Context Menu for Folder, but not
  files

Status in nautilus package in Ubuntu:
  New

Bug description:
  I've recently upgraded from 18.10 to 19.04.
  When I right-click on any folder the context menu has extra padding on the 
bottom edge, below the 'properties' item. Performing the same action on files 
doesn't produce the problem.
  Strangely, while reporting this bug the noted (and recorded) behaviour 
doesn't occur, when minutes before reporting process began the observed 
behaviour was still observed following a cold boot (I witnessed and recorded 
the behaviour last night, and this morning).
  Attached is a recording of the behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 11:45:34 2019
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'260'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'detailed_type', 
'starred']"
  InstallationDate: Installed on 2018-12-30 (116 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1822480] Re: Scrollbar Missing in Font Selection for Insert Character Form

[Bryce]

I'm not sure what GTK theme I'm using. I did realize, however, that I'm 
not using a Snap package. I had to switch to the latest .deb because 
Mendeley extension integration wouldn't work with a Snap. I'll determine 
more information and resubmit the bug report.

The error is reproducible on my system, otherwise.

On 2019-04-01 1:41 p.m., Olivier Tilloy wrote:
> I am not seeing that in a 18.10 VM with the latest libreoffice snap from
> the stable channel. The list of fonts has arrows at its top and bottom,
> scrolling with the mouse wheel and arrow keys works.
>
> Is this something that can be consistently reproduced?
>
> What GTK theme are you using?
>
> ** Changed in: libreoffice (Ubuntu)
> Status: New => Incomplete
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1822480

Title:
  Scrollbar Missing in Font Selection for Insert Character Form

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  On an Ubuntu 18.10 system, using LibreOffice 6.2.2-2 Snap package, a
  scroll-bar is not displayed in the font listing within the ‘Special
  Characters’ dialogue; the field of displayed fonts cannot be moved
  through with the arrow keys or the scroll-wheel on the mouse, but the
  selected font can be changed with the arrow keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 09:13:57 2019
  InstallationDate: Installed on 2018-12-30 (91 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1822480/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822480] [NEW] Scrollbar Missing in Font Selection for Insert Character Form

[Bryce]

Public bug reported:

On an Ubuntu 18.10 system, using LibreOffice 6.2.2-2 Snap package, a
scroll-bar is not displayed in the font listing within the ‘Special
Characters’ dialogue; the field of displayed fonts cannot be moved
through with the arrow keys or the scroll-wheel on the mouse, but the
selected font can be changed with the arrow keys.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: libreoffice-writer (not installed)
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 31 09:13:57 2019
InstallationDate: Installed on 2018-12-30 (91 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libreoffice (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic

** Attachment added: "LibreOffice 6.2.2.2 Insert Character Dialogue Font 
Selection .webm"
   
https://bugs.launchpad.net/bugs/1822480/+attachment/5251203/+files/LibreOffice%206.2.2.2%20Insert%20Character%20Dialogue%20Font%20Selection%20.webm

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1822480

Title:
  Scrollbar Missing in Font Selection for Insert Character Form

Status in libreoffice package in Ubuntu:
  New

Bug description:
  On an Ubuntu 18.10 system, using LibreOffice 6.2.2-2 Snap package, a
  scroll-bar is not displayed in the font listing within the ‘Special
  Characters’ dialogue; the field of displayed fonts cannot be moved
  through with the arrow keys or the scroll-wheel on the mouse, but the
  selected font can be changed with the arrow keys.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libreoffice-writer (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 31 09:13:57 2019
  InstallationDate: Installed on 2018-12-30 (91 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1822480/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Thanks for clearing up that misconception, Daniel (at least for me; I
thought there was at least a sizable team employed by Canonical). I'll be
happy to run these versions and do some testing. I'll looking forward to
19.04/19.10, so I'll see how they are in their current state and report any
bugs I find.

On Mon, Mar 4, 2019, 7:30 PM Daniel van Vugt, 
wrote:

> Short of predicting the future, I think the best answer is that more
> keen Ubuntu users should test the next version of Ubuntu before its
> release. That way we can discuss/prioritize/fix accessibility issues
> before they get released to the wider world.
>
> You can always get a test build of the next Ubuntu version here:
> http://cdimages.ubuntu.com/daily-live/current/
>
> There's a common misconception that Canonical has some big development
> team that will do all the development and testing but that's not true.
> We rely heavily on community users to help make Ubuntu possible.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1767648
>
> Title:
>   Top bar and shell dialogs are not displayed properly when zoom is
>   enabled
>
> Status in Mutter:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Committed
> Status in mutter source package in Cosmic:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   When zoom is enabled, the top bar and some shell dialogs (wireless
>   network selection, shutdown dialog, etc.) are not displayed properly.
>   (See the attached screenshots.)
>
>   [Test Case]
>
>   1. Enable Zoom in Setting > Universal Access
>   2. (Optional) Set zoom factor to around 3 (or higher)
>   3. Look at the top bar. You will notice that all texts and icons are now
> gone. If you move your cursor to the right of the top bar, and then click
> on the status menu, you will see that only a portion of the menu is shown.
>   4. For the shell dialogs, go to the Settings app. In the Wifi section,
> choose one of the secured network available. You will see that the password
> dialog is not displayed in its entirety.
>
>   [Regression Potential]
>
>   Low. The affected code is only used in rendering shell panels and
>   popup menus at the moment. So any potential regression (like the
>   original bug) would be noticed in those places only, and not beyond.
>   Furthermore, the upstream fix has been tested regularly for 8 months
>   already.
>
>   [Other Info]
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.1-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 28 12:54:24 2018
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>b'org.gnome.desktop.interface' b'cursor-size' b'96'
>   LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Will do.

On Tue, Feb 26, 2019, 9:00 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:

> Bryce,
>
> I am not talking about an "issue" at all. If you are experiencing
> problems then please log new bugs for them.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1767648
>
> Title:
>   Top bar and shell dialogs are not displayed properly when zoom is
>   enabled
>
> Status in Mutter:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Committed
> Status in mutter source package in Cosmic:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   When zoom is enabled, the top bar and some shell dialogs (wireless
>   network selection, shutdown dialog, etc.) are not displayed properly.
>   (See the attached screenshots.)
>
>   [Test Case]
>
>   1. Enable Zoom in Setting > Universal Access
>   2. (Optional) Set zoom factor to around 3 (or higher)
>   3. Look at the top bar. You will notice that all texts and icons are now
> gone. If you move your cursor to the right of the top bar, and then click
> on the status menu, you will see that only a portion of the menu is shown.
>   4. For the shell dialogs, go to the Settings app. In the Wifi section,
> choose one of the secured network available. You will see that the password
> dialog is not displayed in its entirety.
>
>   [Regression Potential]
>
>   Low. The affected code is only used in rendering shell panels and
>   popup menus at the moment. So any potential regression (like the
>   original bug) would be noticed in those places only, and not beyond.
>   Furthermore, the upstream fix has been tested regularly for 8 months
>   already.
>
>   [Other Info]
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.1-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 28 12:54:24 2018
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>b'org.gnome.desktop.interface' b'cursor-size' b'96'
>   LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-modu

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Might that be the same issue affecting the context menu (right click) when
using zoom? How does the drawing work for those menus?

On Tue, Feb 26, 2019, 8:35 PM Daniel van Vugt, <
daniel.van.v...@canonical.com> wrote:

> And it only occurred to me today that zoom performance should (and does
> seem to) increase too. Because the combination of the two fixes:
>
>   https://gitlab.gnome.org/GNOME/mutter/commit/8655bc5d
>   https://gitlab.gnome.org/GNOME/gnome-shell/commit/f77b3da7
>
> means that panels/docks don't need to get regenerated every time you
> move the mouse while in zoom.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1767648
>
> Title:
>   Top bar and shell dialogs are not displayed properly when zoom is
>   enabled
>
> Status in Mutter:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Bionic:
>   Fix Committed
> Status in mutter source package in Cosmic:
>   Fix Released
>
> Bug description:
>   [Impact]
>
>   When zoom is enabled, the top bar and some shell dialogs (wireless
>   network selection, shutdown dialog, etc.) are not displayed properly.
>   (See the attached screenshots.)
>
>   [Test Case]
>
>   1. Enable Zoom in Setting > Universal Access
>   2. (Optional) Set zoom factor to around 3 (or higher)
>   3. Look at the top bar. You will notice that all texts and icons are now
> gone. If you move your cursor to the right of the top bar, and then click
> on the status menu, you will see that only a portion of the menu is shown.
>   4. For the shell dialogs, go to the Settings app. In the Wifi section,
> choose one of the secured network available. You will see that the password
> dialog is not displayed in its entirety.
>
>   [Regression Potential]
>
>   Low. The affected code is only used in rendering shell panels and
>   popup menus at the moment. So any potential regression (like the
>   original bug) would be noticed in those places only, and not beyond.
>   Furthermore, the upstream fix has been tested regularly for 8 months
>   already.
>
>   [Other Info]
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.1-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 28 12:54:24 2018
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>b'org.gnome.desktop.interface' b'cursor-size' b'96'
>   LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  Fix Committed
Status in mutter source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3

[Desktop-packages] [Bug 1817269] Re: New Desktop Icons Overlap Existing Icons

[Bryce]

So to resolve the issue, the default package (which is deprecated) must be 
manually changed?
Should I simply install gnome-shell-extensions to resolve it? I'm not clear on 
what you mean, or why the issue is invalid.

As installed from the disc, the issue is present so I'm unsure what I'm
supposed to do, or why this isn't considered a bug.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1817269

Title:
  New Desktop Icons Overlap Existing Icons

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Behaviour observed in Ubuntu Cosmic 18.10
  gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed

  The expected behaviour is for new icons to populate unoccupied cells
  below the column, or occupy the first cell of a new column, or
  displace other icons to maintain alpha-numeric organization.

  The unexpected bevaviour is observed when desktop icons are created,
  such as when disk or network drives are mounted or files are saved to
  the desktop, they overlap the existing icons. They do not seem to take
  any specific position through a column, but they will always be within
  a column (assuming as such, as I always have 'Keep Aligned' enabled).

  An image depicting a series of screenshots is attached to illustrate
  the observed behaviour. From left to right, the images depict: first,
  a single column of organized, aligned icons occupy the desktop;
  second, a network drive is mounted using Files, overlapping (and
  aligned with) the uppermost icon; third, a second network drive is
  mounted, overlapping (and aligned with) the initial and second icon in
  that placement; fourth, an optical medium is mounted, and occupies a
  space two 'cells' below the original column; fifth, the desktop icons
  are arranged using 'Organize Desktop by Name'; sixth, an appimage is
  moved to the desktop using Files 'Move to...' function, overlapping
  half (and not aligned with) the top-most icon; seventh, a docx file is
  moved to the desktop using the same method, overlapping (and aligned
  with) the icon in the second cell of the column; finally, the desktop
  is organized again using the same method.

  Appendum on unexpected behaviour: after the intial creation of this
  bug-report, a third file was moved to the desktop using Files,
  occupying the empty cell in the first column, after it was seen that
  manually moving an icon into that cell was not preserved by 'Organize
  Desktop by Name'. After moving the file to the desktop, using the
  organize function moves that file into the second column, emptying the
  bottom cell in the first column.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 00:40:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-30 (54 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1817269/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1817269] [NEW] New Desktop Icons Overlap Existing Icons

[Bryce]

Public bug reported:

Behaviour observed in Ubuntu Cosmic 18.10
gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed

The expected behaviour is for new icons to populate unoccupied cells
below the column, or occupy the first cell of a new column, or displace
other icons to maintain alpha-numeric organization.

The unexpected bevaviour is observed when desktop icons are created,
such as when disk or network drives are mounted or files are saved to
the desktop, they overlap the existing icons. They do not seem to take
any specific position through a column, but they will always be within a
column (assuming as such, as I always have 'Keep Aligned' enabled).

An image depicting a series of screenshots is attached to illustrate the
observed behaviour. From left to right, the images depict: first, a
single column of organized, aligned icons occupy the desktop; second, a
network drive is mounted using Files, overlapping (and aligned with) the
uppermost icon; third, a second network drive is mounted, overlapping
(and aligned with) the initial and second icon in that placement;
fourth, an optical medium is mounted, and occupies a space two 'cells'
below the original column; fifth, the desktop icons are arranged using
'Organize Desktop by Name'; sixth, an appimage is moved to the desktop
using Files 'Move to...' function, overlapping half (and not aligned
with) the top-most icon; seventh, a docx file is moved to the desktop
using the same method, overlapping (and aligned with) the icon in the
second cell of the column; finally, the desktop is organized again using
the same method.

Appendum on unexpected behaviour: after the intial creation of this bug-
report, a third file was moved to the desktop using Files, occupying the
empty cell in the first column, after it was seen that manually moving
an icon into that cell was not preserved by 'Organize Desktop by Name'.
After moving the file to the desktop, using the organize function moves
that file into the second column, emptying the bottom cell in the first
column.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 22 00:40:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-30 (54 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic package-from-proposed

** Attachment added: "Image of unexpected behaviour"
   
https://bugs.launchpad.net/bugs/1817269/+attachment/5240878/+files/Observed%20Behaviour.png

** Description changed:

  Behaviour observed in Ubuntu Cosmic 18.10
  gnome-shell 3.30.2-0ubuntu1.18.10.1 from cosmic-proposed
  
  The expected behaviour is for new icons to populate unoccupied cells
  below the column, or occupy the first cell of a new column, or displace
  other icons to maintain alpha-numeric organization.
  
  The unexpected bevaviour is observed when desktop icons are created,
  such as when disk or network drives are mounted or files are saved to
- the desktop, they overlap the existing icons. They do not seem to take
+ the desktop, and overlap the existing icons. They do not seem to take
  any specific position through a column, but they will always be within a
  column (assuming as such, as I always have 'Keep Aligned' enabled).
  
  An image depicting a series of screenshots is attached to illustrate the
  observed behaviour. From left to right, the images depict: first, a
  single column of organized, aligned icons occupy the desktop; second, a
  network drive is mounted using Files, overlapping (and aligned with) the
  uppermost icon; third, a second network drive is mounted, overlapping
  (and aligned with) the initial and second icon in that placement;
  fourth, an optical medium is mounted, and occupies a space two 'cells'
  below the original column; fifth, the desktop icons are arranged using
  'Organize Desktop by Name'; sixth, an appimage is moved to the desktop
  using Files 'Move to...' function, overlapping half (and not aligned
  with) the top-most icon; seventh, a docx file is moved to the desktop
  using the same method, overlapping (and aligned with) the icon in the
  second cell of the column; finally, the desktop is organized again using
  the same method.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.2-0ubuntu1.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 22 00:40:39 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

If you look a few posts earlier in the thread, you'll see a guide on how to
test the proposed package. It shouldn't be long now before all users
receive the update. You won't need to reconfigure anything then.

On Mon, Feb 18, 2019, 4:05 PM Declan <1767...@bugs.launchpad.net wrote:

> Ok, I am on Ubuntu 18.10, does that mean I installe dthe update? How do
> I check? The issue hasn't gone away, still can't see the system menu.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1767648
>
> Title:
>   Top bar and shell dialogs are not displayed properly when zoom is
>   enabled
>
> Status in Mutter:
>   Fix Released
> Status in mutter package in Ubuntu:
>   Fix Released
> Status in mutter source package in Bionic:
>   In Progress
> Status in mutter source package in Cosmic:
>   Fix Committed
>
> Bug description:
>   [Impact]
>
>   When zoom is enabled, the top bar and some shell dialogs (wireless
>   network selection, shutdown dialog, etc.) are not displayed properly.
>   (See the attached screenshots.)
>
>   [Test Case]
>
>   1. Enable Zoom in Setting > Universal Access
>   2. (Optional) Set zoom factor to around 3 (or higher)
>   3. Look at the top bar. You will notice that all texts and icons are now
> gone. If you move your cursor to the right of the top bar, and then click
> on the status menu, you will see that only a portion of the menu is shown.
>   4. For the shell dialogs, go to the Settings app. In the Wifi section,
> choose one of the secured network available. You will see that the password
> dialog is not displayed in its entirety.
>
>   [Regression Potential]
>
>   Low. The affected code is only used in rendering shell panels and
>   popup menus at the moment. So any potential regression (like the
>   original bug) would be noticed in those places only, and not beyond.
>   Furthermore, the upstream fix has been tested regularly for 8 months
>   already.
>
>   [Other Info]
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.1-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CasperVersion: 1.394
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 28 12:54:24 2018
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>b'org.gnome.desktop.interface' b'cursor-size' b'96'
>   LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

No worries, Daniel.

I was going to log the new bug report. I re-enabled the proposed updates 
and opened aptitude to install the package but I noticed that there was 
an unmet dependency (libmutter: 3.30.2-1~ubuntu18.10.3) for the proposed 
package. I installed that dependency along with the proposed package, 
and, to my surprise, the package now works as expected. There is some 
minor flickering when the mouse cursor is moved diagonally over context 
(RMB) menus in some gnome applications (files and the desktop), but the 
system menu and the taskbar behave as expected.

Perhaps when I followed instructions the first time I upgraded to the 
proposed package the dependency failed to install. The package works now.

Should I submit a bug for the context-menu flickering?

-Bryce

Expected behaviour of system menu when zoom functionality enabled.

On 2019-02-17 8:59 p.m., Daniel van Vugt wrote:
> Bryce,
>
> Sorry for the delay. I was on leave...
>
> Please log a new bug from your affected machine by running:
>
>ubuntu-bug mutter
>
> and tell us the new bug ID.
>
> ** Changed in: mutter (Ubuntu Cosmic)
>   Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>


** Attachment added: "Screenshot from 2019-02-18 12-35-16.png"
   
https://bugs.launchpad.net/bugs/1767648/+attachment/5239609/+files/Screenshot%20from%202019-02-18%2012-35-16.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

I have an HD 5870. 
I'm not using any additional or proprietary drivers (according to that tab in 
Software & Updates); however, 'Proprietary drivers for devices' is enabled in 
the Ubuntu Software tab in Software & Updates.

The only PPAs I have are for Google Chrome, PlayOnLinux, and Alexander
Larsson's Launchpad.

For my video card information:
Cypress XT [Radeon HD 5870]
Vendor: AMD/ATI
Phys. ID: 0
version: 00
clock: 33MHz
driver: radeon
I'm not sure exactly which information you need, so here is a pastebin of the 
output of 'modinfo radeon': https://pastebin.com/axFRR5hw.

I'm honestly not sure what to provide, so if you want the output of some
commands, I can provide those easily if you tell me which/what you'd
like. I didn't find any GUI-level information on my drivers or what
packages they are, so that's the best I could find in the time I have
for this.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

I can. It will need to happen this evening (+12 hours from this reply),
though.

On Wed, Feb 6, 2019, 1:30 AM Marco Trevisan (Treviño)  Anyway, Bryce, can you give us context about your hw (graphic card,
> drivers, ppas? and versions)?
> Otherwise is probably hard to reproduce your issue, as so far was not
> possible to reproduce for us.
>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

** Tags removed: verification-done-cosmic
** Tags added: verification-failed-cosmic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Yes, a warm reboot was performed after initial testing to confirm lack
of function. Cold booted this morning and the fix still does not work,
so I'm reverting to the previous package now. I'll go through the
process of reenabling -proposed when the next fix is released for other
testing instructions are provided for this fix.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Unintentionally unassigned Cosmic from Daniel. Please reassign to
Daniel.

** Changed in: mutter (Ubuntu Cosmic)
 Assignee: Daniel van Vugt (vanvugt) => Bryce (bryce-a-carson)

** Changed in: mutter (Ubuntu Cosmic)
 Assignee: Bryce (bryce-a-carson) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Bryce]

Verified on Cosmic that mutter version 3.30.2-1~ubuntu.18.10.3 does NOT
fix the problem.

** Attachment added: "Proof of installation; proof of bug."
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767648/+attachment/5235249/+files/Screenshot%20from%202019-02-01%2021-16-19.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1767648

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Bionic:
  In Progress
Status in mutter source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  When zoom is enabled, the top bar and some shell dialogs (wireless
  network selection, shutdown dialog, etc.) are not displayed properly.
  (See the attached screenshots.)

  [Test Case]

  1. Enable Zoom in Setting > Universal Access
  2. (Optional) Set zoom factor to around 3 (or higher)
  3. Look at the top bar. You will notice that all texts and icons are now 
gone. If you move your cursor to the right of the top bar, and then click on 
the status menu, you will see that only a portion of the menu is shown.
  4. For the shell dialogs, go to the Settings app. In the Wifi section, choose 
one of the secured network available. You will see that the password dialog is 
not displayed in its entirety.

  [Regression Potential]

  Low. The affected code is only used in rendering shell panels and
  popup menus at the moment. So any potential regression (like the
  original bug) would be noticed in those places only, and not beyond.
  Furthermore, the upstream fix has been tested regularly for 8 months
  already.

  [Other Info]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 12:54:24 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'cursor-size' b'96'
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)

[bryce aaron smith]

idk

** Changed in: ubuntu-mate
 Assignee: (unassigned) => bryce aaron smith (brycesmith1.)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1754458

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in ubuntu-mate:
  Confirmed
Status in indicator-application package in Ubuntu:
  New
Status in mate-indicator-applet package in Ubuntu:
  New
Status in network-manager-applet package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  New

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1754458/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778344] Re: Shotwell exports images with DPI of 1 according to windows

[Bryce Willey]

The original CR2 image from the camera is:

Exif.Image.XResolution   Rational1  72
Exif.Image.YResolution   Rational1  72
Exif.Image.ResolutionUnitShort   1  inch

But I use Darktable to process the raw image, and it's output is:

Error: XMP Toolkit error 203: Duplicate property or field node
Warning: Failed to decode XMP metadata.
Exif.Image.XResolution   SLong   1  300
Exif.Image.YResolution   SLong   1  300
Exif.Image.ResolutionUnitShort   1  inch

So it must be a problem with Darktable. Thanks for the help, I'll close
this.

** Changed in: shotwell (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1778344

Title:
  Shotwell exports images with DPI of 1 according to windows

Status in shotwell package in Ubuntu:
  Invalid

Bug description:
  When sending images edited with Shotwell to Window's users, the
  properties of the image show a vertical and horizontal resolution of 1
  PPI. I'm assuming that this is a metadata mislabel and that the image
  would have the same problem, but Shotwell does not show the PPI/DPI of
  an image, only the number of pixels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1778344] [NEW] Shotwell exports images with DPI of 1 according to windows

[Bryce Willey]

Public bug reported:

When sending images edited with Shotwell to Window's users, the
properties of the image show a vertical and horizontal resolution of 1
PPI. I'm assuming that this is a metadata mislabel and that the image
would have the same problem, but Shotwell does not show the PPI/DPI of
an image, only the number of pixels.

** Affects: shotwell (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "An example image with 1 PPI"
   
https://bugs.launchpad.net/bugs/1778344/+attachment/5155854/+files/Lacy-A1560562.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1778344

Title:
  Shotwell exports images with DPI of 1 according to windows

Status in shotwell package in Ubuntu:
  New

Bug description:
  When sending images edited with Shotwell to Window's users, the
  properties of the image show a vertical and horizontal resolution of 1
  PPI. I'm assuming that this is a metadata mislabel and that the image
  would have the same problem, but Shotwell does not show the PPI/DPI of
  an image, only the number of pixels.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

[Bryce Leo]

Broken again with kernel 4.15.0.22.23.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1764005

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts

[Bryce Harrington]

** Changed in: inkscape
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1226962

Title:
  Keyboard shortcuts (hotkeys) not functional in some cases in non-latin
  keyboard layouts

Status in aptana-studio-installer:
  New
Status in Default settings and artwork for Baltix OS:
  New
Status in LibreOffice:
  Fix Released
Status in ibus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape:
  Fix Released
Status in Intellij Idea:
  New
Status in monodevelop:
  New
Status in Mutter:
  Fix Released
Status in okular:
  New
Status in OpenOffice:
  New
Status in sigram:
  New
Status in Unity:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-terminal package in Ubuntu:
  Triaged
Status in kdevelop package in Ubuntu:
  Confirmed
Status in mc package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Incomplete
Status in terminator package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in gnome-settings-daemon source package in Xenial:
  Triaged
Status in gnome-terminal source package in Xenial:
  Triaged
Status in kdevelop source package in Xenial:
  Confirmed
Status in mc source package in Xenial:
  Confirmed
Status in openjdk-7 source package in Xenial:
  Incomplete
Status in terminator source package in Xenial:
  Confirmed
Status in unity source package in Xenial:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  In Progress
Status in gnome-shell package in Fedora:
  Won't Fix
Status in openoffice package in Fedora:
  Won't Fix

Bug description:
  Keyboard shortcuts are key combinations like Alt+F (usually opens the
  File menu) and Ctrl+O (usually opens the File→Open... dialog box).

  There is an issue with non-latin keyboard layouts that the keys under F or O 
(for Alt+F and Ctrl+O respectively) would correspond to some other character.
  What should happen then? There is some smart functionality (at least in the 
GTK+ library) that when we press a shortcut, it will try to make Alt+F or 
Ctrl+O work, even if the active keyboard layout is not English.

  For this smart functionality to work, it requires us to have as first 
keyboard layout the English (en) layout. Then, GTK+ will be able to
  check whether the shortcut makes sense for English, and if so, will run it.
  All that even if the active layout is Greek or Russian or something else. 

  This report has over 300 comments and these comments include all sort of 
corner cases that indeed shortcuts do not work. In general, shortcuts work,
  but in specific cases there are issues that need to be fixed.

  What we need to do, is collect those corner cases and create new
  separate reports.

  Here are the corner cases:

  1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, 
Russian), but they do not work for Super+A/F/M/C/V. 
  Report: 

  2. Java GUI applications on Linux do not support shortcuts in non-latin 
languages. This is an issue with Java and should be reported there.
  Java GUI apps are not included in any of the Ubuntu ISOs. 
  Report: 

  3. Shortcuts that use Ctrl on LibreOffice work for several languages (like 
Greek, Russian), but has been reported not to work on Hebrew.
  This should be a separate bug report specific to Hebrew and other languages 
affected in the same way.
  Report: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!

[Bryce Schober]

On Ubuntu 14.04, I've installed the ubuntu-toolchain-r/test ppa in order
to get a gcc-5 compiler, and the assumedly-conflicting
4.8.5-2ubuntu1~14.04.1 came from that PPA along for the ride.

Is there a better PPA option for installing gcc-5 on Ubuntu 14.04?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1750937

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04) by an insufficient compiler!

Status in gcc:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 174650] Re: xorg very slow when rotated on external monitor (i965)

[Bryce Harrington]

** Changed in: xserver-xorg-video-intel (Ubuntu)
 Assignee: Bryce Harrington (bryce) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/174650

Title:
  xorg very slow when rotated on external monitor (i965)

Status in xf86-video-intel:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg-video-intel

  I run kubuntu gutsy on a dell d630 with an external monitor.
  It works well and fast (after manual tweaking of xorg.conf), except when
  I put my external monitor in vertical position and use 
 Option"Rotate"  "left"
  in xorg.conf.

  Then display is ok but VERY slow: when I move a window, I can see
  frames trying to catch up at a rate less that 3/sec (and less than
  1/sec in fullscreen !) . And xorg uses 100% cpu when I do this.

  
  --

  xrandr output:
  Screen 0: minimum 320 x 200, current 2464 x 2000, maximum 2720 x 2048
  VGA connected 1024x1280+0+0 left (normal left inverted right) 376mm x 301mm
 1280x1024  60.0*+   75.0 59.9
 1152x864   74.8
 1024x768   75.1 60.0
 800x60075.0 60.3
 640x48075.0 60.0
 720x40070.1
  LVDS connected 1440x900+1024+1100 (normal left inverted right) 303mm x 189mm
 1440x900   60.0*+   50.0
 1280x800   60.0
 1280x768   60.0
 1024x768   60.0
 800x60060.3
 640x48059.9
  TMDS-1 disconnected (normal left inverted right)
  TV disconnected (normal left inverted right)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/174650/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1735363] Re: inkscape: Port to Python 3

[Bryce Harrington]

I'd second Ted's suggestion of splitting out python code to a separate
package, that's something we've been pondering doing for other reasons
already.

Do we have a listing of what exactly uses python?

I know the extension programs do, and those could be split out to an
inkscape-extras package.

If there are any utilities or build helpers in python, those should be
redoable in python3 without much fuss.  Give me a list and I can make
sure they all get done.

Is there anything else besides that?  Does Inkscape have any python
bindings internally that are version specific?

@moini, being demoted from main isn't that big of a deal, it's more a
loss against Ubuntu than Inkscape itself.  Most users will have universe
enabled so it's not going to impact them.  It just limits Canonical's
ability to make good use of Inkscape in their own products.  Like Ted
points out, users have many ways to get Inkscape.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1735363

Title:
  inkscape: Port to Python 3

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  New
Status in inkscape package in Debian:
  Confirmed

Bug description:
  inkscape: Use/Port of Python3 needed, or considering demotion.

  Currently seeded in usb (???), owned by desktop-packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1735363/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1269838] Re: gnome-session.log takes 8 GB in a few hours

[Bryce Nesbitt]

@mpt  yes, this is still an issue on Ubuntu 14.04LTS.
My /home partition fills up nearly every day (bad on an SSD also because of 
write amplification).

-rw-r- 3151151104 Feb  4 13:06 gnome-session-Unity.log


The log spam is useuless repetive stuff like:
(putty:29947): GLib-CRITICAL **: Source ID 67342 was not found when attempting 
to remove it
[0x7f2468000ec8] v4l2 demux error: dequeue error: No such device
[0x7f2468000ec8] v4l2 demux error: dequeue error: No such device
[4757:4787:0204/130259:ERROR:connection.cc(1892)] Cookie sqlite error 13, errno 
0: database or disk is full, sql: UPDATE cookies SET last_access_utc=? WHERE 
creation_utc=?


** Changed in: gnome-session (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1269838

Title:
  gnome-session.log takes 8 GB in a few hours

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Hello,

  On a fresh install of saucy 64 bits, ~/.cache/upstart/gnome-session.log grows 
incredibly fast. 8 GB in a few hours.
  Worked it around with a rm as cron task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan 16 16:02:23 2014
  InstallationDate: Installed on 2014-01-10 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  upstart.upstart-file-bridge.log:
   Job got added /com/ubuntu/Upstart/jobs/unicast_2dlocal_2davahi
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2dcrash
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2drelease

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1269838/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty

[Bryce Harrington]

** Also affects: inkscape (Ubuntu Zesty)
   Importance: Medium
 Assignee: Mattia Rizzolo (mapreri)
   Status: Triaged

** Also affects: inkscape (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Changed in: inkscape (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: inkscape (Ubuntu Yakkety)
   Importance: Undecided => Medium

** Changed in: inkscape (Ubuntu Yakkety)
 Assignee: (unassigned) => Mattia Rizzolo (mapreri)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1638373

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Triaged
Status in inkscape source package in Yakkety:
  Triaged
Status in inkscape source package in Zesty:
  Triaged

Bug description:
  The dropdown menus for start marker, end marker and mid markers do not
  contains any arrows to select. I have clean up all local settings and
  run inkscape fresh but the same problem.

  Inkscape 0.91, Ubuntu 16.10

  =
  From the duplicate reports:
  - Inkscape 0.91 r13725 on Ubuntu 16.10
  - Inkscape 0.91-11 r13725 on Ubuntu 16.10
  - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11
  - Inkscape 0.92, ubuntu 16.04 LTS
  - Ubuntu 16.04 - upgrade today to 0.92
  - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/1638373/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 627240] Re: Feature request: alternate glyph support (OpenType)

[Bryce Harrington]

** Changed in: inkscape
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/627240

Title:
  Feature request: alternate glyph support (OpenType)

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Invalid

Bug description:
  The only thing making me consider the switch to InDesign is the fact
  that InkScape can't access OpenType glyph alternates in professional
  fonts, nor make use of the marvelous automatic capacities of OpenType
  such as contextual alternates. I vastly prefer InkScape otherwise, and
  want to keep using it permanently—but for many typographers, this
  feature is necessary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/627240/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1640924] [NEW] MFC8600 Brother Prints OK first PDF job, second job prints garbage

[Bryce Nesbitt]

Public bug reported:

It's been like this for years. Some initialization problem between
driver and printer.

If I print certain types of documents the printer is fine.
If I print a pdf, it's fine.
If I print a second pdf, reams of paper spit out of the machine each with a few 
random characters on them.

Resetting CUPS or power cycling the printer fixes the issue for one printout.
Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
does not... at least not for sure... fix the problem.

--

Or maybe it is an end job problem, as the printer often reports a state of
"Idle - Sending data to printer."
Hours after the last printout.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.7
ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
Uname: Linux 3.13.0-100-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CupsErrorLog:
 E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
 E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
 E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
 E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
CurrentDesktop: Unity
Date: Thu Nov 10 11:37:50 2016
Lpstat:
 device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
 device for MFC-8600: usb://Brother/MFC-8600
 device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
MachineType: Supermicro X8SAX
Papersize: letter
PpdFiles:
 MFCJ985DW: Brother MFC-J985DW CUPS
 MFC-8600: Brother MFC-8600 Foomatic/hl7x0 (recommended)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic 
root=UUID=8a67d411-9750-46e4-8a53-b2059e5a4eeb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/10
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: X8SAX
dmi.board.vendor: Supermicro
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 1234567890
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd09/17/10:svnSupermicro:pnX8SAX:pvr1234567890:rvnSupermicro:rnX8SAX:rvr2.0:cvnSupermicro:ct3:cvr1234567890:
dmi.product.name: X8SAX
dmi.product.version: 1234567890
dmi.sys.vendor: Supermicro
mtime.conffile..etc.cups.cupsd.conf: 2015-01-21T15:19:58.577664

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1640924

Title:
  MFC8600 Brother Prints OK first PDF job, second job prints garbage

Status in cups package in Ubuntu:
  New

Bug description:
  It's been like this for years. Some initialization problem between
  driver and printer.

  If I print certain types of documents the printer is fine.
  If I print a pdf, it's fine.
  If I print a second pdf, reams of paper spit out of the machine each with a 
few random characters on them.

  Resetting CUPS or power cycling the printer fixes the issue for one printout.
  Resetting CPUS ("sudo /etc/init.d/cups restart") fixes the issue for one 
printout.

  I use the "Brother MFC-8600 Foomatic/hl7x0 (recommended)" driver.  Changing 
driver
  does not... at least not for sure... fix the problem.

  --

  Or maybe it is an end job problem, as the printer often reports a state of
  "Idle - Sending data to printer."
  Hours after the last printout.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CupsErrorLog:
   E [09/Nov/2016:09:07:28 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
   E [10/Nov/2016:09:18:42 -0800] [Job 2767] Unable to send data to printer.
   E [10/Nov/2016:09:23:43 -0800] [Job 2767] Stopping unresponsive job.
   E [10/Nov/2016:09:26:06 -0800] Unknown directive BrowseAddress on line 10 of 
/etc/cups/cupsd.conf.
  CurrentDesktop: Unity
  Date: Thu Nov 10 11:37:50 2016
  Lpstat:
   device for Brother-MFC-8600: 
ipps://Bryces-Mac-mini.local:631/printers/Brother_MFC_8600
   device for MFC-8600: usb://Brother/MFC-8600
   device for MFCJ985DW: dnssd://Brother%20MFC-J985DW._ipp._tcp.local/
  MachineType: Supermicro X8SAX
  Papersize: letter
  PpdFiles:
   MFCJ985DW: Brother MFC-J985DW CUPS
   MFC-8600: 

[Desktop-packages] [Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup

[Bryce Nesbitt]

This seems to still be an issue: and it's a serious issue when a semi
public computer is involved, as those using the computer won't know the
password.

It is also a problem to train users to enter their password when a
prompt box comes up: that's just ripe for abuse.

See also:
http://askubuntu.com/questions/867/how-can-i-stop-being-prompted-to-unlock-the-default-keyring-on-boot

---
Better and more secure the above cases is a mode for gnome-keyring "never 
prompt".

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/575877

Title:
  gnome-keyring mysteriously asks for keyring password on startup

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-keyring

  I recently (yesterday) upgraded from Karmic to Lucid. Now whenever I start 
up, gnome-keyring asks me for my keyring password. Note that I use a password 
to log in, and I also have a keyring password. So I am not using auto-login. 
What confuses me is that I cannot tell what application is trying to access the 
keyring. And when I am asked for my password, I am unable to switch to other 
applications, e.g. terminal, to perform any debugging.
  This behavior did not occur before the upgrade.
  As far as I know, I should not have to enter my keyring password until 
something actually has to use the keyring. And it should only unlock that 
portion of the keyring that it uses. But the dialog I get provides me with no 
information other than "an application wants to access the keyring".

  From apt-cache policy gnome-keyring:
  gnome-keyring:
Installed: 2.92.92.is.2.30.0-0ubuntu3
Candidate: 2.92.92.is.2.30.0-0ubuntu3
Version table:
   *** 2.92.92.is.2.30.0-0ubuntu3 0
  500 http://ubuntu.osuosl.org/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  From lsb_release -rd:
  Description:  Ubuntu 10.04 LTS
  Release:  10.04

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-keyring 2.92.92.is.2.30.0-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed May  5 12:10:00 2010
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1158432] Re: On graphical login, Network Manager window gets in the way

[Bryce Nesbitt]

Still relevant in 16.04 LTS.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1158432

Title:
  On graphical login, Network Manager window gets in the way

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  New in 13.04, on a laptop with wifi (in addition to being wired), when
  the login gui comes up on boot-up, I can no longer simply type in my
  password to log in.

  This is because a wifi authentication window pops up, asking for a
  password for my wifi connection.  Worse, it does not let me get the
  focus back to the log in screen or anywhere else: I have to explicitly
  click "cancel ".

  After I log in, the wifi password is not needed, since the Manager has
  stored it and connects automatically, using its stored password.

  It may be nice to be able to access the network before logging in, but
  that option should not interrupt my log-in process, and certainly not
  block it!

  Moreover, given that my machine is also connected to wired ethernet
  (by DHCP, no password), it is hardly a high priority to get wifi
  going.

  This problem exists on both of my laptops (very different hardware).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 21 13:47:50 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-18 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  IpRoute:
   default via 132.206.112.1 dev eth0  proto static 
   132.206.112.0/26 dev eth0  proto kernel  scope link  src 132.206.112.10  
metric 1 
   142.157.168.0/23 dev wlan0  proto kernel  scope link  src 142.157.168.8  
metric 9 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-03-19T18:52:07.457464
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   IHSP  3985ff88-5770-4938-8133-23b8ded92641   
802-3-ethernet1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/2
   DHCP  aec2f3e7-cdaa-46ff-b51d-401084613817   
802-3-ethernet0never  no
no /org/freedesktop/NetworkManager/Settings/1
   wpa.mcgill.ca 4ce783b2-6946-417e-ac7c-eb6984d01f15   
802-11-wireless   1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1158432/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1600638] [NEW] Unity control center chokes on upper case in user name

[Bryce Nesbitt]

Public bug reported:

1. Enter control panel
2. "Add account"
3. Use an invalid charcter, such as an upper case letter.
4. Get a confusing error message:

Failed to add account 
running '/usr/sbin/adduser' failed: Child process exited with code 1'


This is an easy fix, and could keep a user from getting really confused.
For a confused user see
http://askubuntu.com/questions/677749/failed-to-add-account-in-ubuntu-14-04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
Uname: Linux 3.13.0-88-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 10 12:46:05 2016
ExecutablePath: /usr/bin/unity-control-center
ProcEnviron:
 PATH=(custom, user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_unity-control-center:
 deja-dup 30.0-0ubuntu4
 gnome-control-center 1:3.6.3-0ubuntu56.1

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty

** Attachment added: "Failed to add account"
   
https://bugs.launchpad.net/bugs/1600638/+attachment/4698512/+files/Ubuntu%20Add%20Account%20Failed%20.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1600638

Title:
  Unity control center chokes on upper case in user name

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  1. Enter control panel
  2. "Add account"
  3. Use an invalid charcter, such as an upper case letter.
  4. Get a confusing error message:

  Failed to add account 
  running '/usr/sbin/adduser' failed: Child process exited with code 1'

  
  This is an easy fix, and could keep a user from getting really confused.
  For a confused user see
  http://askubuntu.com/questions/677749/failed-to-add-account-in-ubuntu-14-04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-88.135-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-88-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 10 12:46:05 2016
  ExecutablePath: /usr/bin/unity-control-center
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1600638/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1572640] Re: cursor invisible after timeout and screen-saving

[Bryce Fowler]

Same problem in ubuntu-mate-16.04-desktop-amd64.iso

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1572640

Title:
  cursor invisible after timeout and screen-saving

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  When installed from the *Lubuntu alternate* ISO files, the default
  systems are affected by this bug:

  After time-out the screensaver kicks in and the user is locked out. At
  the unlock screen the cursor is visible, but after unlock the cursor
  is invisible. This bug does not affect the corresponding desktop ISO
  files, neither the live session nor the default installed systems.

  ISO files: The Lubuntu Xenial final version dated 20160419

  xenial-alternate-i386.iso
  xenial-desktop-i386.iso
  xenial-alternate-amd64.iso
  xenial-desktop-amd64.iso

  Links to the computer specs:

  http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w
  
https://shop.lenovo.com/ISS_Static/ww/wci/products/us/laptop/thinkpad/x-series/x131e-intel/X131e-Datasheet-Intel.pdf

  Link to detailed description:

  http://ubuntuforums.org/showthread.php?t=2321069=13473145#post13473145

  The cursor appears again after logout and stays after login.

  This bug is similar to or the same as Bug #1568604: Mouse cursor lost
  when unlocking

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Apr 20 17:37:20 2016
  InstallationDate: Installed on 2016-04-20 (0 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160419)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1572640/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file

[Bryce Nesbitt]

Also had to delete  .config/monitors.xml  to get my system working
again.  Not smooth.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1268257

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with only error: objdump: '... .tmp_nv.o': No such
  file

Status in NVIDIA Drivers Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for LUG in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

Swap is the equivalent of main memory: the security issues are no
different.  Nobody can complain about swap written to disk, as that's a
risk for any piece of main memory at any time.  Why turn things so far
upside down to support an edge case (infinite scrollback left open for long
periods of time)?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620

Title:
  gnome-terminal writes excessively to /tmp (affecting SSD drives)

Status in vte package in Ubuntu:
  New

Bug description:
  1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
  2) In another window cat a file to the screen.
  3) Observe the activity.  I see large churn on the /tmp partitition:

  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.170354 

Re: [Desktop-packages] [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

The oom killer will only come along if some epic long files have been
cat'ed to the terminal,
and infinite scrollback is selected.  Speed, battery life, SSD life, energy
use and privacy are all reasons to have the common case be no disk writes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620

Title:
  gnome-terminal writes excessively to /tmp (affecting SSD drives)

Status in vte package in Ubuntu:
  New

Bug description:
  1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
  2) In another window cat a file to the screen.
  3) Observe the activity.  I see large churn on the /tmp partitition:

  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.170744 

[Desktop-packages] [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

How do you think gnome-terminal should handle that? Suppose you have 4
GB of ram, shall it consume up to 3 GB and then starting using the
disk? Sounds not only hard to implement, but also why should it take
away RAM from other apps?

The Linux virtual memory system is highly adept at swapping out content that's 
not in active use,
keeping RAM for what's hot.  The global system for this works quite well.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620

Title:
  gnome-terminal writes excessively to /tmp (affecting SSD drives)

Status in vte package in Ubuntu:
  New

Bug description:
  1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
  2) In another window cat a file to the screen.
  3) Observe the activity.  I see large churn on the /tmp partitition:

  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 

[Desktop-packages] [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

@Egmont wrote:
Running out of disk space is much less likely and effects the system less 
badly than running out of RAM, and your RAM would eventually make it into the 
disk (swap) anyways.

But I run out of ram space very rarely.  It's highly elegant to keep
volatile data in RAM unless RAM is full.

--
@Egmont wrote:
still don't think SSD lifetime is a valid real-life issue.
My particular desktop SSD is at 19% lifetime (as measured by the vendor through 
SMART code 202 Perc_Rated_Life_Used or 173 Wear_Leveling_Count).  So yes, real 
people can wear out an SSD.

--
Aside from that writing to disk is dramatically more system overhead, compared 
to RAM.
--
Bash history, which is NOT kept from overwriting, is a better use of disk 
writes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620

Title:
  gnome-terminal writes excessively to /tmp (affecting SSD drives)

Status in vte package in Ubuntu:
  New

Bug description:
  1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
  2) In another window cat a file to the screen.
  3) Observe the activity.  I see large churn on the /tmp partitition:

  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  

[Desktop-packages] [Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles

[Bryce Nesbitt]

Here's output of sudo strace -p XX where X is the process ID
of the misbehaving gvfsd-afp:

recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)
recvfrom(7, , 16, 0, NULL, NULL)  = 0
poll([{fd=3, events=POLLIN}], 1, 0) = 0 (Timeout)

And sudo gdb -p  followed by bt

(gdb) bt
#0  0x7f766cb897eb in __libc_recv (fd=7, buf=0x23d86a0, n=16, flags=-1)
at ../sysdeps/unix/sysv/linux/x86_64/recv.c:33
#1  0x7f766d5e3bec in g_socket_receive_with_blocking ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#2  0x7f766d5cb625 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#3  0x7f766d5cd02b in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f766d5cc28b in g_input_stream_read_async () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x0040c0c1 in ?? ()
#6  0x7f766d5ccd5a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7  0x7f766d5f08db in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8  0x7f766d5f08f9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9  0x7f766d05fce5 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7f766d060048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x7f766d06030a in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x0040b7c1 in ?? ()
#13 0x00406b97 in ?? ()
#14 0x7f766c7d6ec5 in __libc_start_main (main=0x406b40, argc=4, 
argv=0x7fff04eca8e8, 
init=optimized out, fini=optimized out, rtld_fini=optimized out, 
stack_end=0x7fff04eca8d8)
at libc-start.c:287
#15 0x00406bc9 in ?? ()

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/951585

Title:
  gvfsd-afp consumes 100% of processor cycles

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Happens on an irregular basis on 12.04 and I think I've experienced it
  on 11.10.

  For no reason gvfsd-afp starts up. Cooling fan kicks in, system
  becomes laggy. Easily cured using system monitor and killing the
  process. Someone on the Ubuntu Forum asked if I have a Mac on the
  network and the answer is yes, an iMac and there are shares on that
  machine I can access.

  Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles

[Bryce Nesbitt]

(The prior backtrace is under Ubuntu 14.04LTS fully patched)  gvfs
Version: 1.20.1-1ubuntu1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/951585

Title:
  gvfsd-afp consumes 100% of processor cycles

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Happens on an irregular basis on 12.04 and I think I've experienced it
  on 11.10.

  For no reason gvfsd-afp starts up. Cooling fan kicks in, system
  becomes laggy. Easily cured using system monitor and killing the
  process. Someone on the Ubuntu Forum asked if I have a Mac on the
  network and the answer is yes, an iMac and there are shares on that
  machine I can access.

  Have experienced this issue on my Acer Aspire 5742 and Compaq Mini 110

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

See also http://ubuntuforums.org/showthread.php?t=1830432

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/1430620

Title:
  gnome-terminal writes excessively to /tmp (affecting SSD drives)

Status in vte package in Ubuntu:
  New

Bug description:
  1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
  2) In another window cat a file to the screen.
  3) Observe the activity.  I see large churn on the /tmp partitition:

  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
  20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted)
  20:41:24.171222 gnome-terminal(23352): W /tmp/#132828 (deleted)
  

[Desktop-packages] [Bug 1430620] [NEW] gnome-terminal writes excessively to /tmp (affecting SSD drives)

[Bryce Nesbitt]

Public bug reported:

1) In a gnome-terminal run sudo fatrace -f W -t (filter for writes plus 
timestamps).
2) In another window cat a file to the screen.
3) Observe the activity.  I see large churn on the /tmp partitition:

20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.158837 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.159268 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.159674 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.160171 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.160603 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.160919 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.161093 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.161545 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.161999 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.162447 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.162825 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.162899 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.163366 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.163817 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.164331 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.164729 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.164729 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.165219 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.165674 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.166128 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.166587 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.10 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.167056 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.167529 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.167949 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.168451 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.168524 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.168889 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.169364 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.169808 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.170281 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.170354 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.170744 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.171222 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.171222 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.171699 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.171699 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.172114 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.172114 gnome-terminal(23352): W /tmp/#132828 (deleted)
20:41:24.172298 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.172298 gnome-terminal(23352): W /tmp/#132835 (deleted)
20:41:24.172617 

[Desktop-packages] [Bug 865082] Re: gnome-terminal writes to /tmp on every line of output

[Bryce Nesbitt]

Probably related, here's a small sample as captured by the new fatrace
--filter W utility on Ubuntu 14.04 LTS:

09:35:01.577176 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.588323 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.588323 gnome-terminal(8923): RW /tmp/#132359 (deleted)
09:35:01.588323 gnome-terminal(8923): W /tmp/#132358 (deleted)
09:35:01.588323 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.604411 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.604411 gnome-terminal(8923): RW /tmp/#132359 (deleted)
09:35:01.604411 gnome-terminal(8923): W /tmp/#132358 (deleted)
09:35:01.604411 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.606859 bash(12220): CW /home/bnesbitt/.bash_history
09:35:01.606859 bash(12220): RCWO /home/bnesbitt/.bash_history
09:35:01.610768 gnome-terminal(8923): CW /tmp/#132355 (deleted)
09:35:01.610768 gnome-terminal(8923): CW /tmp/#132355 (deleted)
09:35:01.610856 gnome-terminal(8923): CW /tmp/#132356 (deleted)
09:35:01.610856 gnome-terminal(8923): CW /tmp/#132356 (deleted)
09:35:01.636285 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.636285 gnome-terminal(8923): RW /tmp/#132359 (deleted)
09:35:01.636285 gnome-terminal(8923): W /tmp/#132358 (deleted)
09:35:01.636285 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.666355 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.666355 gnome-terminal(8923): RW /tmp/#132359 (deleted)
09:35:01.666355 gnome-terminal(8923): W /tmp/#132358 (deleted)
09:35:01.666355 gnome-terminal(8923): RW /tmp/#132358 (deleted)
09:35:01.677547 gnome-terminal(8923): W /tmp/#132359 (deleted)
09:35:01.677547 gnome-terminal(8923): RW /tmp/#132359 (deleted)
09:35:01.677547 gnome-terminal(8923): W /tmp/#132358 (deleted)
09:35:01.677547 gnome-terminal(8923): RW /tmp/#132358 (deleted)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/865082

Title:
  gnome-terminal writes to /tmp on every line of output

Status in Gnome Virtual Terminal Emulator:
  Confirmed
Status in vte package in Ubuntu:
  Triaged

Bug description:
  STR:

  1. Start xterm
  2. Run python -mpyinotify /tmp
  3. Start gnome-terminal.
  4. Run some command like ls

  Actual Results:

  Observe a ton of IN_MODIFY lines such as
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vteD7DX2V path=/tmp 
pathname=/tmp/vteD7DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte1XDX2V path=/tmp 
pathname=/tmp/vte1XDX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte72DX2V path=/tmp 
pathname=/tmp/vte72DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vteD7DX2V path=/tmp 
pathname=/tmp/vteD7DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte1XDX2V path=/tmp 
pathname=/tmp/vte1XDX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vteD7DX2V path=/tmp 
pathname=/tmp/vteD7DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte1XDX2V path=/tmp 
pathname=/tmp/vte1XDX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte72DX2V path=/tmp 
pathname=/tmp/vte72DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vteD7DX2V path=/tmp 
pathname=/tmp/vteD7DX2V wd=1 
  Event dir=False mask=0x2 maskname=IN_MODIFY name=vte1XDX2V path=/tmp 
pathname=/tmp/vte1XDX2V wd=1 

  Or, when idle -
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteGFOF2V path=/tmp 
pathname=/tmp/vteGFOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteI7NF2V path=/tmp 
pathname=/tmp/vteI7NF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteVCOF2V path=/tmp 
pathname=/tmp/vteVCOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteGFOF2V path=/tmp 
pathname=/tmp/vteGFOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteI7NF2V path=/tmp 
pathname=/tmp/vteI7NF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteVCOF2V path=/tmp 
pathname=/tmp/vteVCOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteGFOF2V path=/tmp 
pathname=/tmp/vteGFOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteI7NF2V path=/tmp 
pathname=/tmp/vteI7NF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteVCOF2V path=/tmp 
pathname=/tmp/vteVCOF2V wd=1 
  Event dir=False mask=0x1 maskname=IN_ACCESS name=vteGFOF2V path=/tmp 
pathname=/tmp/vteGFOF2V wd=1 

  This looks like vte code storing something. According to this question - 
http://ubuntuforums.org/showthread.php?t=1830432,
  Sometimes vte creates temporary files which contains a copy of the whole 
scrollback buffer, [...].

  Expected results:
  Nothing is being written to this dir at this rate by gnome-terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64

[Desktop-packages] [Bug 1372604] [NEW] Setting browser Default application ineffective (screenshot attached). Gnome.

[Bryce Nesbitt]

Public bug reported:

In Ubuntu 14.04LTS:

In system settings there's a control for Default applications for Web.
This does not appear to change the gnome-conf settings.
See attached screenshot.
Note how Firefox is shown in one place, Chrome in the other.

This in turn leads to incorrect behavior when a program like an RSS reader, 
Skype or https://josm.openstreetmap.de/
wants to open a browser window to a particular URL.  Usually I end up with a 
blank Chrome window, where I wanted
a filled in Firefox window.

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-system-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: Selection_112.png
   
https://bugs.launchpad.net/bugs/1372604/+attachment/4211743/+files/Selection_112.png

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: evince (Ubuntu)
   Status: New = Invalid

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1372604

Title:
  Setting browser Default application ineffective (screenshot
  attached). Gnome.

Status in “evince” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New

Bug description:
  In Ubuntu 14.04LTS:

  In system settings there's a control for Default applications for Web.
  This does not appear to change the gnome-conf settings.
  See attached screenshot.
  Note how Firefox is shown in one place, Chrome in the other.

  This in turn leads to incorrect behavior when a program like an RSS reader, 
Skype or https://josm.openstreetmap.de/
  wants to open a browser window to a particular URL.  Usually I end up with a 
blank Chrome window, where I wanted
  a filled in Firefox window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1372604/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 606565] Re: Unclutter removes the cursor too quickly, inhibiting mouse-overs and TITLE tags in browsers.

[Bryce Harrington]

** Changed in: unclutter (Ubuntu)
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unclutter in Ubuntu.
https://bugs.launchpad.net/bugs/606565

Title:
  Unclutter removes the cursor too quickly, inhibiting mouse-overs and
  TITLE tags in browsers.

Status in “unclutter” package in Ubuntu:
  Confirmed
Status in “unclutter” package in Debian:
  New

Bug description:
  Binary package hint: unclutter

  I can't read the TITLE tag text on xkcd easily.

  My mouse cursor disappears too quickly.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: unclutter (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-8.13-genusername 2.6.35-rc5
  Uname: Linux 2.6.35-8-generic i686
  Architecture: i386
  Date: Sat Jul 17 00:25:48 2010
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100707)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: unclutter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unclutter/+bug/606565/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1360606] Re: libcairo.so for Ubuntu 14.04 is dead-slow compared to Ubuntu 13.10

[Bryce Harrington]

Thanks peter and chris, sounds like the issue is resolved so I'll close
the bug as suggested.

** Changed in: cairo (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1360606

Title:
  libcairo.so for Ubuntu 14.04 is dead-slow compared to Ubuntu 13.10

Status in “cairo” package in Ubuntu:
  Fix Released

Bug description:
  I'm running the video mixer software called Snowmix that uses libcairo
  extensively. After updating to Ubuntu 14.04 Desktop amd64, I noticed
  that mixing video required 8 times more CPU compared to Ubuntu 13.10.
  Using oprofile I discovered the heavy CPU load was taking place in
  libpixman used by libcairo. However libpixman is currently the same
  release in Ubuntu 14.04 and 13.10. However I did notice that libcairo
  got upgraded from libcairo.so.2.11200.16 in Ubuntu 13.10 to
  libcairo.so.2.11301.0 in Uuntu 14.04.

  Snowmix uses libcairo2 primarily for scaling and rotating images and
  overlay them in memory.

  Replacing libcairo.so.2.11301.0 with libcairo.so.2.11200.16 in Ubuntu
  14.04 lower the CPU usage by at least 8 times. So I suspect that
  libcairo for Ubuntu 14.04 somehow got compiled without the hardware
  acceleration such as MMX/SSE2/SSE3 etc. This is quite bad if this is
  the case. If it is not the case, something else is seriously wrong
  with libcairo2.

  1)Description:Ubuntu 14.04.1 LTS
Release:14.04
  2) libcairo2:
  Installed: 1.13.0~20140204-0ubuntu1
  Candidate: 1.13.0~20140204-0ubuntu1
  Version table:
 *** 1.13.0~20140204-0ubuntu1 0
  500 http://dk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  3) I expected libcairo2 (libcairo.so.2.11301.0) for Ubuntu14.04 to work as 
efficient as libcairo2 (libcairo.so.2.11200.16)for Ubuntu13.10.
  4) Libcairo2 for Ubuntu 14.04 works 8 times slower indicating a lack of 
MMX/SSE2/SSE3 etc acceleration.

  For the source, you have the source for libcairo2 for Ubuntu14.04.

  I can provide you with the source code for Snowmix using libcairo2,
  but I don't expected you need it nor want it.

  Best regards
  Peter Maersk-Moller

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libcairo2 1.13.0~20140204-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Sat Aug 23 15:23:38 2014
  InstallationDate: Installed on 2013-06-21 (428 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cairo
  UpgradeStatus: Upgraded to trusty on 2014-08-20 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1360606/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1281283] Re: Please merge liferea 1.10.3-1 from Debian unstable

[Bryce Nesbitt]

On Ubuntu 12.04:

(liferea:20434): GLib-GIO-CRITICAL **:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method
DescribeAll with signature  on interface org.gtk.Actions doesn't
exist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liferea in Ubuntu.
https://bugs.launchpad.net/bugs/1281283

Title:
  Please merge liferea 1.10.3-1 from Debian unstable

Status in “liferea” package in Ubuntu:
  Fix Released

Bug description:
  Debian changelog since laste merge:

  liferea (1.10.3-1) unstable; urgency=low

* New upstream release [October 2013]
* Removed patch add_files_to_potfiles.patch. Fixed upstream.
* Refreshed debian-example-feeds.patch.

   -- David Michael Smith sidic...@gmail.com  Sun, 13 Oct 2013
  00:11:46 +0800

  liferea (1.10.2-1) unstable; urgency=low

* New upstream release [September 2013] (Closes: 712961)
* wrap-and-sort maintenance.
* Remove lintian override.
* Added patch add_files_to_potfiles.patch to fix the fail to build due to
new translations files.

   -- David Michael Smith sidic...@gmail.com  Mon, 29 Jul 2013
  14:49:52 +0800

  liferea (1.10.1-1) experimental; urgency=low

* New upstream release [July 2013]
* Added recommends on gnome-icon-theme (Closes: #717028)
* Refreshed debian-example-feeds.patch.

   -- David Michael Smith sidic...@gmail.com  Tue, 16 Jul 2013
  18:20:17 +0800

  liferea (1.10~rc4-1) experimental; urgency=low

* New upstream release [June 2013]
  + fix segfault when opening audio/video attachment (Closes: #714074).

   -- David Michael Smith sidic...@gmail.com  Wed, 10 Jul 2013
  13:37:20 +0800

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1281283/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 967416] Re: inkscape crashed with SIGSEGV in file_save()

[Bryce Harrington]

Do we have a plan for fixing this?  Threading bugs can be so tricky...

Would it make sense to have the save routine set a lock when it starts,
and then have the exit thread check for existing locks and refuse or
delay exiting until they've cleared?  Perhaps the lock could be
timestamped so that the lock is only honored for, say, 10 seconds (the
save routine could re-issue the lock if it expects the save operation to
take more time than that.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/967416

Title:
  inkscape crashed with SIGSEGV in file_save()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Occurred when I closed Inkscape.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 15:01:15 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/967416/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 986816] Re: Inkscape crashed with SIGSEGV when saving drawing for first time

[Bryce Harrington]

I think this may not be an Inkscape bug.  It looks like the crash is
happening in the file chooser code due to trying to do a string
comparison against either an undefined string or a file named with
unicode characters (\240\371V\b)

 Thread 1 (Thread 0x7f024bbcb9c0 (LWP 31756)):
 #0  __strncmp_sse42 () at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:1738
 No locals.
 #1  0x7f024994de68 in completion_match_func (comp=optimized out, 
 key_unused=optimized out, iter=optimized out, data=optimized out) at 
 /build/buildd/gtk+2.0-2.24.10/gtk/gtkfilechooserentry.c:427
 chooser_entry = optimized out
 name = 0x947c550 \240\371V\b
 result = optimized out
 norm_file_part = 0x995c2c0 \001
 norm_name = 0x0
 #2  0x7f0249931b0a in gtk_entry_completion_visible_func (model=optimized 
 out, iter=0x7fff94e081d0, data=0x994f5b0) at 
 /build/buildd/gtk+2.0-2.24.10/gtk/gtkentrycompletion.c:821
 ret = 0
 completion = 0x994f5b0
 #3  0x7f0249a796ee in gtk_tree_model_filter_visible (filter=optimized 
 out, child_iter=optimized out) at 
 /build/buildd/gtk+2.0-2.24.10/gtk/gtktreemodelfilter.c:764

Anyway, I'm not even sure there's anything we could do to work around
this in Inkscape.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/986816

Title:
  Inkscape crashed with SIGSEGV when saving drawing for first time

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  I created a new drawing with a  copule of text boxes and three objects
  - two copied from the original - which was an intersection of two
  rounded boxes.

  The document saved successfully and then I got a message popup that
  there had been an error with Inkscape and had to close.  I was able to
  open the document in inkscape after I selected to restart Inkscape.

  I am using Ubuntu 12.04, last updated mid April.

  Inkscape version 0.48.3.1-1ubuntu1

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 22 11:37:45 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  ProcCmdline: inkscape
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f02445f8390:movzbl (%rsi),%ecx
   PC (0x7f02445f8390) ok
   source (%rsi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %ecx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
  Title: inkscape crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/986816/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 996487] Re: F11 key fullscreen view doesn't work on a webpage made fully by Adobe Flash player

[Bryce Harrington]

Confirmed behavior still exists on Ubuntu 14.04.

** Tags added: trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/996487

Title:
  F11 key fullscreen view doesn't work on a webpage made fully by Adobe
  Flash player

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  this is the page address http://www.bridgebase.com/client/client.php
  on this page, the key F11 for fullscreen view doesn't work

  Ubuntu 12.04 LTS 12.04

  firefox:
Installato: 12.0+build1-0ubuntu0.12.04.1
Candidato:  12.0+build1-0ubuntu0.12.04.1
Tabella versione:
   *** 12.0+build1-0ubuntu0.12.04.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main i386 
Packages
  100 /var/lib/dpkg/status
   11.0+build1-0ubuntu4 0
  500 http://it.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 12.0+build1-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alvise 1529 F pulseaudio
   /dev/snd/pcmC0D0p:   alvise 1529 F...m pulseaudio
  BuildID: 20120423122624
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd034 irq 43'
 Mixer name : 'Conexant CX20549 (Venice)'
 Components : 'HDA:14f15045,103c30a5,00100100'
 Controls  : 19
 Simple ctrls  : 9
  Channel: release
  Date: Tue May  8 13:18:53 2012
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 2
  Profiles: Profile0 (Default) - LastVersion=12.0/20120423122624 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-04-28 (10 days ago)
  dmi.bios.date: 04/25/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.24
  dmi.board.name: 30C6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.24:bd04/25/2007:svnHewlett-Packard:pnPresarioC500(GF866EA#ABZ):pvrF.24:rvnHewlett-Packard:rn30C6:rvr78.10:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Presario C500 (GF866EA#ABZ)
  dmi.product.version: F.24
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/996487/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 693852] Re: Decimal point on my numeric keyboard does not work. Is it because of regional settings?

[Bryce Nesbitt]

*** This bug is a duplicate of bug 795985 ***
https://bugs.launchpad.net/bugs/795985

Still true as of Ubuntu 12.04.4 LTS,
with US English Locale and 101 Key Keyboard.

Neither the numbers above the keyboard, nor the numeric pad . work.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gcalctool in Ubuntu.
https://bugs.launchpad.net/bugs/693852

Title:
  Decimal point on my numeric keyboard does not work. Is it because of
  regional settings?

Status in “gcalctool” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gcalctool

  Decimal point on my numeric keyboard does not work. Is it because of
  the regional setting? There is comma instead of dot on my numeric
  keyboard. In other programs like Open Office spreadsheet this comma
  key works without problem and produces dot in document.

  The superscript and subscript works with Alt or Ctrl + digit from main
  keyboard, but does not work, again, with digits from numeric keyboard.

  By the way I love this new calculator. It is the best.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gcalctool 5.32.0-0ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
  Uname: Linux 2.6.35-23-generic i686
  Architecture: i386
  Date: Thu Dec 23 18:06:59 2010
  ExecutablePath: /usr/bin/gcalctool
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.utf8
  SourcePackage: gcalctool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/693852/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1292699] Re: liferea froze while playing embedded video

[Bryce Harrington]

** Information type changed from Private to Public

** Bug watch added: Debian Bug tracker #739262
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739262

** Also affects: liferea (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739262
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to liferea in Ubuntu.
https://bugs.launchpad.net/bugs/1292699

Title:
  liferea froze while playing embedded video

Status in “liferea” package in Ubuntu:
  Confirmed
Status in “liferea” package in Debian:
  Unknown

Bug description:
  I was watching a youtube video embedded into an article and Liferea
  froze. I had to force it to close.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: liferea 1.10.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Mar 14 16:22:22 2014
  ExecutablePath: /usr/bin/liferea
  InstallationDate: Installed on 2014-02-22 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217)
  ProcCmdline: liferea
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0f3b12c470:cmp%edi,0x20(%rax)
   PC (0x7f0f3b12c470) ok
   source %edi ok
   destination 0x20(%rax) (0x0020) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: liferea
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: liferea crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1292699/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1283938] Re: Ubuntu 14.04 blank screen after wakeup from sleep

[Bryce]

Also affected. Upgraded from Xubuntu 13.10 to 14.04 64-bit. Acer Aspire
TimelineX Intel i5-2410M, Intel graphics.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1283938

Title:
  Ubuntu 14.04 blank screen after wakeup from sleep

Status in “xserver-xorg-video-ati” package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Samsung Serie 5 AMD notebook (find in attachment the hardware 
profile).
  OS: Ubuntu 14.04 (updated today).

  After wakeup the notebook from the sleep mode, the screen goes blank while 
the OS and the hardware is awake.
  (I can also press Ctrl+F1 and Ctrl+Alt+Del to reboot the system).

  This problem is not happening with the AMD property drivers (but they
  have another bug, i can't set up the brighness of the monitor).

  The problem in my opinion is related to this package:  xserver-xorg-
  video-ati.

  Changing quiet splash with nomodeset into /etc/default/grub makes
  the wakeup working, but the pc is really slow (can't be used), also
  after the normal start up.

  
  Best regards and have a good work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  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
  CurrentDesktop: Unity
  Date: Mon Feb 24 12:58:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7500G] [1002:990a] 
(prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd Device [144d:c660]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] 
[1002:6841] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-02-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140218)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U4C
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic 
root=UUID=9f8c7e92-a6ea-41fd-9489-a256c8b9f5d5 ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P06RAF.N93.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP535U4X-S01TH
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP06RAF.N93.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U4C:pvrP06RAF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U4X-S01TH:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U4C
  dmi.product.version: P06RAF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 12:54:54 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1283938/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1005717] Re: [965gm swizzling] Text font corruption after long suspend

[Bryce Harrington]

I no longer use the machine in question.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1005717

Title:
  [965gm swizzling] Text font corruption after long suspend

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Invalid

Bug description:
  == Problem ==
  After resume from suspend in metacity, fonts show vertical line corruption in 
firefox, terminal, etc.

  == Background ==
  I've seen plenty of other people's bug reports showing this behavior but have 
not see it myself on this machine as far as I can remember.

  After being away for Memorial Day Weekend (with machine in suspend),
  woke machine up and immediately saw the corruption for the first time
  on this machine.  The machine is put into suspend a LOT (via lid
  close).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu7
  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: None
  Date: Mon May 28 19:18:58 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Inspiron 1420 [1028:01f3]
 Subsystem: Dell Dell Inspiron 1420 [1028:01f3]
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron 1420
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=d993cb8c-a8a0-414a-8f5f-2853fad9f672 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0LE3C1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd08/15/2007:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0LE3C1:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1005717/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1121279] Re: Evoltiion-ews keeps asking for password for web xchange

[Bryce McNab]

The problem for me was that it could not resolve my Exchange Servers
host name. Once I straightened that out it connected right away. I'm not
sure if that is your problem or not, but could it be?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1121279

Title:
  Evoltiion-ews keeps asking for password for web xchange

Status in “evolution” package in Ubuntu:
  New

Bug description:
  During setup exchange ews asks for password and accepts it, but later
  on on every restarts it keeps asking for password and does not fetch
  emails. This account works perfectly on Android.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.5.0-24.37-generic 3.5.7.4
  Uname: Linux 3.5.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 10 10:12:33 2013
  InstallationDate: Installed on 2011-10-03 (496 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: Upgraded to quantal on 2012-09-17 (146 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1121279/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1251022] Re: Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)

[Bryce Nesbitt]

This is NOT a duplicate of #1079953

And 12.04 is a LTS support version, so a fix for 13.10 is not relevant.
The proper URL for the stable release updates is 
https://wiki.ubuntu.com/StableReleaseUpdates

The feature is completely broken in 12.04 LTS due tothe missing
dependency.

** This bug is no longer a duplicate of bug 1079953
   Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1251022

Title:
  Menu editor alacarte is completely non-functional in Ubuntu 12.04
  (applied patch did not take)

Status in “alacarte” package in Ubuntu:
  Confirmed

Bug description:
  While bug https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953 is 
closed,
  the issue persists.  With alacarte 0.13.2-2ubuntu4 on Ubuntu 12.04, nothing 
works.
  Pressing *New Item* or *Properties* results in a crash.  Checkbox actions 
don't take.
  And inexplicably [x] report an error does nothing.

  But here's a console exception:

  hardhat:~ alacarte 
  Traceback (most recent call last):
File /usr/share/alacarte/Alacarte/MainWindow.py, line 634, in 
on_properties_button_clicked
  self.on_edit_properties_activate(None)
File /usr/share/alacarte/Alacarte/MainWindow.py, line 391, in 
on_edit_properties_activate
  process = subprocess.Popen(['gnome-desktop-item-edit', file_path], 
env=os.environ)
File /usr/lib/python2.7/subprocess.py, line 679, in __init__
  errread, errwrite)
File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child
  raise child_exception
  OSError: [Errno 2] No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

[Bryce Nesbitt]

Using 12.04, fresh upgrade, fully patched:
 alacarte launches but clicking *Properties* or *New Item* results in a crash.
Checking [x] report this error does nothing apparent.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1079953

Title:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

Status in “alacarte” package in Ubuntu:
  Fix Released

Bug description:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

  SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official
  xubuntu .iso image, fully updated as of today.

  The 'Main Menu' editor (alacarte) is completely broken in xubuntu
  12.10.  Changes in the xubuntu Applications Menu made with alacarte
  are not effected.  For example:

  -- Ticking/unticking boxes in alacarte does not stick.
  -- New menu items created with alacarte are not put in place.
  -- Menu items deleted with alacarte remain in place.
  -- Moving items from one menu folder to another with alacarte no longer works.
  -- .desktop files of any menu item opened (with or without (!) change) in 
alacarte simply accumulate in /home/[user]/.local/share/applications, without 
further effect.
  -- sudo alacarte in a terminal no longer works.

  It appears that alacarte is dependent on an item (gnome-desktop-item-
  edit) provided by the gnome-panel package which is not not compiled
  with alacarte and which is not otherwise installed under xubuntu.
  (See also Launchpad Bug #656735 --
  https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/656735).
  However, the full gnome-panel is an alien package under xfce, and it
  should not be installed under xubuntu as it pulls in a mass of
  redundant and undesirable non-xfce gnome desktop functionality.
  (Note:  exo-utils for xfce,which provides exo-desktop-item-edit, IS
  fully installed but this does not resolve the above bugs.)

  Apart from these bugs, alacarte has limited functionality, it is prone
  to crashing, and it is awkward to handle.  Many of these problems have
  a very long history and are never properly addressed.

  It seems better if the alacarte Applications Menu Editor in xubuntu
  would be replaced as standard (or at least as an option through the
  (x)ubuntu repos) by LXMenuEditor (http://lxmed.sourceforge.net/).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

[Bryce Nesbitt]

And pressing HELP gives: The URI ‘ghelp:user-guide?menu-editor#menu-
editor’ does not point to a valid page.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1079953

Title:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

Status in “alacarte” package in Ubuntu:
  Fix Released

Bug description:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

  SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official
  xubuntu .iso image, fully updated as of today.

  The 'Main Menu' editor (alacarte) is completely broken in xubuntu
  12.10.  Changes in the xubuntu Applications Menu made with alacarte
  are not effected.  For example:

  -- Ticking/unticking boxes in alacarte does not stick.
  -- New menu items created with alacarte are not put in place.
  -- Menu items deleted with alacarte remain in place.
  -- Moving items from one menu folder to another with alacarte no longer works.
  -- .desktop files of any menu item opened (with or without (!) change) in 
alacarte simply accumulate in /home/[user]/.local/share/applications, without 
further effect.
  -- sudo alacarte in a terminal no longer works.

  It appears that alacarte is dependent on an item (gnome-desktop-item-
  edit) provided by the gnome-panel package which is not not compiled
  with alacarte and which is not otherwise installed under xubuntu.
  (See also Launchpad Bug #656735 --
  https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/656735).
  However, the full gnome-panel is an alien package under xfce, and it
  should not be installed under xubuntu as it pulls in a mass of
  redundant and undesirable non-xfce gnome desktop functionality.
  (Note:  exo-utils for xfce,which provides exo-desktop-item-edit, IS
  fully installed but this does not resolve the above bugs.)

  Apart from these bugs, alacarte has limited functionality, it is prone
  to crashing, and it is awkward to handle.  Many of these problems have
  a very long history and are never properly addressed.

  It seems better if the alacarte Applications Menu Editor in xubuntu
  would be replaced as standard (or at least as an option through the
  (x)ubuntu repos) by LXMenuEditor (http://lxmed.sourceforge.net/).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1251022] [NEW] Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)

[Bryce Nesbitt]

Public bug reported:

While bug https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953 is 
closed,
the issue persists.  With alacarte 0.13.2-2ubuntu4 on Ubuntu 12.04, nothing 
works.
Pressing *New Item* or *Properties* results in a crash.  Checkbox actions don't 
take.
And inexplicably [x] report an error does nothing.

But here's a console exception:

hardhat:~ alacarte 
Traceback (most recent call last):
  File /usr/share/alacarte/Alacarte/MainWindow.py, line 634, in 
on_properties_button_clicked
self.on_edit_properties_activate(None)
  File /usr/share/alacarte/Alacarte/MainWindow.py, line 391, in 
on_edit_properties_activate
process = subprocess.Popen(['gnome-desktop-item-edit', file_path], 
env=os.environ)
  File /usr/lib/python2.7/subprocess.py, line 679, in __init__
errread, errwrite)
  File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

** Affects: alacarte (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 12.04 regression-update unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1251022

Title:
  Menu editor alacarte is completely non-functional in Ubuntu 12.04
  (applied patch did not take)

Status in “alacarte” package in Ubuntu:
  New

Bug description:
  While bug https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953 is 
closed,
  the issue persists.  With alacarte 0.13.2-2ubuntu4 on Ubuntu 12.04, nothing 
works.
  Pressing *New Item* or *Properties* results in a crash.  Checkbox actions 
don't take.
  And inexplicably [x] report an error does nothing.

  But here's a console exception:

  hardhat:~ alacarte 
  Traceback (most recent call last):
File /usr/share/alacarte/Alacarte/MainWindow.py, line 634, in 
on_properties_button_clicked
  self.on_edit_properties_activate(None)
File /usr/share/alacarte/Alacarte/MainWindow.py, line 391, in 
on_edit_properties_activate
  process = subprocess.Popen(['gnome-desktop-item-edit', file_path], 
env=os.environ)
File /usr/lib/python2.7/subprocess.py, line 679, in __init__
  errread, errwrite)
File /usr/lib/python2.7/subprocess.py, line 1249, in _execute_child
  raise child_exception
  OSError: [Errno 2] No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

[Bryce Nesbitt]

https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1079953

Title:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

Status in “alacarte” package in Ubuntu:
  Fix Released

Bug description:
  Main Menu Editor alacarte is Completely Broken in xubuntu 12.10

  SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official
  xubuntu .iso image, fully updated as of today.

  The 'Main Menu' editor (alacarte) is completely broken in xubuntu
  12.10.  Changes in the xubuntu Applications Menu made with alacarte
  are not effected.  For example:

  -- Ticking/unticking boxes in alacarte does not stick.
  -- New menu items created with alacarte are not put in place.
  -- Menu items deleted with alacarte remain in place.
  -- Moving items from one menu folder to another with alacarte no longer works.
  -- .desktop files of any menu item opened (with or without (!) change) in 
alacarte simply accumulate in /home/[user]/.local/share/applications, without 
further effect.
  -- sudo alacarte in a terminal no longer works.

  It appears that alacarte is dependent on an item (gnome-desktop-item-
  edit) provided by the gnome-panel package which is not not compiled
  with alacarte and which is not otherwise installed under xubuntu.
  (See also Launchpad Bug #656735 --
  https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/656735).
  However, the full gnome-panel is an alien package under xfce, and it
  should not be installed under xubuntu as it pulls in a mass of
  redundant and undesirable non-xfce gnome desktop functionality.
  (Note:  exo-utils for xfce,which provides exo-desktop-item-edit, IS
  fully installed but this does not resolve the above bugs.)

  Apart from these bugs, alacarte has limited functionality, it is prone
  to crashing, and it is awkward to handle.  Many of these problems have
  a very long history and are never properly addressed.

  It seems better if the alacarte Applications Menu Editor in xubuntu
  would be replaced as standard (or at least as an option through the
  (x)ubuntu repos) by LXMenuEditor (http://lxmed.sourceforge.net/).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1243090] Re: Dist Upgrade from 13.04 to 13.10 stuck during flashplugin-installer

[Bryce Nesbitt]

Same here. S tuckarro:

...
  extracting fontinst.inf
  extracting Licen.TXT
All done, no errors.
All fonts downloaded and installed.
flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/
adobe-flashplugin/adobe-flashplugin_11.2.202.310.orig.tar.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1243090

Title:
  Dist Upgrade from 13.04 to 13.10 stuck during flashplugin-installer

Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in “update-notifier” package in Ubuntu:
  Confirmed

Bug description:
  When I was upgrading from Ubuntu 13.04 (raring) to Ubuntu 13.10
  (saucy), the installation was stuck for several hours here:

  flashplugin-installer: downloading
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz

  Eventually, due to a system reboot (caused by baby pounding on the
  keyboard), I had to recover from the half-finished upgrade process
  manually.

  It might be an isolated incident, but I am not alone, as seen by this
  user's experience here:

  13.04 to 13.10 upgrade stalled at flashplugin-installer, posted 
2013-10-19:
  
http://askubuntu.com/questions/361591/13-04-to-13-10-upgrade-stalled-at-flashplugin-installer

  After I got my system back in order (e.g. sudo dpkg --configure -a;
  purging obsolete/unneeded packages; removing ~/.config/gtk-3.0 to get
  the correct set of system tray icons; adding input methods, etc.), I
  tried sudo apt-get --reinstall install flashplugin-installer again:

  Processing triggers for update-notifier-common ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.310.orig.tar.gz

  And it got stuck again, with or without proxy.

  I originally suspected that it may have something to do with GFW of
  China, but then a normal wget
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz, albeit somewhat slow, fetched
  the file just fine, both with direct connection and with proxy.

  Digging deeper, it dawned on me that Ubuntu's flashplugin-installer
  differs from Debian's flashplugin-nonfree, mainly, the Ubuntu-specific
  update-notifier and its package-data-downloader Python script is
  used instead of wget for downloading external package data.

  So, I finally found /usr/share/package-data-downloads/flashplugin-installer,
  and in /usr/lib/update-notifier/package-data-downloader, these relevant 
lines:

  print %s: downloading %s % (relfile, files[i])
  dest_file = urllib.urlretrieve(files[i])[0]
  output = subprocess.check_output([sha256sum, 
dest_file])

  Failed to discover the location of the tempfile that
  urllib.urlretrieve() writes to, I fell asleep.

  Today, I decided to file this bug report before my interests die down
  and my memory fails me.  :-)

  As I was typing this, I tried to install flashplugin-installer again,
  and I discovered that urllib.urlretrieve() writes to /tmp/tmpXX.gz
  (e.g. /tmp/tmpXbszB4.gz) by default, and was able to see the file
  growing in size.

  True to Murphy's Law, despite failing to install flashplugin-installer
  for two days, now I see it installs successfully, as I am finishing
  this bug report!  :-p

  Nevertheless, I think this bug is worth looking into and taking care
  of.  There are at least two such confirmed incidents, and it is such a
  downer when the whole distribution upgrade process got stuck by
  something as innocuous as the Adobe Flash Plugin.  :-p

  A few points to look at:

   1.  Are Python's urllib.urlretrieve() and friends able to provide a
  download progress bar of some sort so that the end-user isn't stuck
  wondering whether the download stalled, or just that it is slow?

   2.  From my cable TV 6 Mbps Internet connection in Beijing, depending
  on the time of the day, the download speed
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz may get as low as 20KB/s or even
  10KB/s, which translates to 10 to 20 minutes of download for this 13MB
  tarball.  Even without connection timeout or whatnot, the end-user
  cannot help but wonder what is happening.  Debian's older flashplugin-
  nonfree package with wget's progress bar has the definite advantage
  here.

   3.  Does urllib.urlretrieve() and the rest of /usr/lib/update-
  notifier/package-data-downloader handle all kinds of exceptions like
  network error, DNS timeout, download interruption, etc. gracefully?
  Or are there some corner cases where stalling would indeed happen?

  Many thanks for looking into this!

  Cheers,
  Anthony Fok

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: flashplugin-installer 

[Desktop-packages] [Bug 1243090] Re: Dist Upgrade from 13.04 to 13.10 stuck during flashplugin-installer

[Bryce Nesbitt]

See also https://bugs.launchpad.net/ubuntu/+source/software-
center/+bug/919600

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to flashplugin-nonfree in Ubuntu.
https://bugs.launchpad.net/bugs/1243090

Title:
  Dist Upgrade from 13.04 to 13.10 stuck during flashplugin-installer

Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in “update-notifier” package in Ubuntu:
  Confirmed

Bug description:
  When I was upgrading from Ubuntu 13.04 (raring) to Ubuntu 13.10
  (saucy), the installation was stuck for several hours here:

  flashplugin-installer: downloading
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz

  Eventually, due to a system reboot (caused by baby pounding on the
  keyboard), I had to recover from the half-finished upgrade process
  manually.

  It might be an isolated incident, but I am not alone, as seen by this
  user's experience here:

  13.04 to 13.10 upgrade stalled at flashplugin-installer, posted 
2013-10-19:
  
http://askubuntu.com/questions/361591/13-04-to-13-10-upgrade-stalled-at-flashplugin-installer

  After I got my system back in order (e.g. sudo dpkg --configure -a;
  purging obsolete/unneeded packages; removing ~/.config/gtk-3.0 to get
  the correct set of system tray icons; adding input methods, etc.), I
  tried sudo apt-get --reinstall install flashplugin-installer again:

  Processing triggers for update-notifier-common ...
  flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.310.orig.tar.gz

  And it got stuck again, with or without proxy.

  I originally suspected that it may have something to do with GFW of
  China, but then a normal wget
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz, albeit somewhat slow, fetched
  the file just fine, both with direct connection and with proxy.

  Digging deeper, it dawned on me that Ubuntu's flashplugin-installer
  differs from Debian's flashplugin-nonfree, mainly, the Ubuntu-specific
  update-notifier and its package-data-downloader Python script is
  used instead of wget for downloading external package data.

  So, I finally found /usr/share/package-data-downloads/flashplugin-installer,
  and in /usr/lib/update-notifier/package-data-downloader, these relevant 
lines:

  print %s: downloading %s % (relfile, files[i])
  dest_file = urllib.urlretrieve(files[i])[0]
  output = subprocess.check_output([sha256sum, 
dest_file])

  Failed to discover the location of the tempfile that
  urllib.urlretrieve() writes to, I fell asleep.

  Today, I decided to file this bug report before my interests die down
  and my memory fails me.  :-)

  As I was typing this, I tried to install flashplugin-installer again,
  and I discovered that urllib.urlretrieve() writes to /tmp/tmpXX.gz
  (e.g. /tmp/tmpXbszB4.gz) by default, and was able to see the file
  growing in size.

  True to Murphy's Law, despite failing to install flashplugin-installer
  for two days, now I see it installs successfully, as I am finishing
  this bug report!  :-p

  Nevertheless, I think this bug is worth looking into and taking care
  of.  There are at least two such confirmed incidents, and it is such a
  downer when the whole distribution upgrade process got stuck by
  something as innocuous as the Adobe Flash Plugin.  :-p

  A few points to look at:

   1.  Are Python's urllib.urlretrieve() and friends able to provide a
  download progress bar of some sort so that the end-user isn't stuck
  wondering whether the download stalled, or just that it is slow?

   2.  From my cable TV 6 Mbps Internet connection in Beijing, depending
  on the time of the day, the download speed
  http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-
  flashplugin_11.2.202.310.orig.tar.gz may get as low as 20KB/s or even
  10KB/s, which translates to 10 to 20 minutes of download for this 13MB
  tarball.  Even without connection timeout or whatnot, the end-user
  cannot help but wonder what is happening.  Debian's older flashplugin-
  nonfree package with wget's progress bar has the definite advantage
  here.

   3.  Does urllib.urlretrieve() and the rest of /usr/lib/update-
  notifier/package-data-downloader handle all kinds of exceptions like
  network error, DNS timeout, download interruption, etc. gracefully?
  Or are there some corner cases where stalling would indeed happen?

  Many thanks for looking into this!

  Cheers,
  Anthony Fok

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: flashplugin-installer 11.2.202.310ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22