[Desktop-packages] [Bug 1717673] Re: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()

I've also had a crash in this function. I rebooted to finish installing 17.04, my Google calendars showed up in Evolution but not GNOME Shell or GNOME Calendar. When I tried to add an event, GNOME calendar crashed. The event was successfully added to Google Calendar. After restarting GNOME Cale

[Desktop-packages] [Bug 1717673] Re: gnome-calendar crashed with SIGSEGV in gtk_stack_set_visible_child_name()

(So after crashing, I wasn't able to reproduce the crash.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1717673 Title: gnome-calendar crashed with SIGSEGV in gtk_stack_set_

[Desktop-packages] [Bug 1553780] [NEW] nautilus rename_newly_added_folder: code should not be reached

Public bug reported: Select some files, right click- and select New Folder with Selection. Nautilus quits with the output `ERROR:nautilus- view.c:1834:rename_newly_added_folder: code should not be reached`. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2

[Desktop-packages] [Bug 1553780] Re: nautilus rename_newly_added_folder: code should not be reached

** Description changed: Select some files, right click- and select New Folder with Selection. Nautilus quits with the output `ERROR:nautilus- view.c:1834:rename_newly_added_folder: code should not be reached`. + + This happens when a lot of items are selected. (Might have something to + do

[Desktop-packages] [Bug 1553780] Re: nautilus assert failure: ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be reached

** Summary changed: - nautilus rename_newly_added_folder: code should not be reached + nautilus assert failure: ERROR:nautilus-view.c:1834:rename_newly_added_folder: code should not be reached -- You received this bug notification because you are a member of Desktop Packages, which is subscribe

[Desktop-packages] [Bug 1536217] Re: crash when toggling grilo plugin

I think I've hit the same bug. I reported it as bug #1555693 using apport, and that report does have a backtrace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1536217 Title: crash

[Desktop-packages] [Bug 1556924] [NEW] rhythmbox crashed with SIGSEGV in tracker_evt_update_orphan_item_cb() (when grilo media tracker is enabled)

Public bug reported: rhythmbox has been crashing without apport showing up, so I used gdb to get a stack trace and generate a core file. This might be a bug in grilo. gdb output: Core was generated by `/usr/bin/rhythmbox'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f

[Desktop-packages] [Bug 1647338] [NEW] gnome-settings-daemon uses 100% CPU after leaving the computer overnight

Public bug reported: Happened twice so far, I don't have any idea why is this happening and I hope to be able to reliably reproduce it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-settings-daemon 3.22.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4

[Desktop-packages] [Bug 1566977] [NEW] soffice.bin crashed with SIGSEGV in FcPatternGetCharSet()

Public bug reported: installing fonts and LibreOffice Impress crashed. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture:

[Desktop-packages] [Bug 1647338] Re: gnome-settings-daemon uses 100% CPU after leaving the computer overnight

I appreciate the reminder, but Ubuntu Bionic is still under development and has not been officially released. Does it make sense to recommend installing pre-release software right now? Perhaps it's better to suggest installing it when it's actually released. -- You received this bug notification

[Desktop-packages] [Bug 1652410] Re: Undescriptive duplicity/collection-status error when the backup directory contains two volumes with different file names and same volume number in the same backup

This can also happen if, for some unlikely reason (like a corrupted NTFS partition), the file system lists the same file twice. See Question #670964 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchp