[Bug 2015800] Re: Blank screen after inactivity when set to Never
I confirm that turning off "Dim Screen" fixes the issue! Thanks Jeremy! ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- 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/2015800 Title: Blank screen after inactivity when set to Never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015800] Re: Blank screen after inactivity when set to Never
heather@fenrir:~$ gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 3600 -- 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/2015800 Title: Blank screen after inactivity when set to Never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015800] Re: Blank screen after inactivity when set to Never
** Attachment added: "pic of g-c-c power settings" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+attachment/5662793/+files/Screenshot%20from%202023-04-10%2013-56-10.png -- 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/2015800 Title: Blank screen after inactivity when set to Never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015800] [NEW] Blank screen after inactivity when set to Never
Public bug reported: OS: 23.04 g-c-c: 44.0-1ubuntu4 My laptop is plugged into the charger and indicates that it is charging. In gnome-control-center, I have the "Screen Blank" setting set to Never. Also, "Automatic Suspend" is set to only happen when on battery power. So perhaps even though the battery charger icon indicates it's charging, maybe g-c-c thinks it's not? ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/2015800 Title: Blank screen after inactivity when set to Never To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2015800/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340]
Hi Alexandre, I just tried on a fresh 20.04.6 vm and the issue is no longer present. To test this, I had to `apt purge firefox && snap install firefox` which installed 111.0-2. xdg-desktop-portals is at version 1.6.0-1ubuntu2. -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013115] Re: Bluetooth slider needs toggling two times to disconnect to device
** Description changed: OS: 23.04 gnome-control-center: 44.0-1ubuntu3 bluez: 5.66-0ubuntu1 I use a common bose QC45 headset daily and if I want to disconnect the device, I need to click the toggle slider twice to actually get the headset to disconnect (I hear confirmation of this in the headset). + On the first click, there are no journalctl logs. On the second click + that actually disconnects the device, I see the expected: + + Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), (0xff) + Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), Success(0x20) + Mar 28 11:21:39 fenrir obexd[5665]: disconnected: Transport got disconnected + I would expect to only have to click the slider once to disconnect from the device. ** Description changed: OS: 23.04 gnome-control-center: 44.0-1ubuntu3 bluez: 5.66-0ubuntu1 + bluez-obexd: 5.66-0ubuntu1 I use a common bose QC45 headset daily and if I want to disconnect the device, I need to click the toggle slider twice to actually get the headset to disconnect (I hear confirmation of this in the headset). On the first click, there are no journalctl logs. On the second click that actually disconnects the device, I see the expected: Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), (0xff) Mar 28 11:21:39 fenrir obexd[5665]: DISCONNECT(0x1), Success(0x20) Mar 28 11:21:39 fenrir obexd[5665]: disconnected: Transport got disconnected I would expect to only have to click the slider once to disconnect from the device. -- 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/2013115 Title: Bluetooth slider needs toggling two times to disconnect to device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2013115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013115] [NEW] Bluetooth slider needs toggling two times to disconnect to device
Public bug reported: OS: 23.04 gnome-control-center: 44.0-1ubuntu3 bluez: 5.66-0ubuntu1 I use a common bose QC45 headset daily and if I want to disconnect the device, I need to click the toggle slider twice to actually get the headset to disconnect (I hear confirmation of this in the headset). I would expect to only have to click the slider once to disconnect from the device. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "video of the issue" https://bugs.launchpad.net/bugs/2013115/+attachment/5658389/+files/Screencast%20from%202023-03-28%2008-58-03.webm -- 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/2013115 Title: Bluetooth slider needs toggling two times to disconnect to device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2013115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2003104] [NEW] Transparency ignored in full screen mode
Public bug reported: Ubuntu 23.04 running wayland gnome-terminal 3.46.7-1ubuntu1 In gnome-terminal, I have set the transparency to some amount. When I go to full screen (F11), the transparency is lost and the default transparency is used. When I exit full screen, the transparency comes back and I can see in the profile settings that the transparency has not changed. It seems that tranparency was accidentally removed, and then re-added via https://git.launchpad.net/ubuntu/+source/gnome-terminal/tree/debian/patches/0001-Restore-transparency.patch?h=applied/ubuntu/lunar-devel However, maybe something was missed with regards to full screen. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "video of the issue" https://bugs.launchpad.net/bugs/2003104/+attachment/5642008/+files/Screencast%20from%202023-01-17%2009-26-27.webm -- 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/2003104 Title: Transparency ignored in full screen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2003104/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989204] Re: Activites view only will highlight first icon
You are right, I only see it with the ubuntu-dock extension enabled, and auto-hide turned on. But this only happens in VMs. My 22.04 host has auto-hide on (I tried all 3 locations for the dock with no behavior change) and I'm able to arrow over to the Activities icons with no problem. So is there some hypervisor issue as well? -- 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/1989204 Title: Activites view only will highlight first icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989204] Re: Activites view only will highlight first icon
This is with virt-manager (v4.0.0-1), which uses qemu-system-x86 (v6.2+dfsg-2ubuntu6.3) under the hood. virt-manager is running on an up to date 22.04 host. -- 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/1989204 Title: Activites view only will highlight first icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989204] Re: Activites view only will highlight first icon
Worth noting too that once a VM gets in this state, there's no going back. It's like this 100% of the time, persistent across reboots. -- 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/1989204 Title: Activites view only will highlight first icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989204] [NEW] Activites view only will highlight first icon
Public bug reported: On a couple of different Jammy VMs, I've seen the system get into the state where only the first searched app is highlighted. Any arrow key strokes move to the panel and do not move back to the list of searched applications. (see video) 1. Press super key to expand the Activities view 2. Start typing something, "software" for example, and see the searched apps narrow 3. The first highlighted app is not what I want. Instead I press the right arrow key to navigate to the second one. 4. As soon as I press the right arrow key, the only running app (terminal) is highlighted in the view. Any left arrow key strokes do not go back to highlighting the first app appearing in the search. Note that mouse clicks do not work to start the app I want either. I need to Esc or Super to exit the Activities view, relaunch, and make sure my search terms are exact to ensure the first highlighted app is the one I want. Then when I press Enter, the app starts. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "video showing issue" https://bugs.launchpad.net/bugs/1989204/+attachment/5614824/+files/Screencast%20from%2009-09-2022%2009%3A35%3A19%20AM.webm -- 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/1989204 Title: Activites view only will highlight first icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1987570] Re: help showing document not found
Jeremey, I think you're right. It is broken in the gnome-clocks snap with the following error: (org.gnome.clocks:396259): org.gnome.Clocks-WARNING **: 15:04:20.941: geocoding.vala:42: Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.598" (uid=1000 pid=396259 comm="/snap/gnome-clocks/x1/usr/bin/gnome-clocks " label="snap.gnome- clocks.gnome-clocks (enforce)") interface="org.freedesktop.GeoClue2.Manager" member="GetClient" error name="(unset)" requested_reply="0" destination=":1.599" (uid=122 pid=396357 comm="/usr/libexec/geoclue " label="unconfined") -- 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/1987570 Title: help showing document not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1987570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
The issue exists in the Firefox snap as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 ** Bug watch added: Mozilla Bugzilla #1784977 https://bugzilla.mozilla.org/show_bug.cgi?id=1784977 -- 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/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
If the solution is to remove libcanberra-gtk3-module and since it hasn't been touched since 2012, do we need to provide it at all? -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] Re: gnome-shell lost connection to Xwayland
Thanks for the clarification on their tight coupling! I really hope the crash i saw was some sort of corner case that rarely appears. If I do see it again, I'll let you know. -- 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/1966796 Title: gnome-shell lost connection to Xwayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] Re: gnome-shell lost connection to Xwayland
Ok it wasn't clear to me if the fault was gnome-shell or xwayland. Following the instructional link, I do see https://errors.ubuntu.com/user/ID items, but none around this time. The workaround in bug 994921 is outdated and the line it says to comment is no longer in the file... so I'll just see if it happens again. -- 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/1966796 Title: gnome-shell lost connection to Xwayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1966796/+attachment/5573879/+files/ShellJournal.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/1966796 Title: gnome-shell invalid memory management cause connection loss to wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1966796/+attachment/5573880/+files/monitors.xml.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/1966796 Title: gnome-shell invalid memory management cause connection loss to wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1966796/+attachment/5573878/+files/ProcCpuinfoMinimal.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/1966796 Title: gnome-shell invalid memory management cause connection loss to wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1966796/+attachment/5573877/+files/GsettingsChanges.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/1966796 Title: gnome-shell invalid memory management cause connection loss to wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1966796/+attachment/5573876/+files/Dependencies.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/1966796 Title: gnome-shell invalid memory management cause connection loss to wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966796] [NEW] gnome-shell invalid memory management cause connection loss to wayland
Public bug reported: On an up2date Jammy, running gnome-shell from proposed, and gnome-shell randomly lost my connection to wayland. There was no crash logged in /var/crash. Journalctl shows that after many of these internal errors, gnome-shell experienced a loss of connection with wayland: Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86MacroPreset3 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu1 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu2 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu3 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu4 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu5 Mar 28 10:25:02 fenrir gnome-shell[15578]: Errors from xkbcomp are not fatal to the X server Mar 28 10:25:04 fenrir NetworkManager[1433]: [1648484704.0244] platform-linux: do-add-ip6-address[3: fe80::468f:31f7:6319:46d7]: failure 13 (Permission denied) Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd044211a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd056dcd40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x55ee75f13920 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd0570ec30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x55ee6fecfa70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. Mar 28 10:25:06 fenrir NetworkManager[1433]: [1648484706.0251] platform-linux: do-add-ip6-address[3: fe80::5e83:5ee2:b24c:71b7]: failure 13 (Permission denied) Mar 28 10:25:08 fenrir NetworkManager[1433]: [1648484708.0256] ipv6ll[d24c39fb7105ee85,ifindex=3]: changed: no IPv6 link local address to retry after Duplicate Address Detection failures (back off) Mar 28 10:25:12 fenrir gnome-shell[15153]: Connection to xwayland lost Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: CRITICAL: gsm_client_peek_id: assertion 'GSM_IS_CLIENT (client)' failed Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: GLib-CRITICAL: g_hash_table_find: assertion 'version == hash_table->version' failed Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: WARNING: Lost name on bus: org.gnome.SessionManager Not sure if there's enough info without a crash file to debug, but putting it here just in case. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-29 (636 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 42~beta-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-04 (82 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy wayland-session ** Attachment added: "thisboot.log" https://bugs.launchpad.net/bugs/1966796/+attachment/5573875/+files/thisboot.log ** Tags added: apport-collected jammy wayland-session ** Description changed: On an up2date Jammy, running gnome-shell from proposed, and gnome-shell randomly lost my connection to wayland. There was no crash logged in /var/crash. Journalctl shows that after many of these internal errors, gnome-shell experienced a loss of connection with wayland: Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86MacroPreset3 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu1 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu2 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu3 Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve
[Bug 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLU
I wonder if this is the same thing I just saw: https://paste.ubuntu.com/p/GSWYFy4jYh/ Or if it's not the same thing, I wonder if it is related. Also a clutter_acto_set_mapped: assertion failed crash. I have a crash log too, if you'd like to take a look. -- 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/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867610] Re: snap-store cannot install local deb packages
I can confirm that this issue exists on an updated focal vm. In order to trigger the problem, you need to go click the download chrome button in firefox. Then you get a firefox pop up window that will ask you if you want to Open With Software Install or save the file. If you save the file, then any attempt to install it works fine. However, if you choose Open With in the firefox pop up window, it opens Software Install but says "failed to install: file not supported". That is on the firefox deb (v91.0.2+build1-0ubuntu0.20.04.1) installed by default in focal. In the same vm, I installed the firefox snap (v92.0.3 from --candidate) and had no problem opening the deb in Software Install from the firefox popup window. So this could be a browser snap vs deb problem. @ken-vandine, what do you make of this? Also, I tested this on Impish (since that's what I'm running) and discovered that the firefox snap (v92.0.3 from --candidate) and firefox deb (92.0+build3-0ubuntu1) did not give you a popup window asking if you wanted to Open With or Save. Both of them just default to saving the file to ~/Downloads. -- 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/1867610 Title: snap-store cannot install local deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1867610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867610] Re: snap-store cannot install local deb packages
Aaron, can you please clarify something for me.. I downloaded the google chrome deb and double clicking on it opens it in the Software Install application and I can install it just fine. And you said this would happen. But how did you reproduce the error exactly? Step 3a is ambiguous to me. Can you expand on what you did to open the deb in Software Install that causes the error? -- 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/1867610 Title: snap-store cannot install local deb packages To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1867610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844699] Re: The snap plugin is not claiming the desktop id correctly
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #804 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/804 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/804 Importance: Unknown Status: Unknown -- 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/1844699 Title: The snap plugin is not claiming the desktop id correctly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1844699/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
Well From the auth.log I see this: Oct 23 16:53:18 WLLNXPF1ZY3PG realmd[4214]: Resolving wks.cie.com failed: No DNS record of the requested type for “_kerberos._udp.wks.cie.com†Oct 23 16:53:18 WLLNXPF1ZY3PG realmd[4214]: Error resolving “wks.cie.comâ€: Name or service not known Oct 23 16:53:18 WLLNXPF1ZY3PG realmd[4214]: * No results: wks.cie.com Oct 23 16:53:18 WLLNXPF1ZY3PG realmd[4214]: * No results: wks.cie.com And then from the same corresponding timestamp in the syslog we see the NXDOMAIN that was received. Based on the error in auth.log, could this be an issue with encoding? I wonder where the extra characters are coming from in “wks.cie.com†-- 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/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865166] Re: undefined symbol: gegl_rectangle_subtract
In case anyone else hits this, perhaps this will help... Another user ran into this very issue on a Debian system but removing gimp and reinstalling didn't fix the issue. In order to find the conflicting library, the user removed gimp and it's dependencies then searched for any remaining libraries to manually remove: $ sudo apt-get remove --purge gimp $ sudo find / -iname "*babl*" $ sudo find / -iname "*gegl*" $ sudo find / -iname "*gimp*" Remove any lingering libraries before re-installing gimp. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1865166 Title: undefined symbol: gegl_rectangle_subtract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1865166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
No fractional scaling is enabled. I eventually started just not using fullscreen to avoid the flashing annoyance. I have since upgraded to 20.04. I see now that when I put an app into fullscreen, I no longer see the flashing I reported in this issue. So my guess is something was fixed in focal. -- 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/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866094] Re: Stray B being printed after switching workspaces with wayland
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2314 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2314 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2314 Importance: Unknown Status: Unknown -- 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/1866094 Title: Stray B being printed after switching workspaces with wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866094/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866094] [NEW] Stray B being printed after switching workspaces with wayland
Public bug reported:
The problem is that a stray "B" character is being printed to the
terminal screen after switching work spaces with the Ctrl+Alt+{Up/Down
arrows}.
On the first workspace, I have a few applications running (Firefox is focused)
On the second workspace I have gnome terminal 3.35.91 running in full screen
(F11, so no window boarder) running.
I Ctrl+Alt+Up Arrow to switch to the first workspace and do some things
in FF and then Ctrl+Alt+Down Arrow to switch back to the second
workspace and now see a "B" on the command line.
This happens over and over.. I see the capital B on the commandline when
I switch to this workspace where the terminal is fullscreened.
Some things to note about when this happens:
* This only happens with wayland
* It happens fairly often but not 100% of the time
* The key character created is always a "B"
* I've only seen this key character be created on gnome-terminal
* There are no journalctl logs generated when this occurs
* I have to release the Ctrl+Alt+Up and then do Ctrl+Alt+Down to see the B. (If
I keep Ctrl+Alt pressed and then do Up and Down, the B is not generated)
* It seems more likely to happen if the first workspace is switched to, spend
some time there just clicking things or typing or whatever, and then go back to
the second workspace
* It only happens if gnome-terminal is full screen'd with F11
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 4 17:24:36 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-09-13 (172 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-02-28 (4 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
** Description changed:
- The problem is that a stray character is being printed to the terminal
- screen after switching work spaces with the Ctrl+Alt+{Up/Down arrows}.
+ The problem is that a stray "B" character is being printed to the
+ terminal screen after switching work spaces with the Ctrl+Alt+{Up/Down
+ arrows}.
On the first workspace, I have a few applications running (Firefox is focused)
On the second workspace I have gnome terminal 3.35.91 running in full screen
(F11, so no window boarder) running.
I Ctrl+Alt+Up Arrow to switch to the first workspace and do some things
in FF and then Ctrl+Alt+Down Arrow to switch back to the second
workspace and now see a "B" on the command line.
This happens over and over.. I see the capital B on the commandline when
I switch to this workspace where the terminal is fullscreened.
Some things to note about when this happens:
* This only happens with wayland
* It happens fairly often but not 100% of the time
* The key character created is always a "B"
* I've only seen this key character be created on gnome-terminal
* There are no journalctl logs generated when this occurs
* I have to release the Ctrl+Alt+Up and then do Ctrl+Alt+Down to see the B.
(If I keep Ctrl+Alt pressed and then do Up and Down, the B is not generated)
* It seems more likely to happen if the first workspace is switched to, spend
some time there just clicking things or typing or whatever, and then go back to
the second workspace
* It only happens if gnome-terminal is full screen'd with F11
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.35.91-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 4 17:24:36 2020
DisplayManager: gdm3
InstallationDate: Installed on 2019-09-13 (172 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
- TERM=screen
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ TERM=screen
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-02-28 (4 days ago)
** Summary changed:
- Stray B being printed on workspace after using key bindings to switch between
workspaces
+ Stray B being printed after switching workspaces with wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
Updated the bug link ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2310 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2310 ** Changed in: gnome-shell Importance: Medium => Unknown ** Changed in: gnome-shell Status: Confirmed => Unknown ** Changed in: gnome-shell Remote watch: bugzilla.gnome.org/ #750260 => gitlab.gnome.org/GNOME/gnome-shell/issues #2310 -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865166] Re: undefined symbol: gegl_rectangle_subtract
False alarm everyone. This was just an issue on my host that had some weird things installed. I can't reproduce this on another system so closing. ** Changed in: gimp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1865166 Title: undefined symbol: gegl_rectangle_subtract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1865166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865166] Re: undefined symbol: gegl_rectangle_subtract
A freshly installed focal system doesn't come with gimp and installing it from apt and runnning it works just fine. On a system that experiences this undefined symbol, uninstalling gimp (and autoremove) and reinstalling it fixes the problem. I'm not sure why this fixes the issue because libgegl is the same versions installed previously.. and the same gegl packages get installed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1865166 Title: undefined symbol: gegl_rectangle_subtract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1865166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865166] [NEW] undefined symbol: gegl_rectangle_subtract
Public bug reported: I'm running focal and have both the snap and the deb of gimp installed. The snap runs just fine (although there is a GeglBuffer leak: https://forum.snapcraft.io/t/gimp-geglbuffer-leak/15732). However, if I run the deb from the command line, it won't start and fails with: heather@bmo:~$ gimp gimp: /usr/local/lib/libbabl-0.1.so.0: no version information available (required by gimp) gimp: /usr/local/lib/libbabl-0.1.so.0: no version information available (required by /lib/libgimpwidgets-2.0.so.0) gimp: /usr/local/lib/libbabl-0.1.so.0: no version information available (required by /lib/libgimpcolor-2.0.so.0) gimp: symbol lookup error: gimp: undefined symbol: gegl_rectangle_subtract libgegl is installed but maybe there's an additional gimp/gegl package that provides this symbol and would need to be included in main for the gimp deb to work: heather@bmo:~$ dpkg -l | grep gegl ii gir1.2-gegl-0.4:amd64 0.4.22-1 amd64GObject introspection data for the Generic Graphics Library ii libgegl-0.4-0:amd640.4.22-1 amd64Generic Graphics Library ii libgegl-common 0.4.22-1 all Generic Graphics Library - common files ii libgegl-dev:amd64 0.4.22-1 amd64Generic Graphics Library (development files) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gimp 2.10.14-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 07:59:36 2020 InstallationDate: Installed on 2019-09-11 (169 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gimp UpgradeStatus: Upgraded to focal on 2020-01-17 (41 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1865166 Title: undefined symbol: gegl_rectangle_subtract To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1865166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Changed in: libreoffice (Ubuntu Eoan) Assignee: Marcus Tomlinson (marcustomlinson) => Heather Ellsworth (hellsworth) ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
On my workstation, this happens with fullscreen'd firefox too. Any fullscreen'd app. So it's not limited to the terminal application. However, this does not appear to happen on my thinkpad running 19.10. So I think you're right, it is likely nvidia-specific. -- 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/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1856251] [NEW] Going from apps overview screen to fullscreen'd app causes flash
Public bug reported: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. - Whenever I have a fullscreen app focused on, and then hit the super key, - I see this JS ERROR in the journalctl: - - Dec 12 16:15:14 bmo gnome-shell[3482]: JS ERROR: TypeError: this._workspacesViews[i] is undefined - _updateWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:774:13 - setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/workspacesView.js:764:9 - setWorkspacesFullGeometry@resource:///org/gnome/shell/ui/viewSelector.js:293:9 - _updateWorkspacesGeometry@resource:///org/gnome/shell/ui/overviewControls.js:471:9 - vfunc_allocate@resource:///org/gnome/shell/ui/overviewControls.js:415:9 - _computeWindowCenter@resource:///org/gnome/shell/ui/workspace.js:309:19 - _init@resource:///org/gnome/shell/ui/workspace.js:160:9 - _addWindowClone@resource:///org/gnome/shell/ui/workspace.js:1845:21 - Workspace<@resource:///org/gnome/shell/ui/workspace.js:1166:17 - _updateWorkspaces@resource:///org/gnome/shell/ui/workspacesView.js:265:29 - WorkspacesView<@resource:///org/gnome/shell/ui/workspacesView.js:100:9 - _updateWorkspacesViews@resource:///org/gnome/shell/ui/workspacesView.js:678:24 - show@resource:///org/gnome/shell/ui/workspacesView.js:608:9 - show@resource:///org/gnome/shell/ui/viewSelector.js:268:9 - _animateVisible@resource:///org/gnome/shell/ui/overview.js:532:9 - show@resource:///org/gnome/shell/ui/overview.js:518:9 - toggle@resource:///org/gnome/shell/ui/overview.js:639:13 - _initializeUI/<@resource:///org/gnome/shell/ui/main.js:211:13 - Dec 12 16:15:14 bmo gnome-shell[3482]: NOTE: Not using GLX TFP! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=screen - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) -- You received this bug notification
[Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
Whenever I have a fullscreen app focused on, and then hit the super key, I see this JS ERROR in the journalctl (see attachment). Note that if the app is not fullscreen, there is no flashing and no journalctl error log. ** Attachment added: "journalctl.out" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+attachment/5312068/+files/journalctl.out -- 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/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853351] [NEW] Object St.Button has already been deallocated
Public bug reported: I don't know what causes it but frequently I see my journalctl being spammed with gnome-shell errors (see attached journalctl snippet). If I do nothing about it, then within a few hours gnome-shell is slow and may eventually freeze. So I end up rebooting to reset the system and avoid a freeze. I'll keep my eye out for reproducers but in the mean time I wanted to record this somewhere in case others see it. This happens every couple of days on both my laptop and workstation and both systems are running 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:36:37 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-13 (67 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (62 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "snippet of journalctl for ~1min" https://bugs.launchpad.net/bugs/1853351/+attachment/5306704/+files/journalctl.log -- 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/1853351 Title: Object St.Button has already been deallocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846000] Re: battery level percentage different with and without power connected to laptop
After testing this a bit more, I noticed that when plugging in the power the battery percentage says 100% for *some period of time* before changing to match the percentage that upower has. The time it takes for the percentage to go from 100%->true% varies anywhere from a second to minutes but it does eventually seem to settle back on the upower reported percentage. -- 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/1846000 Title: battery level percentage different with and without power connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846000] Re: battery level percentage different with and without power connected to laptop
Brief video displaying the behavior. You can see when the power is connected or not because the lightning bolt shows up when the power is connected. ** Attachment added: "1846000.mkv" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292898/+files/1846000.mkv -- 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/1846000 Title: battery level percentage different with and without power connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846000] Re: battery level percentage different with and without power connected to laptop
The output of `upower -d` with the power cable unplugged. ** Attachment added: "unplugged.out" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292886/+files/unplugged.out -- 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/1846000 Title: battery level percentage different with and without power connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846000] [NEW] battery level percentage different with and without power connected to laptop
Public bug reported: Hardware: Lenovo T590 OS: 19.10 I have the battery percentage displayed next to the battery icon in the top bar (Tweaks -> Top Bar -> Battery Percentage). When the power cord is connected, it says 100%. However, if I unplug the power cord, the percentage drops down to 94% immediately. Plug in the power cord again, and it's back to 100%. If I let the battery discharge a bit so the unplugged state shows 91%, then plug in the power cable, it says 100% briefly before updating to be 91%. Let it charge for a few minutes so with the power connected it says 92%, then unplug the power and it says 93%. The percentage displayed when the power is connected vs when the power is not connected is not consistent with each other like it should be. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 30 11:22:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-13 (16 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: Hardware: Lenovo T590 OS: 19.10 I have the battery percentage displayed next to the battery icon in the top bar (Tweaks -> Top Bar -> Battery Percentage). When the power cord is connected, it says 100%. However, if I unplug the power cord, the percentage drops down to 94% immediately. Plug in the power cord again, and it's back to 100%. + + If I let the battery discharge a bit so the unplugged state shows 91%, + then plug in the power cable, it says 100% briefly before updating to be + 91%. Let it charge for a few minutes so with the power connected it says + 92%, then unplug the power and it says 93%. + + The percentage displayed when the power is connected vs when the power + is not connected is not consistent with each other like it should be. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 30 11:22:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-13 (16 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (11 days ago) -- 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/1846000 Title: battery level percentage different with and without power connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1846000] Re: battery level percentage different with and without power connected to laptop
The output of `upower -d` with the power cable plugged in. ** Attachment added: "plugged-in.out" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+attachment/5292885/+files/plugged-in.out -- 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/1846000 Title: battery level percentage different with and without power connected to laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846000/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844699] [NEW] The snap plugin is not claiming the desktop id correctly
Public bug reported: With a desktop snap application open, you can go to "Show Details" and it will launch GNOME Software which expects an app id. The desktop id is being passed to Software and the result is Software displaying "Unable to find gnome-clocks_gnome-clocks.desktop". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 19 17:21:01 2019 InstallationDate: Installed on 2019-09-13 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-09-19 (0 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1844699 Title: The snap plugin is not claiming the desktop id correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1844699/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
