[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Touchpad MSFT0001:00 04F3:3140 is dead on 5.8 rc5 as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04
[Desktop-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
@Seb, for the pulseaudio bionic, I remember you already pushed a build for this SRU to the queue, so @foundation team, could you please build it since our oem project is waiting for this fix. thx. -- 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: Confirmed Status in linux-oem package in Ubuntu: New 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 Committed 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 997934]
*** Bug 134992 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/997934 Title: [Upstream] Spell checking doesn't warn users if the selected dictionary isn't installed, but rather returns a potentially incorrect result Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: This has been the case since Beta 2. To reproduce: 1) Type out a load of rubbish on the keyboard as well as a few correctly spelled words. I used "vmw;qbjk aoeuasnth aoeu house in the street" 2) Press F7 to initiate the spell check. Actual Result: The spell check notifies the user of completion without any recognition of errors. Expected Result: The spell check should highlight each misspelled word and offer alternatives. WORKAROUND: Open the dash and run Language Support 2) Under the 'Language' tab, choose another variant of English and drag it above the US English so it takes precedence. 3) Click "Apply System-wide" and log out. On logging back in, spell check will work. Not reproducible in Xubuntu 32-bit. lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-writer 1:3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Fri May 11 08:53:51 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120328) ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/997934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)
did not work ** Attachment added: "not work" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+attachment/5395064/+files/Screenshot%20from%202020-07-23%2008-50-55.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory) Status in gnome-calculator package in Ubuntu: New Status in snapd package in Ubuntu: Invalid Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)
did not work ** Attachment added: "Screenshot from 2020-07-23 08-50-55.png" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+attachment/5395063/+files/Screenshot%20from%202020-07-23%2008-50-55.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory) Status in gnome-calculator package in Ubuntu: New Status in snapd package in Ubuntu: Invalid Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888598] [NEW] pulseaudio has is buggy with hdmi audio and sleep/wake
Public bug reported: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: New Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1888571] Re: Screen flickering and glitching after install
> Intel integrated driver causes screen flickering with Ubuntu install. I think you mean the generic 'modeset' driver, which is the correct driver to use and the one shown in your XorgLog attachments. If you were using 'xserver-xorg-video-intel' then please just uninstall that package. It should not be used and commonly causes problems (bug 1867668). Most likely I think this is a kernel bug relating to: [ 117.852074] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 117.944970] sof-audio-pci :00:1f.3: firmware boot complete [ 170.252664] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 170.347691] sof-audio-pci :00:1f.3: firmware boot complete [ 235.442471] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 235.537670] sof-audio-pci :00:1f.3: firmware boot complete ... ** Tags added: ice-lake-flicker ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Screen flickering and glitching after install + [Ice Lake] Screen flickering and glitching after install -- 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/1888571 Title: [Ice Lake] Screen flickering and glitching after install Status in linux package in Ubuntu: Confirmed Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 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-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888517] Re: gnome-shell segfaults on idle
** Tags added: 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/1888517 Title: gnome-shell segfaults on idle Status in gnome-shell package in Ubuntu: Fix Released Bug description: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
> This is interesting. When running gnome-shell in Wayland the window placement seems to be correct. I've been testing it a bit. I think that's what I was aiming for with: gsettings set org.gnome.mutter center-new-windows true It likely works better in Wayland because that treats each monitor separately. Whereas Xorg likes to render all monitors as one, so the middle might be the border between the monitors. > Unfortunately Wayland doesn't allow for remote desktop access so I can't help my customers when something goes wrong. Please subscribe to bug 1696885 about that. It is blocked by bug 1802533. > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 Excellent, thanks. > Do you have any recommendations for an alternative window manager Canonical doesn't support anything other than Gnome Shell now. Though as you have found even that "support" has its limitations. I suggest any software that wants a window A to reliably appear over window B should make sure window A is a dialog parented by B, or that A is a modal dialog parented by B. So if you can get that small change made to the POS software then it should work correctly with most window managers including gnome-shell. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Unfortunately I think that means you will need to open a copy of this bug again, after this one closes. -- 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 1857191] Re: Dark themes don't work well with highlighted current line in gedit
** Attachment added: "gedit.png" https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1857191/+attachment/5395035/+files/gedit.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887396] Re: chromium-browser doesn't start
As of July 2nd, again I can't start chromium after having rebooted
Ubuntu without having quitted chromium first. This time, the error
indicates a lack of removal of temporary symlinks named SingletonLock
and related Singleton*. E.g.:
```
Gtk-Message: 00:39:49.309: Failed to load module "canberra-gtk-module"
Gtk-Message: 00:39:49.311: Failed to load module "canberra-gtk-module"
[11356:11356:0723/003949.329173:ERROR:process_singleton_posix.cc(265)] Failed
to unlink /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[11356:11356:0723/003949.329289:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
File exists (17)
[11356:11356:0723/003949.329363:ERROR:process_singleton_posix.cc(265)] Failed
to unlink /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[11356:11356:0723/003949.329412:ERROR:chrome_browser_main.cc(1246)] Failed to
create a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than opening a
new window in the existing process. Aborting now to avoid profile corruption.
[11356:11547:0723/003949.337100:ERROR:browser_gpu_channel_host_factory.cc(153)]
Failed to launch GPU process.
[11564:11564:0723/003949.384057:ERROR:broker_posix.cc(43)] Invalid node channel
message
```
Upon removing of the 3 symlinks within the profile folder, still an
error:
```
Gtk-Message: 01:00:08.609: Failed to load module "canberra-gtk-module"
Gtk-Message: 01:00:08.610: Failed to load module "canberra-gtk-module"
[13997:13997:0723/010008.630073:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/snap/chromium/1213/.config/google-chrome/SingletonLock:
Permission denied (13)
[13997:13997:0723/010008.630170:ERROR:chrome_browser_main.cc(1246)] Failed to
create a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than opening a
new window in the existing process. Aborting now to avoid profile corruption.
[13997:14191:0723/010008.637081:ERROR:browser_gpu_channel_host_factory.cc(153)]
Failed to launch GPU process.
```
Any ideas? Thank you!
--
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/1887396
Title:
chromium-browser doesn't start
Status in chromium-browser package in Ubuntu:
Invalid
Bug description:
Upon launching chromium-browser from the terminal with the command:
$ chromium-browser --user-data-dir=/home/albert/.config/google-chrome
2>&1 >> /dev/null
I get this error:
Gtk-Message: 15:31:01.011: Failed to load module "canberra-gtk-module"
[5823:6010:0713/153101.029812:ERROR:disk_cache.cc(184)] Unable to create cache
[5823:6010:0713/153101.029862:ERROR:shader_disk_cache.cc(606)] Shader Cache
Creation failed: -2
[5823:5823:0713/153101.030904:ERROR:process_singleton_posix.cc(280)] Failed
to create /home/albert/.config/google-chrome/SingletonLock: Permission denied
(13)
[5823:5823:0713/153101.030977:ERROR:chrome_browser_main.cc(1258)] Failed to
create a ProcessSingleton for your profile directory. This means that running
multiple instances would start multiple browser processes rather than opening a
new window in the existing process. Aborting now to avoid profile corruption.
... and chromium remains closed.
The chromium-browser and the command above worked fine until before
the snap-ization of chromium-browser in Ubuntu 20.04, which came about
yesterday when I run the updater.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 83.0.4103.97-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 15:33:56 2020
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-24 (1479 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Snap.Changes:
ID Status Spawn Ready Summary
113 Done2020-07-12T23:38:16+01:00 2020-07-12T23:38:37+01:00 Install
"chromium" snap
114 Done2020-07-12T23:38:38+01:00 2020-07-12T23:38:39+01:00 Connect
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 83.0.4103.116
(8f0c18b4dca9b6699eb629be0f51810c24fb6428-refs/branch-heads/4103@{#716})
Snap.ChromiumVersion: Chromium 83.0.4103.116 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-20 (54 days ago)
To manage
[Desktop-packages] [Bug 1888585] [NEW] seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed
Public bug reported: This bug is seen in the list at https://errors.ubuntu.com/ where it says: seahorse -- Ubuntu 20.04 -- seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed. According to the list at https://errors.ubuntu.com/ it occurred 3201 times the past week, so it clearly happens to many people and not only me, but there is still no bug report associated with it. Therefore I am making this bug report now, hoping this can be associated with the bug listed at https://errors.ubuntu.com/ and help developers become aware of the problem. This is for Ubuntu 20.04. Package: seahorse 3.36-1 PackageArchitecture: amd64 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1888585 Title: seahorse crash: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed Status in seahorse package in Ubuntu: New Bug description: This bug is seen in the list at https://errors.ubuntu.com/ where it says: seahorse -- Ubuntu 20.04 -- seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed. According to the list at https://errors.ubuntu.com/ it occurred 3201 times the past week, so it clearly happens to many people and not only me, but there is still no bug report associated with it. Therefore I am making this bug report now, hoping this can be associated with the bug listed at https://errors.ubuntu.com/ and help developers become aware of the problem. This is for Ubuntu 20.04. Package: seahorse 3.36-1 PackageArchitecture: amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
I ran another test of using the touchscreen and managed to make gnome- shell crash. It looks like apport uploaded it this time, but I couldn't figure out where it put it. I attached the *.uploaded file associated with the reproduction. There's some other files in /var/crash, but I guess they should have already been uploaded. Let me know if I should upload them. ** Attachment added: "_usr_bin_gnome-shell.1000.uploaded" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/+attachment/5395034/+files/_usr_bin_gnome-shell.1000.uploaded -- 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 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Hi Brian, I installed the proposed package and tried to test this. My results were mixed. I used the touchscreen for a while without issues. But then xorg crashed (and this report was a crash in gnome-shell). Apport refused to submit the bug reports because apparently there were a few not-updated packges (there weren't yesterday). I think that's a different issue than this original report, but it's still a crash when using the touchscreen. I'll re-update all my packages and keep testing. -- 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 1888574] Re: Dark mode highlight is too similar to text color
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 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 1857191, 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 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1888574 Title: Dark mode highlight is too similar to text color Status in gedit package in Ubuntu: New Bug description: Hi all! This is just a wishlist bug, but the dark mode in Gedit on Ubuntu doesn't work well for me. In dark mode, the highlight color and the text color are very similar, and the lack of contrast makes it difficult to the see text. Perhaps changing the highlight color to purple or something else to enhance contrast would be much appreciated. Thanks! Ubuntu 20.04 Installed: 3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1888574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183]
*** Bug 134517 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93 and 176) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 583994] Re: Consider replacing ntpdate calls by 'ntpd -g'
** Changed in: ntp (Debian) Importance: Unknown => Low -- 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/583994 Title: Consider replacing ntpdate calls by 'ntpd -g' Status in NTP: Invalid Status in ntp package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in ntp package in Debian: New Bug description: Binary package hint: ntp Given that 'ntpdate' is being obsoleted upstream [1], we should replace 'ntpdate' usage by: * ntpd -qg (if we really want to set the time and exit), or * ntpd-g (if we want to keep ntpd running) the '-q' option will set the clock once, and exit; the 'g' allows for large corrections to the clock, like what is done by 'ntpdate'. [1] http://www.eecis.udel.edu/~mills/ntp/html/ntpdate.html To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/583994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Importance: Unknown => Undecided ** Changed in: mesa Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #727 => None ** Changed in: mesa Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Won't Fix Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
** Changed in: libvdpau (Debian) Importance: Unknown => Undecided ** Changed in: libvdpau (Debian) Remote watch: Debian Bug tracker #617940 => None ** Changed in: libvdpau (Debian) Importance: Undecided => Medium ** Changed in: libvdpau (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvdpau in Ubuntu. https://bugs.launchpad.net/bugs/1300215 Title: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory Status in libvdpau package in Ubuntu: Triaged Status in libvdpau-va-gl package in Ubuntu: Confirmed Status in libvdpau package in Debian: Confirmed Bug description: This has been bothering me at least since precise (although there the missing link went to libvdpau_nvidia.so which was all the more mysterious since I do not own NVIDIA hardware). In numerous cases do I get a warning that libvdpau_i965.so is being tried to be accessed but it fails. I also can't find that file anywhere on my system or in the Ubuntu repository. I tried poking around with ldd to find out where the call to that lib comes from but so far unsuccessful. $ vdpauinfo display: :0 screen: 0 Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory Error creating VDPAU device: 1 libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer
It might be that the same bug affected me after upgrading to 20.04 with another printer: https://answers.launchpad.net/hplip/+question/690767 I also recently tried hplip 3.20.6 for a freshly installed xubuntu, but it did not help. (the result of hp-check brought the same result as https://answers.launchpad.net/hplip/+question/690767 (#5). I was forced to downgrade the system again because it is essential to keep the printer functional. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] [NEW] Split motd-news config into a new package
Public bug reported: The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a NEW package (motd-news-config) - have ubuntu-server depend on motd-news-config (or recommends) - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends (or recommends) on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config-news package, ENABLED=0 must remain set. ** Affects: base-files (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Xenial) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Xenial) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Bionic) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Focal) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: base-files (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Affects: ubuntu-meta (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Groovy) Importance: Undecided Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Also affects: ubuntu-meta (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: base-files (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: base-files (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Xenial) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Bionic) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Focal) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-meta (Ubuntu Groovy) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: base-files (Ubuntu Xenial) Status: New => In Progress ** Changed in: base-files (Ubuntu Bionic) Status: New => In Progress ** Changed in: base-files (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-meta (Ubuntu Groovy) Status: New => In Progress -- 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/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: In Progress Status in ubuntu-meta package in Ubuntu: In Progress Status in base-files source package in Xenial: In Progress Status in ubuntu-meta source package in Xenial: In Progress Status in base-files
[Desktop-packages] [Bug 1888574] [NEW] Dark mode highlight is too similar to text color
Public bug reported: Hi all! This is just a wishlist bug, but the dark mode in Gedit on Ubuntu doesn't work well for me. In dark mode, the highlight color and the text color are very similar, and the lack of contrast makes it difficult to the see text. Perhaps changing the highlight color to purple or something else to enhance contrast would be much appreciated. Thanks! Ubuntu 20.04 Installed: 3.36.2-0ubuntu1 ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gedit.png" https://bugs.launchpad.net/bugs/1888574/+attachment/5395032/+files/gedit.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1888574 Title: Dark mode highlight is too similar to text color Status in gedit package in Ubuntu: New Bug description: Hi all! This is just a wishlist bug, but the dark mode in Gedit on Ubuntu doesn't work well for me. In dark mode, the highlight color and the text color are very similar, and the lack of contrast makes it difficult to the see text. Perhaps changing the highlight color to purple or something else to enhance contrast would be much appreciated. Thanks! Ubuntu 20.04 Installed: 3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1888574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888571] [NEW] Screen flickering and glitching after install
Public bug reported: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 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-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1888571 Title: Screen flickering and glitching after install Status in xorg package in Ubuntu: New Bug description: Intel integrated driver causes screen flickering with Ubuntu install. Windows did not have this issue ProblemType: Bug DistroRelease: Ubuntu 20.04 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-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 15:41:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:875a] InstallationDate: Installed on 2020-07-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY Laptop 13-ba0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9f807172-2b35-4ad1-9f33-5a912ad7c579 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 875A dmi.board.vendor: HP dmi.board.version: 07.34 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd06/04/2020:svnHP:pnHPENVYLaptop13-ba0xxx:pvrType1ProductConfigId:rvnHP:rn875A:rvr07.34:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY Laptop 13-ba0xxx dmi.product.sku: 8KD13AV dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2
[Desktop-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
Looks like a patch was created some time ago. What steps are required in
order to close out this bug?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Triaged
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/1883886 Title: Print dialogue's height in Libreoffice Writer is too high to see and click buttons. Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Hello, I have the bug that is denoted here https://ask.libreoffice.org/en/question/240651/print-dialogue-too- large-to-select-ok-to-print/ and here https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67. Essentially, the libreoffice writer print's dialog box is too high for me to view and press the buttons with the mouse. A workaround is to just press ENTER to print. Please see the following screenshot for an example: https://snipboard.io/vc1X0f.jpg My information is as follows: Results of lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 Results of apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:6.4.3-0ubuntu0.20.04.1 Candidate: 1:6.4.3-0ubuntu0.20.04.1 Version table: *** 1:6.4.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:6.4.2-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. Best regards, Owen Charles ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-writer 1:6.4.3-0ubuntu0.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: LXQt Date: Wed Jun 17 12:47:56 2020 InstallationDate: Installed on 2020-06-05 (11 days ago) InstallationMedia: Lubuntu 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/df-libreoffice/+bug/1883886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872441] Re: Switching to another channel page, then back on an installed snap shows the snap as not installed and some system snaps as uninstallable
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium ** Changed in: snap-store-desktop Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu) Status: New => Triaged ** Changed in: gnome-software (Ubuntu) Status: Triaged => Confirmed ** Changed in: snap-store-desktop Status: New => Confirmed -- 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/1872441 Title: Switching to another channel page, then back on an installed snap shows the snap as not installed and some system snaps as uninstallable Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: When opening a details page for some snap that is already installed (for example the Snap Store itself), then selecting another channel from the Channels drop down menu, then selecting a channel from which the snap is installed, the details page now behaves like the snap is not installed, there is a "Install" button, the "Permissions" button disappears etc. It also seems that for some system snaps (for example the GTK2 Common Themes), the "Remove" button appears! I have a latest Snap Store from latest/stable/ubuntu-20.04 and latest snapd 2.44.3+20.04 from proposed repo. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1872441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Reported this Upstream under https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011 -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
This is interesting. When running gnome-shell in Wayland the window placement seems to be correct. I've been testing it a bit. Unfortunately Wayland doesn't allow for remote desktop access so I can't help my customers when something goes wrong. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's bug tracker now. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875050] Re: package texlive-base 2019.20200218-1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf', which is also in package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texlive-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1875050 Title: package texlive-base 2019.20200218-1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf', which is also in package texlive-plain-generic 2017.20180305-2 Status in texlive-base package in Ubuntu: Confirmed Bug description: error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: texlive-base 2019.20200218-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 25 18:35:45 2020 ErrorMessage: trying to overwrite '/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf', which is also in package texlive-plain-generic 2017.20180305-2 InstallationDate: Installed on 2020-02-05 (79 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all 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.2 SourcePackage: texlive-base Title: package texlive-base 2019.20200218-1 failed to install/upgrade: trying to overwrite '/usr/share/doc/texlive-doc/generic/iftex/iftex.pdf', which is also in package texlive-plain-generic 2017.20180305-2 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1875050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886161] Re: UU should work on roaming laptops
This is not going to happen in apt. It's a question for desktop how to do that, probably disabling the downloading in apt, and using gnome's package kit refresh stuff instead. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails
On 2020-07-22 17:56, Wl-dustin wrote: > At least we're seeing the same thing. Yeah, sorry for being slow. > I tried to experiment with this and couldn't reproduce it outside the > Xsession environment. Indeed, the files in /etc/X11/Xsession.d are not run automatically when entering a Wayland session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails
At least we're seeing the same thing. I tried to experiment with this and couldn't reproduce it outside the Xsession environment. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879352] Re: /usr/bin/im-launch i3 fails
Thanks, your latest comment made me realize what the error message in the bug description actually says. But neither im-config nor x11-common (which provides /etc/X11/Xsession.d/99x11-common_start) does that kind of double quoting AFAICT. The code appears not to be more complex than: ~$ sh $ START="/usr/bin/apt --version" $ exec $START apt 2.0.2ubuntu0.1 (amd64) ~$ And it has worked for many cycles with the common default DMs such as GDM, LightDM and SDDM. So the code should reasonably not be changed without making sure it works everywhere. Even if I finally understand the nature of the error message, it's not clear to me how that error message gets triggered when using i3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888517] Re: gnome-shell segfaults on idle
Ah, sorry—I just noticed & tried the version in focal-updates (3.36.3-1ubuntu1~20.04.2), and the issue is no longer reproducible. It must have been specific to 3.36.2-1ubuntu1~20.04.1. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1888517 Title: gnome-shell segfaults on idle Status in gnome-shell package in Ubuntu: Fix Released Bug description: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888517] Re: gnome-shell segfaults on idle
** Attachment added: "journalctl-2.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+attachment/5394899/+files/journalctl-2.txt ** Description changed: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - - Setting "org.gnome.desktop.session idle-delay" set to a small value, like 30. + - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f - Despite the different symptoms, this occurs 100% of the time. - $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: - Installed: 3.36.2-1ubuntu1~20.04.1 - Candidate: 3.36.3-1ubuntu1~20.04.2 - Version table: - 3.36.3-1ubuntu1~20.04.2 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - *** 3.36.2-1ubuntu1~20.04.1 100 - 100 /var/lib/dpkg/status - 3.36.1-5ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 3.36.2-1ubuntu1~20.04.1 + Candidate: 3.36.3-1ubuntu1~20.04.2 + Version table: + 3.36.3-1ubuntu1~20.04.2 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + *** 3.36.2-1ubuntu1~20.04.1 100 + 100 /var/lib/dpkg/status + 3.36.1-5ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- 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/1888517 Title: gnome-shell segfaults on idle Status in gnome-shell package in Ubuntu: New Bug description: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888517] [NEW] gnome-shell segfaults on idle
Public bug reported: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1888517/+attachment/5394898/+files/journalctl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1888517 Title: gnome-shell segfaults on idle Status in gnome-shell package in Ubuntu: New Bug description: Whenever my session becomes idle, gnome-shell segfaults and dies; I am returned to the login screen. I can reproduce this by: - Setting "org.gnome.desktop.session idle-delay" to a small value, like 30. - Waiting 30 seconds. Two files are attached, extracted from "journalctl -b -0": - journalctl.txt with an external monitor attached, and - journalctl-2.txt, with only the built-in display of the laptop computer. Both show a line near the top indicating the segfault, but these differ, e.g.: Jul 22 16:09:29 khaeru-laptop kernel: show_signal: 63 callbacks suppressed Jul 22 16:09:29 khaeru-laptop kernel: traps: gnome-shell[2272] general protection fault ip:7fed3504129a sp:7fff9fbf98e8 error:0 in libc-2.31.so[7fed34edf000+178000] or Jul 22 16:31:27 khaeru-laptop kernel: gnome-shell[43253]: segfault at 0 ip 7f13545d7252 sp 7ffe6cc45bf0 error 4 in libst-1.0.so[7f13545b7000+4c000] Jul 22 16:31:27 khaeru-laptop kernel: Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f Despite the different symptoms, this occurs 100% of the time. $ lsb_release -rd && apt-cache policy gnome-shell Description:Ubuntu 20.04 LTS Release:20.04 gnome-shell: Installed: 3.36.2-1ubuntu1~20.04.1 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: 3.36.3-1ubuntu1~20.04.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.2-1ubuntu1~20.04.1 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
More info: * ubuntu-driver install did not install nvidia-dkms-440 (had to be installed by hand) * Upon boot, /sys/bus/pci/devices/:01:00.0/power/control is set to `auto`, but the GPU is powered on. Setting it to `on` then to `auto` again powers down the GPU. * This temporary fix above survives suspend/resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description: Ubuntu 20.04 LTS Release: 20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
I'm on a Dell XPS 9560, i7-7700HQ, GP107M (GTX 1050 mobile). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description: Ubuntu 20.04 LTS Release: 20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877727] Re: Nvidia dGPU active despite prime-select set to Intel card
The path to this issue for me is different. I installed this laptop originally with 19.04 and nvidia-435 (possibly post installation?) and all was well upon upgrade to 19.10 and later on to 20.04. Upgrading to 20.04 kept the nvidia-435 driver and this bug did not manifest. Today I upgraded the driver to nvidia-440 via `ubuntu-driver install` and the issue started happening - the gpu is still powered up even though I rebooted into intel. I switched back and forth using `prime- select`. I tried reverting back to nvidia-435 to no avail. I can apply the "fix" via powertop (it does `echo 'auto' > '/sys/bus/pci/devices/:01:00.0/power/control';`) and I can confirm this shuts down the GPU properly and cuts power usage dramatically, until next boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1877727 Title: Nvidia dGPU active despite prime-select set to Intel card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After fresh installation of Ubuntu 20.04 I changed used card to Intel GPU with command "sudo prime-select intel". After reboot Intel card is used to display, but dGPU is still active (more heat and power consumption, this laptop also has led that indicate dGPU activation). In Ubuntu 19.04 which I used till today, after change to iGPU, laptop use iGPU and dGPU is in inactive state. I have MSI PE70 7RD laptop with Intel 7700HQ processor and NVIDIA 1050 GPU. I found similar problem on net, but without solution. https://askubuntu.com/questions/1232461/ubuntu-20-04-dgpu-is-always-on Workaround that I found is use "powertop" and in Tunables card activate power saving for dGPU card "Runtime PM for PCI Device NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile]", but I think it should work without such changes every reboot. Description: Ubuntu 20.04 LTS Release: 20.04 nvidia-prime: Installed: 0.8.14 Candidate: 0.8.14 Version table: *** 0.8.14 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://pl.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 9 11:38:41 2020 Dependencies: InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1877727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880031] Re: Thumbnail is stretched if its aspect ratio is less than that of the container
** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: New => Fix Committed ** Description changed: + [ Impact ] + + Image thumbnails are stretched if the aspect ratio is less than the one + of the container + + [ Test case ] + + To reproduce, create an image that has aspect ratio, e.g., ~0.5 (e.g. + width = 250 and height = 500) + + Save it in the desktop and ensure that the image has proper proportions. + + + [ Regression potential ] + + Image thumbnails are distorted + + + This was discovered when investigating fix for bug #1868529. Aspect ratio is still not correct for images that are more narrow than the container. To reproduce, create an image that has aspect ratio, e.g., ~0.5 (e.g. width = 250 and height = 500). Line in fileItem.js where we calculate icon width does not count the margins (zero is used instead of actual margins): let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0); Here is how the margins are being calculated in desktopGrid.js: - this._extra_width = themeNode.get_margin(St.Side.LEFT) + - themeNode.get_margin(St.Side.RIGHT) + - themeNode.get_border_width(St.Side.LEFT) + - themeNode.get_border_width(St.Side.RIGHT) + - themeNode.get_horizontal_padding(); - this._extra_height = themeNode.get_margin(St.Side.TOP) + - themeNode.get_margin(St.Side.BOTTOM) + - themeNode.get_border_width(St.Side.TOP) + - themeNode.get_border_width(St.Side.BOTTOM) + - themeNode.get_vertical_padding(); + this._extra_width = themeNode.get_margin(St.Side.LEFT) + + themeNode.get_margin(St.Side.RIGHT) + + themeNode.get_border_width(St.Side.LEFT) + + themeNode.get_border_width(St.Side.RIGHT) + + themeNode.get_horizontal_padding(); + this._extra_height = themeNode.get_margin(St.Side.TOP) + + themeNode.get_margin(St.Side.BOTTOM) + + themeNode.get_border_width(St.Side.TOP) + + themeNode.get_border_width(St.Side.BOTTOM) + + themeNode.get_vertical_padding(); -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1880031 Title: Thumbnail is stretched if its aspect ratio is less than that of the container Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Committed Bug description: [ Impact ] Image thumbnails are stretched if the aspect ratio is less than the one of the container [ Test case ] To reproduce, create an image that has aspect ratio, e.g., ~0.5 (e.g. width = 250 and height = 500) Save it in the desktop and ensure that the image has proper proportions. [ Regression potential ] Image thumbnails are distorted This was discovered when investigating fix for bug #1868529. Aspect ratio is still not correct for images that are more narrow than the container. To reproduce, create an image that has aspect ratio, e.g., ~0.5 (e.g. width = 250 and height = 500). Line in fileItem.js where we calculate icon width does not count the margins (zero is used instead of actual margins): let containerWidth = Prefs.getDesiredWidth(scaleFactor, 0); Here is how the margins are being calculated in desktopGrid.js: this._extra_width = themeNode.get_margin(St.Side.LEFT) + themeNode.get_margin(St.Side.RIGHT) + themeNode.get_border_width(St.Side.LEFT) + themeNode.get_border_width(St.Side.RIGHT) + themeNode.get_horizontal_padding(); this._extra_height = themeNode.get_margin(St.Side.TOP) + themeNode.get_margin(St.Side.BOTTOM) + themeNode.get_border_width(St.Side.TOP) + themeNode.get_border_width(St.Side.BOTTOM) + themeNode.get_vertical_padding(); To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1880031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist while resizing or rebooting in VM windows
Well, I'd handle this in a different bug... I see the problem, but as you said this is a virtual window and the flag mutter uses, isn't specific enough to determine whether this a virtual window. But giving that the issue of preserving the configuration, when the window has the same size, I'd mark this as resolved, while please open a new report about the problem of scaling not being preserved while the window is resized. This is something that might not be easy to address, but I will see what's possible. ** 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/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 1879352] Re: /usr/bin/im-launch i3 fails
You are correct that uninstalling `im-config` and reverting `99x11-common_start` to its original `exec $STARTUP`. But that just hides the issue by removing the package containing the bug, and in particular these lines in `70im-config_launch`: ``` if [ -x "$IMLAUNCH" ]; then STARTUP="$IMLAUNCH $STARTUP" fi ``` I'm sorry to insist, but I think the understanding of the issue is incomplete. Please look at the error message in the first comment, and compare: ``` rubin ~ $ bash -c '/usr/bin/nosuch xyz' bash: /usr/bin/nosuch: No such file or directory rubin ~ $ bash -c '"/usr/bin/nosuch xyz"' bash: /usr/bin/nosuch xyz: No such file or directory ``` the shell includes only the first component of the command line in its error message, indicating that it has searched for that string in PATH. In the first comment, you'll see that a space character and `i3` appear in the error message. Another fix to this issue is to replace ``` exec $STARTUP ``` with ``` $STARTUP ``` meaning that something in how dash is interpreting that `exec` is causing it to not split the argument correctly. If this was bash I might suspect that STARTUP was an array, but dash appears to not support arrays. It should be possible to replicate this with a new install, installing i3 and selecting that option from the login menu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1879352 Title: /usr/bin/im-launch i3 fails Status in i3-wm package in Ubuntu: Expired Status in im-config package in Ubuntu: New Bug description: Trying to run i3 in Focal Fossa, login fails. The screen goes black briefly, then returns to the login screen. I expect this is reproducible by just installing `i3`, selecting it on the settings in the login screen, and logging in. I see the following in the log: ``` May 18 11:32:21 hopper /usr/lib/gdm3/gdm-x-session[4733]: /etc/X11/Xsession.d/99x11-common_start: line 5: /usr/bin/im-launch i3: No such file or directory ``` Editing that file to just run `/usr/bin/im-launch i3` works fine. Is this some kind of shell quoting issue, where it's trying to execve that full string? I believe this is in the `x11-common` package: ``` hopper ~ $ dpkg -S /etc/X11/Xsession.d/99x11-common_start x11-common: /etc/X11/Xsession.d/99x11-common_start ``` but Launchpad complains that such a thing does not exist. Perhaps I misunderstand "package". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/i3-wm/+bug/1879352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
I made this video after the last updates, which include: pulseaudio-libraries and linux-firmwares. I created a new user, to see if it was a desktop problem or user settings, but the problem remained. We are available. Hugs. Thanks. ** Attachment added: "sem título.webm" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884255/+attachment/5394894/+files/sem%20t%C3%ADtulo.webm -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
[Desktop-packages] [Bug 1886565] Re: SRU the current 3.36.7 stable update
With -proposed enabled I upgraded evince to version 3.36.7-0ubuntu1. As per the test case I opened a number of .pdf and .ps files. They all appeared to render correctly. ** 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 evince in Ubuntu. https://bugs.launchpad.net/bugs/1886565 Title: SRU the current 3.36.7 stable update Status in evince package in Ubuntu: Fix Released Status in evince 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/evince/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Open some pdf and ps documents, check that they render properly * Regression potential There is no specific change or feature to test in this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1886565/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888505] [NEW] Two-finger touchpad zoom extremely sensitive
Public bug reported: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). 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:43:20 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) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). 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:43:20 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/1888505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] Two-finger touchpad scroll broken
Public bug reported: 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) ** Affects: libreoffice (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 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 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
@Daniel van Vugt Thanks for your understanding and advice. Do you have any recommendations for an alternative window manager that is: - Officially Supported by Canonical under the support contract - Touchscreen Friendly - Secure - Has a sidebar on the left (the product I sell is designed around the Unity design) Gnome is supposed to be the de-facto standard Linux desktop for most distributions. I still don't understand why all these regression bugs are entering Gnome, and the Gnome developers are so hostile to listening to the users and use cases of their desktop. See the gitlab board you pointed me to where the dev, on the subject of the on screen keyboard, just says, nope, I designed it this way, not listening to reason of more than 30 people and then locks the ticket. Even you said "If that's true then this is not a bug." in regards to window placement. Which is just mind boggling, of course it's a bug when the window manager clearly prevents the end user from using the system. There also needs to be an easier way to report things upstream. At the moment everything has to be typed over into a new ticket from Launchpad to Github. Can't there just be some kind of export ticket to GitHub markup? Thanks again for any recommendations on Canonical supported Window Managers. -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
Hi Rene, We are sorry for the hassle caused, but the fix is currently being in the final stage of backporting and will be complete backporting this week, and you can track them at https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1877016, https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920 and https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924. You can also get the fix from here now: https://launchpad.net/~callmepk/+archive/ubuntu/wslu-dev -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created Status in wslu package in Ubuntu: Fix Released Bug description: [ Impact ] * When $HOME/.cache can't be created an error is shown: mkdir: cannot create directory ‘//.cache’: Permission denied [Test Case] * TODO [Regression Potential] * TODO [Other Info] Originally reported to: https://github.com/wslutilities/wslu/issues/101 In addition to suppressing the error message it would probably be also useful to disable the detection by default for system users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader
This is actually a known PAM module issue: https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/64 However, the bug itself is due to a driver error that is hard to debug, so we will need the hardware go do proper analysis. ** Changed in: libfprint (Ubuntu) Status: Triaged => Won't Fix ** Also affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu) Status: New => Triaged ** Changed in: fprintd (Ubuntu) Importance: Undecided => High ** Changed in: fprintd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: fprintd (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader Status in fprintd package in Ubuntu: Triaged Status in libfprint package in Ubuntu: Won't Fix Bug description: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Related to bug #1881380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888495] [NEW] fprintd-verify fails with an USB UPEK reader
Public bug reported: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Related to bug #1881380 ** Affects: libfprint (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Triaged ** Changed in: libfprint (Ubuntu) Status: In Progress => Triaged ** Description changed: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - - fprintd-verify + - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified - lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 + + Related to bug #1881380 ** Changed in: libfprint (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader Status in libfprint package in Ubuntu: Triaged Bug description: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Related to bug #1881380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1888495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
It is hard to feel any enthusiasm from Ubuntu to backport the fix. Considering how many issues I have run into trying to use Ubuntu WSL image, I am not sure Ubuntu has any real interest in WSL. Just like Apple is not really into that boot camp thingy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created Status in wslu package in Ubuntu: Fix Released Bug description: [ Impact ] * When $HOME/.cache can't be created an error is shown: mkdir: cannot create directory ‘//.cache’: Permission denied [Test Case] * TODO [Regression Potential] * TODO [Other Info] Originally reported to: https://github.com/wslutilities/wslu/issues/101 In addition to suppressing the error message it would probably be also useful to disable the detection by default for system users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
Yes, I do believe it's the same PA instance, I had not noticed it restarting (e.g. pavucontrol losing the connection) when testing around this bug. Also, I'm not sure if it helps, but the module likes to spam a ton of pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. pulseaudio[11451]: E: [pulseaudio] module-snap-policy.c: AppArmor profile could not be retrieved. into the log even when *not* running as a snap. I don't know if this is related as I've found it to be harmless to the functionality of my programm when running outside snaps. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the
[Desktop-packages] [Bug 1880405] Re: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
thanks Dan `killall -3 gnome-shell` keeps me sane. No longer need to reboot everyday. -- 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/1880405 Title: High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04
I also found a trick how to make it work again, you close the lit of my
XPS15 laptop and open is again. Then it works again.
(Maybe helps some people who really need this to work ASAP for
development)
Maybe it has something to do with the Gnome Session? As the touchscreen
works in the login screen, then after login it stops working after "one"
touch. Then closing the lit and the touchscreen works fine again.
I have an XPS-15-9530 Dell laptop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1876991
Title:
Touchpad started appearing both as a touchpad and as a mouse input
devices after upgrade to 20.04
Status in xserver-xorg-input-synaptics package in Ubuntu:
Confirmed
Bug description:
It was working perfectly on 18.04 with 5.3 kernel but after upgrade to
20.04 it's becoming disabled because there is a "mouse" attached which
is the same touchpad detected incorrectly, xinput --list showing both
⎜ ↳ MSFT0001:00 06CB:7E7E Mouse id=11 [slave pointer (2)]
⎜ ↳ MSFT0001:00 06CB:7E7E Touchpadid=12 [slave pointer (2)]
The first line was definitely not present before, I know it because I
use it when in openbox session.
There is also a number of questions on AskUbuntu that look like results of
the same problem at first glance:
https://askubuntu.com/q/1231873/20275
https://askubuntu.com/q/1235067/20275
https://askubuntu.com/q/1234975/20275
and two global search results for the same touchpad model ("MSFT0001:00
06CB:7E7E Mouse") that show the same problem in unrelated contexts:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953405
https://bbs.archlinux.org/viewtopic.php?id=240723
I also have these errors in kernel log, may be related, weren't present
previously:
psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
psmouse serio1: Failed to enable mouse on isa0060/serio1
psmouse serio1: Failed to disable mouse on isa0060/serio1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed May 6 00:09:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 5471
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic
root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq
resume=/dev/mapper/ocz-swap_1 crashkernel=384M-2G:128M,2G-:256M
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 05F5VX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: Zahoriya
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.9.0:bd07/25/2018:svnDellInc.:pnVostro5471:pvr:rvnDellInc.:rn05F5VX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5471
dmi.product.sku: 0830
dmi.sys.vendor: Dell 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 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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/xserver-xorg-input-synaptics/+bug/1876991/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
I think I need to dig into this further. The fact you're seeing a few successful module loads with different module indexes would indicate it is the same Pulse Audio instance. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to do an operation. ADDITIONAL INFORMATION == $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500
[Desktop-packages] [Bug 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04
Im not so deep into the technical part but:
Touchscreen does work in the login screen perfectly. After you log in the
touchscreen works for few seconds and after that stops working.
I use the touchscreen for application development testing. So hope this
get solved. Anyone a quick fix for this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1876991
Title:
Touchpad started appearing both as a touchpad and as a mouse input
devices after upgrade to 20.04
Status in xserver-xorg-input-synaptics package in Ubuntu:
Confirmed
Bug description:
It was working perfectly on 18.04 with 5.3 kernel but after upgrade to
20.04 it's becoming disabled because there is a "mouse" attached which
is the same touchpad detected incorrectly, xinput --list showing both
⎜ ↳ MSFT0001:00 06CB:7E7E Mouse id=11 [slave pointer (2)]
⎜ ↳ MSFT0001:00 06CB:7E7E Touchpadid=12 [slave pointer (2)]
The first line was definitely not present before, I know it because I
use it when in openbox session.
There is also a number of questions on AskUbuntu that look like results of
the same problem at first glance:
https://askubuntu.com/q/1231873/20275
https://askubuntu.com/q/1235067/20275
https://askubuntu.com/q/1234975/20275
and two global search results for the same touchpad model ("MSFT0001:00
06CB:7E7E Mouse") that show the same problem in unrelated contexts:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953405
https://bbs.archlinux.org/viewtopic.php?id=240723
I also have these errors in kernel log, may be related, weren't present
previously:
psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
psmouse serio1: Failed to enable mouse on isa0060/serio1
psmouse serio1: Failed to disable mouse on isa0060/serio1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed May 6 00:09:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 5471
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic
root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq
resume=/dev/mapper/ocz-swap_1 crashkernel=384M-2G:128M,2G-:256M
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 05F5VX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: Zahoriya
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.9.0:bd07/25/2018:svnDellInc.:pnVostro5471:pvr:rvnDellInc.:rn05F5VX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5471
dmi.product.sku: 0830
dmi.sys.vendor: Dell 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 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
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/xserver-xorg-input-synaptics/+bug/1876991/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888392] Re: The libreoffice interface does not appear in Ubuntu MATE
** Summary changed: - The libreoffice interface does not appear + The libreoffice interface does not appear in Ubuntu MATE -- 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 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/+source/libreoffice/+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 1886854] Re: Race in load-module snap policy check in classic confinement
I think there's two issues at play here. The hooks we added for module loading/unloading as part of USN-4355-1 simply check if the client has an AppArmor label that looks like it belongs to a snap and denies access if found. This will also deny access to classic snaps, which is probably a mistake. The race condition you've encountered is probably a case of "policy module not in effect" vs. "policy module in effect" rather than a race in the behaviour of the policy module itself. This probably indicates that Pulse is servicing client requests before it has completely started. For the first issue, we can make the hook request info about the snap and allow access to classic snaps. For the second, I think we just need to load module-snap-policy earlier during start up. -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Description changed: + [ Impact ] + In some platforms with specific Nvidia drivers, auto-login will fail due to the old vt-handoff patch in grub2. + + [ Test Case ] + 1. Boot ubuntu into desktop environment. + 2. Enabled auto login in System->Users + 3. Reboot the system + + [Expected result] + System will boot into desktop environment without the login page. + + [Actual result] + System boots to login page, and can't login to desktop environment with the correct password. + + [ Regression potential ] + Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. + + --- + I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-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 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 ** Description changed: [ Impact ] - In some platforms with specific Nvidia drivers, auto-login will fail due to the old vt-handoff patch in grub2. + In some platforms with specific Nvidia drivers, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password.
[Desktop-packages] [Bug 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows
Made a quick video to illustrate the issues: https://youtu.be/SwBtxqTqsHc ** Summary changed: - Fractional scaling does not persist across reboots in resizable VM windows + Fractional scaling does not persist while resizing or rebooting in VM windows -- 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 1884754] Re: Fractional scaling does not persist across reboots in resizable VM windows
Behaviour seems somewhat improved but the root issue is still there. When rebooting with VMware Player running the scaling is now remembered correctly, however if I then shut the VM down completely and restart it, it still starts up at first in default screen size, removing the scaling. Also the scaling modifications seem more aggressive now - if I have the windowed VMware Player maximized on my 4k screen (practical resolution 3840x2015, note not 2160 pixels high due to host window chrome) it allows me to set 125% scaling, but if I then resize the host window or just unmaximize the 125% options disappear from setting *and Ubuntu snaps right back to 200%*. So effectively what I described in https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/9 is still happening as before. I still think https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1884754/comments/11 is the only true fix - in _virtual_ monitors the system should never intervene with scaling settings at all and just trust whatever the user selects for himself, as he may be resizing, maximizing, changing displays etc. all the time. -- 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 1653351] Re: Have option to not automatically open next email
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low ** Changed in: thunderbird (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Invalid Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 Status in libfprint: Unknown Status in gnome-control-center package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Committed Bug description: [ Impact ] When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". For information, my fingerprint sensor is : - lsusb Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor [ Test case ] With a fingerprint reader 138a:0050: - Open gnome-control-center user-accounts - Select the fingeprint row to enroll a finger - Follow the procedure and the finger should be enrolled - Verify with: fprintd-list $USER [ Regression potential ] - The fingerprint is not read by the sensor --- Ubuntu 20.04 gnome-control-center: Installé : 1:3.36.1-1ubuntu5 Candidat : 1:3.36.1-1ubuntu5 Table de version : *** 1:3.36.1-1ubuntu5 500 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen, is that everything works and that I can set up my finger for unlocking. What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 22:00:30 2020 InstallationDate: Installed on 2020-05-11 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
Works great for me too !! Thanks for the update ! -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 Status in libfprint: Unknown Status in gnome-control-center package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Committed Bug description: [ Impact ] When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". For information, my fingerprint sensor is : - lsusb Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor [ Test case ] With a fingerprint reader 138a:0050: - Open gnome-control-center user-accounts - Select the fingeprint row to enroll a finger - Follow the procedure and the finger should be enrolled - Verify with: fprintd-list $USER [ Regression potential ] - The fingerprint is not read by the sensor --- Ubuntu 20.04 gnome-control-center: Installé : 1:3.36.1-1ubuntu5 Candidat : 1:3.36.1-1ubuntu5 Table de version : *** 1:3.36.1-1ubuntu5 500 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen, is that everything works and that I can set up my finger for unlocking. What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 22:00:30 2020 InstallationDate: Installed on 2020-05-11 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886644] Re: SRU the current 3.36.4 stable update
It's worth checking with the security team indeed, thanks for pointing that out, meanwhile it doesn't hurt to have it in -proposed and get some initial testing there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1886644 Title: SRU the current 3.36.4 stable update Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server 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/evolution-data-server/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the calendar integration in GNOME and gnome-calendar is working, also test evolution with an email account. * Regression potential There is no specific change or feature to test in the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1886644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
Hello together, works as expected. Thanks! Ubuntu 20.04, libfprint-2-2 1:1.90.2+tod1-0ubuntu1~20.04.1, FUJITSU LIFEBOOK U748 -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 Status in libfprint: Unknown Status in gnome-control-center package in Ubuntu: Won't Fix Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Committed Bug description: [ Impact ] When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". For information, my fingerprint sensor is : - lsusb Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor [ Test case ] With a fingerprint reader 138a:0050: - Open gnome-control-center user-accounts - Select the fingeprint row to enroll a finger - Follow the procedure and the finger should be enrolled - Verify with: fprintd-list $USER [ Regression potential ] - The fingerprint is not read by the sensor --- Ubuntu 20.04 gnome-control-center: Installé : 1:3.36.1-1ubuntu5 Candidat : 1:3.36.1-1ubuntu5 Table de version : *** 1:3.36.1-1ubuntu5 500 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen, is that everything works and that I can set up my finger for unlocking. What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 22:00:30 2020 InstallationDate: Installed on 2020-05-11 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_BE:fr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_BE.UTF-8 SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888458] Re: text not displaying ubuntu 20.04
* It has been found that this error was caused by a MISSING FONT * Someplace during the Ubuntu 19.10 to Ubuntu 20.04 upgrade process the font Courier New was completely removed. * It is not clear what the use-case would be to removea font in the first place. * Nothing in the removed packages list indicates that this font was removed. It would be useful for the terminal to report an error on a missing font file. ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1888458 Title: text not displaying ubuntu 20.04 Status in gnome-terminal package in Ubuntu: Invalid Bug description: * Have upgraded from Ubuntu 10.10 to Ubuntu 20.04 * Rebooted PC * After reboot, and login * Opened gnome-terminal * something displays, but it is NOT Text * completely unreadable (screen shot attached) * with no terminal, I'm restricted in what I may do to trouble shoot this problem. * Nvidia graphics -- Updating to latest available: nvidia-driver-440, did not help GNOME-TERMINAL not working for this Ubuntu 20.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1888458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I don't have a focal system with nvidia or multi-monitors. Can anyone else verify comment #27? -- 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: Confirmed Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers source package in Focal: Confirmed 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 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I don't have a focal system with nvidia right now. Can anyone else verify comment #27? -- 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: Confirmed Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers source package in Focal: Confirmed 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
