[Bug 1783571] Re: Set Yaru as default
As a reminder, ubuntu-settings is failing due to a meson issue: https://github.com/mesonbuild/meson/issues/3914. The stack has been tested locally and everything works well, including transition with removal of older alternatives and fallback to plan Shell for GDM without the theme installed. ** Bug watch added: github.com/mesonbuild/meson/issues #3914 https://github.com/mesonbuild/meson/issues/3914 -- 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/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773244] Re: gnome-shell using high cpu
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1773244 Title: gnome-shell using high cpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1759591] Re: gnome-control-center assert failure: corrupted size vs. prev_size
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759591 Title: gnome-control-center assert failure: corrupted size vs. prev_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1759591/+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()
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/350174 ** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/nautilus/+git/nautilus/+merge/351021 -- 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 1783676] Re: /usr/bin/gnome-shell:11:clutter_input_device_xi2_get_current_tool:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_host
*** This bug is a duplicate of bug 1783673 *** https://bugs.launchpad.net/bugs/1783673 ** This bug has been marked a duplicate of bug 1783673 gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool() -- 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/1783676 Title: /usr/bin/gnome- shell:11:clutter_input_device_xi2_get_current_tool:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_host_xevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783676/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1627861] Re: Have close button next to windows in list in AO dock's right-click view
** Changed in: gnome-shell Status: Confirmed => Won't Fix -- 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/1627861 Title: Have close button next to windows in list in AO dock's right-click view To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1627861/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783673] Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool()
It appears a few people experience the same crash: https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f in 17.04, 17.10, 18.04 and 18.10. ** Tags added: artful bionic ** Description changed: - NA + https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.28.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.17.0-4.5-generic 4.17.3 Uname: Linux 4.17.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Jul 25 21:54:39 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: - + InstallationDate: Installed on 2018-06-18 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: - Segfault happened at: 0x7f3325479e50:mov0x128(%rdi),%rax - PC (0x7f3325479e50) ok - source "0x128(%rdi)" (0x0128) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7f3325479e50:mov0x128(%rdi),%rax + PC (0x7f3325479e50) ok + source "0x128(%rdi)" (0x0128) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so - ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so - ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so - clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so - ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so + ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so + ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so + clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so + ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** 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/1783673 Title: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783673] Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool()
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/1783673 Title: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783676] [NEW] /usr/bin/gnome-shell:11:clutter_input_device_xi2_get_current_tool:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_ho
*** This bug is a duplicate of bug 1783673 *** https://bugs.launchpad.net/bugs/1783673 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.3-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/4da1b43d4e01e82127276108c1e6c2169c68410f 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: artful bionic cosmic zesty -- 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/1783676 Title: /usr/bin/gnome- shell:11:clutter_input_device_xi2_get_current_tool:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_host_xevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783676/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 513143] Re: geocoding metadata
** Changed in: f-spot Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/513143 Title: geocoding metadata To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/513143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782739] Re: Boot to Black
Perhaps this might be a workaround too?... Edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false Reboot. -- 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/1782739 Title: Boot to Black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764779] Re: Nautilus crashed open Windows-partition
While we're mitigating this error at nautilus level, and while this should also probably be fixed in gtk (same patch, just changing file names), I'm quite sure this is due to some lower level problem. So for now I've also submitted the issue upstream at GLib level: -https://gitlab.gnome.org/GNOME/glib/issues/1458 -- 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/1764779 Title: Nautilus crashed open Windows-partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1764779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764779] Re: Nautilus crashed open Windows-partition
** Changed in: nautilus (Ubuntu) Status: Fix Released => In Progress -- 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/1764779 Title: Nautilus crashed open Windows-partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1764779/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 444282] Re: baobab should be aware of ecryptfs private directories
My nextcloud client also refuses to sync...not enough space... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/444282 Title: baobab should be aware of ecryptfs private directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/444282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 444282] Re: baobab should be aware of ecryptfs private directories
Actually this a pretty ugly bug. My system halted with no icons left on my desktop. And my steam client keeps telling me that there is not space left to install the update, even this is actually not the case. The home folder should be calculated by half because my user has ecryptfs files and mounted ecrypt partition. Both are considered equally when calculating the total disk usage...damned... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/444282 Title: baobab should be aware of ecryptfs private directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/444282/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573581] Re: Showing wrong times for imported calendars
upstream report https://gitlab.gnome.org/GNOME/gnome-calendar/issues/143 ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Triaged -- 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/1573581 Title: Showing wrong times for imported calendars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1573581/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779238] Re: Mouting a disk or iso image asks for sudo password
** Changed in: gnome-disk-utility (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1779238 Title: Mouting a disk or iso image asks for sudo password To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1779238/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt
** Changed in: gnome-menus (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1765799 Title: Applications menu does not get populated with recently installed apps using apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1724188] Re: 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
** Tags added: rls-cc-incoming -- 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/1724188 Title: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1724188/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783626] [NEW] systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed
Public bug reported: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed See https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: block-proposed -- 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/1783626 Title: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1652618] Re: Impossible to unlock the screen when using non-English language
This is possibly related to bug #1769224. -- 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/1652618 Title: Impossible to unlock the screen when using non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
Ubuntu 18.04.1 is coming soon (tomorrow?). What about the bug fixes?
I know a temporary method, but it is not so nice (but it works, saves
~400MB RAM): run after login
sudo killall -u gdm
killall gnome-software
One more, clear gnome-calendar. It launches automatically, uses
constantly 2-400MB RAM, and do nothing.
sudo apt remove gnome-calendar
waffen <1672...@bugs.launchpad.net> ezt írta (időpont: 2018. júl. 16., H, 5:01):
>
> Well for this bug I need to install Xubuntu and lightdm, run very fast
> with no issues, BUT looks like Firefox is eating a lot of RAM in both
> desktops, for my job I need FF to be opened all the time, so the time to
> time I need to close it and relaunch it, if not FF freezing my desktop,
> now even Chrome eats a lower portion of RAM than FF... are you have
> similar problems with FF + ubuntu?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1672297
>
> Title:
> gnome-shell uses lots of memory, and grows over time
>
> Status in GNOME Shell:
> Confirmed
> Status in gjs package in Ubuntu:
> Fix Released
> Status in gjs source package in Bionic:
> In Progress
>
> Bug description:
> Upstream:
> https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
>
> ---
>
> gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
> almost 2 GiB.
>
> user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
> /usr/bin/gnome-shell
>
> strace output is voluminous; here is a representative sample:
>
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\231\n\10\0\n\0
> \0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
> \0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
> poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
> recvmsg(5, {msg_name(0)=NULL,
> msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
> 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
> recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
> writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN},
> {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN},
> {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN},
> {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15,
> 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN},
> {fd=26, events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN},
> {fd=34, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN},
> {fd=40, events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15,
> 0) = 0 (Timeout)
> recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> open("/proc/self/stat", O_RDONLY) = 36
> fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> fcntl(36, F_GETFL) = 0x8000 (flags
> O_RDONLY|O_LARGEFILE)
> fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
> read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
> read(36, "", 3072) = 0
> close(36) = 0
> recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
> unavailable)
> poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
> {fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,
[Bug 1652618] Re: Impossible to unlock the screen when using non-English language
Same issue on 18.04. -- 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/1652618 Title: Impossible to unlock the screen when using non-English language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
yaru MIR is https://bugs.launchpad.net/ubuntu/+source/yaru- theme/+bug/1783600 ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- 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/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783571] Re: Set Yaru as default
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-session (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/1783571 Title: Set Yaru as default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783452] Re: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications
** Package changed: ubuntu => gtk+2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1783452 Title: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783452] [NEW] Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications
You have been subscribed to a public bug: After switching from 16.04 to 18.04 I noticed that fonts are now (in 18.04) rendered differently in GTK+ apps. For example, there is a vertical bar charcter `│` [U+2502](https://unicode-table.com/en/2502), that is used extensively to create solid vertical lines using just text characters. You can see it in console apps such as `mc` or `pstree`. While it is rendered correctly in Terminal in both 16.04 and 18.04, when rendered inside GTK apps it has unexpected vertical gap in-between characters on 18.04 (16.04 renders it correctly). The issue can be seen in GTK apps such as gVIM, Geany, GEdit, but Qt apps seem to render it properly. I have attached a screenshot that clearly demonstrates the difference. It shows brand new Ubuntu 16.04 on a left side where you can see vertical line in GEdit is completely solid, as it should be. On a right side it shows Ubuntu 18.04 where you can see line now has gaps that should not be there. I built a small GTK2 test app that reproduces the problem (sources at https://pastebin.com/WCH1ds4P), and using it I found that the problem occurs when libfreetype 2.8+ is used. I tested FreeType 2.6, 2.7, 2.7.1 and all of them work fine. While 2.8 and above has this gap. I am not 100% sure if this is an Ubuntu font configuration issue, or bug in FreeType, or GTK or some other Ubuntu components, but I hope someone at least can point me at the right direction. Please also check my post on AskUbuntu which has additional detail and screenshots: https://askubuntu.com/questions/1054779/incorrect-font- glyphs-rendering-in-gtk-applications-in-ubuntu-18-04 ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications https://bugs.launchpad.net/bugs/1783452 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
This bug was fixed in the package console-setup - 1.178ubuntu6
---
console-setup (1.178ubuntu6) cosmic; urgency=medium
* keyboard-configuration.{config,templates}: There is no good default for
layout toggling, stop pretending there is. Console users can set one
with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)
-- Adam Conrad Wed, 25 Jul 2018 05:50:59 -0600
** Changed in: console-setup (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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative shortcut for layout switching Alt+Shift unexpectedly set
by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
** Changed in: console-setup (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: console-setup (Ubuntu) Assignee: Gunnar Hjalmarsson (gunnarhj) => Adam Conrad (adconrad) -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
@Adam: Sad to hear that the proposed fix caused yet another regression, and sorry for the inconvenience it caused. On 2018-07-25 03:31, Adam Conrad wrote: > That said, I think the "run it sometimes, but not always" fix was > probably naive at best. The only two options that seem to make > sense for fixing this properly are: > > 1) Make GNOME stop writing things to that file that console-setup > doesn't understand, or > 2) Make console-setup understand the things GNOME writes to that > file. Basically it's the other way around; console-setup adds XKBOPTIONS to /etc/default/keyboard, sometimes behind the scenes, but GNOME does not include GUIs for controlling XKBOPTIONS system wide (only per user). At the same time, when you use the GNOME GUI to change the keyboard configuration system wide, it brutally drops any XKBOPTIONS in /etc/default/keyboard. I'm going to bring it up with the desktop team, and try to figure out a better approach to handle this dissonance. Then let's make sure in advance that whatever we comes up with does not interfere with the installer. -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1782739] Re: Boot to Black
Daniel, Clicking on each of these links resulted in a 404 error. I am very interested and willing to work this issue but I also know your time is valuable. I have established a work around by setting my system to auto logon. That bypasses the offending condition. I have not run into the blank screen anywhere else. I am sure the problem is being caused by some odd ASUS bios boot-up condition. I have worked with Linux enough to know the capability and quality of the product. I would blame ASUS before Ubuntu. Let me know how you want to proceed. Thank you. Gene On Tue, Jul 24, 2018 at 9:57 PM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Note to self: possibly related to bug 1782934. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1782739 > > Title: > Boot to Black > > Status in gdm3 package in Ubuntu: > Incomplete > Status in linux package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > > Bug description: > When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see > the splash screen as expected. The boot continues and it reaches the > point where you would expect to see the login screen. I see what > appears to be a non-backlighted blank black screen. If I wait until > all hard drive activity ceases and then type in my password and press > enter the login completes and I am presented a normal Ubuntu desktop. > > Thank you > Gene > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7 > ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 > Uname: Linux 4.15.0-23-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Jul 20 07:16:51 2018 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, including running git bisection searches > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics > Controller [1043:166d] > InstallationDate: Installed on 2018-07-20 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: ASUSTeK COMPUTER INC. TP550LA > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic > root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash > vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/27/2014 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: TP550LA.210 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: TP550LA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014: > svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.: > rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: TP > dmi.product.name: TP550LA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions > -- 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/1782739 Title: Boot to Black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 965953] Re: Indicator menus are too short and scroll when opened from screen bottom
It got worse in 18.04. Now the workaround does not work any more. And it is ignored by GTK people. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/965953 Title: Indicator menus are too short and scroll when opened from screen bottom To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/965953/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1782347 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726439] Re: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed
Bug confirmed on 18.10, so the patch ( https://gitlab.gnome.org/GNOME/yelp/issues/52#note_179024 ) from upstream was not applied to the master branch. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/726439 Title: Search for document returns an Unknown error: 'URI xref:search=' could not be parsed To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/726439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Changed in: gdm3 (Ubuntu) Status: Confirmed => New ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1753263] Re: GNOME Power Statistics shows nothing on Ubuntu 18.04
On a Dell XPS 15 9560 laptop I'm seeing the same error as above on the "Processor" section : Processor wakeups per second: GDBus.Error:org.freedesktop.UPower.GeneralError: cannot enable timerstats The other panels seem to work right, including: * AC adapter * Laptop battery * Mouse (it's a Logitech bluetooth) * Keyboard (Logitech bluetooth too) -- 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/1753263 Title: GNOME Power Statistics shows nothing on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1753263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Attachment added: "dmesg_noquiet_single.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167535/+files/dmesg_noquiet_single.txt -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Attachment added: "journalctl_noquiet_single.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167536/+files/journalctl_noquiet_single.txt ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Attachment removed: "dmesg_noquiet_nomodeset.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782347/+attachment/5167532/+files/dmesg_noquiet_nomodeset.txt -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
Nothing crashed, so I skipped Your points #2 and #3. As for #1, here's the log: * when booting with 'noquiet nomodeset' * and when booting with 'noquiet single' (I must add 'single' because starting gdm without 'nomodeset' halts the machine). Thanks, MZ ** Attachment added: "dmesg_noquiet_nomodeset.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167532/+files/dmesg_noquiet_nomodeset.txt -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Attachment added: "journalctl_noquiet_nomodeset.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167534/+files/journalctl_noquiet_nomodeset.txt -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782347] Re: [radeon] GDM3 fails to load without nomodeset
** Attachment added: "dmesg_noquiet_nomodeset.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+attachment/5167533/+files/dmesg_noquiet_nomodeset.txt -- 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783363] Re: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable.
This bug was fixed in the package gnome-shell - 3.28.3-0ubuntu2 --- gnome-shell (3.28.3-0ubuntu2) cosmic; urgency=medium * debian/patch/js-fix-invalid-access-errors.patch: - Updated to include upstream requested changes and removing wrongly preserved code from previous refresh (LP: #1783363) * debian/patches/workspace-fix-repositioned-windows-in-activities.patch: - Cherry-pick from upstream 3.28 branch -- Marco Trevisan (Treviño) Wed, 25 Jul 2018 01:40:50 +0200 ** Changed in: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1783363 Title: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783511] [NEW] gvfsd-metadata extreme log spamming
Public bug reported: Hello, I'm Using Ubuntu 18.04 LTS everytime i browse our mounted CIFS / SMB share or open a file Journald fills up with the following messages: jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed jul 25 10:21:17 Precision-7510 gvfsd-metadata[3015]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
[Bug 1783363] Re: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable.
Fix committed to cosmic proposed: https://launchpad.net/ubuntu/+source/gnome-shell/3.28.3-0ubuntu2 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1783363 Title: [regression] GNOME Shell 3.28.3 - Super key makes desktop unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1783363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783499] [NEW] systemd: Failed to send signal
Public bug reported: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dbus systemd ** Also affects: dbus (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/1783499 Title: systemd: Failed to send signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
