[Desktop-packages] [Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Also affects: guix (Ubuntu) Importance: Undecided Status: New -- 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/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in AppArmor: New Status in Wike: New Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in foliate package in Ubuntu: Fix Committed Status in freecad package in Ubuntu: Invalid Status in geary package in Ubuntu: Fix Released Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Invalid Status in goldendict-webengine package in Ubuntu: Fix Released Status in guix package in Ubuntu: New Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Fix Released Status in kdeplasma-addons package in Ubuntu: Fix Released Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Incomplete Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in loupe package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Fix Released Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Fix Released Status in plasma-desktop package in Ubuntu: Fix Released Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Invalid Status in qmapshack package in Ubuntu: Fix Released Status in qutebrowser package in Ubuntu: Fix Released Status in rssguard package in Ubuntu: Fix Released Status in steam package in Ubuntu: Fix Released Status in supercollider package in Ubuntu: Fix Released Status in tellico package in Ubuntu: Fix Released Status in wike package in Ubuntu: Fix Committed Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/2046844/+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 1921931]
*** Bug 1878528 has been marked as a duplicate of this bug. *** -- 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/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in Mozilla Firefox: Won't Fix Status in firefox package in Ubuntu: Fix Released Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1921931/+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 912706]
*** Bug 1856184 has been marked as a duplicate of this bug. *** -- 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/912706 Title: 'Show items that contain' disabled in subscribe dialog Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: * Create an imap account * Go to File -> Subscribe Expect to be able filter folder list using 'Show items that contain' text box. Actually the text box is disabled. Present in 9.0 and 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/912706/+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 1959747]
Is this still reproducible with the latest 115.2 release? We went through some pretty in-depth optimization and it should behave much better. Even more improvements are on the horizon in the upcoming betas. -- 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/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91-102 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0 and later. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+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 1971168] Re: [snap] Files on local network shares are not opened / written
Can someone please explain how this is now logged as fix released when the upstream MR https://gitlab.gnome.org/GNOME/xdg-desktop-portal- gnome/-/merge_requests/67 is still open? In other words, is this an Ubuntu-only patch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 2025538] Re: Unrequested kernel update
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic package, but the linux-image-6.2.0-25-generic package has been available for some time. Package upgrades therefore insist on switching to nvidia- dkms, no matter what I try to do. So I'm still on 6.2.0-24. Is this just another aspect of this bug, or is the linux-objects- nvidia-* package discontinued and we are actually supposed to switch to dkms? -- 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/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 1987976]
*** Bug 1831711 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
*** Bug 1829390 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
*** Bug 1834232 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Released Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. The merge request was accepted upstream and will be included in mutter 44.2 which should be released approximately May 29. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
*** Bug 1833474 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
*** Bug 1832688 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1987976]
*** Bug 1830482 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: New Status in Release Notes for Ubuntu: Fix Released Status in firefox package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: In Progress Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 2016906] [NEW] Inactive zombie ghost icons left behind on desktop when copying files
Public bug reported: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release:22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "Example Zombie Ghost Icons On Desktop" https://bugs.launchpad.net/bugs/2016906/+attachment/5665032/+files/Screenshot%20from%202023-04-08%2007-54-06.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2016906 Title: Inactive zombie ghost icons left behind on desktop when copying files Status in gjs package in Ubuntu: New Bug description: When copying files between directory windows, occasionally zombie ghost icons are left on the desktop. These are like holes in the screen with an icon that appears on top of everything in its covered location, is not selectable and is not moveable. Ubuntu 22.10 Release: 22.10 gjs: Installed: 1.74.0-1 Candidate: 1.74.0-1 Version table: *** 1.74.0-1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gjs 1.74.0-1 ProcVersionSignature: Ubuntu 5.19.0-38.39-generic 5.19.17 Uname: Linux 5.19.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 11:24:52 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-21 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2016906/+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 1987976]
*** Bug 1825991 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 2015134] [NEW] libdmapsharing with 3.0 API is incompatible with libsoup3
Public bug reported: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ ** Affects: libdmapsharing (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdmapsharing in Ubuntu. https://bugs.launchpad.net/bugs/2015134 Title: libdmapsharing with 3.0 API is incompatible with libsoup3 Status in libdmapsharing package in Ubuntu: New Bug description: The version of the libdmapsharing API found in the libdmapsharing packages shipped by Ubuntu is obsolete, and the versions of libdmapsharing that provide it are incompatible with libsoup3. Since more applications are requiring libsoup3, and libsoup3 cannot exist with libsoup2 in the same process, Ubuntu should move to libdmapsharing-3.9.12+ in its upcoming release. Libdmapsharing-3.9.12+ makes use of libsoup3. The packages that use libdmapsharing include Rhythmbox and grilo-plugins, and both recently moved to libsoup3: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1996 https://gitlab.gnome.org/GNOME/grilo-plugins/-/commit/ae34da2264eab49eceaeeb0d1510b952a65ae030 The 3.9 series of libdmapsharing is available at: https://www.flyn.org/projects/libdmapsharing/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2015134/+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 1987976]
*** Bug 1822374 has been marked as a duplicate of this bug. *** -- 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/1987976 Title: firefox black window Status in Mozilla Firefox: Confirmed Status in Mutter: New Status in firefox package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
@BloodyIron, please see: https://github.com/christgau/wsdd I suggest you install as it is a significantly better work-around than constantly killing the daemon. It is intended to be released in the next Debian (bookworm) release as a package, I do not know if Ubuntu will also be including it in their next release. Whether Nautilus will use it or not, I could not answer to that - I have long since switched to using Thunar without any issues. With regards to "If restarting it 'fixers' it, then why on earth does it break in the first place?" I suggest you see one of the replies here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 and further reading here: https://gitlab.gnome.org/GNOME/gvfs/-/issues/506 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #307 https://gitlab.gnome.org/GNOME/gvfs/-/issues/307 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: New Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
And finally this bugfix reached Ubuntu 22.04 LTS today through updates. :) Took a while but it's working great, again. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Released Status in evince source package in Kinetic: Fix Released Status in evince package in Debian: Fix Released Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello everyone subscribed to this topic, I totally edited my previous comment because it was a misconception. Now I noticed, the problem depends on whether the printer is connected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
Hello everyone, I applied Jeffersons version of the solution and it helped (great!), but then I reverted '/etc/apparmor.d/usr.bin.evince' to the original version and printing with evince still works, even after reboot. Is it possible that this setting has to be applied only once? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1987583] [NEW] package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to make backup link of './usr/l
Public bug reported: Reported while upgrading 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgbm1 22.0.5-0ubuntu0.1 Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:40:57 2022 DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for file: '/etc/pulse/default.pa' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libgbm1:21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp WD Blue SN570 NVMe SSD \-[:00]- ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd androidboot.mode=normal root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware) console=tty1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: mesa Title: package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987583 Title: package libgbm1 21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux- gnu/libgbm.so.1.0.0' before installing new version: Invalid cross- device link Status in mesa package in Ubuntu: New Bug description: Reported while upgrading 20.04 to 22.04 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgbm1 22.0.5-0ubuntu0.1 Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:40:57 2022 DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for file: '/etc/pulse/default.pa' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libgbm1:21.2.6-0ubuntu0.1~20.04.2 [modified: usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp WD Blue SN570 NVMe SSD \-[:00]- ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd androidboot.mode=normal
[Desktop-packages] [Bug 1987582] [NEW] package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable to make backup link of './usr
Public bug reported: Reported while upgrading from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:41:07 2022 DistUpgraded: 2022-08-24 22:10:29,326 WARNING no activity on terminal for 300 seconds (Installed libreoffice-script-provider-python (arm64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libgles2:1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: Invalid cross-device link GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp WD Blue SN570 NVMe SSD \-[:00]- ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd androidboot.mode=normal root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware) console=tty1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: libglvnd Title: package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: Invalid cross-device link UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1987582 Title: package libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: Invalid cross-device link Status in libglvnd package in Ubuntu: New Bug description: Reported while upgrading from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libgles2 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:41:07 2022 DistUpgraded: 2022-08-24 22:10:29,326 WARNING no activity on terminal for 300 seconds (Installed libreoffice-script-provider-python (arm64)) DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libgles2:1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libGLESv2.so.2.1.0' before installing new version: Invalid cross-device link GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp
[Desktop-packages] [Bug 1987580] [NEW] package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to make backup link of './usr/lib
Public bug reported: Reported when upgrading from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:41:07 2022 DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for file: '/etc/pulse/default.pa' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libegl1:1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: Invalid cross-device link GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp WD Blue SN570 NVMe SSD \-[:00]- ProcKernelCmdLine: storagemedia=mtd androidboot.storagemedia=mtd androidboot.mode=normal root=UUID=ea5041c4-93df-4890-895c-cc4f02c13672 quiet splash plymouth.ignore-serial-consoles earlycon=uart8250,mmio32,0xfe66 pci=nomsi fsck.mode=force fsck.repair=yes mtdparts=sfc_nor:0x2@0xe(env),0x20@0x10(uboot),0x10@0x30(splash),0xc0@0x40(firmware) console=tty1 Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: libglvnd Title: package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: Invalid cross-device link UpgradeStatus: Upgraded to jammy on 2022-08-25 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1987580 Title: package libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] failed to install/upgrade: unable to make backup link of './usr/lib/aarch64-linux- gnu/libEGL.so.1.1.0' before installing new version: Invalid cross- device link Status in libglvnd package in Ubuntu: New Bug description: Reported when upgrading from 20.04 to 22.04. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libegl1 1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] Uname: Linux 4.19.219-odroid-arm64 aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Wed Aug 24 21:41:07 2022 DistUpgraded: 2022-08-24 22:04:11,462 DEBUG got a conffile-prompt from dpkg for file: '/etc/pulse/default.pa' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl8814au/5.8.5.1, 4.19.219-odroid-arm64, aarch64: installed rtl88x2bu/5.13.1, 4.19.219-odroid-arm64, aarch64: installed DuplicateSignature: package:libegl1:1.3.2-1~ubuntu0.20.04.2 [modified: usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0] Unpacking libgbm1:arm64 (22.0.5-0ubuntu0.1) over (21.2.6-0ubuntu0.1~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2UDLxZ/011-libgbm1_22.0.5-0ubuntu0.1_arm64.deb (--unpack): unable to make backup link of './usr/lib/aarch64-linux-gnu/libgbm.so.1.0.0' before installing new version: Invalid cross-device link ErrorMessage: unable to make backup link of './usr/lib/aarch64-linux-gnu/libEGL.so.1.1.0' before installing new version: Invalid cross-device link GraphicsCard: Lspci-vt: -+-[0002:20]---00.0-[21]00.0 Sandisk Corp WD Blue SN570 NVMe SSD \-[:00]- ProcKernelCmdLine: storagemedia=mtd
[Desktop-packages] [Bug 1969709] Re: libreoffice font selection unusably slow
Okay so we know we have a bug. Is this just going to sit here forever without further investigation and resolution? Ubuntu took Debian's testing fontconfig package and patched it without any change log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1969709] Re: libreoffice font selection unusably slow
There is something else going on with fontconfig. When you go to the fonts viewer "Fonts", some of the DejaVu font families are not shown correctly. Some are duplicated and others are not shown. The issue is solid repeatable. Install fonts-dejavu-extra and then launch "Fonts". I'm not sure this is a libreoffice issue. What patches did Ubuntu make to it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in fontconfig package in Ubuntu: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1969709/+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 1971168] Re: [snap] Files on local network shares are not opened / written
New bug ticket was opened where investigation is continued. ** Bug watch added: Mozilla Bugzilla #1773624 https://bugzilla.mozilla.org/show_bug.cgi?id=1773624 ** Changed in: firefox Status: Confirmed => Unknown ** Changed in: firefox Remote watch: Mozilla Bugzilla #1767316 => Mozilla Bugzilla #1773624 -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1964547]
*** Bug 1771632 has been marked as a duplicate of this bug. *** -- 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/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+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 1964547]
As of bug 1770407, MOZ_DISABLE_RDD_SANDBOX=1 is no longer needed for Mesa users. -- 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/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+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 1971168]
(In reply to Al Savage from comment #6) > [...] it may not be limited to FF, snaps, or even Mozilla, since my Chrome > install behaves similarly. You are right, this is actually affecting other applications, too. I get the exact same behavior described in the steps to reproduce when using Chromium installed via snap: Local files open fine, opening files on network shares does not trigger any reaction. Should this issue here remain open? -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Downloaded files not saved when saving to local network share
I've updated the bug to reflect that multiple applications are affected by this. On my system I can reproduce the issue with Firefox and Chromium, both installed via snap. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce: - 1. Run Firefox as a Snap package in Ubuntu 22.04 + 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable - 4. Open any website containing images in Firefox + 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share + * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. ** Summary changed: - [snap] Downloaded files not saved when saving to local network share + [snap] Files on local network shares are not opened / written -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971092]
Verified fixed, thanks. xwayland: $ snap run firefox wayland: $ MOZ_ENABLE_WAYLAND=1 snap run firefox xwayland: $ MOZ_ENABLE_WAYLAND=0 snap run firefox -- 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/1971092 Title: (touch broken: "glxtest: Could not connect to wayland socket" after upgrade to 22.04 Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: I'm reporting this bug, which is a duplicate of https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970884, since they haven't uploaded the requested information. I noticed that touch in firefox was no longer working after upgrade to 22.04. It looks like the xwayland version of firefox is loading and the error message "glxtest: Could not connect to wayland socket" is reported. I have "MOZ_ENABLE_WAYLAND=1" configured in `~/.pam_environment` as described at https://wiki.archlinux.org/title/firefox#Wayland and https://wiki.archlinux.org/title/Environment_variables#Graphical_environment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 1 18:55:51 2022 InstallationDate: Installed on 2021-10-12 (201 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-22 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971092/+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 1971168] Re: [snap] Downloaded files not saved when saving to local network share
Corresponding bug in Mozilla bugtracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1767316 ** Bug watch added: Mozilla Bugzilla #1767316 https://bugzilla.mozilla.org/show_bug.cgi?id=1767316 -- 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/1971168 Title: [snap] Downloaded files not saved when saving to local network share Status in firefox package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+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 1971168] Re: [snap] Downloaded files not saved when saving to local network share
** Description changed: Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: - * When saving to a folder on the local machine instead, saving works - correctly as expected. + * When saving to a folder on the local machine instead, saving works correctly as expected + * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share -- 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/1971168 Title: [snap] Downloaded files not saved when saving to local network share Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+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 1971168] [NEW] [snap] Downloaded files not saved when saving to local network share
Public bug reported: Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: snap -- 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/1971168 Title: [snap] Downloaded files not saved when saving to local network share Status in firefox package in Ubuntu: New Bug description: Steps to reproduce: 1. Run Firefox as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+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 1964547]
I assume this bug will be fixed once video decoding has been moved to a utility process (bug 1722051). Until then, MOZ_DISABLE_RDD_SANDBOX=1 environment variable is required to try out experimental VAAPI. -- 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/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+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 1964547]
*** Bug 1766517 has been marked as a duplicate of this bug. *** -- 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/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+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 1964547]
*** Bug 1765824 has been marked as a duplicate of this bug. *** -- 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/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: • Ubuntu 21.10 (64 bit) • Firefox 98 installed via apt (cookies & cache have been cleared) • Kernel 5.13.0-30-generic x86_64 • Tried on both wayland and X11 session → same result Steps to reproduce: (1) Visit https://www.youtube.com (2) Choose one of the video Actual Result: Video doesn't play What Expected: Video Play normally Previously it was normal on Firefox 97 (apt version) Tried installing Firefox 98 Snap version and it works normally To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam
Still happening on Ubuntu 20.04LTS: uname -a Linux nodename 5.15.15-76051515-generic #202201160435~1642693824~20.04~97db1bb~dev-Ubuntu SMP Fri Jan 21 x86_64 x86_64 x86_64 GNU/Linux The workaround suggested in original bug description worked for me but I needed to use someone else's computer in order to find the solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 enterprise wifi networks without CA_Certificate, like Eduroam Status in NetworkManager: Fix Released Status in Release Notes for Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Triaged Status in wpasupplicant package in Ubuntu: Triaged Status in network-manager-applet source package in Trusty: Triaged Status in wpasupplicant source package in Trusty: Triaged Status in network-manager package in Debian: New Status in Fedora: Fix Released Status in Gentoo Linux: Fix Released Status in network-manager package in openSUSE: Won't Fix Bug description: HOW TO REPRODUCE: Connect to a MPA2/PEAP/MSCHAPv2 enterprise wifi network that doesn't use a CA Certificate, like Eduroam. RESULT: The computer doesn't connect, as the certificate verification fails. WORKAROUNDS: (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap) RELEASE NOTES TEXT: When connecting to MPA2/PEAP/MSCHAPv2 enterprise wifi networks that doesn't use a CA Certificate, like Eduroam, the connection fails (http://askubuntu.com/questions/279762/cant-connect-to-wpa2-enterprise-peap) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 109943]
This slipped between other bugs, thanks for the ping. I'm not sure there's anything else to do here as I can't reproduce this issue anymore. Tested on 91.5.1 and on my mac the usage remains around 5% without spiking anymore. Also, if I'm not wrong, this is not a XUL element anymore but it's not a standard HTML progressbar. Can anyone else still reproduce it? -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: In Progress Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+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 1741074]
*** Bug 1738488 has been marked as a duplicate of this 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: Confirmed Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1953210] [NEW] package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of pack
Public bug reported: not a programmer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Dec 3 22:36:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libvdpau1:(not installed) Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-CYOEuz/155-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack): trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 770] [1458:3603] InstallationDate: Installed on 2021-09-25 (69 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=4e954e5c-691e-4c0b-a835-8de78a6f578d ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libvdpau Title: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1505:bd06/05/2014:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:skuAll:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIHERO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libvdpau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check package-conflict ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1953210 Title: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 Status in libvdpau package in Ubuntu: New Bug description: not a programmer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libvdpau1 (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Dec 3 22:36:48 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libvdpau1:(not installed) Unpacking libvdpau1:amd64 (1.3-1ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-CYOEuz/155-libvdpau1_1.3-1ubuntu2_amd64.deb (--unpack): trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of package libvdpau1:amd64 GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK104 [GeForce GTX 770] [1458:3603] InstallationDate: Installed on 2021-09-25 (69 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUS All Series
[Desktop-packages] [Bug 1844453]
(In reply to Xisco Faulí from comment #88)
> (In reply to daniel from comment #87)
> > This is not working in v7.2.2.2
> >
> > The key is not being properly stored, and the UI leaves a LOT to be desired.
> >
> > You may find that the way the tool rclone (rclone.org) handles this
> > authentication is much more graceful than the current solution.
> >
> > The dialog box is also misleading about what, when (at which step), and
> > where to paste the key from the OAuth process.
> >
> > There has to be a better way for users to be able to use this feature.
>
> hello,
> Please read comment 82 to allow storing the key
I have, but it is extremely user-unfriendly and unless you are looking
up this bug report, you would never know how to do it. Even then, the
notes in comment #87 are not the complete instructions.
Basically, this method is a dirty workaround of a patch job that needs
to be truly fixed in both the backend and the UI. The method used to get
and capture the key is not graceful, and the UI is plain incorrect.
I would fix it myself if it was something that had the skill to do (I
love open source software for that!), but I do not feel comfortable in
my skill level making those modifications. Instead, I have pointed this
very skilled and talented community to another piece of open-source
software that has done a very good job at tackling this issue for not
only Google Drive, but also for numerous other cloud storage vendors.
Their code base is mature, and the capabilities of that tool complement
what users of this project need.
In reality, the project might even look at integrating that tool's
functionality into this one, similar to how other modules have become
standard within the software. Spell checking is one function that comes
to mind.
I see this as an opportunity to potentially have one community help
another, giving them both a way to learn from the other's work and
experience. Isn't that one of the main benefits of being open source?
--
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/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1844453]
This is not working in v7.2.2.2
The key is not being properly stored, and the UI leaves a LOT to be
desired.
You may find that the way the tool rclone (rclone.org) handles this
authentication is much more graceful than the current solution.
The dialog box is also misleading about what, when (at which step), and
where to paste the key from the OAuth process.
There has to be a better way for users to be able to use this feature.
--
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/1844453
Title:
[upstream] Access to the Google remote account does not work
Status in LibreOffice:
In Progress
Status in libreoffice package in Ubuntu:
Confirmed
Bug description:
I have a Google account with 2FA login, from LibreOffice I try to add the
remote account, but it doesn't work, it asks me for a 6-digit PIN.
Investigating to see if it was just my problem, I discovered that this is a
long-standing LibreOffice bug (1) and seems unresolved.
The last report confirms this: "2019-07-04 04:44:41 UTC
This feature doesn't work with my Google account _w/o_
2FA.
Bug hasn't be resolved for about 3 years and "very soon"
we may celebrate 5 years anniversary. %-("
1) https://bugs.documentfoundation.org/show_bug.cgi?id=101630
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 17 23:00:10 2019
InstallationDate: Installed on 2019-02-18 (210 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
ProcEnviron:
TERM=screen-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1844453/+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 1741074]
> S2(Serious) Major functionality/product severely impaired and a satisfactory workaround does not exist -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1940707]
*** This bug has been marked as a duplicate of bug 1630251 *** -- 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/1940707 Title: [upstream] Maximized window becomes a mess at next startup after manually choosing to restore previous session Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: Confirmed Bug description: Checked on both current and new user. This behavior is observed only if "Restore previous session" is not enabled to occur automatically at startup. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kbar 1005 F pulseaudio /dev/snd/controlC1: kbar 1005 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 20 23:27:25 2021 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:352 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-17 (95 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.release: 15.54 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.49 dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:br15.54:efr86.49:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: L8N69PA#UUF dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940707/+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 1946599]
*** Bug 1737737 has been marked as a duplicate of this bug. *** -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1946599]
(In reply to Darkspirit from comment #1) > $ sudo snap remove firefox; sudo snap install firefox --channel=latest/beta; > snap run firefox https://webglsamples.org/aquarium/aquarium.html > > firefox (beta) 93.0b9-1 from Mozilla✓ installed > > broken Debian Testing, Gnome Wayland, Intel sudo snap remove firefox; sudo snap install firefox --channel=latest/beta EGL/Wayland works: snap run firefox https://webglsamples.org/aquarium/aquarium.html EGL/Xwayland works: DISABLE_WAYLAND=1 snap run firefox https://webglsamples.org/aquarium/aquarium.html -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1946599]
*** Bug 1732582 has been marked as a duplicate of this bug. *** -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #26) > If we do want to do the cleanup described above, we might need a new media > query which determines this (but it should definitely not have `csd` in the > name, since it is not about csd at all). So I'd rather clean up the existing > one since it's confusing at best. > And in all cases this patch stack doesn't regress behavior (and improves it in the obvious cases). So I'd say comment 25 should be a separate bug? Yes. I only remembered that a query like `-moz-gtk-csd-transparent- background` might be useful to allow Xshape removal (if it is desired). -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #20) Non-composited X11 (the legacy variant of X11: i3, KDE with manually disabled compositor, etc.) does not support transparency. Everything that would usually be transparent/alpha is just black/opaque. Menus and window corners had [shadows on black background](https://bug1479135.bmoattachments.org/attachment.cgi?id=8995686) (=fat black borders). The autoscroll icon was a [black square with a white circle](https://bug1649246.bmoattachments.org/attachment.cgi?id=9160184) in it. [XShapeCombineMask](https://searchfox.org/mozilla- central/search?q=XShapeCombineMask=) is implemented for software rendering only. Firefox creates a stencil (like a cookie cutter) of where transparency needs to get cut off. X11 then applies this stencil on every frame. The outer shadow of a rounded main menu, addon widget or [window titlebar](https://searchfox.org/mozilla- central/rev/37373cdeed20695af1ff1fd090f0736d9bf15e65/widget/gtk/nsWindow.cpp#6729,6793) has transparency, so it gets cut off by X11, leaving a rounded widget without shadow. XShapeCombineMask is not implemented for hardware rendering. That's why SW WR is enforced for menus, addons and autoscroll icon on non-composited X11 to make use of XShapeCombineMask while the main window is still using OpenGL. XShapeCombineMask * caused problems on [Mutter](https://searchfox.org/mozilla-central/rev/37373cdeed20695af1ff1fd090f0736d9bf15e65/widget/gtk/nsWindow.cpp#9084) back then * crashes the GPU process on Nvidia: bug 1730991 * causes performance problems according to the Chromium bugtracker: bug 1733094 comment 18,https://bugs.chromium.org/p/chromium/issues/detail?id=1198080 Could XShapeCombineMask be removed and instead menus and the autoscroll icon loose their border-radius (become rectangular) and loose their shadow (to avoid black background) if gdk_screen_is_composited() is false? IIUC, that would reduce code complexity, improve stability and performance. A rectangular autoscroll icon on non-composited X11 would be noticeable. But users choose non-composited X11 to get more performance than with composited X11. Considering this as well, it doesn't make sense to use XShapeCombineMask which contradicts their intent and causes above problems. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #17) > Created attachment 9246290 > Bug 1509931 - Remove -moz-gtk-csd-transparent-background. r=stransky > > > We always use alpha visual for WebRender KDE with disabled compositor, i3, etc. use alpha visual, but it's not transparent. Could -moz-gtk-csd-transparent-background be defined with gdk_screen_is_composited() and be used to forbid outer border-radius + outer shadow of main menu/addon/etc. widgets to remove any Xshape usage (bug 1730991 comment 6)? According to the Chromium bugtracker, Xshape also causes performance problems (bug 1730991 comment 7). -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
This bug should be fixed with https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2003 I cannot reproduce the issue anymore when this change is applied on my system. Can someone initiate that this fix is backported into Ubuntu 21.04? -- 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/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 gnome-shell package in Ubuntu: Triaged 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 1940417]
Ubuntu and Fedora ship an untested pre-Nightly feature. (MOZ_ENABLE_WAYLAND = bug 1543600) -- 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/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Steps to reproduce: Open Downloads panel, Library or Application menu form the Toolbar by clicking on the corresponding icons. Actual results: From version 90 I noticed that Library or other items in the Toolbar won't open when I click it. Instead it flickers a few times on mouse movement - it looks like it opens but it's not visible, it becomes visible a fraction of a second when I move the mouse otherwise it's completely transparent. Which Toolbar icon this affects seems random. I tried to fix it by resetting the Toolbar and disabling extensions which have icons in the Toolbar. Then I noticed that Library was working normal again but Downloads or Application Menu wouldn't open. When this happened with the Application Menu I could barely see the contents of the menu by moving the mouse which made the menu flicker. The cursor was able to select menu items in the menu but it was completely transparent. In the enclosed screenshot you can see I selected the Library menu item but it isn't opened. Expected results: The menus in the Toolbar should open like they used to. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeroen 3189 F pulseaudio /dev/snd/pcmC0D3p: jeroen 3189 F...m pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME 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:352 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 21.04 ForcedLayersAccel: False InstallationDate: Installed on 2021-05-22 (87 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 192.168.0.1 dev enp3s0 proto dhcp metric 20100 10.0.0.243 dev wgpia0 scope link 10.17.128.1 dev wgpia0 scope link 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.102 metric 100 Package: firefox 91.0+build2-0ubuntu0.21.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 (In use) RunningIncompatibleAddons: False Tags: wayland-session hirsute Uname: Linux 5.11.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/29/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: VM60 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd04/29/2014:br4.6:svnASUSTeKComputerINC.:pnVM60:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnVM60:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: VM60 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1943838] [NEW] libreoffice install should not use relative sym-link
Public bug reported: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute /usr/lib/libreoffice/program/soffice is symlinked twice into /usr/bin as libreoffice and soffice ** root@agnes ** /usr/bin ** Thu Sep 16 11:09:37 # ls -la *office lrwxrwxrwx 1 root root 36 Sep 16 10:56 libreoffice -> ../lib/libreoffice/program/soffice -rwxr-xr-x 1 root root 53 Aug 2 01:31 loffice lrwxrwxrwx 1 root root 36 Sep 16 11:05 soffice -> ../lib/libreoffice/program/soffice However, soffice is a shell script which derefs the symlink and then fails to find "../lib" If one recreates the symlinks with full paths, all is well ** root@agnes ** /usr/bin ** Thu Sep 16 11:16:37 # ls -la *office lrwxrwxrwx 1 root root 36 Sep 16 10:56 libreoffice -> /usr/lib/libreoffice/program/soffice -rwxr-xr-x 1 root root 53 Aug 2 01:31 loffice lrwxrwxrwx 1 root root 36 Sep 16 11:05 soffice -> /usr/lib/libreoffice/program/soffice ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: libreoffice -- 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/1943838 Title: libreoffice install should not use relative sym-link Status in libreoffice package in Ubuntu: New Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.04 Release:21.04 Codename: hirsute /usr/lib/libreoffice/program/soffice is symlinked twice into /usr/bin as libreoffice and soffice ** root@agnes ** /usr/bin ** Thu Sep 16 11:09:37 # ls -la *office lrwxrwxrwx 1 root root 36 Sep 16 10:56 libreoffice -> ../lib/libreoffice/program/soffice -rwxr-xr-x 1 root root 53 Aug 2 01:31 loffice lrwxrwxrwx 1 root root 36 Sep 16 11:05 soffice -> ../lib/libreoffice/program/soffice However, soffice is a shell script which derefs the symlink and then fails to find "../lib" If one recreates the symlinks with full paths, all is well ** root@agnes ** /usr/bin ** Thu Sep 16 11:16:37 # ls -la *office lrwxrwxrwx 1 root root 36 Sep 16 10:56 libreoffice -> /usr/lib/libreoffice/program/soffice -rwxr-xr-x 1 root root 53 Aug 2 01:31 loffice lrwxrwxrwx 1 root root 36 Sep 16 11:05 soffice -> /usr/lib/libreoffice/program/soffice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1943838/+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 1770587]
Calendar is disabled by default on first start up, and it's now possible to use
TB without an email account and avoid getting prompted at every startup.
So yeah, this issue should be pretty impossible to reproduce.
--
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/1770587
Title:
creation of new email account impossible in thunderbird
Status in Mozilla Thunderbird:
Invalid
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
With Ubuntu 18.04, creation of new email account is not possible.
You have a first screen "Would you like a new email address?" and no button
is active
I have restarted with add-on disabled but same issue
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:52.7.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jmax 2698 F pulseaudio
BuildID: 20180416164209
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Fri May 11 10:07:03 2018
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
Français Language Pack - langpack...@thunderbird.mozilla.org
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2016-01-31 (830 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
default via 192.168.0.254 dev wlo1 proto dhcp metric 600
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600
MostRecentCrashID: bp-da66c229-e498-447a-8233-47b610170721
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=52.7.0/20180416164209 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to bionic on 2018-04-28 (12 days ago)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1A
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3581
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 10.31
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.1A:bd07/20/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn3581:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 058F1124461620100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1770587/+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 1931722] [NEW] software-properties-gtk generates python errors
Public bug reported: Launching software-properties-gtk gives all these Python errors after having upgraded to 21.04: Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module" Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 196, in __init__ bus = dbus.SystemBus() File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__ return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop, File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of active connections for UID 1000 has been reached Version: 0.99.10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 11 17:36:34 2021 InstallationDate: Installed on 2020-09-06 (277 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- 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/1931722 Title: software-properties-gtk generates python errors Status in software-properties package in Ubuntu: New Bug description: Launching software-properties-gtk gives all these Python errors after having upgraded to 21.04: Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module" Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 196, in __init__ bus = dbus.SystemBus() File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__ return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop, File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__ bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__ bus = cls._new_for_bus(address_or_type, mainloop=mainloop) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of active connections for UID 1000 has been reached Version: 0.99.10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Fri Jun 11 17:36:34 2021 InstallationDate: Installed on 2020-09-06 (277 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1931722/+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 109943]
Comment on attachment 9225034 562977-progressmeter-statusbar.patch Review of attachment 9225034: - Looks good, thanks. Let's leave this open so I can later take it and investigate the performance issue. ::: mail/themes/shared/mail/folderProps.css @@ +25,1 @@ >overflow: hidden; little nit: this could benefit from a `vertical-align: middle` in the folder props dialog, because the default value from toolkit is `-0.2em`, for whatever reason. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: In Progress Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+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 109943]
Comment on attachment 9223784 562977-progressmeter-statusbar.patch Review of attachment 9223784: - I tested this on my slow mac and the CPU usage spikes up to 60%, with or without this patch. Nonetheless, the UI changes to the progress bar are welcome as it brings consistency to the interface. I'm not sure I like the current style of the progress bar. The height is a bit too tall and the border + bg color + animation + progress color makes this little widget look a bit busy and over styled. What do you think about: - 4px height - 2px border radius - no border color I'll see if I have any capacity later this week to investigate this and see if I can find how to prevent the spike in CPU usage. -- 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/109943 Title: Thunderbird: high CPU usage from progress bars Status in Mozilla Thunderbird: In Progress Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: mozilla-thunderbird When sending a simple and short email with Thunderbird via SMTP the CPU is used intensively. This seems not to be necessary. If the sending failed and an corresponding error message dialog appears, the CPU is still being used. When pressing ok to close the error dialog the CPU is fine. This suggests it might be related specifically to the progress bar. Such behavior is especially annoying on a laptop where you can hear the CPU usage because of a starting fan. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/109943/+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 643440]
We open the add-on homepage in the default system browser now, not within Thunderbird. So this bug is no longer valid. -- 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/643440 Title: show addon homepage fails with "Secure Connection Failed" Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Invalid Bug description: Binary package hint: thunderbird When an add-on's homepage uses an invalid certificate the connection fails with "Secure Connection Failed". There is no option to accept the certificate, so no way to visit the homepage. Steps to reproduce: 1. Install removedupes.mozdev.org 2. Click Tools->Add-ons->Remove Duplicates->Visit homepage Expected: a. A dialog to accept the security certificate b. A dialog to attempt an insecure connection c. Delegate all this to the web-browser ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.8+build2+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.43-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Mon Sep 20 13:21:23 2010 InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/643440/+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 1924282] [NEW] /etc/hp is empty after installing hplip package - 20.04LTS
Public bug reported: After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing. Looking at the logs, I found the following errors: E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin version[3.17.10] mismatch with HPLIP version[3.20.3] E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching I tried completely purging and re-installing the hplip package and the problem still exists. I then tried installing the correct plugin - here is what happened: * $ sudo apt update Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease [17.5 kB] Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Fetched 17.5 kB in 1s (22.0 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt install hplip --reinstall Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 204 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 hplip amd64 3.20.3+dfsg0-2 [204 kB] Fetched 204 kB in 0s (781 kB/s) (Reading database ... 303799 files and directories currently installed.) Preparing to unpack .../hplip_3.20.3+dfsg0-2_amd64.deb ... Unpacking hplip (3.20.3+dfsg0-2) over (3.20.3+dfsg0-2) ... Setting up hplip (3.20.3+dfsg0-2) ... Creating/updating hplip user account... Can't open /etc/hp/hplip.conf: No such file or directory. Can't open /etc/hp/hplip.conf: No such file or directory. Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for man-db (2.9.1-1) ... $ wget https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run --2021-04-15 08:51:22-- https://developers.hp.com/sites/default/files/hplip-3.20.3-plugin.run Resolving developers.hp.com (developers.hp.com)... 35.167.236.162, 34.210.182.99 Connecting to developers.hp.com (developers.hp.com)|35.167.236.162|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 11514166 (11M) Saving to: ‘hplip-3.20.3-plugin.run.2’ hplip-3.20.3-plugin 100%[===>] 10.98M 8.32MB/sin 1.3s 2021-04-15 08:51:24 (8.32 MB/s) - ‘hplip-3.20.3-plugin.run.2’ saved [11514166/11514166] $ sh hplip-3.20.3-plugin.run Verifying archive integrity... All good. Uncompressing HPLIP 3.20.3 Plugin Self Extracting Archive.. Error setting home directory: /etc/hp/hplip.conf not found. Is HPLIP installed? $ * I looked in the directory /etc/hp and it was indeed empty! See this question for more info: https://answers.launchpad.net/hplip/+question/696517 ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: installation missing-files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1924282 Title: /etc/hp is empty after installing hplip package - 20.04LTS Status in hplip package in Ubuntu: New Bug description: After upgrading to 20.04LTS, my HP-LaserJet 1018 printer stopped printing. Looking at the logs, I found the following errors: E [04/Apr/2021:12:12:55] common/utils.c 177: validate_plugin_version() Plugin version[3.17.10] mismatch with HPLIP version[3.20.3] E [04/Apr/2021:12:12:55] common/utils.c 210: Plugin version is not matching I tried completely purging and re-installing the hplip package and the problem still exists. I then tried installing the correct plugin - here is what happened: * $ sudo apt update Hit:1 http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Get:4 http://ppa.launchpad.net/system76-dev/stable/ubuntu focal InRelease [17.5 kB] Hit:5 http://security.ubuntu.com/ubuntu focal-security InRelease Fetched 17.5 kB in 1s (22.0 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. $ sudo apt install hplip --reinstall Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem: - Kernel: 5.8.0-41-generic - OS: Ubuntu 20.04.02 LTS - Headset: Sennheiser MB Pro 2 I can switch to HSP but even audio output won't work at all. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1914992] Re: gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
** Description changed: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.386][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:1041][info] BYTECOUNT: 3311031560, 118663140 - Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.387][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:942][info] peer: handshake at 1612777449 - "3 sec" ago Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support - -- + -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. - -- + -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. - - Stack trace of thread 249540: - #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) - #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) - #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) - #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) - #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) - #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) - #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) - #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) - #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) - #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) - #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) - #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) - #13 0x5562ad747532 main (gnome-calendar + 0x24532) - #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) - #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) - - Stack trace of thread 249544: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) - #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) - #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) - #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) - #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) - #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) - - Stack trace of thread 249543: - #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) - #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) -
[Desktop-packages] [Bug 1914992] [NEW] gnome-calendar crashes after a few clicks when creating event or un/toggling which calendar to show
Public bug reported: I am using gnome-calendar (3.36.2) on Linux Mint 20 (Ulyana), Cinnamon 4.6.7. I am able to replicate the crash by opening gnome-calendar, then clicking on "Manage your calendars" and toggling / untoggling different calendars at random. Here's a log from journalctl if it's of use: -- The job identifier is 27260. Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.386][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:1041][info] BYTECOUNT: 3311031560, 118663140 Feb 08 01:44:12 saturn pia-daemon[1412]: [2021-02-08 09:44:12.387][7b0a][wireguardmethod][daemon/src/wireguardmethod.cpp:942][info] peer: handshake at 1612777449 - "3 sec" ago Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: ** Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn org.gnome.Calendar[249540]: Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Feb 08 01:44:15 saturn systemd[1]: Started Process Core Dump (PID 249641/UID 0). -- Subject: A start job for unit systemd-coredump@41-249641-0.service has finished successfully -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit systemd-coredump@41-249641-0.service has finished successfully. -- -- The job identifier is 27350. Feb 08 01:44:16 saturn systemd-coredump[249642]: Process 249540 (gnome-calendar) of user 1000 dumped core. Stack trace of thread 249540: #0 0x7f1ff002018b __GI_raise (libc.so.6 + 0x4618b) #1 0x7f1fe859 __GI_abort (libc.so.6 + 0x25859) #2 0x7f1ff0523b43 n/a (libglib-2.0.so.0 + 0x1db43) #3 0x7f1ff0580b2f g_assertion_message_expr (libglib-2.0.so.0 + 0x7ab2f) #4 0x5562ad7685a7 n/a (gnome-calendar + 0x455a7) #5 0x7f1ff0645a56 n/a (libgobject-2.0.so.0 + 0x14a56) #6 0x7f1ff0664b28 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33b28) #7 0x7f1ff06650d3 g_signal_emit (libgobject-2.0.so.0 + 0x340d3) #8 0x5562ad7825ec n/a (gnome-calendar + 0x5f5ec) #9 0x7f1ff0557e6e g_main_context_dispatch (libglib-2.0.so.0 + 0x51e6e) #10 0x7f1ff0558220 n/a (libglib-2.0.so.0 + 0x52220) #11 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #12 0x7f1ff0773fd5 g_application_run (libgio-2.0.so.0 + 0xe2fd5) #13 0x5562ad747532 main (gnome-calendar + 0x24532) #14 0x7f1ff00010b3 __libc_start_main (libc.so.6 + 0x270b3) #15 0x5562ad74757e _start (gnome-calendar + 0x2457e) Stack trace of thread 249544: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) #2 0x7f1ff05582c3 g_main_context_iteration (libglib-2.0.so.0 + 0x522c3) #3 0x7f1ff155799d n/a (libdconfsettings.so + 0xa99d) #4 0x7f1ff0581911 n/a (libglib-2.0.so.0 + 0x7b911) #5 0x7f1fef452609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f1ff00fc293 __clone (libc.so.6 + 0x122293) Stack trace of thread 249543: #0 0x7f1ff00efaff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f1ff055818e n/a (libglib-2.0.so.0 + 0x5218e) #2 0x7f1ff0558513 g_main_loop_run (libglib-2.0.so.0 + 0x52513)
[Desktop-packages] [Bug 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
My apologies for sidetracking this far trying to explain differences between discovery and browsing but there seems to be a lot of mixing the 2 as one. The fact that you have "discovered" a server you wish to "browse" is irrelivant for this bug (afaik you shouldn't have been able to discover it as there are currently no working mechanisms to do so in LTS versions judging from the open bug reports). If however you are experiencing a crash whilst attempting to browse a share of the discovered host, that is relevant and is to do with the way SMB protocol versions themselves are being handled. WRT the rest of the discussion: SMBv1 leveraged NetBios to do discovery, (as did WINS which was a fallback discovery method). With SMBv1 removed/disabled, all of the NetBios discovery is also removed/disabled. Therefore, a discovery protocol is needed. Enter WSD. SMBv2 and SMBv3 use WSD to discover hosts on the network, (incidentally WSD was designed for SMBv2 during the development of Vista to remove the dependancy on NetBios). If you know the address of a host serving SMBv2 or SMBv3 already (via WSD, any other discovery protocol, off by heart), you can just do an SMB request against that address: smbclient --list=<> --user=Anonymous -N >The discoverability and connectivity works when the process is terminated and >restarted. Clearly this is achievable. > Yes, netbios was used previously, but clearly after killing the process I can > reach them without SMB v1, just not after the first boot. This is still probably nothing more than a cached entry, start-up check of previously known hosts, or initial broadcast. Some of which may or may not be unintentional from a security perspective, so as @seb128 said, file another bug report against them if you so wish. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
In the very same article you linked: https://docs.microsoft.com/en-us /windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by- default-in-windows With SMBv1 being removed, Network Browser (which depended on SMBv1) was removed, all of which relied on NetBios being used for discovery. (Hence, NetBios is dead, long live NetBios). Microsoft's replacement for NetBios discovery is *drumroll please*: WSD. I'm completely speculating here but: Your initial start up effect is probably gvfsd-smbd doing something like a Browser Tree scan of last known hosts. This actively goes to the host asking about available protocols, shares etc. This is NOT discovery. You could argue "well if it already knew about it, how does it lose it?" and that is a fair question, to which the answer might well be "Don't want to do an expensive back n forth poll, would rather use a discovery protocol", and now we are back to the discussion of needing a discovery protocol: WSD. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1828107] Re: gvfs can't list shares from smb servers that disabled SMB1
Not to put too fine a point on it, but actually that is exactly what this requires. Microsoft phased out the SMBv1 protocol, (NetBios is dead, long live NetBios), in favour of their new protocol: Web Services Dynamic Discovery (WSD). There has been a lot of discussion and work as to exactly HOW WSD should be implemented for SAMBA and gvfs and what to do in future if Microsoft do another flip of the switch. Granted this has taken a lot of time, but as previously mentioned, all of this discussion and development is dependent on people gratuitously handing over their free time. If you want up to date support and to demand for things to be done, might I politely suggest you fork out for a Red Hat enterprise subscription. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1828107 Title: gvfs can't list shares from smb servers that disabled SMB1 Status in gvfs: Unknown Status in gvfs package in Ubuntu: Triaged Bug description: After bug #1778322 is fixed (just needs a gvfs rebuild with newer samba), samba machines will start to show up again in the "windows network" tab in nautilus. But if a server has disabled the SMB1 protocol, nautilus will show an error when that server is clicked on, instead of showing the shares list. Even with SMB1 disabled, it should still be technically possible to get a share list, since smbclient can do it: andreas@nsnx:~$ nmblookup -A 192.168.122.101 Looking up status of 192.168.122.101 D-NO-SMB1 <00> - B D-NO-SMB1 <03> - B D-NO-SMB1 <20> - B ..__MSBROWSE__. <01> - B WORKGROUP <00> - B WORKGROUP <1d> - B WORKGROUP <1e> - B MAC Address = 00-00-00-00-00-00 andreas@nsnx:~$ smbclient -L 192.168.122.101 -N WARNING: The "syslog" option is deprecated Sharename Type Comment - --- print$ Disk Printer Drivers pub_no_smb1 Disk IPC$IPC IPC Service (d-no-smb1 server (Samba, Ubuntu)) Reconnecting with SMB1 for workgroup listing. protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE Failed to connect with SMB1 -- no workgroup available andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m NT1 WARNING: The "syslog" option is deprecated protocol negotiation failed: NT_STATUS_INVALID_NETWORK_RESPONSE andreas@nsnx:~$ smbclient //192.168.122.101/pub_no_smb1 -U ubuntu%ubuntu -m SMB2 WARNING: The "syslog" option is deprecated Try "help" to get a list of possible commands. smb: \> dir . D0 Fri May 3 18:16:38 2019 .. D0 Fri May 3 18:15:24 2019 hello.txt N 21 Fri May 3 18:16:12 2019 hello-from-nsnx.txt A9 Fri May 3 18:16:38 2019 20509264 blocks of size 1024. 13121800 blocks available To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1828107/+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 1900454]
(In reply to kchingx from comment #48) > how can this be a duplicate when it is not working on libre 7.0.2.2? > it was working on 7.0.1 upon upgrade it did not work anymore. > so do i downgrade? upgrade to newest Version 7.0.3.1 and check your scenario again. If the BUG is still present you can give a feedback again please. -- 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/1900454 Title: Calc doesn't recalculate formulas on cell content changes Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Committed Bug description: libreoffice-calc 1:7.0.2-0ubuntu1 (Groovy) The problem is better explained via steps to reproduce: 1. Start calc; you'll get a new spreadsheet. 2. Fill in the following in cells A1-A3: A1: 1 A2: =A1+1 A3: =A1-1 As expected: A2 is calculated as 2, A3 is calculated as 0. 3. Change A1 to 2 and press enter. A2 is autocalculated to 3, but A3 remains at 0 (wrong!). Now for the fun part: switch to a different application so LibreOffice window loses focus, the put it back in focus. A3 is now recalculated to 1. (Partially taken from: https://ask.libreoffice.org/en/question/271324/calc-v7022-cell- autocalculate-not-working-while-window-has-focus/) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1900454/+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 1889784]
Yes, bug 1658035 is about videos being completely green until the next Nightly update. -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1891079] [NEW] Issues Encountered installing lirc on new 20.04 device
Public bug reported:
** The first issue: Missing module and Deprecated syntax
While installing lirc:
If I run at the command line: sudo apt install lirc, it installs
lirc version 0.10.1-6.1ubuntu1.1 successfully.
However, when I run "sudo lirc-setup", I get the following dump;
-
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13:
PyGIWarning: Gtk was imported without specifying a v
ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure that
the right version gets loaded.
from gi.repository import Gtk # pylint: disable=no-name-in-module
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_view.py:14:
PyGIWarning: Vte was imported without specifying a vers
ion first. Use gi.require_version('Vte', '2.91') before import to ensure that
the right version gets loaded.
from gi.repository import Vte # pylint: disable=no-name-in-module
/usr/lib/python3/dist-packages/lirc/database.py:135: YAMLLoadWarning: calling
yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full
details.
cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:69: YAMLLoadWarning: calling
yaml.load() without Loader=... is deprecated, as the de
fault Loader is unsafe. Please read https://msg.pyyaml.org/load for full
details.
cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:142: YAMLLoadWarning: calling
yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full
details.
cf = yaml.load(f.read())
/usr/lib/python3/dist-packages/lirc/database.py:161: YAMLLoadWarning: calling
yaml.load() without Loader=... is deprecated, as the d
efault Loader is unsafe. Please read https://msg.pyyaml.org/load for full
details.
cf = yaml.load(f.read())
jwb@richese:~$ sudo lirc-setup
[sudo] password for jwb:
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13:
PyGIWarning: Gtk was imported without specifying a v
ersion first. Use gi.require_version('Gtk', '3.0') before import to ensure that
the right version gets loaded.
from gi.repository import Gtk # pylint: disable=no-name-in-module
Traceback (most recent call last):
File "/usr/bin/lirc-setup", line 16, in
import mvc_control
File
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py",
line 16, in
import choosers
File
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/choosers.py",
line 11, in
import mvc_model
File
"/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_model.py",
line 14, in
from lirc.database import Database
File "/usr/lib/python3/dist-packages/lirc/__init__.py", line 7, in
from .client import get_default_lircrc_path
File "/usr/lib/python3/dist-packages/lirc/client.py", line 38, in
import _client
ModuleNotFoundError: No module named '_client'
-
The last line "ModuleNotFoundError: No module named '_client'" is
apparently the same as was found in 18.04 and previously reported.
Note: I only installed from the binary package and did not install any
related source package.
The "deprecated calls" also will need addressing, but this is not
required immediately.
** Mis-located Document
:PROPERTIES:
:ID: a39c9ba0-7bfe-4ea9-8354-a67519473250
:END:
See the attached screenshot of the message from lirc-setup when trying
to verify some of the online documentation. The installed document is
not in the location the source code expects, so only the warning message is
displayed.
I have completed the install and configuration of lirc manually, but I
feel these issues should be resolved to simplify use of lirc by others.
John
** Affects: lirc (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Help Document Not Found"
https://bugs.launchpad.net/bugs/1891079/+attachment/5400505/+files/Screenshot%20from%202020-06-29%2012-39-31.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1891079
Title:
Issues Encountered installing lirc on new 20.04 device
Status in lirc package in Ubuntu:
New
Bug description:
** The first issue: Missing module and Deprecated syntax
While installing lirc:
If I run at the command line: sudo apt install lirc, it installs
lirc version 0.10.1-6.1ubuntu1.1 successfully.
However, when I run "sudo lirc-setup", I get the following dump;
-
/usr/lib/x86_64-linux-gnu/python3.8/site-packages/lirc-setup/mvc_control.py:13:
PyGIWarning: Gtk was imported without specifying a v
ersion first. Use
[Desktop-packages] [Bug 1889784]
[Tracking Requested - why for this release]: This regression affects: * MOZ_ENABLE_WAYLAND=1 users with Firefox 79, * MOZ_X11_EGL=1 and MOZ_ENABLE_WAYLAND=1 users with Firefox 80. Everyone is excited that Firefox 80 finally supports VAAPI hardware decoding on X11, it got news coverage, etc., but those who tested it know that it suffers from at least two fatal bugs. (bug 1645672 is the other one.) Wayland/MOZ_X11_EGL and VAAPI are still experimental and disabled-by-default, but it's a killer feature that brings users back. Therefore please consider uplifing this into beta, and even into a dot release, if there is any. Downstream Fedora applies this patch on Firefox 79: https://src.fedoraproject.org/rpms/firefox/c/cd18e999f576523b6b3f2076bca625d5e04d1178?branch=master https://www.reddit.com/r/archlinux/comments/i0ireu/firefox_developer_edition_hardware_video/fzpojad/ https://www.reddit.com/r/flatpak/comments/i157dm/green_flashes_in_video_in_firefox/ https://www.reddit.com/r/linux/comments/i04cvr/psa_firefox_79_appears_to_break_vaapi_decoding_on/ https://www.reddit.com/r/firefox/comments/i1p2ct/linux_vaapi_video_decode_acceleration_unreliable/ -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784]
*** Bug 1656777 has been marked as a duplicate of this bug. *** -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: New Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1889784]
*** Bug 1656653 has been marked as a duplicate of this bug. *** -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: New Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+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 1887646] [NEW] Add support for BGRA glyphs and scaling
Public bug reported: Not sure if the maintainers here are aware of this, but libxft2 has been misbehaving with emoji for a while. The result is that e.g. st (the terminal emulator) and gitk crash immediately when trying to render emoji. Very annoying. There's an upstream PR in the works here: https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1#note_567035 It is not merged upstream yet and does seem to need another push to do so. This persisted for me through an upgrade from 20.04 to "rolling rhino" and people in that thread report it for the 18. and 19 series too. I'm not in a position to contribute code to this, sadly. I barely understand what this is all about. But it is an annoying user facing bug so I figured it'd be better the Ubuntu maintainers be aware of it. Sorry if this is already being handled, I couldn't find any matching reports here yet. ** Affects: xft (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xft in Ubuntu. https://bugs.launchpad.net/bugs/1887646 Title: Add support for BGRA glyphs and scaling Status in xft package in Ubuntu: New Bug description: Not sure if the maintainers here are aware of this, but libxft2 has been misbehaving with emoji for a while. The result is that e.g. st (the terminal emulator) and gitk crash immediately when trying to render emoji. Very annoying. There's an upstream PR in the works here: https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1#note_567035 It is not merged upstream yet and does seem to need another push to do so. This persisted for me through an upgrade from 20.04 to "rolling rhino" and people in that thread report it for the 18. and 19 series too. I'm not in a position to contribute code to this, sadly. I barely understand what this is all about. But it is an annoying user facing bug so I figured it'd be better the Ubuntu maintainers be aware of it. Sorry if this is already being handled, I couldn't find any matching reports here yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xft/+bug/1887646/+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 1838965]
*** This bug has been marked as a duplicate of bug 1587060 *** -- 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/1838965 Title: Screen tearing in Firefox on Wayland Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: New Bug description: Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:36:32 2019 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:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1838965/+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 1838965]
(In reply to mail from comment #5) If you open about:support, what does "Compositing" say? It is normal that the Basic compositor (software rendering) shows tearing. Please open about:config, set gfx.webrender.all to true and restart Firefox to enable OpenGL rendering. WebRender is in the process of becoming enabled by default on Linux. -- 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/1838965 Title: Screen tearing in Firefox on Wayland Status in Mozilla Firefox: Invalid Status in firefox package in Ubuntu: New Bug description: Details here: https://photos.app.goo.gl/9kA7R6KqNaSsn9CB8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BuildID: 20190719083815 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 13:36:32 2019 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:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-08-04 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.0.1/20190719083815 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1838965/+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 827695]
Created attachment 162107 Announced attachment (In reply to dante19031999 from comment #48) > ... > In my humble opinion as begginer programmer they seem to be related with a > disfunction with OpenGL in windows. > ... Either misunderstood completely or cannot confirm: With LibO 7.0.0.0.beta1 under Win 10 I got exactly the behavior previously described independent of whether 'skia' was enabled or not. See new attachment. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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 1793124]
Set back to "Inherited by OOo". Please do not change the version field with a LibreOffice version you see the issue the last time. This field is for the oldest version where this issue was seen. -- 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/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I sometimes receive Calc documents where the content of an individual cell is split on so many lines that it fills up the whole screen and more. I can easily see the top part of these cells but scrolling to the bottom does not seem to work. Whether I try dragging the scrollbar or moving the screen with my laptop’s touchpad, Calc seems to skip the bottom part of the cell and jump directly to the following cell. See the attached screenshots of a document which has numbers 1 to 50 so that numbers 4 to 40 occupy one single cell (A4). In the first screenshot I see the top part of that cell (4 to 23) and in the next I have scrolled down the screen as little as possible, and now I see cell A5 (number 41) on the top. Everything in between is visually inaccessible whatever I try. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:16:17 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 1315835] Re: gedit overwrite dconf config with root permission
I experienced this problem in Ubuntu 18.04 LTS today... ** Changed in: gedit (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1315835 Title: gedit overwrite dconf config with root permission Status in gedit package in Ubuntu: Confirmed Bug description: Hi, gedit overrides the /home/user/.config/dconf/user file and convert it to root user. Also the gedit config files where overritten as root. The problem exists since xubuntu 14.04. I tried sudo, gksudo and sudo -H, but it does not change anything. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1315835/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Unfortunately, I wasn't able to re-enact the buggy state when I uninstalled the packages. Not sure why. I even tried to upgrade a clean version of Ubuntu 19.10 and 20.04 and still can't get the buggy state with that version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
this is guest-after.txt ** Attachment added: "guest-after.txt" https://bugs.launchpad.net/ubuntu/focal/+source/spice-vdagent/+bug/1872527/+attachment/5371584/+files/guest-after.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Ok so I'm attaching the dpkg -l output after my tests. I found no obvious issues with the fix in ppa2. I also tested the ppa2 on a freshly installed Ubuntu 20.04 and found no obvious issues. The team might want to consider deploying this fix and see if it could help more users and get their feedback. Note that I was testing the 'guest' VMs as I was having issues with them all along. guest-ubuntu.txt is from a freshly installed Ubuntu 20.04 VM guest-after.txt is from the original affected VM with Pop OS 20.04 installed. ** Attachment added: "dpkg status of Ubuntu 20.04 after applying ppa2 fix" https://bugs.launchpad.net/ubuntu/focal/+source/spice-vdagent/+bug/1872527/+attachment/5371583/+files/guest-ubuntu.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
ok let me try. I tried to upgrade another VM from 18.04 to 20.04 to do this, but I didn't experience any copy and paste issues by doing so. The affected VM was from 19.10 to 20.04. I will test the VM out with your suggestions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
You are right. I need to build spice-protocol 0.14.1 to get spice- vdagent 0.20 to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
I don't mind trying out the ppa, but my distro is Pop OS Ubuntu 20.04. Is that alright? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Triaged Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
Thanks! Hope to see the fix in Ubuntu Focal soon! -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+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 684982]
(In reply to Mike de Boer [:mikedeboer] from comment #92) > Well, I haven't heard about KDE Activities up 'till today, so I'll need to investigate this a little more before I can say anything relevant. Certainly, it deserves its own bug - which would be most appropriate for you to file - referencing this one. I just did so ( Bug 1633870 ). > I have to say, though, that the part of the appeal of fixing this bug was that it was beneficial for Linux users across various WMs, Mac OSX and - since late version 10 - Windows users. I understand, and I'm aware that there is only a small "activity" community. Therefore, it is very hard to find people which could help with problems in this context - that's exactly, why I'm hoping for you... -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
(In reply to Mike de Boer [:mikedeboer] from comment #76) > Hehe, I'm really glad you liked it! This was something of a spare time > project, so I'm especially happy when it reaches the right people. > > I hope there'll be more fun things coming in Firefox for you in the near > future ;-) This is, indeed, a great improvement - I was waiting the same 13 years for a solution as Hans-Peter! But as you kindly rise hope for more fun things, here still one feature I'm missing: essentially the same "bug" still occurs when I use KDE/plasma's "activities": Firefox restores (now) the windows on the correct desktops - thanks again! - but the desktops are mixed up on different activities (a window of desktop 1 in activity 2 may be restored on desktop 1 but on activity 1) . Of course, there might be some specific interferences with the activity handling of plasma (which, I think, is not used by many people and even less supported); but the similarity of the problem is striking, and as you was able to solve the desktop problem, I'm wondering whether it could be equally easy to solve the activity problem. (I'm not sure whether this should be reported as a new bug??) Currently I use: kubuntu 19.10; kernel 5.3.0-46; KDE-Plasma version 5.16.5. But the problem is as old as the activities of plasma. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 1871503] [NEW] Samsung M2026 doesn't work (patch available)
Public bug reported: Splix is a free (libre) and open-source alternative to Samsung's closed- source ULD driver. Next to being free, Splix also offers better grayscale rendering than Samsung's ULD driver. Splix mainly provides a raster-to-QPDL filter (QPDL is Samsung's proprietary printer command language) and PPD files for respective printers. In the past, I successfully used Splix to print with a Samsung M2022. When I had to replace the printer with an almost identical M2026 (same features, same enclosure, just younger) I noticed that the M2026 does not work with Splix as supplied by Ubuntu. (Printer accepts print jobs but does only produce empty pages or does not emit a page at all.) I recently came across a patch (to Splix) from 2019 that makes the M2026 work by adjusting some details in the generated QPDL stream. The patch was committed here: https://gitlab.com/ScumCoder/splix (looks like a fork of the SourceForge repository where Splix was available in the past). Using the code from the Gitlab repo, I was able to successfully use the M2026 with Ubuntu 18.04. Is there any way to get this modification into the Ubuntu splix (printer-driver-splix) package? I'm willing to help by creating a patch that can be applied against the package's source if needed/desired. ** Affects: splix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to splix in Ubuntu. https://bugs.launchpad.net/bugs/1871503 Title: Samsung M2026 doesn't work (patch available) Status in splix package in Ubuntu: New Bug description: Splix is a free (libre) and open-source alternative to Samsung's closed-source ULD driver. Next to being free, Splix also offers better grayscale rendering than Samsung's ULD driver. Splix mainly provides a raster-to-QPDL filter (QPDL is Samsung's proprietary printer command language) and PPD files for respective printers. In the past, I successfully used Splix to print with a Samsung M2022. When I had to replace the printer with an almost identical M2026 (same features, same enclosure, just younger) I noticed that the M2026 does not work with Splix as supplied by Ubuntu. (Printer accepts print jobs but does only produce empty pages or does not emit a page at all.) I recently came across a patch (to Splix) from 2019 that makes the M2026 work by adjusting some details in the generated QPDL stream. The patch was committed here: https://gitlab.com/ScumCoder/splix (looks like a fork of the SourceForge repository where Splix was available in the past). Using the code from the Gitlab repo, I was able to successfully use the M2026 with Ubuntu 18.04. Is there any way to get this modification into the Ubuntu splix (printer-driver-splix) package? I'm willing to help by creating a patch that can be applied against the package's source if needed/desired. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1871503/+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 684982]
(In reply to Hans-Peter Jansen from comment #77) > Dear Mike, > > with all due respect, but imagine, you suffer from such an issue for a good > part of this century, and now, you admit, fixing this issue was a spare time > dedication. Just to be clear, it doesn't lower your achievement, but it sheds > a really bad light on the *missing* Firefox development control. This is > accompanied with *degrading* this issue to an **enhancement**, with what most > of us comprehend as a **major bug**. > > Sure, we all know, which OS gets the most attention. But be assured, that for > a couple of us Linux Hardcore users (in other words, those, that suffer > **most** from this bug since **ages**) such experiences burrow into one's > subconscious, and that harms the project as a whole. > > Please understand, that those of us, that stick with Firefox still, don't > stick with it purely for technical reasons. A lot of us know about the > **political dimension** of the last free browser engine. My users and me use > Firefox, because we don't want to increase Google's influence even further, > *despite* bad performances like this. Again, no pun intended to you > personally. You're the **hero** for the moment in this small corner of > ontology. Some of us may have a picture of the bigger side of it, some > obviously don't! It's a pity, that those doesn't read this. > > I sincerely hope, that the fix will work for both situations, where it failed > before with different behavior: session restore from a restart of Firefox and > session restore from the window manager, and that it will *keep* working. > Wayland is lurking around the corner already... > > Hopefully, you don't feel offended. You shouldn't. > > Unfortunately, I have to wait for the 75.0 release to test this thoroughly on > about 30 very different openSUSE systems. A backport failed miserably. I really second this. IMHO this is/was a **major** bug even if LInux user are a minority group as usability also matters for minority groups -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
(In reply to Hans-Peter Jansen from comment #67) > Can you show us the output of `wmctrl -d`, please? ``` /home/werner> wmctrl -d 0 * DG: 10080x2100 VP: 0,0 WA: 0,0 3360x1050 N/A /home/werner> grep -i desktopsize ~/.fvwm/config DeskTopSize 3x2 ``` -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
I really like to know why upstream does ignore this bug. Is linux and the various used desktops (not GNOME) that dinky? Interesting the code seems to be there but overwritten later on -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Not sure if this will work with the virtual desktop screens I'm using here with fvwm as this is different from having several desktops in fvwm which can be done also. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 1869501] [NEW] Bluetooth status in the Unity menu bar does not always match status in system settings
Public bug reported: When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off. Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection. Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status. Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop Info: unity: 7.5.0+19.10.20190924-0ubuntu1 unity-control-center: 15.04.0+19.10.20190921-0ubuntu1 service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago Docs: man:bluetoothd(8) Main PID: 1035 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 3.5M CGroup: /system.slice/bluetooth.service └─1035 /usr/lib/bluetooth/bluetoothd Mär 28 14:17:39 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:49:02 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:50:08 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:59:25 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready Bluetooth device: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0029 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 28 16:53:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (68 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1869501 Title: Bluetooth status in the Unity menu bar does not always match status in system settings Status in unity-control-center package in Ubuntu: New Bug description: When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off. Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection. Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status. Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop Info: unity: 7.5.0+19.10.20190924-0ubuntu1 unity-control-center: 15.04.0+19.10.20190921-0ubuntu1 service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago Docs: man:bluetoothd(8) Main PID: 1035 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 3.5M CGroup: /system.slice/bluetooth.service └─1035
[Desktop-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
I can confirm that rolling back to linux-firmware=1.173.12 solves the issue with Kernel: 5.3.0-40-generic x86_64. -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in xorg package in Ubuntu: Confirmed Bug description: when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 79CN46WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO
[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
dualshock3nerd's solution also works for me too! Thanks!!! -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx 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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1863188] [NEW] Touchpad controls are not shown in System Settings
Public bug reported: The touchpad of this laptop is working fine from the beginning, however the System Settings application at "Mouse & Touchpad" will show only very basic mouse configuration options: Primary button left/right Double-Click speed I can not set the options about two-finger scrolling, tapping, edge, nor even pointer speed. This seems to be a unity-control-center bug because the Gnome Settings app does show the touchpad controls. OS: Ubuntu 19.10 (standard version) with Unity desktop added after installation Here is some info about the device: Notebook: Asus X571 /proc/bus/input/devices N: Name="ELAN1200:00 04F3:3104 Touchpad" P: Phys=i2c-ELAN1200:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3104.0001/input/input11 xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN1200:00 04F3:3104 Touchpadid=11 [slave pointer (2)] xinput list-props 11 Device 'ELAN1200:00 04F3:3104 Touchpad': Device Enabled (198): 1 Coordinate Transformation Matrix (200): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (335): 0 libinput Tapping Enabled Default (336): 0 libinput Tapping Drag Enabled (337):1 libinput Tapping Drag Enabled Default (338):1 libinput Tapping Drag Lock Enabled (339): 0 libinput Tapping Drag Lock Enabled Default (340): 0 libinput Tapping Button Mapping Enabled (341): 1, 0 libinput Tapping Button Mapping Default (342): 1, 0 libinput Natural Scrolling Enabled (343): 0 libinput Natural Scrolling Enabled Default (344): 0 libinput Disable While Typing Enabled (345):1 libinput Disable While Typing Enabled Default (346):1 libinput Scroll Methods Available (347):1, 1, 0 libinput Scroll Method Enabled (348): 1, 0, 0 libinput Scroll Method Enabled Default (349): 1, 0, 0 libinput Click Methods Available (350): 1, 1 libinput Click Method Enabled (351):1, 0 libinput Click Method Enabled Default (352):1, 0 libinput Middle Emulation Enabled (353):0 libinput Middle Emulation Enabled Default (354):0 libinput Accel Speed (355): 0.00 libinput Accel Speed Default (356): 0.00 libinput Left Handed Enabled (357): 0 libinput Left Handed Enabled Default (358): 0 libinput Send Events Modes Available (320): 1, 1 libinput Send Events Mode Enabled (321):0, 0 libinput Send Events Mode Enabled Default (322):0, 0 Device Node (323): "/dev/input/event8" Device Product ID (324):1267, 12548 libinput Drag Lock Buttons (359): libinput Horizontal Scroll Enabled (360): 1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Feb 14 01:11:48 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1863188 Title: Touchpad controls are not shown in System Settings Status in unity-control-center package in Ubuntu: New Bug description: The touchpad of this laptop is working fine from the beginning, however the System Settings application at "Mouse & Touchpad" will show only very basic mouse configuration options: Primary button left/right Double-Click speed I can not set the options about two-finger scrolling, tapping, edge, nor even pointer speed. This seems to be a unity-control-center bug because the Gnome Settings app does show the touchpad controls. OS: Ubuntu 19.10 (standard version) with Unity desktop added after installation Here is some info about the device: Notebook: Asus X571 /proc/bus/input/devices N: Name="ELAN1200:00 04F3:3104 Touchpad" P: Phys=i2c-ELAN1200:00 S: Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN1200:00/0018:04F3:3104.0001/input/input11 xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ELAN1200:00 04F3:3104 Touchpadid=11 [slave pointer (2)] xinput list-props 11 Device
[Desktop-packages] [Bug 1859369] [NEW] Gnome Cheese Overwrites gsettings
Public bug reported: I cannot get cheese to use my external USB webcam. cheese: 3.28.0-1ubuntu1 OS: 18.04.3 LTS on x86_64 gnome: 3.28.2 After plugging in the webcam, a new device appears at /dev/video2. Before running cheese, I set the camera setting as follows: $ gsettings set org.gnome.Cheese camera '/dev/video2' I then confirm the settings are correct: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera '/dev/video2' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' I then run the Cheese app, open the Preferences menu and find that the Device field is greyed out and shows just one choice: "BisonCam, NB Pro: BisonCam, NB" I then run gsettings again: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera 'BisonCam, NB Pro: BisonCam, NB' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' So, cheese seems to overwrite the gconf settings. I can't figure out how to get cheese to use my USB webcam! Additional info: $ sudo lsusb -v -s 003:036 Bus 003 Device 036: ID 0ac8:0302 Z-Star Microelectronics Corp. ZC0302 Webcam Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0ac8 Z-Star Microelectronics Corp. idProduct 0x0302 ZC0302 Webcam bcdDevice1.00 iManufacturer 1 V Micro. Corp. iProduct2 PC Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 336 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 160mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer
[Desktop-packages] [Bug 1857373] Re: GUI does not refresh when needed
I noticed that the compositor backend renderer was set to OpenGL3.1.
Setting is to OpenGL2 seems to solve the issue for now. Will test some
more and come back to update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1857373
Title:
GUI does not refresh when needed
Status in xserver-xorg-video-intel package in Ubuntu:
New
Bug description:
Yesterday I updated to Kubuntu 19.10. Since then, I'm having graphical
issues. It looks as if the screen is not refreshed when needed. Examples:
- clicking a link in a browser
- typing commands in Konsole
- typing this bug report
When I force a "big" screen update, for instance by alt-tabbing (usually,
pressing only alt is enough) the screen is refreshed.
When a "freeze" happens, the mouse cursor can still be moved.
I have an HP laptop using the Intel i915 driver. However, there is
also an Nvidia gpu on board, which might muddy the water a bit.
However, the nvidia gpu should be switched off (prime-select query
returns intel). There are no options set for the i915 module.
Additionally, it seems that the issue doe not occur on a fresh boot,
only after a sleep or hibernate.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Dec 23 21:03:15 2019
DistUpgraded: 2019-12-21 22:30:51,931 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.8, 5.3.0-24-generic, x86_64: installed
nvidia, 440.44, 5.3.0-24-generic, x86_64: installed
virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
wireguard, 0.0.20191219, 5.3.0-24-generic, x86_64: installed
zfs, 0.8.1, 5.3.0-24-generic, x86_64: installed
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520]
[103c:80a4]
InstallationDate: Installed on 2016-02-03 (1419 days ago)
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro
resume=UUID=321acbbf-9a6a-4825-8f47-a89d56536272 quiet splash pci=noaer
pcie_port_pm=off nogpumanager nouveau.runpm=0 nouveau.blacklist=1
crashkernel=512M-:192M
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to eoan on 2019-12-21 (1 days ago)
dmi.bios.date: 10/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.85
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80A4
dmi.board.vendor: HP
dmi.board.version: 91.1E
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.85:bd10/13/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1E:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: P4A01EA#ABH
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Dec 22 20:16:54 2019
xserver.configfile: default
xserver.errors:
libinput: SynPS/2 Synaptics TouchPad: Failed to create a device for
/dev/input/mouse1
PreInit returned 2 for "SynPS/2 Synaptics TouchPad"
Failed to open authorization file
"/var/run/sddm/{c77f7939-c416-47bb-80e1-c72f4be5b355}": No such file or
directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 22596
vendor SDC
xserver.version: 2:1.20.5+git20191008-0ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1857373/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help :
[Desktop-packages] [Bug 1857373] [NEW] GUI does not refresh when needed
Public bug reported:
Yesterday I updated to Kubuntu 19.10. Since then, I'm having graphical issues.
It looks as if the screen is not refreshed when needed. Examples:
- clicking a link in a browser
- typing commands in Konsole
- typing this bug report
When I force a "big" screen update, for instance by alt-tabbing (usually,
pressing only alt is enough) the screen is refreshed.
When a "freeze" happens, the mouse cursor can still be moved.
I have an HP laptop using the Intel i915 driver. However, there is also
an Nvidia gpu on board, which might muddy the water a bit. However, the
nvidia gpu should be switched off (prime-select query returns intel).
There are no options set for the i915 module.
Additionally, it seems that the issue doe not occur on a fresh boot,
only after a sleep or hibernate.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-intel 2:2.99.917+git20190815-1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Dec 23 21:03:15 2019
DistUpgraded: 2019-12-21 22:30:51,931 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.8, 5.3.0-24-generic, x86_64: installed
nvidia, 440.44, 5.3.0-24-generic, x86_64: installed
virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed
wireguard, 0.0.20191219, 5.3.0-24-generic, x86_64: installed
zfs, 0.8.1, 5.3.0-24-generic, x86_64: installed
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if
00 [VGA controller])
Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:80a4]
InstallationDate: Installed on 2016-02-03 (1419 days ago)
InstallationMedia: Error: [Errno 13] Permission denied:
'/var/log/installer/media-info'
MachineType: HP HP Pavilion Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=43cbb8c2-c0ce-40e2-a795-3a506e63d450 ro
resume=UUID=321acbbf-9a6a-4825-8f47-a89d56536272 quiet splash pci=noaer
pcie_port_pm=off nogpumanager nouveau.runpm=0 nouveau.blacklist=1
crashkernel=512M-:192M
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to eoan on 2019-12-21 (1 days ago)
dmi.bios.date: 10/13/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.85
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80A4
dmi.board.vendor: HP
dmi.board.version: 91.1E
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.85:bd10/13/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1E:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.sku: P4A01EA#ABH
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Dec 22 20:16:54 2019
xserver.configfile: default
xserver.errors:
libinput: SynPS/2 Synaptics TouchPad: Failed to create a device for
/dev/input/mouse1
PreInit returned 2 for "SynPS/2 Synaptics TouchPad"
Failed to open authorization file
"/var/run/sddm/{c77f7939-c416-47bb-80e1-c72f4be5b355}": No such file or
directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 22596
vendor SDC
xserver.version: 2:1.20.5+git20191008-0ubuntu1
** Affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan freeze gpu gui intel kubuntu refresh
** Summary changed:
- GUI does not refreshing when needed
+ GUI does not refresh when needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1857373
Title:
GUI does not refresh when needed
Status in xserver-xorg-video-intel package in Ubuntu:
New
Bug description:
Yesterday I updated to Kubuntu 19.10. Since then, I'm having graphical
issues. It looks as if the screen is not refreshed when needed. Examples:
- clicking a link in a browser
- typing commands in Konsole
- typing this bug report
When I force a "big" screen update, for instance by alt-tabbing (usually,
pressing only alt is enough) the screen is
[Desktop-packages] [Bug 827695]
The bug is still present in V6.4.0.0.beta1. -- 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/827695 Title: [Upstream] bug in displaying scalable square brackets in math object Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) When is expected to happen in LibreOffice Writer via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2284273/+files/bracket_example.odt && lowriter --nologo bracket_example.odt is the scalable square brackets look as they would in Word. Latex also shows the desired bracket shape as per https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/827695/+attachment/2287347/+files/latex_brackets.pdf . 4) What happens instead is the top and bottom part of the bracket look like a square instead of a line pointing inwards towards the equation. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/827695/+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
