[Bug 1457321] [NEW] lxc-stop does not shut down container
Public bug reported: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html SRU TEST CASE: -- - Create a vivid LXC container (system or unprivileged) - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. REGRESSION POTENTIAL: - - This new unit is only active in containers (LXC, docker, nspawn, etc.). There a possible regression is that someone is running/testing nut or a similar UPS responder in a container, but that seems like a theoretical scenario only. - There is no change for VMs or real hardware. ** Affects: systemd (Ubuntu) Importance: Medium Assignee: Martin Pitt (pitti) Status: In Progress ** Affects: systemd (Ubuntu Vivid) Importance: Medium Status: New ** Affects: systemd (Ubuntu Wily) Importance: Medium Assignee: Martin Pitt (pitti) Status: In Progress ** Tags: systemd-boot ** Also affects: systemd (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Vivid) Importance: Undecided Status: New ** Tags added: systemd-boot ** Changed in: systemd (Ubuntu Wily) Importance: Undecided = Medium ** Changed in: systemd (Ubuntu Vivid) Importance: Undecided = Medium ** Description changed: lxc-stop sends SIGPWR to a container's pid 1 to notify it that it should shut down. This merely starts sigpwr.target right now, but nothing is hooked into it. That's deliberate for real iron systems as there it's usually UPSes sending that, which should be handled by e. g. nut, not directly systemd. However, for containers I believe that's a safe default. https://lists.linuxcontainers.org/pipermail/lxc- users/2015-May/009279.html + + SRU TEST CASE: + -- + - Create a vivid LXC container (system or unprivileged) + - Try to lxc-stop it. With current vivid it will do nothing/hang, with the proposed version it will shut down as expected. ** Changed in: systemd (Ubuntu Wily) Status: New = In Progress ** Changed in: systemd (Ubuntu Wily) Assignee: (unassigned) = Martin Pitt (pitti) -- 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/1457321 Title: lxc-stop does not shut down container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457398] [NEW] systemd immediately unmounts manually mounted directories
Public bug reported: Hi, I've installed Ubuntu Vivid in OpenVZ container and observing strange systemd behaviour. Every time I do bind mount systemd immideately umounts it. Bind mount is on root partition which is block device /dev/ploopXXX. I've found the similar BUG about block device in Gentoo: https://bugs.gentoo.org/show_bug.cgi?id=541402 They fixed the problem by the patch (see in the BUG^^^). Also, there is BUG in mainstream: https://bugs.freedesktop.org/show_bug.cgi?id=89383 I can reproduce the BUG with 100% probability and confirm it. What's about backporting Gentoo's fix to Vivid? Regards, Kirill ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1457398 Title: systemd immediately unmounts manually mounted directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457398/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work
In 15.04 I've observed that Super+Space actually works when Space is pressed very rapidly after Super. The delay must not exceed roughly half a second. ** Changed in: unity Status: Expired = Confirmed ** Changed in: unity (Ubuntu) Status: Expired = 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/1201679 Title: ibus' Super+Space shortcut (usually) doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1201679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 982259] Re: Adjust window shoots off the screen when adjustments are made
Xubuntu 12.04 reached EOL (end-of-life) on April 26, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. ** Changed in: shotwell (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xfwm4 (Ubuntu) Status: Confirmed = Incomplete -- 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/982259 Title: Adjust window shoots off the screen when adjustments are made To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/982259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1393463] Re: image description / title should be visible via shotwell viewer
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shotwell (Ubuntu) Status: New = Confirmed -- 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/1393463 Title: image description / title should be visible via shotwell viewer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1393463/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Launchpad Bug Tracker wrote on 06.05.2015 20:01: ** Changed in: gvfs (Ubuntu Precise) Status: Fix Committed = Fix Released Fix tested and confirmed in Ubuntu 12.04 Precise. Before, I reproducibly ran into this bug when saving a data: URL from a Firefox-based webapp to a local file using the normal Firefox download dialog. I installed the Precise update from the normal Precise update package repositories. I save now, and I do not see the 100% CPU usage anymore. Bug fixed. Thanks a lot to Ross Lagerwall,Tomas Bzate, Alexander Larsson, Ondrej Holy (all GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095), Monsta, Marc Deslauriers (here) and everybody else involved! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457321] Re: lxc-stop does not shut down container
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
[Bug 1454173] Re: Assertion crash with ExecStart=- /path
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
[Bug 1435905] Re: gnome-terminal randomly outputs control characters
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: terminator (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1435905 Title: gnome-terminal randomly outputs control characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1435905] Re: gnome-terminal randomly outputs control characters
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1435905 Title: gnome-terminal randomly outputs control characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1435905] Re: gnome-terminal randomly outputs control characters
In Vivid where libvte-2.90-9 is default there error only appears in terminator, gnome-terminal is working. ** Also affects: terminator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1435905 Title: gnome-terminal randomly outputs control characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress
** Tags added: vivid -- 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/1284308 Title: Can't copy files from a bluetooth device: Another operation in progress To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1284308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1432171] Re: [udev] Shows starting version 219 boot message even with quiet
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
[Bug 1457054] Re: journal is broken in unprivileged LXC and nspawn containers
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
[Bug 1444402] Re: LXC with r/w sys and udev keeps trying to unmount bind mounts
This bug was fixed in the package systemd - 219-10ubuntu1 --- systemd (219-10ubuntu1) wily; urgency=medium * Merge with Debian experimental branch. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. - Keep our much simpler udev maintainer scripts (all platforms must support udev, no debconf). - initramfs init-top: Drop $ROOTDELAY, we do that in a more sensible way with wait-for-root. Will get applicable to Debian once Debian gets wait-for-root in initramfs-tools. - initramfs init-bottom: If LVM is installed, settle udev, otherwise we get missing LV symlinks. Workaround for LP #1185394. - Add debian/udev.lvm2.init: Dummy SysV init script to satisfy insserv dependencies to lvm2 which is handled with udev rules in Ubuntu. - Add debian/udev.lvm2.service to avoid running the dummy lvm2 init script. - Provide shutdown fallback for upstart. (LP: #1370329) - debian/extra/ifup@.service: Additionally run for auto class. We don't really support allow-hotplug in Ubuntu at the moment, so we need to deal with auto devices appearing after /etc/init.d/networking start already ran. (LP: #1374521) Also run ifup in the background during boot, to avoid blocking network.target. (LP: #1425376) - ifup@.service: Drop dependency on networking.service (i. e. /etc/init.d/networking), and merely ensure that /run/network exists. This avoids unnecessary dependencies/waiting during boot and dependency cycles if hooks wait for other interfaces to come up (like ifenslave with bonding interfaces). (LP: #1414544) - Add Get-RTC-is-in-local-time-setting-from-etc-default-rc.patch: In Ubuntu we currently keep the setting whether the RTC is in local or UTC time in /etc/default/rcS UTC=yes|no, instead of /etc/adjtime. (LP: #1377258) - Put session scopes into all cgroup controllers. This makes unprivileged user LXC containers work under systemd. (LP: #1346734) - systemctl: Don't forward telinit u to upstart. This works around upstart's Restart() always reexec'ing /sbin/init on Restart(), even if that changes to point to systemd during the upgrade. This avoids running systemd during a dist-upgrade. (LP: #1430479) - Drop hwdb-update dependency from udev-trigger.service, which got introduced in v219-stable. This causes udev and plymouth to start too late and isn't really needed in Ubuntu yet as we don't support stateless systems yet and handle hwdb.bin updates through dpkg triggers. This can be dropped again with initramfs-tools 0.117. - Lower Breaks: to plymouth version which has the udev inotify fix in Ubuntu. - Lower libappamor dep to the Ubuntu version where it moved to /lib. - Lower apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) - Make failure of boot-and-services NSpawn.test_boot non-fatal for now. This currently fails when being triggered by Jenkins, but is totally unreproducible when running this manually on the exact same machine. Upgrade fixes, keep until 16.04 LTS release: - systemd Conflicts/Replaces/Provides systemd-services. - Remove obsolete systemd-logind upstart job. - Clean up obsolete /etc/udev/rules.d/README. systemd (219-10) experimental; urgency=medium * Fix assertion crash with empty Exec*= paths. (LP: #1454173) * Drop Avoid-reload-and-re-start-requests-during-early-boot.patch and Avoid-reloading-services-when-shutting-down.patch: This was fixed more robustly in invoke-rc.d and service now, see #777113. * debian/tests/boot-smoke: Allow 10 seconds for systemd jobs to settle down. * Fix tentative state of devices which are not in /dev (mostly in containers), and avoid overzealous cleanup unmounting of mounts from them. (LP: #102) * debian/extra/udev-helpers/net.agent: Eliminate cat and most grep calls. * Drop Set-default-polling-interval-on-removable-devices-as.patch; it's long obsolete, CD ejection with the hardware button works properly without it. * Re-enable-journal-forwarding-to-syslog.patch: Update patch description, journal.conf.d/ exists now. * journal: Gracefully handle failure to bind to audit socket, which is known to fail in namespaces (containers) with current kernels. Also conditionalize systemd-journald-audit.socket on CAP_AUDIT_READ. (LP: #1457054) * Put back *.agent scripts and use net.agent in Ubuntu. This fixes escaping of unit names, reduces the delta, and will make it easier to get a common solution for integrating ifup.d/ scripts with networkd. * When booting with quiet, run the initramfs' udevd with notice log level. (LP: #1432171) * Add sigpwr-container-shutdown.service: Power off when receiving SIGPWR in a
[Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress
Using Xubuntu 15.04: hci0: Type: BR/EDR Bus: USB BD Address: E4:D5:3D:CB:D3:1D ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:273872 acl:1239 sco:0 events:586 errors:0 TX bytes:39316 acl:1037 sco:0 commands:41 errors:0 btusb 32768 0 bluetooth 491520 22 bnep,btusb,rfcomm Bus 001 Device 006: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) -- 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/1284308 Title: Can't copy files from a bluetooth device: Another operation in progress To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1284308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457660] [NEW] Sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main)
Public bug reported: Please sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Change appdata-tools b-dep to appstream-util Droppped upstream Changelog entries since current wily version 1:3.14.1-1ubuntu1: gucharmap (1:3.16.2-1) unstable; urgency=medium * New upstream release. * Drop appdata-tools build-dependency, no longer needed. -- Andreas Henriksson andr...@fatal.se Tue, 19 May 2015 15:02:43 +0200 ** Affects: gucharmap (Ubuntu) Importance: Wishlist Status: New ** Changed in: gucharmap (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1457660 Title: Sync gucharmap 1:3.16.2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1457660/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1376602] Re: Sync gucharmap 1:3.14.0-1 (main) from Debian unstable (main)
** Changed in: gucharmap (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1376602 Title: Sync gucharmap 1:3.14.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1376602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1448259] Re: Systemd does not send SIGTERM first on shutdown
** Changed in: systemd (Debian) Status: Fix Committed = Fix Released -- 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/1448259 Title: Systemd does not send SIGTERM first on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
Autopkgtest seems still mark release for trusty as cause of regression :( http://people.canonical.com/~ubuntu-archive/pending-sru.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457411] Re: Nautilus shows all of the files in / even for normal users
@Sebastian Here is the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=749677 ** Description changed: + Upstream Bug Report: https://bugzilla.gnome.org/show_bug.cgi?id=749677 + Right now if you go to `/` you would still see all of the files there. If your logged in as root, I can understand that, but as a normal users, its just an invitation for some users to go around and possibly break things. Currently users see this: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old By some minor tweaking one could turn that into this: home tmp That can be achieved by adding a file in the root folder `/.hidden` with the following content: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys usr var vmlinuz vmlinuz.old Every file you put in - that’s in the same directory as the file itself - will be hidden. Now, I also hide the home folder, made a link of my $username folder, and paste that in the root dir /. I also made a Applications folder with desktop files in them. We could link it to /usr/share/applications/. But the icons are not active for some reason? I copied the .desktop files to a folder in my home dir, and activated that, We could do something like that? I think that this is how all the `/` folders should look like for normal users in the future: Applications $username tmp screenshot - http://i.stack.imgur.com/8FyXD.png + http://i.stack.imgur.com/5UyYH.png This is just an idea. I wrote about this years ago: - http://www.eurobytes.nl/tutorials/how-to-hide-files-and-folders And to did others: - http://www.webupd8.org/2015/05/how-to-hide-files-and-folders-in-your.html - http://ubuntuguide.net/another-way-to-hide-files-folders-in-ubuntu - http://askubuntu.com/questions/243805/hide-certain-files-and-folders/ - http://askubuntu.com/questions/143315/how-to-hide-files-and-folders-in-nautilus/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 21 11:15:35 2015 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2015-05-18 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Bug watch added: GNOME Bug Tracker #749677 https://bugzilla.gnome.org/show_bug.cgi?id=749677 -- 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/1457411 Title: Nautilus shows all of the files in / even for normal users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1457411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457411] [NEW] Nautilus shows all of the files in / even for normal users
Public bug reported: Right now if you go to `/` you would still see all of the files there. If your logged in as root, I can understand that, but as a normal users, its just an invitation for some users to go around and possibly break things. Currently users see this: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old By some minor tweaking one could turn that into this: home tmp That can be achieved by adding a file in the root folder `/.hidden` with the following content: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys usr var vmlinuz vmlinuz.old Every file you put in - that’s in the same directory as the file itself - will be hidden. Now, I also hide the home folder, made a link of my $username folder, and paste that in the root dir /. I also made a Applications folder with desktop files in them. We could link it to /usr/share/applications/. But the icons are not active for some reason? I copied the .desktop files to a folder in my home dir, and activated that, We could do something like that? I think that this is how all the `/` folders should look like for normal users in the future: Applications $username tmp screenshot http://i.stack.imgur.com/8FyXD.png This is just an idea. I wrote about this years ago: - http://www.eurobytes.nl/tutorials/how-to-hide-files-and-folders And to did others: - http://www.webupd8.org/2015/05/how-to-hide-files-and-folders-in-your.html - http://ubuntuguide.net/another-way-to-hide-files-folders-in-ubuntu - http://askubuntu.com/questions/243805/hide-certain-files-and-folders/ - http://askubuntu.com/questions/143315/how-to-hide-files-and-folders-in-nautilus/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9 Uname: Linux 3.16.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 21 11:15:35 2015 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2015-05-18 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: hidden-nemo.png https://bugs.launchpad.net/bugs/1457411/+attachment/4401587/+files/hidden-nemo.png ** Description changed: Right now if you go to `/` you would still see all of the files there. If your logged in as root, I can understand that, but as a normal users, its just an invitation for some users to go around and possibly break things. Currently users see this: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys tmp usr var vmlinuz vmlinuz.old By some minor tweaking one could turn that into this: home tmp That can be achieved by adding a file in the root folder `/.hidden` with the following content: bin boot cdrom dev etc home initrd.img initrd.img.old lib lib32 lib64 lost+found media mnt opt proc root run sbin srv sys usr var vmlinuz vmlinuz.old Every file you put in - that’s in the same directory as the file itself - will be hidden. Now, I also hide the home folder, made a link of my $username folder, and paste that in the root dir /. I also made a Applications folder with desktop files in them. We could link it to /usr/share/applications/. But the icons are not active for some reason? I copied the .desktop files to - a folder in my home dir, and activated that, We cloud do something like + a folder in my home dir, and activated that, We could do something like that? I think that this is how all the `/` folders should look like for normal users in the future: Applications $username tmp screenshot http://i.stack.imgur.com/8FyXD.png This is just an idea. I wrote about this years ago: - - http://www.eurobytes.nl/tutorials/how-to-hide-files-and-folders + - http://www.eurobytes.nl/tutorials/how-to-hide-files-and-folders And to did others: - - http://www.webupd8.org/2015/05/how-to-hide-files-and-folders-in-your.html - - http://ubuntuguide.net/another-way-to-hide-files-folders-in-ubuntu - - http://askubuntu.com/questions/243805/hide-certain-files-and-folders/ - -
[Bug 1457411] Re: Nautilus shows all of the files in / even for normal users
Note that - users can see those directories but don't have write access to most so they can't actually damage things - nautilus open by default in the user directory, you need to go out of your way to see the system directories, it's not likely to confuse users then - that's not likely a change Ubuntu is going to work on, maybe upstream would be interested though -- 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/1457411 Title: Nautilus shows all of the files in / even for normal users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1457411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457438] [NEW] files not shown when known to exist
Public bug reported: When using dia I saved some .png images, as I had done before with the same names. Going to nautilus in order to select those images, I find that they are not listed, yet the dia save dialogue does show them. Reloading did not find them. See attached screenshot, which shows both the nautilus window after a reload and the dia dialogue. Later, opening a new nautilus window did find the files. So, why did they not show when I first looked? I have observed this problem before but did not keep records. This time I thought it worthwhile. Files are: timetrial_duties2.png regatta_duties2.png I'm using a fully up-to-date 14.04 on an AMD 64 motherboard and Dia- gnome 0.97.2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot from 2015-05-21 11:57:02.png https://bugs.launchpad.net/bugs/1457438/+attachment/4401648/+files/Screenshot%20from%202015-05-21%2011%3A57%3A02.png -- 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/1457438 Title: files not shown when known to exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1457438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457411] Re: Nautilus shows all of the files in / even for normal users
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided = Wishlist ** Changed in: nautilus (Ubuntu) Status: New = Won't Fix -- 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/1457411 Title: Nautilus shows all of the files in / even for normal users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1457411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456816] Re: Key binding with F-# keys don't work anymore
** Tags added: trusty ** Changed in: metacity (Ubuntu) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1456816 Title: Key binding with F-# keys don't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1456816/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1454698] Re: Unlocking the screen after sleep logs user off and back on
Thanks Walter for posting this as a bug. Would just like to link to my askubuntu.com's open question regarding this, as many Googlers would probably reach that page. http://askubuntu.com/questions/618527/14-04-unlocking-the-screen-after- sleep-logs-user-off-and-back-on It would be good to get updates there as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1454698 Title: Unlocking the screen after sleep logs user off and back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1454698/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456965] Re: Shouldn't use CSD under Unity
The dialogs work fine but look weird because they have no borders, it's also not easy to resize them due to that. They might be usable but that's still an user visible regression imho... -- 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/1456965 Title: Shouldn't use CSD under Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1456965/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
weird, it seems that it keeps getting change events ... does gvfs-ls trash:/// works? does it work if you uninstall python-nautilus? do you get the same issue in a guest session? ** Changed in: nautilus (Ubuntu) Status: Incomplete = New -- 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/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.37-1ubuntu10.1 --- accountsservice (0.6.37-1ubuntu10.1) vivid-proposed; urgency=medium * debian/patches/0010-set-language.patch: Use static variables inside user_get_fallback_value() to prevent execution of expensive code at each invocation (LP: #1443178). -- Gunnar Hjalmarsson gunna...@ubuntu.com Tue, 12 May 2015 17:44:00 +0200 ** Changed in: accountsservice (Ubuntu Vivid) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443178 Title: Accounts Service always relies on language fallback if never set by the user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Changed in: gvfs Status: Unknown = Fix Released ** Changed in: gvfs Importance: Unknown = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1450724] Re: Epiphany browser doesn't show most visited page
** Changed in: epiphany-browser (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1450724 Title: Epiphany browser doesn't show most visited page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1450724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449959] Re: Running ./unity --replace ... terminates the session and starts a new one on vivid
This bug was fixed in the package gnome-session - 3.14.0-2ubuntu5 --- gnome-session (3.14.0-2ubuntu5) vivid; urgency=medium * In 3.14.0-2ubuntu1, RequiredComponents of ubuntu (unity)'s session file incorrectly gained compiz. This caused compiz to be started by gnome-session and not to be managed by upstart in user sessions meaning, for example, that it won't be restarted correctly in the event of a crash. (LP: #1449959) -- Iain Lane iain.l...@canonical.com Wed, 29 Apr 2015 12:01:55 +0100 ** Changed in: gnome-session (Ubuntu Vivid) Status: Fix Committed = Fix Released -- 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/1449959 Title: Running ./unity --replace ... terminates the session and starts a new one on vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1449959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1449959] Update Released
The verification of the Stable Release Update for gnome-session has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1449959 Title: Running ./unity --replace ... terminates the session and starts a new one on vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1449959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1410190] Re: /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu-location-serviced': malloc(): memory corruption (fast): ADDR ***
** Changed in: location-service (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1410190 Title: /usr/bin/ubuntu-location-serviced:*** Error in `/usr/bin/ubuntu- location-serviced': malloc(): memory corruption (fast): ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1410190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1455868] Re: improve visibility of currently active tab
Please: 1. Add an screen-shot of this bug. 2. Set this bug status back to confirmed. Thank you. ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1455868 Title: improve visibility of currently active tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1455868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
This bug was fixed in the package accountsservice - 0.6.35-0ubuntu7.2 --- accountsservice (0.6.35-0ubuntu7.2) trusty-proposed; urgency=medium * debian/patches/0010-set-language.patch: Use static variables inside user_get_fallback_value() to prevent execution of expensive code at each invocation (LP: #1443178). -- Gunnar Hjalmarsson gunna...@ubuntu.com Tue, 12 May 2015 18:30:00 +0200 ** Changed in: accountsservice (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443178 Title: Accounts Service always relies on language fallback if never set by the user To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1443178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage
** Tags removed: hang verification-needed ** Tags added: verification-done-precise verification-needed-utopic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1452084] Re: Segmentation fault whilst opening Rubbish Bin/ trash://
Can confirm gvfs-ls trash:/// works fine producing the output of all the files in the trash:// location. I have another account on the system with plenty of files in that trash:// works perfectly fine for. Guest mode trash:// also works perfectly fine. The program still crashes with SIGSEGV (__GI__IO_default_xsputn (f=0x7f7ff600, data=optimised out, n=38) at genops.c:463) with python-nautilus uninstalled and pruged out (I did not restart the system, but I ensured that nautilus was completely killed before I re- attempted the test) I'm guessing there's probably something in my trash:// that's triggering this right? Any particular file types I should look for? Interestingly opening `nautilus ~/.local/share/Trash/files` causes a sefault too! -- 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/1452084 Title: Segmentation fault whilst opening Rubbish Bin/ trash:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452084/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1374841] Re: gstreamer crashes when opening WMA files
Is there any activity on solving this bug? As it stands, Ubuntu has a regression that makes it incapable of playing one of the three most common audio codecs. -- 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/1374841 Title: gstreamer crashes when opening WMA files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1374841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457400] [NEW] Ubuntu taking long to shutdown
You have been subscribed to a public bug: I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently onwards the ubuntu is taking long to shut down nearly 1:30 minutes. I checked the shutdown log messages and I get the follow message. A stop job is running for Session c2 of user * (25s/ 1min 30 s) It count downs till 1:30 minutes and then shutdown the machine. Why is it happening. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: plymouth shutdown time vivid -- Ubuntu taking long to shutdown https://bugs.launchpad.net/bugs/1457400 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457400] Re: Ubuntu taking long to shutdown
plymouth is just the messenger. Reassigning to systemd, which is at least where the message comes from. ** Package changed: plymouth (Ubuntu) = systemd (Ubuntu) -- 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/1457400 Title: Ubuntu taking long to shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1457564] [NEW] Boot hangs before graphic login, message starting version 219
Public bug reported: Please note: there are obviously several different causes for this error. Other reports on launchpad and elsewhere identified sddm, systemd, nvidia drivers and grub config. Since none of the solutions mentioned there helped in my case, I am deliberately leaving the information on the source package open. I have upgraded to Kubuntu Vivid 15.04 shortly after the final release and used that without issues until two days ago when I ran updates (apt log attached). Ran »sudo systemctl enable sddm.service -f«, then reboot: no change. Changed the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub to include »nomodeset«: no change. Other variations of this line did not help, either. I do not have nvidia or nouveau driver packages installed. I am aware that 219 is the current systemd version, so I tried the upstart option in grub. Hangs, too (though with different error message). »systemctl start sddm« asks for password, the returns »authentication complete« (in all-caps); nothing else happens. Re-installing linux-generic or kubuntu-desktop had no effect. What can I do to at least identify the cause of this issue? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: apt_history.log https://bugs.launchpad.net/bugs/1457564/+attachment/4401851/+files/apt_history.log -- 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/1457564 Title: Boot hangs before graphic login, message starting version 219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1435905] Re: gnome-terminal randomly outputs control characters
Vivid ships 3 parallel versions of vte: libvte9 0.28.x - used by Gtk2 apps such as terminator, xfce4-terminal libvte-2.90-9 0.36.x - a tiny bit older than the newest, used by e.g. roxterm-gtk3 libvte-2.91-0 0.38.x - the newest, used by e.g. gnome-terminal As stated above, the bug was fixed in 0.35.x, so apps using either of the two new versions of vte should be fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1435905 Title: gnome-terminal randomly outputs control characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1435905/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
