[Bug 2059859] Re: pam_env(sshd:session): deprecated reading of user environment enabled
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2059859 Title: pam_env(sshd:session): deprecated reading of user environment enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2059859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** Changed in: qemu (Ubuntu) Status: New => Fix Released ** Changed in: seabios (Ubuntu) Status: New => Fix Released ** Changed in: seabios (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: seabios (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: seabios (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: seabios (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: seabios (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice (Ubuntu) Status: New => Fix Released ** Changed in: spice (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: spice (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: spice (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-protocol (Ubuntu) Status: New => Fix Released ** Changed in: spice-protocol (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-protocol (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: spice-protocol (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-protocol (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: spice-protocol (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-vdagent (Ubuntu) Status: New => Fix Released ** Changed in: spice-vdagent (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-vdagent (Ubuntu Focal) Status: New => Fix Released ** Changed in: spice-vdagent (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: spice-vdagent (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: spice-vdagent (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virglrenderer (Ubuntu) Status: New => Fix Released ** Changed in: virglrenderer (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virglrenderer (Ubuntu Focal) Status: New => Fix Released ** Changed in: virglrenderer (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virglrenderer (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: virglrenderer (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virt-manager (Ubuntu) Status: New => Fix Released ** Changed in: virt-manager (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virt-manager (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: virt-manager (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: virt-manager (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: meson (Ubuntu) Status: New => Fix Released ** Changed in: meson (Ubuntu Focal) Status: New => Won't Fix ** Changed in: qemu (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** Changed in: dpdk (Ubuntu) Status: New => Fix Released ** Changed in: dpdk (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: dpdk (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: dpdk (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: dpdk (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: edk2 (Ubuntu) Status: New => Fix Released ** Changed in: edk2 (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: edk2 (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: edk2 (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: edk2 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: edk2 (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libslirp (Ubuntu) Status: New => Fix Released ** Changed in: libslirp (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libslirp (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libslirp (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libslirp (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: libslirp (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt (Ubuntu) Status: New => Fix Released ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt (Ubuntu Focal) Status: New => Fix Released ** Changed in: libvirt (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: libvirt (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt-python (Ubuntu) Status: New => Fix Released ** Changed in: libvirt-python (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt-python (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: libvirt-python (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt-python (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: libvirt-python (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: openvswitch (Ubuntu) Status: New => Fix Released ** Changed in: openvswitch (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: openvswitch (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: openvswitch (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: openvswitch (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: qemu (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: qemu (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: rdma-core (Ubuntu) Status: New => Fix Released ** Changed in: rdma-core (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: rdma-core (Ubuntu Focal) Status: New => Fix Released ** Changed in: rdma-core (Ubuntu Focal) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: rdma-core (Ubuntu Jammy) Status: Fix Committed => Fix Released ** Changed in: rdma-core (Ubuntu Jammy) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037695] Re: Backport packages to server-backports PPA from lunar
** Changed in: dpdk (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: dpdk (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: edk2 (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: edk2 (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: libslirp (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: libslirp (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: libvirt (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: libvirt (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: libvirt-python (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: libvirt-python (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: spice-vdagent (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: spice-vdagent (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: virt-manager (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: virt-manager (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: virglrenderer (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: virglrenderer (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: spice-protocol (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: spice-protocol (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: spice (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: spice (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: seabios (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: seabios (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: rdma-core (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: rdma-core (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: qemu (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: qemu (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: openvswitch (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: openvswitch (Ubuntu) Milestone: ubuntu-23.10 => None ** Changed in: meson (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: meson (Ubuntu) Milestone: ubuntu-23.10 => None -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/2037695 Title: Backport packages to server-backports PPA from lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2037695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** Changed in: virt-manager (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2072599] [NEW] Backport packages from oracular to server-backports PPA for jammy and noble
Public bug reported: Backport the following packages to the server-backports PPA for oracular:* ['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 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 ** Affects: dpdk (Ubuntu Noble) Importance: Undecided Status: New ** Affects: edk2 (Ubuntu Noble) Importance: Undecided Status: New ** Affects: libslirp (Ubuntu Noble) Importance: Undecided Status: New ** Affects: libvirt (Ubuntu Noble) Importance: Undecided Status: New ** Affects: libvirt-python (Ubuntu Noble) Importance: Undecided Status: New ** Affects: meson (Ubuntu Noble) Importance: Undecided Status: New ** Affects: openvswitch (Ubuntu Noble) Importance: Undecided Status: New ** Affects: qemu (Ubuntu Noble) Importance: Undecided Status: New ** Affects: rdma-core (Ubuntu Noble) Importance: Undecided Status: New ** Affects: seabios (Ubuntu Noble) Importance: Undecided Status: New ** Affects: spice (Ubuntu Noble) Importance: Undecided Status: New ** Affects: spice-protocol (Ubuntu Noble) Importance: Undecided Status: New ** Affects: spice-vdagent (Ubuntu Noble) Importance: Undecided Status: New ** Affects: virglrenderer (Ubuntu Noble) Importance: Undecided Status: New ** Affects: virt-manager (Ubuntu Noble) Importance: Undecided Status: New ** Tags: needs-ppa-backport ** Changed in: dpdk (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: edk2 (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: libslirp (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: libvirt (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: libvirt-python (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: meson (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: openvswitch (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: qemu (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: rdma-core (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: seabios (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: spice (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: spice-protocol (Ubuntu) Milestone: None => ubuntu-24.05 ** Changed in: spice-vdagent (Ubuntu) Milestone: None => ubuntu-24.05 **
[Bug 2040472] Re: Backport packages from noble(-devel) to server-backports PPA for focal and jammy, post-FF
** 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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040472/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713098] Re: Frequent DEP8 test failures related to ftp
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1713098 Title: Frequent DEP8 test failures related to ftp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875669] Re: autopkgtest failures
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1875669 Title: autopkgtest failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1875669/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2040472] [NEW] Backport packages from mantic to server-backports PPA for focal and jammy
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 ** Cha
[Bug 1939065] Re: autopkgtest failure in 0002-benchmark test
** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939065 Title: autopkgtest failure in 0002-benchmark test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939067] [NEW] FTBFS 5.0.3-2 due to missing symbols
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 Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939067 Title: FTBFS 5.0.3-2 due to missing symbols To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939065] [NEW] autopkgtest failure in 0002-benchmark test
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 Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1939065 Title: autopkgtest failure in 0002-benchmark test To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1939065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1939058] [NEW] autopkgtest failure "stacking/override-redirect.metatest" on armhf
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1939058 Title: autopkgtest failure "stacking/override-redirect.metatest" on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1939058/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1855318] Re: autofs tries to find .xdg-volume-info and autorun.inf
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 Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1855318 Title: autofs tries to find .xdg-volume-info and autorun.inf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1855318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1580451] Re: mutter does not remember position of extra displays
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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1580451 Title: mutter does not remember position of extra displays To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1580451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
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 Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transparency/graphics corruption issue when
GTK_IM_MODULE=xim is set
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1760818/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
I can't say for certain if the issue resides with ssh-askpass-fullscreen or is a UI usability issue in unity, gnome, or elsewhere, however this UI is not driven by OpenSSH itself, so I'll retarget this bugtask to ssh-askpass-fullscreen as a slightly more likely candidate. ** Package changed: openssh (Ubuntu) => ssh-askpass-fullscreen (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1843201/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826438] Re: Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826438] [NEW] Extra Bottom Edge Padding in RMB Context Menu for Folder, but not files
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817269] Re: New Desktop Icons Overlap Existing Icons
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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1817269 Title: New Desktop Icons Overlap Existing Icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1817269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817269] [NEW] New Desktop Icons Overlap Existing Icons
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 2018-1
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
** Tags removed: verification-done-cosmic ** Tags added: verification-failed-cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778344] Re: Shotwell exports images with DPI of 1 according to windows
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 Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1778344 Title: Shotwell exports images with DPI of 1 according to windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1778344] [NEW] Shotwell exports images with DPI of 1 according to windows
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 Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1778344 Title: Shotwell exports images with DPI of 1 according to windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1778344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** Changed in: inkscape Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719062] [NEW] systemd-resolved malformed packet on cert dns lookup
Public bug reported: systemd-resolved returns a malformed packet when looking up an openpgp key (via a cert record rfc4398) from my internal authoritative dns server. The command I used was gpg2 -v --auto-key-locate=clear,cert,local --locate-keys [Email Address] This works correctly if I change /etc/resolv.conf symlink to point at /run/systemd/resolve/resolv.conf so that it doesn't use the local systemd-resolved resolver/cache instead of /run/resolvconf/resolv.conf I'm including a wireshark capture of the malformed packet (filtered for 127.0.0.53). I noticed that this was over udp. If I recall correctly, cert records are usually big enough that they require using tcp. Description:Ubuntu Artful Aardvark (development branch) Release:17.10 systemd: Installed: 233-8ubuntu3 Candidate: 233-8ubuntu3 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bug.pcapng" https://bugs.launchpad.net/bugs/1719062/+attachment/4955485/+files/bug.pcapng -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1719062 Title: systemd-resolved malformed packet on cert dns lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1719062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1269838] Re: gnome-session.log takes 8 GB in a few hours
@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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1269838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 575877] Re: gnome-keyring mysteriously asks for keyring password on startup
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 Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/575877 Title: gnome-keyring mysteriously asks for keyring password on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/575877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
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 Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
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 Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles
(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 Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/951585 Title: gvfsd-afp consumes 100% of processor cycles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951585] Re: gvfsd-afp consumes 100% of processor cycles
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=, fini=, rtld_fini=,
stack_end=0x7fff04eca8d8)
at libc-start.c:287
#15 0x00406bc9 in ?? ()
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/951585
Title:
gvfsd-afp consumes 100% of processor cycles
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/951585/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
>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 Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
@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 Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430620] [NEW] gnome-terminal writes excessively to /tmp (affecting SSD drives)
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 gnome-terminal(23352
[Bug 1430620] Re: gnome-terminal writes excessively to /tmp (affecting SSD drives)
See also http://ubuntuforums.org/showthread.php?t=1830432 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1430620 Title: gnome-terminal writes excessively to /tmp (affecting SSD drives) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1430620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 865082] Re: gnome-terminal writes to /tmp on every line of output
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 Ubuntu Desktop Bugs, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/865082 Title: gnome-terminal writes to /tmp on every line of output To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/865082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1372604] [NEW] Setting browser "Default application" ineffective (screenshot attached). Gnome.
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 Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1372604 Title: Setting browser "Default application" ineffective (screenshot attached). Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1372604/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 693852] Re: Decimal point on my numeric keyboard does not work. Is it because of regional settings?
*** 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 Ubuntu Desktop Bugs, 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? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/693852/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1121279] Re: Evoltiion-ews keeps asking for password for web xchange
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 Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1121279 Title: Evoltiion-ews keeps asking for password for web xchange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1121279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251022] Re: Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)
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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1251022] [NEW] Menu editor alacarte is completely non-functional in Ubuntu 12.04 (applied patch did not take)
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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1251022/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984357] Re: gnome-panel crashed with SIGSEGV in magazine_chain_pop_head()
Seems to be easily reproducible on 12.04 (tested on several machines). Found this googling around a bit, found https://mail.gnome.org/archives /gtk-devel-list/2010-December/msg00065.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/984357 Title: gnome-panel crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/984357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984357] Re: gnome-panel crashed with SIGSEGV in magazine_chain_pop_head()
** Information type changed from Private to Public ** Changed in: gnome-panel (Ubuntu) Importance: Medium => High ** Changed in: gnome-panel (Ubuntu) Status: Confirmed => Triaged ** Description changed: gnome-panel crashed when I changed the theme from Ambiance to Radiance. + + Thread 1 (Thread 0x7fd61b0ed980 (LWP 6929)): + #0 magazine_chain_pop_head (magazine_chunks=0x1999660) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:528 + #1 thread_memory_magazine1_alloc (ix=, tmem=) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:835 + mag = 0x1999660 + #2 g_slice_alloc (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:994 + tmem = 0x1999650 + #3 0x7fd6185d71a6 in g_slice_alloc0 (mem_size=16) at /build/buildd/glib2.0-2.32.1/./glib/gslice.c:1029 + #4 0x7fd61a2d6a8b in gtk_widget_path_new () at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkwidgetpath.c:119 + #5 0x7fd61a2d6ac5 in gtk_widget_path_copy (path=0x1e56b6f) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkwidgetpath.c:175 + __PRETTY_FUNCTION__ = "gtk_widget_path_copy" + #6 0x7fd61a221b5a in create_query_path (context=0x1cfc6e0) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkstylecontext.c:1039 + priv = 0x1cfc700 + #7 style_data_lookup (context=0x1cfc6e0, state=GTK_STATE_FLAG_BACKDROP) at /build/buildd/gtk+3.0-3.4.1/./gtk/gtkstylecontext.c:1104 + path = 0x1ed4080 + priv = 0x1cfc700 + __PRETTY_FUNCTION__ = "style_data_lookup" ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-panel 1:3.4.1-0ubuntu1 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: Tue Apr 17 22:41:22 2012 ExecutablePath: /usr/bin/gnome-panel InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111005) ProcCmdline: gnome-panel --replace SegvAnalysis: - Segfault happened at: 0x7fd6185d6ded :mov 0x8(%rax),%rbx - PC (0x7fd6185d6ded) ok - source "0x8(%rax)" (0x1e56d0008) not located in a known VMA region (needed readable region)! - destination "%rbx" ok + Segfault happened at: 0x7fd6185d6ded :mov 0x8(%rax),%rbx + PC (0x7fd6185d6ded) ok + source "0x8(%rax)" (0x1e56d0008) not located in a known VMA region (needed readable region)! + destination "%rbx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-panel StacktraceTop: - g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - gtk_widget_path_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - gtk_widget_path_copy () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + gtk_widget_path_new () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + gtk_widget_path_copy () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-panel crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to precise on 2012-02-25 (52 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/984357 Title: gnome-panel crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/984357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
** Changed in: xkeyboard-config (Ubuntu Precise) Assignee: Bryce Harrington (bryce) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1154838] Re: when I run the program "brightness & lock" the brightness goes to the maximum
** Package changed: xorg (Ubuntu) => gnome-power-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1154838 Title: when I run the program "brightness & lock" the brightness goes to the maximum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1154838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Tags added: raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1011257] Re: x-gvfs-show option doesn't work
** Also affects: gnome-disk-utility (Ubuntu Raring) Importance: Undecided Status: Confirmed ** Changed in: gnome-disk-utility (Ubuntu Raring) Milestone: None => ubuntu-13.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1011257 Title: x-gvfs-show option doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1011257/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1138315] Re: Could not apply the stored configuration for monitors
Sounds like a dupe of bug 1145689 (which has more detailed logs attached). Workaround would be to move aside ~/.config/monitors.xml (but attach it here first). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1138315 Title: Could not apply the stored configuration for monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1138315/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1145689] Re: error dialog due to problems monitors.xml file after dist-upgrade
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1145689 Title: error dialog due to problems monitors.xml file after dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1145689/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388547] Re: Volume keys don't work inside a full-screen game
** Also affects: hundredpapercuts/precise Importance: Undecided Status: New ** Also affects: hundredpapercuts/quantal Importance: Undecided Status: New ** Also affects: hundredpapercuts/raring Importance: Undecided Status: Confirmed ** Changed in: hundredpapercuts/quantal Status: New => Confirmed ** Changed in: hundredpapercuts/precise Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/388547 Title: Volume keys don't work inside a full-screen game To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1113678] Re: X server starts with brightness at lowest possible level (off!) in raring
Unless you narrow the problem to the X driver specifically, probably better to just handle it as a gnome-power-manager issue. ** Package changed: xorg (Ubuntu) => gnome-power-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1113678 Title: X server starts with brightness at lowest possible level (off!) in raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1113678/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
[Unsubscribing ubuntu-sponsors since it appears the posted patches need further work.] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 466667] Re: totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:863: vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed.
*** This bug is a duplicate of bug 1059316 *** https://bugs.launchpad.net/bugs/1059316 ** This bug is no longer a duplicate of bug 459637 totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:863: vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed. ** This bug has been marked a duplicate of bug 1059316 vlc assert failure: vlc: vm.c:956: vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/47 Title: totem assert failure: totem: /build/buildd/libdvdnav-4.1.3/src/vm/vm.c:863: vm_get_video_aspect: Assertion `aspect == 0 || aspect == 3' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/47/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160264] Re: [nvidia] compiz displays white screen when locked
** Changed in: xorg-server (Ubuntu Hardy) Assignee: Bryce Harrington (bryce) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/160264 Title: [nvidia] compiz displays white screen when locked To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/160264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
@Roman, I mean details like verifying that you have the right version of xkeyboard-config installed. You may need to reboot, as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
** Package changed: xserver-xorg-video-intel (Ubuntu) => gnome-settings- daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu S-series) Status: Confirmed => Triaged ** Changed in: gnome-settings-daemon (Ubuntu S-series) Importance: Undecided => High ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Low => Wishlist ** Changed in: gnome-settings-daemon (Ubuntu S-series) Importance: High => Wishlist ** Changed in: gnome-settings-daemon (Ubuntu Quantal) Importance: Low => Wishlist ** Changed in: gnome-settings-daemon (Ubuntu Precise) Importance: High => Wishlist ** Changed in: gnome-settings-daemon (Ubuntu Oneiric) Importance: Medium => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828623] Re: [Regression] gnome control centre does not allow you to disable the laptop screen while leaving an external DisplayPort connected screen working
It's been long enough that there's probably not much value in completing the oneiric backport. ** Changed in: gnome-control-center (Ubuntu Oneiric) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/828623 Title: [Regression] gnome control centre does not allow you to disable the laptop screen while leaving an external DisplayPort connected screen working To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/828623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)
** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: Canonical X.org (canonical-x) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/408903 Title: Does not handle microphone mute button (KEY_MICMUTE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/408903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388547] Re: Volume keys don't work inside a full-screen game
A while ago we wrote up some architecture and troubleshooting documents for hotkeys - https://wiki.ubuntu.com/Hotkeys Some of that has gotten dated (e.g. we don't use HAL anymore), but it's still roughly descriptive. Many of the tools listed there are still useful in isolating where in the stack problems creep in. I'd like to see if I can reproduce this issue locally. Can someone suggest a game (ideally a freely available one) that demonstrates this behavior? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/388547 Title: Volume keys don't work inside a full-screen game To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
@Roman, more details needed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
** Description changed: + [Impact] + F10 behaves the same as Shift-F10. This causes menus to pop up incorrectly. + + [Fix] + Upstream patch preserves Shift so that Shift-F10 and F10 act as separate keys. + + [Test Case] + 1. Open a gnome-terminal window + 2. Run aptitude + 3. Press F10 + + Expected behavior: Aptitude's menu opens + Broken behavior: Menus for both aptitude and gnome-terminal are shown. + + In different window environments (e.g. unity) other menus can be + triggered than should be. + + [Regression Potential] + The patch simply changes a keyboard layout config file, so the severity of any possible regression would be limited to keyboard configuration misbehaviors. This is a well reviewed, tested patch from upstream and not expected to have any regression. + + [Original Report] Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=661973 Visible in Unity - change keybinding for opening first global menu entry to Alt+F10. Pressing F10 triggers short flash of global menu nevertheless. When you disable the F10 shortcut in gnome-terminal, pressing the key triggers context menu in gnome terminal. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-0 3.3.14-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.92-0ubuntu1 Architecture: i386 Date: Tue Feb 21 16:29:08 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120119) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)
** Also affects: gtk+2.0 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: xkeyboard-config (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Precise) Importance: Undecided Status: New ** No longer affects: gtk+3.0 (Ubuntu Precise) ** Changed in: gtk+2.0 (Ubuntu Precise) Status: New => Invalid ** Changed in: xkeyboard-config (Ubuntu Precise) Importance: Undecided => High ** Changed in: xkeyboard-config (Ubuntu Precise) Status: New => Fix Committed ** Changed in: xkeyboard-config (Ubuntu Quantal) Status: Triaged => Fix Committed ** Changed in: xkeyboard-config (Ubuntu Precise) Assignee: (unassigned) => Bryce Harrington (bryce) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/937822 Title: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937822/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1051027] Re: MacBookAir3, 1 loses desktop background image after suspend/resume
Unlikely to be X doing this, but feel free to reopen if evidence comes to light indicating X is doing something wrong. I'd suggest also trying multiple times and see if the fault is reproducible or not. ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1051027 Title: MacBookAir3,1 loses desktop background image after suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1051027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 859104] Re: Nautilus extensions written in Python do not work in Oneiric
The postr task should now be fixed due to the sync for bug #1050484 ** Changed in: postr (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/859104 Title: Nautilus extensions written in Python do not work in Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus-pastebin/+bug/859104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 948667] Re: gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants()
** Changed in: gnome-panel (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/948667 Title: gnome-panel crashed with SIGSEGV in gtk_widget_pop_verify_invariants() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/948667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 945987] Re: No Settings are available in "Preferred format", only preset defaults are used
Not sure from comment #42 why this failed verification, but as there is at the moment nothing further to be sponsored, I'm unsubbing sponsors for now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/945987 Title: No Settings are available in "Preferred format", only preset defaults are used To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/945987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998156] Re: GTK Print dialog sends broken custom page size attribute: "PageSize=Custom.Custom.x"
** Description changed:
- When trying to print a photo, the printer stops with status "rendering
- completed". I have to remove all printing jobs and restart CUPS to be
- able to print again. This error does not occur when printing other
- documents, i.e. simple text.
+ [Impact]
+
+ [Fix]
+
+ [Test Case]
+
+ [Regression Potential]
+
+ [Original Report]
+ When trying to print a photo, the printer stops with status "rendering
completed". I have to remove all printing jobs and restart CUPS to be able to
print again. This error does not occur when printing other documents, i.e.
simple text.
I use a HP PhotoSmart b109a connected to a Fritz!Box 7390 wireless
router ("socket://fritz.box:9100").
This bug is also present in Debian: http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=664031
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/998156
Title:
GTK Print dialog sends broken custom page size attribute:
"PageSize=Custom.Custom.x"
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/998156/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 940569] Re: Adding playlist inserts the new entry at the wrong spot in the playlist list (temporarily)
I'm no longer using rhythmbox. ** Changed in: rhythmbox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/940569 Title: Adding playlist inserts the new entry at the wrong spot in the playlist list (temporarily) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/940569/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 945987] Re: No Settings are available in "Preferred format", only preset defaults are used
** Description changed: This has been going on since 11.10 dev, maybe should be addressed - In Edit - Preferences, the Settings button is greyed out & unavailable. So there is no user available means to adjust encoding for vorbis, mp3, mp4, ect. + In Edit > Preferences, on the Music tab the Settings button for Preferred Format is greyed out & unavailable. So there is no user available means to adjust encoding for vorbis, mp3, mp4, ect. Even using something like sound-juicer to change the very same 'Preferred.. ' is of no use, Rhythmbox doesn't use. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.95-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94-0ubuntu1 Architecture: i386 Date: Sat Mar 3 19:25:18 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120302) ProcEnviron: - TERM=xterm - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/945987 Title: No Settings are available in "Preferred format", only preset defaults are used To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/945987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 221112] Re: Can't use space bar in search bar when using french alternative keyboard
The fix has been reverted out, due to a bug report (bug #1013881) filed about it during testing in -proposed. You guys will need to work with upstream to find a better way of fixing it that doesn't cause regressions for anyone. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 221112] Re: Can't use space bar in search bar when using french alternative keyboard
** Changed in: xkeyboard-config (Ubuntu Precise) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
In investigating further it appears that something (apport?) is linking people to this bug report. However, this bug was fixed four years ago. It's likely the logic in whatever is linking to this is faulty in some fashion, rather than that this ancient crash has "come back". In any case, like I said, a new bug should be filed for this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/197153 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/197153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 197153] Re: gnome-settings-daemon crashed with SIGSEGV
This bug is closed; it's better to open a new bug (with fresh backtrace and logs) than to comment on this one. ** Changed in: gnome-desktop (Ubuntu) Assignee: Bryce Harrington (bryce) => (unassigned) ** Changed in: gnome-control-center (Ubuntu) Assignee: Bryce Harrington (bryce) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/197153 Title: gnome-settings-daemon crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/197153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1006413] Re: quantal 20120530 cannot set displays on dual monitor
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1006413 Title: quantal 20120530 cannot set displays on dual monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1006413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1007588] Re: quantal 1 June i386.iso external monitor
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1007588 Title: quantal 1 June i386.iso external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1007588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1008249] Re: quantal 3 June daily build external monitor DBus error
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1008249 Title: quantal 3 June daily build external monitor DBus error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1008249/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 906987] Re: syndaemon polls 5 times a second even though it is started with the -R XRecord extension option
@Sarvatt, is there anything we should do on the -synaptics end for this bug? When we looked at the issue previously it did not seem like XRecord was easily fixable for this usage; are there any new ideas on what we might do (even if just papering over it...)? ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Milestone: ubuntu-12.04 => None -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/906987 Title: syndaemon polls 5 times a second even though it is started with the -R XRecord extension option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/906987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985264] Re: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node()
405: *hash_return = hash_value; 406: 407: node_index = hash_value % hash_table->mod; /* SIGFPE */ 408: node_hash = hash_table->hashes[node_index]; Attached patch should fix it. ** Patch added: "0001-Fix-modulo-division-by-zero-SIGFPE-in-g_hash_table_l.patch" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/985264/+attachment/3173204/+files/0001-Fix-modulo-division-by-zero-SIGFPE-in-g_hash_table_l.patch ** Changed in: rhythmbox (Ubuntu) Status: New => In Progress ** Changed in: rhythmbox (Ubuntu) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/985264 Title: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/985264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 806306] Re: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
Are you able to reproduce this on Precise? I attempted using the directions provided, but on ejecting the first disc, rb cleared itself. The second cd was detected and loaded ok. There have been some significant changes to the section of glib2.0 code this bug hit, perhaps it already got fixed upstream. ** Changed in: rhythmbox (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/806306 Title: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/806306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 985264] Re: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node()
** Visibility changed to: Public ** Changed in: rhythmbox (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/985264 Title: rhythmbox crashed with SIGFPE in g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/985264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 806306] Re: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
#1 0x7f08dd022a56 in g_hash_table_lookup_node (hash_table=0x41ec880, key=0x41ec890, notify=1) at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:313 node = node_index = hash_value = step = 0 313:hash_value = (* hash_table->hash_func) (key); 314:if (G_UNLIKELY (hash_value <= 1)) 315: hash_value = 2; 316: 317:node_index = hash_value % hash_table->mod; Can hash_table->hash_func == NULL ? Line 313 has been since changed by this patch: http://git.gnome.org/browse/glib/commit/glib/ghash.c?id=88f23fb1d9aa0f84cbeebe086db022864a7eb3be -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/806306 Title: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node() To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/806306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 806306] Re: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
** Description changed:
Steps to reproduce:
1. insert a CD
2. let rhythmbox recognize it
3. remove it with the button on the drive
4. the CD is now removed from the drive but rhythmbox already shows it
5. now insert a new CD
6. rhythmbox crashes
+
+ #0 0x7f08c4128740 in ?? ()
+ No symbol table info available.
+ #1 0x7f08dd022a56 in g_hash_table_lookup_node (hash_table=0x41ec880,
key=0x41ec890, notify=1) at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:313
+ node =
+ node_index =
+ hash_value =
+ step = 0
+ #2 g_hash_table_remove_internal (hash_table=0x41ec880, key=0x41ec890,
notify=1) at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:1093
+ node =
+ node_index = 3290159760
+ __PRETTY_FUNCTION__ = "g_hash_table_remove_internal"
+ #3 0x7f08e1ae059c in remove_child (data=,
parent=) at rhythmdb-tree.c:1514
+ _g_boolean_var_ =
+ #4 0x7f08e1ae0631 in remove_entry_from_album (db=,
entry=0x41ec890) at rhythmdb-tree.c:1535
+ table = 0x3ad0b70
+ __PRETTY_FUNCTION__ = "remove_entry_from_album"
+ #5 0x7f08e1ae4675 in rhythmdb_tree_entry_set (adb=,
entry=0x41ec890, propid=, value=) at
rhythmdb-tree.c:1608
+ artist =
+ genre =
+ albumname = 0x7f08c41bda90 ""
+ db = 0x1d64040
+ type = 0x7f08c4128740
+ __PRETTY_FUNCTION__ = "rhythmdb_tree_entry_set"
+ #6 0x7f08e1acf8b6 in rhythmdb_entry_set_internal (db=0x1d64040,
entry=0x41ec890, notify_if_inserted=, propid=5,
value=0x7fff7aeb6ff0) at rhythmdb.c:3345
+ klass = 0x1cfa9b0
+ handled =
+ podcast = 0x0
+ old_value = {g_type = 0, data = {{v_int = 0, v_uint = 0, v_long = 0,
v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer =
0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 =
0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
+ nop =
+ __PRETTY_FUNCTION__ = "rhythmdb_entry_set_internal"
+ #7 0x7f08b5f98fc1 in update_tracks (source=,
property=RHYTHMDB_PROP_ALBUM, value=0x7fff7aeb6ff0) at rb-audiocd-source.c:1178
+ priv = 0x1d5ea90
+ db = 0x1d64040
+ i = 0x3aa2560
+
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: rhythmbox 0.13.3-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Wed Jul 6 06:50:47 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: rhythmbox
ProcEnviron:
- LANGUAGE=de_DE:en
- PATH=(custom, user)
- LANG=de_DE.UTF-8
- SHELL=/bin/bash
+ LANGUAGE=de_DE:en
+ PATH=(custom, user)
+ LANG=de_DE.UTF-8
+ SHELL=/bin/bash
SegvAnalysis:
- Segfault happened at: 0x7f08c4128740:add%dl,0x1d1(%rcx)
- PC (0x7f08c4128740) in non-executable VMA region:
0x7f08c400-0x7f08c425d000 rw-p None
- source "%dl" ok
- destination "0x1d1(%rcx)" (0xc4128911) not located in a known VMA region
(needed writable region)!
+ Segfault happened at: 0x7f08c4128740:add%dl,0x1d1(%rcx)
+ PC (0x7f08c4128740) in non-executable VMA region:
0x7f08c400-0x7f08c425d000 rw-p None
+ source "%dl" ok
+ destination "0x1d1(%rcx)" (0xc4128911) not located in a known VMA region
(needed writable region)!
SegvReason:
- executing writable VMA None
- writing unknown VMA
+ executing writable VMA None
+ writing unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
- ?? ()
- g_hash_table_lookup_node (hash_table=0x41ec880, key=0x41ec890, notify=1) at
/build/buildd/glib2.0-2.28.6/./glib/ghash.c:313
- g_hash_table_remove_internal (hash_table=0x41ec880, key=0x41ec890, notify=1)
at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:1093
- remove_child (data=, parent=) at
rhythmdb-tree.c:1514
- remove_entry_from_album (db=, entry=0x41ec890) at
rhythmdb-tree.c:1535
+ ?? ()
+ g_hash_table_lookup_node (hash_table=0x41ec880, key=0x41ec890, notify=1) at
/build/buildd/glib2.0-2.28.6/./glib/ghash.c:313
+ g_hash_table_remove_internal (hash_table=0x41ec880, key=0x41ec890, notify=1)
at /build/buildd/glib2.0-2.28.6/./glib/ghash.c:1093
+ remove_child (data=, parent=) at
rhythmdb-tree.c:1514
+ remove_entry_from_album (db=, entry=0x41ec890) at
rhythmdb-tree.c:1535
Title: rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
UpgradeStatus: Upgraded to natty on 2011-04-23 (73 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
** Changed in: rhythmbox (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/806306
Title:
rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node()
To manage notifications about this bug go to:
https://bugs.launchpad.net/rhyth
[Bug 974066] Re: rhythmbox crashed with SIGSEGV in rhythmdb_entry_delete()
*** This bug is a duplicate of bug 806306 *** https://bugs.launchpad.net/bugs/806306 ** This bug is no longer a duplicate of private bug 939555 ** This bug has been marked a duplicate of bug 806306 rhythmbox crashed with SIGSEGV in g_hash_table_lookup_node() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/974066 Title: rhythmbox crashed with SIGSEGV in rhythmdb_entry_delete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/974066/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 879528] Re: Display utility doesn't offer to use nvidia-settings with proprietary drivers installed?
Now that -nvidia supports xrandr 1.2, it's probably not worth the effort to fix this. For quantal, presumably the stock config dialog should "just work" with nvidia, so no need for special hacks there. And for precise, unfortunately I think even if we did come up with a special hack it wouldn't be SRUable anyway. I think this bug can be closed as WONTFIX. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/879528 Title: Display utility doesn't offer to use nvidia-settings with proprietary drivers installed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/879528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
