[Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout
** Changed in: ubiquity (Ubuntu Bionic) Assignee: Jean-Baptiste Lallement (jibel) => Łukasz Zemczak (sil2100) ** Changed in: ubiquity (Ubuntu Bionic) Status: Confirmed => In Progress -- 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 1765290] Re: /usr/bin/gnome-shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:handle_hotplug_event
This looks similar to bug 1765269 ** Summary changed: - /usr/bin/gnome-shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:handle_hotplug_event + gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from handle_hotplug_event() ** 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/1765290 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from handle_hotplug_event() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current()
Also tracking in https://errors.ubuntu.com/problem/1e18be3177eec7b64bb8d8b6f51d7dc727e21bc1 ** Description changed: + https://errors.ubuntu.com/problem/1e18be3177eec7b64bb8d8b6f51d7dc727e21bc1 + + --- + At upstart the problem occurred ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 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: GNOME-Greeter:GNOME Date: Wed Apr 18 19:50:57 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - + InstallationDate: Installed on 2018-04-08 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: - Segfault happened at: 0x7f01cd93a89b:mov0x30(%rax),%edi - PC (0x7f01cd93a89b) ok - source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! - destination "%edi" ok + Segfault happened at: 0x7f01cd93a89b:mov0x30(%rax),%edi + PC (0x7f01cd93a89b) ok + source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! + destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - meta_gpu_read_current () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - meta_monitor_manager_read_current_state () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - meta_monitor_manager_setup () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + meta_gpu_read_current () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + meta_monitor_manager_read_current_state () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + meta_monitor_manager_setup () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() + gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() -- 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/1765269 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current()
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/1765269 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765289] [NEW] /usr/bin/gnome-shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:meta_monitor_manager_setup
*** This bug is a duplicate of bug 1765269 *** https://bugs.launchpad.net/bugs/1765269 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.0-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/1e18be3177eec7b64bb8d8b6f51d7dc727e21bc1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765289 Title: /usr/bin/gnome- shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:meta_monitor_manager_setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_m
See also bug 1765290 -- 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/1765269 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765289] Re: /usr/bin/gnome-shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:meta_monitor_manager_setup
*** This bug is a duplicate of bug 1765269 *** https://bugs.launchpad.net/bugs/1765269 ** This bug has been marked a duplicate of bug 1765269 gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() -- 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/1765289 Title: /usr/bin/gnome- shell:11:meta_kms_resources_init:meta_gpu_kms_read_current:meta_gpu_read_current:meta_monitor_manager_read_current_state:meta_monitor_manager_setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765289/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current()
** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private to Public -- 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/1765269 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765269] Re: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current()
Status changed to 'Confirmed' because the bug affects multiple users. ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765269 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from meta_monitor_manager_setup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765269/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765290] [NEW] gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from hand
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.0-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/5ca9512852dd9082cf25e1660f73b33cba732fa0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic -- 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/1765290 Title: gnome-shell crashed with SIGSEGV in meta_kms_resources_init() from meta_gpu_kms_read_current() from meta_gpu_read_current() from meta_monitor_manager_read_current_state() from handle_hotplug_event() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765288] 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/1765288/+attachment/5122088/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122090/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122094/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122095/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122096/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122097/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765288/+attachment/5122098/+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/1765288 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/1765288/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 11334] Re: MASTER Copy-Paste doesn't work if the source is closed before the paste
I'm predicting riots in response to the most recent status update. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (36165). https://bugs.launchpad.net/bugs/11334 Title: MASTER Copy-Paste doesn't work if the source is closed before the paste To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/11334/+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
I wonder if we should keep using this bug as the additional leak fixes land in future? Leaks are likely to come and go indefinitely over time as the code changes, so we should try to decide the acceptance criteria for closing this bug. And when it would be more appropriate to open new similar bugs. -- 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 1765268] 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/1765268/+attachment/5122017/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122019/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122022/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122023/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122024/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122025/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765268/+attachment/5122026/+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/1765268 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/1765268/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1744970] Re: Lowering some windows causes other, unrelated windows to also be lowered.
Fix released in mutter 3.28.0 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** No longer affects: gnome-shell (Ubuntu) ** Tags added: bionic -- 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/1744970 Title: Lowering some windows causes other, unrelated windows to also be lowered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1744970/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 29894] Re: can't take screenshot when menu on panel is opened
I have this issue in Ubuntu 18.04 (X) when trying to take a screenshot of an application with a menu open. Tried to add custom shortcuts like gnome-screenshot -w --delay=3 but it still wouldn't work -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/29894 Title: can't take screenshot when menu on panel is opened To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/29894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765261] Re: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt
Possibly related: bug 1590719, bug 1720010 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765261] [NEW] Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt
Public bug reported: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt.. This seems to be a new problem, just started today. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 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 Date: Thu Apr 19 11:16:17 2018 InstallationDate: Installed on 2017-12-12 (127 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765261] Re: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt
Seems related to a cold boot. Once it starts working, it keeps working. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1765261 Title: Ubuntu 18.04 login screen rejects a valid password on first attempt. Always works on the second attempt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765261/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 11334] Re: MASTER Copy-Paste doesn't work if the source is closed before the paste
** Changed in: gtk Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (36165). https://bugs.launchpad.net/bugs/11334 Title: MASTER Copy-Paste doesn't work if the source is closed before the paste To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/11334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1744001] Re: Expanded panel menus don't fade out cleanly on close
** Branch linked: lp:~3v1n0/gnome-shell/bionic-patches-add-gpu-cached- texture -- 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/1744001 Title: Expanded panel menus don't fade out cleanly on close To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1744001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765198] Re: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony.
*** This bug is a duplicate of bug 1763878 *** https://bugs.launchpad.net/bugs/1763878 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1763878, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1763878 [regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called from cairo_debug_reset_static_data() -- 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/1765198 Title: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1765198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)
Awesome. Thanks Marco. -- 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/1747566 Title: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1747566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
I think there are going to be multiple ways this Xwayland crash could be triggered. Also we don't seem to have fully deduplicated similar crashes yet: https://bugs.launchpad.net/ubuntu/+source/xorg-server So I think it's most helpful to keep this bug open and findable for now. ** Changed in: xorg-server (Ubuntu) Status: Invalid => 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/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765244] StacktraceTop.txt
** Attachment added: "StacktraceTop.txt" https://bugs.launchpad.net/bugs/1765244/+attachment/5121942/+files/StacktraceTop.txt -- 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/1765244 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765244] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765244/+attachment/5121943/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765244/+attachment/5121897/+files/CoreDump.gz ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** 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/1765244 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765110] Re: login screen frozen after kernel update
Please try to find the closest two kernel versions where one works and the other doesn't. ** Tags added: artful ** Package changed: gdm3 (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: login screen frozen after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765244] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1765244/+attachment/5121941/+files/StacktraceSource.txt -- 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/1765244 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765244] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765244/+attachment/5121940/+files/Stacktrace.txt -- 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/1765244 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()
** No longer affects: gnome-shell (Ubuntu) -- 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/1703668 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1703668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] Re: gnome-shell crashed with SIGABRT in __GI_raise()
*** This bug is a duplicate of bug 1422253 ***
https://bugs.launchpad.net/bugs/1422253
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1422253, so it 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. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 1422253
gnome-shell crashed with SIGABRT in g_assertion_message("assertion failed:
(window->display->focus_window != window)") from g_assertion_message_expr()
from meta_window_unmanage() from handle_other_xevent()
--
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/1765139
Title:
gnome-shell crashed with SIGABRT in __GI_raise()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765141] Re: [regression] Full screen white flash from time to time with Wayland
** Summary changed: - Full screen white flash from time to time with Wayland + [regression] Full screen white flash from time to time with Wayland ** Tags added: visual-quality ** Also affects: mutter (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/1765141 Title: [regression] Full screen white flash from time to time with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
This should be actually fixed by nautilus 1:3.26.3-0ubuntu1 ** Changed in: nautilus (Ubuntu) Status: In Progress => 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/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765244] [NEW] gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1
Public bug reported: Having trouble with the sound on my azpen x1150 2in1 which is an atom chipset which linux hasn't fully caught up with yet. Regardless, while trying a work around that others have had success with on similar chips the work around succesfully allowed the intel audio devices to show up in the sound control panel but while attempting to test the speakers to prove it worked the control panel app crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CasperVersion: 1.392 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 01:33:50 2018 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: gnome-control-center sound ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gvc_mixer_control_change_profile_on_selected_device () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1765244 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() while testing speakers on atom 2in1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen
3.28.1 is now in Ubuntu 18.04 so this bug *should* be fixed. -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724977] Re: two mouse cursors visible at the same time on rotated screen
mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** No longer affects: gnome-shell (Ubuntu) ** Package changed: wayland (Fedora) => mutter (Fedora) ** Project changed: gnome-shell => mutter -- 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/1724977 Title: two mouse cursors visible at the same time on rotated screen To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724977/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1752197] Re: Videos won't resume after being paused
** Changed in: webkit-open-source Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1752197 Title: Videos won't resume after being paused To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1752197/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default
The semantics of systemd-networkd-wait-online.service are that the service is ready when "the Internet" is reachable. In the past, the implementation of network-online.target has been less correct on Ubuntu, *because* ipv6 RA was handled asynchronously, and this target did not block waiting to find out if ipv6 had been configured. That was mostly ok up until now in an IPv4-dominated world, but over the course of 18.04 LTS's lifetime, I expect we will increasingly see IPv6-enabled deployments where the default IPv6 route is as important as, or more important than, the default IPv4 route, and to not block waiting for SLAAC results in an RFC-compliant manner would make the boot racy. We cannot regard IPv6 as an afterthought. I agree with systemd upstream's decision to block on IPv6 results by default. However, in most environments where cloud-init is running, we shouldn't need a configurable timeout for SLAAC at all because we know by design whether or not we can expect ipv6 and if we know that the substrate does not provide ipv6, the netplan yaml for this provider should specify 'accept-ra: false'. Then the timeout is the correct 0, and there is no adverse effect on boot speed. For public clouds that don't provide netplan yaml today and instead have default netplan yaml generated by cloud-init, this should be included as part of the default policy in cloud-init. For any public clouds that are ipv6 opt-in, it is probably still appropriate to emit accept-ra: false by default in order to ensure a good default experience; and deal with opt-in ipv6 support via user- provided (or, preferably: cloud-provided) override cloud config. For the lxd case, the default should be 'accept-ra: false', with logic added later in lxd to set 'accept-ra: true' when lxd knows that the bridge supports ipv6. I think we will want to extend networkd and netplan to allow expression of additional network policies beyond the options of 'accept-ra: true' and 'accept-ra: false'. It should be possible to express that the kernel should try SLAAC, but that networkd should not block on SLAAC results for purposes of systemd-networkd-wait-online, while still blocking on *ipv4* connectivity for this interface. However, this will take some time to design properly, and I do not think that this should be the default for networkd+netplan once implemented: the forward- looking default is still that we should wait for a firm answer from SLAAC before considering the network up, and that if the user wants a different policy from this, it should be an override of the default netplan configuration. So I believe the quick path for addressing this issue in 18.04 is for cloud-init to declare 'accept-ra: false' everywhere that this is reasonable, with a possible relaxation to a future opportunistic accept- ra policy once this is available in netplan+networkd. ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Also affects: netplan.io (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/1765173 Title: networkd waits 10 seconds for ipv6 network discovery by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1765173/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1389336] Re: Use geoclue-2.0
libunity-webapps was removed from Ubuntu 17.10 so I'm closing that task. The remaining bug here, ubuntu-geoip (a Recommends of indicator- datetime) is a problem. geoclue was removed from Debian 2 years ago. geoclue build-depends on libnm-glib-dev and libnm-util-dev which Debian is removing now. Maybe it's time to remove ubuntu-geoip. ** Changed in: libunity-webapps (Ubuntu) Status: Confirmed => Won't Fix -- 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/1389336 Title: Use geoclue-2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725133] Re: Window buttons lack padding when scale is set to 200%
This bug was fixed in the package mutter - 3.28.1-1 --- mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1725133 Title: Window buttons lack padding when scale is set to 200% To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725133/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
This bug was fixed in the package mutter - 3.28.1-1 --- mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764554] Re: Mutter SSD decorations do not properly scale -gtk-scaled images
This bug was fixed in the package mutter - 3.28.1-1 --- mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1764554 Title: Mutter SSD decorations do not properly scale -gtk-scaled images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703668] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor()
This bug was fixed in the package mutter - 3.28.1-1 --- mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1703668 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_main_output() from meta_monitor_get_vendor() from meta_input_settings_find_logical_monitor() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1703668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764558] Re: Window buttons icon effect isn't applied to mutter decorations
This bug was fixed in the package mutter - 3.28.1-1 --- mutter (3.28.1-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release - Fix window button spacing when display is scaled (LP: #1725133) * Bump Standards-Version to 4.1.4 [ Marco Trevisan (Treviño) ] * Add patches proposed upstream: * theme-frames-Use-surface-device-scale-instead-of-cairo_sc.patch: - theme, frames: Use surface device scale instead of cairo_scale (LP: #1764554) * theme-use-gtk_render_icon_suface-to-paint-button-icon.patch: - theme: use gtk_render_icon_suface to paint button icon (LP: #1764558) * theme-load-icons-as-Gtk-does-with-fallback-and-RTL-suppor.patch: - theme: load icons as Gtk does with fallback and RTL support * clutter-Smooth-out-master-clock-to-smooth-visuals.patch: - clutter: Smooth out master clock to smooth visuals * core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch: - core: Return -1 if meta_window_get_monitor is called on an unmanaged window (LP: #1724439) * backends-Move-MetaOutput-crtc-field-into-private-struct.patch: - backends: Move MetaOutput::crtc field into private struct (LP: #1703668) * backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch: - backends: Add logical monitor -> monitor -> output -> crtc ref chain (LP: #1703668) -- Jeremy Bicha Mon, 16 Apr 2018 22:35:14 -0400 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- 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/1764558 Title: Window buttons icon effect isn't applied to mutter decorations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1764558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765202] 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/1765202/+attachment/5121761/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121763/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121766/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121767/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121768/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121769/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765202/+attachment/5121770/+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/1765202 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765198] Re: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony.
** Tags removed: need-amd64-retrace -- 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/1765198 Title: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1765198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747717] Re: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw
I did update ubuntu 16.04 to 18.04 2 days ago, and during the upgrade I got that problem. Also it repeats every time after boot, so gnome-menus 3.13.3-11ubuntu1 fails to install for me. Just wondering why I can't see any symptoms though, as everything seems to work perfectly as far I can tell other than that crash report every time after start. I had an unaltered Dell factory install of Ubuntu 16.04(.3-4?) on a new XPS 13 before the upgrade, so it had Unity instead of Gnome 3. -- 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/1747717 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> ufw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1747717/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765198] [NEW] gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony.
Public bug reported: The error occurred while entering the administrator password, when the "bleachbit" program was started. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gjs 1.52.1-1 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 AssertionMessage: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony. Date: Wed Apr 18 22:38:18 2018 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2016-05-08 (710 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160522) ProcCmdline: /usr/bin/gjs /usr/share/org.gnome.Weather/org.gnome.Weather.Application --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: __assert_fail_base (fmt=0x7f852654b1c4 , assertion=assertion@entry=0x7f852134dd05 "hash_table->live_entries == 0", file=file@entry=0x7f852134dce8 "../../../../src/cairo-hash.c", line=line@entry=217, function=function@entry=0x7f852134de90 "_cairo_hash_table_destroy") at assert.c:92 __GI___assert_fail (assertion=0x7f852134dd05 "hash_table->live_entries == 0", file=0x7f852134dce8 "../../../../src/cairo-hash.c", line=217, function=0x7f852134de90 "_cairo_hash_table_destroy") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony. UpgradeStatus: Upgraded to bionic on 2018-04-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public -- 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/1765198 Title: gjs-console assert failure: gjs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Warunek zapewnienia `hash_table->live_entries == 0' nie został spełniony. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1765198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765194] Re: Gnome-shell search always open new instance of gnome-terminal
Removing line NoDisplay=true from /usr/share/applications/org.gnome.Terminal.desktop fix the problem. gnome-terminal also create an additional desktop file named gnome- terminal.desktop which is unnecessary. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1765194 Title: Gnome-shell search always open new instance of gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1765194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)
Thanks for fixing/maintaining this package!!! Really appreciate it. I can confirm this bug is squashed. -- 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/1747566 Title: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1747566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765194] [NEW] Gnome-shell search always open new instance of gnome-terminal
Public bug reported: If I search 'terminal' in shell and hit enter, it always open new instance of gnome-terminal. How to regenerate: 1. Open a terminal (gnome-terminal) 2. Press super key or click Activities to start overview mode 3. Search for terminal and hit enter 4. It will open another instance of gnome-terminal Expected behavior: 1. Bring already opened instance to front. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 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-communitheme:ubuntu:GNOME Date: Thu Apr 19 02:14:30 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-26 (174 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-03-29 (20 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: If I search 'terminal' in shell and hit enter, it always open new instance of gnome-terminal. How to regenerate: 1. Open a terminal (gnome-terminal) 2. Press super key or click Activities to start overview mode 3. Search for terminal and hit enter 4. It will open another instance of gnome-terminal Expected behavior: 1. Bring already opened instance to front. - - It also doesn't work for Gedit ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.1-1ubuntu1 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-communitheme:ubuntu:GNOME Date: Thu Apr 19 02:14:30 2018 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-26 (174 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to bionic on 2018-03-29 (20 days ago) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1765194 Title: Gnome-shell search always open new instance of gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1765194/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1746728] Re: Uninstalling VLC using Ubuntu Software does not uninstall the actual application
** Changed in: vlc (Debian) Status: Won't Fix => Fix Released -- 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/1746728 Title: Uninstalling VLC using Ubuntu Software does not uninstall the actual application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1746728/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765181] 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/1765181/+attachment/5121644/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121646/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121649/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121650/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121651/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121652/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765181/+attachment/5121653/+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/1765181 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/1765181/+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
I talked with cyphermox and it seems the delta was removed intentionally - with the intention of just starting to use xkb-keymap in ubiquity - but this cycle that didn't happen. Since it does require a small amount of design work and we're really close to release, it's best to just re- introduce the changes. I'll be uploading as soon as I have a moment. -- 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 1588150] Re: Remove webkitgtk from archive
*** This bug is a duplicate of bug 1710318 *** https://bugs.launchpad.net/bugs/1710318 I'm marking this a duplicate of the newer bug 1710318 because the other bug is more direct for the final steps needed here. ** This bug has been marked a duplicate of bug 1710318 Please remove webkitgtk from Ubuntu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1588150 Title: Remove webkitgtk from archive To manage notifications about this bug go to: https://bugs.launchpad.net/bijiben/+bug/1588150/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765173] [NEW] networkd waits 10 seconds for ipv6 network discovery by default
Public bug reported: 1. $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 2. $ apt-cache policy systemd systemd: Installed: 237-3ubuntu8 Candidate: 237-3ubuntu8 Version table: *** 237-3ubuntu8 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. systemd-networkd-wait-online doesn't block for 10 seconds waiting on an IPV6 Router Advertisement 4. systemd-networkd sends at least two RA solicitation packets waiting for a response before setting the link to configured. This blocks the boot for every Ubuntu system where it does not have a IPV6 router responding to solicitations. THis includes bionic containers, cloud instances, vms and physical machines. -- We can see that we're spending 13 seconds waiting for networkd to say the network is up. % systemd-analyze blame 13.326s systemd-networkd-wait-online.service 999ms cloud-init-local.service 954ms cloud-init.service 887ms cloud-config.service 749ms dev-vda1.device 666ms cloud-final.service 248ms keyboard-setup.service 175ms systemd-udev-trigger.service 171ms lxd-containers.service 165ms snapd.service 154ms apparmor.service 147ms ssh.service 144ms systemd-timesyncd.service 133ms grub-common.service 130ms systemd-journald.service 130ms accounts-daemon.service 99ms systemd-modules-load.service 98ms systemd-resolved.service 94ms apport.service 92ms rsyslog.service 88ms systemd-logind.service 80ms lvm2-monitor.service 75ms iscsid.service 64ms ebtables.service 62ms user@1000.service 54ms dev-mqueue.mount 53ms ufw.service 52ms systemd-remount-fs.service 52ms kmod-static-nodes.service 34ms systemd-journal-flush.service 34ms polkit.service 32ms systemd-tmpfiles-setup-dev.service 27ms systemd-udevd.service 26ms systemd-networkd.service 26ms systemd-sysctl.service 25ms systemd-tmpfiles-setup.service 21ms dev-hugepages.mount 17ms sys-kernel-debug.mount 16ms console-setup.service 15ms plymouth-read-write.service 15ms snapd.socket 15ms plymouth-quit.service 14ms systemd-update-utmp.service 10ms systemd-user-sessions.service 9ms boot-efi.mount 8ms sys-fs-fuse-connections.mount 8ms systemd-update-utmp-runlevel.service 8ms lxd.socket 7ms blk-availability.service 5ms systemd-random-seed.service 3ms setvtrgb.service 3ms plymouth-quit-wait.service 3ms sys-kernel-config.mount Here we can see that we start networking at 18:30:51.69, and then IPv6 NDISC runs for 10 seconds and then the link is configured at 18:31:05. *AND* we see NDISC stays around and continues to see if it gets a RA packet. $ journalctl -o short-precise -u systemd-networkd.service | egrep "(Starting Network|Discovering IPv6 routers|NDISC|Configured)" Apr 18 18:30:51.691532 rharper-b1 systemd[1]: Starting Network Service... Apr 18 18:30:53.031041 rharper-b1 systemd-networkd[603]: ens3: Discovering IPv6 routers Apr 18 18:30:53.031306 rharper-b1 systemd-networkd[603]: NDISC: Started IPv6 Router Solicitation client Apr 18 18:30:53.031612 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 4s Apr 18 18:30:57.092282 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 8s Apr 18 18:31:05.040895 rharper-b1 systemd-networkd[603]: NDISC: No RA received before link confirmation timeout Apr 18 18:31:05.040932 rharper-b1 systemd-networkd[603]: NDISC: Invoking callback for 't'. Apr 18 18:31:05.041099 rharper-b1 systemd-networkd[603]: ens3: Configured Apr 18 18:31:05.484261 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 16s Apr 18 18:31:21.550612 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 33s Apr 18 18:31:54.706283 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 1min 5s Apr 18 18:33:00.232685 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 2min 15s Apr 18 18:35:15.436376 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 4min 32s Apr 18 18:39:48.111413 rharper-b1 systemd-networkd[603]: NDISC: Sent Router Solicitation, next solicitation in 9min 16s networkd runs ndisc if your host is configured with ipv6 forwarding disabled and accept_ra enabled. % sysctl net.ipv6.conf.all.forwarding net.ipv6.conf.all.f
[Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
This bug was fixed in the package gjs - 1.52.1-1ubuntu1 --- gjs (1.52.1-1ubuntu1) bionic; urgency=medium * Add fix-crashes-lp1763878-revert-575f1e2e077.patch to fix shutdown crashes (LP: #1763878) * Add some patches to solve large memory leaks (LP: #1672297) - fix-leaks-lp1672297-1-context-Add-API-to-force-GC-schedule.patch - fix-leaks-lp1672297-2-object-Queue-a-forced-GC-when-toggling-down.patch - Note: More such patches are under review so this list may grow in future. -- Daniel van Vugt Mon, 16 Apr 2018 14:30:31 +0800 ** Changed in: gjs (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 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 1763878] Re: [regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called
This bug was fixed in the package gjs - 1.52.1-1ubuntu1 --- gjs (1.52.1-1ubuntu1) bionic; urgency=medium * Add fix-crashes-lp1763878-revert-575f1e2e077.patch to fix shutdown crashes (LP: #1763878) * Add some patches to solve large memory leaks (LP: #1672297) - fix-leaks-lp1672297-1-context-Add-API-to-force-GC-schedule.patch - fix-leaks-lp1672297-2-object-Queue-a-forced-GC-when-toggling-down.patch - Note: More such patches are under review so this list may grow in future. -- Daniel van Vugt Mon, 16 Apr 2018 14:30:31 +0800 ** Changed in: gjs (Ubuntu) Status: In Progress => Fix Released -- 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/1763878 Title: [regression] Many programs crashing at exit with assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed. Called from cairo_debug_reset_static_data() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1763878/+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
I think I finally understand how the whole default-keyboard configuration is done in ubiquity and console-setup. The reason why it's busted is indeed the keyboard-configuration/xkb-keymap debconf variable. The reason everything worked up until artful was that before artful we have been reverting the xkb-keymap pieces from keyboard- configuration.config because of ubiquity (mostly), and this change was dropped with the artful console-setup merge with Debian. I'm trying to ask around if that was intentional or not. If it was, then we need to handle setting of xkb-keymap after performing language selection (possibly in ubiquity). If not, then we'd have to remove it - or at least the pieces where xkb-keymap is overriding all locale/country-based default keyboard layout selection in console-setup. -- 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 1765147] 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/1765147/+attachment/5121420/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121422/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121425/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121426/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121427/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121428/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765147/+attachment/5121429/+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/1765147 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765147/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765143] Re: nautilus crashed with SIGSEGV in gtk_widget_unparent()
*** This bug is a duplicate of bug 1723791 *** https://bugs.launchpad.net/bugs/1723791 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 #1723791, 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/1765143/+attachment/5121372/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121374/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121378/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121379/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121380/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121381/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765143/+attachment/5121382/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1723791 ** 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/1765143 Title: nautilus crashed with SIGSEGV in gtk_widget_unparent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1754445] Re: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_icon_theme_changed()
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1 --- gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop obsolete patches: - 27-nm-libexec-path.patch - fix-wayland-vbox-crash.patch [ Marco Trevisan (Treviño) ] Cherry-pick patches applied to upstream git master: * ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Renamed from ubuntu_theme_lookup_xdg.patch and cherry-picked from upstream * workspaceThumbnail-only-update-_porthole-if-the-overview-.patch: workspaceThumbnail-rebuild-thumbnails-if-workareas-size-c.patch: workspaceThumbnail-initialize-porthole-based-on-workArea.patch: - Cherry-picks from upstream, avoid unneeded computations in activities * popupMenu-Fix-wrong-call-to-clutter_actor_add_child.patch: - Cherry-pick from upstream * volume-Add-back-sound-feedback-on-scroll.patch: - Fix regression causing missing feedback on volume slider scroll Add patches proposed upstream: * shell-ignore-invalid-window-monitor-index.patch: - Fix crash on accessing on invalid monitor windows (LP: #1724439) * StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch: - Don't try to compute shadows on not allocated icons (LP: #1723378) * js-fix-invalid-access-errors.patch: - Fix javascript errors (LP: #1747566) * workspace-fix-repositioned-windows-in-activities.patch: - Ensure windows thumbnails coordinates are correct (LP: #1653153) * st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch: - Fix possible crash on cache loading * st-texture-cache-Don-t-add-NULL-textures-to-cache.patch: - Fix crash when deleting NULL textures from cache (LP: #1754445) -- Marco Trevisan (Treviño) Tue, 17 Apr 2018 14:40:17 -0400 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- 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/1754445 Title: gnome-shell crashed with SIGSEGV in cogl_object_unref() from iter_remove_or_steal() from g_hash_table_iter_remove() from st_texture_cache_evict_icons() from on_icon_theme_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1653153] Re: Windows not always drawn in correct places in AO when under Wayland
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1 --- gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop obsolete patches: - 27-nm-libexec-path.patch - fix-wayland-vbox-crash.patch [ Marco Trevisan (Treviño) ] Cherry-pick patches applied to upstream git master: * ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Renamed from ubuntu_theme_lookup_xdg.patch and cherry-picked from upstream * workspaceThumbnail-only-update-_porthole-if-the-overview-.patch: workspaceThumbnail-rebuild-thumbnails-if-workareas-size-c.patch: workspaceThumbnail-initialize-porthole-based-on-workArea.patch: - Cherry-picks from upstream, avoid unneeded computations in activities * popupMenu-Fix-wrong-call-to-clutter_actor_add_child.patch: - Cherry-pick from upstream * volume-Add-back-sound-feedback-on-scroll.patch: - Fix regression causing missing feedback on volume slider scroll Add patches proposed upstream: * shell-ignore-invalid-window-monitor-index.patch: - Fix crash on accessing on invalid monitor windows (LP: #1724439) * StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch: - Don't try to compute shadows on not allocated icons (LP: #1723378) * js-fix-invalid-access-errors.patch: - Fix javascript errors (LP: #1747566) * workspace-fix-repositioned-windows-in-activities.patch: - Ensure windows thumbnails coordinates are correct (LP: #1653153) * st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch: - Fix possible crash on cache loading * st-texture-cache-Don-t-add-NULL-textures-to-cache.patch: - Fix crash when deleting NULL textures from cache (LP: #1754445) -- Marco Trevisan (Treviño) Tue, 17 Apr 2018 14:40:17 -0400 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- 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/1653153 Title: Windows not always drawn in correct places in AO when under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1653153/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1 --- gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop obsolete patches: - 27-nm-libexec-path.patch - fix-wayland-vbox-crash.patch [ Marco Trevisan (Treviño) ] Cherry-pick patches applied to upstream git master: * ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Renamed from ubuntu_theme_lookup_xdg.patch and cherry-picked from upstream * workspaceThumbnail-only-update-_porthole-if-the-overview-.patch: workspaceThumbnail-rebuild-thumbnails-if-workareas-size-c.patch: workspaceThumbnail-initialize-porthole-based-on-workArea.patch: - Cherry-picks from upstream, avoid unneeded computations in activities * popupMenu-Fix-wrong-call-to-clutter_actor_add_child.patch: - Cherry-pick from upstream * volume-Add-back-sound-feedback-on-scroll.patch: - Fix regression causing missing feedback on volume slider scroll Add patches proposed upstream: * shell-ignore-invalid-window-monitor-index.patch: - Fix crash on accessing on invalid monitor windows (LP: #1724439) * StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch: - Don't try to compute shadows on not allocated icons (LP: #1723378) * js-fix-invalid-access-errors.patch: - Fix javascript errors (LP: #1747566) * workspace-fix-repositioned-windows-in-activities.patch: - Ensure windows thumbnails coordinates are correct (LP: #1653153) * st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch: - Fix possible crash on cache loading * st-texture-cache-Don-t-add-NULL-textures-to-cache.patch: - Fix crash when deleting NULL textures from cache (LP: #1754445) -- Marco Trevisan (Treviño) Tue, 17 Apr 2018 14:40:17 -0400 ** Changed in: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747566 Title: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1747566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723378] Re: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline(
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1 --- gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop obsolete patches: - 27-nm-libexec-path.patch - fix-wayland-vbox-crash.patch [ Marco Trevisan (Treviño) ] Cherry-pick patches applied to upstream git master: * ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Renamed from ubuntu_theme_lookup_xdg.patch and cherry-picked from upstream * workspaceThumbnail-only-update-_porthole-if-the-overview-.patch: workspaceThumbnail-rebuild-thumbnails-if-workareas-size-c.patch: workspaceThumbnail-initialize-porthole-based-on-workArea.patch: - Cherry-picks from upstream, avoid unneeded computations in activities * popupMenu-Fix-wrong-call-to-clutter_actor_add_child.patch: - Cherry-pick from upstream * volume-Add-back-sound-feedback-on-scroll.patch: - Fix regression causing missing feedback on volume slider scroll Add patches proposed upstream: * shell-ignore-invalid-window-monitor-index.patch: - Fix crash on accessing on invalid monitor windows (LP: #1724439) * StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch: - Don't try to compute shadows on not allocated icons (LP: #1723378) * js-fix-invalid-access-errors.patch: - Fix javascript errors (LP: #1747566) * workspace-fix-repositioned-windows-in-activities.patch: - Ensure windows thumbnails coordinates are correct (LP: #1653153) * st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch: - Fix possible crash on cache loading * st-texture-cache-Don-t-add-NULL-textures-to-cache.patch: - Fix crash when deleting NULL textures from cache (LP: #1754445) -- Marco Trevisan (Treviño) Tue, 17 Apr 2018 14:40:17 -0400 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- 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/1723378 Title: gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from _st_create_shadow_pipeline() from _st_create_shadow_pipeline_from_actor() from st_icon_update_shadow_pipeline() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724439] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call()
This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1 --- gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop obsolete patches: - 27-nm-libexec-path.patch - fix-wayland-vbox-crash.patch [ Marco Trevisan (Treviño) ] Cherry-pick patches applied to upstream git master: * ui-Theme-lookup-should-respect-XDG_DATA_DIRS.patch: - Renamed from ubuntu_theme_lookup_xdg.patch and cherry-picked from upstream * workspaceThumbnail-only-update-_porthole-if-the-overview-.patch: workspaceThumbnail-rebuild-thumbnails-if-workareas-size-c.patch: workspaceThumbnail-initialize-porthole-based-on-workArea.patch: - Cherry-picks from upstream, avoid unneeded computations in activities * popupMenu-Fix-wrong-call-to-clutter_actor_add_child.patch: - Cherry-pick from upstream * volume-Add-back-sound-feedback-on-scroll.patch: - Fix regression causing missing feedback on volume slider scroll Add patches proposed upstream: * shell-ignore-invalid-window-monitor-index.patch: - Fix crash on accessing on invalid monitor windows (LP: #1724439) * StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch: - Don't try to compute shadows on not allocated icons (LP: #1723378) * js-fix-invalid-access-errors.patch: - Fix javascript errors (LP: #1747566) * workspace-fix-repositioned-windows-in-activities.patch: - Ensure windows thumbnails coordinates are correct (LP: #1653153) * st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch: - Fix possible crash on cache loading * st-texture-cache-Don-t-add-NULL-textures-to-cache.patch: - Fix crash when deleting NULL textures from cache (LP: #1754445) -- Marco Trevisan (Treviño) Tue, 17 Apr 2018 14:40:17 -0400 ** Changed in: gnome-shell (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1724439 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765140] 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/1765140/+attachment/5121358/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121360/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121363/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121364/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121365/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121366/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765140/+attachment/5121367/+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/1765140 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/1765140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765139/+attachment/5121438/+files/Stacktrace.txt -- 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765139/+attachment/5121440/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1765139/+attachment/5121346/+files/CoreDump.gz ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Summary changed: - gnome-shell crashed with SIGABRT in g_assertion_message() + gnome-shell crashed with SIGABRT in __GI_raise() ** 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1765139/+attachment/5121439/+files/StacktraceSource.txt -- 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] gnome-shell crashed with SIGABRT in g_assertion_message()
StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:79 g_assertion_message (domain=domain@entry=0x7f13421afb4d "mutter", file=file@entry=0x7f13421b9c4a "core/window.c", line=line@entry=1481, func=func@entry=0x7f13421bbed0 <__func__.113539> "meta_window_unmanage", message=message@entry=0x55636922d150 "assertion failed: (window->display->focus_window != window)") at ../../../../glib/gtestutils.c:2532 g_assertion_message_expr (domain=domain@entry=0x7f13421afb4d "mutter", file=file@entry=0x7f13421b9c4a "core/window.c", line=line@entry=1481, func=func@entry=0x7f13421bbed0 <__func__.113539> "meta_window_unmanage", expr=expr@entry=0x7f13421bac60 "window->display->focus_window != window") at ../../../../glib/gtestutils.c:2555 meta_window_unmanage (window=window@entry=0x55636a9eef40, timestamp=timestamp@entry=3709838) at core/window.c:1481 -- 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/1765139 Title: gnome-shell crashed with SIGABRT in __GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765136] 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/1765136/+attachment/5121332/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121334/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121338/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121339/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121340/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121341/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765136/+attachment/5121342/+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/1765136 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765136/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765135] 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/1765135/+attachment/5121321/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121323/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121327/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121328/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121329/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121330/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765135/+attachment/5121331/+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/1765135 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765135/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765139] [NEW] gnome-shell crashed with SIGABRT in g_assertion_message()
Public bug reported: ubuntu 18.04 . It came out of nowhere. hmmm. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.15.14-041514-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Apr 18 23:08:39 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 meta_window_unmanage () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- 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/1765139 Title: gnome-shell crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765139/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765141] [NEW] Full screen white flash from time to time with Wayland
Public bug reported: I am using Ubuntu 18.04 with gnome shell on Wayland. >From time to time, maybe every one or two hours, the desktop becomes white for a fraction of second. I guess it is just one frame (1/60 of second). It looks like a full filled rectangle of white color but it is so fast I cannot verify to be sure (the only solution I'm thinking of would be to have a fast recording camera pointed to my display). I did not experience that problem on Ubuntu 17.10 with Wayland. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 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: Wed Apr 18 19:26:15 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-07 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session ** Summary changed: - Full screen white flash from time to time + Full screen white flash from time to time with Wayland -- 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/1765141 Title: Full screen white flash from time to time with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765141/+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: console-setup (Ubuntu Bionic) Status: New => In Progress -- 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 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
This Debian bug report is touches this issue: https://bugs.debian.org/877312 Osamu Aoki (the im-config maintainer): > If ibus is started outside of im-config, it may be better to > automatically set im-config to set to "REMOVE". ** Bug watch added: Debian Bug tracker #877312 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877312 -- 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/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765104] Re: nautilus crashed with SIGSEGV in _int_malloc()
*** This bug is a duplicate of bug 1763954 *** https://bugs.launchpad.net/bugs/1763954 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 #1763954, 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/1765104/+attachment/5121140/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121142/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121145/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121146/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121147/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121148/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765104/+attachment/5121149/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1763954 ** 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/1765104 Title: nautilus crashed with SIGSEGV in _int_malloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765110] [NEW] login screen frozen after kernel update
Public bug reported: Ubuntu 17.10 4.13.0-37-generic Asus UX305FA When using the 4.13.0-37-generic kernel, the login screen is completely frozen and unresponsive. Using a different kernel works fine. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1765110 Title: login screen frozen after kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1765110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765088] Re: gnome-shell crashed with SIGABRT
*** This bug is a duplicate of bug 1753078 *** https://bugs.launchpad.net/bugs/1753078 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 #1753078, 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/1765088/+attachment/5121108/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121110/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121115/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121116/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121117/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121118/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765088/+attachment/5121119/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1753078 gnome-shell crashed with SIGABRT in dump_gjs_stack_on_signal_handler() from __GI_raise() from __GI_abort() from glibtop_error_io_vr() from glibtop_error_io_r() from file_to_buffer() from glibtop_get_cpu_s() ** 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/1765088 Title: gnome-shell crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726118] Re: gvfsd-mtp crashed with SIGSEGV in g_vfs_daemon_register_path()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1726118 Title: gvfsd-mtp crashed with SIGSEGV in g_vfs_daemon_register_path() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1726118/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
Crashed at the same time as I got "gnome-shell crashed with SIGSEGV in cogl_object_unref()" after entering xorg session from the gnome-greeter lock-screen. I am not sure if it is related but I had problems with the wayland sessions crashing in the begining, until I changed to single monitor in the settings. For some reason the os detects my unplugged vga connector and wants to use it as an extended screen. I have no idea what the greeter sees or how it handles that, or if it's related at all. -- 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/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+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
Rocko, the other thing to consider is that the patch in comment #68 stops all types of GObject leaks, including those holding resources outside of normal memory. So if for example that texture leak returns (which I expect it may), that will consume texture memory even faster than you see main memory being used. It's mostly an invisible resource, contributing to the VSIZE only, but still using very real and very limited physical/GPU memory. Hidden resource leaks like that would explain slow-downs probably better than the visible memory growth would. -- 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 1765044] [NEW] Cannot set per display scaling from `Displays` applet
Public bug reported: (First of all, this is my first ever bug report :tada: so some information may be missing) Ubuntu Budgie 17.10 gnome-control-center - 1:3.26.2-0ubuntu0.2 Using the `Displays` applet, I am trying to set my primary display to have 200% scaling. However, this causes all displays to use that setting. I can change other settings for my external display (and the `Apply` button appears) but when I change the scaling setting to 100%, I am unable to save! I submitted a report initially to https://github.com/UbuntuBudgie /budgie-desktop-environment/issues/91, but they have directed me here. Apologies if this is in the wrong place - please move around if need be. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Wed Apr 18 13:57:34 2018 InstallationDate: Installed on 2018-02-07 (70 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20180106) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful gnome-17.10 -- 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/1765044 Title: Cannot set per display scaling from `Displays` applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765044/+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
Seems not committed anywhere yet. ** Changed in: gjs (Ubuntu Bionic) Status: Fix Committed => 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 1757058] Re: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R
This bug was fixed in the package gnome-calendar - 3.28.1-1ubuntu2 --- gnome-calendar (3.28.1-1ubuntu2) bionic; urgency=medium * debian/patches/0001-auto-disconnect-weather-changed-signal-handler.patch: fix crash when closing gnome-calendar (LP: #1757058). -- Andrea Azzarone Mon, 16 Apr 2018 17:30:41 +0200 ** Changed in: gnome-calendar (Ubuntu) Status: Fix Committed => Fix Released -- 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/1757058 Title: gnome-calendar (11) gtk_image_reset → gtk_image_clear → update_weather → g_closure_invoke → signal_emit_unlocked_R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1757058/+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
Yes, we know that is only one of the leak fixes. The other fixes (upstream, not reviewed yet) are less mature and have not been included in the Ubuntu patch. -- 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 1761576] Re: gnome-software crashed with SIGSEGV in wl_proxy_marshal → gtk_text_input_destroy → registry_handle_global_remove
the fix is in .30 which is in bionic now ** Changed in: gtk+3.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 gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1761576 Title: gnome-software crashed with SIGSEGV in wl_proxy_marshal → gtk_text_input_destroy → registry_handle_global_remove To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1761576/+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
** Tags added: id-5ad61a208d39d0e15b7bb3c2 -- 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 1765029] 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/1765029/+attachment/5120846/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120848/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120852/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120853/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120854/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120855/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765029/+attachment/5120856/+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/1765029 Title: nautilus-desktop crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765030] 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/1765030/+attachment/5120857/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120859/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120863/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120864/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120865/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120866/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765030/+attachment/5120867/+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/1765030 Title: nautilus-desktop crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1765030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765017] Re: package libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/l
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1765017 Title: package libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1765017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765020] 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/1765020/+attachment/5120813/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120815/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120819/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120820/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120821/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120822/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765020/+attachment/5120823/+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 ** 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/1765020 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765019] 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/1765019/+attachment/5120803/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120805/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120808/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120809/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120810/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120811/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765019/+attachment/5120812/+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/1765019 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/1765019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765020] [NEW] gnome-shell crashed with signal 5
Public bug reported: Left the computer locked and idling over night. When I checked it today there was a crash report on-screen. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 14 01:59:55 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-04-13 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash bionic need-amd64-retrace ** Information type changed from Private to Public -- 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/1765020 Title: gnome-shell crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765020/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765017] [NEW] package libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc
Public bug reported: Trying to update to fix issues with rstudio but this package error prevents this. I don't know what it is or how to fix it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Apr 18 12:16:56 2018 DuplicateSignature: package:libgstreamer0.10-0:0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ... dpkg: error processing archive /var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 InstallationDate: Installed on 2017-09-20 (209 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gstreamer0.10 Title: package libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1765017 Title: package libgstreamer0.10-0 0.10.36-1.5ubuntu1 [modified: usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different from other instances of package libgstreamer0.10-0:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1765017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765004] 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/1765004/+attachment/5120755/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120757/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120760/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120761/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120762/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120763/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1765004/+attachment/5120764/+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/1765004 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/1765004/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764078] Re: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned
what can I do to help out with this problem? -- 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/1764078 Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1764078/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
How about handling this through the docs for now? https://gitlab.gnome.org/gunnarhj/gnome-user-docs/commit/05003485 ** Also affects: gnome-user-docs (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/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+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
I managed to build and install a patched gjs last night thanks to a helpful hint from a fellow user (ie to use debuild -us -uc -b to build it instead of make and make install). Initially, gnome-shell was using around 170 MB according to gnome- system-monitor (atop says consistently says it is using around 100 MB more). It stayed that way until the next morning when something made it jump to 250 MB, and an hour or so later it jumped to 350 MB (it's hard to tell if it jumped all at once or slowly increased, because I think there's a bug in gnome-system-monitor that makes it stop auto-refreshing until you click on its window - when I clicked on gnome-system-monitor, gnome-shell's displayed usage jumped 100 MB each time). Usage stayed at around 350 MB for the morning and most of the afternoon. Eventually, I restarted gnome-shell with ALT-F2 and 'r' and usage dropped immediately to 120 MB. It stayed there for about half an hour until it suddenly jumped to 170 MB, and it has been sitting on that for the last two hours. gnome-shell with an _unpatched_ gjs on my system will go to 450 MB or more in less than an hour, so I think there's a definite improvement with the patch, but there are still some big leaks there. -- 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
