[Bug 1371928] Re: Main window content fully transparent
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gimp (Ubuntu) Status: New = Confirmed -- 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/1371928 Title: Main window content fully transparent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1371928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1473156] [NEW] Deadfreeze above 10k of photos
Public bug reported: Ubuntu 14.04LTS / Linuxmind Rafaela LTS AMD64 Tested versions shotwell 0.18. LTS / 0.20.0 from yorba ppa Assumed function: Shotwell should be able to import photos and deal with larger amount of them by internal database. Expired function: Above 10k of photos the import from folder or update settled photo folder shotwell go into a deepfreeze. Means that the knight rider animation for input freeze up, harddisk stop searching and cpu load from shotwell turns to solid zero. The shotwell window can now be wiped with other program windows, started from within terminal there is no stop or crash response. Shotwell needs to be closed hard by taskmanager, nothing appears in the console. As described this happens to 0.18 and 0.20 and renders the software useless for photo collectors. 12163 photos, 53gb of data, a collection since 2001 ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New -- 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/1473156 Title: Deadfreeze above 10k of photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1473156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 192629] Re: Cannot move file to trash, do you want to delete immediately? on NTFS / VFAT partitions
The solution of mounting the ntfs partition with uid=1000 and gid=46 (46=plugdev) allows to use the trash only for the first user (uid=1000). However if there are more users it does not work for them. Even if they are included in the pludev group and all the permissions are given to the group and a .Trash-1001 folder is created, there is no access to the trash for user 1001. User 1001 can manually write into the .Trash-1001 folder (which belongs to 1000:46). However deletion of a file (from nautilus menu) is immediate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/192629 Title: Cannot move file to trash, do you want to delete immediately? on NTFS / VFAT partitions To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/192629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 994612] Re: gnome-screensaver-preferences missing
Hi, What can be done without gnome-screensaver-preferences ? -- 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/994612 Title: gnome-screensaver-preferences missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/994612/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1350123] Re: Startup with iPhone plugged in causes inability to logout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libimobiledevice (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1350123 Title: Startup with iPhone plugged in causes inability to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1350123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1021375] Re: Nautilus says the USB stick is read only when it is not
I have this issue on fedora 22. -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1021375/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 953875] Re: Encrypted swap no longer mounted at bootup
@Albert: trusty tasks added for ecryptfs and ubiquity. I'll upload ecryptfs for trusty together with the fix for bug 1453738. ** Also affects: ubiquity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ecryptfs-utils (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ecryptfs-utils (Ubuntu Trusty) Status: New = Triaged ** No longer affects: systemd (Ubuntu Trusty) ** Changed in: ubiquity (Ubuntu Trusty) Status: New = Triaged ** Changed in: ubiquity (Ubuntu Trusty) Importance: Undecided = High ** Changed in: ecryptfs-utils (Ubuntu Trusty) Importance: Undecided = High ** Changed in: ubiquity (Ubuntu Trusty) Milestone: None = ubuntu-14.04.3 -- 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/953875 Title: Encrypted swap no longer mounted at bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1473006] [NEW] [SRU] New upstream release 3.14.14
Public bug reported: [ Description ] New stable bugfix release gtk+3.0 (3.14.14-0ubuntu1) UNRELEASED; urgency=medium * New upstream release 3.14.14, fixing bugs: + gtk print dialog shows Getting printer information failed for cups remote printer + GtkMenuButton is not disabled even if corresponding GAction is + GTK+/Quartz = 3.14.8: Symbol not found: _gtk_drag_cancel + Adwaita : missing background for menu + icontheme: don't modify symbolic SVG dimensions when recoloring + Recent Chooser Widget doesn't expand + gtk3 does apparently ignore replayed events? + X11: First mouse wheel event ignored after right click or Alt+Tab or Win key press + Moving the mouse while a stepper is activated causes the scrollbar to jump to the beginning + file picker list box height stretches to match extra widgets area height + resource_path value cleared in gtk_image_set_from_resource + Deadlock in X11 when setting XSetErrorHandler while another thread is opening display with XOpenDisplay + Memleak when both opening shm and opening file in tmp fail -- Iain Lane iain.l...@canonical.com Thu, 09 Jul 2015 11:28:26 +0100 [ QA regression potential ] This is being uploaded under the GNOME MRE. You're allowed to believe upstream that the bugs are really fixed - just give the system a general once (or twice) over to see if things still work. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- 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/1473006 Title: [SRU] New upstream release 3.14.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1473006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998715] Re: Please transition gcr to multi-arch
It is not yet solved for Precise 12.04.5 which has LTS. Is it scheduled in any way for backporting to Precise ? -- 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/998715 Title: Please transition gcr to multi-arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/998715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998715] Re: Please transition gcr to multi-arch
Precise has LTS, and as told earlier in this bug discussion, the LTS should receive a fix. ** Changed in: gcr (Ubuntu Precise) Status: Invalid = Confirmed -- 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/998715 Title: Please transition gcr to multi-arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/998715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
** Bug watch added: Debian Bug tracker #774153 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153 ** Also affects: systemd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774153 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: Incomplete = New ** Changed in: systemd (Ubuntu) Status: New = Confirmed -- 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/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 998715] Re: Please transition gcr to multi-arch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-keyring (Ubuntu Precise) Status: New = Confirmed -- 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/998715 Title: Please transition gcr to multi-arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/998715/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 663146] Re: Rapidly creating/renaming new folders leads to confusing could not be renamed message
** Changed in: nautilus (Ubuntu) Status: Incomplete = Invalid -- 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/663146 Title: Rapidly creating/renaming new folders leads to confusing could not be renamed message To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/663146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1448159] Re: all started programs closes after computer unlock
** Changed in: gnome-screensaver (Ubuntu) Assignee: (unassigned) = LaRusCat (larionenkoruslan) ** Changed in: gnome-screensaver (Ubuntu) Status: New = Invalid -- 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/1448159 Title: all started programs closes after computer unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1448159/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1470060] Re: [wily] unprivileged containers don't work any more due to missing cgroup permissions
This bug was fixed in the package systemd - 222-1ubuntu1 --- systemd (222-1ubuntu1) wily; urgency=medium * Merge with Debian unstable. 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 scsi_wait_scan and udevadm settle, we do that in a more sensible way with wait-for-root. - 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 apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) 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.postinst: Migrate mountall specific fstab options to standard util-linux nofail option. * Add autopkgtest for user session cgroup permissions. This covers our Put session scopes into all cgroup controllers patch for unprivileged LXC containers. * core-Put-session-scopes-into-all-cgroup-controllers.patch: Update unit_get_cgroup_mask() to declare that user session scope units want all cgroup controllers, to avoid resetting them. This re-fixes user LXC containers. (LP: #1470060) systemd (222-1) unstable; urgency=medium [ Martin Pitt ] * New upstream release: - Fix reload killing BusName= units. (Closes: #746151) - sysv-generator: detect invalid names and escape them. (Closes: #677075) - Document removal of PIDFile on daemon shutdown. (Closes: #734006) - Drop Revert-rules-fix-tests-for-removable-state.patch, the auto-suspend rules now got dropped entirely. * Add Revert-VT-reuse-patches.patch: Revert a couple of logind VT reuse patches which alternately broke lightdm and gdm. * debian/libsystemd0.symbols: Add new symbols from this release. * Disable test-netlink during package build, fails on some buildds. * udev.postinst: Don't call addgroup with --quiet, so that if the input group already exists as a non-system group you get a sensible error message. Some broken tutorials forget the --system option. (Closes: #769948, LP: #1455956) * systemd.postinst: Drop the --quiet from the addgroup calls as well, same reason as above. (Closes: #762275) * udev: Drop doc dir symlinking. It has caused too much trouble and only marginally helps to avoid duplication. Such duplication should be dealt with at the distro, not package level. * debian/rules: Entirely ignore $LD_PRELOAD instead of just libfakeroot in the link check, to also avoid libeatmydata. (Closes: #790546) *
[Bug 1455956] Re: package udev 219-7ubuntu5 failed to install/upgrade: group input already exists as a non-systemd group
This bug was fixed in the package systemd - 222-1ubuntu1 --- systemd (222-1ubuntu1) wily; urgency=medium * Merge with Debian unstable. 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 scsi_wait_scan and udevadm settle, we do that in a more sensible way with wait-for-root. - 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 apparmor Breaks: to the Ubuntu version that dropped $remote_fs. - Change systemd-sysv's conflicts to upstart-sysv. (LP: #1422681) 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.postinst: Migrate mountall specific fstab options to standard util-linux nofail option. * Add autopkgtest for user session cgroup permissions. This covers our Put session scopes into all cgroup controllers patch for unprivileged LXC containers. * core-Put-session-scopes-into-all-cgroup-controllers.patch: Update unit_get_cgroup_mask() to declare that user session scope units want all cgroup controllers, to avoid resetting them. This re-fixes user LXC containers. (LP: #1470060) systemd (222-1) unstable; urgency=medium [ Martin Pitt ] * New upstream release: - Fix reload killing BusName= units. (Closes: #746151) - sysv-generator: detect invalid names and escape them. (Closes: #677075) - Document removal of PIDFile on daemon shutdown. (Closes: #734006) - Drop Revert-rules-fix-tests-for-removable-state.patch, the auto-suspend rules now got dropped entirely. * Add Revert-VT-reuse-patches.patch: Revert a couple of logind VT reuse patches which alternately broke lightdm and gdm. * debian/libsystemd0.symbols: Add new symbols from this release. * Disable test-netlink during package build, fails on some buildds. * udev.postinst: Don't call addgroup with --quiet, so that if the input group already exists as a non-system group you get a sensible error message. Some broken tutorials forget the --system option. (Closes: #769948, LP: #1455956) * systemd.postinst: Drop the --quiet from the addgroup calls as well, same reason as above. (Closes: #762275) * udev: Drop doc dir symlinking. It has caused too much trouble and only marginally helps to avoid duplication. Such duplication should be dealt with at the distro, not package level. * debian/rules: Entirely ignore $LD_PRELOAD instead of just libfakeroot in the link check, to also avoid libeatmydata. (Closes: #790546) *
[Bug 663146] Re: Rapidly creating/renaming new folders leads to confusing could not be renamed message
Still happens on Ubuntu 15.04 (Vivid Vervet). Occurs every time when done fairly quickly. Easiest to cause via [Ctrl][Shift]N test [Return] [Ctrl][Shift]N test2 [Return] Also occurs in Nemo 4.2.2. Cannot reproduce in Thunar 1.6.6. Nautilus screenshot attached. ** Attachment added: screenshot of Nautilus showing error message alert box https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/663146/+attachment/4426994/+files/nautilus%20two-folder%20quick%20creation%20bug.jpg -- 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/663146 Title: Rapidly creating/renaming new folders leads to confusing could not be renamed message To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/663146/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
** 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/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1047517] Re: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc()
My dupe: bug #1047517 :/ -- 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/1047517 Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() ... from unity::IconLoader::Impl::IconLoaderTask::LoaderJobFunc() To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1047517/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1473252] Re: nautilus crashed with SIGABRT in g_assertion_message() when opening an smb share
*** This bug is a duplicate of bug 1438216 *** https://bugs.launchpad.net/bugs/1438216 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1438216, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1473252/+attachment/4427262/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427264/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427267/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427268/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427269/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427270/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1473252/+attachment/4427271/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1438216 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1473252 Title: nautilus crashed with SIGABRT in g_assertion_message() when opening an smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1473252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 988251] Re: Nautilus cut, copy, paste, move and rename options are greyed out and stop working
killall ibus-daemon is a workaround -- 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/988251 Title: Nautilus cut, copy, paste, move and rename options are greyed out and stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/988251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs