[Bug 1999501] [NEW] Login Loop
You have been subscribed to a public bug: As of Ubuntu 22.04 LTS, installing the ISO file on a virtual machine using VirtualBox 7.0.4 r154605 on Windows 10 version 21H2, the operating system gets stuck on the login page, even after inputing the correct password. Some specs of the machine in question: -- System Information -- Machine name: --- Machine Id: --- Operating System: Windows 10 Home 64-bit (10.0, Build 19044) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: ASUSTeK COMPUTER INC. System Model: ROG Zephyrus G15 GA503QR_GA503QR BIOS: GA503QR.413 (type: UEFI) Processor: AMD Ryzen 9 5900HS with Radeon Graphics (16 CPUs), ~3.3GHz Memory: 16384MB RAM Available OS Memory: 15776MB RAM Page File: 12722MB used, 7405MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Supported --- Display Devices --- Card name: AMD Radeon(TM) Graphics Manufacturer: Advanced Micro Devices, Inc. Chip type: AMD Radeon Graphics Processor (0x1638) Display Memory: 8384 MB Dedicated Memory: 496 MB Shared Memory: 7888 MB Current Mode: 2560 x 1440 (32 bit) (165Hz) Card name: NVIDIA GeForce RTX 3070 Laptop GPU Manufacturer: NVIDIA Chip type: NVIDIA GeForce RTX 3070 Laptop GPU Display Memory: 15921 MB Dedicated Memory: 8033 MB Shared Memory: 7888 MB The problem seems to be with the usage of both integrated GPU and dedicated GPU, as the problem persists when the integrated GPU is the one in usage. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 amd nvidia -- Login Loop https://bugs.launchpad.net/bugs/1999501 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999501] Re: Login Loop
** Package changed: linux (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1999501 Title: Login Loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1999501/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1982560] Re: Mouse lag/stutter (missed frames) in Wayland sessions
Hi Daniel, thanks! Currently testing these options. It would be helpful if others would do the same. -- 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/1982560 Title: Mouse lag/stutter (missed frames) in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1982560/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999207] [NEW] Error in dead key management of latin keyboards
You have been subscribed to a public bug: Composition events are incorrect in Ubuntu 22.04 for latin keyboard I opened an issue at Firefox [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1802989) that gives all the details, but they diagnosed a bug in ubuntu-ibus To reproduce the issue, you can go [here](https://developer.mozilla.org/en- US/docs/Web/API/Element/compositionstart_event#result) and type ^+u with a fr+latin9 keayboard configuration. Here is the conclusion on the bug report: Ubuntu-ibus commits dead key sequence with empty string first, then, sends only commit string without "composing" state. The latter behavior is a usual case for inputting non-ASCII characters like Emojis. In this case, browsers need to handle it without composition for compatibility between browsers. Therefore, we cannot represent the composed character insertion as a set of composition events. Anyway, dispatching 2 set of composition events for one dead key sequence may cause trouble in web apps. Therefore, as expected, the first composition should update the "preedit string" to the composed string and commit it simply. The bug was reproduced with installing Ubuntu 22.04 with English locale and adding "French (alt., Latin-9 only)" keyboard layout. And also reproduced with the other Western keyboard layouts which have dead keys. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: Incomplete -- Error in dead key management of latin keyboards https://bugs.launchpad.net/bugs/1999207 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999207] Re: Error in dead key management of latin keyboards
Good. Then let me try to explain the nature of the problem you encountered. It's not really an ibus issue. But GNOME integrates ibus into its desktop, and this is about the way they do so. ibus is started and configured by default in GNOME desktops. But for some reason they have an on/off mechanism for GTK, so for a user who does not have any ibus input methods enabled (and does not make use of the on-screen keyboard) ibus is turned "off" for GTK applications. By adding "Intelligent Pinyin" to your list of input sources you turned ibus "on" and it started to work as expected. Can't tell why you don't see the issue with Chrome. Maybe Chrome somehow ignores the GNOME on/off thing. At the release of Ubuntu 22.04 there was a related issue, which I reported upstream: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682 I mention that because Carlos Garnacho's reply includes a description of how the mechanism is thought to work. I can't help wondering how this relates to your app. In a previous comment you let me know that your "app relies on compositionend events". But if I understand it correctly, "compsitionend" is only used that way if ibus is running. Is your app an ibus app, but it fails to tell the system? Or is it a non-ibus app which still is relying on an ibus specific mechanism with respect to dead keys composing? Have you tried to run your app on a desktop where ibus is not present at all? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #682 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682 ** Package changed: ibus (Ubuntu) => gnome-settings-daemon (Ubuntu) -- 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/1999207 Title: Error in dead key management of latin keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999207] Re: Error in dead key management of latin keyboards
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #682 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/682 -- 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/1999207 Title: Error in dead key management of latin keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999207] Re: Error in dead key management of latin keyboards
My app is a React app. It contains an advanced text editor. To develop it we needed to catch the input events made on a contentEditable div to update an internal model. So we need to be aware about any change made to the editor. As the compositionend event is wrong, it generates a difference between our internal model and the current html of the page. I'm not sure about what you mean by an "ibus app". And how composition events are "ibus specific" mechanism? They are event documented in the HTML5 W3C standard : https://w3c.github.io/uievents/#interface- compositionevent Is there something I should do in my app that would enable the correct mechanism? I'm not sure neither about your last question. What would be a desktop where ibus is not present at all? -- 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/1999207 Title: Error in dead key management of latin keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999207] Re: Error in dead key management of latin keyboards
On 2022-12-20 21:39, Sharcoux wrote: > I'm not sure about what you mean by an "ibus app". And how > composition events are "ibus specific" mechanism? They are event > documented in the HTML5 W3C standard : > https://w3c.github.io/uievents/#interface-compositionevent I'm certainly not an expert on the topic. At this point I just observe. And when testing, using your test case ^+u, I only see the expected sequence of composition* events if ibus is up and running. Btw, you saw it yourself when it started to work for you on a GNOME desktop only when you had enabled an ibus input method. I should add that also Chrome requires ibus to generate the expected sequence of composition* events; on a desktop where ibus is not present (or completely disabled) you won't see the expected sequence. Maybe GTK itself isn't standards compliant in this respect. > Is there something I should do in my app that would enable the > correct mechanism? I don't know. In the upstream issue I mentioned, there are a couple of workarounds which might help. But that would just be a replacement for enabling an ibus input method. And in case of Wayland they would be poor workarounds with adverse side effects. > I'm not sure neither about your last question. What would be a > desktop where ibus is not present at all? Most non-Ubuntu desktops, actually. :) One example is Xubuntu, which I used when testing. Another option is to simply uninstall ibus on your Ubuntu desktop. -- 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/1999207 Title: Error in dead key management of latin keyboards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1999207/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000185] [NEW] Nautilus crashes when returning to search results from a directory
Public bug reported: I cannot figure out how to capture the crash. Launching nautilus from terminal does not give any crash logs when it happens and it is very easily reproduced and extremely annoying. To reproduce it yourself, perform the following: 1. Launch nautilus and click on the 'other locations' tab. 2. Select any drive, partition, filesystem, whatever you have there. For the sake of continuity, just select whatever drive Ubuntu is installed on. 3. Type in a search query. It doesn't matter what it is, but it has to return a directory in the results that you can then enter. For example, type 'pictures' into the search to return your pictures folder. 4. Enter any of the directories that show up in the search results. From here, it doesn't matter what you do. As soon as you press back to return to the search results, nautilus will ALWAYS crash. This obviously makes searching for things like application files, where many directories will have the same name, extremely difficult and cumbersome. I can reproduce this crash 100% of the time. This is on Ubuntu 22.10 with nautilus 1:43.0-1ubuntu1. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7 Uname: Linux 5.19.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Dec 20 20:21:26 2022 InstallationDate: Installed on 2022-07-09 (164 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-21 (60 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-megasync 5.1.0-1.1 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic nautilus -- 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/2000185 Title: Nautilus crashes when returning to search results from a directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2000185/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999098] Autopkgtest regression report (glib2.0/2.74.3-0ubuntu1)
All autopkgtests for the newly accepted glib2.0 (2.74.3-0ubuntu1) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: git-evtag/2016.1-2build1 (s390x, arm64, ppc64el) cluster-glue/1.0.12-21ubuntu1 (s390x) snapd-glib/1.63-0ubuntu1 (armhf) gvfs/1.50.2-2 (amd64, ppc64el) netplan.io/unknown (arm64) gtk4/4.8.1+ds-1ubuntu1 (armhf) systemd/unknown (arm64) mutter/43.0-1ubuntu4 (armhf, arm64) netplan.io/0.105-0ubuntu2 (s390x) openmsx-catapult/18.0-1 (armhf) cpdb-libs/1.2.0-0ubuntu8 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/kinetic/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1999098 Title: Update glib to 2.74.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993244] Re: weird default applications behaviour
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993244 Title: weird default applications behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
