[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
Oh, I upgraded kernel to 5.8.0 and it works! -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
** Changed in: xorg-server (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights Status in xorg-server package in Ubuntu: New Bug description: All files in home folder are owned by the user. startx is only working with root rights. xinit: connection to X server lost/usr/bin/gnome-session: 29: exec: /usr/libexec/gnome-session-binary: Permission denied 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jun 4 16:25:19 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset rootflags=subvol=ROOT SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A 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 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889051] Re: Unreachable options
Laptop resolution: 1366 * 768 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1889051 Title: Unreachable options Status in libreoffice package in Ubuntu: New Bug description: Proof: https://webmshare.com/qda19 What I am doing in "Screen Record"? Ans: I am trying to Save the Keyboard Shortkey that I created for Insert. But sadly 3 options which say "Reset", "Cancel" and "Ok" are hidden down below. Neither I can touch it by dragging my Window around, nor I can save this shortkey. Distro: Ubuntu 20.04 LibreOffice Writer Version: 6.4.4.2 Display Server: Wayland GNOME: 3.36.3 What to do? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 13:52:26 2020 InstallationDate: Installed on 2020-02-16 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890373] [NEW] [M17xR4, Creative CA0132, Line In, Internal] fails after a while
Public bug reported: I just install Ubuntu 20.04 (I had LinuxMint before) I have the ound for a while then, for no reason, no more sound. I have to listen with my earphones (USB) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: aliennux 1841 F pulseaudio /dev/snd/controlC0: aliennux 1841 F pulseaudio /dev/snd/controlC1: aliennux 1841 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 00:28:26 2020 InstallationDate: Installed on 2020-08-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Line In, Internal Symptom_Type: Sound works for a while, then breaks Title: [M17xR4, Creative CA0132, Line In, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: Alienware dmi.bios.version: A12 dmi.board.name: M17xR4 dmi.board.vendor: Alienware dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A12 dmi.modalias: dmi:bvnAlienware:bvrA12:bd05/17/2013:svnAlienware:pnM17xR4:pvrA12:rvnAlienware:rnM17xR4:rvrA12:cvnAlienware:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: M17xR4 dmi.product.sku: M17xR4 dmi.product.version: A12 dmi.sys.vendor: Alienware ** 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/1890373 Title: [M17xR4, Creative CA0132, Line In, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I just install Ubuntu 20.04 (I had LinuxMint before) I have the ound for a while then, for no reason, no more sound. I have to listen with my earphones (USB) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: aliennux 1841 F pulseaudio /dev/snd/controlC0: aliennux 1841 F pulseaudio /dev/snd/controlC1: aliennux 1841 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 00:28:26 2020 InstallationDate: Installed on 2020-08-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=fr_CA:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_CA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Line In, Internal Symptom_Type: Sound works for a while, then breaks Title: [M17xR4, Creative CA0132, Line In, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: Alienware dmi.bios.version: A12 dmi.board.name: M17xR4 dmi.board.vendor: Alienware dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A12 dmi.modalias: dmi:bvnAlienware:bvrA12:bd05/17/2013:svnAlienware:pnM17xR4:pvrA12:rvnAlienware:rnM17xR4:rvrA12:cvnAlienware:ct8:cvrA12: dmi.product.family: 103C_5335KV dmi.product.name: M17xR4 dmi.product.sku: M17xR4 dmi.product.version: A12 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1890373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics
** Changed in: mutter (Ubuntu) Status: Expired => 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/1882216 Title: [bochs_drm] Booting gets stuck with corrupt graphics Status in mutter package in Ubuntu: New Bug description: When booting on a VPS connected via VNC at first the text messages via boot are displayed. Then the resolution changes several times (VNC size changes) and after a lot of resolution changes it gets stuck in a corrupd graphic design. The cursor is still blinking but alt+Fx does also not work. Using sudo service gdm3 stop and sudo startx is working. Due to the fact that the VNC console is completely frozen and this is hosted at a provider I have to use a separate putty session to stop gdm and starting a new gui session which is then displayed in the VNC. This problem does not exist with Ubuntu 18.04 LTS. It does not matter if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04 LTS. On a second VPS the problem is similar but not the same. The second one does not get totally frozen. There is still no GUI when booting but it ends up in a purple uniform screen even the text mode is purple (the first VPS ends up a blueish screen with blue vertical lines). On the second VPS it is possible to switch to shell (purple style) and executing the abovementioned commands directly without a second putty session. But the behavior is basically similar for both VPS. When using sudo reboot the second VPS displays text again and the first only some graphic trash. So basically they have both the same behavior but on the first the graphics are totally destroyed even text is not working anymore. The Funny thing is that startx is still working but after clothng the startx session the graphic trash is shown again. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 5 10:39:59 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A 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 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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/mutter/+bug/1882216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1882102 Title: [vmwgfx] Gnome Desktop only starting with root rights Status in xorg-server package in Ubuntu: Expired Bug description: All files in home folder are owned by the user. startx is only working with root rights. xinit: connection to X server lost/usr/bin/gnome-session: 29: exec: /usr/libexec/gnome-session-binary: Permission denied 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jun 4 16:25:19 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset rootflags=subvol=ROOT SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A 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 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881175] Re: nautilus doesnt start
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1881175 Title: nautilus doesnt start Status in nautilus package in Ubuntu: Expired Bug description: for an unknown cause nautilus does not want to start, after a reboot it works ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 20:01:29 2020 InstallationDate: Installed on 2020-01-14 (135 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-12 (16 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1881175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882216] Re: [bochs_drm] Booting gets stuck with corrupt graphics
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1882216 Title: [bochs_drm] Booting gets stuck with corrupt graphics Status in mutter package in Ubuntu: Expired Bug description: When booting on a VPS connected via VNC at first the text messages via boot are displayed. Then the resolution changes several times (VNC size changes) and after a lot of resolution changes it gets stuck in a corrupd graphic design. The cursor is still blinking but alt+Fx does also not work. Using sudo service gdm3 stop and sudo startx is working. Due to the fact that the VNC console is completely frozen and this is hosted at a provider I have to use a separate putty session to stop gdm and starting a new gui session which is then displayed in the VNC. This problem does not exist with Ubuntu 18.04 LTS. It does not matter if I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04 LTS. On a second VPS the problem is similar but not the same. The second one does not get totally frozen. There is still no GUI when booting but it ends up in a purple uniform screen even the text mode is purple (the first VPS ends up a blueish screen with blue vertical lines). On the second VPS it is possible to switch to shell (purple style) and executing the abovementioned commands directly without a second putty session. But the behavior is basically similar for both VPS. When using sudo reboot the second VPS displays text again and the first only some graphic trash. So basically they have both the same behavior but on the first the graphics are totally destroyed even text is not working anymore. The Funny thing is that startx is still working but after clothng the startx session the graphic trash is shown again. 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Jun 5 10:39:59 2020 DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem anderen Prozess verwendet?) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.1 dmi.sys.vendor: QEMU version.compiz: compiz N/A 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 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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/mutter/+bug/1882216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1869963] Re: Unable to install chromium-browser in docker
[Expired for cloud-images because there has been no activity for 60 days.] ** Changed in: cloud-images Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1869963 Title: Unable to install chromium-browser in docker Status in cloud-images: Expired Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Bug description: Steps to reproduce: Create a docker container with the official image "ubuntu:focal". Inside of the container, run "apt-get install chromium-browser". Expected results: Chromium is installed. Actual results: Chromium installation fails. The error is telling me that it is unable to reach the snap store (probably because snapd is not running). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1869963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Project changed: eog => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3033 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3033 ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2923 => gitlab.gnome.org/GNOME/gnome-shell/-/issues #3033 ** Description changed: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile + + Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile Originally reported in https://bugzilla.gnome.org/show_bug.cgi?id=675645 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/938751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 388712] Re: gvfsd-gphoto2 locks camera
Is there a way to stop gvfsd-gphoto2 from respawning? Even after killing and disabling the process, blacklisting '60-glibphoto2-6.rules' from udev, GTK still respawn it: 153716 tty2 Sl+0:00 /usr/libexec/gvfsd-gphoto2 --spawner :1.6 /org/gtk/gvfs/exec_spaw/20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/388712 Title: gvfsd-gphoto2 locks camera Status in gvfs package in Ubuntu: Confirmed Bug description: After plugging in a camera, gvfsd-gphoto2 launches and locks the camera. This prevents gphoto2 from doing its job, since it does not acces the camera via GVFS/GIO: Steps to reproduce: 1) Plug in the camera. 2) 'ps x | grep gphoto' shows gvfsd-gphoto2 and/or gvfs-gphoto2-volume-monitor running 3) 'gphoto2 --auto-detect --capture-image-and-download' fails with "Error (-60: 'Could not lock the device'" 4) 'killall gvfsd-gphoto2 gvfs-gphoto2-volume-monitor' 5) rerun (3), and have your picture taken and downloaded. I don't know if the daemon is only locking the camera as soon as some process starts accessing it. (well, maybe nautilus does acces it). It would be great, if it could release the lock as soon as possible, or (don't know about the locking) don't lock for read-only access. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/388712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890307] Re: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox)
Sounds like some kind of feedback bug. Maybe it's resetting itself because it's prioritizing manual window resizing. Can you just resize the VM window instead? ** Summary changed: - Screen resolution change not possible (AMD/VirtualBox) + [vmwgfx] Screen resolution change not possible (AMD/VirtualBox) ** Package changed: xorg (Ubuntu) => xserver-xorg-video-vmware (Ubuntu) ** Also affects: kwin (Ubuntu) Importance: Undecided Status: New -- 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/1890307 Title: [vmwgfx] Screen resolution change not possible (AMD/VirtualBox) Status in kwin package in Ubuntu: New Status in xserver-xorg-video-vmware package in Ubuntu: New Bug description: I installed Kubuntu 20.10 in VirtualBox. It is not possible to set the initial resolution (800x600) to a higher one. If you do so, the screen resolution changes back to 800x600 after 1-2 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 4 18:05:56 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-08-04 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200804) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgkubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4 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+git20200714-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/kwin/+bug/1890307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab
It sounds like this bug was fixed before Ubuntu 20.04 was released. Can anyone else confirm? ** Tags removed: eoan ** Tags added: bionic ** Changed in: mutter (Ubuntu) Status: Won't Fix => Confirmed ** Summary changed: - [wayland] Fullscreen games offset after returning from alt-tab + Fullscreen game windows vertically offset after returning from Alt-Tab -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890281] Re: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit
*** This bug is a duplicate of bug 1732245 *** https://bugs.launchpad.net/bugs/1732245 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1732245, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1732245 Fullscreen game windows vertically offset after returning from Alt-Tab -- 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/1890281 Title: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit Status in xorg package in Ubuntu: New Bug description: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:220d] InstallationDate: Installed on 2016-11-03 (1369 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=fff07cd8-771d-418e-a056-c094fe8e3a55 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-24 (11 days ago) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 24 10:49:18 2020 xserver.configfile: default xserver.errors: Failed to load module "vesa" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 831 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862081] Re: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling)
Continued in bug 1890141. -- 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/1862081 Title: Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) Status in mutter package in Ubuntu: Fix Released Bug description: When I play a video with mpv (or e.g. Firefox), it works just fine. When this video is fullscreened (e.g. in mpv by pressing f), the screen quickly turns off, and switches resolution modes in such a rate the screen is unusable. The native resolution of the screen is 1440p, but Xorg somehow increases the size to 3424x1926 for the fullscreen, then quickly switches back to 1440p, before increasing it again. As soon as the video is de-fullscreened (by pressing f again in mpv, or esc in Firefox), the funny resolution switching stops and the system is usable again. This also happens with the modesetting 2d-driver. This does not happen with Wayland. This can be seen in the Xorg-log: [20.215] (II) intel(0): EDID vendor "JDI", prod id 0 [20.215] (II) intel(0): Printing DDC gathered Modelines: [20.215] (II) intel(0): Modeline "2560x1440"x0.0 245.12 2560 2608 2640 2720 1440 1443 1449 1502 +hsync -vsync (90.1 kHz eP) [ 258.869] (II) intel(0): resizing framebuffer to 3424x1926 [ 258.905] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 268.955] (II) intel(0): resizing framebuffer to 2560x1440 [ 269.097] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 270.383] (II) intel(0): resizing framebuffer to 3424x1926 [ 270.400] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 271.852] (II) intel(0): resizing framebuffer to 2560x1440 [ 271.858] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none [ 273.294] (II) intel(0): resizing framebuffer to 3424x1926 [ 273.314] (II) intel(0): switch to mode 2560x1440@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none When the resolution is increased, the Kernel complains about the framebuffer size: [ 269.830034] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 00:00:07 2020 DistUpgraded: 2020-02-05 22:21:13,002 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:2259] MachineType: LENOVO 20LES01W00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=/dev/mapper/hostname-ubunturoot ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-02-05 (0 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N25ET52W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LES01W00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN25ET52W(1.38):bd11/27/2019:svnLENOVO:pn20LES01W00:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LES01W00:rvrNotDefined:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 3rd dmi.product.name: 20LES01W00 dmi.product.sku: LENOVO_MT_20LE_BU_Think_FM_ThinkPad X1 Yoga 3rd dmi.product.version: ThinkPad X1 Yoga 3rd dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 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+git20190815-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/mutter/+bug/1862081/+subscriptions --
[Desktop-packages] [Bug 1890141] Re: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling
** Summary changed: - Scaling issue with fullscreening YouTube, Netflix, games, etc + Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Tags added: amdgpu -- 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/1890141 Title: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling Status in mutter package in Ubuntu: New Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890365] [NEW] Web Serial fails to access local device
Public bug reported:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium on
the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device is
listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1890365
Title:
Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
New
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870790] Re: Two mouse cursors after login
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 We're now tracking this in bug 1873052. ** Tags added: xrandr-scaling ** This bug has been marked a duplicate of bug 1873052 Showing two cursors after login when fractional scaling is enabled -- 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/1870790 Title: Two mouse cursors after login Status in mutter package in Ubuntu: New Bug description: When i logout and log back in, there's two mouse cursors on the screen, a bigger and a smaller. Ubuntu 20.04, fractional scaling enabled. This hasn't happened in other Gnome distros or in earlier Ubuntu versions. HW: AMD Ryzen 7 2700X 16GB RAM Radeon RX570 (with open driver) Asus 28" 4K monitor (DisplayPort) Panasonic 55" TV (HDMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874835] Re: gdm3 hangs after entering password with automounting network share
** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/618 Importance: Unknown Status: Unknown -- 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/1874835 Title: gdm3 hangs after entering password with automounting network share Status in gdm: Unknown Status in gdm3 package in Ubuntu: New Bug description: Whether I am using autofs or systemd automount units to mount network shares (mainly cifs), gdm3 hangs regularly as soon my notebook returns from suspend mode and the user enters their password. With automount being disabled gdm3 doesn't hang. 1) lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 2) gdm3: Installiert: 3.28.3-0ubuntu18.04.4 gnome-shell: Installiert: 3.28.4-0ubuntu18.04.3 3) I'd expect to gdm3 to login the user after authenticating the user. 4) gdm3 hangs after the user typed in their password. Steps to reproduce - as an example a samba network share gets mounted in /shares/transfer: a) The notebook is connected to network via ethernet. b) Network share gets mounted by automounter (eg. ls /shares/transfer). c) As soon the share is mounted suspend the notebook. d) Disconnect ethernet (eg. undocking the notebook). e) Power on the notebook (in undocked state with no ethernet connected). f) Whether the notebook has a wifi connection or not, after typing in the password, gdm3 hangs. tty logins still possible, hanging automounter connection is to see. My current workaround: I am using a systemd unit to unmount all automatically mounted network shares. Additional NetworkManager dispatcher script kills network connection to file server in case network device changes with automounts being active. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1874835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: Showing two cursors after login when fractional scaling is enabled
** Summary changed: - GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen + Showing two cursors after login when fractional scaling is enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: Showing two cursors after login when fractional scaling is enabled Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix -- 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/1732245 Title: [wayland] Fullscreen games offset after returning from alt-tab Status in Mutter: New Status in mutter package in Ubuntu: Won't Fix Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878597] Re: Bump Breaks/Replaces for mesa dev pkgs to allow upgrade 18.04->20.04
Hello Timo, or anyone else affected, Accepted libglvnd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libglvnd/1.3.1-1ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libglvnd (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1878597 Title: Bump Breaks/Replaces for mesa dev pkgs to allow upgrade 18.04->20.04 Status in libglvnd package in Ubuntu: Fix Released Status in libglvnd source package in Focal: Fix Committed Bug description: [Impact] EGL/GL/GLES headers got moved to libglvnd from mesa, but we backport mesa without this change, so upgrade from 18.04 to 20.04 will need to be handled once the 18.04.5 stack backports are in bionic. And this means bumping the versioned Breaks/Replaces on mesa dev packages. Need to ensure that focal has a newer mesa than bionic, so that the last point-release of 20.0.x won't get in bionic before focal. [Test case] Test upgrade from bionic to focal with dev packages installed. [Regression potential] none, as long as the upgrade is tested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1878597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell package in Debian: Fix Released Bug description: [ Impact ] gnome-shell-calendar-server memory usage increases daily [ Test case ] Monitor the memory usage of gnome-shell-calendar-server process using top or similar tools and ensure that its memory usage is stable. [ Regression potential ] Events in gnome-shell calendar aren't visible anymore --- It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885346] Re: gnome-shell-calendar-server leaks GBs of memory every few days
As requested in, I installed and ran gnome-shell 3.36.4-1ubuntu1~20.04.1, from focal proposed. I followed the steps that I previously was able to reproduce this issue with, and didn't see a similar memory-growth behavior (when looking at top). I hope this helps. -- 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/1885346 Title: gnome-shell-calendar-server leaks GBs of memory every few days Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell package in Debian: Fix Released Bug description: [ Impact ] gnome-shell-calendar-server memory usage increases daily [ Test case ] Monitor the memory usage of gnome-shell-calendar-server process using top or similar tools and ensure that its memory usage is stable. [ Regression potential ] Events in gnome-shell calendar aren't visible anymore --- It's been happening repeatedly over the last maybe week? I have to manually kill it about once a day, when I start to feel everything slow down as the OS starts to swap. Actually, I tracked down and fixed a few leaks in the code, and it looks stable so far. I'll submit a patch soon, as well as send the fix upstream to Gnome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1885346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890049] Re: global menu bar no longer supported after 20.04 upgrade
I don't understand, it's not like Unity was the only DE environment with a global menu bar. This looks like another case of Gnome dragging everyone else's UX down with them. -- 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/1890049 Title: global menu bar no longer supported after 20.04 upgrade Status in firefox package in Ubuntu: Won't Fix Bug description: 1) version: 79.0+build1-0ubuntu0.20.04.1 500 2) Ubuntu Release : Ubuntu 20.04.1 LTS 3) What I expected to happen: In Unity DE. menu bars are integrated with title bar or top panel when maximized 4) What happened instead: Menu bar doesn't integrate. Takes too much vertical space. Problematic because I have made a jump to wide screens around 2012. I guess decision makers at ubuntu still enjoy 4:3 screens and thus don't see the value in DEs that optimize vertical space. But it would be really nice to have a hand here. The current workaround is to disable the menu bar, which leaves me at the mercy of the hamburger menu. The hamburger menu is an implant from old Mobile App Design. But nowadays even Mobile App UX designers decry the Hamburger menu and in a desktop it makes little sense. Firefox is a good example because the menu bar has sections like History which are a lot richer than what's available to be accessed from the hamburger menu. It's really just not possible to have as many menu options and categories as a menu bar in a hamburger menu. And access is less efficient -> more mouse movement -> more mouse clicks. So I have to choose between wasting space unnecessarily with a menu bar that does not integrate with the top panel OR losing a lot of access to options and settings by removing the menu bar and using the hamburger menu instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122]
(In reply to Botond Ballo [:botond] from comment #18) > Martin, WDYT? Based on the above info, should we enable XInput 2 for KWin >= > 5.19.3 (and >= 5.18.next)? How about other window managers? Fedora has used XINPUT2 by default for five years and I don't have any reports so I guess it's okay to enable it for recent systems, at least for KDE/Gnome. -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1697122]
Martin, WDYT? Based on the above info, should we enable XInput 2 for KWin >= 5.19.3 (and >= 5.18.next)? How about other window managers? -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, - and also adds a check for the existence of an environment variable "RPCBIND_RMTCALLS_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. + and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable, instead of changing or adding the cmdline parameter, allows anyone using the variable to disable the remote calls default to upgrade to Focal without breaking rpcbind. After the upgrade to Focal, the environment variable (defined in /etc/default/rpcbind and/or /etc/rpcbind.conf) will simply be ignored without any change needed to the rpcbind package in Focal or later. [original description] As this backports that functionality, it Binary package hint: cups cups 1.3.9-2ubuntu4 From /var/log/cups/error_log: cups: unable to bind socket for address 127.0.0.1:631 - Address already in use. Nothing actually looks wrong. 127.0.0.1:631 is only in use by cupsd when started. ** Description changed: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo
[Desktop-packages] [Bug 1888392] Re: The libreoffice interface does not appear in Ubuntu MATE
Can’t test this, sorry; the MATE compositor doesn’t work for my AMD laptop (https://ubuntu-mate.community/t/20-04-display-issues-with-amd- gpu/21648/9 ?) ** Also affects: ubuntu-mate Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1888392 Title: The libreoffice interface does not appear in Ubuntu MATE Status in Ubuntu MATE: New Status in libreoffice package in Ubuntu: New Bug description: When I try to open a document in libreoffice, the application does not open completely. Only the window bar appears. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-core 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Jul 21 09:26:19 2020 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2020-04-27 (84 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1888392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889460] Re: Missing font after $LANG change
Perhaps related to bug 1839022 in fonts-ubuntu. ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1889460 Title: Missing font after $LANG change Status in libreoffice package in Ubuntu: New Bug description: When $LANG is set for example to: "pl_PL.UTF-8" or "en_GB.utf8" certain fonts are not displayed on font list - for example Ubuntu Light, Ubuntu Thin. When $LANG is unset - all fonts are displayed on font list - for example Ubuntu Light, Ubuntu Thin. Tested on OS: Ubuntu 18.04.04 LTS, LiveCD Kubuntu 20.04.01 LTS, in calc and writer. Version: 6.4.4-0ubuntu0.20.04.1, 6.0.7-0ubuntu0.18.04.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Agreed. I'll be referencing this issue there. And I'll have a look into the journal, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is working properly are included above under
[Desktop-packages] [Bug 1638610]
*** Bug 1612533 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1638610
Title:
Dependency of JavaScript objects is Misconfigured Browser Crashes.
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Hey Team ,
The bug i want to mention here is a denial of service attack that will not
allow any kind of redirection on a page crafted by attacker where we have used
hyper-links(ahref).
The bug can be maliciously used by crafting an HTML file by an attacker and
then sending it to the victim clearly showing there is a hyper-link that
redirects to lets say (google.com) through status bar but it will not , instead
cause denial of service , browser's also hang up and Crashes.
I have tested it on the Very Latest Version of Ubuntu LTS Default Browser.
Reason:
The following script stops the page from being redirected:
window.onbeforeunload = function(){
//Unredirectable Page
setTimeout("window.location=document.location;",0);
}
Demo URL : http://hackies.in/Unredirect-Browsers-Test.html
Actual results:
It should redirect me to the new page , where as it don't redirect to
a new page and the browsers Hangs up.
Expected results:
So dependency of JavaScript objects(window.document) on Href attribute should
not be there.
Attached POC for References
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1638610/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870790] Re: Two mouse cursors after login
** Package changed: ubuntu => mutter (Ubuntu) -- 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/1870790 Title: Two mouse cursors after login Status in mutter package in Ubuntu: New Bug description: When i logout and log back in, there's two mouse cursors on the screen, a bigger and a smaller. Ubuntu 20.04, fractional scaling enabled. This hasn't happened in other Gnome distros or in earlier Ubuntu versions. HW: AMD Ryzen 7 2700X 16GB RAM Radeon RX570 (with open driver) Asus 28" 4K monitor (DisplayPort) Panasonic 55" TV (HDMI) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870790] [NEW] Two mouse cursors after login
You have been subscribed to a public bug: When i logout and log back in, there's two mouse cursors on the screen, a bigger and a smaller. Ubuntu 20.04, fractional scaling enabled. This hasn't happened in other Gnome distros or in earlier Ubuntu versions. HW: AMD Ryzen 7 2700X 16GB RAM Radeon RX570 (with open driver) Asus 28" 4K monitor (DisplayPort) Panasonic 55" TV (HDMI) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal -- Two mouse cursors after login https://bugs.launchpad.net/bugs/1870790 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888480] Re: problem in menu graphic
** Package changed: ubuntu => nautilus (Ubuntu) ** Tags added: focal -- 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/1888480 Title: problem in menu graphic Status in nautilus package in Ubuntu: New Bug description: when right click on folder in ubuntu 20.04 menu size is not fix with menu items. but when for example click on copy optin, for the next time we right click on folder, problem disapeared. if i can send images of this problem, problem get Clear and precise for you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1888480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
I agree that a new bug should be filed. When doing so, please attach any relevant policy violations from journalctl to the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is working
[Desktop-packages] [Bug 1888480] [NEW] problem in menu graphic
You have been subscribed to a public bug: when right click on folder in ubuntu 20.04 menu size is not fix with menu items. but when for example click on copy optin, for the next time we right click on folder, problem disapeared. if i can send images of this problem, problem get Clear and precise for you. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- problem in menu graphic https://bugs.launchpad.net/bugs/1888480 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
@Rüdiger: Quite some water has passed under the bridge since the submission of this bug. It mostly came to be about the method for achieving a distinguishable abstract path for IBus, and is now closed. I would suggest that you file a new bug about the issue you now encounter. It sounds like an apparmor issue to me, and bug #1856738 is possibly related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<<
[Desktop-packages] [Bug 1718135] Re: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers()
** Changed in: nautilus Status: New => Fix Released -- 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/1718135 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: Copying files ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:25:22 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-10-06 (713 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x5573e2a1d902 : cmpq $0x0,0x20(%rdi) PC (0x5573e2a1d902) ok source "$0x0" ok destination "0x20(%rdi)" (0x0020) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: nautilus_progress_manager_has_viewers () () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in nautilus_progress_manager_has_viewers() UpgradeStatus: Upgraded to artful on 2017-09-14 (4 days ago) UserGroups: adm audio cdrom dialout dip fax lpadmin lxd netdev plex plugdev sambashare scanner sudo tape vboxusers video usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1718135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland
** Changed in: xserver Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1718719 Title: qemu can't capture keys properly under wayland Status in QEMU: New Status in XServer: New Status in qemu package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: This appears to be different than the previous similar bugs; patches do look to be applied to use libinput in the wayland case. Still: unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org I am using qemu-system-x86 1:2.10+dfsg-0ubuntu1 on artful. Many key inputs work correctly, but at boot the system will not properly catch the arrow keys, the above error shows up immediately after hitting Esc (for instance) to get to the boot menu. Booting from CD onto a daily Ubuntu desktop image, I can't navigate the splash menu. The same works correctly through virt-manager (which uses spice AFAICT, but wayland tends to crash when running virt-manager), and things work if I switch my session to Xorg rather than wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1718719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
We are talking about recent Ubuntu focal, thst is: Ubuntu 20.04.1. This is deemed safe for LTS upgrade! It is not! It will make petfectly working installs of 18.04 LTS unusable without any warning. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This will affect many installs, notably in professional multi user environments. It is absurd assuming that $XDG_CACHE_HOME is unset (any installation with a few hundred users will have homes on a network share and consequently caches moved elsewhere). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Test case: chromium snap with $XDG_CACHE_HOME set. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is working properly are included above under 'Extended test case'. = SRU apparmor =
[Desktop-packages] [Bug 1890028] Re: Unable to determine the session we are in: No session for pid XXXXX
I'll be happy to provide any information you need, but I can't use apport. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1890028 Title: Unable to determine the session we are in: No session for pid X Status in policykit-1-gnome package in Ubuntu: Incomplete Bug description: On a regular recently installed Xubuntu, the Gnome PolicyKit agent will not start: $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 (polkit-gnome-authentication-agent-1:18789): polkit-gnome-1-WARNING **: 10:14:23.384: Unable to determine the session we are in: No session for pid 18789 $ ps aux | grep pol smith18821 0.0 0.0 19256 736 pts/0S+ 10:16 0:00 grep pol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1890028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890028] Re: Unable to determine the session we are in: No session for pid XXXXX
I would love it, but apport does not work for me (see #1890003). apport-collect 1890028 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=wChJTq6tWF70sZ5H0XzJ_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 710, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 595, in run_update_report apport.packaging.get_version(p) File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 163, in get_version pkg = self._apt_pkg(package) File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 156, in _apt_pkg return self._cache()[package] File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 121, in _cache self._apt_cache = apt.Cache(progress, rootdir='/') File "/usr/lib/python3/dist-packages/apt/cache.py", line 150, in __init__ apt_pkg.read_config_dir(apt_pkg.config, SystemError: returned NULL without setting an error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1890028 Title: Unable to determine the session we are in: No session for pid X Status in policykit-1-gnome package in Ubuntu: Incomplete Bug description: On a regular recently installed Xubuntu, the Gnome PolicyKit agent will not start: $ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 (polkit-gnome-authentication-agent-1:18789): polkit-gnome-1-WARNING **: 10:14:23.384: Unable to determine the session we are in: No session for pid 18789 $ ps aux | grep pol smith18821 0.0 0.0 19256 736 pts/0S+ 10:16 0:00 grep pol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1890028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881751] Re: Chromium 83 on xenial − consistent renderer crash when playing back video
This bug was fixed in the package chromium-browser - 84.0.4147.105-0ubuntu0.16.04.1 --- chromium-browser (84.0.4147.105-0ubuntu0.16.04.1) xenial; urgency=medium * Upstream release: 84.0.4147.105 - CVE-2020-6537: Type Confusion in V8. - CVE-2020-6538: Inappropriate implementation in WebView. - CVE-2020-6532: Use after free in SCTP. - CVE-2020-6539: Use after free in CSS. - CVE-2020-6540: Heap buffer overflow in Skia. - CVE-2020-6541: Use after free in WebUSB. -- Olivier Tilloy Tue, 28 Jul 2020 11:21:33 +0200 ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6532 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6537 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6538 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6539 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6540 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6541 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1881751 Title: Chromium 83 on xenial − consistent renderer crash when playing back video Status in chromium-browser package in Ubuntu: Fix Released Bug description: I'm testing the latest stable release update for chromium-browser on xenial (83.0.4103.61-0ubuntu0.16.04.1 from ppa:canonical-chromium- builds/stage), and I'm observing that the renderer process consistently crashes when attempting to play back video. This was reported by whoopsie as https://errors.ubuntu.com/oops/34ab8952-a4cc-11ea-9bfd-fa163e102db1. The bionic build in the same PPA is not affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
Our $XDG_CACHE_HOME points to /var/cache/usercache//
I tried adding /var/cache/usercache/ to @{HOMEDIRS} in apparmor, but it did not
work. How do I tell my snaps that user caches are in /var/cache/usercache/ ??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
Status in ibus:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in ibus package in Ubuntu:
Fix Released
Status in im-config package in Ubuntu:
Fix Released
Status in snapd package in Ubuntu:
Fix Released
Status in apparmor source package in Xenial:
Fix Released
Status in im-config source package in Xenial:
Fix Released
Status in snapd source package in Xenial:
Fix Released
Status in apparmor source package in Yakkety:
Fix Released
Status in im-config source package in Yakkety:
Fix Released
Status in snapd source package in Yakkety:
Fix Released
Bug description:
= SRU im-config =
[Impact]
ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has
AppArmor mediation, ibus-daemon does not so it is important that its abstract
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue
mediating DBus abstract sockets like normal and also mediate access to the
ibus-daemon-specific abstract socket via unix rules. This also tidies up the
abstract socket paths so that it is clear which are for ibus-daemon, which for
dbus-daemon, etc.
The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
changes are required.
[Test Case]
1. start a unity session before updating to the package in -proposed
2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76
3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
ibus-daem 2973 jamie8u unix 0x 0t0 29606
@/tmp/dbus-oxKYpN30 type=STREAM
4. update the package in -proposed and perform '2' and '3'. The
IBUS_ADDRESSES should be the same as before
5. logout of unity, then log back in
6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e
(notice '/tmp/ibus/' in the path)
7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
ibus-daem 3471 jamie8u unix 0x 0t0 26107
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
...
(notice '@/tmp/ibus/' in the path)
In addition to the above, you can test for regressions by opening
'System Settings' under the 'gear' icon in the panel and selecting
'Text Entry'. From there, add an input source on the right, make sure
'Show current input source in the menu bar' is checked, then use the
input source panel indicator to change input sources.
Extended test case to verify input support still works in unconfined
and confined applications:
1. Systems Settings Language Support, if prompted install the complete
language support
2. Install Chinese (simple and traditional)
3. sudo apt-get install ibus-pinyin ibus-sunpinyin
4. logout / login
5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
6. select pinyin from the indicator
7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
8. open gnome-calculator and try to type something in (should get a pop-up)
9. open evince and try to search a pdf (should get a pop up)
10. upgrade apparmor and im-config from xenial-proposed
11. logout and back in
12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
13. open gnome-calculator and try to type something in (should get a pop-up)
14. open evince and try to search a pdf (should get a pop up)
15. verify no new apparmor denials
[Regression Potential]
The regression potential is considered low because there are no
compiled code changes and because the changes only occur after ibus-
daemon is restarted, which is upon session start, not package upgrade.
When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
updated accordingly for other applications to pick up.
This change intentionally requires a change to the unity7 snapd
interface, which is in already done.
This change intentionally requires a change to apparmor to add a unix
rule for communicating with the new ibus address. This is in xenial-
proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages
changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to
ensure that the apparmor abstraction is updated and policy recompiled
before ibus is restarted. This was omitted from the initial
[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
This is *not* fixed. I still see this issue in a recent install of Ubuntu 20.04, where $XDG_CACHE_HOME is set. We have home dirs mounted via network, so user caches were moved to local storage to sanitize network load. The right and perfectly valid way of doing so is setting $XDG_CACHE_HOME. Snapd honors this variable, from what I get from related bug reports. However, it appears that snaps are still not allowed access to the direcrory configured in this environment variable. This is a production environment for 800+ users who rely on chromium and Ubuntu. I *really, honestly* need this fixed ASOP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1580463 Title: Snap blocks access to system input methods (ibus, fcitx, ...) Status in ibus: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in im-config package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Fix Released Status in im-config source package in Xenial: Fix Released Status in snapd source package in Xenial: Fix Released Status in apparmor source package in Yakkety: Fix Released Status in im-config source package in Yakkety: Fix Released Status in snapd source package in Yakkety: Fix Released Bug description: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus- daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change
[Desktop-packages] [Bug 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3
Doing the usual Ubuntu operating system updates, we are now up to 18.04.4. Epson came out with a new driver (3.63), as opposed to the 2 previous drivers mentioned above. 3.63 works just fine, so it looks as though it just wouldn't work with the previous 2 drivers. So it looks as though this problem is solved, but I don't know how to mark this question as solved. I'm going to make this same entry in the question (687949) that I started on this problem, and try to close it out also. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1862847 Title: New Epson V19 scanner problems under Ubuntu 18.04.3 Status in sane-backends package in Ubuntu: New Bug description: Bought new Epson V19 scanner, and it works fine on my wife's computer running Windows 7, and also on my computer running Windows XP. Rebooted my computer into Ubuntu 18.04.3, and installed the driver packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64 bit, release date 12-26-2019) using their install.sh file with the without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650 1.0.2, and imagescan-plugin-ocr-engine 1.0.2). Looking at these packages using Aptitude, it appears that they are installed OK with no missing dependencies. Imagescan (on the graphical desktop) appears to find the scanner, and when you click to scan, you can hear the scanner seeming to run normally, but no image is produced at the end. Using the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to work fine for finding the scanner. But when I try scanimage -T, no image file is produced, although you can hear the scanner appearing to do a normal scan. So it appears that all the control functions are working fine, but the problem is getting the scan data. I also tried the suggestions in this video (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04 scanner problems how to fix them" concerning bug 1728012. In the end, nothing appears to have changed, so it appears I didn't make it any better or any worse. Any help would be greatly appreciated, including referring me to another place if I'm not posting in the right place yet. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)
Will do shortly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1884850 Title: Xorg server uses unacceptably large amounts of memory (and keep growing) Status in xorg-server package in Ubuntu: Incomplete Bug description: Description: Xorg server uses unacceptably large amounts of memory (and keep growing) Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I have been troubled by the way Xorg process uses memory. Here is an example of memory usage of Xorg as a function of time. I rebooted the laptop on June 17: Xorg-usage-20200617a.txt:root1224 1.9 0.8 948408 98848 tty7 Rsl+ 10:38 0:05 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200617b.txt:root1224 2.2 0.8 978264 105180 tty7 Ssl+ 10:38 0:22 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200618a.txt:root1224 0.3 1.3 1143064 162584 tty7 Ssl+ Jun17 3:15 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200619a.txt:root1224 0.3 2.9 1432232 360700 tty7 Ssl+ Jun17 12:30 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200619b.txt:root1224 0.3 2.7 1313120 338656 tty7 Ssl+ Jun17 12:39 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200623a.txt:root1224 0.3 6.0 1944364 738596 tty7 Ssl+ Jun17 31:55 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch The filename indicates the date the "ps fuxa" command was run. Contrast this against the memory usage of another Xorg process run for XPRA: Xorg-usage-20200617b.txt:wirawan 4452 2.4 2.0 1106920 244984 ? Ssl 10:46 0:12 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200618a.txt:wirawan 4452 0.2 2.0 1108572 246616 ? Ssl Jun17 2:25 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200619a.txt:wirawan 4452 0.2 2.0 1112460 249516 ? Ssl Jun17 8:34 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200619b.txt:wirawan 4452 0.2 2.0 1112964 250020 ? Ssl Jun17 8:40 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200623a.txt:wirawan 4452 0.1 2.0 1113092 250544 ? Ssl Jun17 11:22 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 My desktop usage pattern: * MATE desktop * 4-desktop setting (standard default MATE when shipped) * GNUCASH * about 3 windows of terminal (each about 5-10 tabs) * XPRA running Firefox web browser (to isolate web browser pixmap memory usage, if that was the culprit) * LibreOffice (several windows open at any time) * using "redshift" to change the desktop color to red at night I have never seen this before using Ubuntu 20.04 on this machine. Before, when I was running Debian 8, I could run this machine for months literally without Xorg memory bloating rapidly like this (but then I was using xfce instead of MATE). I viewed the output of xrestop, the pixmap memory usage is dominated by marco and wnck-applet: xrestop - Display: localhost Monitoring 36 clients. XErrors: 0 Pixmaps: 110748K total, Other: 84K total, All: 110833K total res-base Wins
[Desktop-packages] [Bug 1863080] Re: Unable to use dead keys in Java apps
Even though it says fix released, Ubuntu 18.04 is still affected by this. Presumably this needs LTS backporting? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1863080 Title: Unable to use dead keys in Java apps Status in ibus: Fix Released Status in ibus package in Ubuntu: Confirmed Bug description: This is same bug as #540751, as it happens again in Ubuntu 19.10 with Java 11. Way of reproduce it: - Fresh Ubuntu 19.10 install. - Install default-jre. - Download (for example) lastest NetBeans version. - Edit a file in NetBeans, you can't insert characters like 'á'. The workaround is the same, define XMODIFIERS='' before launching the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1863080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890321] [NEW] package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Public bug reported: Unable to install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: chromium-browser:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 4 21:23:44 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package chromium-browser (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890321 Title: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in chromium-browser package in Ubuntu: New Bug description: Unable to install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: chromium-browser:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 4 21:23:44 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package chromium-browser (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890141] Re: Scaling issue with fullscreening YouTube, Netflix, games, etc
** Description changed: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx-linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. + YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1890141 Title: Scaling issue with fullscreening YouTube, Netflix, games, etc Status in mutter package in Ubuntu: Incomplete Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890141] Re: Scaling issue with fullscreening YouTube, Netflix, games, etc
Here are the outputs ** Description changed: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx-linux/issues/2429). + + EDIT: This only happens when fractional scaling is enabled. + Specifically; main 4K screen at 150% and secondary 1080p screen to the + right at 100%. This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx-linux/issues/2429). - EDIT: This only happens when fractional scaling is enabled. - Specifically; main 4K screen at 150% and secondary 1080p screen to the - right at 100%. + EDIT: This only happens when fractional scaling is enabled. My config; + main 4K screen at 150% and secondary 1080p screen to the right at 100%. This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+attachment/5398732/+files/lspcik.txt -- 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/1890141 Title: Scaling issue with fullscreening YouTube, Netflix, games, etc Status in mutter package in Ubuntu: Incomplete Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1890141] Re: Scaling issue with fullscreening YouTube, Netflix, games, etc
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+attachment/5398733/+files/journal.txt -- 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/1890141 Title: Scaling issue with fullscreening YouTube, Netflix, games, etc Status in mutter package in Ubuntu: Incomplete Bug description: Same issue as this one: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1863391 Some websites like YouTube will attempt to fullscreen, just not successfully. Other websites, like Netflix, will fullscreen for a second and de-fullscreen after that. Some games act weirdly in fullscreen mode (this might be related, as I've never had this issue before now: https://github.com/ValveSoftware/csgo-osx- linux/issues/2429). EDIT: This only happens when fractional scaling is enabled. My config; main 4K screen at 150% and secondary 1080p screen to the right at 100%. YouTube fullscreens fine on the sec. screen (1080 100%). This is a gif I posted in the related bug report showing exactly what happens: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1863391/+attachment/5397743/+files/20200731_160007.gif ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 14:03:00 2020 InstallationDate: Installed on 2020-07-30 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876442] Re: [snap] chromium causing many audit messages in syslog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1876442 Title: [snap] chromium causing many audit messages in syslog Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium as installed through snap: chromium 81.0.4044.129 1135 latest/stable canonical✓ - $ tail -f /var/log/syslog May 2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 audit(1588416380.844:3238): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:20 master3900x kernel: [56493.196389] audit: type=1326 audit(1588416380.844:3239): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.999823] audit: type=1326 audit(1588416389.648:3240): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.35] audit: type=1326 audit(1588416389.648:3241): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993348] audit: type=1326 audit(1588416390.644:3242): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993410] audit: type=1326 audit(1588416390.644:3243): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104490] audit: type=1326 audit(1588416390.752:3244): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104561] audit: type=1326 audit(1588416390.752:3245): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398229] audit: type=1326 audit(1588416394.048:3246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398318] audit: type=1326 audit(1588416394.048:3247): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357592] audit: type=1326 audit(1588416409.004:3248): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:49 master3900x kernel: [56521.357678] audit: type=1326 audit(1588416409.004:3249): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1876442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1876442] Re: [snap] chromium causing many audit messages in syslog
Same here, flood of kernel/audit messages as below. Chromium 84.0.4147.105, snap rev 1244, Ubuntu 20.04.1 Aug 04 17:27:59 ole kernel: audit: type=1326 audit(1596558479.339:301): auid=1001 uid=1001 gid=1001 ses=3 subj==snap.chromium.chromium (enforce) pid=25861 comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7faf1689db9f code=0x5 Aug 04 17:27:59 ole kernel: audit: type=1326 audit(1596558479.339:302): auid=1001 uid=1001 gid=1001 ses=3 subj==snap.chromium.chromium (enforce) pid=25861 comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7faf1689db9f code=0x5 Aug 04 17:27:59 ole audit[25861]: SECCOMP auid=1001 uid=1001 gid=1001 ses=3 subj==snap.chromium.chromium (enforce) pid=25861 comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7faf1689db9f code=0x5 Aug 04 17:27:59 ole audit[25861]: SECCOMP auid=1001 uid=1001 gid=1001 ses=3 subj==snap.chromium.chromium (enforce) pid=25861 comm="chrome" exe="/snap/chromium/1244/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7faf1689db9f code=0x5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1876442 Title: [snap] chromium causing many audit messages in syslog Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium as installed through snap: chromium 81.0.4044.129 1135 latest/stable canonical✓ - $ tail -f /var/log/syslog May 2 12:46:20 master3900x kernel: [56493.196311] audit: type=1326 audit(1588416380.844:3238): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:20 master3900x kernel: [56493.196389] audit: type=1326 audit(1588416380.844:3239): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.999823] audit: type=1326 audit(1588416389.648:3240): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:29 master3900x kernel: [56501.35] audit: type=1326 audit(1588416389.648:3241): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993348] audit: type=1326 audit(1588416390.644:3242): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56502.993410] audit: type=1326 audit(1588416390.644:3243): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104490] audit: type=1326 audit(1588416390.752:3244): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:30 master3900x kernel: [56503.104561] audit: type=1326 audit(1588416390.752:3245): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398229] audit: type=1326 audit(1588416394.048:3246): auid=4294967295 uid=1000 gid=1000 ses=4294967295 subj==snap.chromium.chromium (enforce) pid=55655 comm="chrome" exe="/snap/chromium/1135/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7fdf221bdb8f code=0x5 May 2 12:46:34 master3900x kernel: [56506.398318] audit: type=1326 audit(1588416394.048:3247): auid=4294967295 uid=1000 gid=1000 ses=4294967295
[Desktop-packages] [Bug 1890307] Re: Screen resolution change not possible (AMD/VirtualBox)
** Summary changed: - Screen resolution not possible (AMD/VirtualBox) + Screen resolution change not possible (AMD/VirtualBox) -- 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/1890307 Title: Screen resolution change not possible (AMD/VirtualBox) Status in xorg package in Ubuntu: New Bug description: I installed Kubuntu 20.10 in VirtualBox. It is not possible to set the initial resolution (800x600) to a higher one. If you do so, the screen resolution changes back to 800x600 after 1-2 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 4 18:05:56 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-08-04 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200804) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgkubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4 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+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1890307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890307] [NEW] Screen resolution not possible (AMD/VirtualBox)
Public bug reported: I installed Kubuntu 20.10 in VirtualBox. It is not possible to set the initial resolution (800x600) to a higher one. If you do so, the screen resolution changes back to 800x600 after 1-2 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 4 18:05:56 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-08-04 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200804) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgkubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu4 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+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy has-workaround reproducible single-occurrence 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/1890307 Title: Screen resolution not possible (AMD/VirtualBox) Status in xorg package in Ubuntu: New Bug description: I installed Kubuntu 20.10 in VirtualBox. It is not possible to set the initial resolution (800x600) to a higher one. If you do so, the screen resolution changes back to 800x600 after 1-2 seconds. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 4 18:05:56 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-08-04 (0 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200804) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgkubuntu-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dm
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Marking this as verified, as it was properly reported as fixed in previous version (via https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/15) which doesn't change anything related to this bug. Also no e.u.c failure has been recorded so far. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
Hello Daniel, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers source package in Focal: Won't Fix Bug description: [ Impact ] When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 [ Test case ] In a Nvidia system: - From g-c-c enable fractional scaling - Set all the available fractional scaling values and ensure they work + In any case the screen should be turned off [ Regression potential ] Wrong screen size is set and panning might be enabled. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Please test proposed package
Hello Ivan, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows
Hello Niels, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1884754 Title: Fractional scaling does not persist while resizing or rebooting in VM windows Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860, but those report the issues are fixed. They also do not mention the VMware specific issues. [ Test case ] Install Ubuntu 20.04 in VMware Player, install open-vm-tools (done automatically with Easy Install), go to settings, enable Fractional Scaling and select any non-integer value. Results: - The scaling is applied - After next reboot the setting is reverted to 100%, but should use previous value [ Regression potential ] Resolution doesn't adapt properly to the vmware player window size. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.2-1ubuntu1~20.04.1 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: ubuntu:GNOME Date: Tue Jun 23 04:30:21 2020 InstallationDate: Installed on 2020-06-22 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876894] Please test proposed package
Hello Iain, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1876894 Title: Scaling is not reverted properly (appears shrunk) when disabling fractional scaling Status in gnome-control-center package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: * Impact Scaling is not reverted properly (appears shrunk) when disabling fractional scaling * Test Case Do this in an Ubuntu/Xorg session: 0. Be on a "clean" system wrt. fractional scaling, i.e. disabled & scaling at 100% 1. Open gnome-control-center → displays 2. Turn on fractional scaling 3. Select 125% 4. Press apply (the scaling should correctly change now) 5. Turn off fractional scaling by changing the toggle Now everything is shrunk - it's not been returned to 100% properly. See the attached screenshot where the text is tiny instead of regular 100% size. If you do this instead of step 5: 5. Select 100% scaling 7. Press apply 8. Turn off fractional scaling by changing the toggle Then everything returns to the normal size. Repeat the same selecting 200% at 5., (or 100% if 200% was your default) and ensure it's applied. I'm on nvidia(-440), but Séb said that he saw this on his Intel machine too. * Regression potential Verify that scaling changes are correctly applied on different setup ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 10:57:40 2020 InstallationDate: Installed on 2012-10-07 (2766 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-01-16 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Hello Matt, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic
[Desktop-packages] [Bug 1857947] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes [ Test case ] Four-finger gesture seems to trigger it, in any case it can be monitored via - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886996] Please test proposed package
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1886996 Title: Restore previous configuration after turning off fractional scaling does not work Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] It's not possible to restore the application a non-fractional scaling configuration when fractional scaling was previously enabled and applied. [ Test case ] 1. From control center, display panel, enable fractional scaling 2. Set scaling to some fractional value and apply and confirm it. 3. Turn off the fractional scaling switch and apply it 4. Fractional scaling should be reverted to the selected integer scaling. 5. When gnome-shell shows the confirmation dialog, click "Revert Settings" 6. Expect the fractional scaling to be re-enabled and applied as it used to be [ Regression potential ] - Configuration can't be applied - Scaling (fractional or not) is not properly applied in single and multi-monitor - Fractional scaling can't be toggled anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Please test proposed package
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size
Hello Marco, or anyone else affected,
Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags added: verification-needed verification-needed-focal
--
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/1889090
Title:
GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
in meta_monitor_manager_xrandr_update_screen_size
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Focal:
Fix Committed
Bug description:
Reported initially as comments of bug #1887998:
[ Impact ]
Ubuntu session doesn't start with some particular monitor
configurations, as per this fatal assertion:
Jul 27 00:30:33 jojda gnome-shell[15068]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
[ Test case ]
Start ubuntu session, you should be able to log-in and no error
fallback dialog is shown.
[ Regression potential ]
Screen size is not set properly for the session, panning is enabled.
---
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1
does not fix it. Unfortunately I cannot switch to Wayland because it
doesn't start on my system (video card: 00:02.0 VGA compatible
controller: Intel Corporation Iris Plus Graphics 655 (rev 01)).
Symptom is that after waking up from sleep I get white screen of death
that says what the bug description says ("Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please log
out and try again.") and I have to click the Log out button at which
points it lets me log in again. Sometime it does the same thing again
right after logging in.
Syslog message are also pretty much the same as from other comments,
here you can see it failing twice, first up while running then right
after re-login.
Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion
'GVC_IS_MIXER_CARD (card)' failed
Jul 27 00:30:32 jojda gnome-shell[4633]: **
Jul 27 00:30:32 jojda gnome-shell[4633]:
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out!
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled
restart job, restart counter is at 1.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session
(session: ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session:
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME
Re: [Desktop-packages] [Bug 1853331] Re: nm-applet assertion failure manipulating widgets
On Tue, 2020-08-04 at 13:14 +, Sebastien Bacher wrote: > @Raphael, it could be that your mirror was not updated yet? > > what is output of > > $ apt policy network-manager-gnome > # apt policy network-manager-gnome network-manager-gnome: Installed: 1.8.10-2ubuntu3 Candidate: 1.8.10-2ubuntu3 Version table: *** 1.8.10-2ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.8.10-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages -- 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/1853331 Title: nm-applet assertion failure manipulating widgets Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Focal: Fix Committed Bug description: * Impact the applet keeps logging gtk warnings * Test case Under xubuntu connect to a wifi, the journal shouldn't get nm-applet warnings * Regression potential The change is in the VPN submenu code, check that the items there are still correctly updated and available when needed --- nm-applet is logging a continuous stream of: Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent System updated on 19 Nov 2019 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Nov 20 15:48:21 2019 InstallationDate: Installed on 2018-11-06 (379 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100 192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Desktop-packages] [Bug 1889051] Re: Unreachable options
Thanks for reporting your issue! Can you please tell me your screen resolution? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1889051 Title: Unreachable options Status in libreoffice package in Ubuntu: New Bug description: Proof: https://webmshare.com/qda19 What I am doing in "Screen Record"? Ans: I am trying to Save the Keyboard Shortkey that I created for Insert. But sadly 3 options which say "Reset", "Cancel" and "Ok" are hidden down below. Neither I can touch it by dragging my Window around, nor I can save this shortkey. Distro: Ubuntu 20.04 LibreOffice Writer Version: 6.4.4.2 Display Server: Wayland GNOME: 3.36.3 What to do? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.4-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 13:52:26 2020 InstallationDate: Installed on 2020-02-16 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-05-08 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889051/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888504] Re: Two-finger touchpad scroll broken
We reviewed the rls incoming nomination and decided while the issue is worth investigating and fixing it's not important enough at this point to be nominated as a rls target, marked as rls-bb-notfixing ** Tags removed: rls-bb-incoming ** Tags added: rls-bb-notfixing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1888504 Title: Two-finger touchpad scroll broken Status in libreoffice package in Ubuntu: New Bug description: Run Calc -> drag two fingers up, down, left or right slowly. Expected behaviour: content pans in the direction of movement Observed behaviour: no effect on viewport, sometimes at all, sometimes after a sufficiently long drag, the viewport jumps/snaps to a different part of the document, as if the entire "accumulated" movement happened at once The behaviour is easily reproducible in Calc and Draw, but does not happen in Writer. Other applications (e.g. Firefox, Nautilus, GVim...) work as expected, scrolling smoothly as fingers slide along the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:31:59 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853331] Re: nm-applet assertion failure manipulating widgets
@Raphael, it could be that your mirror was not updated yet? what is output of $ apt policy network-manager-gnome -- 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/1853331 Title: nm-applet assertion failure manipulating widgets Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Focal: Fix Committed Bug description: * Impact the applet keeps logging gtk warnings * Test case Under xubuntu connect to a wifi, the journal shouldn't get nm-applet warnings * Regression potential The change is in the VPN submenu code, check that the items there are still correctly updated and available when needed --- nm-applet is logging a continuous stream of: Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent System updated on 19 Nov 2019 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Nov 20 15:48:21 2019 InstallationDate: Installed on 2018-11-06 (379 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100 192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781597] Re: [SRU] WoWLAN settings are not supported
The bionic n-m updates have been blocked for long enough it's probably not realistic to expect desktop to deal with those now so I'm going to unassign myself & mark as wontfix for bionic, especially that a newer LTS is out now. If someone else want to deal with testing and sponsoring nothing is blocking you though ** Changed in: network-manager (Ubuntu Bionic) Assignee: Sebastien Bacher (seb128) => (unassigned) ** Changed in: network-manager (Ubuntu Bionic) Status: Triaged => Won't Fix -- 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/1781597 Title: [SRU] WoWLAN settings are not supported Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Won't Fix Status in network-manager source package in Cosmic: Fix Released Bug description: [Impact] WoWLAN lets us wake up the system by sending wake packets over the wifi connection. This is something requested by some OEM projects, for bionic server images. NM 1.12 supports configuring this feature, so this can be achieved by backporting that support to 1.10 (bionic version). These are the MPs for cosmic and bionic: https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349468 https://code.launchpad.net/~alfonsosanchezbeato/network-manager/+git/network-manager/+merge/349465 [Test Case] First, the wifi card must support WoWLAN. This can be checked by running $ iw phy and searching for "WoWLAN support:" in the output. If it is supported, with the patch applied a connection configured with wowlan can be created with: $ sudo nmcli d wifi connect password $ sudo nmcli c modify 802-11-wireless.wake-on-wlan 8 $ sudo nmcli c down $ sudo nmcli c up We can check with 'iw' that WoWLAN is active for the connection: $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet In this case we have configured the connection to wake up the system when a 'magic' packet is received. We can then suspend the system with $ sudo systemctl suspend And we should be able to wake the system from another device with the command $ sudo etherwake -i [Regression Potential] Although the patch is not especially small, it is a backport of changes that have been merged upstream, with very little modifications to make it compile in 1.10. It is also a rather isolated feature that should not conflict with existing ones. The feature will be activated only if configured from the command line, so the risk of regressions should be small. Note also that the patch will be removed as soon as Ubuntu moves to NM 1.12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1781597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869021] Re: desktop dash search clicking on a snap application leads to error page in software centre
** Changed in: gnome-software (Ubuntu Eoan) Status: Confirmed => Won't Fix ** Changed in: gnome-software (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: snap-store-desktop Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869021 Title: desktop dash search clicking on a snap application leads to error page in software centre Status in snap-store-desktop: New Status in gnome-software package in Ubuntu: Confirmed Status in gnome-software source package in Bionic: Confirmed Status in gnome-software source package in Eoan: Won't Fix Status in gnome-software source package in Focal: Confirmed Bug description: Reproduction Steps: - search for a snap application you don't have installed in the "dash" - click that snap application - You will be led to an errored page in the software center. It looks "blank" for me - From there you can click back and usually click on the first item, and things are fine. What I would have expected to happen: - when I click the application, it takes me to software center to the application directly This is happening on Bionic with the latest updates, and on Focal as of today (2020-03-25) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890281] [NEW] Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit
Public bug reported: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:220d] InstallationDate: Installed on 2016-11-03 (1369 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=fff07cd8-771d-418e-a056-c094fe8e3a55 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-24 (11 days ago) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 24 10:49:18 2020 xserver.configfile: default xserver.errors: Failed to load module "vesa" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 831 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption 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/1890281 Title: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit Status in xorg package in Ubuntu: New Bug description: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller
[Desktop-packages] [Bug 1790360] Re: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace
*** This bug is a duplicate of bug 1732245 *** https://bugs.launchpad.net/bugs/1732245 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1790360 Title: [wayland] Fullscreen games offset after switching back to them from an app in the same workspace Status in mutter package in Ubuntu: Confirmed Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the game down by the size of the GNOME Shell top bar and to the right by the size of the Ubuntu Dock. Test Case = 1. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 2. Press Alt-Tab or click a dock icon to switch to another window in the same workspace and then press Alt-Tab or click the dock icon to switch back to the game. The game should display and function normally. Workaround == Switch apps again using any method. Other Info == This is a duplicate of #1732245 which has been reported on Ubuntu 17.10 which reached it's end-of-life on July 19, 2018. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 2 14:36:29 2018 InstallationDate: Installed on 2018-07-10 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time
** Description changed: Side scrollbar setting feature works from time to time . If you set it on and close the window it saves the setting and side scrollbar works . If you set it on and move to another menu item i.e. "Sound" or "search" it doesn't save the setting and switch it back to off. S.T.R. 1. Open "Settings"; 2. Move to "Mouse and scroll pad" item; 3. Set Side scrollbar to on; 4. Move to "Sound" item; 5. Move to "Mouse and scroll pad" item. - A.R. Side scrollbar is on. - E.R. Side scrollbar is off. + E.R. Side scrollbar is on. + A.R. Side scrollbar is off. Severity: low Environment: Ubuntu 20.04 LTS 64 bit Russian language Gnome 3.36.2 Check screenshot attached. -- 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/1886162 Title: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time Status in gnome-control-center package in Ubuntu: New Bug description: Side scrollbar setting feature works from time to time . If you set it on and close the window it saves the setting and side scrollbar works . If you set it on and move to another menu item i.e. "Sound" or "search" it doesn't save the setting and switch it back to off. S.T.R. 1. Open "Settings"; 2. Move to "Mouse and scroll pad" item; 3. Set Side scrollbar to on; 4. Move to "Sound" item; 5. Move to "Mouse and scroll pad" item. E.R. Side scrollbar is on. A.R. Side scrollbar is off. Severity: low Environment: Ubuntu 20.04 LTS 64 bit Russian language Gnome 3.36.2 Check screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD)
iommu=soft as workaround helped me (ThinkPad T495 / AMD) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1872452 Title: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD) Status in kwin package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Always when I turn on my Lenovo Thinkpad T495 (AMD CPU)- without the power supply connected - the laptop boots correctly at the beginning, but then just before going to the login screen it gets black. It can only be restarted. When I attach the power supply before the laptop boot everything works correctly. I see this behavior only on Kubuntu (with KDE desktop). On Ubuntu 20.04 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 13 14:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-04-02 (10 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d6957960-70a9-45a8-98b1-b0a14d07b829 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-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/kwin/+bug/1872452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888805] Re: Ubuntu 20.04 gnome-software can't handle CAB file by default installation
Hi ShengYao, Could you please let us know your latest solution? It's to install gnome-software in default installation, right? Regards, Jiqi. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/105 Title: Ubuntu 20.04 gnome-software can't handle CAB file by default installation Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: LVFS firmware CAB file can't be identified by Ubuntu 20.04 software management, which should invoke fwupdmgr to execute associated system BIOS or other firmware update. Ubuntu20.04 default software management is ‘ubuntu-software’, which do not support cab by default.It need to install gnome-software by manually. CAB file need to support in Nautilus and be enabled by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have got it working with the liquorix kernel and updated firmware, the biggest issue seems to be that the ibt firmware does not get loaded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890261] [NEW] I am not prompted for my password when booting after running out of power (e.g. empty battery)
Public bug reported: Ubuntu 18.04.4 LTS When the system shuts down because of lack of power supply, the next time, I am not prompted for my password; I go directly to the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 11:06:26 2020 InstallationDate: Installed on 2018-10-04 (669 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (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 gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1890261 Title: I am not prompted for my password when booting after running out of power (e.g. empty battery) Status in gnome-screensaver package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS When the system shuts down because of lack of power supply, the next time, I am not prompted for my password; I go directly to the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 11:06:26 2020 InstallationDate: Installed on 2018-10-04 (669 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1890261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878597] Re: Bump Breaks/Replaces for mesa dev pkgs to allow upgrade 18.04->20.04
** Summary changed: - Bump Breaks/Replaces for mesa dev to allow upgrade 18.04->20.04 + Bump Breaks/Replaces for mesa dev pkgs to allow upgrade 18.04->20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1878597 Title: Bump Breaks/Replaces for mesa dev pkgs to allow upgrade 18.04->20.04 Status in libglvnd package in Ubuntu: Fix Released Status in libglvnd source package in Focal: Triaged Bug description: [Impact] EGL/GL/GLES headers got moved to libglvnd from mesa, but we backport mesa without this change, so upgrade from 18.04 to 20.04 will need to be handled once the 18.04.5 stack backports are in bionic. And this means bumping the versioned Breaks/Replaces on mesa dev packages. Need to ensure that focal has a newer mesa than bionic, so that the last point-release of 20.0.x won't get in bionic before focal. [Test case] Test upgrade from bionic to focal with dev packages installed. [Regression potential] none, as long as the upgrade is tested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1878597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873184] Re: Wired and wireless connection details have not enough height and items overlap
** Also affects: oem-priority Importance: Undecided Status: New -- 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/1873184 Title: Wired and wireless connection details have not enough height and items overlap Status in gnome-control-center: Unknown Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Bug description: There is a display bug when you unplug the network cable on focal. Please see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1873184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1197400] Re: Main menu bar (Settings, etc) not showing.
On bionic you can also install the snap which doesn't have the issue $ snap install gnome-mahjongg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1197400 Title: Main menu bar (Settings, etc) not showing. Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: Description: Ubuntu 13.04 Release: 13.04 N: Unable to locate package pkgname (I'm using the new Gnome+Ubuntu pkg) The Main Menu bar (Settings, etc) not showing. I have tried many different types of ways to get access to it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-mahjongg 1:3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 3 09:02:08 2013 InstallationDate: Installed on 2013-05-18 (45 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-mahjongg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1197400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1197400] Re: Main menu bar (Settings, etc) not showing.
The menubar was removed in https://gitlab.gnome.org/GNOME/gnome- mahjongg/-/commit/76d8385e and now there is an popdown button on the top bar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1197400 Title: Main menu bar (Settings, etc) not showing. Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: Description: Ubuntu 13.04 Release: 13.04 N: Unable to locate package pkgname (I'm using the new Gnome+Ubuntu pkg) The Main Menu bar (Settings, etc) not showing. I have tried many different types of ways to get access to it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-mahjongg 1:3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 3 09:02:08 2013 InstallationDate: Installed on 2013-05-18 (45 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-mahjongg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1197400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1197400] Re: Main menu bar (Settings, etc) not showing.
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the current version of Ubuntu. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: gnome-mahjongg (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-mahjongg (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-mahjongg in Ubuntu. https://bugs.launchpad.net/bugs/1197400 Title: Main menu bar (Settings, etc) not showing. Status in gnome-mahjongg package in Ubuntu: Fix Released Bug description: Description: Ubuntu 13.04 Release: 13.04 N: Unable to locate package pkgname (I'm using the new Gnome+Ubuntu pkg) The Main Menu bar (Settings, etc) not showing. I have tried many different types of ways to get access to it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-mahjongg 1:3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Wed Jul 3 09:02:08 2013 InstallationDate: Installed on 2013-05-18 (45 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-mahjongg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mahjongg/+bug/1197400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop
** Summary changed: - Make digital mic on the AMD renoir machines work under gnome desktop + Make digital mic on the AMD Renoir machines work under gnome desktop ** Description changed: [Impact] - On the LENOVO AMD renoir machines, there is a digital mic directly + On the LENOVO AMD Renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] On the AMD Renoir machines:
[Desktop-packages] [Bug 1806334] Re: Thunderbolt 2 storage not auto mounted and show in file manager
Is that still an issue in focal? Could you maybe upstream it to https://github.com/storaged-project/udisks/ ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1806334 Title: Thunderbolt 2 storage not auto mounted and show in file manager Status in OEM Priority Project: Confirmed Status in OEM Priority Project bionic series: New Status in OEM Priority Project focal series: New Status in udisks2 package in Ubuntu: New Bug description: OS 18.04 Plug thunderbolt 2 storage device, can see the device in lsblk as /dev/sda (and /dev/sda1 is a ext4 partition) however I can't see it in file manager (check attachment, it say TBT3 in the picture, however I use TBT2 and I can reproduce it) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1806334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
The solution for https://bugs.launchpad.net/bugs/1874567 solved this issue for me. -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718719] Re: qemu can't capture keys properly under wayland
upstream can't reproduce this bug, so I wonder if the backport was incomplete and it's fixed in the current release (1.20.8), could you test again? ** Changed in: xserver Importance: Medium => Unknown ** Changed in: xserver Remote watch: freedesktop.org Bugzilla #102475 => gitlab.freedesktop.org/xorg/xserver/issues #706 ** Changed in: xorg-server (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1718719 Title: qemu can't capture keys properly under wayland Status in QEMU: New Status in XServer: Unknown Status in qemu package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: This appears to be different than the previous similar bugs; patches do look to be applied to use libinput in the wayland case. Still: unknown keycodes `(unnamed)', please report to qemu-de...@nongnu.org I am using qemu-system-x86 1:2.10+dfsg-0ubuntu1 on artful. Many key inputs work correctly, but at boot the system will not properly catch the arrow keys, the above error shows up immediately after hitting Esc (for instance) to get to the boot menu. Booting from CD onto a daily Ubuntu desktop image, I can't navigate the splash menu. The same works correctly through virt-manager (which uses spice AFAICT, but wayland tends to crash when running virt-manager), and things work if I switch my session to Xorg rather than wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1718719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 That's a new bug so please log it as such. Though if you are using Pop!OS then it's not a bug at all, since System76 has now removed the feature from their package. If you are using regular Ubuntu then please open a new bug by running: ubuntu-bug mutter -- 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/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Working on fully updated focal fossy Procedure to make bug happen: 1. open gnome control center and select screen (skærme in danish) 2. click the "fractional scaling" switch 3. select 150% scaling and click the green button at top right 4. Result is a blank screen and the monitor going into a power save state A reboot doesn't help. The login screen appears, when I log in the screen goes blank again and the monitor power save kicks in. If I select the "unity" environment, the display does work. If I do this on the command line "gsettings set org.gnome.mutter experimental-features ['']", I can log in as usual and fractional scaling has been turned off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 12:11:39 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880108] Re: package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1
*** This bug is a duplicate of bug 1878597 *** https://bugs.launchpad.net/bugs/1878597 ** This bug has been marked a duplicate of bug 1878597 Bump Breaks/Replaces for mesa dev to allow upgrade 18.04->20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1880108 Title: package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 Status in libglvnd package in Ubuntu: New Status in libglvnd source package in Focal: Triaged Bug description: When I was updating my system from 18.04LTS to 20.04, the computer's power shutting down unfortunately. After rebooted, the bugs throw out. So I've tried to --fix the problem. But they keep occurring. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgl-dev 1.3.1-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 22 12:26:23 2020 ErrorMessage: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 InstallationDate: Installed on 2018-06-20 (701 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libglvnd Title: package libgl-dev 1.3.1-1 failed to install/upgrade: 正试图覆盖 /usr/include/GL/gl.h，它同时被包含于软件包 mesa-common-dev:amd64 20.0.4-2ubuntu1~18.04.1 UpgradeStatus: Upgraded to focal on 2020-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1880108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
** Changed in: oem-priority Status: Fix Committed => Fix Released -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
I installed the mutter libraries from focal proposed as described in #15 and the issue seems to be fixed. Also copied my ~/.config/monitors.xml to /var/lib/gdm/.config/monitors.xml and was able to get the same monitor configuration working at the login screen. So this is verified and finally works as it used to work in 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A 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
[Desktop-packages] [Bug 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Description changed: [Impact] On the LENOVO AMD renoir machines, there is a digital mic directly connected to the APU instead of the codec, so there are two separate sound cards in the system, one is for analogue codec driven by hda driver, the other is for the dmic driven by ASoC acp driver. The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't support this design yet, it could support all audio devices on the codec well, but it doesn't support that dmic well. In the gnome-control-center, the dmic becomes two input devices: analog input and multichannel input, and users can only record sound from analog input, the multichannel input can't function at all. Besides this issue, there is another issue, after users plug an external mic, the external mic can't replace the dmic automatically, this gives users a bad experience since this behaviour is different from the other audio designs. [Fix for pulseaudio] backport 3 patches: 2 of them from upstream device-port: queue CARD CHANGE event before update default sink alsa: adjust ucm sink/source priority according to ports priority 1 of them from a merge request: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305 [Fix for alsa-ucm-conf] backport 14 patches: 11 of them from upstream: ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch ucm.conf-add-support-for-the-kernel-module-name-tree.patch sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch sof-soundwire-initial-UCM2-version.patch sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch sof-soundwire-rewrite-for-syntax-3.patch HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch Fix-invalid-Regex-Type-in-various-Condition-blocks.patch hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch 3 of them from a merge request: https://github.com/alsa-project/alsa-ucm-conf/pull/41 [Fix for alsa-lib] backport 47 patches from upstream: Enabled-extended-namehints-in-alsa.conf.patch conf-add-snd_config_is_array-function.patch topology-use-snd_config_is_array-function.patch ucm-merge-the-array-items-from-the-condition-blocks.patch ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch ucm-execute-SectionDefaults-lately-when-the-first-ve.patch ucm-handle-set-_once-command.patch ucm-handle-set-_defaults-command.patch ucm-initialize-mgr-once_list.patch ucm-fix-SectionOnce-comment.patch ucm-fix-compilation-error-in-set_defaults_user.patch ucm-rename-SectionOnce-to-BootSequence.patch ucm-rename-_once-command-to-_boot-command.patch ucm-configuration-implement-in-place-Include.patch ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch ucm-config-substitute-File-string-to-allow-variables.patch ucm-configuration-allow-to-define-the-configuration-.patch ucm-configuration-add-DefineRegex.patch ucm-substitute-arguments-in-sequences.patch ucm-allow-syntax-version-3.patch ucm-config-change-the-in-place-include-evaluation-or.patch ucm-allow-to-specify-the-toplevel-directory-using-as.patch ucm-substitute-also-value-strings.patch ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch ucm-String-condition-implement-Empty.patch ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch ucm-substitute-OpenName.patch ucm-substitute-CardNumber.patch ucm-implement-the-toplevel-ucm-configuration-file-pa.patch ucm-substitute-device-modifier-names-too.patch ucm-substitute-device-strings-in-the-device-lists.patch ucm-substitute-component-sequence-string.patch ucm-substitute-verb-name-and-file-field.patch ucm-substitute-Comment-in-Transition-and-Device.patch ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch ucm-substitute-arguments-in-sequences-only-for-synta.patch ucm-shuffle-code-in-compound_merge.patch ucm-implement-CardIdByName-substitution.patch ucm-allow-to-ignore-errors-for-the-value-substitutio.patch ucm-allow-to-use-the-defined-variables-in-the-substi.patch ucm-implement-CardNumberByName-substitution.patch ucm-fix-the-possible-buffer-overflow-substitution.patch ucm-simplify-get_by_card-in-parser.c.patch ucm-implement-AlwaysTrue-Condition.Type.patch ucm-Allow-empty-strings-in-var-.-substitutions.patch ucm-substitution-remove-duplicate-allow_empty-assign.patch ucm-fix-parse_get_safe_name-safe-name-must-be-checke.patch ucm-substitute-the-merged-tree-completely.patch add Breaks alsa-ucm-conf (<= 1.2.2-1ubuntu0.1) in the d/control add snd_config_is_array@ALSA_0.9 1.2.2-2.1ubuntu1 in the d/libasound2.symbols [Test Case] - On the AMD renoir machines: - Boot the system with these updated packages (already backported kernel - drivers to focal and oem-5.6 kernels), open the gnome-control-center, - we could see the digital mic in the input device tab, and only one - input device. we
[Desktop-packages] [Bug 1870758] Re: [nvidia] Display scaling results in a blank screen (power save state)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 Nvidia 1080 with two 4K screens. After updating to 440 i only have lost fraction scaling, gnome settings only shows 100,200,300,400. The old experimental flag does not work (xorg). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870758 Title: [nvidia] Display scaling results in a blank screen (power save state) Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: Working on fully updated focal fossy Procedure to make bug happen: 1. open gnome control center and select screen (skærme in danish) 2. click the "fractional scaling" switch 3. select 150% scaling and click the green button at top right 4. Result is a blank screen and the monitor going into a power save state A reboot doesn't help. The login screen appears, when I log in the screen goes blank again and the monitor power save kicks in. If I select the "unity" environment, the display does work. If I do this on the command line "gsettings set org.gnome.mutter experimental-features ['']", I can log in as usual and fractional scaling has been turned off. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 12:11:39 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.10 --- pulseaudio (1:11.1-1ubuntu7.10) bionic; urgency=medium * d/p/0903-device-port-switch-on-port-available-fix-automatic-p.patch * (LP: #1882248) -- Hui Wang Thu, 09 Jul 2020 16:03:25 +0800 ** Changed in: pulseaudio (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Released Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
