[Bug 1765899] Re: unity-gnome-shell-migration.17.10.py crashed with signal 5
*** This bug is a duplicate of bug 1754623 *** https://bugs.launchpad.net/bugs/1754623 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 #1754623, 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/1765899/+attachment/5124693/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124695/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124699/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124700/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124701/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124702/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765899/+attachment/5124703/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1754623 ** 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 gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1765899 Title: unity-gnome-shell-migration.17.10.py crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1765899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 360970] Re: Multi-monitor - When using two displays with different vertical resolution, icons get lost on the shorter display
Still an issue in Bionic -- 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/360970 Title: Multi-monitor - When using two displays with different vertical resolution, icons get lost on the shorter display To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/360970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765894] Re: gnome-calendar crashed with SIGSEGV in gcal_manager_is_client_writable()
*** This bug is a duplicate of bug 1761466 *** https://bugs.launchpad.net/bugs/1761466 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 #1761466, 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/1765894/+attachment/5124658/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124660/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124663/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124664/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124665/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124666/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765894/+attachment/5124667/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1761466 ** 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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1765894 Title: gnome-calendar crashed with SIGSEGV in gcal_manager_is_client_writable() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1765894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765892] Re: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765892 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765892] [NEW] package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: I dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:amd64 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri Apr 20 20:34:12 2018 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-07-19 (275 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-04-18 (2 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765892 Title: package libglib2.0-0:amd64 2.48.2-0ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1765892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765893] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765893/+attachment/5124648/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124650/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124653/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124654/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124655/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124656/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765893/+attachment/5124657/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765893 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765893/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765891] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765891/+attachment/5124629/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124631/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124635/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124636/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124637/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124638/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765891/+attachment/5124639/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765891 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765891/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765889] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765889/+attachment/5124619/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124621/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124624/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124625/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124626/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124627/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765889/+attachment/5124628/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765889 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765889/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765886] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765886/+attachment/5124604/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124606/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124609/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124610/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124611/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124612/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765886/+attachment/5124613/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765886 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730871] Re: Close lid action missing in Ubuntu 17.10
You already know the reason why the upstream report was closed, don't you? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1730871 Title: Close lid action missing in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1730871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765854] Re: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name()
*** This bug is a duplicate of bug 1724188 *** https://bugs.launchpad.net/bugs/1724188 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 #1724188, 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/1765854/+attachment/5124437/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/5124439/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/5124442/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/5124443/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/512/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/5124445/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765854/+attachment/5124446/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724188 gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name → get_installed_updates_cb → g_task_return_now → complete_in_idle_cb → g_main_dispatch ** 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1765854 Title: gnome-software crashed with SIGSEGV in gtk_stack_set_visible_child_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1765854/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730871] Re: Close lid action missing in Ubuntu 17.10
Is it fixed, or why should it be closed? :( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1730871 Title: Close lid action missing in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1730871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765847] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765847/+attachment/5124399/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124401/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124404/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124405/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124406/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124407/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765847/+attachment/5124408/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765847 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765847/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765841] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765841/+attachment/5124368/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124370/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124374/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124375/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124376/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124377/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765841/+attachment/5124378/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765841 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759161] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message() from handle_other_xevent()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759161 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message() from handle_other_xevent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759161/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720685] Re: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()
This bug was fixed in the package nautilus - 1:3.26.3-0ubuntu4 --- nautilus (1:3.26.3-0ubuntu4) bionic; urgency=medium * debian/patches/server_list_segfault.patch, debian/patches/clear_pending_selection.patch: - don't segfault in the remote server UI, thanks Marco (lp: #1720685) -- Sebastien BacherFri, 20 Apr 2018 17:39:11 +0200 ** Changed in: nautilus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720685 Title: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765814] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1755786 *** https://bugs.launchpad.net/bugs/1755786 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 #1755786, 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/1765814/+attachment/5124203/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124205/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124208/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124209/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124210/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124211/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765814/+attachment/5124212/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755786 ** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765814 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765814/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Started report here https://gitlab.gnome.org/GNOME/gnome-shell/issues/221 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765809] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1755786 *** https://bugs.launchpad.net/bugs/1755786 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 #1755786, 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/1765809/+attachment/5124168/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124170/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124173/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124174/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124175/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124176/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765809/+attachment/5124177/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755786 ** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765809 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765809/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765795] Re: gsd-wacom crashed with SIGSEGV in g_type_check_value()
*** This bug is a duplicate of bug 1763316 *** https://bugs.launchpad.net/bugs/1763316 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 #1763316, 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/1765795/+attachment/5124121/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124123/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124126/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124127/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124128/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124129/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765795/+attachment/5124130/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763316 ** 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1765795 Title: gsd-wacom crashed with SIGSEGV in g_type_check_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1765795/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765799] [NEW] Applications menu does not get populated with recently installed apps using apt
Public bug reported: Applications menu doesn't get populated with recently installed app using apt. For example, after installing Firefox using apt, its shortcut does not appear immediately in the applications main menu. It only appeared there after I rebooted (maybe logging off also does the job). A “refresh menu” action has to be triggered somehow after installations. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 20 18:39:49 2018 Dependencies: InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180418) SourcePackage: gnome-menus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1765799 Title: Applications menu does not get populated with recently installed apps using apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?
Thanks for your suggestions. >The list of files you have tried didn't include >$HOME/.config/gtkrc-2.0 >My own experimentation shows settings in this file take precedence over >$HOME/.gtkrc-2.0 1) Just tried it, doesn't make any difference. 2) I actually tried running GnuCash under a debugger, and I observed it in the debugger opening and parsing both ~/.gtkrc-2.0 and ~/.gtkrc-2.0.gnucash, so I don't think the issue is that my config files are in the wrong place (and that shouldn't even matter, because the setting in dconf is correct and GnuCash should be obeying that setting even if there are no config files at all). >In addition you may check for the presence of >/etc/gtk-2.0/gtkrc >Which may also set this as well as the gtkrc file for the current gtk theme >Bionic is using. Doesn't exist. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765401 Title: gtk+ toolbar style setting ignored in bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765779] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765779/+attachment/5124044/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124046/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124049/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124050/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124051/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124052/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765779/+attachment/5124053/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765779 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765777] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1754924 *** https://bugs.launchpad.net/bugs/1754924 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 #1754924, 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/1765777/+attachment/5124034/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124036/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124039/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124040/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124041/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124042/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765777/+attachment/5124043/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1754924 gnome-control-center crashed with SIGSEGV in actualize_printers_list() ** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765777 Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765777/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764096] Re: Brasero can't burn DVD because of permissions issue
cat /proc/sys/kernel/shmmax: 18446744073692774399 ls -ld /dev/shm: drwxrwxrwt 2 root root 80 Apr 20 22:23 /dev/shm It seems that Brasero is working now even if remove the s bit for /usr/bin/wodim, not sure why, so I guess there is nothing to fix. Thanks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1764096 Title: Brasero can't burn DVD because of permissions issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1764096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765776] [NEW] nautilus crashes in other locations by middle-click
Public bug reported: Ubuntu 18.04 nautilus 3.26.3 Reproduce: 1-Open nautilus 2-Click Other Locations 3-Middle-Click Computer Result: Nautilus crashes ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1765776 Title: nautilus crashes in other locations by middle-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765775] [NEW] Window decoration becomes very large if the image has much more height than width
Public bug reported: When a image with much higher height than width is opened, the window decoration becomes very big, as it tries to keep the image proportional: https://i.imgur.com/SZu0lOk.png ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 Uname: Linux 4.16.3-041603-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Apr 20 13:08:37 2018 InstallationDate: Installed on 2017-06-13 (310 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: eog UpgradeStatus: Upgraded to bionic on 2017-10-20 (182 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1765775 Title: Window decoration becomes very large if the image has much more height than width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1765775/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765401] Re: gtk+ toolbar style setting ignored in bionic?
I don't have the solution for your issue unfortunately. But I can eliminate a few elements: Gnucash has switched to gsettings/dconf starting with 2.6.0. That means gconftool and gconftool2 changes are ignored by gnucash. As you discovered making the change in dconf is seen by gnucash 2.6.x. As I mentioned on the gnucash mailing list, gtk as of 3.10 has completely removed user control over the tool bar style. It is up to the developers to handle it (which hasn't happened for gnucash so far). That means unfortunately I don't know of any way to reliably control this setting in gnucash 3.x. >From the test result I infer gtk-query-settings only queries settings for gtk3, so any result you get from that will not help. The list of files you have tried didn't include $HOME/.config/gtkrc-2.0 My own experimentation shows settings in this file take precedence over $HOME/.gtkrc-2.0 In addition you may check for the presence of /etc/gtk-2.0/gtkrc Which may also set this as well as the gtkrc file for the current gtk theme Bionic is using. Perhaps with the switch back to gnome shell Ubuntu has chosen to make a very strict theme to enforce their style. But I have no idea about this as I'm not on Ubuntu. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1765401 Title: gtk+ toolbar style setting ignored in bionic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1765401/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765772] [NEW] xserver-xorg-video-intel crashes xorg session
Public bug reported: System: Ubuntu 18.04 PC: Dell inspiron n5110 laptop CPU: intel i7 2630QM GPU: nvidia gt 525m Reproduce: 1- install nvidia proprietary driver, restart 2- open nvidia-setting, select intel driver, reboot (or prime-select) Result: you cant login xorg session but you can login wayland (xorg or gnome-shell crashing and back to gdm) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765772 Title: xserver-xorg-video-intel crashes xorg session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765772/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765760] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765760/+attachment/5123983/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123985/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123988/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123989/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123990/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123991/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765760/+attachment/5123992/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765760 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720685] Re: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name()
** Changed in: nautilus (Ubuntu) Status: In Progress => Fix Committed -- 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/1720685 Title: nautilus crashed with SIGSEGV in gtk_stack_set_visible_child_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1720685/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()
Not sure if this issue is related but since I upgrade to the last daily update I am not able to click with my trackpad or connected mouse. When I suspend the laptop, I can use the keyboard to open a terminal. Gnome-shell is reporting this bug since this problem appears. I am using an XPS 13 - 9370 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1759621 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765758] [NEW] Gtk.Entry is not receiving editing-done signal (at least in python3, ubuntu 16.04)
Public bug reported: Description: Ubuntu 16.04.4 LTS Release: 16.04 According to: https://developer.gnome.org/gtk3/stable/GtkCellEditable.html#GtkCellEditable-editing-done Implementations of GtkCellEditable are responsible for emitting this signal when they are done editing, e.g. GtkEntry is emitting it when the user presses Enter. What I did: On the http://python-gtk-3-tutorial.readthedocs.io/en/latest/entry.html example I added a "connect signal": self.entry.connect("editing-done", self.on_editentry_done) also added the def def on_editentry_done(self, widget, *args): print('Hi!') Running the script and pressing either the "enter" or the "return" key, inside the entry box, expected "Hi!" to be printed on the terminal. (I have not checked if this is not working in C, I checked only in python 3) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: python3 xenial -- 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/1765758 Title: Gtk.Entry is not receiving editing-done signal (at least in python3, ubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1765758/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765732] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1759621 *** https://bugs.launchpad.net/bugs/1759621 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 #1759621, 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/1765732/+attachment/5123862/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123864/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123869/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123870/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123871/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123872/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765732/+attachment/5123873/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1759621 gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765732 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765735] Re: gsd-wacom crashed with SIGSEGV in g_type_check_value()
*** This bug is a duplicate of bug 1763316 *** https://bugs.launchpad.net/bugs/1763316 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 #1763316, 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/1765735/+attachment/5123882/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123884/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123887/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123888/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123889/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123890/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765735/+attachment/5123891/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763316 ** 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1765735 Title: gsd-wacom crashed with SIGSEGV in g_type_check_value() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1765735/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765729] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765729/+attachment/5123841/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123843/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123846/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123847/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123848/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123849/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765729/+attachment/5123850/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765729 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765725] Re: nautilus crashed with signal 5
*** This bug is a duplicate of bug 1760905 *** https://bugs.launchpad.net/bugs/1760905 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 #1760905, 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/1765725/+attachment/5123828/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123830/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123834/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123835/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123836/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123837/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765725/+attachment/5123838/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1760905 nautilus does not start at all ** 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/1765725 Title: nautilus crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765725/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765718] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765718/+attachment/5123803/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123805/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123808/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123809/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123810/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123811/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765718/+attachment/5123812/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765718 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start
Similar to bug 1736072 Note that in the fstab attached I commented out the swap entry to allow the system to boot. ** Also 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/1765724 Title: Xenial -> Bionic - System fails to boot after upgrade - systemd- cryptsetup@cryptswap1.service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1765724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765713] [NEW] Evolution on restarting for Google imap account chnage automatically receiving/ sending options to OAuth 2.0 and then it does not work
Public bug reported: Evolution 3.28.1-2 on Ubuntu 18.04. On restarting evolution for Google imap account, settings for receiving/ sending options change automatically to OAuth 2.0 And I get the error: "The reported error was “Failed to authenticate: Data source “xx...@gmail.com” does not support OAuth 2.0 authentication”." If I change the settings again in preferences manually, on restarting the account settings for receiving - change itself from Password to OAuth2(Google), and for sending - from login to OAuth2(Google). Do let me if it is not clear or more information is needed. Please suggest a solution. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.1-2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 18:45:02 2018 InstallationDate: Installed on 2018-04-16 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: account amd64 apport-bug bionic email evolution google imap -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1765713 Title: Evolution on restarting for Google imap account chnage automatically receiving/ sending options to OAuth 2.0 and then it does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1765713/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733597] Re: "gio open" handles mailto: links wrong, putting /// at the start of the email address
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1733597 Title: "gio open" handles mailto: links wrong, putting /// at the start of the email address To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1733597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765701] [NEW] [min. installation] Cannot change Passphrase.
Public bug reported: Since Ubuntu 18.04 LTS, a minimal installation is possible with the Ubuntu installer. If I go for that and choose to encrypt the disk, I cannot change the password via the utility gnome-disks graphically afterwards. Steps to Reproduce 1. install Ubuntu 18.04 LTS (daily 20180420 and Beta 2 tested) 2. encrypt the disk, while going through the installer 3. after installation: Disks (3.28.1) » (highlight) Partition 3 with LUKS (open padlock icon) » (button with two cog-wheels) Options » Change Passphrase » … Expected Results The password should be changed. Or if a software package is missing for this, it should install that. At least, a note should appear how to install/add that package. Actual Results “Error changing passphrase on device /dev/sda3: The function 'bd_crypto_luks_change_key_blob' called, but not implemented! (udisks-error-quark, 0)” Workaround sudo apt install libblockdev-crypto2 After that, a log-off was not sufficient; instead I had to restart the computer. Before I found that, I was able to change the password non-graphically thanks to <https://superuser.com/a/431832>. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1765701 Title: [min. installation] Cannot change Passphrase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1765701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
I have to go out, guess could file upstream bug tonight if no one does.. Seems best place is gitlab? https://gitlab.gnome.org/GNOME/gnome-shell/issues The commit allowing this seems to be, https://github.com/GNOME/gnome-shell/commit/cb4252e888c651c5a11fa0cb4c330e9351d61f1b (- confirmed here by reverting that commit to latest ubuntu gnome-shell source -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765687] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765687/+attachment/5123690/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123692/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123696/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123697/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123698/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123699/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765687/+attachment/5123700/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765687 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765687/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** This bug is no longer a duplicate of bug 1672297 gnome-shell uses lots of memory, and grows over time -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
And you should... SEE THIS LINK https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773 which is the most important memory leak and I posted it 3 years ago, could be possible that just ONE developer take this seriously? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Let's keep this open till we have the full set up upstream fixes in Ubuntu: https://gitlab.gnome.org/GNOME/gnome-shell/issues/64 ** Changed in: gjs (Ubuntu Bionic) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
** Package changed: glib (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1707451 Title: udisksd crashed with SIGSEGV in g_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1707451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748321] Re: Sort order is bizarre, and can not be changed
** Package changed: glib (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1748321 Title: Sort order is bizarre, and can not be changed To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1748321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707451] [NEW] udisksd crashed with SIGSEGV in g_mutex_lock()
You have been subscribed to a public bug: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65: lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: udisks Importance: Unknown Status: New ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: udisks2 (Ubuntu) Importance: High Assignee: Andrea Azzarone (azzar1) Status: Fix Released ** Tags: amd64 apport-crash artful bionic bugpattern-needed -- udisksd crashed with SIGSEGV in g_mutex_lock() https://bugs.launchpad.net/bugs/1707451 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
It didn't help here either, I've deleted it back when I filed this bug originally. FWIW, mine is also an upgrade, at least two releases back. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765667] [NEW] [Feature Request] enhance Apport with a usefull GUI to fill a complete bugreport.
Public bug reported: this little Window which you get if you start apport-bug is not realy helpfull. in my opinion, if you click on "Other problem. ther must be an automatic step that do https://wiki.ubuntu.com/Bugs/FindRightPackage#Any and allow to point on the Application you which to report. Enhance it with a Printscreen/screenrecording and allow to enhance it with some Text and arrows. In background you collect your data. At the end calculate the logs, anonymize some information (/home/max.muster -> /home/USER) and present a Window where People could Insert some additional Information. If sending the whole collection not work. Save it in Background and show a kind of notification. until it got sent. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport bughunting bugrepport gui screenrecording screenshot systemtray -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765667 Title: [Feature Request] enhance Apport with a usefull GUI to fill a complete bugreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765390] Re: printer settings: add switch for disable autodetect and add
thanks for the hint to https://wiki.ubuntu.com/Bugs/FindRightPackage It seems this Article is in the section Gnome not anymore actual. I had to use https://wiki.ubuntu.com/Bugs/FindRightPackage#Any to get it. ** Package changed: ubuntu => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765390 Title: printer settings: add switch for disable autodetect and add To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765659] Re: gnome-calendar crashed with SIGSEGV in g_str_equal()
*** This bug is a duplicate of bug 1755960 *** https://bugs.launchpad.net/bugs/1755960 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 #1755960, 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/1765659/+attachment/5123582/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123584/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123587/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123588/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123589/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123590/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765659/+attachment/5123591/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1755960 ** 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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1765659 Title: gnome-calendar crashed with SIGSEGV in g_str_equal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1765659/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765390] [NEW] printer settings: add switch for disable autodetect and add
You have been subscribed to a public bug: First and most important problem: I miss a switch in the printer settings to disable automatic detection and adding. I have problems on the VM in the company, because after system startup masses of printer messages appear and annoy me. I also have the problem that I am no longer able to find the printer I would need in the whole series of other unwanted printers. It would be easier if I only had to use the default printer, but unfortunately this is not the case. Another problem is adding a printer: It is easy to obtain the IP address of the printer. In the Add dialog there is a text in the search bar that says that I could insert an IP address. But that doesn't work. I need to go to "additional printer settings". Here I can add an IP address, but it must be an address starting with "ipp://"? Why do I have to do this? IP address is IP address, The program should find the protocol that it needs itself! Then I have to choose HPLIB and two AppSocket. For a printer that wasn't supported, I first had to enter the printer details and scroll through a shitty long list of printers and research that a Cannon iR is a Cannon Image Runner. In the end I had to download a ppd file from canon. (This was an adventure of its own, which has nothing to do with Linux). Now I have a printer that works and has been renamed with special text to get it to the top of the big list of unwanted printers in the system. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: autodetect bot-comment cups gui printer settings -- printer settings: add switch for disable autodetect and add https://bugs.launchpad.net/bugs/1765390 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765645] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765645/+attachment/5123496/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123498/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123502/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123503/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123504/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123505/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765645/+attachment/5123506/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765645 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765648] Re: gnome-control-center crashed with SIGSEGV in g_object_unref()
*** This bug is a duplicate of bug 1763255 *** https://bugs.launchpad.net/bugs/1763255 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 #1763255, 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/1765648/+attachment/5123517/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123519/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123522/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123523/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123524/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123525/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765648/+attachment/5123526/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763255 ** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765648 Title: gnome-control-center crashed with SIGSEGV in g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730871] Re: Close lid action missing in Ubuntu 17.10
** Changed in: gnome-control-center Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1730871 Title: Close lid action missing in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1730871/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724955] Re: unable to drag monitors in Display Arrangement
I have the same issue, Having two external monitor connected to a DELL Dock TB16 and Dock connected to my Dell XPS 13 laptop. I can also confirm that dreamwalker workaround worked for me. When I activate the laptop screen the UI started working draging the screen icons on the display arrangement window in gnome settings (device) page (gnome-control-center). Then after arrangement was set I diactivated the laptop screen before confirming all by pressing apply. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724955 Title: unable to drag monitors in Display Arrangement To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1724955/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765636] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765636/+attachment/5123472/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123474/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123477/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123478/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123479/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123480/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765636/+attachment/5123481/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765636 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765636/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765635] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765635/+attachment/5123461/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123463/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123467/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123468/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123469/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123470/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765635/+attachment/5123471/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765635 Title: gnome-shell crashed with signal 5 in g_log_default_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Yep, that's about ignorant gnome-shell team and really outdated toolkit. Ubuntu should use KDE. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1672297 Title: gnome-shell uses lots of memory, and grows over time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1672297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759939] Re: Nautilus Rubbish Bin doesn't show deleted items from network mount
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. -- 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/1759939 Title: Nautilus Rubbish Bin doesn't show deleted items from network mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1759939/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
I did, but logout/login didn't seem to fix the issue. Maybe gdm should've been restarted as well? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765620] Re: nautilus-desktop crashed with signal 5
*** This bug is a duplicate of bug 1760870 *** https://bugs.launchpad.net/bugs/1760870 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 #1760870, 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/1765620/+attachment/5123384/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123386/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123390/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123391/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123392/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123393/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765620/+attachment/5123394/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1760870 nautilus-desktop crashed with signal 5 ** 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/1765620 Title: nautilus-desktop crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765620/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754422] Re: [MIR] volume-key
Override component to main volume-key 0.3.9-4 in bionic amd64: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic arm64: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic armhf: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic i386: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic ppc64el: universe/utils/optional/100% -> main volume-key 0.3.9-4 in bionic s390x: universe/utils/optional/100% -> main 6 publications overridden. ** Changed in: volume-key (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to volume-key in Ubuntu. https://bugs.launchpad.net/bugs/1754422 Title: [MIR] volume-key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/volume-key/+bug/1754422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765613] Re: gnome-shell crashed with signal 5
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1765613/+attachment/5123338/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123340/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123344/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123345/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123346/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123347/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765613/+attachment/5123348/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765613 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
the issue sounds similar to bug #1620806, do you have a ~/.xinputrc? does deleting it fixes the issue? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
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. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1760818/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout
** Changed in: ubiquity (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1758647 Title: ubiquity doesn't preselect the right default keyboard layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1758647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1750780] Re: Race with local file systems can make open-vm-tools fail to start
** Also affects: open-vm-tools (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Artful) ** Changed in: open-vm-tools (Ubuntu Xenial) Status: Invalid => Triaged ** Changed in: open-vm-tools (Ubuntu Artful) Status: New => Triaged ** Changed in: open-vm-tools (Ubuntu) Status: Fix Released => Invalid -- 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/1750780 Title: Race with local file systems can make open-vm-tools fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs