[Desktop-packages] [Bug 2063815] [NEW] No microphone available
Public bug reported: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2063815 Title: No microphone available Status in alsa-driver package in Ubuntu: New Bug description: The system Ubuntu 24.04 does not detect any microphone. The system is Lenovo ThinkPad T14 Gen4. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:frybort2330 F pipewire /dev/snd/controlC0: frybort2334 F wireplumber /dev/snd/controlC1: frybort2334 F wireplumber CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 11:37:02 2024 InstallationDate: Installed on 2024-04-19 (7 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: LENOVO 21K3003RCK PackageArchitecture: all ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2024 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R2FET55W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 21K3003RCK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrR2FET55W(1.35):bd02/20/2024:br1.35:efr1.28:svnLENOVO:pn21K3003RCK:pvrThinkPadT14Gen4:rvnLENOVO:rn21K3003RCK:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K3_BU_Think_FM_ThinkPadT14Gen4: dmi.product.family: ThinkPad T14 Gen 4 dmi.product.name: 21K3003RCK dmi.product.sku: LENOVO_MT_21K3_BU_Think_FM_ThinkPad T14 Gen 4 dmi.product.version: ThinkPad T14 Gen 4 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2063815/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Unlocking SSH keys with the passphrase that is saved to gnome-keyring now works too. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Released Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
Can you give me an answer to my question if this is related or if I should file a new bug? https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/2060575/comments/20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: Opinion Status in gnome-keyring package in Ubuntu: Won't Fix Status in gnome-shell package in Ubuntu: Fix Committed Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2060575] Re: gnome-keyring fails to automatically unlock login keyring after recent updates in noble
I noticed another problem which makes me wonder if it's related to this. When you unlock the keyring yourself it still fails to unlock ssh keys. If you do: $ export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh it starts working again. Is this related or should I report a separate bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/2060575 Title: gnome-keyring fails to automatically unlock login keyring after recent updates in noble Status in gdm3 package in Ubuntu: New Status in gnome-keyring package in Ubuntu: Triaged Bug description: After installing recent updates in 24.04, upon logging in the gnome- shell based UI pops up saying that the login keyring was not unlocked and asking for the users password to be input to unlock it. Similarly a second, non-gnome-shell based UI is also present asking the same thing. Will try and get a screenshot to attach. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libpam-gnome-keyring 46.1-2build1 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 9 06:16:46 2024 InstallationDate: Installed on 2021-08-03 (980 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210802) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-keyring UpgradeStatus: Upgraded to noble on 2024-01-31 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2060575/+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 2049630] [NEW] [LE-Beats Studio Pro tilhørende j, playback] Playback problem
Public bug reported: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no problem switching to and from off and a2dp_sink but I can no longer get to the handsfree_head_unit. journalctl -b -f gives the follwing error message when trying to activate the handsfree_head_unit profile: myleno pulseaudio[405145]: Refused to switch profile to handsfree_head_unit: Not connected cut/paste of pacmd command: list-cards: .. . . index: 2 name: driver: owner module: 24 properties: device.description = "Beats Studio Pro tilhørende jan" device.string = "A4:16:C0:63:87:DD" device.api = "bluez" device.class = "sound" device.bus = "bluetooth" device.form_factor = "headphone" bluez.path = "/org/bluez/hci0/dev_A4_16_C0_63_87_DD" bluez.class = "0x240418" bluez.alias = "Beats Studio Pro tilhørende jan" device.icon_name = "audio-headphones-bluetooth" bluetooth.codec = "sbc_xq_453" profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) handsfree_head_unit: Handsfree Head Unit (HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: sinks: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink/#1: Beats Studio Pro tilhørende jan sources: bluez_sink.A4_16_C0_63_87_DD.a2dp_sink.monitor/#2: Monitor of Beats Studio Pro tilhørende jan ports: headphone-output: Headphone (priority 0, latency offset 10 usec, available: unknown) properties: headphone-input: Bluetooth Input (priority 0, latency offset 0 usec, available: no) properties: >>> set-card-profile 2 handsfree_head_unit Failed to set card profile to 'handsfree_head_unit'. >>> set-card-profile 2 a2dp_sink >>> set-card-profile 2 off >>> set-card-profile 2 a2dp_sink ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jan 2314 F pulseaudio /dev/snd/controlC0: jan2314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Jan 17 14:58:03 2024 InstallationDate: Installed on 2022-12-08 (404 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: LE-Beats Studio Pro tilhørende j Symptom_Type: Only some of outputs are working Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2022 dmi.bios.release: 1.46 dmi.bios.vendor: LENOVO dmi.bios.version: GLCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76465WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 17ALC6 dmi.ec.firmware.release: 1.46 dmi.modalias: dmi:bvnLENOVO:bvrGLCN46WW:bd03/23/2022:br1.46:efr1.46:svnLENOVO:pn82KV:pvrIdeaPad317ALC6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrIdeaPad317ALC6:skuLENOVO_MT_82KV_BU_idea_FM_IdeaPad317ALC6: dmi.product.family: IdeaPad 3 17ALC6 dmi.product.name: 82KV dmi.product.sku: LENOVO_MT_82KV_BU_idea_FM_IdeaPad 3 17ALC6 dmi.product.version: IdeaPad 3 17ALC6 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2049630 Title: [LE-Beats Studio Pro tilhørende j, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: I am no longer able to change pulseaudio card profile from a2dp_sink to handsfree_head_unit It used to work before running apt upgrade where I got a new kernel 6.5.0-14-generic #14~22.04.1-Ubuntu installed. As you can see below - and actual experience with the headphones, there is no problem switching to an
[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom of screen
It is there again in 23.10.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867613 Title: Ubuntu dock does not allow drag and move icons at bottom of screen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Ubuntu 20.04 daily development branch @ 16/3/2020 After a clean install daily at 14/3/2020 the ubuntu dock does not allow drag and move icons anymore with the dock placed at bottom you can still mouseclick and hold the icon, but it does not make space between other icons to release starting an application still showing the icon, and add to favorites still works the dock placed left or right it works better ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 12:31:30 2020 InstallationDate: Installed on 2020-03-14 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867613/+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 2028853] [NEW] Window management - window size and state is not restored
Public bug reported: Ubuntu 23.04 gnome-shell 44.2 X11 When maximizing a window like i.e. Nemo or Evolution and closing it, starting the app again leads to an unmaximized window. This behaviour is always the same within one session or after reboot. Firefox (not snap! but .deb install) for instance just shows this behaviour after a session restart/reboot. Within the session it remembers the window size and state. I expect that the window size of the last state before closing is restored after starting the app again. That was the normal behaviour until the upgrade to 23.04. 44.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 44.0-2ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/2028853 Title: Window management - window size and state is not restored Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 23.04 gnome-shell 44.2 X11 When maximizing a window like i.e. Nemo or Evolution and closing it, starting the app again leads to an unmaximized window. This behaviour is always the same within one session or after reboot. Firefox (not snap! but .deb install) for instance just shows this behaviour after a session restart/reboot. Within the session it remembers the window size and state. I expect that the window size of the last state before closing is restored after starting the app again. That was the normal behaviour until the upgrade to 23.04. 44.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages 100 /var/lib/dpkg/status 44.0-2ubuntu3 500 500 http://de.archive.ubuntu.com/ubuntu lunar/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028853/+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 2023049] Re: nautilus shows wrong files after delete
It seems a bug in nautilus which was fixed 1 month ago. When will ubuntu upgrade nautilus? https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2941 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2023049 Title: nautilus shows wrong files after delete Status in nautilus package in Ubuntu: Confirmed Bug description: Test case: 1) in a new directory: touch 1 2 3 result: files appear in nautilus 2) delete file 1 result: 3 disappears, 1 and 2 are shown 3) refresh using F5 results: 2 and 3 are shown I noticed this bizarre issue a few days ago and therefore reinstalled the 23.04 OS partition. Issue remains even after * fresh install of 23.04 on OS partition * gsettings reset-recursively org.gnome.nautilus * sudo rm -rf ~/.config/nautilus ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 16:04:48 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1663, 327)' InstallationDate: Installed on 2023-06-06 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2023049/+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 1969602] Re: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing
Same issue here, when setting Focus Follow Mouse, but with Xorg. I have a terminal and an editor opened. My mouse is over the terminal. I Alt+Tab to the editor, it changes focus to the editor and immediately focused back on the terminal -- effectively Alt+Tab is no longer working. Ubuntu 22.04.2 LTS. I do have two mouses plugged in -- in case this makes any difference, but when this happens I'm not touching them. -- 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/1969602 Title: gnome-shell with focus-mode=mouse behaves wrongly when alt-tabbing Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969602/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@Christian, @Konrad, Ubuntu 22.04 has this fixed. It was fixed in PulseAudio 15, run `pulseaudio --version` to see the version you are running. But HSP sound is still much worse than A2DP sound e.g. if you listen to music. HSP is still mono and limited to a bandwidth of 8 kHz. The scope of this bug was only to support WBS in the Linux stack, so improve HSP sound from even more terrible 4 kHz bandwidth to what it is now. The current limitations are with the Bluetooth specification and the limited data rates that bluetooth offers, so PipeWire is not going to help with that. If you want better two-way sound your options currently are using a wire, or using a proprietary wireless transmission (search for gaming headsets) or Bluetooth codec (there is the FastStream codec, but supporting headsets are extremely rare, I couldn't find anything with a proper mic that I would consider for video calls). -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 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 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: pulseaudio (Ubuntu) => ddeb-retriever -- 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/2008469 Title: ubuntu jammy debug mirror out of sync Status in ddeb-retriever: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ddeb-retriever/+bug/2008469/+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 2008469] Re: ubuntu jammy debug mirror out of sync
** Package changed: ubuntu-keyring (Ubuntu) => pulseaudio (Ubuntu) -- 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/2008469 Title: ubuntu jammy debug mirror out of sync Status in pulseaudio package in Ubuntu: Confirmed Bug description: Why dose the Ubuntu debug mirror is again out of sync how should it be used in a productive environment when every month the mirror is for one week broken. libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 2.7.4-1ubuntu3.1 is to be installed libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2 is to be installed libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 2.1.27+dfsg2-3ubuntu1.1 is to be installed libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 7:4.4.2-0ubuntu0.22.04.1 is to be installed libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 is to be installed libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 2:1.0.25-1ubuntu2 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008469/+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 1492580] Re: Display corruption
Same problem here https://haseebpc.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1492580 Title: Display corruption Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: I am running a newly installed and updated Ubuntu 14.04.3 LTS on a Samsung P500 Laptop (Model NP-P500I, NP-P500-RA01DE). I guess this issue is related to the graphics card, which is a Radeon Xpress 1250. The display corruption occurs directly after login on the top of the screen and i mentioned something at the bottom of the search window. I attached screenshots of it. I see similar corruption with ubuntu 15.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 5 14:05:22 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] [1002:7942] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c034] InstallationDate: Installed on 2015-09-05 (0 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: SAMSUNG ELECTRONICS CO., LTD. R59P/R60P/R61P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=baa0aac5-0549-40cc-b292-1b9a4af32753 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 09YI dmi.board.name: R59P/R60P/R61P dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr09YI:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR59P/R60P/R61P:pvr02YI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR59P/R60P/R61P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A: dmi.product.name: R59P/R60P/R61P dmi.product.version: 02YI dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Sep 5 13:47:09 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1492580/+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 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
Fresh installation Ubuntu 20.04 LTS with all updates / Fresh installation with all updates 22.04 LTS. Thinkpad X230 and external display. Default resolution external display 2560x1440. After screenlock the external display has a different resolution. Sometimes 1920x1080 or 1280x720. Only unplugging and plugging it back solves the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias:
[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
** Bug watch added: Red Hat Bugzilla #2155862 https://bugzilla.redhat.com/show_bug.cgi?id=2155862 ** Also affects: gnome-desktop (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2155862 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in gnome-desktop package in Fedora: Unknown Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 1995743] Re: webdav error trying to connect to nextcloud
For those having the same problem: You can simply replace the URL to open in order to make it work. Instead of /remote.php/dav/files/$USERNAME you can use /remote.php/webdav/ -- 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/1995743 Title: webdav error trying to connect to nextcloud Status in gvfs package in Ubuntu: Confirmed Bug description: upgraded to ubuntu 22.10 from 22.04 and webdav fails to connect to nextcloud. Reimaged back to 22.04 and it worked. Error message is "Message recipient disconnected from message bus without replying Please select another viewer and try again." I have tried webdav from mate 22.10 and gnome 22.10 with same failure. Crash report fails as well but I was able to get a copy before deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1995743/+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 1917939] Re: Windows maximise underneath dock after monitor sleep
Maybe related to this: https://gitlab.gnome.org/GNOME/mutter/-/issues/230#note_1551972. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #230 https://gitlab.gnome.org/GNOME/mutter/-/issues/230 ** Bug watch added: Red Hat Bugzilla #1878367 https://bugzilla.redhat.com/show_bug.cgi?id=1878367 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1878367 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell package in Fedora: Unknown Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+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 1993889] Re: nautilus does not launch
Nautilus works the first 3-5 minutes after booting, then it stops working with this zombie process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993889 Title: nautilus does not launch Status in nautilus package in Ubuntu: New Bug description: Problem: nautilus does not launch after it was closed previously. Expectation: Close nautilus, start nautilus again -> new nautilus window spawns. What happens: nautilus does not launch a second time. The cursor spins, but no window opens. Observations: the nautilus process does not get terminated properly. There is a nautilus process remaining with almost no CPU consumption. Workarounds: Killing the process and starting nautilus again works. Starting it via console and exiting it via X button does not end the task in the terminal. CTRL+C terminates the process and it's restarting fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:03:06 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)' InstallationDate: Installed on 2022-10-22 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1993889] [NEW] nautilus does not launch
Public bug reported: Problem: nautilus does not launch after it was closed previously. Expectation: Close nautilus, start nautilus again -> new nautilus window spawns. What happens: nautilus does not launch a second time. The cursor spins, but no window opens. Observations: the nautilus process does not get terminated properly. There is a nautilus process remaining with almost no CPU consumption. Workarounds: Killing the process and starting nautilus again works. Starting it via console and exiting it via X button does not end the task in the terminal. CTRL+C terminates the process and it's restarting fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:03:06 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)' InstallationDate: Installed on 2022-10-22 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993889 Title: nautilus does not launch Status in nautilus package in Ubuntu: New Bug description: Problem: nautilus does not launch after it was closed previously. Expectation: Close nautilus, start nautilus again -> new nautilus window spawns. What happens: nautilus does not launch a second time. The cursor spins, but no window opens. Observations: the nautilus process does not get terminated properly. There is a nautilus process remaining with almost no CPU consumption. Workarounds: Killing the process and starting nautilus again works. Starting it via console and exiting it via X button does not end the task in the terminal. CTRL+C terminates the process and it's restarting fine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:03:06 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1033, 685)' InstallationDate: Installed on 2022-10-22 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993889/+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 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Its still a bug in 22.04. as a normal user i can change the highlight active line setting as a "workaround" but that is not possible if gedit is started as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: Fix Released Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+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 1979137] [NEW] BT headset - microphone not working
Public bug reported: Hi The BT microphones is not working in Ubuntu / pulseaudio . Have tried several BT headset and none is working in Ubuntu. The Ubuntu guys ask me to open a case here (the case ID from Ubuntu is: 00338011 but here is a summery - I have never had a single one working. The one I have at my hand is * JLab GO Work It is connecting and shows up in the sound settings for the output - and give s sound out but not for the input. I have ad several Jabra from work also not working regarding the microphone. And before - and now - I have a BT set from Sony. Also not working regarding the microphone. All above are working at the Android phones, tables *and* Microsoft systems >From Ubuntu support I did various tests and discussed the problem with the OEM team. Here is a quick summary: - We don't have a list of supported Bluetooth headsets. The main problem here is that only a very limited number of vendors publish their source code and this makes it very difficult to have a compatibility list - The OEM team suggests opening a bug on launchpad for PulseAudio in order to leverage the community support. You can do this by using the link at [1] - The OEM team tested only with one model which is "Lenovo HE05" and it works (I'm waiting for an official confirmation for this. I cannot guarantee!) - During the last few days, I did some tests on my laptop (Dell XPS 15 9500). Actually, I'm using "JBL T450BT" and it works but, if I enable the built-in microphone, the audio quality switches to mono instead of stereo. Another test I did, is to use Pipewire instead of PulseAudio, which will be adopted (presumably) in Ubuntu 22.10 as the default but nothing changes in my own setup. Still, mono instead of stereo when enabling the microphone (If interested you can try to switch to Pipewire on Focal using the link at [2] (note that this is not an official guide and should be used as a reference only) .. .. This workarounds are not suitable for the general use and specific as we - at our firm has to use BT. Any ideas ? Best Jan ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1979137 Title: BT headset - microphone not working Status in pulseaudio package in Ubuntu: New Bug description: Hi The BT microphones is not working in Ubuntu / pulseaudio . Have tried several BT headset and none is working in Ubuntu. The Ubuntu guys ask me to open a case here (the case ID from Ubuntu is: 00338011 but here is a summery - I have never had a single one working. The one I have at my hand is * JLab GO Work It is connecting and shows up in the sound settings for the output - and give s sound out but not for the input. I have ad several Jabra from work also not working regarding the microphone. And before - and now - I have a BT set from Sony. Also not working regarding the microphone. All above are working at the Android phones, tables *and* Microsoft systems From Ubuntu support I did various tests and discussed the problem with the OEM team. Here is a quick summary: - We don't have a list of supported Bluetooth headsets. The main problem here is that only a very limited number of vendors publish their source code and this makes it very difficult to have a compatibility list - The OEM team suggests opening a bug on launchpad for PulseAudio in order to leverage the community support. You can do this by using the link at [1] - The OEM team tested only with one model which is "Lenovo HE05" and it works (I'm waiting for an official confirmation for this. I cannot guarantee!) - During the last few days, I did some tests on my laptop (Dell XPS 15 9500). Actually, I'm using "JBL T450BT" and it works but, if I enable the built-in microphone, the audio quality switches to mono instead of stereo. Another test I did, is to use Pipewire instead of PulseAudio, which will be adopted (presumably) in Ubuntu 22.10 as the default but nothing changes in my own setup. Still, mono instead of stereo when enabling the microphone (If interested you can try to switch to Pipewire on Focal using the link at [2] (note that this is not an official guide and should be used as a reference only) .. .. This workarounds are not suitable for the general use and specific as we - at our firm has to use BT. Any ideas ? Best Jan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1979137/+subscriptions -- Mailing list: https://launchpad.
[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 1793124]
As akkad...@gmail.com asked more than a year ago in comment #29: Will a donation make a difference? I need the smooth scrolling to use OO Calc on a touch display by elderly people in my business, so I'm financially interested into 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/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 1973468] [NEW] New Windows from favorites often not working
Public bug reported: Running Ubuntu 22.04 jammy, firefox 100 from snap. First time launch from the left launcher (favorites) normally works fine. Open a second window using the context menu "New Window" or "Open a New Windows" (what is the difference?) often just gives the rotating Ubuntu cursor and no Firefox window is opened. Sometimes works though, so you have to try a few times. ^N in an open firefox window work fine. ** Affects: firefox (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/1973468 Title: New Windows from favorites often not working Status in firefox package in Ubuntu: New Bug description: Running Ubuntu 22.04 jammy, firefox 100 from snap. First time launch from the left launcher (favorites) normally works fine. Open a second window using the context menu "New Window" or "Open a New Windows" (what is the difference?) often just gives the rotating Ubuntu cursor and no Firefox window is opened. Sometimes works though, so you have to try a few times. ^N in an open firefox window work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1973468/+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 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 1970871] [NEW] Misbehaving context menu in autohide dock mode
Public bug reported: Steps to reproduce: Configure Ubuntu-dock to be a dock with auto hide enabled. Also move it to the lower edge of the screen. Have any application overlapping with the dock for triggering the auto hide. Move mouse to lower screen edge to show dock, then right click on any application icon, open the apps context menu and move the cursor up to any of the context menu entry and click it. What happens: As soon as you click at a context menu item, the dock auto hides and the whole context menu window moves down and aligns with the lower edge of the screen which leads to selecting a wrong menu item above the selected one. Reproducible. Does not happen if no overlapping window triggers the dock to hide. What should happen: The context menu shouldn't move at all while the cursor is interacting with it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 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: Fri Apr 29 08:04:40 2022 InstallationDate: Installed on 2022-04-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1970871 Title: Misbehaving context menu in autohide dock mode Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Steps to reproduce: Configure Ubuntu-dock to be a dock with auto hide enabled. Also move it to the lower edge of the screen. Have any application overlapping with the dock for triggering the auto hide. Move mouse to lower screen edge to show dock, then right click on any application icon, open the apps context menu and move the cursor up to any of the context menu entry and click it. What happens: As soon as you click at a context menu item, the dock auto hides and the whole context menu window moves down and aligns with the lower edge of the screen which leads to selecting a wrong menu item above the selected one. Reproducible. Does not happen if no overlapping window triggers the dock to hide. What should happen: The context menu shouldn't move at all while the cursor is interacting with it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 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: Fri Apr 29 08:04:40 2022 InstallationDate: Installed on 2022-04-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1970871/+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 1967843] Re: cheese display corrupted under Ubuntu 22.04
I added a fix for this to Arch's `clutter-gst` (bug link https://bugs.archlinux.org/task/74222): https://github.com/archlinux/svntogit-packages/blob/packages/clutter- gst/trunk/0001-video-sink-Remove-RGBx-BGRx-support.patch This allows MJPEG cameras to work properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Unknown Status in cheese package in Ubuntu: Triaged Status in cheese source package in Jammy: Triaged Bug description: The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 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-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-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: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1967843/+subscriptions --
[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 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- 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/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+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] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Also affects: plasma-browser-integration (Ubuntu) Importance: Undecided Status: New -- 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: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: New Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager 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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I've also got an Avantree DG80 as a workaround and I can confirm it works with my Trekz OpenComm headset. It supports sounds up to 8 kHz (corresponding to mSBC with a 16 kHz sampling frequency) with the mic enabled, while anything connected directly to Linux bluetooth only goes up to 4 kHz in HSP/HFP mode (CVSD). The sound with mSBC is still noticeably worse than in A2DP mode when listening to music, but a lot better than CVSD. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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
Re: [Desktop-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK I printed two files successfully with: jbm@curlew:~/test_set$ lp Truloc-211-Retainer.pdf request id is jbm-2810-314 (1 file(s)) jbm@curlew:~/test_set$ lp IMG_4737x.JPG request id is jbm-2810-315 (1 file(s)) The files are enclosed, together with the subsequent error_log. The Trulocpdf file should be the same one that failed whem sent from Document Viewer. On 2022-03-21 17:44, Till Kamppeter wrote: > I your error_log I have found the following: > > D [21/Mar/2022:15:08:48 +0100] [Job 312] Send-Document: client-error- > document-format-error (client-error-document-format-error) > > This looks like that the printer was not able to work with the data it > received. > > The printer reports that it accepts PWG Raster as the only of the known > data formats used for driverless printing (it supports other formats, > too, but these are formats we cannot generate). Therefore we print in > PWG Raster format. > > It is possible that some printers have firmware bugs, not able to print > certain files in standard format. It is less probable that the PWG > Raster provided by us has problems as otherwise I would have received > many more bug reports. > > Now I need also CUPS error_log output from jobs which succeeded for you > and also I need the files which you have actually sent, both succeeding > and failing files. Could you attach these? > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "IMG_4737x.JPG" https://bugs.launchpad.net/bugs/1964095/+attachment/5571377/+files/IMG_4737x.JPG ** Attachment added: "Truloc-211-Retainer.pdf" https://bugs.launchpad.net/bugs/1964095/+attachment/5571378/+files/Truloc-211-Retainer.pdf ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571379/+files/error_log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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
Re: [Desktop-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
OK, that worked; file attached. On 2022-03-21 17:26, Till Kamppeter wrote: > Seems that your version of "driverless" is too old, not yet having the " > --std-ipp-uris" option (see also output of "driverless -h"). > > But I have found the URI you need in your error_log. Please run the > following command: > > ipptool -tv ipp://EPSON0EF3E0.local:631/ipp/print get-printer- > attributes.test > attrs.txt > > and attach attrs.txt. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "attrs.txt" https://bugs.launchpad.net/bugs/1964095/+attachment/5571360/+files/attrs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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
Re: [Desktop-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Tried the below, but it didn't work for me: jbm@curlew:~$ driverless --std-ipp-uris ERROR: Unable to create PPD file: Could not poll sufficient capability info from the printer (--std-ipp-uris, (null)) via IPP! On 2022-03-21 15:36, Till Kamppeter wrote: > Thanks for the files. > > For the "ipptool -tv ..." command do the following: > > Run > > driverless --std-ipp-uris > > You get an URI for your printer in standard IPP format. Please use that > URI for the "ipptool -tv ..." command of my comment above (comment #2) > and attach the attrs.txt here. > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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
Re: [Desktop-packages] [Bug 1964095] Re: print sent to Epson ET-2810 is not printed
Hi Till Kamppeter. Thanks for looking into my bug report. I have replied via Launchpad, but wasn't able to confirm that I managed to attach the files you asked for, so I attach them here, too. --jan On 2022-03-20 17:54, Till Kamppeter wrote: > Could you also attach your file > > /etc/cups/ppd/EPSON_ET_2810_Series.ppd > -- Jan Mathisen Email: jbmi...@gmail.com Adress: Bispeveien 54B, NO-1362 Hosle Phone: +47 97460585 Web:100yr.no ** Attachment added: "error_log" https://bugs.launchpad.net/bugs/1964095/+attachment/5571317/+files/error_log ** Attachment added: "jbm-2810.ppd" https://bugs.launchpad.net/bugs/1964095/+attachment/5571318/+files/jbm-2810.ppd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] Re: print sent to Epson ET-2810 is not printed
In response to advice 2022_03_20: jbm@curlew:~/Desktop$ driverless ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ jbm@curlew:~/Desktop$ ipptool -tv ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ get-printer-attributes.test > attrs.test ipptool: Unable to connect to "EPSON ET-2810 Series._ipp._tcp.local" on port 631 - Name or service not known I suppose this might possibly have failed because I have assigned a new name to the printer after the debug report using: lpadmin -p jbm-2810 -v ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ - E -m driverless:ipp://EPSON%20ET-2810%20Series._ipp._tcp.local/ Since then I have had good experience printing pdf- and jpg-files from a terminal window using the lp command; printing e-mail and pdf-attachments from Thunderbird also works; printing pdf-files from Document Viewer and jpg-files from Image Viewer fails. jbm@curlew:~/Desktop$ cupsctl --debug-logging Attepted to print a file called "Truloc-211-Retainer.pdf" from Document Viewer to jbm-2810; it appears to be placed in the print queue and toleave the print queue but no print emerges from the printer. I have tried to attach the cups/error_log file and the jbm-2810.ppd file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: Incomplete Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+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 1964095] [NEW] print sent to Epson ET-2810 is not printed
Public bug reported: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1964095 Title: print sent to Epson ET-2810 is not printed Status in cups package in Ubuntu: New Bug description: This is a new network printer in my home/local network. It works ok from my mobile phone and from Windows, but not from Ubuntu 20.04 on the same PC, my preferred system. I can print the test page consistently via 'Settings - Printers - Printer Details'; occasionally I have managed to print a simple text e-mail from Thunderbird; pdf-files and jpg-files don't come out; the process shows the job entering the print queue and being completed, but nothing appears to happen on the printer. I have used 'ubuntu-bug cups'to generate this report, so I hope it has included all the info you need, but please let me know if I can provide anything you are missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 10:11:02 2022 InstallationDate: Installed on 2021-03-13 (359 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON_ET_2810_Series: implicitclass://EPSON_ET_2810_Series/ MachineType: Dell Inc. XPS 8700 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON_ET_2810_Series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON_ET_2810_Series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=35fa7eb2-f276-418c-9acd-f55a95687068 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/16/2014:br4.6:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr:skuXPS8700: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1964095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1959027]
Vlad, thanks for the hint! The xdg-desktop-portal-gtk package was not installed on my Jammy test system. After installing it, all three remaing UI issues (wrong theme, wrong cursor, wrong font size) seem to be fixed! So it would help, at least on Kubuntu, if the xdg-desktop-portal-gtk package was installed by default. -- 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 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:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+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 1959027]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #2) > Does this work on the nightly? I would expect bug 1734934 to have fixed this. Two of the issues seem to be fixed in nightly: 1. Dark theme is now correctly enabled without requiring a session restart first. 5. Firefox correctly uses KDE file dialogs now (with correctly rendered fonts!) The following three issues remain unchanged: 2. Font size of the UI elements is too big. 3. Wrong GTK theme is used (Adwaita, instead of Breeze Dark). 4. Mouse cursor uses wrong theme and is too big (it changes, when moving in and out of the Firefox window). I installed nightly by running 'snap refresh --edge 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 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:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions
[Desktop-packages] [Bug 1959027]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #4) > Does that happen with other GTK apps ran via snap? I don't think we have > control about the GTK theme in use. Interesting, I tested two other GTK3 apps via snap (Inkscape and eog): * when running under Plasma Wayland, they also used the "wrong" GTK theme (Adwaita instead of Breeze), just like Firefox. And they had the same ugly font rendering like in the GTK file dialog on my screenshot. * on Plasma X11, all three apps (Inkscape, eog and Firefox) correctly used Breeze as GTK theme! So it seems to me there is a general issue in Snap when running GTK3 apps under Plasma Wayland, which also affects 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 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:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/19
[Desktop-packages] [Bug 1959027] Re: Various UI and theming issues in Firefox snap when running in Plasma Wayland session
** Attachment added: "Second screenshot: GTK File dialog with distorted fonts" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+attachment/5557396/+files/Screenshot_20220125_165558.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 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:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+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 1959027] [NEW] Various UI and theming issues in Firefox snap when running in Plasma Wayland session
Public bug reported: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 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:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Wrong theme, UI font too big" https://bugs.launchpad.net/bugs/1959027/+attachment/5557383/+files/Screenshot_20220125_165617.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI i
[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 1941752]
(In reply to Jan Rathmann from comment #15) > For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from > kubuntu-backports-ppa. Please disregard this comment - I totally forgot that I had installed a patched version of exiv2 (with the change described in Comment 4) to workaround the bug, sorry for causing confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from kubuntu-backports-ppa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
The following change in CVE-2021-37620-3.patch is responsible: --- exiv2-0.27.3.orig/src/tags_int.cpp +++ exiv2-0.27.3/src/tags_int.cpp @@ -2865,7 +2865,7 @@ namespace Exiv2 { } std::string stringValue = value.toString(); -if (stringValue[19] == 'Z') { +if (stringValue.at(19) == 'Z') { stringValue = stringValue.substr(0, 19); } for (size_t i = 0; i < stringValue.length(); ++i) { -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Relevant terminal output from crash: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 108229 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
CVE-2021-37620-3.patch is responsible. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
** Also affects: gwenview (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] [NEW] Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Public bug reported: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwenview Importance: Unknown Status: Unknown ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Crash report of Gwenview" https://bugs.launchpad.net/bugs/1941752/+attachment/5520895/+files/gwenview-20210826-153914.kcrash ** Bug watch added: KDE Bug Tracking System #441121 https://bugs.kde.org/show_bug.cgi?id=441121 ** Also affects: gwenview via https://bugs.kde.org/show_bug.cgi?id=441121 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1778983] Re: Resume from suspend on Wayland breaks window positioning
See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1419 https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
I swapped my environment (gnome-fallback, chromium-browser, evolution, libreoffice, gnome-terminal) for a vanilla env of ctwm, xterm and firefox. After 4 days the memory usage stayed at 0.6%. Confirm that it is not a bug in xorg but in one of the other apps, as suggested by Daniel. So I need to check all other apps to see which one is causing the memory use and report it to the offending one. I've changed the status of this bug report to invalid. Thanks Daniel! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1931301] Re: NIC unavailable after suspend to RAM
i did a fresh install of 21.04, not an upgrade. the same problem. Doesn't seem to be upgrade related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1931301 Title: NIC unavailable after suspend to RAM Status in network-manager package in Ubuntu: Confirmed Bug description: Upgraded to 21.04 (hirsute) and now the network card is unavailable after suspend to RAM (sleep state S3). It worked flawlessly up until 20.10. My workaround for now is unloading and reloading the kernel module, but that won't work for normal users, hence this report. NIC in its unavailable state: 2: enp4s0: mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether d0:50:99:27:02:11 brd ff:ff:ff:ff:ff:ff NIC (from lspci): 04:00.0 Ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10) Trying to ifconfig it down/up results in: SIOCSIFFLAGS: No such device journalctl shows (right after recovering from suspend): NetworkManager[1911]: [1623181236.9371] manager: sleep: wake requested (sleeping: yes enabled: yes) NetworkManager[1911]: [1623181236.9372] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') NetworkManager[1911]: [1623181236.9382] manager: NetworkManager state is now CONNECTED_LOCAL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 8 21:59:15 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-25 (1748 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2021-06-04 (4 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1931301/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Yes, and since it could be the desktop env, the gnome terninal, anywhere really, I'm going to try real primitive: Tom's Window Mgr (twm) with an xterm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Well, it's not libreoffice nor evolution mail client. And I also tried Unity with X instead of fallback, no better, so it doesn't look like metacity. I'll try more experiments tomorrow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
i don't think it is libreoffice. I last restarted X 4 days ago, and memory usage has gone from under 1% to 8%. Libreoffice has stayed unchanged at 459376K total (with 2 docs open). metacity has grown but not conclusively. So I'll give it another week -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
I restarted the server, monitored it for a few days. The results were inconclusive, so doing more careful logging over a longer period to see if I can find a clear culprit :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1930641/+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 1930641] Re: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
xrestop - Display: localhost Monitoring 44 clients. XErrors: 0 Pixmaps: 708248K total, Other: 120K total, All: 708369K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 4604141 139 648 475983K 17K 476000K 192487 LibreOffice 6.4 1801852 20 1428 119656K 36K 119692K 190524 metacity 0c0 841 30 38343461K 10K 43471K 190467 gnome-flashback 400 0105 1724462K432B 24463K ? 360 3010 2212231K 1K 12233K ? Chromium clipboard 000 2020 14710800K 5K 10805K ? 640 0001010800K 0B 10800K ? 42029519 395 4001K 11K 4012K 192208 evolution 2c023211 70 3368K 3K 3371K ? Qt Selection Owner for VirtualBox 4a0 4412 248 1950K 7K 1957K 247305 pavucontrol 300 7316 284 1161K 7K 1169K 191186 Terminal 24014404 284 248K 7K255K 190649 Panel 380 540 24 176 124K 4K128K 191260 chrome 280 2300 485B 1K 1K 191201 update-notifier 2e0 111080B 1K 1K ? Qt Selection Owner for kdeconnectd 340 111060B 1K 1K ? 200 3100 130B408B408B 190623 ibus-x11 260 110090B264B264B 190668 nm-applet 0a0 210080B264B264B 190468 gnome-flashback-clipboard 540 110080B240B240B 336471 xdg-desktop-portal-gtk 520 110080B240B240B 580778 VirtualBox 4e0 110080B240B240B 312045 WebKitWebProcess 4c0 110080B240B240B 291315 WebKitWebProcess 480 110080B240B240B 291316 WebKitWebProcess 440 110080B240B240B 192244 WebKitWebProcess 3a0 110080B240B240B 343635 dropbox 320 110080B240B240B 190703 kdeconnectd 2a0 110080B240B240B 190700 evolution-alarm-notify ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg-server package in Ubuntu: Incomplete Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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
[Desktop-packages] [Bug 1930641] [NEW] memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2
Public bug reported: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: GIGABYTE GB-BXi7-5500 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=6999d6bd-6356-4df2-b056-032c25b2dd60 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2021-04-26 (37 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MQLP7AP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x 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.:bvrF2:bd12/05/2014:svnGIGABYTE:pnGB-BXi7-5500:pvr1.x:rvnGIGABYTE:rnMQLP7AP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GB-BXi7-5500 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1930641 Title: memory leak in xorg-server 2:1.20.9-2ubuntu1.2~20.04.2 Status in xorg package in Ubuntu: New Bug description: Progressive memory leak in Xorg. With 16Gb RAM, memory use increases by about 1% each day according to top. Started at about 1%, now 24% after nearly 3 weeks. Video driver is i915, uname -m shows x86_64. Ubuntu 20.04, up to date as at 29 May 2021. HDMI connector. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME-Flashback:GNOME Date: Thu Jun 3 11:06:35 2021 DistUpgraded: 2021-04-26 20:35:01,095 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox-guest, 6.1.16, 5.4.0-73-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 5500 [1458:1000] InstallationDate: Installed on 2017-05-31 (1463 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" -
[Desktop-packages] [Bug 1924757] Re: Ubuntu debug mirror is out of sync
** Package changed: ubuntu => mesa (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/1924757 Title: Ubuntu debug mirror is out of sync Status in mesa package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 When using the Ubuntu debug mirror (ddebs.ubuntu.com) and the official mirror (archive.ubuntu.com), it is not possible to install some debug symbols. For example: apt install mesa-vulkan-drivers-dbgsym Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mesa-vulkan-drivers-dbgsym : Depends: mesa-vulkan-drivers (= 20.0.4-2ubuntu1) but 20.2.6-0ubuntu0.20.04.1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1924757/+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 341024] Re: Use liberation fonts in firefox by default for better website layout
Yes, this bug is fixed of course since years! Totally forgot about this ancient report... ** Changed in: firefox (Ubuntu) Status: Incomplete => Fix Released -- 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/341024 Title: Use liberation fonts in firefox by default for better website layout Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Hello, with the fonts that are currently used by default in Firefox to render websites (I guess DejaVu), the layout on some sites is a bit distorted, you can see this in the screenshots below (taken on a fresh Jaunty installation). The cause for this seems to be that these fonts are a bit bigger than the default Microsoft fonts (Arial, Times New Roman, ...), on whose size some web layouter obviously rely. A possible workaround would be to use the Liberation Fonts for Firefox which are metric compatible with the Microsoft ones: http://en.wikipedia.org/wiki/Liberation_fonts I am doing this on my machine for some time now by selecting them manually in "Edit -> Preferences -> Content -> Fonts & Colors -> Extended...", they look very good. The Liberations Fonts package seems to be in Main now (ttf-liberation). Kind regards, Jan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/341024/+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 1917191]
I've already backported this fix; thanks. -- 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/1917191 Title: firefox will not start after it crashed unexpectedly Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: firefox crashed unexpectedly, and it will not start or restart. I am running the latest ubuntu-20.04.2 LTS, all updates applied. firefox 86.0+build3 --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnfg 1725 F pulseaudio /dev/snd/controlC1: johnfg 1725 F pulseaudio BuildID: 20210222142601 CasperMD5CheckResult: skip 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:348 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2020-02-22 (371 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp10s0 proto dhcp metric 600 10.8.0.0/24 via 10.8.0.17 dev tun0 10.8.0.17 dev tun0 proto kernel scope link src 10.8.0.18 169.254.0.0/16 dev wlp10s0 scope link metric 1000 192.168.1.0/24 dev wlp10s0 proto kernel scope link src 192.168.1.8 metric 600 NonfreeKernelModules: openafs Package: firefox 86.0+build3-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 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:348 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=80.0/20200818235255 (Out of date) Profile0 - LastVersion=86.0/20210222142601 RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (309 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.00L12 dmi.board.asset.tag: No Asset Tag dmi.board.name: CF52-4 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.00L12:bd07/05/2011:svnPanasonicCorporation:pnCF-52SLGDD1M:pvr004:rvnPanasonicCorporation:rnCF52-4:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CF52-4 dmi.product.name: CF-52SLGDD1M dmi.product.sku: CF-52SLGDD1M dmi.product.version: 004 dmi.sys.vendor: Panasonic Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1917191/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic - OS: Kubuntu 20.04.1 LTS - Machine: Dell Latitude 5501 - Headset: Haylou GT1 Plus -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1906120] [NEW] NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
Public bug reported: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROOT_PATH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_ROUTERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_SUBNET_MASK=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_TIME_OFFSET=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_WPAD=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: NM_DISPATCHER_ACTION=dhcp4-change Nov 28 06:04:05 drako
[Desktop-packages] [Bug 1905200] Re: Ubuntu-dock in Wayland slow
Please mark this bug as duplicate of Bug #1874578 Saw the bug report to late. Issue immediately vanishes after hiding mounted devices in the dock with: gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905200 Title: Ubuntu-dock in Wayland slow Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Only in Ubuntu's wayland session, on 20.04 and 20.10: App icons will appear with a massive delay (~10 seconds) after launching an app currently not in the favorites. Also moving pinned icons within the dock will only appear in the new location after a similar long time span. Otherwise the dock works without delays. I could see this behavior on two completely different machines. No problems in the default Xorg session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 21:46:23 2020 InstallationDate: Installed on 2020-11-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905200/+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 1874578] Re: [wayland] dock has very long load time when show-mounts is enabled
I can confirm this bug an completely vanilla 20.04 and 20.10 installs on two completely different machines. Long startup for icons to appear at boot, non favourite apps will appear with delay and moving apps will also have a big delay to appear in the new order. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: [wayland] dock has very long load time when show-mounts is enabled Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1874578/+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 1905200] [NEW] Ubuntu-dock in Wayland slow
Public bug reported: Only in Ubuntu's wayland session, on 20.04 and 20.10: App icons will appear with a massive delay (~10 seconds) after launching an app currently not in the favorites. Also moving pinned icons within the dock will only appear in the new location after a similar long time span. Otherwise the dock works without delays. I could see this behavior on two completely different machines. No problems in the default Xorg session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 21:46:23 2020 InstallationDate: Installed on 2020-11-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1905200 Title: Ubuntu-dock in Wayland slow Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Only in Ubuntu's wayland session, on 20.04 and 20.10: App icons will appear with a massive delay (~10 seconds) after launching an app currently not in the favorites. Also moving pinned icons within the dock will only appear in the new location after a similar long time span. Otherwise the dock works without delays. I could see this behavior on two completely different machines. No problems in the default Xorg session. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-ubuntu-dock 68ubuntu20.10.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 21:46:23 2020 InstallationDate: Installed on 2020-11-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1905200/+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 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Same problem on the fresh released Fedora 33, GNOME desktop on Wayland. I think this is a Wayland related issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1897784]
(In reply to Olivier Tilloy from comment #8) > This bug looks similar to > https://bugs.documentfoundation.org/show_bug.cgi?id=131083 Nice find. Summary of bug 131083: Happened reproducible for the user with LO Ubuntu build 6.4.0-0ubuntu7 and LO Tinderbox build 45ca47ac39c03df4de52d627a764f16068b1eab0 (7.0.0.0.alpha0+ is reported for all development builds before branch off / alpha1 / beta) and just with kf5 in KDE / Plasma 2, not with Xubuntu (Xfce? which VCL in About? I would assume gtk3). Happens with the empty / default document. Bug 131083 comment 13 states: "I'm testing both Kubuntu and Xubuntu in a VM environment (VirtualBox 6.1.4)." You can get a comparable (but not equal!) build to the Tinderbox one via https://bibisect.libreoffice.org/linux-64-7.0 commit fc089b4dda133f1fd03922b713708e53af6c16fa. Reproduce: 1. start Calc 2. mark F10/11 vertically 3. exit LO 4. choose not to save Questions for each point (which might be related or not): 1. How is Calc started? Desktop link, command line (which one?), via start center? Does it happen with non-default profile via -env:UserInstallation=file:///tmp/test? 2. How are the cells marked? Mouse only, keyboard? Which cell first? Does it crash with other cells? 3. Exit crash just happens via window decorations? Or also via menu? Or by using Alt+F4 or Ctrl+Q? Or also by closing the Calc document and then the start center? 4. Why does Calc think the document was modified? Point 4 is AFAIK already exposing the real bug. General question: any additional output in a terminal? New entries in ~/.xsession-errors? Is this just happening with the localized KDE (the reporter uses de-DE.UTF-8)? An other eventually related crash I found (fixed?) is bug 131533 in LO 6.4.4. The implemented fix / patch is just a workaround, as I couldn't come up with a minimal reproducer without LO. There are some additional comments (see last ones) with info in https://gerrit.libreoffice.org/c/core/+/90990. According to bug 131083 comment 15, an old LO profile doesn't seem to be the cause of this, as the crash could be reproduced after deleting the profile. Since it didn't crash with the first try, it still might somehow be related. Would still be nice to get a known crashing profile for testing / reference, in the case there is some setting in it, leading to the crash. Bug 131083 comment 26 states the problem to reproduce the bug. "Made the installed DEB packages identical" I guess just means the package list, like "dpkg --get-selections", not the exact versions. An other bug that just comes to my mind and which was actually fixed for 6.4.0 is bug 104717. That changes the selection / clipboard handling in Calc. Quoting from my commit message: "Calc also removes the system selection when clearing the selection. Other applications keep the primary selection valid, until the application or document closes, so do the same in Calc." So maybe this introduces some case, where the primary selection isn't correctly cleared on shutdown. This is not KDE specific, but the QClipboard handling / API is very different from either Gtk+ or X11, so there might be some broken case now, where we don't clean the selection on module shutdown. Can you see, if the Kubuntu crashes happen on KDE shutdown, AKA session management related? > In the errors.ubuntu.com tracker, the earliest version exhibiting the crash > is 6.4.3, and there are new reports daily with 6.4.6. The thing we definitely know is that the LO 1:6.4.6-0ubuntu0.20.04.1 build in combination with KDE makes the crash much more likely. It seems the original bug is older. Still we don't have any reproducer, just a huge amount of reported crashes from Kubuntu users. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: Incomplete Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Still not showing in latest 20.04. Already purged and installed again with no changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1897784]
FWIW: I have installed Ubuntu's LO 6.4.6 in my focal schroot. I'm running Debian Buster with KDE on the host in X11. I couldn't produce any crash with the LO in the chroot, doing Calc selections and copy and paste operations, D'n'D and also some external copy actions. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+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 1898334] [NEW] When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy
Public bug reported: Hello, this bug was originally reported on https://github.com/ubuntu/snapcraft- desktop-helpers/issues/205 where I added a comment with my experience ( https://github.com/ubuntu/snapcraft-desktop- helpers/issues/205#issuecomment-696781060 ). I thought creating a bug report on Launchpad in addition would maybe help to track this issue. The following has happened to me for two times so far: 1) Tried to start Chromium (one time it was via UI/.desktop file, one time it was by running 'chromium-browser' in terminal) 2) Chromium didn't launch but instead the helper script 'desktop-launch' (in /snap/chromium/1320/bin/desktop-launch) moved files and folders that are located on a separate partition to my home directory (detailed description below) until I killed it. Luckily I had a backup, but it caused some work to restore everything. Really eerie experience, when all of a sudden my files began to get messed up. My setup is as follows: The / and /home directory of my main installation (Kubuntu 20.04) are on a SSD drive, while there is also a much bigger HDD as a second drive where I store all of my "bigger" data (photos, music, videos etc.). The HDD partition is mounted unter /mnt/my_hdd and there are symbolic links in my home directory to its directories (e.g. ~/photos is a symlink to /mnt/my_hdd/photos). Now what desktop-launch seemed to do was to move the files and directorys of this symlinked directories (HDD) to my home directory (SSD). E.g. ~/photos/* (actually stored on /mnt/my_hdd/photos/) was moved to ~/*. Subdirectories like photos/album1 were kept intact, but all the content of the "top level folders" of my HDD (music, videos, photos, ...) got mixed up together in my home directory. In both cases I noticed there's something going wrong and managed to kill desktop-launch after a short time, otherwise, it would have filled up all the small space on my SSD. This can be a cause of data loss without having a backup, because 1) it destroys directory structures by moving files/folders from different directories into one (as described above), and 2) related to that mv could silently overwrite files with different ones which have the same name. Can I provide any further information to help to debug this? I'm not sure how I can reproduce this, since in all cases except the two ones recently Chromium startup worked just fine. Fortunately I'm using Chromium only for testing purposes, so I don't launch it that often and can make btrfs snapshots before doing so and taking that risk again. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Oct 3 09:19:51 2020 InstallationDate: Installed on 2020-04-08 (177 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1898334 Title: When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy Status in chromium-browser package in Ubuntu: New Bug description: Hello, this bug was originally reported on https://github.com/ubuntu /snapcraft-desktop-helpers/issues/205 where I added a comment with my experience ( https://github.com/ubuntu/snapcraft-desktop- helpers/issues/205#issuecomment-696781060 ). I thought creating a bug report on Launchpad in addition would maybe help to track this issue. The following has happened to me for two times so far: 1) Tried to start Chromium (one time it was via UI/.desktop file, one time it was by running 'chromium-browser' in terminal) 2) Chromium didn't launch but instead the helper script 'desktop-launch' (in /snap/chromium/1320/bin/desktop-launch) moved files and folders that are located on a separate partition to my home directory (detailed description below) until I killed it. Luckily I had a backup, but it caused some work to restore everything. Really eerie experience, when all of a sudden my files began to get messed up. My setup is as follows: The / and /home directory of my main installation (Kubuntu 20.04) are on a SSD drive, while there is also a much bigger HDD as a second drive where I store all of my "bigger" data (photos, music, videos etc.). The HDD partition is mounted unter /mnt/my_hdd and there are symbolic links in my home directory to its directories (e.g. ~/photos is a sym
[Desktop-packages] [Bug 1897784]
No. (In reply to Michael Weghorn from comment #2) > The only relatively recent commit related to QMimeData handling (i.e. mostly > copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in > 6.4.4 already. > > @jmux: Any ideas? We know the fix for tdf#131533 is rather fishy and more of a workaround, then a real fix. But if we have the same backtraces before 6.4.4 (and I checked that libreoffice_6.3.3-0ubuntu1.debian.tar.xz doesn't carry that fix), we can - kind of - rule that out. Also all the backtraces just indicate Calc (ScSelectionTransferObj), not any other LO modules (at least Writer), which is strange. Maybe an active selection in Calc is just more common on shutdown, then in other applications? OTOH a copy in Calc keeps the selection, even if you move the "cursor rectangle". There is also nothing suspicious new on https://crashreport.libreoffice.org/stats/version/6.4.6.2 And the only "fix" in vcl/qt5 between 6.4.2 and 6.4.3 is commit 1000169ebca79478a05b4c23e760d99bd77e739e ("Qt5 unify font attribute conversions"), which I would also rule out as the origin of any bug (famous last words). There is also no other fix in vcl/ or sc/ since commit cbac26c52ccbe59c51c6631cb8c4b0a314a9848a / 6.4.0, which looks suspicious at all w.r.t. the backtrace at a first glance. And the whole lazy clipboard stuff was already in 6.3. And your fix for tdf#129809 was already in 6.4.2. Still nothing would explain the current peak, I can see in https://errors.ubuntu.com since https://errors.ubuntu.com/?release=Ubuntu%2020.04=libreoffice- core=2020-08-24=2020-09-25, which matches the publishing date from https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1 . So I checked the diff of the 6.4.6 fix range for sc and interestingly it contains commit 8718d243edc9400b0e0131b096702af8d33df327 (rhbz#1847031 null-deref), which fixes a null-deref in ~ScTransferOb. That should really just fix a bug, not cause one, but eventually this just papers- over some real bug in the other fixes, which now hits Qt in some way. Because ScTransferObj is part of libsclo, which can't exists with "pScMod == nullptr". $ git log --pretty=oneline f2e448175cee92fc695413e7281223e9f23e30ee~1..origin/libreoffice-6-4-6 | wc -l 123 Now I really would like to have a reproducer, which eventually should also happen on master... and tdf#130559 is the only additional thing in sc that looks strange, but that's just 17 out of the 123 patches. Someone from Kubuntu could "mine" the crash reports, if there is anything reproducible in it. And I have to get the RHEL bug report from someone (Caolan, eventually). So while I first suspected something non-LO, it now smells like a LO bug, independent of VCL, evetually. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+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 1897784]
Created attachment 165978 Kubuntu shutdown crash bt It appears that one can just DL the text with a Launchpad login. So this is just a copy from the BT as reference. For whatever reason the clipboard object is still active, while the module is already gone, which is causing the crash. An other question is, what other packages were published that day, just in the case it's eventually no LO bug (I still think it is). -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+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 1897784]
Created attachment 165976 rhbz#1847031 cleaned crash bt That whole bt looks broken. RH has no reproducer either, so the fix is just a guess. Version was libreoffice-6.4.4.2-2.fc32.x86_64, as you can see in the bt paths. The bt itself looks "wrong". The user did a right-click on a Calc cell, that would open the context menu, but at that point, when the Gtk event is processed, a lot more stuff is already "gone", like all the aGuard objects have nullptr, so no mutex in them. So I guess this is just for reference, but won't help. -- 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/1897784 Title: /usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Status in libreoffice source package in Focal: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.6-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/cfc41540ed80c870e8fb93c32ad7df0b7391f1b7 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+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 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)
Resolving hosts in Chromium stopped working after applying the changes as described in: https://bugs.launchpad.net/ubuntu/+source/network- manager-strongswan/+bug/1864256/comments/3 Firefox and Chrome still could resolve host names. -- 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/1876083 Title: chromium snap from focal fails DNS lookups, or delays them (ipv6) Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: When working with the chromium snap included in focal, it sometimes takes a few seconds to lookup an URL, sometimes it cannot resolve the hostname of the URL at all. Doing the same browsing using firefox doesn't show such behavior, no timeouts, no failed lookups, no delays. Any way how to debug that? That is using IPv6 only. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1876083/+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 33072] Re: Pulling AC plug suspends computer
This happens consistently every time on my laptop running Ubuntu 20.04.1 LTS. I keep it running with the lid open and the AC power cable connected, when I unplug the cable Ubuntu auto-suspends (battery is well over 90%). Extremely annoying. The power settings are: * Automatic suspend when on battery power -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/33072 Title: Pulling AC plug suspends computer Status in HAL: Fix Released Status in gnome-power-manager package in Ubuntu: Fix Released Status in hal package in Ubuntu: Fix Released Status in gnome-power-manager package in Fedora: Fix Released Bug description: g-p-m (I guess) immediately suspends when switching from AC to battery - even if the battery is full (as reported by g-p-m itself after unsuspension). This is almost always reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/33072/+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 1778983] Re: Resume from suspend on Wayland breaks window positioning
Maybe related: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574251 (though that bug is against xorg). -- 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/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in Mutter: Unknown Status in mutter package in Ubuntu: New Status in mutter package in Fedora: Unknown Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/380 --- While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1778983/+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