[Desktop-packages] [Bug 2061165] [NEW] Could not play camera stream
Public bug reported: Running snapshot, I get a UI error message "could not play camera stream", a black window, and the following log messages: 2024-04-12T16:32:17.738325Z INFO snapshot::application::imp: Snapshot (org.gnome.Snapshot) 2024-04-12T16:32:17.738340Z INFO snapshot::application::imp: Version: 46.0 2024-04-12T16:32:17.738346Z INFO snapshot::application::imp: Datadir: /usr/share/snapshot (snapshot:923479): Adwaita-WARNING **: 09:32:17.773: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead. 2024-04-12T16:32:18.266073Z ERROR aperture::viewfinder: Could not start camerabin: Element failed to change its state 2024-04-12T16:32:18.270673Z ERROR aperture::viewfinder: Could not start camerabin: Element failed to change its state 2024-04-12T16:32:18.272590Z ERROR aperture::viewfinder: Bus Error from Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") stream error: error output enum formats: Invalid argument Some("../src/gst/gstpipewiresrc.c(689): on_state_changed (): /GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") 2024-04-12T16:32:18.272628Z ERROR aperture::viewfinder: Bus Error from Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") Internal data stream error. Some("../libs/gst/base/gstbasesrc.c(3175): gst_base_src_loop (): /GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir:\nstreaming stopped, reason not-negotiated (-4)") Running the flatpak org.gnome.Snapshot version of the app, everything works ok, fwiw ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-snapshot 46.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 12 09:31:36 2024 InstallationDate: Installed on 2019-08-17 (1701 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-snapshot UpgradeStatus: Upgraded to noble on 2024-03-23 (20 days ago) ** Affects: gnome-snapshot (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 gnome-snapshot in Ubuntu. https://bugs.launchpad.net/bugs/2061165 Title: Could not play camera stream Status in gnome-snapshot package in Ubuntu: New Bug description: Running snapshot, I get a UI error message "could not play camera stream", a black window, and the following log messages: 2024-04-12T16:32:17.738325Z INFO snapshot::application::imp: Snapshot (org.gnome.Snapshot) 2024-04-12T16:32:17.738340Z INFO snapshot::application::imp: Version: 46.0 2024-04-12T16:32:17.738346Z INFO snapshot::application::imp: Datadir: /usr/share/snapshot (snapshot:923479): Adwaita-WARNING **: 09:32:17.773: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead. 2024-04-12T16:32:18.266073Z ERROR aperture::viewfinder: Could not start camerabin: Element failed to change its state 2024-04-12T16:32:18.270673Z ERROR aperture::viewfinder: Could not start camerabin: Element failed to change its state 2024-04-12T16:32:18.272590Z ERROR aperture::viewfinder: Bus Error from Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") stream error: error output enum formats: Invalid argument Some("../src/gst/gstpipewiresrc.c(689): on_state_changed (): /GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") 2024-04-12T16:32:18.272628Z ERROR aperture::viewfinder: Bus Error from Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir") Internal data stream error. Some("../libs/gst/base/gstbasesrc.c(3175): gst_base_src_loop (): /GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir:\nstreaming stopped, reason not-negotiated (-4)") Running the flatpak org.gnome.Snapshot version of the app, everything works ok, fwiw ProblemType: Bug DistroRelease: Ubuntu 24.04
[Desktop-packages] [Bug 2054481] [NEW] Move "enhanced tiling" into Keyboard settings
Public bug reported: Starting in 23.10, Ubuntu introduced "enhanced tiling", which modifies the default behavior for Super+Right so that it does not only moves the window over to one side, but it also brings up a task-switcher for the remaining space. I wanted to turn this off, but did not know what it was called or what program/library etc. was causing it. It was a change to the behavior of a keyboard shortcut, so I went to "keyboard shortcuts". There it still says Super+Right is "view split on right". This not accurate anymore, as that is only half of what Super+Right does with Enhanced Tiling on. I had to do like 15 different Google searches before finding this Ask Ubuntu question https://askubuntu.com/questions/1494628/how-can-i-disable-the-new- superarrow-window-screen-aligning-feature which finally relieved my confusion, told me the name of the behavior, and allowed me to turn it off in the unexpected "Ubuntu Desktop" location. Please somehow make it clear from the keyboard settings that "enhanced tiling" exists, since it does modify keyboard behavior to be other than what keyboard settings says it is. You could do this by: - having "View Split On Left" and "Enhanced Tiling To Left" be two separate actions, and Super+left/right could be assigned to one or the other - somehow indicate the existence of Enhanced Tiling in the description of the keyboard action, like "View Split on left (see also Enhanced Tiling)" would have at least let me know I needed to search for an "Enhanced Tiling" setting See also related bug I filed for documenting Enhanced Tiling as part of keyboard shortcuts in ubuntu-docs https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2054478 ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2054481 Title: Move "enhanced tiling" into Keyboard settings Status in ubuntu-settings package in Ubuntu: New Bug description: Starting in 23.10, Ubuntu introduced "enhanced tiling", which modifies the default behavior for Super+Right so that it does not only moves the window over to one side, but it also brings up a task-switcher for the remaining space. I wanted to turn this off, but did not know what it was called or what program/library etc. was causing it. It was a change to the behavior of a keyboard shortcut, so I went to "keyboard shortcuts". There it still says Super+Right is "view split on right". This not accurate anymore, as that is only half of what Super+Right does with Enhanced Tiling on. I had to do like 15 different Google searches before finding this Ask Ubuntu question https://askubuntu.com/questions/1494628/how-can-i-disable-the-new- superarrow-window-screen-aligning-feature which finally relieved my confusion, told me the name of the behavior, and allowed me to turn it off in the unexpected "Ubuntu Desktop" location. Please somehow make it clear from the keyboard settings that "enhanced tiling" exists, since it does modify keyboard behavior to be other than what keyboard settings says it is. You could do this by: - having "View Split On Left" and "Enhanced Tiling To Left" be two separate actions, and Super+left/right could be assigned to one or the other - somehow indicate the existence of Enhanced Tiling in the description of the keyboard action, like "View Split on left (see also Enhanced Tiling)" would have at least let me know I needed to search for an "Enhanced Tiling" setting See also related bug I filed for documenting Enhanced Tiling as part of keyboard shortcuts in ubuntu-docs https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2054478 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2054481/+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 2048076] [NEW] Screen crashes in a wierd way
ENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=1945 comm="snap-confine" capability=38 capname="perfmon" [ 21.245177] overlayfs: fs on '/home/joe/.local/share/docker/overlay2/check-overlayfs-support3971078866/lower2' does not support file handles, falling back to xino=off. [ 21.256807] evict_inodes inode 867da6a8, i_count = 1, was skipped! [ 21.256815] evict_inodes inode f8db770e, i_count = 1, was skipped! [ 21.256819] evict_inodes inode 5765f53f, i_count = 1, was skipped! [ 21.256822] evict_inodes inode 5458467f, i_count = 1, was skipped! [ 21.256825] evict_inodes inode 949894ec, i_count = 1, was skipped! [ 21.258540] overlayfs: fs on '/home/joe/.local/share/docker/overlay2/metacopy-check1382144368/l1' does not support file handles, falling back to xino=off. [ 21.260005] evict_inodes inode 2dc61da9, i_count = 1, was skipped! [ 21.260012] evict_inodes inode 636c7c00, i_count = 1, was skipped! [ 21.260015] evict_inodes inode 0b73d191, i_count = 1, was skipped! [ 21.260018] evict_inodes inode d8b7d0c2, i_count = 1, was skipped! [ 21.309738] rfkill: input handler enabled [ 23.079841] rfkill: input handler disabled [ 23.985541] audit: type=1400 audit(1704364434.996:128): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2883 comm="snap-confine" capability=12 capname="net_admin" [ 23.985565] audit: type=1400 audit(1704364434.996:129): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=2883 comm="snap-confine" capability=38 capname="perfmon" [ 33.140391] usb 3-2.2: device descriptor read/64, error -110 [ 33.328357] usb 3-2.2: new full-speed USB device number 5 using xhci_hcd [ 46.849948] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 [ 48.905109] usb 3-2.2: device descriptor read/64, error -110 [ 64.564094] usb 3-2.2: device descriptor read/64, error -110 [ 64.676424] usb 3-2-port2: attempt power cycle [ 65.292593] usb 3-2.2: new full-speed USB device number 6 using xhci_hcd [ 70.366477] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 75.732213] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 75.940022] usb 3-2.2: device not accepting address 6, error -62 [ 76.019765] usb 3-2.2: new full-speed USB device number 7 using xhci_hcd [ 81.100524] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 86.470729] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 86.678505] usb 3-2.2: device not accepting address 7, error -62 [ 86.678760] usb 3-2-port2: unable to enumerate USB device [ 988.648266] usb 3-2.2: new full-speed USB device number 8 using xhci_hcd [ 1004.093450] usb 3-2.2: device descriptor read/64, error -110 [ 1019.713431] usb 3-2.2: device descriptor read/64, error -110 [ 1019.901387] usb 3-2.2: new full-speed USB device number 9 using xhci_hcd [ 1035.329901] usb 3-2.2: device descriptor read/64, error -110 [ 1050.942376] usb 3-2.2: device descriptor read/64, error -110 [ 1051.054563] usb 3-2-port2: attempt power cycle [ 1051.666360] usb 3-2.2: new full-speed USB device number 10 using xhci_hcd [ 1056.750547] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1062.130695] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1062.338654] usb 3-2.2: device not accepting address 10, error -62 [ 1062.418667] usb 3-2.2: new full-speed USB device number 11 using xhci_hcd [ 1067.502850] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1072.878997] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1073.086966] usb 3-2.2: device not accepting address 11, error -62 [ 1073.087137] usb 3-2-port2: unable to enumerate USB device [ 1169.817093] usb 3-2.2: new full-speed USB device number 12 using xhci_hcd [ 1185.349407] usb 3-2.2: device descriptor read/64, error -110 [ 1200.961721] usb 3-2.2: device descriptor read/64, error -110 [ 1201.149688] usb 3-2.2: new full-speed USB device number 13 using xhci_hcd [ 1216.578486] usb 3-2.2: device descriptor read/64, error -110 [ 1232.194238] usb 3-2.2: device descriptor read/64, error -110 [ 1232.302402] usb 3-2-port2: attempt power cycle [ 1232.914167] usb 3-2.2: new full-speed USB device number 14 using xhci_hcd [ 1238.002414] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1243.377705] xhci_hcd :03:00.4: Timeout while waiting for setup device command [ 1243.585638] usb 3-2.2: device not accepting address 14, error -62 [ 1243.669633] usb 3-2.2: new full-speed USB device number
[Desktop-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all
Weirdly simple, but wow, this cannot be it. Hallelujah After a few days reading and testing many things, I finally have audio! Apparently, it was missing (some?) library required for pipewire. I have a Legion 7i Pro running popOS on kernel 6.6.6-76060606-generic. Try running this command: sudo apt install libpipewire* Two library files were installed: libpipewire-0.3-dev:amd64 (1.0.0~1701092078~22.04~594e8f5) libspa-0.2-dev:amd64 (1.0.0~1701092078~22.04~594e8f5, automatic) Then, I rebooted, tested audio, and voila! -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2037460] Re: gnome-shell crash
there's nothing in /var/crash or in errors.ubuntu.com ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2037460] Re: gnome-shell crash
-b -1 ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704967/+files/prevjournal.txt -- 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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2037460] Re: gnome-shell crash
-b 0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704966/+files/journal.txt -- 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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2037460] [NEW] gnome-shell crash
Public bug reported: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+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 2035395] [NEW] windows randomly raise when others close
Public bug reported: (I am not sure if xwayland is at fault or the session or window manager. It happens under Wayland using gnome-session and gnome-shell, but not under X.org.) When I close a window, even using ^W or ^Q, another seemingly-random window may raise to the top, possibly under the cursor and intercepting my typing. Expected behavior is for other windows to maintain their placement when a window closes. I use sloppy focus. Otherwise, I have a relatively unaltered setup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.1-1ubuntu0.6 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 14:52:38 2023 InstallationDate: Installed on 2023-03-18 (179 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_us.ut...@cdate.utf-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2035395 Title: windows randomly raise when others close Status in xwayland package in Ubuntu: New Bug description: (I am not sure if xwayland is at fault or the session or window manager. It happens under Wayland using gnome-session and gnome-shell, but not under X.org.) When I close a window, even using ^W or ^Q, another seemingly-random window may raise to the top, possibly under the cursor and intercepting my typing. Expected behavior is for other windows to maintain their placement when a window closes. I use sloppy focus. Otherwise, I have a relatively unaltered setup. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.1-1ubuntu0.6 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 14:52:38 2023 InstallationDate: Installed on 2023-03-18 (179 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_us.ut...@cdate.utf-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2035395/+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 2035394] [NEW] browser windows get thick black border, resize badly
Public bug reported: (I am not sure if xwayland is at fault or the session or window manager or the browser apps. It happens under Wayland using gnome-session and gnome-shell and to both Firefox and Chrome browser windows, but not to any other app. These are the only browsers I use.) After using a browser for a while (both Chrome and Firefox), the transparent "halo" around one or more (but not generally all) of its windows may acquire an opaque color. This is usually an image of whatever was behind the window when the bug triggers, but eventually gets filled in as all black. Sometimes when this happens, resizing it larger and smaller clears the problem, sometimes not. Sometimes when this happens, resizing the window larger will result in the window staying the same size and place, but the border expanding into a larger black background rectangle, without the window resizing at all. Sometimes when this happens, resizing the window smaller will result in the window image being truncated without resizing, and upon resizing larger again, the window maintains its small, truncated size, sitting in the corner of a larger black rectangle. If the portion including the titlebar buttons in the upper-right gets truncated, it becomes impossible to click maximize, iconify, or close. A workaround is to open a new browser window, select all the tabs, and drag them to the new window. That window will act normally for a while (a few days?) and then may be susceptible to the bug. The windows that have this happen to them seem to be the most-used ones, so maybe it's related to the number of user window interactions or moving between monitors. I have some browser windows with tabs I use only rarely. These stay minimized most of the time and rarely if ever suffer from the problem. If it matters, I use sloppy focus. This is the only substantive change from default install. Obviously, expected behavior is not to have any of these things happen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.1-1ubuntu0.6 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 14:37:17 2023 InstallationDate: Installed on 2023-03-18 (178 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_us.ut...@cdate.utf-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2035394 Title: browser windows get thick black border, resize badly Status in xwayland package in Ubuntu: New Bug description: (I am not sure if xwayland is at fault or the session or window manager or the browser apps. It happens under Wayland using gnome- session and gnome-shell and to both Firefox and Chrome browser windows, but not to any other app. These are the only browsers I use.) After using a browser for a while (both Chrome and Firefox), the transparent "halo" around one or more (but not generally all) of its windows may acquire an opaque color. This is usually an image of whatever was behind the window when the bug triggers, but eventually gets filled in as all black. Sometimes when this happens, resizing it larger and smaller clears the problem, sometimes not. Sometimes when this happens, resizing the window larger will result in the window staying the same size and place, but the border expanding into a larger black background rectangle, without the window resizing at all. Sometimes when this happens, resizing the window smaller will result in the window image being truncated without resizing, and upon resizing larger again, the window maintains its small, truncated size, sitting in the corner of a larger black rectangle. If the portion including the titlebar buttons in the upper-right gets truncated, it becomes impossible to click maximize, iconify, or close. A workaround is to open a new browser window, select all the tabs, and drag them to the new window. That window will act normally for a while (a few days?) and then may be susceptible to the bug. The windows that have this happen to them seem to be the most-used ones, so maybe it's related to the number of user window interactions or moving between monitors. I have some browser windows with tabs I use only rarely. These stay minimized most of the time and rarely if ever suffer from the problem. If it matters, I use
[Desktop-packages] [Bug 2035391] [NEW] Terminal windows disappear when external monitors connect
Public bug reported: (I am not sure if xwayland is at fault or the session or window manager or the GNOME Terminal app. It happens under Wayland using gnome-session and gnome-shell.) When I connect external monitors (via a Thunderbolt 4 dock), sometimes GNOME Terminal windows that stay on the primary display disappear. Using the Ubuntu dock, I can see the windows in the thumbnails when I click on the Terminal app, but when I click on the thumbnail, the terminal in the lower-right corner highlights as though it is the window that was clicked; the missing window does not reappear. When I unplug the monitors, the terminals are still gone, but if I click on the thumbnails, they restore, usually in the lower-right rather than the upper-left and upper-right corners they started in. It seems only to be these two windows that vanish, not the other four terminals I have on screen. Terminal borders are contained within the primary laptop screen, but they do sometimes overlap each other or other windows, and the transparent halos (or whatever they're called) that the window manager puts around them are sometimes off-screen. The windows are on the far right screen edge and on the left flush with the right edge of the dock, and both flush with the bottom edge of the Activities bar that runs across the top of the primary display. Needless to say, my expected behavior is that they don't move or disappear when external monitors are connected, since they've never been pulled to external monitors, and that regardless, they appear when their thumbnails are clicked. In the same or a possibly related problem, some windows, notably the Thunderbird appointment reminder list, get reduced to the tiniest possible size and put on an external monitor, when one is attached. This requires finding them (usually there is a piece of the title bar left) and stretching them out. I use sloppy focus (follow pointer but keep last focused window when pointer is over background), if that matters. GNOME Terminal 3.44.0 for GNOME 42. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xwayland 2:22.1.1-1ubuntu0.6 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 12:09:08 2023 InstallationDate: Installed on 2023-03-18 (178 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_us.ut...@cdate.utf-8 SHELL=/bin/bash SourcePackage: xwayland UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xwayland (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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2035391 Title: Terminal windows disappear when external monitors connect Status in xwayland package in Ubuntu: New Bug description: (I am not sure if xwayland is at fault or the session or window manager or the GNOME Terminal app. It happens under Wayland using gnome-session and gnome-shell.) When I connect external monitors (via a Thunderbolt 4 dock), sometimes GNOME Terminal windows that stay on the primary display disappear. Using the Ubuntu dock, I can see the windows in the thumbnails when I click on the Terminal app, but when I click on the thumbnail, the terminal in the lower-right corner highlights as though it is the window that was clicked; the missing window does not reappear. When I unplug the monitors, the terminals are still gone, but if I click on the thumbnails, they restore, usually in the lower-right rather than the upper-left and upper-right corners they started in. It seems only to be these two windows that vanish, not the other four terminals I have on screen. Terminal borders are contained within the primary laptop screen, but they do sometimes overlap each other or other windows, and the transparent halos (or whatever they're called) that the window manager puts around them are sometimes off-screen. The windows are on the far right screen edge and on the left flush with the right edge of the dock, and both flush with the bottom edge of the Activities bar that runs across the top of the primary display. Needless to say, my expected behavior is that they don't move or disappear when external monitors are connected, since they've never been pulled to external monitors, and that regardless, they appear when their thumbnails are clicked. In the same or a possibly related problem, some windows, notably the Thunderbird appointment reminder list, get reduced to the tiniest possible size and put on an external monitor,
[Desktop-packages] [Bug 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
I'm also having this issue on 2 separate computers. Both have Zoiper installed as we use it at work. I do not have anydesk installed -- 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/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2012388/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 I'm also having this issue on 2 separate computers. Both have Zoiper installed as we use it at work. -- 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/2017333 Title: Some Area in Top right corner of the screen is not clickable. Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/ This link contains the visual representation and more details about the bug. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 12:10:32 2023 DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2022-04-01 (385 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: HP HP Notebook ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/17/2019 dmi.bios.release: 15.48 dmi.bios.vendor: Insyde dmi.bios.version: F.48 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 61.61 dmi.modalias: dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T44PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/2017333/+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 2015577] Re: middle click to lower window no longer works for xwayland windows
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2778 https://gitlab.gnome.org/GNOME/mutter/-/issues/2778 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2778 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2015577 Title: middle click to lower window no longer works for xwayland windows Status in Mutter: Unknown Status in mutter package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015577/+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 2015577] [NEW] middle click to lower window no longer works for xwayland windows
Public bug reported: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2015577 Title: middle click to lower window no longer works for xwayland windows Status in xwayland package in Ubuntu: New Bug description: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2015577/+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 2015493] [NEW] file chooser / screen share portal not observing dark theme
Public bug reported: I have dark theme variant set, but the file chooser / screen share portal displayed by firefox (snap) use the light theme. In kinetic it was using the dark theme but started to display light theme in lunar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Apr 6 08:43:40 2023 InstallationDate: Installed on 2019-08-17 (1328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-05 (0 days ago) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2015493 Title: file chooser / screen share portal not observing dark theme Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: I have dark theme variant set, but the file chooser / screen share portal displayed by firefox (snap) use the light theme. In kinetic it was using the dark theme but started to display light theme in lunar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Apr 6 08:43:40 2023 InstallationDate: Installed on 2019-08-17 (1328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2015493/+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 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top
i think this is maybe fixed in lunar? seems better at least with initial testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
Also affecting me. Odd keyboard studdering of characters (intermittant). Also way too slow at displaying contents of folders. I'm looking for a replacement. -- 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/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in nautilus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1996652/+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 2009435] [NEW] Xorg freeze
Public bug reported: Files application hangs when switched to from other application. Only occurs when mounted to internal HDD. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 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: ubuntu:GNOME Date: Mon Mar 6 08:50:17 2023 DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367] InstallationDate: Installed on 2020-10-24 (862 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=9db35888-ce9e-4ddd-96ab-979cf2de8c9e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-09-30 (156 days ago) dmi.bios.date: 11/13/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2006 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze jammy 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/2009435 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Files application hangs when switched to from other application. Only occurs when mounted to internal HDD. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 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: ubuntu:GNOME Date: Mon Mar 6 08:50:17 2023 DistUpgraded: 2022-09-30 11:53:10,478 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-67-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Lexa PRO [Radeon RX 550] [1da2:e367] InstallationDate: Installed on 2020-10-24 (862 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic
[Desktop-packages] [Bug 1805197] Re: cannot switching keyboard layout with xfce4-keyboard-settings
I'm still seeing the bug in a clean install of Xubuntu 22.04.1 ...with additional problems that I assume are related, such as choosing "change layout option" to be "both alt together" lets me switch from the second layout in my list to the first layout, but not from the first layout back to the second layout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/1805197 Title: cannot switching keyboard layout with xfce4-keyboard-settings Status in Xfce4 Settings: Confirmed Status in libxklavier package in Ubuntu: Confirmed Status in xfce4-settings package in Ubuntu: Triaged Bug description: This is on xubuntu 18.04: With xfce4-keyboard-settings I have loaded the keyboard layouts "English (US)" and "German". Both are listed in the "Keybord layout" table. When I change the order with [key up] or [key down] nothing happens, I still have the old keyboard layout active. To switch the layout I have to DELETE the other one! This was not the case with xubuntu 16.04: just changing the order was sufficent there. To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-settings/+bug/1805197/+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 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top
I've also noticed that the crash in https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 gets triggered by the 1pixel shift, even when sharing the full desktop screen. ** Bug watch added: Mozilla Bugzilla #1790496 https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 1997480] [NEW] maximized xwayland windows shift by 1 pixel when on top vs/ not on top
Public bug reported: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) ** Affects: xwayland (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 xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+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 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070 addresses this in gtk3 apps, can it (and/or the next gtk release) be added to the ubuntu package and the snap package that contains gtk3 (gnome-* snap?) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click Status in GTK+: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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 1986861] [NEW] pulseaudio stops accepting connections
Public bug reported: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1986861 Title: pulseaudio stops accepting connections Status in pulseaudio package in Ubuntu: New Bug description: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: 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/ubuntu/+source/pulseaudio/+bug/1986861/+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 1971744] [NEW] external monitor static image after unlocking session
Public bug reported: Occasionally after unlocking a locked gnome session, the image on my external monitor is "frozen" -- it displays the unlocked desktop as of the lock/unlock time, but does not update (no mouse cursor etc). Started noticing this post-jammy release. Unplugging and replugging the monitor fixes it. Internal laptop display does not have the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 09:17:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (992 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (47 days ago) ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1971744 Title: external monitor static image after unlocking session Status in gnome-shell package in Ubuntu: New Bug description: Occasionally after unlocking a locked gnome session, the image on my external monitor is "frozen" -- it displays the unlocked desktop as of the lock/unlock time, but does not update (no mouse cursor etc). Started noticing this post-jammy release. Unplugging and replugging the monitor fixes it. Internal laptop display does not have the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 09:17:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (992 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971744/+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 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
is there a way for users to re-enable wayland / override the DISABLE_WAYLAND=1 setting recently set in the snap? -- 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/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) Status in Mozilla Firefox: New Status in Mutter: Unknown Status in firefox package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) A similar behavior can also be observed in gedit, nautilus and other GNOME applications whether they are confined or not (while snapped ones seems to underline the issue more) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+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 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
seeing the same behavior with the -non-free version too, does it need a separate rebuild? ** Also affects: intel-media-driver-non-free (Ubuntu) Importance: Undecided Status: New -- 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/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Committed Status in intel-media-driver-non-free package in Ubuntu: New Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1966593] [NEW] gnome session locks when disconnecting external screen
Public bug reported: After upgrade to jammy, noticed that the gnome session locks the screen when I unplug an external screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Mar 27 08:49:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (953 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (8 days ago) ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1966593 Title: gnome session locks when disconnecting external screen Status in gnome-shell package in Ubuntu: New Bug description: After upgrade to jammy, noticed that the gnome session locks the screen when I unplug an external screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Mar 27 08:49:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (953 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966593/+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 1965968] [NEW] post jammy update, black/flickering screen on boot
Public bug reported: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: plymouth (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 plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in plymouth package in Ubuntu: New Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: 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/ubuntu/+source/plymouth/+bug/1965968/+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 1965648] Re: Autorotate initiates, but doesn't reset
One more piece of information in a wayland session: If I fully fold the device into tablet mode, then I can rotate back and forth successfully, it only gets stuck if I go back into laptop mode. -- 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/1965648 Title: Autorotate initiates, but doesn't reset Status in mutter package in Ubuntu: New Bug description: In jammy I can get mutter's auto-rotate to switch to portrait mode ("right-up") by rotating the device (this only worked in impish if I installed the autorotate gnome-shell extension). However, putting it back into "normal" orientation doesn't put the screen back in landscape mode. Flipping it around ("left-up") does swap to the reverse portrait mode, but still can't get back to "normal" afterward. running `monitor-sensor` does show the accelerometer orientation change events (including the "normal" ones) triggering properly, just the desktop doesn't respond. Plugging in an external monitor does seem to trigger the desktop to go back to normal landscape mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:41:42 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1963264] Re: Screencast not recording
I had pipewire-media-session libpipewire-0.3-common installed fine after an upgrade from impish->jammy, but still had to remove the libgstpipewire so, and reinstall the package to get gstreamer to recognize the pipewiresrc element -- 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/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: Invalid Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+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 1965648] Re: Autorotate initiates, but doesn't reset
The bug does not appear to occur under Xorg sessions: - Ubuntu on Xorg: rotated back and forth numerous times successfully - Ubuntu: rotated back and forth once successfully and then got stuck in portrait mode - Gnome on Xorg: rotated back and forth numerous times successfully - Gnome: rotated back and forth once successfully and then got stuck in portrait mode ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+attachment/5571502/+files/journal.txt ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1965648 Title: Autorotate initiates, but doesn't reset Status in mutter package in Ubuntu: New Bug description: In jammy I can get mutter's auto-rotate to switch to portrait mode ("right-up") by rotating the device (this only worked in impish if I installed the autorotate gnome-shell extension). However, putting it back into "normal" orientation doesn't put the screen back in landscape mode. Flipping it around ("left-up") does swap to the reverse portrait mode, but still can't get back to "normal" afterward. running `monitor-sensor` does show the accelerometer orientation change events (including the "normal" ones) triggering properly, just the desktop doesn't respond. Plugging in an external monitor does seem to trigger the desktop to go back to normal landscape mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:41:42 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
I do occasionally get crashes when attempting to rearrange tabs as well. The crashes happen both in .deb & snap versions of firefox though? -- 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/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+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 1965647] Re: pulseaudio gets stuck after launching firefox
seems like pulse was fighting with pipewire; not sure what I did to clean it up but appears to be working better now -- 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/1965647 Title: pulseaudio gets stuck after launching firefox Status in pulseaudio package in Ubuntu: New Bug description: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: 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/ubuntu/+source/pulseaudio/+bug/1965647/+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 1965648] [NEW] Autorotate initiates, but doesn't reset
Public bug reported: In jammy I can get mutter's auto-rotate to switch to portrait mode ("right-up") by rotating the device (this only worked in impish if I installed the autorotate gnome-shell extension). However, putting it back into "normal" orientation doesn't put the screen back in landscape mode. Flipping it around ("left-up") does swap to the reverse portrait mode, but still can't get back to "normal" afterward. running `monitor-sensor` does show the accelerometer orientation change events (including the "normal" ones) triggering properly, just the desktop doesn't respond. Plugging in an external monitor does seem to trigger the desktop to go back to normal landscape mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:41:42 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1965648 Title: Autorotate initiates, but doesn't reset Status in mutter package in Ubuntu: New Bug description: In jammy I can get mutter's auto-rotate to switch to portrait mode ("right-up") by rotating the device (this only worked in impish if I installed the autorotate gnome-shell extension). However, putting it back into "normal" orientation doesn't put the screen back in landscape mode. Flipping it around ("left-up") does swap to the reverse portrait mode, but still can't get back to "normal" afterward. running `monitor-sensor` does show the accelerometer orientation change events (including the "normal" ones) triggering properly, just the desktop doesn't respond. Plugging in an external monitor does seem to trigger the desktop to go back to normal landscape mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:41:42 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+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 1965647] [NEW] pulseaudio gets stuck after launching firefox
Public bug reported: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jbarnett 3283 F wireplumber - /dev/snd/controlC0: jbarnett 3283 F wireplumber - jbarnett 7684 F pulseaudio - /dev/snd/seq:jbarnett 3278 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC1: jbarnett 3283 F wireplumber + /dev/snd/controlC0: jbarnett 3283 F wireplumber + jbarnett 7684 F pulseaudio + /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out "Audio device got stuck!" + + killing pulseaudio (and having systemd user session restart it) restores + sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate:
[Desktop-packages] [Bug 1965638] [NEW] Can't drag to reorder tabs
Public bug reported: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 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 (945 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 wlp2s0 scope link metric 1000 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.6.86 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:365 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=98.0.1/20220313140707 (Out of date) RunningIncompatibleAddons: False Snap.Changes: ID Status Spawn Ready Summary 495 Done2022-03-19T13:27:26-07:00 2022-03-19T13:30:56-07:00 Remove "firefox" snap 496 Done2022-03-19T13:33:19-07:00 2022-03-19T13:34:07-07:00 Install "firefox" snap SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965638 Title: Can't drag to reorder tabs Status in firefox package in Ubuntu: New Bug description: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 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 (945 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 wlp2s0 scope link metric 1000
[Desktop-packages] [Bug 1934243] Re: thunderbird drag-n-drop move messages fails on Wayland
Not sure if same bug but I'm consistently having problems dragging attachments onto Thunderbird compose windows w/21.10 and Wayland (Thunderbird running as Xwayland). See further description of behavior here https://askubuntu.com/questions/1396768/drag-drop-to-thunderbird-works- poorly-with-wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1934243 Title: thunderbird drag-n-drop move messages fails on Wayland Status in thunderbird package in Ubuntu: Confirmed Bug description: On Ubuntu 21.04 when I use Thunderbird, drag-n-drop sometimes fails to work when moving messages. I attempt to drag a message (or a collection of messages) from one folder to another, but the attempt to drag fails and nothing happens. This occurs when I use the default (Wayland) login. The problem does not occur when I use X.org login. The problem is intermittent; it may take a few moves for the failures to start occurring. I reported this issue in bug#1934185 but that bug report is primarily about Ubuntu Dock and I was asked to file a separate bug report about Thunderbird. To file this bug report, I ran "ubuntu-bug" under X.org but the bug actually occurs only under Wayland. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.11.0+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eggert1613919 F pulseaudio /dev/snd/controlC1: eggert1613919 F pulseaudio BuildID: 20210528153351 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 00:21:11 2021 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd} InstallationDate: Installed on 2018-08-03 (1062 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev enp5s0 proto static metric 100 169.254.0.0/16 dev enp5s0 scope link metric 1000 192.168.0.0/24 via 192.168.1.8 dev enp5s0 proto static metric 1 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.9 metric 100 192.168.86.0/24 via 192.168.1.7 dev enp5s0 proto static metric 1 MostRecentCrashID: bp-5d346b68-65ef-4a14-bd19-5d5520200408 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.11.0/20210528153351 RunningIncompatibleAddons: True SourcePackage: thunderbird SubmittedCrashIDs: bp-5d346b68-65ef-4a14-bd19-5d5520200408 UpgradeStatus: Upgraded to hirsute on 2021-06-03 (27 days ago) dmi.bios.date: 11/28/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3108 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS 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.:bvr3108:bd11/28/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1934243/+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 1950925] Re: alt-tab doesnt work anymore after upgrade to 21.10
Hi all, This also affects me, starting with the update to 21.04 and continuing with the 21.10 update. alt does nothing, super switches between applications. I haven't installed any Gnome extensions. ~$ gsettings get org.gnome.desktop.wm.keybindings switch-applications ['Tab'] ~$ gsettings get org.gnome.desktop.wm.keybindings switch-windows ['Tab'] Thank you for the work!! -Joe -- 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/1950925 Title: alt-tab doesnt work anymore after upgrade to 21.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I want to swicth windows with alt-tab. This worked until before I just upgraded from 21.4 to 21.10. Now nothing happens anymore. In Settings -> Keyboard -> Customize Shortcuts -> Navigation the Shortcut for "Switch Windows" is set to alt-tab, but pressing these doesnt do anything. Super-Tab works, but it switches applications, not windows. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 15 00:47:15 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-12 (581 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 40.5-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-11-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950925/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
For anyone needing a fix for nonfunctional alt-tab switching, at least for Ubuntu/Gnome you can remap in keyboard shortcuts to have the "direct windows switching", which by default is alt-esc, to be instead alt-tab. It is slightly different behavior -- more visual noise -- but fulfills the same essential function. -- 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/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1945518] [NEW] The WidevineCdm plugin has crashed
*** This bug is a duplicate of bug 1945100 *** https://bugs.launchpad.net/bugs/1945100 Public bug reported: Watching Widevine content (eg netflix, hbomax, etc) on the .deb package of firefox in impish has recently stopped working. Get a "The WidevineCdm plugin has crashed" message at the top of the browser window. Get the same thing when running in --safe-mode as well. Appears to work fine on the snap package though. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 92.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 52134 F pulseaudio BuildID: 20210922161155 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Wed Sep 29 10:56:50 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 (774 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.240 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:358 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=92.0.1/20210922161155 RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-09-16 (13 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:sku080D: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. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** This bug has been marked a duplicate of bug 1945100 Widevine violates the sandbox and crashes -- 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/1945518 Title: The WidevineCdm plugin has crashed Status in firefox package in Ubuntu: New Bug description: Watching Widevine content (eg netflix, hbomax, etc) on the .deb package of firefox in impish has recently stopped working. Get a "The WidevineCdm plugin has crashed" message at the top of the browser window. Get the same thing when running in --safe-mode as well. Appears to work fine on the snap package though. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 92.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 52134 F pulseaudio BuildID: 20210922161155 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Wed Sep 29 10:56:50 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 (774 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.240 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @
[Desktop-packages] [Bug 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
** Patch added: "0001-editor-fix-vpn-tree-sort-parameters.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+attachment/5512368/+files/0001-editor-fix-vpn-tree-sort-parameters.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
** Patch added: "0001-editor-fix-crash-when-evaluating-secondaries.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+attachment/5512367/+files/0001-editor-fix-crash-when-evaluating-secondaries.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
** Patch added: "0001-c-e-fix-initializing-drop-down-list-for-connection.s.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+attachment/5512366/+files/0001-c-e-fix-initializing-drop-down-list-for-connection.s.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
Attaching the patches I've used to test the fix. I've generated these patches via `git format-patch -1 HASH` from upstream for each of the above listed commit hashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
After some experimentation I have found that applying the following commits from the upstream 1.22 version of the pacakge to the focal/devel branch of network-manager-applet appears to fix the bug. 1. `768eb7dfa974bd3255e0062b1e9f191b731aefbe` c-e: fix initializing drop-down-list for connection.secondaries 2. `da6b2bb94250d8ffb218caf921c9df8c394372d4` editor: fix crash when evaluating secondaries 3. `8183932d985e4ca7c17bafb2cbaddb1ed5d5d6b8` editor: fix vpn tree sort parameters (the final commit I added only to simplify my debugging, I have not tested without it) I have no prior experience with debian or ubuntu package contributions, so I'm not entirely sure how to contribute these potential backported changes as patches to the package. I would very much welcome any suggestions. Please note that as these patches are just backports of specific commits from upstream they would not be necessary if the entire 1.22 version of the package could be made to work on focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
I started experimenting with Xubuntu 21.04 hirsute I've noted the following things: 1. The default hirsute install currently installs newer versions of network-manager dependency packages (1.30.0-1ubuntu3) with the sole exception being network-manager-gnome 2. The default hirsuite installed version of network-manager-gnome is 1.18.0-1ubuntu2 which is very similar in version to the 1.18.24 in Xubuntu 20.04.02 When network-manager-gnome-1.18.0 is installed in hirsute my bug is replacable. If I upgrade to network-manager-gnome-1.22.0 from impish (which I can do on hirsute thanks to the higher dependency package versions) the bug disappears and everything appears to work. Upstream has also seemed to imply in my original bug report to them that work had been done as of 1.22 of the upstream packages which might have fixed my bug. My experience seems to suggest that my problem is already solved as of network-manager-gnome-1.22.0, but it looks like 1.22 hasn't been backported to focal. What would it take to backport 1.22.0 to focal for those of us stuck on LTS releases? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1936955] [NEW] firefox 90 stopped remembering window size
Public bug reported: since upgrading to firefox 90, all newly opened firefox windows are very small and need to be manually resized to a usable size. prior to firefox 90, new windows would be the same size as the last opened window. running on gnome on wayland with fractional scaling enabled, if that matters. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2823 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Jul 20 09:23:39 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 (703 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.0.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.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.25 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=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-07-08 (11 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 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.15.1:bd03/25/2021:br1.15: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. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1936955 Title: firefox 90 stopped remembering window size Status in firefox package in Ubuntu: New Bug description: since upgrading to firefox 90, all newly opened firefox windows are very small and need to be manually resized to a usable size. prior to firefox 90, new windows would be the same size as the last opened window. running on gnome on wayland with fractional scaling enabled, if that matters. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2823 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Jul 20 09:23:39 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 (703 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.0.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.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.25 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=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs:
[Desktop-packages] [Bug 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
For anyone who may not want to download the full ova just to see the bug, I've created a screen recording of the bug as I experience it. It can be viewed here: https://www.youtube.com/watch?v=RVFoaiHCto8 >From the video description to give some context to what I'm demonstrating in the video: A demonstration of an nm-connection-editor bug I'm experiencing. For some reason the saved VPN does not persist across future saves even if I change nothing in the dialog. Simply saving the dialog is enough to trick it into swapping behind the scenes. This video demonstrates 2 things: 1. The first demo shows that when the VPN selected is "Vancouver" then every time the dialog is saved the stored VPN is changed. 2. When Vancouver is selected it rotates only through "Vancouver", "US West", and "Corp - UK London" 3. If either of the remaining 2 VPNs are chosen ("Corp - Hong Kong" or "US East") then they do NOT exhibit the bug. 4. Swapping back to any of the original 3 causes the bug to express again. To test the bug locally it's enough to create 5 VPNs with the same names as mine. They need not be fully functional as you don't need to connect to the VPN to trigger the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] Re: network-manager-applet: stored auto connect VPN gets changed when viewing settings
I've created a virutal machine which expresses the bug in Xubuntu 20.04.02 from a fresh install. You'll need to log in as the user "user" with the password "password". In order to experience the bug you'll need to change and save the VPN once, then you should be able to follow the instructions above. Hopefully having this virtual machine will make it a little easier to identify the cause. I've so far been unable to identify what could possibly be causing it. The VM export in ova format can be found here: http://files.coderjoe.net/Xubuntu.ova -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+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 1935604] [NEW] network-manager-applet: stored auto connect VPN gets changed when viewing settings
Public bug reported: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS
Like napsty above, I'm using LM 19.3. I fixed the problem with printing by adding the "net_admin caps" correction, per Jamie. That worked fine, but now the default media player in LM 19.3 won't play mpg4 video files. If I remove the "net_admin caps" correction, the ability to play mpg4 files is restored. Suggestions? Thanks! Joe Henley -- 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/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined
[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
ok that makes sense, I think opening links from slack (electron/x11) was likely the culprit that "poisoned" the running firefox instance -- 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: Confirmed Status in firefox package in Ubuntu: In Progress 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 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
Thanks Olivier. That bug report looks related but seems more like it never works, vs/ works for a little while and then stops working? But adding the MOZ_DBUS_REMOTE flag that it mentions seems to fix the issue when running with MOZ_ENABLE_WAYLAND in limited testing so far. -- 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: Unknown Status in firefox package in Ubuntu: New 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 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
Yes, commenting out the MOZ_ENABLE_WAYLAND line appears to fix the issue. With MOZ_ENABLE_WAYLAND=1, initial link requests work, but after a short while start getting the firefox is running but not responding dialog. Without it, link requests work even after a while. ** Changed in: firefox (Ubuntu) Status: Incomplete => 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/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in firefox package in Ubuntu: New 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/ubuntu/+source/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 1921931] [NEW] Opening links results in "Firefox is already running, but is not responding"
Public bug reported: 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. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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 firefox package in Ubuntu: New 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:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Works fine after installing hwe kernel using apt.(5.8.0.44 Ubuntu 20.04 Lenovo R7000P) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Update (based on #296) = The latest kernel tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has the complete solution to fix this bug. So we can expect kernel v5.11 to fix this issue without any additional work. Before the release of v5.11, you are suggested to use #189 to save your touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd driver is built into the initramfs. So you have to rebuild the initramfs after replacing the old module with new one. On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs -u`. The complete solution is three patches, - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce filter setting in IRQ type setting") - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way to disable debounce filter") - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into account debounce settings") The first two patches has reached the stable tree. If the last one is also backported to LTS kernel, you won't need to install kernel 5.11. But I don't know when this will happen. Original bug report === Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Lenovo R7000P Laptop. Sadly, still not a good solution. The touch pad now works with kernel 5.11.0, but it has problem with Nvidia GPU and the brightness control is not working. I can have Nvidia GPU working and manually do some fixes to enable brightness control with 5.8.0, though touch pad is not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Update (based on #296) = The latest kernel tree (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) has the complete solution to fix this bug. So we can expect kernel v5.11 to fix this issue without any additional work. Before the release of v5.11, you are suggested to use #189 to save your touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd driver is built into the initramfs. So you have to rebuild the initramfs after replacing the old module with new one. On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs -u`. The complete solution is three patches, - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce filter setting in IRQ type setting") - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way to disable debounce filter") - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into account debounce settings") The first two patches has reached the stable tree. If the last one is also backported to LTS kernel, you won't need to install kernel 5.11. But I don't know when this will happen. Original bug report === Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date:
[Desktop-packages] [Bug 1906283] Re: Scroll wheel stopped working on message contents in Geary
seems to have fixed itself somehow. ** Changed in: geary (Ubuntu) Status: New => Invalid ** Changed in: webkit2gtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1906283 Title: Scroll wheel stopped working on message contents in Geary Status in geary package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Invalid Bug description: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 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.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1906283/+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 1906283] [NEW] Scroll wheel stopped working on message contents in Geary
Public bug reported: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 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.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) ** Affects: geary (Ubuntu) Importance: Undecided Status: New ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages wayland-session ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Scroll wheel stopped working on message contents + Scroll wheel stopped working on message contents in Geary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1906283 Title: Scroll wheel stopped working on message contents in Geary Status in geary package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 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.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1906283/+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 1686895] Re: Gnome Night Light stays warmer after overnight suspend
Hi All, I am experiencing this too. After my monitors have lost the display port signal from my machine (either during suspension or blank screen), changing the nightlight settings is no longer possible and the last used setting is permanently engaged. Rebooting fixes the issue, however. I am on Ubuntu 20.04.1 LTS and am using three monitors in series via MST. Many thanks for any guidance. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1686895 Title: Gnome Night Light stays warmer after overnight suspend Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Won't Fix Bug description: Gnome Night Light is scheduled from sunset to sunrise. In the evening, the screen color turns warmer as expected. Going to bed, the computer is put in suspend mode. The next day, after sunrise, the warm color is still on and stays on. Turning Gnome Night Light off (and on) does not help. The Night Light settings clearly show the correct time of day in the slider in the blue color section. * Ubuntu 17.04 * gnome-control-center: Installed: 1:3.24.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+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 602809] Re: add Mouse Click Debounce Feature?
FWIW I have been plagued with this same issue for a long time now and the libinput_debounce_time.patch above* fixes the problem for me. Obviously hard coding these values is a bad idea -- will this ever get fixed properly? * I had to adjust it to get it to apply on my LM20 system (libinput-1.15.5), and I used 60 ms and 30 ms instead of 100/50. Many thanks to Yei Gei (yzgyzg) for posting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/602809 Title: add Mouse Click Debounce Feature? Status in xserver-xorg-input-evdev: New Status in xserver-xorg-input-evdev package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Model: bonp3 OS: Ubuntu 10.04 LTS When I single click the mouse (external USB Mouse - Mouse Pad disabled) half the time the system responds as though I have double clicked the mouse. I try 2 different USB mouse units and it still does this. I am running Ubuntu 10.04 on a separate PC that does not have this mouse problem. So I am thinking this problem is a System76 driver issue??? It's annoying. :( To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/602809/+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 1901829] Re: thunderbird fails to open, xml parse error
Hi there. I figured out, that after removing the language packets thunderbird-locale-en 1:78.3.3+build1-0ubuntu0.20.10.1 thunderbird-locale-en-gb thunderbird-locale-de installed from this source http://ppa.launchpad.net/ubuntu-mozilla- security/ppa/ubuntu/ and reinstalling the 1:78.3.2+build1-0ubuntu1 packets from the official Source, fixed the problem in my case. maybe it helps?! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1901829] Re: thunderbird fails to open, xml parse error
Olivier, unfortunally it does not work for me. like MK1Softie suggest: if i remove my .thunderbird folder in the home directory, its starting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1901829] Re: thunderbird fails to open, xml parse error
here it is. :) ** Attachment added: "tb-profile-extensions.zip" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+attachment/5428624/+files/tb-profile-extensions.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1901829] Re: thunderbird fails to open, xml parse error
safe mode does not working in neither 4 me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1901829] Re: thunderbird fails to open, xml parse error
** Attachment added: "tb-profile-extensions.zip" https://bugs.launchpad.net/bugs/1901829/+attachment/5428622/+files/tb-profile-extensions.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1901778] Re: Thunderbird crashes on start up
in my case, tb does not start in -safe-mode neither. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901778 Title: Thunderbird crashes on start up Status in thunderbird package in Ubuntu: Confirmed Bug description: When I try to start up Thunderbird (v 1:78.3.2), a information box appears with this message : "key id="openLightningKey"" This bug happened since yesterday, with Ubuntu 20.10. It didn't happen at the beginning when I have updated to 20.10 If I start Thunderbird by a command in the Terminal, I get these messages : [calBackendLoader] Using Thunderbird's libical backend Extension error: Error while loading 'jar:file:///usr/lib/thunderbird/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND) resource://gre/modules/Extension.jsm:570 :: readJSON/https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901778/+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 1898080] [NEW] Dsiplay artifacts in groovy when moving windows around
Public bug reported: In a wayland session with fractional scaling (175% on laptop screen), seeing weird visual artifacts around windows when moving them around, see attached video for an example. Also see similar artifacts near terminal prompt, gtk file chooser when mousing over items, and maybe other locations too? artifacts do not appear on external monitor set to 100% scaling, or on laptop screen if scaling is set to 100%, 150%, or 200%. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PXL_20201001_164915228.mp4" https://bugs.launchpad.net/bugs/1898080/+attachment/5416237/+files/PXL_20201001_164915228.mp4 -- 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/1898080 Title: Dsiplay artifacts in groovy when moving windows around Status in mutter package in Ubuntu: New Bug description: In a wayland session with fractional scaling (175% on laptop screen), seeing weird visual artifacts around windows when moving them around, see attached video for an example. Also see similar artifacts near terminal prompt, gtk file chooser when mousing over items, and maybe other locations too? artifacts do not appear on external monitor set to 100% scaling, or on laptop screen if scaling is set to 100%, 150%, or 200%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1898080/+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 1886351] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while
Public bug reported: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1410 F pulseaudio /dev/snd/pcmC0D0c: joe1410 F...m pulseaudio /dev/snd/pcmC0D0p: joe1410 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 19:23:02 2020 InstallationDate: Installed on 2020-06-02 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 17:44:12 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.26' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:17 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:56 joe systemd[900]: pulseaudio.service: Succeeded. Jul 05 17:45:05 joe systemd[900]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L745 dmi.product.sku: PSK0YU-01V00E dmi.product.version: PSK0YU-01V00E dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886351 Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USER
[Desktop-packages] [Bug 1884126] Re: Trying to add google account fails with AUTH-1140
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126 https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126 ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1884126 Title: Trying to add google account fails with AUTH-1140 Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+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 1884126] [NEW] Trying to add google account fails with AUTH-1140
Public bug reported: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1884126 Title: Trying to add google account fails with AUTH-1140 Status in gnome-online-accounts package in Ubuntu: New Bug description: Trying to add a google account that redirects to another site for sign in results in a window with the following error: {"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is an invalid header value that can't be parsed."}]} ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jun 18 11:41:17 2020 InstallationDate: Installed on 2019-08-17 (306 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1884126/+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 1882481] Re: A dialog box stays on desktop and does not go away
Thank you, attached is a screenshot and also journal.txt. Regards, Joe On 6/8/20 12:11 AM, Daniel van Vugt wrote: > This sounds like bug 1824874. To help us check that please: > > 1. Provide a screenshot or photo of the problem; and > > 2. After the dialog has appeared run: > >journalctl -b0 > journal.txt > >or if you had to reboot then run: > >journalctl -b-1 > prevboot.txt > >and attach the resulting text file here. > > > ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > ** Attachment added: "Screenshot from 2020-06-08 14-02-35.png" https://bugs.launchpad.net/bugs/1882481/+attachment/5381742/+files/Screenshot%20from%202020-06-08%2014-02-35.png ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1882481/+attachment/5381743/+files/journal.txt -- 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/1882481 Title: A dialog box stays on desktop and does not go away Status in gnome-shell package in Ubuntu: Incomplete Bug description: Upon rebooting, I get dialog box Authentication Required Authentication is required to start 'cups.service'. I can type in the password and click Authenticate, but then nothing happens. I can't see under the box. I can't move the box, can't cancel the dialog. But, I can click on where I know the underneath icon to be and that click is accepted and the program in question runs. It appears the display manager does not remove the image after it is done with the dialog. I have recently done a clean install of 20.04. There is a screenshot in this Stack Exchange post: https://askubuntu.com/questions/1242999/dialog-box-does-not-accept-input-stays-on-top-and-hides-everything-under-it-ub ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 23:10:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 3.3-19, 5.4.0-31-generic, x86_64: installed amdgpu, 3.3-19, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Radeon RX 580 [1462:8a92] InstallationDate: Installed on 2020-05-12 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=ebb08f84-7501-4461-a5c4-c69c3c25d9b0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0804:bd11/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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/gnome-shell/+bug/1882481/+subscriptions -- Mailing list: https://
[Desktop-packages] [Bug 1866926] Re: usb_modeswitch does not switch modems (remain visible as mass storage)
I just spent a few hours trying to figure out why my Alcatel modem wasn't establishing a connection...and ran across this bug. Thank you Hanno for the workaround! I uninstalled the usb_modeswitch package and installed the one from Debian Bullseye, and my modem shows up now! After adding entries to my netplan configuration to enable DHCP, I can access the interfaces. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1866926 Title: usb_modeswitch does not switch modems (remain visible as mass storage) Status in usb-modeswitch package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu focal fossa development branch the usb_modeswitch does not seem to work any more on a Toshiba laptop. Two modems I have D-Link DWM-156 and Huawei E3372 show up as drives and stay like that until I use "Eject" in Gnome or explicitly use usb_modeswitch from the terminal. I have a strong feeling that it may either be related to Gnome or hardware. On another Dell laptop with Kubuntu focal fossa development, both modems connect automatically. /var/log/usb_modeswitch.log ends with: Warning: SCSI attribute "ref" not readable. Check class of first interface ... Device is in istall mode. No access to interface 8. Exit Up until and including the "ref" not readable is exactly the same as on Kubuntu @ Dell. Yet on Kubuntu I get plenty of successful config logs after that and on Ubuntu @ Toshiba I don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1866926/+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 1868155] Re: Banner text and user list functionality seem broken
Sorry I somehow missed your message for a month ago, Sebastien. It seems I missed a notification about it somehow. That said, all seems to be working now. I haven't tried it in some time, but the banner text is now displaying as it should. We should be able to close out this issue. Thank you. -- 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/1868155 Title: Banner text and user list functionality seem broken Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 14:33:30 2020 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868155/+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 1868155] Re: Banner text and user list functionality seem broken
Sorry for taking some time to reply, but I have filed the bug as requested. https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2472 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2472 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2472 -- 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/1868155 Title: Banner text and user list functionality seem broken Status in gnome-shell package in Ubuntu: New Bug description: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 14:33:30 2020 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868155/+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 1868155] [NEW] Banner text and user list functionality seem broken
Public bug reported: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 14:33:30 2020 InstallationDate: Installed on 2020-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1868155 Title: Banner text and user list functionality seem broken Status in gdm3 package in Ubuntu: New Bug description: Hello, I am testing out what will become Ubuntu 20.04, and features that are useful or simply mandatory in an enterprise environment currently do not work. These features are the ability to utilize a login banner, as well as disable the user list on the login screen. For instance, even after enabling org.gnome.login-screen -> banner- message-enable and setting banner text via org.gnome.login-screen -> banner-message-text, there is no banner text present on the login screen. If you blink, you can maybe see it for a split second upon submitting the user's password, but this is not at all useful for scenarios where a user must comply with certain terms before logging into a workstation. Also, it seems that org.gnome.login-screen -> disable-user-list currently has no effect, as it will always show my user when starting the machine, instead of having an empty username field that must be populated. Either these are bugs, or there is some new way to achieve this functionality. If there is a new way to achieve this functionality, please let me know and then close this issue. Otherwise, I think that this all needs addressed. This used to work before the recent login/lock screen changes that were brought in when GNOME 3.36 was brought into the build. (Although my output below says that GNOME shell is 3.35.91, actually.) Some more details: I am currently using the 2020-03-08 daily-live ISO from cdimage.ubuntu.com . Other requested information: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ gnome-shell --version GNOME Shell 3.35.91 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Interesting that I didn't see this in eoan, but did once upgrading to focal. appears the "Highlight current line" option default changed to true maybe? -- 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: New Status in gtksourceview4 package in Ubuntu: Confirmed 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 1867819] [NEW] Dark theme current line highlight hard to read
Public bug reported: In focal, with a dark theme (adwaita-dark), the current line highlight in almost the same color as the text, making it very hard to read. see screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.0-3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 17 11:28:29 2020 InstallationDate: Installed on 2019-08-17 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-03-06 (11 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "Screenshot from 2020-03-17 11-28-41.png" https://bugs.launchpad.net/bugs/1867819/+attachment/5338089/+files/Screenshot%20from%202020-03-17%2011-28-41.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1867819 Title: Dark theme current line highlight hard to read Status in gedit package in Ubuntu: New Bug description: In focal, with a dark theme (adwaita-dark), the current line highlight in almost the same color as the text, making it very hard to read. see screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.0-3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 17 11:28:29 2020 InstallationDate: Installed on 2019-08-17 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-03-06 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1867819/+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 1866851] Re: lock screen scaled down backgound image in top left corner
Looks like already reported, linked to existing bug ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2239 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1866851 Title: lock screen scaled down backgound image in top left corner Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866851/+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 1866851] [NEW] lock screen scaled down backgound image in top left corner
Public bug reported: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "IMG_20200310_073917.jpg" https://bugs.launchpad.net/bugs/1866851/+attachment/5335362/+files/IMG_20200310_073917.jpg ** Description changed: - The new lock screen in gnome 3.26 looks strange, as if the blurred + The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) -- 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/1866851 Title: lock screen scaled down backgound image in top left corner Status in gnome-shell package in Ubuntu: New Bug description: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866851/+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 1865314] [NEW] Suggest removal of xkeystone
Public bug reported: Originally posted this as a question https://answers.launchpad.net/ubuntu/+question/689060 and was directed here. x11-xserver-utils includes the script /usr/bin/xkeystone xkeystone is a nickle script, and x11-xserver-utils does not depend on nickle, and even if you install nickle the script fails with a massive amount of syntax errors. (as tested with both bionic and focal packages). It's not clear to me what xkeystone is supposed to do - there's no man page or any documentation I could find. The only thing I was able to find are various threads where other distros remove this binary, so I suggest we remove it from ubuntu as well. ** Affects: x11-xserver-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1865314 Title: Suggest removal of xkeystone Status in x11-xserver-utils package in Ubuntu: New Bug description: Originally posted this as a question https://answers.launchpad.net/ubuntu/+question/689060 and was directed here. x11-xserver-utils includes the script /usr/bin/xkeystone xkeystone is a nickle script, and x11-xserver-utils does not depend on nickle, and even if you install nickle the script fails with a massive amount of syntax errors. (as tested with both bionic and focal packages). It's not clear to me what xkeystone is supposed to do - there's no man page or any documentation I could find. The only thing I was able to find are various threads where other distros remove this binary, so I suggest we remove it from ubuntu as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1865314/+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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
I can possibly try 19.10 later, however at the moment I only have my LTS laptop to test with. Just to ensure we've covered any variations, here is a redacted version of my connection file, in case I have missed anything. [connection] id=Vxxx uuid=---- type=vpn permissions=user::; timestamp=1572967683 [vpn] auth=SHA512 ca=/home//.cert/nm-openvpn/xxx-ca.pem cert=/home//.cert/nm-openvpn/xxx-cert.pem cert-pass-flags=0 cipher=AES-256-CBC comp-lzo=adaptive connection-type=password-tls dev=tun key=/home//.cert/nm-openvpn/xxx-key.pem password-flags=2 remote=1.vpn..xxx remote-cert-tls=server reneg-seconds=604800 ta=/home//.cert/nm-openvpn/xxx-tls-auth.pem ta-dir=1 username=xx service-type=org.freedesktop.NetworkManager.openvpn [ipv4] dns-priority=50 dns-search= method=auto never-default=true [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto -- 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/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
Did you ensure that the connection was set for "use only for resources on the connection"? (I believe this may be ipv4.never-default=yes setting in nmcli... and only bring it up because you do not mention it.) I also think the negative DNS priority might be historical, no longer needed. (I just noticed mine was set to 50, which I believe is default for VPN connections now) I should also note that if the never-default is set to "no"... I *will* see the DNS server, however the routing is then incorrect as the VPN concerned doesn't provide public routes. So to be clear... never-default needs to be set to yes... DNS we expect is from DHCP options sent from the VPN server, and the problem is that you will see NO DNS servers for tun0 when you run the 'systemd-resolve --status' command -- 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/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
1) Add an openvpn connection, which emits DHCP DNS servers, and is flagged "use only for resources on this connection" 2) Add a negative dns_priority to the connection via CLI or editing the connection Prior to the change, this worked fine, you could connect, and the indicated DNS server would become prioritised. After the change, this no longer works, and networkmanager will not associate a DNS server to the connection at all. -- 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/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
3.34.1+git20191107-1ubuntu1~19.10.1 appears to fix the issue here. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Fix Committed Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+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 1851407] [NEW] NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
Public bug reported: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: New Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
1.10.6-2ubuntu1.2 has cause a regression in functionality. Anyone using a "split" VPN, where there is no default route, AND wish to have DNS services supplied by the server to be honoured, via use of the ipv4.dns-priority parameter, will have this broken. This is a bit of a sore point considering the hoops one has to jump through to make this work at all. Reverting to previous version restores functionality. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1851146] [NEW] No Virtual Terminals
Public bug reported: I'll start this bug report with my first disclaimer: I'm filing this report from a fixed system. The original system that I'm going to reference has been installed over with the current system I'm filing this report from. The first install was UEFI, minimal install, not connected to the internet during installation. Now, I'll continue with my story. So, when doing the first install, I realized I had screwed up my username when doing the install. But you can't do a lot of the 'usermod' commands from the user you're logged in as. Since I was having to log in as a regular user, and then run 'sudo usermod', it was stating that the user I was trying to modify was currently logged in. So I logged out, and then attempted to switch to a tty, as I didn't need a graphical login for root. When trying to access virtual TTYs from Ctrl+Alt+F{3,4,5,6}, there were no terminals to access. I did some googling and didn't find anything directly related. Most were related to either accessing virtual terminals, or getting back to a graphical desktop if you mistakenly get to a vtty. So I took to IRC (#ubuntu on freenode). After someone did a '!tty' to really rub salt in the wound, someone recommended that I try uncommenting 'GRUB_TERMINAL=console' and regenerating grub.cfg, I took them up on the offer. So I open /etc/default/grub, and scroll down to that line. I immediately see it says 'grub-pc only'. I knew my install was UEFI, but since it was a fresh install I ignored the warning and did it anyway. Uncommented GRUB_TERMINAL=console did a 'sudo update-grub'. I went down for a reboot...and my system did not boot again. I considered chrooting and fixing it, but I thought it may be less annoying to just re-install. However, this time I elected to do a full install while connected to wifi. After booting up the first time, I try switch over to a TTY and *POOF!*, I have ttys now. So I'm not sure if my install the first time was simply busted, or the difference of doing a minimal install vs a full install is what caused my vtty issue. But anyway. Thought I'd open a bug. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:06:00 2019 InstallationDate: Installed on 2019-11-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1851146 Title: No Virtual Terminals Status in gdm3 package in Ubuntu: New Bug description: I'll start this bug report with my first disclaimer: I'm filing this report from a fixed system. The original system that I'm going to reference has been installed over with the current system I'm filing this report from. The first install was UEFI, minimal install, not connected to the internet during installation. Now, I'll continue with my story. So, when doing the first install, I realized I had screwed up my username when doing the install. But you can't do a lot of the 'usermod' commands from the user you're logged in as. Since I was having to log in as a regular user, and then run 'sudo usermod', it was stating that the user I was trying to modify was currently logged in. So I logged out, and then attempted to switch to a tty, as I didn't need a graphical login for root. When trying to access virtual TTYs from Ctrl+Alt+F{3,4,5,6}, there were no terminals to access. I did some googling and didn't find anything directly related. Most were related to either accessing virtual terminals, or getting back to a graphical desktop if you mistakenly get to a vtty. So I took to IRC (#ubuntu on freenode). After someone did a '!tty' to really rub salt in the wound, someone recommended that I try uncommenting 'GRUB_TERMINAL=console' and regenerating grub.cfg, I took them up on the offer. So I open /etc/default/grub, and scroll down to that line. I immediately see it says 'grub-pc only'. I knew my install was UEFI, but since it was a fresh install I ignored the warning and did it anyway. Uncommented GRUB_TERMINAL=console did a 'sudo update-grub'. I went down for a reboot...and my system did not boot again. I considered chrooting and fixing it, but I thought it may be less annoying to just re-install. However, this time I elected to do a full install while connected to wifi. After booting up the first time, I
[Desktop-packages] [Bug 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
Have seen it both with the internal laptop keyboard as well as an external USB keyboard -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
Initial testing does make it look like an Xorg session behaves better in this regard than a wayland session (using vanilla gnome sessions in both, fwiw) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1848086] [NEW] Keyboard shortcuts to launch apps sometimes launch twice
Public bug reported: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1848086/+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 1844575] Re: Pixelated fonts sometimes
agree that mutter#804 is the upstream issue -- 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/1844575 Title: Pixelated fonts sometimes Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844575/+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 1845031] [NEW] gnome not remembering numlock state in eoan
Public bug reported: in 3.34, gnome-settings-daemon has removed its handling of numlock state persistence, claiming that mutter should be handling that now (https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f). However, numlock is always off when I start a session, and does not get remembered when I turn it on, log out, and log back in. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 23 11:15:27 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1845031 Title: gnome not remembering numlock state in eoan Status in mutter package in Ubuntu: New Bug description: in 3.34, gnome-settings-daemon has removed its handling of numlock state persistence, claiming that mutter should be handling that now (https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f). However, numlock is always off when I start a session, and does not get remembered when I turn it on, log out, and log back in. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 23 11:15:27 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+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 1844575] Re: Pixelated fonts sometimes
** Attachment added: "Screenshot from 2019-09-18 12-59-08.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+attachment/5289524/+files/Screenshot%20from%202019-09-18%2012-59-08.png -- 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/1844575 Title: Pixelated fonts sometimes Status in gnome-shell package in Ubuntu: New Bug description: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+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 1844575] [NEW] Pixelated fonts sometimes
Public bug reported: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1844575 Title: Pixelated fonts sometimes Status in gnome-shell package in Ubuntu: New Bug description: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+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 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all
Made sure everything is on/not muted and still no sound. Also tried under a live session of Ubuntu 16.04 which detected the card, but still came up with no sound. -- 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/1833652 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.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.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833652/+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 1833652] Re: [SB-XFi - Creative X-Fi, playback] No sound at all
Internal audio is disabled in the BIOS. -- 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/1833652 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.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.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1833652/+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 1833652] [NEW] [SB-XFi - Creative X-Fi, playback] No sound at all
Public bug reported: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.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.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1833652 Title: [SB-XFi - Creative X-Fi, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Installed a new X-Fi sound card, but no audio is being heard during playback on Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/controlC1: jfilingeri 1723 F pulseaudio CurrentDesktop: MATE Date: Thu Jun 20 23:32:37 2019 InstallationDate: Installed on 2019-06-18 (3 days ago) InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi failed Symptom_Card: Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jfilingeri 1723 F pulseaudio jfilingeri 3577 F alsamixer /dev/snd/pcmC0D0p: jfilingeri 1723 F...m pulseaudio /dev/snd/controlC1: jfilingeri 1723 F pulseaudio Symptom_Type: No sound at all Title: [SB-XFi - Creative X-Fi, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170M-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.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.:bvrF3:bd09/08/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170M-D3H-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version:
[Desktop-packages] [Bug 1566032] Re: crl-verify is not an option
It looks like this option is available via "crl-verify-file" and "crl- verify-dir" in network-manager-openvpn 1.8.4 and higher. It looks like versions with this functionality are already in the cosmic (network- manager-openvpn 1.8.6) and disco (network-manager-openvpn 1.8.10) repositories. Are there any plans to update the version used by bionic? I'm required to use bionic for a little while longer now in my org and it would be a boon to be able to have access to this functionality sooner rather than later.. Even if the new versions won't be packaged for bionic, at the very least you may be able to close this wishlist item as fixed for those future versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1566032 Title: crl-verify is not an option Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: I am unable to specify a CRL for OpenVPN through either the nmcli, network-manager-openvpn-gnome, or the configuration file (/etc/NetworkManager/system_connections/some_vpn.conf). Would be nice to have a crl-verify=/path/to/crl.pem option. Ubuntu 15.10 network-manager-openvpn 0.9.10.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1566032/+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