[Bug 2007262] Re: Ubuntu's GNOME desktop is higher latency than necessary
** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed -- 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/2007262 Title: Ubuntu's GNOME desktop is higher latency than necessary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2007262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I've created https://github.com/snapcore/snapd/pull/12627 as a proposed fix for the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
Okay. In a clean Lunar VM with glib 2.75.3 installed and ibus enabled as
described in the bug description, I could reproduce the input problems
in Firefox. I saw the following AppArmor denial in the dmesg logs:
[ +0.343553] audit: type=1400 audit(1678248386.012:62):
apparmor="DENIED" operation="connect" profile="snap.firefox.firefox"
name="/home/james/.cache/ibus/dbus-THbBfRNt" pid=2398 comm="pool-
firefox" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000
I edited /var/lib/snapd/apparmor/profiles/snap.firefox.firefox and added
the following rule:
@{HOME}/.cache/ibus/dbus-* rw,
After reloading the policy with "apparmor_parser -r
.../snap.firefox.firefox", keyboard input worked again. So that confirms
my guess about the cause of the problem. This is something we can fix
via a snapd update.
Longer term, we should get these snaps using ibus's portal interface,
which is both more secure (i.e. suitable to allow in the desktop
interface) and should be immune to future changes of this type.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2008279
Title:
glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
IBus is turned on
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04
The missing style is called disk-space-display in nautilus: src/resources/css/Adwaita.css ** No longer affects: nautilus (Ubuntu) -- 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/2008791 Title: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2008791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
This seems like the most likely culprit: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3005 This basically means that code that would have created an abstract namespace socket in glib 2.74.x now creates a regular unix domain socket in 2.75.x. We have AppArmor rules in snapd's desktop-legacy interface granting access to the abstract namespace socket in $XDG_CACHE_HOME, but nothing for the equivalent regular socket: https://github.com/snapcore/snapd/blob/d5f47ca71fcd8a884072e75391a7e55d9ec9d145/interfaces/builtin/desktop_legacy.go#L142-L149 I still need to verify this is the actual cause, but if so it should be relatively simple to update snapd's AppArmor rules to allow access to this socket. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on
I think last time we had problems like this it was due to changes in the location of the socket for ibus's private D-Bus bus. Looking into the glib diffs for clues. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009564] Re: Touchpad disabling while typing does not work
Please report the bug to: https://gitlab.freedesktop.org/libinput/libinput/-/issues and mention the machine model is Razer x Lambda. ** Summary changed: - Touchpad disabling while typing does not work + [Razer x Lambda] Touchpad disabling while typing does not work ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2009564 Title: [Razer x Lambda] Touchpad disabling while typing does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2009564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008613] Re: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1949 https://github.com/micheleg/dash-to-dock/issues/1949 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1949 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (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-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2008613 Title: gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu- d...@ubuntu.com/locations.js:370] To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/2008613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
I'm still seeing this behaviour (precisely as described at the top: fades to black, switches off, then switches on to black a second or two later) with the lunar daily image and the bootstrap 6.2 kernel, so it'll likely be an issue in lunar. I'll flash a jammy and kinetic image to a card in a bit and try and re- confirm them there but kinetic certainly exhibited the issue last week before I upgraded my devel system. In case this is monitor specific, the monitor I'm using is a Benq GW2270H running at 1080p. -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2009564] Re: Touchpad disabling while typing does not work
Thanks, Daniel - I assumed this bug was known -- others online have had it. But I wanted to still report it in hope that it will not always be an issue. - Neither setting org.gnome.desktop.peripherals.touchpad disable-while-typing nor any other solution I have found online for this works. Everything has invariably failed to make the touchpad shut off while typing. - I have been trying earlier today to log in with Xorg, and this is its own can of worms. I can't, and I'm not sure why. I don't have the option to with a little gear on startup/login. And when I try to edit /etc/gdm3/custom.conf and restart the computer, it won't start up unless I use ctrl+alt+f4 to open up a virtual console on startup and undo the change to /etc/gdm3/custom.conf. In summary, nothing works. If some immediate solution comes to mind, great. Else, I'll hope for an update soon. Thanks! On Tue, Mar 7, 2023 at 4:30 AM Daniel van Vugt <2009...@bugs.launchpad.net> wrote: > I assume you mean: > > org.gnome.desktop.peripherals.touchpad disable-while-typing true > > Does it work any better if you log into Ubuntu on Xorg instead? > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Also affects: libinput (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2009564 > > Title: > Touchpad disabling while typing does not work > > Status in libinput package in Ubuntu: > New > Status in mutter package in Ubuntu: > New > > Bug description: > It makes my laptop much less usable. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 > Uname: Linux 5.19.0-35-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular > file. > .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. > .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular > file. > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 > 00:49:50 UTC 2023 >GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) > ApportVersion: 2.20.11-0ubuntu82.3 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: pass > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Mar 7 00:44:08 2023 > DistUpgraded: Fresh install > DistroCodename: jammy > DistroVariant: ubuntu > DkmsStatus: >backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! > Diff between built and installed module!) (WARNING! Diff between built and > installed module!) (WARNING! Diff between built and installed module!) > (WARNING! Diff between built and installed module!) (WARNING! Diff between > built and installed module!) (WARNING! Diff between built and installed > module!) >backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! > Diff between built and installed module!) (WARNING! Diff between built and > installed module!) (WARNING! Diff between built and installed module!) > (WARNING! Diff between built and installed module!) (WARNING! Diff between > built and installed module!) (WARNING! Diff between built and installed > module!) >nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed >nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed >nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed > ExtraDebuggingInterest: I just need to know a workaround > GraphicsCard: >Intel Corporation Alder Lake-P Integrated Graphics Controller > [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) > Subsystem: Razer USA Ltd. Device [1a58:201f] >NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA > controller]) > Subsystem: Razer USA Ltd. Device [1a58:201f] > InstallationDate: Installed on 2023-01-03 (62 days ago) > InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 > (20220809.1) > MachineType: Razer x Lambda TensorBook (2022) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic > root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro > button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/29/2022 > dmi.bios.release: 1.0 > dmi.bios.vendor: Razer >
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg
** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 + + Test 1: Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. + Test 2: + Install the ibus-libpinyin package. + Log out and log in again. + Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)" + to your input sources. + Log out + Click your name on the login screen. + Click the gear button to choose Ubuntu (on Wayland). + Enter your password to finish logging in. + Open Firefox (or Chromium) + Try to enter text in the address bar. + What Happens - No text is input + No text is inputted Other Info -- - This issue appears to only affects the Xorg session. + You see the issue as soon as IBus has been 'turned on'. With the current g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 session IBus is always turned on due to im-config 0.55-1. In a Wayland session you need to tell it to turn IBus on by either adding an IBus input method to your input sources or make use of the Screen Keyboard feature. And I've only seen the issue with the Firefox and Chromium snaps. + Warning message if you start firefox from terminal: + + [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could not + connect: Permission denied: 'glib warning', file + /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167 + + (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to + ibus: Could not connect: Permission denied + gnome-settings-daemon - - It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 + gnome-settings-daemon 44 Beta makes the situation worse since it always turns IBus on in both Wayland and X11, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. - - The issue happens with kinetic's gnome-settings-daemon 43; it just looks - like the gnome-settings-daemon commit made the situation worse but that - commit was reverted. ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
** Description changed: Test Case - + From Ubuntu 23.04, install glib >= 2.75.3-3 + Log out + Click your name on the login screen. + Click the gear button to choose Ubuntu on Xorg + Enter your password to finish logging in. + Open Firefox (or Chromium) + Try to enter text in the address bar. + What Happens + + No text is input - Original Bug Report - --- - While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. + Other Info + -- + This issue appears to only affects the Xorg session. - Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- + It also affected the Wayland session with gnome-settings-daemon 44 Beta, + but I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. - I was unable to reproduce the issue on Debian Testing but there may have - been differences in how snap was configured there. - - I'm filing this bug since ideally we would not be diverging from - upstream here. + The issue happens with kinetic's gnome-settings-daemon 43; it just looks + like the gnome-settings-daemon commit made the situation worse but that + commit was reverted. ** Description changed: Test Case - From Ubuntu 23.04, install glib >= 2.75.3-3 Log out Click your name on the login screen. Click the gear button to choose Ubuntu on Xorg Enter your password to finish logging in. Open Firefox (or Chromium) Try to enter text in the address bar. What Happens No text is input Other Info -- This issue appears to only affects the Xorg session. - It also affected the Wayland session with gnome-settings-daemon 44 Beta, - but I reverted https://gitlab.gnome.org/GNOME/gnome-settings- - daemon/-/commit/27bc0889c so that we could continue with the update. See - https://salsa.debian.org/gnome-team/gnome-settings- - daemon/-/commit/baeeed93 + And I've only seen the issue with the Firefox and Chromium snaps. + + gnome-settings-daemon + - + It also affected the Wayland session with gnome-settings-daemon 44 Beta, but I reverted https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. The issue happens with kinetic's gnome-settings-daemon 43; it just looks like the gnome-settings-daemon commit made the situation worse but that commit was reverted. ** Summary changed: - glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps + glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006070] Re: incredibly high memory usage
Ok, somewhat good news. I have been watching the memory usage on the machine as many applications start / stop , and am tracking the growth and management. A tool to tweak the behavior --- One system parameter I had tweaked before reporting this issue was vm.swappiness , I had moved this down to 30, mostly because I'd like to get the best performance, while avoiding the use of swap space. it had the intened effect, while using almost all available memory - generally a good thing (why have all this memory if you're not using it, right?). Now, i've moved this back up to 60 (which I believe is the default for the kernel options). In response I am seeing better free-memory management from the kernel. The downside is that I am absolutely seeing lower performance on and across web-pages and other applications as swap is used a bit more. The difference is measured in fractions of a second, I could measure the difference but I'm not sure if this audience would like to see those details (let me know if this is interesting). For those at home -- edit: /etc/sysctl.conf, modify or add the parameter 'vm.swappiness = 60' and then on your terminal run 'sysctl -p'. I mention this on this bug thread because this parameter directly effects the OOM killer behavior because the OOM killer appears to be swapiness un-aware, and this is also the underlying behavior modifier for the Chrome threads, and the Flatpak or gnome-software threads as they grow in size. I will continue to monitor for gnome-software threads and memory usage, but this means the heavier memory usage is effectively hidden by worse offenders (chrome likely being one of the heaviest users for us all). On Chrome -- Since Chrome is doing so much lately to manage their own threads, I hope this kerenel tuning parameter is kept in mind for memory management, it could save the team a lot of time building their own memory management utility/toolchain. There might even be some kind of alert / capability for the kernel to respond differently to certain applications depending on how aggressive they would like their own userspace managed. (Kerenel development feature!) One gnome-software -- I will keep tabs on the Flatpak memory usage. In the mean time I have disabled snapd entirely. I don't wish to manage my applications like this. Apt is about as far as I want to go now, the interactions of many different pakage managers adds a lot of complexity. I want to incentivize application develoeprs to use as few packaging systems as possible. It's getting quite bad out there - there's are now whole businesses that have sprung up to convert the same binaries into different packaging formats and their dependencies. It's really got to stop, it's such a waste of time and resources to 're-invent the wheel'. On the root cause -- I would much prefer that we encourage developers to build statically compiled binaries, rather than build containers upon containers to manage what I see as effectively a problem stemming from resource sharing linked to library (mis)management. I hope this is helpful to development here and across kernel development. I will continue to provide meaningful feedback as much as possible. -- 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/2006070 Title: incredibly high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/2006070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps
Gunnar, can you add a test case to the bug description? I don't know how to reproduce this issue with a new Ubuntu 23.04 install (using American English). By the way, the issue still exists with glib 2.75.4-1 (currently in Debian Experimental and not in Ubuntu yet). ** Description changed: - While preparing the gnome-settings-daemon 44 Beta update for Ubuntu - 23.04, I noticed that I could no longer enter text in the address bars - for the Chromium or Firefox snaps. + Test Case + - + + + Original Bug Report + --- + While preparing the gnome-settings-daemon 44 Beta update for Ubuntu 23.04, I noticed that I could no longer enter text in the address bars for the Chromium or Firefox snaps. Therefore, I reverted https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/commit/27bc0889c so that we could continue with the update. See https://salsa.debian.org/gnome-team/gnome-settings- daemon/-/commit/baeeed93 Before I did that, I tested disabling our patches but it didn't make a difference. I was unable to reproduce the issue on Debian Testing but there may have been differences in how snap was configured there. I'm filing this bug since ideally we would not be diverging from upstream here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2008279 Title: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008420] Re: '/usr/share/applications/default.list' content outdated
This bug was fixed in the package desktop-file-utils - 0.26-1ubuntu5 --- desktop-file-utils (0.26-1ubuntu5) lunar; urgency=medium * defaults.list: use the current .desktop for rhythmbox (lp: #2008420) -- Sebastien Bacher Mon, 06 Mar 2023 13:07:27 +0100 ** Changed in: desktop-file-utils (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2008420 Title: '/usr/share/applications/default.list' content outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2008420/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999884] Re: gdm-smartcard not passing successful authentication to desktop at system logon
The gdm3 update in jammy-proposed fixed the smartcard login issue for us. Thanks. -- 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/1999884 Title: gdm-smartcard not passing successful authentication to desktop at system logon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1999884/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007742] Re: Can't update stage views actor
Same issue w/ my system locking up for about 30 seconds to 1 minute each time it happens: Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e06fa94310] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e075f10b10] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e06fce46c0] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e07281faf0] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e072823850] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e07281e740] is on because it needs an allocation. Mar 07 10:04:21 jacob-hp-dev-one gnome-shell[7543]: Can't update stage views actor [:0x55e0728226d0] is on because it needs an allocation. My system is running Pop! OS 22.04 - it's not Ubuntu, but it is based on it and I figured this would be useful. jacob@jacob-hp-dev-one -- OS: Pop!_OS 22.04 LTS x86_64 Host: Dev One Notebook PC Kernel: 6.1.11-76060111-generic Uptime: 23 hours, 26 mins Packages: 2289 (dpkg), 16 (flatpak), 6 (snap) Shell: bash 5.1.16 Resolution: 1920x1080, 1920x1080 DE: GNOME 42.5 WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: AMD Ryzen 7 PRO 5850U with Radeon Graphics (16) @ 1.900GHz GPU: AMD ATI 03:00.0 Cezanne Memory: 17926MiB / 63630MiB -- 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/2007742 Title: Can't update stage views actor To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04
Which Ubuntu release, theme and variant are you using? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/2008791 Title: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008791] Re: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04
Despite affecting Nautilus from the user's perspective, on second thought I think the bug is in yaru-theme. ** 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2008791 Title: Disk properties in Gnome Files (Nautilus) shows a black chart for disk usage on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2008791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
I was unable to reproduce this behavior on an up-to-date 22.04 and on 22.10 (5.19.0-1009-raspi) with gnome-shell 43.0-1ubuntu2 running on a Pi4 device. Do you still experience the issue with the latest kernel image and firmware installed? Have you tried to reproduce the problem with a different monitor? ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Incomplete -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009592] Re: gjs-console crashed with SIGABRT
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1986455, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2009592/+attachment/5652398/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652400/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652403/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652404/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652405/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652406/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2009592/+attachment/5652407/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1986455 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2009592 Title: gjs-console crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2009592/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009435] Re: Xorg freeze
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu) ** Summary changed: - Xorg freeze + Nautilus freeze -- 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/2009435 Title: Nautilus freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2009435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000409] Re: totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included)
** Tags added: nvidia ** Summary changed: - totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included) + [nvidia] totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2000409 Title: [nvidia] totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/2000409/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009523] Re: totem crashes almost at every start
*** This bug is a duplicate of bug 2000409 *** https://bugs.launchpad.net/bugs/2000409 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2000409, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2000409 totem crashes on startup (assert !xcb_xlib_unknown_req_in_deq) in _XReply because XInitThreads is not called early enough by libx11 (patch included) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2009523 Title: totem crashes almost at every start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2009523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009564] Re: Touchpad disabling while typing does not work
I assume you mean: org.gnome.desktop.peripherals.touchpad disable-while-typing true Does it work any better if you log into Ubuntu on Xorg instead? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- 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/2009564 Title: Touchpad disabling while typing does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2009564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009435] [NEW] Xorg freeze
You have been subscribed to a public bug: Files application hangs when switched to from other application. Only occurs when mounted to internal HDD. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Mar 6 08:50:17 2023 DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367] InstallationDate: Installed on 2020-10-24 (862 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago) dmi.bios.date: 11/13/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze jammy ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/2009435 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009576] Re: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash)
*** This bug is a duplicate of bug 2008613 *** https://bugs.launchpad.net/bugs/2008613 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2008613, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2008613 gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370] -- 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/2009576 Title: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009564] [NEW] Touchpad disabling while typing does not work
You have been subscribed to a public bug: It makes my laptop much less usable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 00:44:08 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: backport-iwlwifi/9858, 5.19.0-32-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) backport-iwlwifi/9858, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) nvidia/525.85.05, 5.15.0-56-generic, x86_64: installed nvidia/525.85.05, 5.19.0-32-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] NVIDIA Corporation Device [10de:24e0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Device [1a58:201f] InstallationDate: Installed on 2023-01-03 (62 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Razer x Lambda TensorBook (2022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=4cd4fe61-a6ef-48c5-acc8-b96e7da91171 ro button.lid_init_state=open i915.enable_fbc=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: CH580 dmi.board.vendor: Razer x Lambda dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer x Lambda dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnRazer:bvr1.00:bd07/29/2022:br1.0:efr1.0:svnRazerxLambda:pnTensorBook(2022):pvr8.04:rvnRazerxLambda:rnCH580:rvr4:cvnRazerxLambda:ct10:cvr:skuRZ09-0421NEL9: dmi.product.family: 1A58201F Razer x Lambda TensorBook dmi.product.name: TensorBook (2022) dmi.product.sku: RZ09-0421NEL9 dmi.product.version: 8.04 dmi.sys.vendor: Razer x Lambda version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- Touchpad disabling while typing does not work https://bugs.launchpad.net/bugs/2009564 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009576] Re: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash)
** Description changed: - will add details when at real keyboard/mouse + Ubuntu lunar daily (LIVE) test on + - lenovo g560 (i5m-480, 4gb, i915) + + Most of session went well; then screen just went black, a white segment + (window trying to draw? as large rectangle) then report of crash... + + Reported against GNOME-SHELL due to .crash file in /var/crash. + + Attempts to `ubuntu-bug _usr_bin_gnom` failed due to 502 PROXY + ERROR & inability to login... message led me to believe report would be + https://launchpad.net/bugs/2009260 but that maybe wrong)... this was + filed later on same box.. + + ** Expected result + + No black screen followed by large white rectangle being drawn then crash + evidence on screen + + ** Notes + + I was having trouble with MOUSE operation on the device (esp clicks).. + so user-behavior (me) was likely involved (I usually use real mice!) + ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 08:51:50 2023 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230306) ProcEnviron: - LANG=C.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=C.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 43.2-6ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2009576 Title: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2009576] [NEW] ubuntu lunar live test; gnome shell c(rashed (according to /var/crash)
Public bug reported: will add details when at real keyboard/mouse ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 43.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.480 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 7 08:51:50 2023 DisplayManager: gdm3 LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230306) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 43.2-6ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2009576 Title: ubuntu lunar live test; gnome shell c(rashed (according to /var/crash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2009576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
