[Desktop-packages] [Bug 1981163] Re: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
Error message when launching a pdf from attached files in Compose window, on a computer where Firefox is removed (replaced by Librewolf as default browser), instead of opening it with Evince. ** Attachment added: "TB-Evince.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+attachment/5602324/+files/TB-Evince.png -- 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/1981163 Title: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in thunderbird package in Ubuntu: New Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+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 1981186] [NEW] Thunderbird 102 : keeps an empty window even if all calendar alarms closed
Public bug reported: Since Thunderbird 102 (deb version on Ubuntu 22.10), a new bug appeared on calendar : when a window opens with many alarm reminders, after having reported or closed all of them, it remains an empty window with "0 reminder" title, instead of closing the floating window as before. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Attachment added: "TB-102.png" https://bugs.launchpad.net/bugs/1981186/+attachment/5602323/+files/TB-102.png -- 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/1981186 Title: Thunderbird 102 : keeps an empty window even if all calendar alarms closed Status in thunderbird package in Ubuntu: New Bug description: Since Thunderbird 102 (deb version on Ubuntu 22.10), a new bug appeared on calendar : when a window opens with many alarm reminders, after having reported or closed all of them, it remains an empty window with "0 reminder" title, instead of closing the floating window as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981186/+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 1370953] Re: layout switch is delayed
** Tags added: jammy ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in GNOME Shell: Unknown Status in console-setup package in Ubuntu: Incomplete Status in gconf package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1370953/+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 1370953] Re: layout switch is delayed
Yes, this bug is still present in 22.04, the reason and workaround described here https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/1154#note_1065418 ** Patch added: "keyboard-layout-switching-delay-workaround.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+attachment/5602294/+files/keyboard-layout-switching-delay-workaround.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in GNOME Shell: Unknown Status in console-setup package in Ubuntu: Incomplete Status in gconf package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1370953/+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 1370953] Re: layout switch is delayed
Is anyone still experiencing this bug in 22.04? ** Changed in: console-setup (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gconf (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in GNOME Shell: Unknown Status in console-setup package in Ubuntu: Incomplete Status in gconf package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1370953/+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 1370953] Re: layout switch is delayed
** Tags removed: 14.04 ** Tags added: bionic focal ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1154 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1154 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1154 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in GNOME Shell: Unknown Status in console-setup package in Ubuntu: Incomplete Status in gconf package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1370953/+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 1370953] Re: layout switch is delayed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in GNOME Shell: Unknown Status in console-setup package in Ubuntu: Incomplete Status in gconf package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1370953/+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 1754702] Re: Delay before you can type after switching input source
*** This bug is a duplicate of bug 1370953 *** https://bugs.launchpad.net/bugs/1370953 ** This bug has been marked a duplicate of bug 1370953 layout switch is delayed -- 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/1754702 Title: Delay before you can type after switching input source Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: In ubuntu 18.04 I installed different keyboard languages: spanish latin american, japanese, japanese-ibus. To change the input method you press the selected key, and an indicator menu appears on-screen to indicate which language is selected next. The menu disapears after 2~3 seconds and during which time typing is blocked. If you type while the language input method menu is displayed, the menu will not disapear and stay as long as you type. The language input menu should not block typing, and the disapearance of the menu should not be delayed by typing. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1754702/+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 1877289] Re: switch of language freezes keyboard
*** This bug is a duplicate of bug 1370953 *** https://bugs.launchpad.net/bugs/1370953 ** This bug is no longer a duplicate of bug 1754702 Delay before you can type after switching input source ** This bug has been marked a duplicate of bug 1370953 layout switch is delayed -- 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/1877289 Title: switch of language freezes keyboard Status in gnome-shell package in Ubuntu: New Bug description: Hi there. In my ubuntu 20.04 i have two input sources (en and ru) installed and switching between them via super+space is successful but freezes keyboard for about 2 seconds whatever editor i'm focused in. It happens not always, bu, say, in > 50% of input switches. The only thing i could distinguish it happens when i swith to english. BTW, english is a system language as well. It never happens in ubuntu 19.04 and previous versions as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 7 13:49:37 2020 PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877289/+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 1799840] Re: Input does not work for half a second while switching keyboard language
*** This bug is a duplicate of bug 1370953 *** https://bugs.launchpad.net/bugs/1370953 ** This bug is no longer a duplicate of bug 1754702 Delay before you can type after switching input source ** This bug has been marked a duplicate of bug 1370953 layout switch is delayed -- 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/1799840 Title: Input does not work for half a second while switching keyboard language Status in gnome-shell package in Ubuntu: New Bug description: After switching keyboard language by pressing Meta+Space, keyboard input stops to work for a time interval like 0.5 sec. That is when I press Meta+Space and directly after then type some letters, the input does not work like half of a second. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 02:29:32 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-06-23 (123 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-10-20 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799840/+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 1977790] Re: Window could be glitched with Intel + NVIDIA GPU laptops, and prime-select set to intel
** Changed in: oem-priority Importance: Undecided => High -- 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/1977790 Title: Window could be glitched with Intel + NVIDIA GPU laptops, and prime- select set to intel Status in OEM Priority Project: New Status in firefox package in Ubuntu: New Bug description: [Summary] Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel. Either setting gfx.x11-egl-force-disabled to true in about:config, or setting prime-select to on-demand or nvidia, makes the issue unreproducible. Note that through nvidia-settings GUI, prime-select cannot be set to intel. Reproducibility: 1/8 [Reproduce Steps] 1. Run `sudo prime-select intel` in Terminal then reboot 2. Open Firefox window 3. Close Firefox window 4. Repeat until window is glitched (usually Firefox being transparent except the borders of the window) [Results] Expected: Firefox should not have its window glitched Actual: Firefox is glitched with window being transparent but the border, and every window on top of it draws on the Firefox window. Video attached. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1753 F pulseaudio BuildID: 20220330194208 CasperMD5CheckResult: skip Channel: Unavailable DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215 DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-05-25 (12 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IpRoute: default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 metric 600 10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 metric 100 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 NoProfiles: True NonfreeKernelModules: nvidia_modeset nvidia Package: firefox 99.0+build2-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.14.0-1034-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/16/2022 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: RAID dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1: dmi.product.family: Precision dmi.product.name: Precision 3470 dmi.product.sku: 0BC1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977790/+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 1972884] Re: Err:10 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu jammy Release 404 Not Found [IP: 91.189.95.85 443]
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1972884 Title: Err:10 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu jammy Release 404 Not Found [IP: 91.189.95.85 443] Status in software-properties package in Ubuntu: Expired Bug description: Err:10 https://ppa.launchpadcontent.net/flatpak/stable/ubuntu jammy Release 404 Not Found [IP: 91.189.95.85 443] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1972884/+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 1973014] Re: gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or session change
[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/1973014 Title: gnome-shell crashes with SIGSEGV in libgbm.so.1.0.0 on resume or session change Status in gnome-shell package in Ubuntu: Expired Bug description: Trying to change session with ctrl-alt f1 or suspend-resume the computer systematically leads to a crash on my system : -First i can see the screen, but mouse an keyboard are not responsive. -Then many visual artifacts appear on my secondary monitor. -Then i get a new login prompt. After that in dmesg i can see errors such as : [ 6574.079637] gnome-shell[5525]: segfault at 55713299a720 ip 7f7c0af012e7 sp 7ffc8932bdb8 error 4 in libgbm.so.1.0.0[7f7c0af0+8000] [ 6574.079660] Code: 18 c3 90 f3 0f 1e fa 48 8b 07 ff a0 c0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 a8 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 a0 b0 00 00 00 0f 1f 00 f3 0f 1e fa 48 8b 07 ff a0 b8 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30 Uname: Linux 5.15.0-27-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 11 15:05:07 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-23 (1114 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-05-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973014/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
The libva library is the same as me. >>snap: vainfo: VA-API version: 1.14 (libva 2.6.0) The old libva impacted my hardware configeration. It is not correct in fact. I expect the depended libva could be solved so my hardware could use this snap packages. expected: snap: vainfo: VA-API version: 1.14 (libva 2.14.0) Thanks. -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the snap with sudo snap install --channel candidate/hwacc chromium 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples 4. Enter about:media-internals in the address bar and note what the page says for kVideoDecoderName. Please report - The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder; - If failed, the video used for testing, including codec and resolution if possible; - Distro version (if in doubt, `grep VERSION= /etc/os_release`); - GPU (if in doubt, attach the output of `lscpu`); - CPU generation (if in doubt, attach the output of `lscpu`). About the last point, it may be that unfortunately only those with newer generations of Intel CPUs will have luck with this, but it's still an uncertainty. So reports are highly welcome. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1981163] [NEW] In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince
Public bug reported: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- 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/1981163 Title: In Compose window, if a PDf is joined and clicked to open, Thunderbird launches Firefox instead of Evince Status in thunderbird package in Ubuntu: New Bug description: In Thunderbird on Ubuntu Gnome, I set Evince as default program to open pdf files from Thunderbird. In received messages, and those saved on "Sent" folder, it works perfectly. But in the "Compose" window: if I add a pdf file to the message, and double-click on it to open and verify it, Thunderbird always uses Firefox to show it. In case Firefox is not installed (has been removed), I have an error message telling there is not associated application for pdf files and to go to Preferences - where Evince is already and still defined as default. It happens since many months and bug is still present in Thunderbird 102 / Ubuntu 22.10 beta. It's not the same as bug 234349 as here, it's not an URL file but directly a pdf joined in a mail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1981163/+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 1968622] Re: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1968622 Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. Status in pulseaudio package in Ubuntu: Confirmed Bug description: Audio only had "Dummy output" as output but after running: $ echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf audio output changed to HDMI/Built-in-Audio however the sound is still not working sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 22:58:11 2022 InstallationDate: Installed on 2022-03-23 (19 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 2.19 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.19 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.19 dmi.modalias: dmi:bvnHUAWEI:bvr2.19:bd12/09/2021:br2.19:efr2.19:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968622/+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 1968622] Re: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card.
Very same issue here with Product Name: NBD-WXX9-PCB-B3 on Ubuntu 22.04 , only "Dummy Output" audio output availlable -- 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/1968622 Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. Status in pulseaudio package in Ubuntu: Confirmed Bug description: Audio only had "Dummy output" as output but after running: $ echo "options snd-hda-intel model=generic" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "options snd-hda-intel dmic_detect=0" | sudo tee -a /etc/modprobe.d/alsa-base.conf $ echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf audio output changed to HDMI/Built-in-Audio however the sound is still not working sound ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 11 22:58:11 2022 InstallationDate: Installed on 2022-03-23 (19 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) SourcePackage: pulseaudio Symptom: audio Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Digital Out, HDMI Title: [NBD-WXX9, Intel Tigerlake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2021 dmi.bios.release: 2.19 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.19 dmi.board.asset.tag: N/A dmi.board.name: NBD-WXX9-PCB-B4 dmi.board.vendor: HUAWEI dmi.board.version: M1010 dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1010 dmi.ec.firmware.release: 2.19 dmi.modalias: dmi:bvnHUAWEI:bvr2.19:bd12/09/2021:br2.19:efr2.19:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100: dmi.product.family: MateBook D dmi.product.name: NBD-WXX9 dmi.product.sku: C100 dmi.product.version: M1010 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1968622/+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 1748895]
Created attachment 181206 revision of (current) senddoc to correct problems Revisions labelled #001 enable sending email when Tools-Options- Internet-Email is set to /usr/bin/xdg-email (under Ubuntu 20.04 LTS) The revision labelled #002 enable sending document as email when Option- Email is blank - in this case LO currently does NOT supply any MAILER to senddoc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: New Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1748895]
Against Timurs comment #29, "(3) I asked you to clarify, to have all here, but that would be another issue anyway.", - the Browse button doesn't really help the user (it listes all files in the HOME directory - and though the user might want to enter a simple application name (and perhaps should be given a list of found names to choose from), past experience suggested that a full path may be desirable. - the button might be better to validate an entered application name? The user can't be assumed to know the file system! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1748895 Title: LO unable to find a working email configuration Status in LibreOffice: New Status in libreoffice package in Ubuntu: Fix Released Bug description: Installed from PPA: ppa:libreoffice/ppa $ lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ apt-cache policy libreoffice libreoffice: Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 Version table: *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 1:5.1.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages WHAT YOU EXPECT TO HAPPEN: Should spawn an new Evolution eMAIL with attached ODF document WHAT HAPPENED INSTEAD: Error Dialogue: LibreOffice is unable to find a working email configuration. Please save your document locally and attached from within your eMAIL client. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1748895/+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 1803604]
Against Timurs comment #29, "(3) I asked you to clarify, to have all here, but that would be another issue anyway.", - the Browse button doesn't really help the user (it listes all files in the HOME directory - and though the user might want to enter a simple application name (and perhaps should be given a list of found names to choose from), past experience suggested that a full path may be desirable. - the button might be better to validate an entered application name? The user can't be assumed to know the file system! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1803604]
Created attachment 181206 revision of (current) senddoc to correct problems Revisions labelled #001 enable sending email when Tools-Options- Internet-Email is set to /usr/bin/xdg-email (under Ubuntu 20.04 LTS) The revision labelled #002 enable sending document as email when Option- Email is blank - in this case LO currently does NOT supply any MAILER to senddoc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
I've tested this today and the acceleration works. - kVideoDecoderName: "VDAVideoDecoder" - Distro: Ubuntu 22.04 - GPU: AMD Radeon RX 5600 XT - CPU: AMD Ryzen 5 3600 Also about the libva native: vainfo: VA-API version: 1.14 (libva 2.12.0) [installed libva packages are at version 2.14] snap: vainfo: VA-API version: 1.14 (libva 2.6.0) -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: To test the snap with VA-API changes, 1. Install the snap with sudo snap install --channel candidate/hwacc chromium 2. snap run chromium --disable-features=UseChromeOSDirectVideoDecoder --enable-features=VaapiVideoDecoder 3. Open a video, e.g. one from https://github.com/chthomos/video- media-samples 4. Enter about:media-internals in the address bar and note what the page says for kVideoDecoderName. Please report - The value for kVideoDecoderName from step 4. Success is typically {Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder; - If failed, the video used for testing, including codec and resolution if possible; - Distro version (if in doubt, `grep VERSION= /etc/os_release`); - GPU (if in doubt, attach the output of `lscpu`); - CPU generation (if in doubt, attach the output of `lscpu`). About the last point, it may be that unfortunately only those with newer generations of Intel CPUs will have luck with this, but it's still an uncertainty. So reports are highly welcome. --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1981148] [NEW] saving dialog focus skips to search bar
Public bug reported: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1981148 Title: saving dialog focus skips to search bar Status in firefox package in Ubuntu: New Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days a