[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
OMG, this looks like it's it. On my main computer with Geforce 330M I have a background that's 1x screen res and I haven't been getting the corrupted background. I just switched to a stock Ubuntu bg image, which I presume is much larger than 1440x900, suspended the machine and now it's completely white. The corruption I now get after resume from suspend is this: 1. The Gnome menu (the one on the left after pressing the super key) when using Gnome session is corrupted or invisible. Moving the mouse over the icons makes them appear and closing and re-opening the overlay fixes it. The left menu from Ubuntu session seems fine, but I only tried a couple of suspends as I use the Gnome session. 2. Current program icon in the top bar of the Gnome session gets corrupted. 3. Icons in some applications (like Cura) get corrupted. I think it may be related to Qt. But I guess that would be a different bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX 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.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about
[Desktop-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Sounds like a userspace issue. Have you tried any chromium based browser? -- 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 : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -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 jackpoll_ms :
[Desktop-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Do you see the issue on Ubuntu proper? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted
this is what I got so far, please tell me if you need more information: - leder@home-ryzen-desktop:~$ apport-retrace --stdout /var/crash/_usr_libexec_gnome-shell-hotplug-sniffer.1000.crash ERROR: report file does not contain one of the required fields: Package - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887263 Title: nautilus freezes possibly in connection w/ samba share mounted/unmounted Status in nautilus package in Ubuntu: In Progress Bug description: test steps: - mouunt samba share w/: smb://host/share - open local disc w/ personal folder - scroll directory e. g. w/ show hidden files enabled in order to get a long list expected result: directory scrolls up and down actual result: scrolling freezes for some seconds before scrolling completes: - no directory selection appears until after freeze is over - only selection possible is the mounted samba share, which returns to the top level directory of the share leder@home-ryzen-desktop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 leder@home-ryzen-desktop:~$ apt-cache policy nautilus nautilus: Installiert: 1:3.36.3-0ubuntu1 Installationskandidat: 1:3.36.3-0ubuntu1 Versionstabelle: *** 1:3.36.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 Uname: Linux 5.6.19-050619-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 04:32:18 2020 InstallationDate: Installed on 2020-06-22 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887829] Re: graphic card not working
Please reproduce the freeze again, reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-340/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887383] Re: Yaru updates not related to themes and icons
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887383 Title: Yaru updates not related to themes and icons Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Several parts of the build, including the yaru README and github actions to stay synced with upstream, are out of date and need updates. Those changes are: - fix Yaru project name + update README pictures - build: deduplicate meson.build and introduce Flavours https://github.com/ubuntu/yaru/pull/1884 - add libgtk-3-dev to the bootstrap script https://github.com/ubuntu/yaru/pull/ - updates to the upstream directories, which include the source code of the unmodified upstream gnome-shell and gtk3 themes https://github.com/ubuntu/yaru/pull/2084 - Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py to avoid errors while building https://github.com/ubuntu/yaru/pull/2206 - Check for updates to GitHub Actions every weekday https://github.com/ubuntu/yaru/pull/2223 - Adding new non-uniform app icon templates https://github.com/ubuntu/yaru/pull/1920 * Backporting these updates to focal, will greatly improve the build process of the yaru project and help to avoid bugs and help the development of the team * all fixes are in yaru master since several weeks and have been tested several times [Test Case] * Look at the yaru project page while in this branch https://github.com/ubuntu/yaru/tree/ubuntu/focal and find the images to be removed * Look at the yaru project page while in the master branch https://github.com/ubuntu/yaru/tree/master and find all images to show what currently is in focal * All other test cases are described in the corresponding pull requests [Regression Potential] * Outdated versions of meson may clash with the current yaru build, otherwise, no regression potential * Unity theme misses assets [Other Info] * Those changes are not "visible" for the end-user while using the ubuntu desktop, i.e. no theme changes, no icon changes here, but they greatly improve the daily work of the yaru team To manage notifications about this bug go
[Desktop-packages] [Bug 1887389] Re: Microphone icon outlines can look fuzzy on certain screens
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887389 Title: Microphone icon outlines can look fuzzy on certain screens Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * The microphone icon only consists of small outlines which are very close to each other, making the icon look fuzzy and hard to understand, especially on screens with high sharpness * Backporting this to focal would greatly improve the visibility and legibility of the microphone icon and thus help to improve the overall look of the ubuntu desktop in focal * The fix is already in ubuntu master: https://github.com/ubuntu/yaru/pull/2200 [Test Case] * If your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display until the icon becomes fuzzy and hard to understand * Build yaru from master and if your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display and watch how the icon stays sharp and "intact" even with high sharpness [Regression Potential] * No regression potential, tested by building the branch of the pull request [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887393] Re: The system-lock-screen icon has a twisted/deformed path
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887393 Title: The system-lock-screen icon has a twisted/deformed path Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * The lock icon in gnome-control-center privacy page has a twisted path in it's key-hole * Backporting this to focal, would greatly increase the level of visual polish and increase the professional look of the ubuntu desktop and the yaru icon theme * The fix is already in the yaru master branch: https://github.com/ubuntu/yaru/issues/2201 [Test Case] * Open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see the twisted path of the key whole * Build yaru from master, open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see that the path of the key-hole is now an even square [Regression Potential] * No regression potential, tested by building the branch in the pull request [Other Info] * Link to the github issue: https://github.com/ubuntu/yaru/issues/2201 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887300] Re: Wacom overlay text labels are invisible
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887300 Title: Wacom overlay text labels are invisible Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: https://github.com/ubuntu/yaru/issues/2099 [Impact] * The wacom overlay text is invisible and users can not use this gnome-shell dialog to map their wacom tablet hardware buttons * Backporting this to the stable release focal will let wacom users use this dialogue again, which is very important because you have no other way to map it in ubuntu * The fix is already in yaru master https://github.com/ubuntu/yaru/pull/2198 [Test Case] * Plug a wacom tablet to your computer, search for "wacom" in the gnome shell search and press enter to open the corresponding gnome- control-center page. Now open the dialog to map your buttons. See how the labels for each button are invisible * Build yaru from master and repeat these steps and see how the labels appear and you can properly map the correct button [Regression Potential] * No regression potential * Built and tested with the yaru master branch [Other Info] * Yaru issue: https://github.com/ubuntu/yaru/issues/2099 * yaru fix: https://github.com/ubuntu/yaru/pull/2198 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887388] Re: Several mimetype icons are missing
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887388 Title: Several mimetype icons are missing Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Many mimetype icons are not showing up in yaru, even if they have been included in the yaru theme suite and some mimetype icons are were not included previously * Backporting them to focal would greatly increase the differentiation of the file types that are existent for the average user * All those fixes are already in yaru master: - img and iso https://github.com/ubuntu/yaru/pull/2213 - Lilypond https://github.com/ubuntu/yaru/pull/2230 - QML https://github.com/ubuntu/yaru/pull/2226 - log files https://github.com/ubuntu/yaru/pull/2229 - arduino, jpynbgjson, mswinurl, cursor https://github.com/ubuntu/yaru/pull/2234 - scala https://github.com/ubuntu/yaru/pull/2231 - lmms https://github.com/ubuntu/yaru/pull/2249 - theme files https://github.com/ubuntu/yaru/pull/2243 - rss https://github.com/ubuntu/yaru/pull/2248 - executable https://github.com/ubuntu/yaru/pull/2204 - apple images https://github.com/ubuntu/yaru/pull/2233 [Test Case] * open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have either a generic text file as their mimetype icon or the wrong mimetype icon * install yaru master branch and open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have the correct mimetype icons which make it very clear what is inside those files [Regression Potential] * No regression potential, tested by building all pull requests [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1887298] Re: blue GtkSpinner is hard to see on red .destrucive-action buttons
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887298 Title: blue GtkSpinner is hard to see on red .destrucive-action buttons Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Blue blue GtkSpinner is hard to see on red .destrucive-action buttons, like the "Stop scanning" button in simple-scan, Link to the yaru github issue: https://github.com/ubuntu/yaru/issues/2182 * Reason to backport this to focal: users have it very hard to see the spinner, especially color blind people, backporting this will greatly improve the accessibility and legibility of the yaru theme and the ubuntu desktop for focal users [Test Case] * Press the green "Scan" button in simple-scan and it will turn red with a "Stop" label and a blue spinner inside the button. The spinner is hard to see on this red background * Build yaru from master and notice how the white spinner is much more visible against a red background [Regression Potential] * No regression potential * Tested by building yaru from source [Other Info] * Link to the github pull request: https://github.com/ubuntu/yaru/pull/2187 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887297] Re: gnome-shell notifications and gtk3 menus are hard to distinguish from the background
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887297 Title: gnome-shell notifications and gtk3 menus are hard to distinguish from the background Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Gtk and shell menus, popups and notifications are often hard to distinguish against the elements that are beneath them (Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217) * backporting this QOL change to focal would greatly improve the legibility of the yaru theme(s) * the fixes for this are already in the master branch of https://github.com/ubuntu/yaru [Test Case] * populate gtk3 menus against a nautilus window and spawn a notification by either adding or removing a favourite app in the dock with rightclick add/remove favourite. Gtk3 menus almost look like they are part of the window and not a different part of the desktop. Notifications, especially when using yaru-light are also hard to see and recognize [Regression Potential] * No regression potential * Tested by building the fixed branch(es) of yaru and then switching back and forth the gtk3 and shell themes, please see the corresponding github pull requests https://github.com/ubuntu/yaru/pull/2232 + https://github.com/ubuntu/yaru/pull/2236 [Other Info] * Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887411] Re: system-users-symbolic icon has unclear visual metaphor
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887411 Title: system-users-symbolic icon has unclear visual metaphor Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: New Bug description: [Impact] * The system-users-symbolic icon doesn't represent users in the plural. It shows a single generic figure (head and shoulders) representing one user. This is a misleading visual metaphor, since a single head and shoulders is universally recognised as the current or logged-in user. * Reason to backport to Focal: the corresponding Adwaita icon shows two users. Third party apps that use the icon will expect it to represent more than one person. Failing to provide a suitable icon will have confusing results in Ubuntu. [Test Case] * Install Lollypop and look at the sidebar. "Compilations" has the symbol of a single user, which is confusing. Lollypop requested an icon with multiple figures to represent multiple artists, but Ubuntu supplied something inappropriate. This issue may be duplicated whenever a third party app uses this icon. * Build Yaru from Master and notice how the icon now has the same visual metaphor as Adwaita (i.e., it shows two users). The Lollypop UI makes more sense and the theme honours the app's intentions. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the Github PR: https://github.com/ubuntu/yaru/pull/2209 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887419] Re: Lollypop music player mixes Yaru and Adwaita symbols
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887419 Title: Lollypop music player mixes Yaru and Adwaita symbols Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Triaged Bug description: [Impact] * The Yaru theme has some of the icons used by Lollypop but not all of them. This results in the Lollypop sidebar having a mix of Adwaita symbols (with 2px strokes) and Yaru ones (which have 1px). See GitHub issue https://github.com/ubuntu/yaru/issues/2208. * Reason to backport to Focal: displaying symbols from two different themes gives a poor impression of Ubuntu to users who want to use a popular native music player. [Test Case] * Install Lollypop and look at the sidebar. Some of the symbols are heavy and some are light. (Alternatively, the GitHub issue linked above has a screenshot.) * Build Yaru from Master and notice how the Lollypop sidebar is now consistent with itself and the rest of the Yaru theme. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Links to the GitHub PRs: https://github.com/ubuntu/yaru/pull/2235 and https://github.com/ubuntu/yaru/pull/2253. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887420] Re: network-cellular-connected-symbolic isn't monochrome
This bug was fixed in the package yaru-theme - 20.10.2 --- yaru-theme (20.10.2) groovy; urgency=medium [ Carlo Lobrano ] * update README pictures (LP: #1887383) * build: deduplicate meson.build and introduce Flavours (#1884) (LP: #1887383) * fix Yaru project name (LP: #1887383) * Fix spinner typo in tweaks.scss (LP: #1887383) * bootstrap: libgtk-3-dev is needed for building too (#) (LP: #1887383) [ Feichtmeier ] * Gtk theme new changes from upstream (#2195) * Special case spinners in destructive, suggested action buttons (#2187) (LP: #1887298) * Make wacom overlay visible (#2198) (LP: #1887300) * Shell: revert insensitive fg color change (#2199) * Gtk3: increase menu visibility (#2232) (LP: #1887297) * Shell: popup and notification improvements (#2236) (LP: #1887297) [ github-actions[bot] ] * New upstream snapshot for GTK (#2084) [ Ԝеѕ ] * icons - add application/x-sharedlib alias for x-executable (#2204) * Use CD image icon for apple disk images (#2233) [ Chris Billington ] * Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py (#2206) (LP: #1887383) [ ubuntujaggers ] * adding second user to system-users (#2209) (LP: #1887411) * Adding mimetype for LMMS projects (#2249) (LP: #1887388) * Some missing icons for Lollypop UI (#2235) (LP: #1887419) * Adding new non-uniform app icon templates (#1920) * removing green from network-cellular-connected-symbolic (#2252) (LP: #1887420) * rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ John Losito ] * Check for updates to GitHub Actions every weekday (#2223) (LP: #1887383) [ Jupiter007 ] * Add a solid background to microphone icons (#2200) (Closes: #2185) (LP: #1887389) * Re: Fix lock icons twisted path (#2205) (Closes: #2201) (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ MadsRH ] * Added text to img and iso icons (#2213) * Added mimetype for Lilypond music files (#2230) (LP: #1887388) * Added icon for QML mimetypes (#2226) (LP: #1887388) * Added mimetype icon for log files (#2229) (LP: #1887388) * Added more mimetype icons again (#2234) (LP: #1887388) * Added mimetype icon for Scala files (#2231) (LP: #1887388) [ Muqtadir ] * mimetype application-x-theme (#2243) (LP: #1887388) * Mimetypes application x rss+xml (#2248) (LP: #1887388) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 02:43:50 +0200 ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887420 Title: network-cellular-connected-symbolic isn't monochrome Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Triaged Bug description: [Impact] * The icon called network-cellular-connected-symbolic appears at the top right of the desktop when users connect to their phones via bluetooth to use data. The icon includes green fill, which is inconsistent with the monochrome icons used for (e.g.) wifi. See GitHub issue https://github.com/ubuntu/yaru/issues/2192. * Reason to backport to Focal: the inconsistency was missed because I don't use this feature and it's an unfortunate oversight. When the icon appears, it does so in a prominent position and is constantly visible to the user, giving a poor impression of Ubuntu. [Test Case] * Use Bluetooth tethering so your laptop is making use of your phone's data connection. Notice that, unlike the rest of the icons at the top right of the screen, the symbol for the connection isn't monochrome. * Build Yaru from Master and notice how all icons are now monochrome. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the GitHub PR: https://github.com/ubuntu/yaru/pull/2252. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted
see previous post... ** Attachment added: "second crash file w/o debug symbols" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+attachment/5393318/+files/_opt_Franz_franz.1000.crash ** Changed in: nautilus (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887263 Title: nautilus freezes possibly in connection w/ samba share mounted/unmounted Status in nautilus package in Ubuntu: In Progress Bug description: test steps: - mouunt samba share w/: smb://host/share - open local disc w/ personal folder - scroll directory e. g. w/ show hidden files enabled in order to get a long list expected result: directory scrolls up and down actual result: scrolling freezes for some seconds before scrolling completes: - no directory selection appears until after freeze is over - only selection possible is the mounted samba share, which returns to the top level directory of the share leder@home-ryzen-desktop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 leder@home-ryzen-desktop:~$ apt-cache policy nautilus nautilus: Installiert: 1:3.36.3-0ubuntu1 Installationskandidat: 1:3.36.3-0ubuntu1 Versionstabelle: *** 1:3.36.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 Uname: Linux 5.6.19-050619-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 04:32:18 2020 InstallationDate: Installed on 2020-06-22 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887263] Re: nautilus freezes possibly in connection w/ samba share mounted/unmounted
Thank you, Sebastien. I am uncertain of what to do: - nautilus does not crash, but freeze for some seconds - I have two crashes for packages, that do not have a "-dbg" package available - I attach the two crash files All the best Gerrit ** Attachment added: "crash file w/o debug symbols" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+attachment/5393317/+files/_usr_libexec_gnome-shell-hotplug-sniffer.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887263 Title: nautilus freezes possibly in connection w/ samba share mounted/unmounted Status in nautilus package in Ubuntu: In Progress Bug description: test steps: - mouunt samba share w/: smb://host/share - open local disc w/ personal folder - scroll directory e. g. w/ show hidden files enabled in order to get a long list expected result: directory scrolls up and down actual result: scrolling freezes for some seconds before scrolling completes: - no directory selection appears until after freeze is over - only selection possible is the mounted samba share, which returns to the top level directory of the share leder@home-ryzen-desktop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 leder@home-ryzen-desktop:~$ apt-cache policy nautilus nautilus: Installiert: 1:3.36.3-0ubuntu1 Installationskandidat: 1:3.36.3-0ubuntu1 Versionstabelle: *** 1:3.36.3-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 Uname: Linux 5.6.19-050619-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 04:32:18 2020 InstallationDate: Installed on 2020-06-22 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869522] Re: Simple Scan doesn't work
[Expired for simple-scan (Ubuntu) because there has been no activity for 60 days.] ** Changed in: simple-scan (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1869522 Title: Simple Scan doesn't work Status in simple-scan package in Ubuntu: Expired Bug description: The latest version of Simple Scan released for Ubuntu 18.04 LTS does not work. Version 3.28.0-0ubuntu1 is installed. When I click to launch it nothing happens. I initially reported the bug against Simple Scan, but they said it was a problem with the Ubuntu 18.04 LTS distribution. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.14 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 28 15:29:05 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2014-08-08 (2059 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2020-01-05 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
Moved to Private so only the original reporter (JPM) can reply. ** Information type changed from Private to Public -- 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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6 sendmsg 0.010.27 3 9 mmap 0.000.02
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
dantheperson, the problem you describe is bug 1880405. ** Information type changed from Public to Private -- 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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6 sendmsg 0.010.27 3 9 mmap 0.000.02
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
Dan, Please report your own bug. This one was due to expire in 10 days. ** Information type changed from Public to Private -- 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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6 sendmsg 0.010.27 3 9 mmap 0.00
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
** Attachment added: "Screenshot from 2020-07-17 15-33-50.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393306/+files/Screenshot%20from%202020-07-17%2015-33-50.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
lspci ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393305/+files/lspcik.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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930 ioctl 0.400.001092 3 318 write 0.140.000386 664 close 0.130.000344 0 469 getpid 0.110.000295 464 timerfd_create 0.110.000292 1 222 mprotect 0.060.000177 264 timerfd_settime 0.060.000153 625 munmap 0.040.000121 1 121 read 0.010.38 049 4 futex 0.010.18 6 3 sendmsg 0.000.13 13 1 restart_syscall 0.000.00 0 7 mmap 0.000.00 0 2 getrusage -- --- --- - - 100.000.274406 76211 15904 total After closing the terminal windows too, therefore only the terminal running strace is open: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.430.196569 3 54115 27576 recvmsg 35.250.190224 3 53266 poll 26.920.145275 5 26592 writev 0.300.001631 4 405 write 0.230.001245 5 248 mprotect 0.230.001229 9 136 close 0.210.001120 1 621 ioctl 0.160.000889 6 136 timerfd_create 0.130.000711 5 136 timerfd_settime 0.060.000328 1 300 getpid 0.030.000180 268 3 futex 0.030.000159 185 read 0.010.53 8 6 sendmsg 0.010.27 3 9
[Desktop-packages] [Bug 1880723] Re: gnome-shell high CPU usage on Ubuntu 20.04
I'm seeing something very similar. Did a fresh install of 20.04 a week ago. After being logged in half a day things really start slowing down. Alt+Tab takes a few seconds to pop up, then you tab through to e.g. an open Calculator instance and that takes 8 seconds to come to the foreground. gnone-shell using 50% of one CPU. Have tried your suggestions to no avail. attaching the logs requested. journalctl shows a tone of javascript errors e.g. JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 $ sudo strace -c -p 7087 strace: Process 7087 attached ^Cstrace: Process 7087 detached % time seconds usecs/call callserrors syscall -- --- --- - - 34.730.215539 2 98592 sendmsg 23.990.148891 2 70929 36904 recvmsg 22.680.140739 2 68317 poll 16.420.101903 2 34030 writev 1.210.007527 4 1716 ioctl 0.460.002841 3 932 138 futex 0.250.001521 5 300 260 stat 0.100.000590 0 656 mprotect 0.060.000362 0 1165 write 0.040.000278 554 munmap 0.030.000205 0 305 getpid 0.010.89 0 383 read 0.000.22 113 timerfd_create 0.000.17 113 close 0.000.17 110 mmap 0.000.17 113 timerfd_settime 0.000.02 2 1 restart_syscall 0.000.00 0 2 getrusage -- --- --- - - 100.000.620560277431 37302 total Your journalctl command produced a 1.5Gb file. I have attached the last 100K lines. Let me know if you need more. ** Attachment added: "journal-tail.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880723/+attachment/5393304/+files/journal-tail.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/1880723 Title: gnome-shell high CPU usage on Ubuntu 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: After having a couple of terminals and and Chrome windows open for most of the day, everything becomes sluggish. Switching desktops is clearly very slow and Chrome's windows don't react to all mouse actions. Looking at htop I can see gnome-shell takes anywhere between 5% and 50% of CPU, normally between 10% and 20%. With Chrome and terminal windows open, an strace on the PID of gnome- shell shows the following: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 [sudo] password for jpmeijers: strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.370.108651 3 30932 16434 recvmsg 34.990.104531 3 29278 poll 26.200.078272 5 14601 writev 1.060.003158 2 1181 ioctl 0.350.001041 2 430 write 0.270.000812 1 602 getpid 0.260.000773 4 158 read 0.110.000316 396 timerfd_create 0.100.000313 396 close 0.100.000300 473 4 futex 0.080.000241 296 timerfd_settime 0.070.000201 0 228 mprotect 0.040.000111 27 4 getrusage 0.010.38 12 3 sendmsg 0.000.08 011 munmap 0.000.05 0 6 mmap 0.000.02 1 2 1 recvfrom -- --- --- - - 100.000.298773 77797 16439 total After closing Chrome windows: jpmeijers@jpmeijers-XPS13-9333:~$ sudo strace -c -p 3491 strace: Process 3491 attached ^Cstrace: Process 3491 detached % time seconds usecs/call callserrors syscall -- --- --- - - 36.240.099458 3 30319 15900 recvmsg 35.150.096450 3 29053 poll 26.860.073711 5 14500 writev 0.680.001858 1 930
[Desktop-packages] [Bug 1883920] Re: ubuntu logo in wslfetch needs update
Tested 2.3.6-0ubuntu2~20.04.0. As the screenshot shown, the logo is now the correct version instead of the old logo. ** Attachment added: "Annotation 2020-07-17 101900.png" https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+attachment/5393301/+files/Annotation%202020-07-17%20101900.png ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * This patch just update the logo of wslfetch to the proper current Ubuntu logo. Potential regressions would be a result of the patch having typo that caused error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
Tested 2.3.6-0ubuntu2~20.04.0 on focal. As the screenshot is shown, the error is now gone if Windows Path is not included in the PATH. ** Attachment added: "Annotation 2020-07-17 101900.png" https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1877016/+attachment/5393300/+files/Annotation%202020-07-17%20101900.png ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
Tested 2.3.6-0ubuntu2~20.04.0 on focal. As the screenshot is shown, the error is now gone if Windows Path is not included in the PATH. ** Attachment added: "Annotation 2020-07-17 101900.png" https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1877016/+attachment/5393299/+files/Annotation%202020-07-17%20101900.png -- 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/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++ o++o ydddhh+ .++.o+ +oo+:` /dddhhh; .+.o+oo:. odd+ \+.++o+o` -.:ohdh+ `:o+++ oyo++os: .o: .syhhh'.oo++o. /osyyy.+++\ ` +oo+++o:/ `oo++'` After : echo $PATH /snap/bin:/snap/sbin:/mnt/c/windows/system32/:/home/rafaeldtinoco/work/sources/upstream/ubuntu-dev-tools/:/usr/lib/ccache:/sbin:/bin:/usr/sbin:/usr/bin:/home/rafaeldtinoco/work/sources/bzr/ubuntu-archive-tools:/home/rafaeldtinoco/work/sources/upstream/lxd/bin:. $ wslfetch ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD:18363 .++ .:/++/-.`sss/` BRANCH: 19h1_release .:++o: `\/:---:/-RELEASE: Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 19m
[Desktop-packages] [Bug 1887871] Re: Graphics bug
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1887871 Title: Graphics bug Status in xorg-server package in Ubuntu: Won't Fix Bug description: Not sure about it's a bug, but I've been having problems with some programs, mostly games. It slows down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 16 20:48:28 2020 DistUpgraded: 2020-06-10 00:02:31,715 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0434] InstallationDate: Installed on 2011-08-18 (3255 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1464 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=68c2f41b-3cd6-45e1-b3ad-8329a3b67db8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2020-06-10 (36 days ago) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0C6HFD dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1464:pvrA13:rvnDellInc.:rn0C6HFD:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1464 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jul 16 19:48:13 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4156 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1887871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887843] Re: Dismissing notifications in the notification window changes position of do-not-disturb button
Hmm, downward or upward this sounds like https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2250 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2250 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2250 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2250 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1887843 Title: Dismissing notifications in the notification window changes position of do-not-disturb button Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: When new notifications appear in the notification window of Ubuntu 20.04 it is possible to dismiss them by clicking the 'clear all' button or by dismissing individual notifications. When messages are dismissed, it results in a (downward) change in position of the 'do not disturb' toggle button. The expected behavior would be that the position of the button is not affected by addition/removal of notifications. Reporting in gnome shell, but it is also possible this is a theme styling issue. 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: Thu Jul 16 14:06:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-06 (10 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/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/1887843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887829] Re: graphic card not working
Please switch back to the Nvidia driver, reproduce the freeze again, reboot and then immediately run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Tags added: nvidia ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- 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/1887829 Title: graphic card not working Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-390/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887821] Re: gnome-shell GUI freezes totally
Also... 4. Run this command: lspci -k > lspcik.txt and attach the resulting text file here. 5. If the problem is just the machine running out of memory then please track that using the 'free -h' and 'ps auwx' commands and find out which process is using the most memory. ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1887821 Title: gnome-shell GUI freezes totally Status in Ubuntu: Incomplete Bug description: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog after that, and ping worked into this frozen machine. So the whole OS didn't crash. Only GUI related. I hope this helps. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy firefox firefox: Installed: 78.0.2+build2-0ubuntu0.20.04.1 Candidate: 78.0.2+build2-0ubuntu0.20.04.1 Version table: *** 78.0.2+build2-0ubuntu0.20.04.1 500 500 http://fi.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 75.0+build3-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages I'm sure this is a bug. The same effect has happened 3 times in 30 days. I didn't check the previous syslog which error message there was. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887821] Re: gnome-shell GUI freezes totally
Please: 1. Run this command to send us more info about the machine: apport-collect 1887821 2. Next time the problem happens and you have to reboot, please then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. 3. Check for crashes by following *all* of these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1887821 Title: gnome-shell GUI freezes totally Status in Ubuntu: Incomplete Bug description: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog after that, and ping worked into this frozen machine. So the whole OS didn't crash. Only GUI related. I hope this helps. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy firefox firefox: Installed: 78.0.2+build2-0ubuntu0.20.04.1 Candidate: 78.0.2+build2-0ubuntu0.20.04.1 Version table: *** 78.0.2+build2-0ubuntu0.20.04.1 500 500 http://fi.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 75.0+build3-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages I'm sure this is a bug. The same effect has happened 3 times in 30 days. I didn't check the previous syslog which error message there was. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887728] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Disk encryption should have no influence on display corruption. Most likely something else about the machine changed around the same time you enabled encryption. ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
If you have an Intel GPU then you should not be subscribed to this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX 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.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887816] Re: Right click "open with" opens directly without asking for a program
** Description changed: I copied .txt files to my desktop folder (from NTFS external disk) and tried to open them but they were with right 777 (rwxrwxrwx) so press Enter (etc.) try to execute and not open the file with an editing program. Then I rote a bug report (#1887514), understood my problem and changed the rights of the files. But there is still a problem. When I was trying to identify the problem, I tried "open with" on the right click menu. It worked (a window is opened and ask witch program I - want to use). And after reporting the "bug" (that wasn't a bug) the + want to use). And after reporting bug 1887514 (that wasn't a bug) the option "open with" didn't opened anymore the window to choose a program. It opens directly as if I've selected "open". It do the same to every new files I add to the desktop, and I already have rebooted my computer (it was some days ago). - - I am not sure if the package I've selected is the right one for this problem, I don't know a lot about how Ubuntu is structured (and I don't know where I can find precise information). + I am not sure if the package I've selected is the right one for this + problem, I don't know a lot about how Ubuntu is structured (and I don't + know where I can find precise information). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-2~ubuntu20.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: Thu Jul 16 16:20:32 2020 InstallationDate: Installed on 2020-07-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1887816 Title: Right click "open with" opens directly without asking for a program Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I copied .txt files to my desktop folder (from NTFS external disk) and tried to open them but they were with right 777 (rwxrwxrwx) so press Enter (etc.) try to execute and not open the file with an editing program. Then I rote a bug report (#1887514), understood my problem and changed the rights of the files. But there is still a problem. When I was trying to identify the problem, I tried "open with" on the right click menu. It worked (a window is opened and ask witch program I want to use). And after reporting bug 1887514 (that wasn't a bug) the option "open with" didn't opened anymore the window to choose a program. It opens directly as if I've selected "open". It do the same to every new files I add to the desktop, and I already have rebooted my computer (it was some days ago). I am not sure if the package I've selected is the right one for this problem, I don't know a lot about how Ubuntu is structured (and I don't know where I can find precise information). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-2~ubuntu20.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: Thu Jul 16 16:20:32 2020 InstallationDate: Installed on 2020-07-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1887816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887411] Re: system-users-symbolic icon has unclear visual metaphor
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887411 Title: system-users-symbolic icon has unclear visual metaphor Status in yaru-theme package in Ubuntu: New Status in yaru-theme source package in Focal: New Bug description: [Impact] * The system-users-symbolic icon doesn't represent users in the plural. It shows a single generic figure (head and shoulders) representing one user. This is a misleading visual metaphor, since a single head and shoulders is universally recognised as the current or logged-in user. * Reason to backport to Focal: the corresponding Adwaita icon shows two users. Third party apps that use the icon will expect it to represent more than one person. Failing to provide a suitable icon will have confusing results in Ubuntu. [Test Case] * Install Lollypop and look at the sidebar. "Compilations" has the symbol of a single user, which is confusing. Lollypop requested an icon with multiple figures to represent multiple artists, but Ubuntu supplied something inappropriate. This issue may be duplicated whenever a third party app uses this icon. * Build Yaru from Master and notice how the icon now has the same visual metaphor as Adwaita (i.e., it shows two users). The Lollypop UI makes more sense and the theme honours the app's intentions. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the Github PR: https://github.com/ubuntu/yaru/pull/2209 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887419] Re: Lollypop music player mixes Yaru and Adwaita symbols
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887419 Title: Lollypop music player mixes Yaru and Adwaita symbols Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Triaged Status in yaru-theme source package in Focal: Triaged Bug description: [Impact] * The Yaru theme has some of the icons used by Lollypop but not all of them. This results in the Lollypop sidebar having a mix of Adwaita symbols (with 2px strokes) and Yaru ones (which have 1px). See GitHub issue https://github.com/ubuntu/yaru/issues/2208. * Reason to backport to Focal: displaying symbols from two different themes gives a poor impression of Ubuntu to users who want to use a popular native music player. [Test Case] * Install Lollypop and look at the sidebar. Some of the symbols are heavy and some are light. (Alternatively, the GitHub issue linked above has a screenshot.) * Build Yaru from Master and notice how the Lollypop sidebar is now consistent with itself and the rest of the Yaru theme. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Links to the GitHub PRs: https://github.com/ubuntu/yaru/pull/2235 and https://github.com/ubuntu/yaru/pull/2253. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887393] Re: The system-lock-screen icon has a twisted/deformed path
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887393 Title: The system-lock-screen icon has a twisted/deformed path Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * The lock icon in gnome-control-center privacy page has a twisted path in it's key-hole * Backporting this to focal, would greatly increase the level of visual polish and increase the professional look of the ubuntu desktop and the yaru icon theme * The fix is already in the yaru master branch: https://github.com/ubuntu/yaru/issues/2201 [Test Case] * Open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see the twisted path of the key whole * Build yaru from master, open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see that the path of the key-hole is now an even square [Regression Potential] * No regression potential, tested by building the branch in the pull request [Other Info] * Link to the github issue: https://github.com/ubuntu/yaru/issues/2201 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887388] Re: Several mimetype icons are missing
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887388 Title: Several mimetype icons are missing Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Many mimetype icons are not showing up in yaru, even if they have been included in the yaru theme suite and some mimetype icons are were not included previously * Backporting them to focal would greatly increase the differentiation of the file types that are existent for the average user * All those fixes are already in yaru master: - img and iso https://github.com/ubuntu/yaru/pull/2213 - Lilypond https://github.com/ubuntu/yaru/pull/2230 - QML https://github.com/ubuntu/yaru/pull/2226 - log files https://github.com/ubuntu/yaru/pull/2229 - arduino, jpynbgjson, mswinurl, cursor https://github.com/ubuntu/yaru/pull/2234 - scala https://github.com/ubuntu/yaru/pull/2231 - lmms https://github.com/ubuntu/yaru/pull/2249 - theme files https://github.com/ubuntu/yaru/pull/2243 - rss https://github.com/ubuntu/yaru/pull/2248 - executable https://github.com/ubuntu/yaru/pull/2204 - apple images https://github.com/ubuntu/yaru/pull/2233 [Test Case] * open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have either a generic text file as their mimetype icon or the wrong mimetype icon * install yaru master branch and open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have the correct mimetype icons which make it very clear what is inside those files [Regression Potential] * No regression potential, tested by building all pull requests [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887298] Re: blue GtkSpinner is hard to see on red .destrucive-action buttons
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887298 Title: blue GtkSpinner is hard to see on red .destrucive-action buttons Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Blue blue GtkSpinner is hard to see on red .destrucive-action buttons, like the "Stop scanning" button in simple-scan, Link to the yaru github issue: https://github.com/ubuntu/yaru/issues/2182 * Reason to backport this to focal: users have it very hard to see the spinner, especially color blind people, backporting this will greatly improve the accessibility and legibility of the yaru theme and the ubuntu desktop for focal users [Test Case] * Press the green "Scan" button in simple-scan and it will turn red with a "Stop" label and a blue spinner inside the button. The spinner is hard to see on this red background * Build yaru from master and notice how the white spinner is much more visible against a red background [Regression Potential] * No regression potential * Tested by building yaru from source [Other Info] * Link to the github pull request: https://github.com/ubuntu/yaru/pull/2187 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887420] Re: network-cellular-connected-symbolic isn't monochrome
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887420 Title: network-cellular-connected-symbolic isn't monochrome Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Triaged Status in yaru-theme source package in Focal: Triaged Bug description: [Impact] * The icon called network-cellular-connected-symbolic appears at the top right of the desktop when users connect to their phones via bluetooth to use data. The icon includes green fill, which is inconsistent with the monochrome icons used for (e.g.) wifi. See GitHub issue https://github.com/ubuntu/yaru/issues/2192. * Reason to backport to Focal: the inconsistency was missed because I don't use this feature and it's an unfortunate oversight. When the icon appears, it does so in a prominent position and is constantly visible to the user, giving a poor impression of Ubuntu. [Test Case] * Use Bluetooth tethering so your laptop is making use of your phone's data connection. Notice that, unlike the rest of the icons at the top right of the screen, the symbol for the connection isn't monochrome. * Build Yaru from Master and notice how all icons are now monochrome. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the GitHub PR: https://github.com/ubuntu/yaru/pull/2252. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887389] Re: Microphone icon outlines can look fuzzy on certain screens
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887389 Title: Microphone icon outlines can look fuzzy on certain screens Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * The microphone icon only consists of small outlines which are very close to each other, making the icon look fuzzy and hard to understand, especially on screens with high sharpness * Backporting this to focal would greatly improve the visibility and legibility of the microphone icon and thus help to improve the overall look of the ubuntu desktop in focal * The fix is already in ubuntu master: https://github.com/ubuntu/yaru/pull/2200 [Test Case] * If your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display until the icon becomes fuzzy and hard to understand * Build yaru from master and if your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display and watch how the icon stays sharp and "intact" even with high sharpness [Regression Potential] * No regression potential, tested by building the branch of the pull request [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887300] Re: Wacom overlay text labels are invisible
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887300 Title: Wacom overlay text labels are invisible Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: https://github.com/ubuntu/yaru/issues/2099 [Impact] * The wacom overlay text is invisible and users can not use this gnome-shell dialog to map their wacom tablet hardware buttons * Backporting this to the stable release focal will let wacom users use this dialogue again, which is very important because you have no other way to map it in ubuntu * The fix is already in yaru master https://github.com/ubuntu/yaru/pull/2198 [Test Case] * Plug a wacom tablet to your computer, search for "wacom" in the gnome shell search and press enter to open the corresponding gnome- control-center page. Now open the dialog to map your buttons. See how the labels for each button are invisible * Build yaru from master and repeat these steps and see how the labels appear and you can properly map the correct button [Regression Potential] * No regression potential * Built and tested with the yaru master branch [Other Info] * Yaru issue: https://github.com/ubuntu/yaru/issues/2099 * yaru fix: https://github.com/ubuntu/yaru/pull/2198 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887871] [NEW] Graphics bug
Public bug reported: Not sure about it's a bug, but I've been having problems with some programs, mostly games. It slows down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 16 20:48:28 2020 DistUpgraded: 2020-06-10 00:02:31,715 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0434] InstallationDate: Installed on 2011-08-18 (3255 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0c45:641d Microdia 1.3 MPixel Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 1464 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=68c2f41b-3cd6-45e1-b3ad-8329a3b67db8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2020-06-10 (36 days ago) dmi.bios.date: 03/29/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0C6HFD dmi.board.vendor: Dell Inc. dmi.board.version: A13 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd03/29/2011:svnDellInc.:pnInspiron1464:pvrA13:rvnDellInc.:rn0C6HFD:rvrA13:cvnDellInc.:ct8:cvrA13: dmi.product.name: Inspiron 1464 dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jul 16 19:48:13 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4156 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.11 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1887871 Title: Graphics bug Status in xorg package in Ubuntu: New Bug description: Not sure about it's a bug, but I've been having problems with some programs, mostly games. It slows down. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 16 20:48:28 2020 DistUpgraded: 2020-06-10 00:02:31,715 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0434] InstallationDate: Installed on 2011-08-18 (3255 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003:
[Desktop-packages] [Bug 1887297] Re: gnome-shell notifications and gtk3 menus are hard to distinguish from the background
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu Focal) Importance: Undecided => Low ** Changed in: yaru-theme (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887297 Title: gnome-shell notifications and gtk3 menus are hard to distinguish from the background Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: [Impact] * Gtk and shell menus, popups and notifications are often hard to distinguish against the elements that are beneath them (Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217) * backporting this QOL change to focal would greatly improve the legibility of the yaru theme(s) * the fixes for this are already in the master branch of https://github.com/ubuntu/yaru [Test Case] * populate gtk3 menus against a nautilus window and spawn a notification by either adding or removing a favourite app in the dock with rightclick add/remove favourite. Gtk3 menus almost look like they are part of the window and not a different part of the desktop. Notifications, especially when using yaru-light are also hard to see and recognize [Regression Potential] * No regression potential * Tested by building the fixed branch(es) of yaru and then switching back and forth the gtk3 and shell themes, please see the corresponding github pull requests https://github.com/ubuntu/yaru/pull/2232 + https://github.com/ubuntu/yaru/pull/2236 [Other Info] * Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887383] Re: Yaru updates not related to themes and icons
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: yaru-theme (Ubuntu Focal) ** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887383 Title: Yaru updates not related to themes and icons Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: New Bug description: [Impact] * Several parts of the build, including the yaru README and github actions to stay synced with upstream, are out of date and need updates. Those changes are: - fix Yaru project name + update README pictures - build: deduplicate meson.build and introduce Flavours https://github.com/ubuntu/yaru/pull/1884 - add libgtk-3-dev to the bootstrap script https://github.com/ubuntu/yaru/pull/ - updates to the upstream directories, which include the source code of the unmodified upstream gnome-shell and gtk3 themes https://github.com/ubuntu/yaru/pull/2084 - Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py to avoid errors while building https://github.com/ubuntu/yaru/pull/2206 - Check for updates to GitHub Actions every weekday https://github.com/ubuntu/yaru/pull/2223 - Adding new non-uniform app icon templates https://github.com/ubuntu/yaru/pull/1920 * Backporting these updates to focal, will greatly improve the build process of the yaru project and help to avoid bugs and help the development of the team * all fixes are in yaru master since several weeks and have been tested several times [Test Case] * Look at the yaru project page while in this branch https://github.com/ubuntu/yaru/tree/ubuntu/focal and find the images to be removed * Look at the yaru project page while in the master branch https://github.com/ubuntu/yaru/tree/master and find all images to show what currently is in focal * All other test cases are described in the corresponding pull requests [Regression Potential] * Outdated versions of meson may clash with the current yaru build, otherwise, no regression potential [Other Info] * Those changes are not "visible" for the end-user while using the ubuntu desktop, i.e. no theme changes, no icon changes here, but they greatly improve the daily work of the yaru team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887383] Re: Yaru updates not related to themes and icons
** No longer affects: yaru-theme (Ubuntu Focal) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887383 Title: Yaru updates not related to themes and icons Status in yaru-theme package in Ubuntu: In Progress Bug description: [Impact] * Several parts of the build, including the yaru README and github actions to stay synced with upstream, are out of date and need updates. Those changes are: - fix Yaru project name + update README pictures - build: deduplicate meson.build and introduce Flavours https://github.com/ubuntu/yaru/pull/1884 - add libgtk-3-dev to the bootstrap script https://github.com/ubuntu/yaru/pull/ - updates to the upstream directories, which include the source code of the unmodified upstream gnome-shell and gtk3 themes https://github.com/ubuntu/yaru/pull/2084 - Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py to avoid errors while building https://github.com/ubuntu/yaru/pull/2206 - Check for updates to GitHub Actions every weekday https://github.com/ubuntu/yaru/pull/2223 - Adding new non-uniform app icon templates https://github.com/ubuntu/yaru/pull/1920 * Backporting these updates to focal, will greatly improve the build process of the yaru project and help to avoid bugs and help the development of the team * all fixes are in yaru master since several weeks and have been tested several times [Test Case] * Look at the yaru project page while in this branch https://github.com/ubuntu/yaru/tree/ubuntu/focal and find the images to be removed * Look at the yaru project page while in the master branch https://github.com/ubuntu/yaru/tree/master and find all images to show what currently is in focal * All other test cases are described in the corresponding pull requests [Regression Potential] * Outdated versions of meson may clash with the current yaru build, otherwise, no regression potential [Other Info] * Those changes are not "visible" for the end-user while using the ubuntu desktop, i.e. no theme changes, no icon changes here, but they greatly improve the daily work of the yaru team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870260] Re: initramfs unpacking failed: Decoding failed", message appears on boot up.
*** This bug is a duplicate of bug 1835660 *** https://bugs.launchpad.net/bugs/1835660 ** This bug has been marked a duplicate of bug 1835660 initramfs unpacking failed -- 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/1870260 Title: initramfs unpacking failed: Decoding failed", message appears on boot up. Status in linux package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: OS : Ubuntu 20.04(20200401) Problem: "initramfs unpacking failed: Decoding failed", message appears on boot up solution: If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing . Expected solution: This but in there from a long time I have seen this from Ubuntu 18.04,19.04,19.10 now in 20.04 So please fix it or change it from lz4 to gzip. an early reply is highly appreciated Thank you . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tamal 1451 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx Package: ubuntu-meta ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=29f895bf-ab7b-4df8-8e9a-c277376a2685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 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.23:bd11/29/2019:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY34PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Fix Released
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1072187
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.195989:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.197368:ERROR:CONSOLE(70)] "Uncaught TypeError:
Cannot read property 'setInspectedTabId' of undefined", source:
devtools://devtools/bundled/devtools_compatibility.js (70)
**
[Desktop-packages] [Bug 1887478] Re: missing symlinks for login and logout files used by gnome
As mentioned in the bug description, I've filed a MR upstream to fix the issue and this is a downstream bug for tracking. To test the issue, install the freedesktop sound theme and enable it as the default sound theme, and install the gnome-session-canberra to get the startup and shutdown execution. I'm running xubuntu 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1887478 Title: missing symlinks for login and logout files used by gnome Status in sound-theme-freedesktop package in Ubuntu: Incomplete Bug description: Merge request submitted upstream in Debian to fix the issue. https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886323]
Created attachment 9163882 TB Printer Options.png Hi, so as you ask me I will share some "insights". First, I use Ubuntu 20.04 with the nice Unity desktop environment. Others may show different. Almost all views in the TB printer dialogue are perfectly localized to German with one exception, the advanced tab shows the options in English, and only for 2 of the 3 HP printer drivers I have installed, see screen shot. Also a different count of options is shown for the 3 drivers, and for the HP PS driver there is an additional tab "Printer quality". As far as I guess, the translations and options come from the /etc/cups/ppd*.ppd files, shipped by the driver. for example, the file for the HP PS driver has 137 kb whereas the 2 others have only 14 kb. The first contains several translations, whereas the 2 smaller have only English items. Don't know from where the translated items in the TB dialogue come from. The print dialogue for TB and the PDF viewer are the same, so they seem to come from the OS, but the printer dialogue for LibreOffice looks very different. Hope that helps! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1886323 Title: Print dialog is only partially localized in KDE Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Confirmed Bug description: I changed the langueage of my thunderbird client from English to German. Most parts of Thunderbird are now in German, but the pring dialog settings is still in English. I use Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.8.0+build2-0ubuntu0.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.3 Architecture: amd64 BuildID: 20200504155042 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 14:52:31 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-05-17 (49 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.8.0/20200504155042 (In use) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1886323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887829] Re: graphic card not working
** Package changed: ubuntu => xorg (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/1887829 Title: graphic card not working Status in xorg package in Ubuntu: New Bug description: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887829] [NEW] graphic card not working
You have been subscribed to a public bug: graphic card not working properly so I have to switch to custom graphic driver |If i use nvidia driver the system freezes after few minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 16 22:06:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8322] InstallationDate: Installed on 2020-07-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=2f89e325-7cba-46e0-8714-d8d6cbab9ff2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH55TC dmi.board.vendor: Intel Corporation dmi.board.version: AAE70932-206 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55TC:rvrAAE70932-206:cvn:ct3:cvr: 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 -- graphic card not working https://bugs.launchpad.net/bugs/1887829 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887821] Re: gnome-shell GUI freezes totally
System: - Gigabyte X570 Aorus Ultra Gigabyte Technology Co., Ltd. X570 AORUS ULTRA/X570 AORUS ULTRA, BIOS F3 06/13/2019 - AMD Ryzen 5 3600 - 64GB ram - gfx: GTX 680 NVIDIA-SMI 440.95.01Driver Version: 440.95.01CUDA Version: 10.2 -- 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/1887821 Title: gnome-shell GUI freezes totally Status in gnome-shell package in Ubuntu: New Bug description: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog after that, and ping worked into this frozen machine. So the whole OS didn't crash. Only GUI related. I hope this helps. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy firefox firefox: Installed: 78.0.2+build2-0ubuntu0.20.04.1 Candidate: 78.0.2+build2-0ubuntu0.20.04.1 Version table: *** 78.0.2+build2-0ubuntu0.20.04.1 500 500 http://fi.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 75.0+build3-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages I'm sure this is a bug. The same effect has happened 3 times in 30 days. I didn't check the previous syslog which error message there was. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887821] Re: gnome-shell GUI freezes totally
** Package changed: pulseaudio (Ubuntu) => gnome-shell (Ubuntu) -- 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/1887821 Title: gnome-shell GUI freezes totally Status in gnome-shell package in Ubuntu: New Bug description: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog after that, and ping worked into this frozen machine. So the whole OS didn't crash. Only GUI related. I hope this helps. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy firefox firefox: Installed: 78.0.2+build2-0ubuntu0.20.04.1 Candidate: 78.0.2+build2-0ubuntu0.20.04.1 Version table: *** 78.0.2+build2-0ubuntu0.20.04.1 500 500 http://fi.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 75.0+build3-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages I'm sure this is a bug. The same effect has happened 3 times in 30 days. I didn't check the previous syslog which error message there was. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887821/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887843] [NEW] Dismissing notifications in the notification window changes position of do-not-disturb button
Public bug reported: When new notifications appear in the notification window of Ubuntu 20.04 it is possible to dismiss them by clicking the 'clear all' button or by dismissing individual notifications. When messages are dismissed, it results in a (downward) change in position of the 'do not disturb' toggle button. The expected behavior would be that the position of the button is not affected by addition/removal of notifications. Reporting in gnome shell, but it is also possible this is a theme styling issue. 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: Thu Jul 16 14:06:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-06 (10 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/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1887843 Title: Dismissing notifications in the notification window changes position of do-not-disturb button Status in gnome-shell package in Ubuntu: New Bug description: When new notifications appear in the notification window of Ubuntu 20.04 it is possible to dismiss them by clicking the 'clear all' button or by dismissing individual notifications. When messages are dismissed, it results in a (downward) change in position of the 'do not disturb' toggle button. The expected behavior would be that the position of the button is not affected by addition/removal of notifications. Reporting in gnome shell, but it is also possible this is a theme styling issue. 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: Thu Jul 16 14:06:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-06 (10 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/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/1887843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887383] Re: Yaru updates not related to themes and icons
** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: yaru-theme (Ubuntu Focal) ** Also affects: yaru-theme (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887383 Title: Yaru updates not related to themes and icons Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: New Bug description: [Impact] * Several parts of the build, including the yaru README and github actions to stay synced with upstream, are out of date and need updates. Those changes are: - fix Yaru project name + update README pictures - build: deduplicate meson.build and introduce Flavours https://github.com/ubuntu/yaru/pull/1884 - add libgtk-3-dev to the bootstrap script https://github.com/ubuntu/yaru/pull/ - updates to the upstream directories, which include the source code of the unmodified upstream gnome-shell and gtk3 themes https://github.com/ubuntu/yaru/pull/2084 - Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py to avoid errors while building https://github.com/ubuntu/yaru/pull/2206 - Check for updates to GitHub Actions every weekday https://github.com/ubuntu/yaru/pull/2223 - Adding new non-uniform app icon templates https://github.com/ubuntu/yaru/pull/1920 * Backporting these updates to focal, will greatly improve the build process of the yaru project and help to avoid bugs and help the development of the team * all fixes are in yaru master since several weeks and have been tested several times [Test Case] * Look at the yaru project page while in this branch https://github.com/ubuntu/yaru/tree/ubuntu/focal and find the images to be removed * Look at the yaru project page while in the master branch https://github.com/ubuntu/yaru/tree/master and find all images to show what currently is in focal * All other test cases are described in the corresponding pull requests [Regression Potential] * Outdated versions of meson may clash with the current yaru build, otherwise, no regression potential [Other Info] * Those changes are not "visible" for the end-user while using the ubuntu desktop, i.e. no theme changes, no icon changes here, but they greatly improve the daily work of the yaru team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
Remark: this problems only ocurrs in encrypted Kubuntu (LVM). Without encryption it was OK. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883920] Re: ubuntu logo in wslfetch needs update
Hello Patrick, or anyone else affected, Accepted wslu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wslu/2.3.6-0ubuntu2~20.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wslu (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883920 Title: ubuntu logo in wslfetch needs update Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. The Ubuntu branding is the outdated version: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-1814.png [Test Case] * Install Ubuntu WSL and install this fix. * run wslfetch command. * new logo should be shown like the following: https://cdn.patrickwu.space/garage/screenshots/Annotation2020-06-18111946.png [Regression Potential] * This patch just update the logo of wslfetch to the proper current Ubuntu logo. Potential regressions would be a result of the patch having typo that caused error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877016] Re: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable
Hello Rafael, or anyone else affected, Accepted wslu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wslu/2.3.6-0ubuntu2~20.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wslu (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1877016 Title: ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: Confirmed Status in wslu source package in Bionic: Confirmed Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases. When PATH do not include Windows path, the all tools will complain that reg.exe is not found. [Test Case] * Add appendWindowsPath = false under [interop] section in /etc/wsl.conf file, and restart the distribution * run any wslu tool (like wslfetch) * "/mnt/c/Windows/System32/reg.exe: Permission denied" should not be shown [Regression Potential] * For future release of wslu 3.1.0 proposed, huge refactoring will be needed. [Original Bug Report] ubuntu-wsl / wslu : needs /mnt/c/windows/system32/ in PATH env variable $ wslfetch /usr/bin/wslfetch: line 108: reg.exe: command not found /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 108: reg.exe: command not found /usr/bin/wslsys: line 183: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 185: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 187: /mnt/c/Windows/System32/reg.exe: Permission denied /usr/bin/wslsys: line 189: /mnt/c/Windows/System32/reg.exe: Permission denied ./+o+- Windows 10 Linux Subsystem y. 'yy+ rafaeldtinoco@lenovo .;//+/h yyo BUILD: .++ .:/++/-.`sss/` BRANCH: .:++o: `\/:---:/-RELEASE:Ubuntu 20.04 LTS o:+o+:++. `'-/ooo+\ KERNEL: Linux 4.4.0-18362-Microsoft .:+o:+o/. `+sssooo+\ UPTIME: 0d 2h 6m .++/+ +oo+o:` \sssooo; /+++//+: oo+o \+/+o+++
[Desktop-packages] [Bug 1881524] Re: package libridl-java 1:6.4.2-0ubuntu3 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Invalid -- 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/1881524 Title: package libridl-java 1:6.4.2-0ubuntu3 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 Status in libreoffice package in Ubuntu: Invalid Bug description: it crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libridl-java 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jun 1 09:50:03 2020 Dependencies: ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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.2ubuntu0.1 SourcePackage: libreoffice Title: package libridl-java 1:6.4.2-0ubuntu3 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881524/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883924] Re: Ubuntu.exe will not be detected properly if other LTS version is installed
Hello Patrick, or anyone else affected, Accepted wslu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wslu/2.3.6-0ubuntu2~20.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wslu (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1883924 Title: Ubuntu.exe will not be detected properly if other LTS version is installed Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Xenial: New Status in wslu source package in Bionic: New Status in wslu source package in Focal: Fix Committed Status in wslu source package in Groovy: Fix Released Bug description: [Impact] This affects all wslu tools on all releases when using from the Ubuntu app from Microsoft Store. When other LTS version of app is installed from Microsoft Store, baseexec generated by wslu on Ubuntu app will not be using ubuntu.exe but other LTS release apps (such as ubuntu1804.exe) [Test Case] * Install Ubuntu and Ubuntu 18.04 LTS from Microsoft Store. * run any wslu tools (like wslfetch --help) * Verify that ~/.config/wslu/baseexec contains the path to ubuntu.exe [Regression Potential] This patch will try to regenerate ~/.config/wslu/baseexec when trying to execute any wslu commands (like wslfetch). Potential regressions would be a result of ~/.config/wslu/baseexec not regenerated properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1883924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791520] Re: package libxdmcp6 1:1.1.2-1.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: libxdmcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxdmcp in Ubuntu. https://bugs.launchpad.net/bugs/1791520 Title: package libxdmcp6 1:1.1.2-1.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in libxdmcp package in Ubuntu: Invalid Bug description: NA ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxdmcp6 1:1.1.2-1.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Sep 9 17:42:59 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 DistUpgraded: 2018-09-09 19:28:03,076 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-30-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] InstallationDate: Installed on 2017-12-13 (270 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80E5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libxdmcp Title: package libxdmcp6 1:1.1.2-1.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-09-09 (0 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: 31900059WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN40WW:bd06/20/2014:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Sep 9 20:23:28 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxdmcp/+bug/1791520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080564] Re: package libgtk-3-0 3.6.0-0ubuntu3 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1080564 Title: package libgtk-3-0 3.6.0-0ubuntu3 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2 Status in Ubuntu: Invalid Bug description: Adding this package as the result of adding another package on a newly free install of ubuntu 12.10 system. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libgtk-3-0 3.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sun Nov 18 21:56:31 2012 ErrorMessage: subprocess dpkg-deb --control returned error exit status 2 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gtk+3.0 Title: package libgtk-3-0 3.6.0-0ubuntu3 failed to install/upgrade: subprocess dpkg-deb --control returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1080564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Hello! When I log in, the sound does not appear. Then I have to close the application and try again until the sound appears. -- 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 : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Desktop-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
I installed kernel 5.7.9. The scramble screen did not change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1887728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881320] Re: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: libglvnd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1881320 Title: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in libglvnd package in Ubuntu: Invalid Bug description: got the issue while updating ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 29 21:46:42 2020 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.4.0-1ubuntu1~18.04 DuplicateSignature: package:libglvnd0:1.0.0-2ubuntu2 Unpacking libegl1:amd64 (1.0.0-2ubuntu2.3) over (1.0.0-2ubuntu2) ... dpkg-deb: error: '/tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-NFAxk9/66-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: libglvnd Title: package libglvnd0 1.0.0-2ubuntu2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1881320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libical3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libical3 in Ubuntu. https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Status in libical3 package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1806166] Re: package gettext 0.19.8.1-8 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! ** Changed in: gettext (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1806166 Title: package gettext 0.19.8.1-8 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 Status in gettext package in Ubuntu: Invalid Bug description: First auto update of the OS since installation an hour earlier. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: gettext 0.19.8.1-8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Fri Nov 30 21:32:50 2018 DuplicateSignature: package:gettext:0.19.8.1-8 Unpacking gedit (3.30.2-0ubuntu0.18.10.1) over (3.30.1-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-qK5YKy/41-gettext_0.19.8.1-8ubuntu0.1_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-qK5YKy/41-gettext_0.19.8.1-8ubuntu0.1_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 InstallationDate: Installed on 2018-12-01 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: gettext Title: package gettext 0.19.8.1-8 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1806166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> The chromium snap is strictly confined, and that means that it cannot read/write to hidden directories inside the user's home folder (such as $HOME/.config or $HOME/.cache). Change the folder it's confined to. > That one is stored in $HOME/chromium/common/.cache/ No, not really. The profile folder contains gigabytes of cache files. > The default profile directory is stored in $HOME/chromium/common/chromium/. No, not really. Copying it over resulted in a utterly broken profile, some vital files are not in the common folder. > Given all this, I'm not really sure what the bug really is about? Can you share concrete use cases? I'm not sure what's unclear, XDG base directory specification is NOT followed, my environment variables are ignored and the wrong folder is used for everything. That has multiple negative effects, as I listed. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification Status in chromium-browser package in Ubuntu: Confirmed Bug description: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887824] [NEW] License wrong in software list
Public bug reported: In the package page in the Ubuntu software center, this appears as proprietary, it should be GPLv3 Checked on version 1:13.0.1-1 on 20.04 ** Affects: gucharmap (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gucharmap in Ubuntu. https://bugs.launchpad.net/bugs/1887824 Title: License wrong in software list Status in gucharmap package in Ubuntu: New Bug description: In the package page in the Ubuntu software center, this appears as proprietary, it should be GPLv3 Checked on version 1:13.0.1-1 on 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gucharmap/+bug/1887824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849162] Re: Lightning extension should be installed and enabled by default
The upcoming update to thunderbird 78 will have the calendar features of lightning integrated, thus fixing this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1849162 Title: Lightning extension should be installed and enabled by default Status in thunderbird package in Ubuntu: Triaged Bug description: Upstream builds of thunderbird are now shipping lightning, and it is enabled by default. In contrast, lightning in Ubuntu is a separate binary package (xul- ext-lightning), and it’s neither installed by default nor even recommended by thunderbird. This results in confusion for users who don't know where to get lightning from. The extension should be bundled with the thunderbird package, i.e. installed and enabled by default (as was done for the wetransfer file link provider, see bug #1823361). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Possible dupe of lp: #1884981, with different error though. -- 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: New 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 1887804] Re: chromium-browser does not follow XDG base directory specification
The chromium snap is strictly confined, and that means that it cannot read/write to hidden directories inside the user's home folder (such as $HOME/.config or $HOME/.cache). That's a security feature to prevent snap applications from reading other applications' data. Instead, as you've found out, the app gets its own home directory located at $HOME/snap/chromium/current. The application itself does respect the XDG base directory specification, but with a rewritten $HOME. Now, you mention the cache data. That one is stored in $HOME/chromium/common/.cache/. The default profile directory is stored in $HOME/chromium/common/chromium/. The transitional package does copy over an existing profile from $HOME/.config/chromium if it exists the first time the snap is being run. Given all this, I'm not really sure what the bug really is about? Can you share concrete use cases? ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- 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/1887804 Title: chromium-browser does not follow XDG base directory specification Status in chromium-browser package in Ubuntu: Incomplete Bug description: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1677505] Re: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1659002 *** https://bugs.launchpad.net/bugs/1659002 invalid, you changed your /usr/bin/python symlink to point to python3 ** Changed in: pygobject (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 1659002 ImportError: No module named 'ConfigParser' when running pycompile -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1677505 Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in pygobject package in Ubuntu: Invalid Bug description: sudo apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: dh-translations dia-libs gfortran gfortran-5 gnome-control-center-data gnome-icon-theme gnome-icon-theme-symbolic gnome-settings-daemon iio-sensor-proxy intltool launchpad-getkeys libblas-dev libbz2-dev libcairo-script-interpreter2 libcolord-gtk1 libdbus-1-dev libegl1-mesa-dev libepoxy-dev libfontconfig1-dev libfreetype6-dev libgfortran-5-dev libgmp-dev libgmpxx4ldbl libharfbuzz-dev libharfbuzz-gobject0 libice-dev libjavascriptcoregtk-3.0-0 libjpeg-dev libjpeg-turbo8-dev libjpeg8-dev liblapack-dev liblzma-dev libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2 libncurses5-dev libpixman-1-dev libpng12-dev libprotobuf-dev libpython-all-dev libpython-dev libpython2.7-dev libreadline-dev libreadline6-dev libsm-dev libtinfo-dev libwayland-dev libwebkitgtk-3.0-0 libwebkitgtk-3.0-common libxcb-shm0-dev libxcomposite-dev libxcursor-dev libxft-dev libxi-dev libxinerama-dev libxkbcommon-dev libxrandr-dev libxrender-dev libxtst-dev nettle-dev planner-data planner-doc ppa-purge scrollkeeper x11proto-composite-dev x11proto-randr-dev x11proto-record-dev x11proto-render-dev x11proto-xinerama-dev xclip yad 0 upgraded, 0 newly installed, 72 to remove and 0 not upgraded. 35 not fully installed or removed. After this operation, 198 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 288586 files and directories currently installed.) Removing dh-translations (129) ... Removing dia-libs (0.97.3-1) ... Removing liblapack-dev (3.6.0-2ubuntu2) ... Removing libblas-dev (3.6.0-2ubuntu2) ... Removing gfortran (4:5.3.1-1ubuntu1) ... Removing gfortran-5 (5.4.0-6ubuntu1~16.04.4) ... Removing gnome-control-center-data (1:3.18.2-1ubuntu6) ... Removing gnome-icon-theme-symbolic (3.12.0-1) ... Removing gnome-icon-theme (3.12.0-1ubuntu3) ... Removing gnome-settings-daemon (3.18.2-0ubuntu3.1) ... Removing iio-sensor-proxy (1.1-1ubuntu1) ... Removing intltool (0.51.0-2) ... Removing launchpad-getkeys (0.3.3-1~webupd8~2) ... Removing libbz2-dev:amd64 (1.0.6-8) ... Removing libcairo-script-interpreter2:amd64 (1.14.6-1) ... Removing libcolord-gtk1:amd64 (0.1.26-1) ... Removing libdbus-1-dev:amd64 (1.10.6-1ubuntu3.3) ... Removing libegl1-mesa-dev:amd64 (12.0.6-0ubuntu0.16.04.1) ... Removing libepoxy-dev:amd64 (1.3.1-1) ... Removing libxft-dev (2.3.2-1) ... Removing libfontconfig1-dev:amd64 (2.11.94-0ubuntu1.1) ... Removing libfreetype6-dev:amd64 (2.6.1-0.1ubuntu2.1) ... Removing libgfortran-5-dev:amd64 (5.4.0-6ubuntu1~16.04.4) ... Removing nettle-dev (3.2-1ubuntu0.16.04.1) ... Removing libgmp-dev:amd64 (2:6.1.0+dfsg-2) ... Removing libgmpxx4ldbl:amd64 (2:6.1.0+dfsg-2) ... Removing libharfbuzz-dev (1.0.1-1ubuntu0.1) ... Removing libharfbuzz-gobject0:amd64 (1.0.1-1ubuntu0.1) ... Removing libsm-dev:amd64 (2:1.2.2-1) ... Removing libice-dev:amd64 (2:1.0.9-1) ... Removing yad (0.38.2-1~webupd8~xenial0) ... Removing libwebkitgtk-3.0-0:amd64 (2.4.11-0ubuntu0.1) ... Removing libjavascriptcoregtk-3.0-0:amd64 (2.4.11-0ubuntu0.1) ... Removing libjpeg-dev:amd64 (8c-2ubuntu8) ... Removing libjpeg8-dev:amd64 (8c-2ubuntu8) ... Removing libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... Removing liblzma-dev:amd64 (5.1.1alpha+20120614-2ubuntu2) ... Removing libmirclient-dev:amd64 (0.21.0+16.04.20160330-0ubuntu1) ... Removing libmircommon-dev:amd64 (0.21.0+16.04.20160330-0ubuntu1) ... Removing libmircookie-dev:amd64 (0.21.0+16.04.20160330-0ubuntu1) ... Removing libmircookie2:amd64 (0.21.0+16.04.20160330-0ubuntu1) ... Removing libncurses5-dev:amd64 (6.0+20160213-1ubuntu1) ... Removing libpixman-1-dev (0.33.6-1) ... Removing libpng12-dev:amd64 (1.2.54-1ubuntu1) ... Removing libprotobuf-dev:amd64 (2.6.1-1.3) ... Removing libpython-all-dev:amd64 (2.7.11-1) ... Removing libpython-dev:amd64 (2.7.11-1) ... Removing libpython2.7-dev:amd64 (2.7.12-1ubuntu0~16.04.1) ... Removing libreadline-dev:amd64 (6.3-8ubuntu2) ... Removing libreadline6-dev:amd64 (6.3-8ubuntu2) ...
[Desktop-packages] [Bug 1886314] Re: preinstall `earlyoom` by default
** Tags removed: rls-gg-incoming ** Tags added: rls-gg-notfixing -- 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/1886314 Title: preinstall `earlyoom` by default Status in ubuntu-meta package in Ubuntu: New Bug description: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1886314/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887822] [NEW] SRU to stable 1.90.2
Public bug reported: [ Impact ] Update to the libfprint 1.90.2 stable version containing various drivers and crash fixes https://gitlab.freedesktop.org/libfprint/libfprint/-/tags/v1.90.2 [ Test case ] If you already enrolled your fingers in gnome-control-center, ensure that fprintd-verify (or gnome-shell fingerprint unlock) works as it was before. If you didn't or you couldn't enroll your fingers before, ensure you can from gnome-control-center or using fprintd-enroll utility. [ Regression potential ] A patch for nbis required for some sensors was accidentally dropped in an earlier release. Users of these sensors/drivers (aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll (see https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/142). ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: libfprint (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Summary changed: - SRU 1.90.2 + SRU to stable 1.90.2 -- 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/1887822 Title: SRU to stable 1.90.2 Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: In Progress Bug description: [ Impact ] Update to the libfprint 1.90.2 stable version containing various drivers and crash fixes https://gitlab.freedesktop.org/libfprint/libfprint/-/tags/v1.90.2 [ Test case ] If you already enrolled your fingers in gnome-control-center, ensure that fprintd-verify (or gnome-shell fingerprint unlock) works as it was before. If you didn't or you couldn't enroll your fingers before, ensure you can from gnome-control-center or using fprintd-enroll utility. [ Regression potential ] A patch for nbis required for some sensors was accidentally dropped in an earlier release. Users of these sensors/drivers (aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll (see https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/142). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1887822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887821] [NEW] gnome-shell GUI freezes totally
Public bug reported: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog after that, and ping worked into this frozen machine. So the whole OS didn't crash. Only GUI related. I hope this helps. lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 apt-cache policy firefox firefox: Installed: 78.0.2+build2-0ubuntu0.20.04.1 Candidate: 78.0.2+build2-0ubuntu0.20.04.1 Version table: *** 78.0.2+build2-0ubuntu0.20.04.1 500 500 http://fi.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 75.0+build3-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages I'm sure this is a bug. The same effect has happened 3 times in 30 days. I didn't check the previous syslog which error message there was. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887821 Title: gnome-shell GUI freezes totally Status in pulseaudio package in Ubuntu: New Bug description: I'm using basic Ubuntu 20.04 and GUI (gnome?) freezes totally. - I was running Firefox 78.0.2 and watching Youtube. The video and sound stopped. - Keyboard was unresponsive, can't get into console, and for example pressing caps lock/num lock didn't toggle keyboard leds. - mouse didn't move. - The whole computer and OS didn't crash I suppose. I could ping the computer from another computer. and there were entries in /var/log/syslog after the GUI freeze. What ever happened I can find some indicating in /var/log/syslog: Crash happened 14:21 local time which pinpoints the bug into these entries: Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, ImageBridgeChld] WARNING: failed to open shm: Too many open files: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/ipc/chromium/src/base/shared_memory_posix.cc, line 246 Jul 16 14:21:24 Aorus-Ultra-Ryzen gnome-shell[897367]: [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470 Jul 16 14:21:25 Aorus-Ultra-Ryzen gnome-shell[897367]: message repeated 2 times: [ [Child 897367, MediaDecoderStateMachine #1] WARNING: Decoder=7f08246e5000 Decode error: NS_ERROR_OUT_OF_MEMORY (0x8007000e) - mozilla::MediaResult mozilla::FFmpegVideoDecoder<46465650>::CreateImage(int64_t, int64_t, int64_t, MediaDataDecoder::DecodedData &): image allocation error: file /build/firefox-k3d8Rk/firefox-78.0.2+build2/dom/media/MediaDecoderStateMachine.cpp, line 3470] after that anything GUI, keyboard or mouse related was totally unresponsive. there were other entries in syslog
[Desktop-packages] [Bug 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority
Hi, Lukas and SRU taem This one is blocking another SRU[1] for a certification platform. If we would like land the #1887610 soon to meet the project schedule, what would be the best approach to do this? - Can we reduce the review time for this SRU, since it's verified? - Or should we merge two SRU into one? [1] https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610 ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- 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/1882161 Title: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] * On the Dell machines with multi function audio jack, the headphone/headset can't output sound automatically, which is different from ubuntu 18.04. The headphone/headset should be able to output sound automatically after plugging in the audio jack. [Test Case] * On Tiger Lake platform Reproduce step: 1. plug headphone/headset 2. open g-c-c sound to check Expect result: The output device should switch to headphone or headset, since headphone's priority is higher in ucm2 config. Actual result: The output device is still internal speaker. [Regression Potential] * The change insert the ucm device by its priority, the potential regression is low, since if the change is not working properly, the side effect is that the order of ucm devices are wrong, and it won't switch to the correct output device as expect, but user can still config it manually. [Other] * This bug originates from an OEM private bug #1875597, then ubuntu users reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329 and the 1st issue of #1881659 have the same root cause as #1875597 * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, finally the audio jack is set to Mic2 mode, this make the audio jack can't output sound anymore. To fix it, let the audio jack set to Headset MIC mode by default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the device event to module-switch-on-port-available by the order of priority in the umc2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Shengyao Xue (xueshengyao) -- 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/1887610 Title: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode' Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Bionic: Confirmed Status in pulseaudio source package in Eoan: Won't Fix Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: [Impact] On some I+N machines (inlcuding lenovo and dell machines), after setting the graphic mode to perofermance mode, and open the gnome sound seting, run suspend/resume test, the audio devices will disappear from UI, instead a dummy audio shows on the UI, and from then on, the audio can't work anymore. [Fix] The root cause is after resuming, the pulseaudio try to recover the PCM device, but at that moment, the devices nodes at /dev/snd/ are not accessible yet sometimes, it will make snd_pcm_open fail and the pulseaudio will calll unload_module to unload alsa audio card. I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(), this will retry the snd_pcm_open() a couple of times if it fails. [Test Case] Install the pulseaudio wit this fix, set the graphic mode to performance mode, open the sound setting, then run suspend/resume 90 times, after test check the audio devices on the UI, the speaker, digital mic are still on the UI, and they could work well. [Regression Risk] Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open() doesn't fail, this patch will not introduce any change, if snd_pcm_open() fails, it just retry a couple of times, so it will not introduce the regression in theory. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1887610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Please raise the issue to the following email address: Jarkko Nikula (maintainer:SYNOPSYS DESIGNWARE I2C DRIVER) Andy Shevchenko (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Mika Westerberg (reviewer:SYNOPSYS DESIGNWARE I2C DRIVER) Philipp Zabel (maintainer:RESET CONTROLLER FRAMEWORK) linux-...@vger.kernel.org (open list:SYNOPSYS DESIGNWARE I2C DRIVER) linux-ker...@vger.kernel.org (open list) -- 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: New 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
[Desktop-packages] [Bug 1887793] Re: chromium unable to launch
Can you please refresh again to revision 1229 and run the snap with the following command, and share the output? chromium --enable-logging=stderr --v=1 ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1887793 Title: chromium unable to launch Status in chromium-browser package in Ubuntu: Incomplete Bug description: Updated the chromium snap yesterday, latest/stable (1229). Today from a fresh boot, it won't launch. ``` mattias@cerebus:~$ chromium Gtk-Message: 10:04:38.060: Failed to load module "canberra-gtk-module" Gtk-Message: 10:04:38.061: Failed to load module "canberra-gtk-module" Trace/breakpoint trap (core dumped) ``` Using snap revert it goes back to latest/stable (1213), and works perfectly. Refreshing back to 1229 reproduces the issue. OS: Ubuntu 20.04 LTS x86_64 Kernel: 5.4.0-40-generic Uptime: 1 hour, 43 mins Packages: 2233 (dpkg), 86 (snap) Shell: bash 5.0.16 Resolution: 2560x1440, 2560x1440 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-4770K (8) @ 3.900GHz GPU: NVIDIA GeForce GTX 970 Memory: 8251MiB / 15945MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887514] Re: Some desktop files don't open with double click or Enter
Some precisions : the mount was a NTFS external hard drive and the remaining issue is the bug report #1887816. -- 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/1887514 Title: Some desktop files don't open with double click or Enter Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: I have two folders visible in my desktop but not in the folder desktop (personal folder and trash), they were there when I installed Ubuntu. Some days ago I've added two .txt files on the desktop folder. Theses two files don't open when I double click, select and press Enter, or right click and select "open". To open them from the desktop, I have to right click, select "open with another application", then it opens a window and I select my program. After doing it two times and execute ubuntu-bug, select "open with..." don't open anymore the window but opens directly the file with the program I've selected before (it acts like "open"). To pinpoint the problem, I've copied two new .txt files, one with nautilus and one with right click on the desktop. Theses new files open normally, with double click or select and Enter. So the two other files are kind of locked... I am not sure if the problem comes from xdg-desktop-portal package, but I could not find a "better" package... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal 1.6.0-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: Tue Jul 14 12:49:58 2020 InstallationDate: Installed on 2020-07-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xdg-desktop-portal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1887514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887816] [NEW] Right click "open with" opens directly without asking for a program
Public bug reported: I copied .txt files to my desktop folder (from NTFS external disk) and tried to open them but they were with right 777 (rwxrwxrwx) so press Enter (etc.) try to execute and not open the file with an editing program. Then I rote a bug report (#1887514), understood my problem and changed the rights of the files. But there is still a problem. When I was trying to identify the problem, I tried "open with" on the right click menu. It worked (a window is opened and ask witch program I want to use). And after reporting the "bug" (that wasn't a bug) the option "open with" didn't opened anymore the window to choose a program. It opens directly as if I've selected "open". It do the same to every new files I add to the desktop, and I already have rebooted my computer (it was some days ago). I am not sure if the package I've selected is the right one for this problem, I don't know a lot about how Ubuntu is structured (and I don't know where I can find precise information). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-2~ubuntu20.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: Thu Jul 16 16:20:32 2020 InstallationDate: Installed on 2020-07-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-desktop-icons (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 gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1887816 Title: Right click "open with" opens directly without asking for a program Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I copied .txt files to my desktop folder (from NTFS external disk) and tried to open them but they were with right 777 (rwxrwxrwx) so press Enter (etc.) try to execute and not open the file with an editing program. Then I rote a bug report (#1887514), understood my problem and changed the rights of the files. But there is still a problem. When I was trying to identify the problem, I tried "open with" on the right click menu. It worked (a window is opened and ask witch program I want to use). And after reporting the "bug" (that wasn't a bug) the option "open with" didn't opened anymore the window to choose a program. It opens directly as if I've selected "open". It do the same to every new files I add to the desktop, and I already have rebooted my computer (it was some days ago). I am not sure if the package I've selected is the right one for this problem, I don't know a lot about how Ubuntu is structured (and I don't know where I can find precise information). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-2~ubuntu20.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: Thu Jul 16 16:20:32 2020 InstallationDate: Installed on 2020-07-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1887816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887285] Re: Restore the "open with" submenu
*** This bug is a duplicate of bug 1647217 *** https://bugs.launchpad.net/bugs/1647217 Upstream discussion is on https://gitlab.gnome.org/GNOME/nautilus/-/issues/531 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887285 Title: Restore the "open with" submenu Status in nautilus package in Ubuntu: New Bug description: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887285] Re: Restore the "open with" submenu
*** This bug is a duplicate of bug 1647217 *** https://bugs.launchpad.net/bugs/1647217 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 1647217, 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 1647217 Nautilus “Open with …” context menu gone on upgrade to yakkety ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #531 https://gitlab.gnome.org/GNOME/nautilus/-/issues/531 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887285 Title: Restore the "open with" submenu Status in nautilus package in Ubuntu: New Bug description: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887478] Re: missing symlinks for login and logout files used by gnome
Why should that be done in the package and isn't done upstream? Also how do you test those service, using what desktop? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1887478 Title: missing symlinks for login and logout files used by gnome Status in sound-theme-freedesktop package in Ubuntu: Incomplete Bug description: Merge request submitted upstream in Debian to fix the issue. https://salsa.debian.org/gnome-team/sound-theme-freedesktop/-/merge_requests/1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1887478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887646] Re: Add support for BGRA glyphs and scaling
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: xft (Ubuntu) Importance: Undecided => Wishlist ** Changed in: xft (Ubuntu) Importance: Wishlist => Low ** Changed in: xft (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xft in Ubuntu. https://bugs.launchpad.net/bugs/1887646 Title: Add support for BGRA glyphs and scaling Status in xft package in Ubuntu: Incomplete Bug description: Not sure if the maintainers here are aware of this, but libxft2 has been misbehaving with emoji for a while. The result is that e.g. st (the terminal emulator) and gitk crash immediately when trying to render emoji. Very annoying. There's an upstream PR in the works here: https://gitlab.freedesktop.org/xorg/lib/libxft/-/merge_requests/1#note_567035 It is not merged upstream yet and does seem to need another push to do so. This persisted for me through an upgrade from 20.04 to "rolling rhino" and people in that thread report it for the 18. and 19 series too. I'm not in a position to contribute code to this, sadly. I barely understand what this is all about. But it is an annoying user facing bug so I figured it'd be better the Ubuntu maintainers be aware of it. Sorry if this is already being handled, I couldn't find any matching reports here yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xft/+bug/1887646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768074] Re: Mouseover does not show folder names reliably
The report is now also in gitlab on https://gitlab.gnome.org/GNOME/baobab/-/issues/14 ** Bug watch added: gitlab.gnome.org/GNOME/baobab/-/issues #14 https://gitlab.gnome.org/GNOME/baobab/-/issues/14 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1768074 Title: Mouseover does not show folder names reliably Status in baobab: Confirmed Status in baobab package in Ubuntu: Confirmed Bug description: When holding my cursor still over a folder in the visualization (in either mode) I expect the name and size of the folder to appear in a floating box, as well as the names the folders contained in it. In my brand new install of Ubuntu 18.04, however, this does not happen most of the time. When holding my cursor over a folder, it «lights up» as usual, but after a second or two, it gets darker again, and nothing appears. However, it sometimes does work for certain folders. Based on a small amount of testing, those folders seem to be close to 8 or 9 o'clock when using the pie chart mode, and mostly only folders at the bottom of the hierarchy. I can then move the cursor within the visualization and see the names of all the folders as usual. But if the cursor is outside any folder for some small amount of time, I have to «activate» it again by holding the cursor over a working folder again. The behavior is quite strange and unpredictable, and I have no idea what is causing it or what to do about it. But I thought I would report it here as it makes it very difficult for me to use this application. I am happy to answer any questions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: baobab 3.28.0-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 17:43:39 2018 InstallationDate: Installed on 2018-04-27 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/baobab/+bug/1768074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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)
Could you also give the output of $ snap info gnome-3-34-1804 ? -- 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 1887514] Re: Some desktop files don't open with double click or Enter
Thanks ! I didn't notice but yes, it's right. -- 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/1887514 Title: Some desktop files don't open with double click or Enter Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: I have two folders visible in my desktop but not in the folder desktop (personal folder and trash), they were there when I installed Ubuntu. Some days ago I've added two .txt files on the desktop folder. Theses two files don't open when I double click, select and press Enter, or right click and select "open". To open them from the desktop, I have to right click, select "open with another application", then it opens a window and I select my program. After doing it two times and execute ubuntu-bug, select "open with..." don't open anymore the window but opens directly the file with the program I've selected before (it acts like "open"). To pinpoint the problem, I've copied two new .txt files, one with nautilus and one with right click on the desktop. Theses new files open normally, with double click or select and Enter. So the two other files are kind of locked... I am not sure if the problem comes from xdg-desktop-portal package, but I could not find a "better" package... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xdg-desktop-portal 1.6.0-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: Tue Jul 14 12:49:58 2020 InstallationDate: Installed on 2020-07-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: xdg-desktop-portal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1887514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887807] Re: KDE doesn't prompt whether headphones or a headset is plugged in
The desktop integration is not up to pulseaudio, reassigning to KDE ** Package changed: pulseaudio (Ubuntu) => kdebase (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887807 Title: KDE doesn't prompt whether headphones or a headset is plugged in Status in kdebase package in Ubuntu: New Bug description: As a follow-up from: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056 I have a Dell XPS 7590 with a combined headset jack. As I understood from the previous ticket 1876056, when on Ubuntu you plug in something, it will prompt you what you plugged in: either a headset or headphones. Kubuntu doesn't do this. This means that it will never automatically switch to the headset microphone when I plug it in, even though I never ever use headphones on this laptop. So it would be great if Kubuntu would prompt me what I plugged in and allow me to either select every time or select the default option when I plug something in. For now I'm working around this by adding [Jack Headphone Mic] state.plugged = no state.unplugged = unknown [Jack Headset Mic] state.plugged = no state.unplugged = unknown to /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal- mic.conf but after each update of pulseaudio this file gets reverted. And it's not really user friendly. I'm really not sure against what package I should report this - please correct me if this should be more specific (e.g. phonon or kde multimedia). I wouldn't know which part this would be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/1887807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835644] Re: CRL files are not accessible for the Verify CRL options
Could you report the issue upstream on https://gitlab.gnome.org/GNOME /NetworkManager-openvpn/issues since it's likely a problem in the upstream codebase? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1835644 Title: CRL files are not accessible for the Verify CRL options Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Hello, The Network Manager GUI options 'Verify CRL from file' and 'Verify CRL from directory' won't work because the openvpn process cannot access the files since being run with chroot, so the connection fails: nm-openvpn[5069]: chroot to '/var/lib/openvpn/chroot' and cd to '/' succeeded nm-openvpn[6135]: Options error: --crl-verify fails with '/var/lib/openvpn/chroot//home/steve/VPN/config/crl.rsa.4096.pem': No such file or directory (errno=2) Thanks. Ubuntu 19.04 network-manager-openvpn, network-manager-openvpn-gnome 1.8.10-1 openvpn 2.4.6-1ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1835644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866498] Re: [Snap] Libreoffice Snap is not available in Hungarian
** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Adolfo Jayme (fitojb) ** Changed in: libreoffice (Ubuntu) Status: New => Triaged -- 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/1866498 Title: [Snap] Libreoffice Snap is not available in Hungarian Status in libreoffice package in Ubuntu: Triaged Bug description: Could you please add Hungarian language to libreoffice snap. I want to change all my deb applications to snaps but this isn'T possible without correct localization. Thanks I know it adds ~ 8mb overhead to the snap but I think it's an acceptable size compared to nowadays HDD sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1866498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870564] Re: Libreoffice's "Customize" dialog is too big in Ubuntu 19.10
** Summary changed: - Libreoffice's option "Customize" is imcompatble to decrease its Window size in Ubuntu 19.10 + Libreoffice's "Customize" dialog is too big in Ubuntu 19.10 -- 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/1870564 Title: Libreoffice's "Customize" dialog is too big in Ubuntu 19.10 Status in libreoffice package in Ubuntu: New Bug description: As discussed here in detail: https://ask.libreoffice.org/en/question/236517/i-think-we-need- scroolbar-in-los-customize-option-so-that-users-can-peacefull-use-the- option-which-are-not-visible-in-the-screen/ I was wondering if it's happening in Ubuntu distros only. Since our GNOME is unique. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1870564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887807] [NEW] KDE doesn't prompt whether headphones or a headset is plugged in
Public bug reported: As a follow-up from: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056 I have a Dell XPS 7590 with a combined headset jack. As I understood from the previous ticket 1876056, when on Ubuntu you plug in something, it will prompt you what you plugged in: either a headset or headphones. Kubuntu doesn't do this. This means that it will never automatically switch to the headset microphone when I plug it in, even though I never ever use headphones on this laptop. So it would be great if Kubuntu would prompt me what I plugged in and allow me to either select every time or select the default option when I plug something in. For now I'm working around this by adding [Jack Headphone Mic] state.plugged = no state.unplugged = unknown [Jack Headset Mic] state.plugged = no state.unplugged = unknown to /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf but after each update of pulseaudio this file gets reverted. And it's not really user friendly. I'm really not sure against what package I should report this - please correct me if this should be more specific (e.g. phonon or kde multimedia). I wouldn't know which part this would be. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1887807 Title: KDE doesn't prompt whether headphones or a headset is plugged in Status in pulseaudio package in Ubuntu: New Bug description: As a follow-up from: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876056 I have a Dell XPS 7590 with a combined headset jack. As I understood from the previous ticket 1876056, when on Ubuntu you plug in something, it will prompt you what you plugged in: either a headset or headphones. Kubuntu doesn't do this. This means that it will never automatically switch to the headset microphone when I plug it in, even though I never ever use headphones on this laptop. So it would be great if Kubuntu would prompt me what I plugged in and allow me to either select every time or select the default option when I plug something in. For now I'm working around this by adding [Jack Headphone Mic] state.plugged = no state.unplugged = unknown [Jack Headset Mic] state.plugged = no state.unplugged = unknown to /usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal- mic.conf but after each update of pulseaudio this file gets reverted. And it's not really user friendly. I'm really not sure against what package I should report this - please correct me if this should be more specific (e.g. phonon or kde multimedia). I wouldn't know which part this would be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues
This issue is related to it and probably both could be fixed at the same time. -- 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/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: In Progress Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1616650] Re: snap refresh while command is running may cause issues
I opened https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1887804 to address the fact that chromium-browser-snap is not following XDG base directory specification and that breaks backing up the snap's configuration and wiping it's cache properly. -- 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/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: In Progress Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification Status in chromium-browser package in Ubuntu: Confirmed Bug description: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
