[Bug 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload
** Changed in: systemd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683867] Re: Have to click "Restart" and "Shutdown" button twice to make button work.
Yes, that's what it says if you click on the 'Triaged' button at the top where you can change it, for it is says as a description "Verified by the bug supervisor.". -- 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/1683867 Title: Have to click "Restart" and "Shutdown" button twice to make button work. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1683867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683867] Re: Have to click "Restart" and "Shutdown" button twice to make button work.
@cubic-wizard, I'm pretty sure that 'Triaged' indicates that a developer here was able to reproduce it and that it is more than just users having the issue. That's what I've always taken it to mean anyway. Please correct me if I am wrong. -- 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/1683867 Title: Have to click "Restart" and "Shutdown" button twice to make button work. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1683867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
It may not be flatpak on its own, but the machine I installed (and later removed and purged) flatkpak on this problem exists. (So a correlation does seem to exist) It might have something to do with other PPAs or how packages you install from external PPAs affect the system. The only major changes I made with the system around the time this happened was installing flatpak (and monodevelop through it), wine updating to 2.11 staging, and some retroarch cores updating. Also it might be worth looking into how exactly the gnome-keyring-daemon is started on login to see if there is a manual edit to some file that could resolve this issue. Sadly I don't have much else to offer other than that I am using Xubuntu 16.04.2 and have decided that the best temporary fix is to just enter my password in a second time by automatically starting the keyring daemon on startup. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703087] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1703087/+attachment/4911173/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911175/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911178/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911179/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911180/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911181/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1703087/+attachment/4911182/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** 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/1703087 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1703087/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
@all: Please try if the problem appears for a new clean user. In my case it didn't so I suspect that it is related to some configuration files in ~/. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
17.04 with GNOME Shell: can't use the Alt+Shift+# key combination in the gnome-terminal because of that. -- 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/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1245473/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703092] [NEW] package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: error shows when upgrading system Could not install 'systemd-shim' ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-23.25-generic 4.10.17 Uname: Linux 4.10.0-23-generic i686 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: i386 Date: Sat Jul 8 10:37:04 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2013-05-04 (1525 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check third-party-packages zesty -- 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/1703092 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
In my case, the problem appears also for the new clean user. I tried a new standard user without password, a new standard user with password and a new administrator user with password, but it did the same in all cases. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Thanks for testing, looks like several different bugs are mixed up here (or it's just me posting a similar problem in the wrong bug report...). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703110] [NEW] notes doesn't delete only if empty
Public bug reported: [Impact] Unnesessary work for the user as he is forced to clear the note from text in order to delete it. It makes it more difficult that selecting text isn't possible with mouse. [Test Case] Write anything in a note and it can't be deleted with 'x' or with 'delete notes' menu item. [Other Info] System configuration: roland@roland-Lenovo-ideapad-110-15I `:+ss+:` -+ssyy+- OS: Ubuntu 17.04 x86_64 .ossdMMMNyo. Model: 80T7 Lenovo ideapad 110-15IBR /ssshdmmNNmmyNhss/ Kernel: 4.10.0-26-generic +shmydMMMNy+ Uptime: 4 hours, 45 mins /hNMMMyhhhmNMMMNh/Packages: 2360 .dMMMNhsshNMMMd. Shell: bash 4.4.7 +hhhyNMMNyyNMMMysss+ Resolution: 1366x768 ossyNMMMNyMMhsshmmmhssso DE: GNOME-Flashback:GNOME ossyNMMMNyMMhsshmmmhssso WM: Compiz +hhhyNMMNyyNMMMysss+ WM Theme: Adwaita .dMMMNhsshNMMMd. Theme: Adwaita [GTK2/3] /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3] +sdmydy+ Terminal: gnome-terminal /ssshdmmyNhss/ CPU: Intel Pentium N3710 (4) @ 2.5GH .ossdMMMNyo. GPU: Intel HD Graphics 405 -+syyy+- Memory: 1674MiB / 3862MiB `:+ss+:` .-/+oooo+/-. Stickynotes version: 3.22.0 ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1563155] Re: No Application Data Found
Maybe this will help somebody, the only thing that works for me: FoxitReader creates the file /home/nis/.local/share/applications but gnome-software needs the directory /home/nis/.local/share/applications/ After deleting /home/nis/.local/share/applications all works well again. (I installed FoxitReader as newcomer from Windows... and now I tested all things proposed here. With gnome-software --verbose let's me find the problem.) -- 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/1563155 Title: No Application Data Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1563155] Re: No Application Data Found
> FoxitReader creates the file /home/nis/.local/share/applications Are you sure it creates a *file* with that name? If so, that's a pretty huge bug in FoxitReader's install process, and we should report it to them. -- 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/1563155 Title: No Application Data Found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1563155/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
…flatpak may not be the source problem but it seems to bring something that helps highlighting the problem… ( I suspect some gnome-related parameters ). I assume some other ppa's as well can bring the same problem, maybe by comparing them we could narrow down a culprit ? I can also confirm that once the problem surfaces it affects all the users on the machine ( ubuntu 16.04 unity here ). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700764] Re: snap policykit prompt in Turkish language
Is there any progress on this, or any logs we can provide to help debug? This is (for many people) the first thing they see when installing a snap, and it's a bit alarming to get it in a language we don't recognise. I just experienced it on a new laptop in 17.04. ** Attachment added: "Screenshot from 2017-07-08 18-13-50.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1700764/+attachment/4911353/+files/Screenshot%20from%202017-07-08%2018-13-50.png -- 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/1700764 Title: snap policykit prompt in Turkish language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1700764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700764] Re: snap policykit prompt in Turkish language
Alan Pope 🍺🐧🐱 🦄 (popey), I don't think the status has changed since the last update. Robert hasn't been able to figure out how to ensure the user's language environment settings get passed through to the correct place. -- 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/1700764 Title: snap policykit prompt in Turkish language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1700764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296270] Re: Have to login twice after suspending
By the way, I'm on Xubuntu Xenial (16.04) as well. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1296270 Title: Have to login twice after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296270] Re: Have to login twice after suspending
Hey guys, I have figured out what was causing the problem for me. In the power manager, there is an option that says "automatically lock the screen" and it was set to "when the screensaver was activated". Along with that, there was another checkbox that was checked that said "lock screen when system is going for sleep." Because both of these things happened when my system went for sleep, the system ended up locking itself twice. Setting the "automatically lock the screen" option to "never" fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1296270 Title: Have to login twice after suspending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1296270/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703145] [NEW] gvfsd-mtp crashed with SIGSEGV
Public bug reported: . ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gvfs-backends 1.32.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sat Jul 8 12:40:42 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2015-04-30 (800 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/3 ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fe004a03cc9: mov0x18(%rax),%rax PC (0x7fe004a03cc9) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash artful need-amd64-retrace third-party-packages -- 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/1703145 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1703145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703110] Re: notes doesn't delete only if empty
** Also affects: gnome-applets (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703145] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1689770 *** https://bugs.launchpad.net/bugs/1689770 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 #1689770, 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/1703145/+attachment/4911405/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911407/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911410/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911411/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911412/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911413/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1703145/+attachment/4911414/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1689770 ** Tags removed: need-amd64-retrace -- 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/1703145 Title: gvfsd-mtp crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1703145/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703110] Re: notes doesn't delete only if empty
This bug was fixed in the package gnome-applets - 3.24.1-1ubuntu1 --- gnome-applets (3.24.1-1ubuntu1) artful; urgency=medium * Backport two upstream fixes for the stickynotes applet (LP: #1703110). -- Dmitry Shachnev Sat, 08 Jul 2017 23:56:20 +0300 ** Changed in: gnome-applets (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in Ubuntu. https://bugs.launchpad.net/bugs/1703110 Title: notes doesn't delete only if empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/1703110/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1618910] Re: (gnome-shell:4131): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
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/1618910 Title: (gnome-shell:4131): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1618910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1647187] Re: gnome-software crashed with signal 5 in g_main_context_new()
I'm on Ubuntu 16.04.1 (Gnome) and experienced this problem. Solved with: sudo apt-get upgrade gnome-software -- 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/1647187 Title: gnome-software crashed with signal 5 in g_main_context_new() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1647187/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 581618] Re: Restart session unexpected 10.04
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/581618 Title: Restart session unexpected 10.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/581618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1703171] Re: gnome-shell crashed with signal 5 in _XIOError()
*** This bug is a duplicate of bug 1505409 *** https://bugs.launchpad.net/bugs/1505409 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 #1505409, 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/1703171/+attachment/4911513/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911515/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911518/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911519/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911520/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911521/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1703171/+attachment/4911522/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1505409 gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"] ** 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/1703171 Title: gnome-shell crashed with signal 5 in _XIOError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1703171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
