[Desktop-packages] [Bug 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
In Jammy Jellyfish (Thunderbird 91.5.0, GNOME Shell 40.5) when this bug occurs it also cause the Thunderbird window to not display at all. The application dock shows that it is open, but there is no way to get to it unless you right click the dock icon and open a new window. Sharing here as I believe it is related. Hopefully the fix committed will take care of this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950918] Re: [regression] gnome crashed by mpv media player
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1950918 Title: [regression] gnome crashed by mpv media player Status in gnome-shell package in Ubuntu: Expired Bug description: gnome will freeze (stop updating the display) This is a regression, because it was working a for the past year up until a few days ago. I'll remove mpv media player and go back to VLC (which I stopped using due to 10bit color issues) tail /var/log/apt/history.log -n 21 Start-Date: 2021-11-12 09:04:56 Commandline: /usr/bin/unattended-upgrade Upgrade: libtalloc2:amd64 (2.3.0-3ubuntu1, 2.3.1-0ubuntu0.20.04.1), python3-talloc:amd64 (2.3.0-3ubuntu1, 2.3.1-0ubuntu0.20.04.1) End-Date: 2021-11-12 09:04:56 Start-Date: 2021-11-12 09:04:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libtdb1:amd64 (1.4.2-3build1, 1.4.3-0ubuntu0.20.04.1) End-Date: 2021-11-12 09:04:59 Start-Date: 2021-11-12 09:05:02 Commandline: /usr/bin/unattended-upgrade Install: python3-ldb:amd64 (2:2.2.3-0ubuntu0.20.04.2, automatic) Upgrade: libldb2:amd64 (2:2.0.10-0ubuntu0.20.04.3, 2:2.2.3-0ubuntu0.20.04.2), libwbclient0:amd64 (2:4.11.6+dfsg-0ubuntu1.10, 2:4.13.14+dfsg-0ubuntu0.20.04.1), samba-libs:amd64 (2:4.11.6+dfsg-0ubuntu1.10, 2:4.13.14+dfsg-0ubuntu0.20.04.1), libsmbclient:amd64 (2:4.11.6+dfsg-0ubuntu1.10, 2:4.13.14+dfsg-0ubuntu0.20.04.1), libtevent0:amd64 (0.10.1-4, 0.10.2-0ubuntu0.20.04.1) End-Date: 2021-11-12 09:05:05 Start-Date: 2021-11-13 06:39:01 Commandline: /usr/bin/unattended-upgrade Upgrade: libpq5:amd64 (12.8-0ubuntu0.20.04.1, 12.9-0ubuntu0.20.04.1) End-Date: 2021-11-13 06:39:02 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 13 18:02:44 2021 InstallationDate: Installed on 2020-11-13 (365 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-13 (367 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.10.0-1051.53-oem 5.10.76 RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1 Tags: focal wayland-session Uname: Linux 5.10.0-1051-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922715] Re: [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all (dummy output)
Has exactly the same model (Dell Inspiron 24 5000 All-in-one, aka Inspiron 5400 All-in-one). Also "aplay -l" showed the card is "ALC274 Analog". Finally got the sound working in Ubuntu 20.04, by appending the following line 횘횙횝횒횘횗횜 횜횗획-횑획횊-횒횗횝횎횕 횖횘획횎횕=획횎횕횕-횑횎횊획횜횎횝-횖횞횕횝횒 in /etc/modprobe.d/alsa.conf. After reboot, the sound at both speaker and microphone worked. Various articles mentioned this. One such reference is: https://bbs.archlinux.org/viewtopic.php?id=234965 A big thank you to the community! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1922715 Title: [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all (dummy output) Status in pulseaudio package in Ubuntu: New Bug description: Brand new PC (it is a descktop All-In-One with integrated speakers), no change to the bios, fresh install with no additional package. In the "sound" section of the parameters, the output menu has a single entry "dummy output" and the vu-meter below this menu tracks the input microphone, which works. (the UI is in Russian, it's a friend's PC, sorry if the English terms are not exactly right). Same with pavucontrol. Same on ubuntu 20.04 and 20.10. I first searched the internets and randomly tried the following additions to /etc/modprobe.d/alsa-base.conf (one by one), none of them worked options snd-hda-intel model=generic options snd-hda-intel model=alc274-dell-aio options snd-hda-intel model=auto options snd-hda-intel dmic_detect=0 options snd-hda-intel index=2 # tested 0, 1, 2 and 8 -- wish I new what it means options snd-intel-dspcfg.dsp_drivers=1 I was delighted to hear that Apport could play noise on this machine because before that I didn't get a click, I was wondering if the HW was working. That's all. Bug reports are love letters. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 908 F pulseaudio /dev/snd/pcmC0D0c: anton 908 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 12:55:41 2021 InstallationDate: Installed on 2021-04-02 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 908 F pulseaudio /dev/snd/pcmC0D0c: anton 908 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2020 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.0 dmi.board.name: 0H1TR9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.0:bd09/04/2020:br1.1:svnDellInc.:pnInspiron5400AIO:pvr:rvnDellInc.:rn0H1TR9:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5400 AIO dmi.product.sku: 0A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922715/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956838] Re: drag and drop broken chromium snap
See also https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1956888/comments/10 for downgrading instructions and possible upstream bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71 Chromium will not drag and drop selected text onto any any application including Chromium. In a virtual machine, I was able to revert the Chromium snap to version 96.0.4664.110 and drag and drop works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
I think the relevant bug report is: https://bugs.chromium.org/p/chromium/issues/detail?id=1279532 It causes havoc with Tab moving, and broken sortable lists (like the bookmarks), and with pasting stuff to the wrong (X11) window. (See my previous comment.) Downgrading to a previous version (1854) should be a matter of: # snap list chromium --all # snap revert chromium --revision 1854 Maybe allow more historic snap packages than 2 in the future: # snap set system refresh.retain=4 And if you've lost the 1854 snap for amd64, I have it here: https://junk.devs.nu/2022/bugs/chromium_96.0.4664.110_snap_1854_amd64.snap sha512sum c636cd18798f0bb98138ec6aafa85b1ae460f415dfca5973d38cc3a70f0eb2b02629eaedf2b10acb561267bcdf73eb7f575c431d0ef56b5f350da855956c50b1 # snap install ./chromium_96.0.4664.110_snap_1854_amd64.snap --dangerous (I think --dangerous is needed, but possibly not if you already had 1854 running before.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956647] Re: CUPS TAKE LONG TIME TO PRINT (CTRL+P)
** Package changed: ubuntu-release-upgrader (Ubuntu) => cups (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1956647 Title: CUPS TAKE LONG TIME TO PRINT (CTRL+P) Status in cups package in Ubuntu: New Bug description: CUPS TAKE LONG TIME TO PRINT IN UBUNTU UBUNTU 20.04.3 BUT IN UBUNTU 20.04.1 IS NORMAL. IN LIBRE TAKE A 5-7 SECOND TO SHOW THE PRINT WINDOW, IN WPS IS TAKE 7-10 SECOND TO POPUP PRINT WINDOW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 [origin: unknown] ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 10:02:15 2022 InstallationDate: Installed on 2021-09-22 (106 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-09-22T12:06:48.046711 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1956647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956647] [NEW] CUPS TAKE LONG TIME TO PRINT (CTRL+P)
You have been subscribed to a public bug: CUPS TAKE LONG TIME TO PRINT IN UBUNTU UBUNTU 20.04.3 BUT IN UBUNTU 20.04.1 IS NORMAL. IN LIBRE TAKE A 5-7 SECOND TO SHOW THE PRINT WINDOW, IN WPS IS TAKE 7-10 SECOND TO POPUP PRINT WINDOW ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.36 [origin: unknown] ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 10:02:15 2022 InstallationDate: Installed on 2021-09-22 (106 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2021-09-22T12:06:48.046711 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages -- CUPS TAKE LONG TIME TO PRINT (CTRL+P) https://bugs.launchpad.net/bugs/1956647 You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957944] [NEW] CSD do not distinguish focused and unfocused FF windows
Public bug reported: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-06-18 (941 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profile2Extensions: extensions.sqlite corrupt or missing Profile2IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile2Locales: extensions.sqlite corrupt or missing Profile2PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile2PrefSources: prefs.js Profile2Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=96.0/20220106144528 (In use) Profile0 (Default) - LastVersion=96.0/20220106144528 (In use) Profile2 - LastVersion=71.0/20191205203726 (Out of date) RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to impish on 2021-10-31 (75 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "ff-csd-focus-bug.png" https://bugs.launchpad.net/bugs/1957944/+attachment/5554362/+files/ff-csd-focus-bug.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1957944 Title: CSD do not distinguish focused and unfocused FF windows Status in firefox package in Ubuntu: New Bug description: After the FF 96 upgrade I can't distinguish focused and unfocused FF windows from their client side decorations. Previously the distinction was subtle, but not impossible. The attached image shows two windows, the one on the left has focus. The only way you can tell this is that the scrollbar is faded in the unfocused window. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 96.0+build2-0ubuntu0.21.10.1 Uname: Linux 5.14.0-051400-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BuildID: 20220106144528 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 14 13:15:27 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales:
[Desktop-packages] [Bug 1949605] Re: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS
Debian now have 91.5.0-2 in sid and seem to have long since sorted the portability/architecture issues. @osomon -- Please let us all have a test-package for Ubuntu update testing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1949605 Title: Backport Thunderbird 91 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: In Progress Status in thunderbird source package in Focal: In Progress Status in thunderbird source package in Hirsute: In Progress Bug description: Similarly to bug #1895643, which was about upgrading thunderbird from 68 to 78 in all supported Ubuntu releases, this bug is to track the update from thunderbird 78 to 91 in hirsute, focal and bionic. The rationale is that series 78 will soon be out of support (the last release, 78.14.0, was made public on September 7, 2021). Thunderbird follows the Firefox ESR release cycle, and the next/current series is 91 (already available in impish and jammy). User-facing announcement: https://discourse.ubuntu.com/t/thunderbird- lts-update-78-to-91/25391. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1949605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
Is this related to https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1956838/comments/4 perhaps? That bug reared its head for me when I was using a drag-drop widget in a website. If it is, it is even uglier than you think. > As a workaround, it's too bad we can't restore a bugfree version of chromium. I've been pulling my hair out trying to find/download a working 1854 version, but that one got dropped when I tried beta/edge. Not a happy camper. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956838] Re: drag and drop broken chromium snap
I'm really unhappy with this, because it appears to paste text into the window below it: https://junk.devs.nu/2022/bugs/chromium_98.0.4758.9_snap_pastes_in_gedit.mp4 """This is a video with two gedit windows side by side, and this bug report on top. When dragging and dropping text INSIDE the browser, it gets copied to a different windows BEHIND it.""" https://junk.devs.nu/2022/bugs/chromium_97.0.4692.71_snap_pastes_in_shell.mp4 """This is a similar video, this time pasting text in a shell, back when I did not know that the mouse position of release was relevant. Unintentionally pasting text into a shell is not cool.""" Observed with chromium 97.0.4692.71 and 98.0.4758.9 on Ubuntu Focal. I could not revert to the older version 1854 because snap had already removed it. Walter Doekes OSSO B.V. P.S. This commit looks related: commit 0d6d861a1f39380238f4163f1325f5802792d4d5 author Joel HockeyWed Nov 17 20:27:34 2021 committer Chromium LUCI CQ Wed Nov 17 20:27:34 2021 [Merge to M97] Ignore X DragWidget when doing drag-drop image Chrome has only recently supported image drag-drop between tabs, and this has revealed a bug in the X drag-drop code. When doing the drop drop, a DragWidget (semi-transparent version of image being dragged) is created. Since this image is under the cursor, it was incorrectly chosen when XDragDropClient::ProcessMouseMove() calls XTopmostWindowFinder::FindWindowAt(). The fix is to allow finder to take a set of windows to ignore, similar to what is already done for FindLocalProcessWindowAt(). The X11TopmostWindowFinder constructor now takes the ignore-set which applies to both Find* functions. Because, if it ignores its own window, then the dropped text may land in a window below it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956838 Title: drag and drop broken chromium snap Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the latest Chromium refresh on 2020-01-07 to version 97.0.4692.71 Chromium will not drag and drop selected text onto any any application including Chromium. In a virtual machine, I was able to revert the Chromium snap to version 96.0.4664.110 and drag and drop works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
Also because Wayland allows the television to be at 60Hz, whenever I login (after boot) and have it in mirror mode, the sound is therefore too fast by default. I cannot change it, since the HDMI port is the first port on the GPU and the DisplayPort port is the second. This means it by default assumes the television to be the default display. Of course this would not be an issue if the sound just worked. But right now it would also be nice to be able to change the primary display when mirroring screens. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in xorg package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1957816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using xkb-options for switching input sources not reflected by the input source indicator in a wayland session
I tested some more, and the issue seems to be more complex than I indicated in comment #14. Some XKB shortcuts for switching input source work in both Wayland and Xorg. Examples are: i.e. if you define a single modifier key for the purpose it works. + is a problem on wayland at least, and when I tested in a VM it failed to work on Xorg too. Also + is problematic (on Wayland). ** Summary changed: - Using xkb-options for switching input sources not reflected by the input source indicator in a wayland session + Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using certain xkb-options, e.g. Alt+Shift, for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: New Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957909] [NEW] NetworkManager connectivity check fails
Public bug reported: I randomly receive "No internet connection available" notification, even if my internet connection is stable. (Not the exact term) In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint http://connectivity-check.ubuntu.com./ is used. I manually pinged the endpoint. I live in europe and the server is located in the US. The latency is about 160ms. Usually I have an approximate latency of 15ms. It is not a problem of my ISP, I receive this notification on different locations in Germany and Switzerland. I propose to use another endpoint or provide another server for the same endpoint for europe. So the DNS servers in europe provide the IP of a server located in europe. The config comes from the package "network-manager-config-connectivity- ubuntu" version 1.32.12-0ubuntu1. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1957909 Title: NetworkManager connectivity check fails Status in network-manager package in Ubuntu: New Bug description: I randomly receive "No internet connection available" notification, even if my internet connection is stable. (Not the exact term) In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint http://connectivity-check.ubuntu.com./ is used. I manually pinged the endpoint. I live in europe and the server is located in the US. The latency is about 160ms. Usually I have an approximate latency of 15ms. It is not a problem of my ISP, I receive this notification on different locations in Germany and Switzerland. I propose to use another endpoint or provide another server for the same endpoint for europe. So the DNS servers in europe provide the IP of a server located in europe. The config comes from the package "network-manager-config- connectivity-ubuntu" version 1.32.12-0ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957816] Re: Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed
** Summary changed: - Wayland dual monitor 60Hz: High pitch audio + Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed ** Summary changed: - Wayland dual monitor from 30Hz to 60Hz: High pitch audio double playback speed + Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1957816 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in xorg package in Ubuntu: New Bug description: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1957816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957819] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed
** Summary changed: - Wayland dual monitor 60Hz: High pitch audio and fast playback + Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1957819 Title: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed Status in alsa-driver package in Ubuntu: New Bug description: I described the issue here first: https://bugs.launchpad.net/ubuntu/+bug/1957816 I am not sure it belongs here, but after the initial report i made an audio issue report with `ubuntu-bug -s audio` copy/paste: I have a desktop computer with a 60Hz 4K display connected through Display Port. The display is a ThinkVision X1 with built in audio. With the Display Port cable I am then able to output sound from the monitor and this works without any issues. I have now added a 4K Samsung television through HDMI to the same GPU, which also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear however, that when it is set to 60Hz in Wayland, the animation on the television is much more smooth. The problem is that whenever I set the television to 60Hz, the playback of any sound is both high pitched and faster than normal. If I play a video in YouTube, the video appears to playback about twice as fast as normal and and very high pitched sound (everyone sounds like chipmunks). This is the case on the entire system (also when playing the video or any other sounds on the X1 display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz again does everything play and sound normal again. It is only the playback of media that is doubled in speed. Everything else (animations, mouse, etc.) is still behaving as normal. If I change audio output to the ThinkVision X1 (or something else) at 60Hz while also being connected to the television at 60Hz, the audio stays high pitched and sped up. If I unplug the main display, ThinkVision X1, then the playback of media on the television becomes normal. I have tried with different +100 USD HDMI cables, that are all rated as HDMI 2.0 and the behavior stays the same. My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the behavior was the same. I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI). As mentioned I cannot test it in Xorg, but that is only because it does not allow me to set the refresh rate to 60Hz. I am uncertain whether this is related to MESA, Pulseaudio or maybe Mutter/Wayland? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 13 17:24:02 2022 InstallationDate: Installed on 2020-05-03 (620 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful Symptom_Card: Vega 20 HDMI Audio [Radeon VII] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8101 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8101:bd07/15/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx: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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1957819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
** Also affects: pulseeffects (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
Changing this to d-conf because its downgrade helps to eliminate the issue ** Package changed: pulseeffects (Ubuntu) => d-conf (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: New Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948882] [NEW] PulseEffects does not properly initialize on startup
You have been subscribed to a public bug: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) ** Affects: d-conf (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish third-party-packages -- PulseEffects does not properly initialize on startup https://bugs.launchpad.net/bugs/1948882 You received this bug notification because you are a member of Desktop Packages, which is subscribed to d-conf in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956916] Re: Using xkb-options for switching input sources not reflected by the input source indicator in a wayland session
** Summary changed: - [22.04] Unable to set Left Alt + Left Shift key combination to switch keyboard layouts + Using xkb-options for switching input sources not reflected by the input source indicator in a wayland session ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => New ** Tags removed: ubiquity-22.04.3 ** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956916 Title: Using xkb-options for switching input sources not reflected by the input source indicator in a wayland session Status in gnome-control-center package in Ubuntu: New Bug description: Currently, there is no way to define Left Alt + Left Shift key combination to change keyboard layouts in Ubuntu 22.04. In previous versions there was a convenient "Keyboard Layout Options" window in which there was able to set required key combination. Since 22.04 release I can't find a way to do that because useless "Keyboard Shortcuts" window opens instead in which unable to set Left Alt + Left Shift as "Switch to the next source" shortcut. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211230) NonfreeKernelModules: nvidia_modeset nvidia Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: jammy wayland-session ubiquity-22.04.3 Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup impish on 201606-22459 in cert pool. Then doing same test as #3, test result is positive. GPU will keep in nvidia mode, and glxinfo works normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Impish: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957890] [NEW] Lockscreen animation glitch
Public bug reported: >From today I'm facing lockscreen animation glitch. When I enter users password and hit Enter, lockscreen animation stay 0.5 sec on half a screen. Description:Ubuntu 20.04.3 LTS Release:20.04 gnome-shell: Installed: 41.1-1~devacom Candidate: 41.1-1~devacom Version table: *** 41.1-1~devacom 500 500 http://ppa.launchpad.net/devacom/gnome-41/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 40.5-1ubuntu1 500 500 http://ppa.launchpad.net/devacom/gnome-40/ubuntu focal/main amd64 Packages 3.36.9-0ubuntu0.20.04.2 500 500 http://rs.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.4-1ubuntu1~20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://rs.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: glitch lockscreen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1957890 Title: Lockscreen animation glitch Status in gnome-shell package in Ubuntu: New Bug description: From today I'm facing lockscreen animation glitch. When I enter users password and hit Enter, lockscreen animation stay 0.5 sec on half a screen. Description: Ubuntu 20.04.3 LTS Release: 20.04 gnome-shell: Installed: 41.1-1~devacom Candidate: 41.1-1~devacom Version table: *** 41.1-1~devacom 500 500 http://ppa.launchpad.net/devacom/gnome-41/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 40.5-1ubuntu1 500 500 http://ppa.launchpad.net/devacom/gnome-40/ubuntu focal/main amd64 Packages 3.36.9-0ubuntu0.20.04.2 500 500 http://rs.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.4-1ubuntu1~20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://rs.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1957890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
Fedora here, but same keyboard and 100% same issue! Let's see if Osvald Lindholms fix fixes this too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
