[Desktop-packages] [Bug 1824692] Re: Question mark within the Wi-Fi icon
*** This bug is a duplicate of bug 1722256 *** https://bugs.launchpad.net/bugs/1722256 Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1824692 Title: Question mark within the Wi-Fi icon Status in gnome-shell package in Ubuntu: Confirmed Bug description: Question mark within the Wi-Fi icon after connecting to the internet. It should be noted that there is no problem with connecting to the Internet, and I have full Internet access and there is only a question mark within the Wi-Fi icon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.403 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 14 10:48:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:194d] Subsystem: ASUSTeK Computer Inc. GK208BM [GeForce 920M] [1043:232a] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) MachineType: ASUSTeK COMPUTER INC. TP300LJ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP300LJ.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP300LJ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP300LJ.206:bd08/05/2015:svnASUSTeKCOMPUTERINC.:pnTP300LJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP300LJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP300LJ dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/1824692/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832222] Re: using aakar font reboots printer
I re-tested in preparation for submitting the bug to Debian, and the problem has disappeared. Something has changed in the 10 months since my report, the package is still Version: 1.0-6ubuntu0.1, but plenty of other packages on the system have been updated. As there is no way of reproducing and investigating the root cause, I'm marking it as Invalid. ** Changed in: fonts-gujr-extra (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-gujr-extra in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: using aakar font reboots printer Status in fonts-gujr-extra package in Ubuntu: Invalid Bug description: A user accidentally selected the aakar font for one cell of a spreadsheet containing English text. Printing the spreadsheet resulted in the printer displaying: Rebooting... followed by Initializing The result was the same for both printers tried: Samsung SL-M3820ND and HP Colour LaserJet CM1017 The spreadsheet was exported to a PDF, printing the PDF caused the same printer reboot. Opening the PDF in Libre Office Draw and printing caused the same printer reboot. If the font was changed to Liberation Sans, the file could be printed. A minimal Libre Office spreadsheet with the problem is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-gujr-extra/+bug/183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
What's happening is g-c-c is attempting to select the requested online account setup (ubuntusso in this case) at the time it's creating the panel. This works if the panel was already selected. Investigating exactly why doing both at the same time crashes and how to resolve. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Please test latest 20.04. SoF DMIC should work now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873386] [NEW] nmcli error report on reboot after latest 20.04 updates
Public bug reported: Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416. Upon reboot system should error and error for nmcli. Crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 16 21:58:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1873386 Title: nmcli error report on reboot after latest 20.04 updates Status in network-manager package in Ubuntu: New Bug description: Ubuntu MATE 20.04. Updated to latest updates and newest kernel, on 20200416. Upon reboot system should error and error for nmcli. Crash file located in /var/crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Apr 16 21:58:56 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.159 metric 600 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-04-04 (12 days ago) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull full /org/freedesktop/NetworkManager/Devices/3 Lothlorien 41892137-acd0-46f2-8959-5f1e126489b0 /org/freedesktop/NetworkManager/ActiveConnection/1 enp1s0 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873386/+subscriptions --
[Desktop-packages] [Bug 1872276] Re: Gnome shell huge app's icon size in the app folder
In that case please attach a screenshot of the bug. ** This bug is no longer a duplicate of bug 1869737 App icons shrink or disappear after closing an app folder ** 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/1872276 Title: Gnome shell huge app's icon size in the app folder Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app folder created in app launcher, the resulting dialog holding apps of app folder are having icon size larger than the other apps shown in the app launcher. How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Drag app icon to create apps folder. 3- As the app folder gets created, click to open it and observe the size of app icons shown by the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:48:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873263] Re: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c
This bug was fixed in the package shadow - 1:4.8.1-1ubuntu5 --- shadow (1:4.8.1-1ubuntu5) focal; urgency=medium * debian/patches/1015_add_zsys_support.patch: Fix regression on zfs system when the user dataset wasn’t created (LP: #1873263) - wrong variable was used when merged with debian - reset the correct order to ensure owner and mod are correct. -- Didier Roche Thu, 16 Apr 2020 14:36:45 +0200 ** Changed in: shadow (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1873263 Title: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Released Bug description: There is no more zsys integration for this part of the stack. Fix regression from disco due to useradd merge with debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873346] Re: Remove the grey border/background from the Files (nautilus) icon
** Summary changed: - Gnome Files icon bug focal + Remove the grey border/background from the Files (nautilus) icon ** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu) ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Wishlist ** Changed in: yaru-theme (Ubuntu) Status: New => Triaged -- 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/1873346 Title: Remove the grey border/background from the Files (nautilus) icon Status in yaru-theme package in Ubuntu: Triaged Bug description: Gnome Files icon is showing on the light background in gnome-shell, but all other icons on transparent background. See attached screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 22:48:17 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/yaru-theme/+bug/1873346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873354] Re: Application icons don't show when external monitor connected
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 Actually it sounds like you will experience both bug 1869571 and bug 1869737, so please subscribe to both. -- 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/1873354 Title: Application icons don't show when external monitor connected Status in xorg package in Ubuntu: New Bug description: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236PA8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET79WW(1.49):bd09/05/2016:svnLENOVO:pn4236PA8:pvrThinkPadT420:rvnLENOVO:rn4236PA8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236PA8 dmi.product.version: ThinkPad T420 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873354] Re: Application icons don't show when external monitor connected
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 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 1869571, 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 1869571 Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen -- 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/1873354 Title: Application icons don't show when external monitor connected Status in xorg package in Ubuntu: New Bug description: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236PA8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET79WW(1.49):bd09/05/2016:svnLENOVO:pn4236PA8:pvrThinkPadT420:rvnLENOVO:rn4236PA8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236PA8 dmi.product.version: ThinkPad T420 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872276] Re: Gnome shell huge app's icon size in the app folder
*** This bug is a duplicate of bug 1869737 *** https://bugs.launchpad.net/bugs/1869737 this bug is different, am talking about the size of icons inside the app folder and not the event that occur after closing the app folder. The icons inside app folder are huge and do not matches the rest of the fnome shell. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872276 Title: Gnome shell huge app's icon size in the app folder Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app folder created in app launcher, the resulting dialog holding apps of app folder are having icon size larger than the other apps shown in the app launcher. How to reproduce: 1- Click on 9 dots qt bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Drag app icon to create apps folder. 3- As the app folder gets created, click to open it and observe the size of app icons shown by the folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:48:05 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869635] Re: the menu "Dash to Dock Settings" is visible
See also https://github.com/micheleg/dash-to-dock/issues/1164 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1164 https://github.com/micheleg/dash-to-dock/issues/1164 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869635 Title: the menu "Dash to Dock Settings" is visible Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: When the user performs a right-button mouse click on the "Show Applications" button of the Ubuntu Dock then a "Dash to Dock Settings" menu option appears as shown in the attached image. Normally, this menu option is only available on the original "Dash to Dock" GNOME shell extension used as the basis for the Ubuntu Dock and it should not be visible or functional on the Ubuntu Dock itself. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 02:31:58 2020 InstallationDate: Installed on 2020-02-12 (46 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873321] Re: The Show Applications button is unclickable in the corner and along its bottom edge
I don't think this is a bug since the button doesn't reach the corner of the screen. But rather than relying on what I say you should report the issue to the upstream developers at: https://github.com/micheleg/dash-to-dock/issues and then tell us the new bug ID. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button is unclickable in the corner and along its bottom edge Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873316] Re: bluetooth
Your kernel shows some recurring problems with Bluetooth: [205443.289468] Bluetooth: hci0: command 0x1001 tx timeout ... [205451.385131] Bluetooth: hci0: CSR: Local version failed (-110) "CSR" sounds like Cambridge Silicon Radio, which is a brand of Bluetooth chip that many people find to be unreliable. So it might be a good idea to try a different brand. ** Summary changed: - bluetooth + I can't get bluetooth to work ** Package changed: xorg (Ubuntu) => linux (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/1873316 Title: I can't get bluetooth to work Status in linux package in Ubuntu: Confirmed Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 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 2:1.19.6-1ubuntu4.3 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: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873302] Re: Unable to use builtin monitor
You seem to get getting some of your graphics packages from the 'oibaf' PPA, which is not part of Ubuntu and is not supported here. Please remove that from your system and then feel free to open new bugs for any problems you find. ** Package changed: xorg (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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1873302 Title: Unable to use builtin monitor Status in Ubuntu: Invalid Bug description: At some point today, I notice my built in monitor is all black but still on when I use the laptop external monitor. When I unplug the HDMI cable, I dont see anything in the built in display, only the black screen. Restarting the computer shows the usual things in the builtin screen but after booting up into the loginscreen, it goes black. ubuntu19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.82 Wed Apr 1 20:04:33 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 10:36:52 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.82, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 [1462:11ad] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 1060 Mobile] [1462:11ad] InstallationDate: Installed on 2020-04-12 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GS63VR 7RF ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=c4c9dc9f-4b3c-4b89-8954-a0bdc6ffbd8f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16K2IMS.31B dmi.board.asset.tag: Default string dmi.board.name: MS-16K2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16K2IMS.31B:bd03/14/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS63VR7RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16K2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GS dmi.product.name: GS63VR 7RF dmi.product.sku: 16K2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101+git2004031830.27fa47~oibaf~e version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004161334.e3e704~oibaf~e 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.8-2ubuntu2~oibaf~e 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/+bug/1873302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873295] Re: Extensions don't work on Gnome Shell 3.36
*** This bug is a duplicate of bug 1865342 *** https://bugs.launchpad.net/bugs/1865342 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 1870285, 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. ** Summary changed: - Updated 04-16-2000 and system-monitor shell extension broke + Extensions don't work on Gnome Shell 3.36 ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- system-monitor (Ubuntu) ** Changed in: gnome-shell-extension-system-monitor (Ubuntu) Status: Invalid => New ** This bug has been marked a duplicate of bug 1870285 extension system-monitor cannot be loaded, causes errors ** This bug is no longer a duplicate of bug 1870285 extension system-monitor cannot be loaded, causes errors ** This bug has been marked a duplicate of bug 1865342 Error: Tried to construct an object without a GType -- 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/1873295 Title: Extensions don't work on Gnome Shell 3.36 Status in gnome-shell-extension-system-monitor package in Ubuntu: New Bug description: I updated my 20.04 beta box to on 16 Apr 2020 and the system-monitor applet stopped working. Going to https://extensions.gnome.org/extension/120/system-monitor/ shows error. I removed and tried readding with same result. When adding back the /var/log/syslog shows: Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet init from /home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com Apr 16 11:07:58 x1 gnome-shell[1892]: [System monitor] applet enabling Apr 16 11:07:58 x1 gnome-shell[1892]: JS ERROR: Extension system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object without a GType; are you using GObject.registerClass() when inheriting from a GObject type?#012SystemMonitor_TipItem@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9#012tip_format@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27#012SystemMonitor_Cpu@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:14#012createCpus@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20#012enable@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:166:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:336:26#012callback@resource:///org/gnome/shell/ui/extensionDownloader.js:232:39#012gotExtensionZipFile/<@resource:///org/gnome/shell/ui/extensionDownloader.js:115:13 Apr 16 11:08:00 x1 gnome-shell[1892]: JS ERROR: TypeError: this.tip_labels[i] is undefined#012update@/home/pgraner/.local/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:925:56 Nothing I've done can get it working. Googleing hasn't revealed anything useful. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:11:22 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-25 (82 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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-extension-system-monitor/+bug/1873295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
@cpbl see https://askubuntu.com/a/158872 ("Software & Updates" in the
menu now)
--
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/1776873
Title:
Whitelisted allowedURLschemes breaks some desktop apps
Status in snapd:
Triaged
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55
snapd has a hard-coded list of allowed URL schemes. Currently that is
limited to "http", "https", "mailto", "snap".
We have a number of applications in the store which are trying to use
protocol handlers outside this scope and break when that's not
possible.
e.g.
Telegram Desktop: tg:/
Github Desktop: git:/
IRCCloud Desktop: irc:/
These are the ones I know of, others may also be affected. Can we
please at least expand the list to those that we know of, and perhaps
research other popular protocol handlers?
Ideally we wouldn't have a whitelist, because this delays our ability
to land new applications with as-yet unknown url schemes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD)
** Summary changed: - Orange indicator dot is rendered over text in thr app grid + Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) -- 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/1872275 Title: Orange indicator dot is rendered over text in the app grid (with screen resolutions below FHD) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873257] Re: gnome-shell crashes randomly
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/1873257 Title: gnome-shell crashes randomly Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, ubuntu session with wayland. After about one hour usage, while firefox has been launched gnome-shell(?) crashed and falled back to gdm login screen. This has happened several times. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:26:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-06 (740 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-04-07T00:19:12.727815 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873257/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 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-shell/+bug/1872198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873348] Re: Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873348 Title: Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured Status in mutter package in Ubuntu: Fix Released Bug description: - Enable fractional scaling toggle on x11 - Scale a monitor of 200%, 300%... (any integer value) - Play a game or a video fullscreen - The monitors are reconfigured causing a black window This is expected in fractional scaling to make direct-rendering to work properly, but not when the monitor is not scaled or scaled or with an integer value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871849] Re: firefox bug fractional scalling
** Tags added: nvidia xrandr-scaling ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - firefox bug fractional scalling + [nvidia] Firefox does not properly play full screen videos using fractional scale at 125% ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Importance: Low => Undecided -- 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/1871849 Title: [nvidia] Firefox does not properly play full screen videos using fractional scale at 125% Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: firefox does not properly play full screen videos using fractional scale at 125% --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-29 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1872970 Title: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio package in Fedora: Unknown Bug description: I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 sound card. downgrade pulseaudio_13.0-1ubuntu1.1 sound work. https://bugzilla.redhat.com/show_bug.cgi?id=1818883 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/ please build next pulseaudio include patch, ucm: fix the port / ucm device activation on boot alsa sink/source: fix the mixer initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid
This bug was fixed in the package mutter - 3.36.1-3ubuntu2 --- mutter (3.36.1-3ubuntu2) focal; urgency=medium * d/p/monitor-config-manager-Fallback-to-closed-laptop-lid-conf.patch: - Fallback to closed laptop lid configuration if no other available (LP: #1793496) * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Don't override non-fractionally scaled monitors scaling (LP: #1873348) -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 22:04:59 +0200 ** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1793496 Title: scaling changes when closing/re-opening the lid Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Confirmed Status in mutter source package in Focal: Fix Released Bug description: scaling changes when closing/re-opening the lid. Seen in bionic. Mz scaling is set to 100%, but the laptop is considered highdpi by mutter, and during suspend/resume it changes back to default ignoring settings. $ xprop -spy -root RESOURCE_MANAGER [...] RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n" RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n" xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 2560x1440 60.00*+ 59.9959.9959.9659.95 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1873266 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: nvidia ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873266 Title: cannot change main monitor after setting scaling for monitors w/nvidia drivers Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873348] Re: Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured
This bug was fixed in the package mutter - 3.36.1-3ubuntu2 --- mutter (3.36.1-3ubuntu2) focal; urgency=medium * d/p/monitor-config-manager-Fallback-to-closed-laptop-lid-conf.patch: - Fallback to closed laptop lid configuration if no other available (LP: #1793496) * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch: - Don't override non-fractionally scaled monitors scaling (LP: #1873348) -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 22:04:59 +0200 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873348 Title: Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured Status in mutter package in Ubuntu: Fix Released Bug description: - Enable fractional scaling toggle on x11 - Scale a monitor of 200%, 300%... (any integer value) - Play a game or a video fullscreen - The monitors are reconfigured causing a black window This is expected in fractional scaling to make direct-rendering to work properly, but not when the monitor is not scaled or scaled or with an integer value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
I will set up a test environment with actual performance measurements for this bug, but not right now. I don't think there's any additional info we need before then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872796 Title: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have a Dell XPS 9360 with a FHD screen and a Intel HD620 iGPU, running Ubuntu 20.04. On this system animations should be smooth and at 60fps, but this is not always the case. The applications animation (the icons coming from the bottom left) is specially stuttery most of the time. Sometimes it is buttery smooth, but most of the times it is not. It is difficult to pinpoint when. Some exploration that may help to find the issue: * I also have a desktop with 20.04 and a Nvidia 750ti and it seems to be much smoother. This seems to indicate that the problem is somehow related to the Intel iGPU. * Animations seem smoother under Wayland. But, because of other limitations, I am staying on Xorg for now. * The application animation is super stuttery the first time it is opened in a session. It gets slowly better with subsequent uses, although never totally smooth. " The animation is noticeably more stuttery if it opens the “All” applications tab instead of “Frequent” apps. Maybe the number of apps (icons) is a factor? * Vanilla gnome-session seems to be smoother. Maybe the problem is related to Dash-to-dock or another Ubuntu extension? (In my ubuntu session only default extensions are enabled). These datapoints are mainly subjective as I have no means of properly measure animations performance. Don't get my wrong, 20.04 is a clear improvement over 18.04. But it seems there is some room for improvement at least in this hardware. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 15:23:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (780 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873164] Re: [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation
It sounds like the main problem then is actually during boot then. Would you like this bug to focus on that or some other problem after booting? ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Changed in: plymouth (Ubuntu) Importance: Undecided => Low ** Changed in: plymouth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1873164 Title: [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation Status in iio-sensor-proxy package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Bug description: I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD Graphics 600. and its a touchscreen laptop. The Problem is i'm facing with g sensor and screen orientation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:08:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 605 [17aa:39ff] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 81H3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 8NCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad D330-10IGM dmi.modalias: dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM: dmi.product.family: ideapad D330-10IGM dmi.product.name: 81H3 dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM dmi.product.version: Lenovo ideapad D330-10IGM 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/iio-sensor-proxy/+bug/1873164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872111] Re: gnome-software should not provide ubuntu-software
This bug was fixed in the package gnome-software - 3.36.0-0ubuntu3 --- gnome-software (3.36.0-0ubuntu3) focal; urgency=medium * debian/patches/0026-Add-a-dialog-to-log-into-the-snap-store.patch: - Fix FTBFS on riscv64 where snap support is disabled -- Robert Ancell Fri, 17 Apr 2020 10:03:17 +1200 ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872111 Title: gnome-software should not provide ubuntu-software Status in gnome-software package in Ubuntu: Fix Released Bug description: The gnome-software deb provides an ubuntu-software desktop file. This is now provided by the snap-store snap so should be removed from the deb to prevent confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870991] Re: Update gnome-software to 3.36.0 for Focal
This bug was fixed in the package gnome-software - 3.36.0-0ubuntu3 --- gnome-software (3.36.0-0ubuntu3) focal; urgency=medium * debian/patches/0026-Add-a-dialog-to-log-into-the-snap-store.patch: - Fix FTBFS on riscv64 where snap support is disabled -- Robert Ancell Fri, 17 Apr 2020 10:03:17 +1200 ** Changed in: gnome-software (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870991 Title: Update gnome-software to 3.36.0 for Focal Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Focal: Fix Released Bug description: The gnome-software package was replaced by a Snap Store snap, however it would be still good to update it to 3.36.0 (or 3.36.1 when it is released) for Ubuntu 20.04 to allow users with custom configuration or flavours (i believe that, for example, Ubuntu MATE uses the deb version of gnome-software) to have the latest stable gnome-software version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1870991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872258] Re: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored"
This bug was fixed in the package gnome-software - 3.36.0-0ubuntu3 --- gnome-software (3.36.0-0ubuntu3) focal; urgency=medium * debian/patches/0026-Add-a-dialog-to-log-into-the-snap-store.patch: - Fix FTBFS on riscv64 where snap support is disabled -- Robert Ancell Fri, 17 Apr 2020 10:03:17 +1200 ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872258 Title: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored" Status in gnome-software package in Ubuntu: Fix Released Bug description: Hi! GNOME Software currently injects invalid AppStream metadata in Focal, causing a complaint message like "AppStream cache update completed, but some metadata was ignored due to errors." on every APT update. This can be fixed by applying this patch from upstream and Debian, which was present in GNOME's release candidate but was accidentally reverted: https://salsa.debian.org/gnome-team/gnome-software/-/blob/05553c1bfa2124a12e3afe5c63de510310377036/debian/patches/02_fix-appstream-featured-data.patch Debian already ships this patch. Thanks for considering! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873263] Re: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c
This bug was fixed in the package zsys - 0.4.5 --- zsys (0.4.5) focal; urgency=medium * Fix user creation and rename integration (LP: #1873263) * Close socket when the service stops (thanks blkeller) -- Didier Roche Thu, 16 Apr 2020 15:54:23 +0200 ** Changed in: zsys (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1873263 Title: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Fix Released Bug description: There is no more zsys integration for this part of the stack. Fix regression from disco due to useradd merge with debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
I can confirm that this issue is still present in Ubuntu 19.10 and 20.04, as well as Fedora 31. Erikas' suggestion works very well to fix this issue too. I have the same outcome as James Adams above. My laptop is the HP Pavilion x360 Convertible 14-ba0xx. ** Also affects: fedora Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Status in Fedora: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: In Progress Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873321] Re: The Show Applications button is unclickable in the corner and along its bottom edge
gnome-shell-extension-ubuntu-dock has just been updated to version 67ubuntu20.04.4. The issue is still here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button is unclickable in the corner and along its bottom edge Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6
Many many thanks to Butterfly (kelebek333). Finally a capable and willing developer who has made drivers missing for some time. I am testing them with the fast xanmod kernel 5.6.4 and at the moment they seem to be working flawlessly,so I suppose they work with official kernels too. I think a not so small of Ubuntu community that still has a legacy card should be grateful for your work. Thanks again and have a nice day. -- 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/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 and 5.6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
The scratchiness was fixed in alsamixer, by setting mic boost to 100, and internal mic boost to 0. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870737] Re: gnome-control-center crashed with SIGSEGV in get_renderer_from_helper()
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870737 Title: gnome-control-center crashed with SIGSEGV in get_renderer_from_helper() Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I clicked Show Applications -> Settings -> About and the gnome- control-center crashed with this error that I am reporting here. https://errors.ubuntu.com/problem/56089f562d44d6c5438098879570f9bb19f30c8e ktaraszk@x1:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ktaraszk@x1:~$ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.1-1ubuntu3 Candidate: 1:3.36.1-1ubuntu3 Version table: *** 1:3.36.1-1ubuntu3 500 500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:06:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-03-18 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7efec14c25a5 <__strlen_avx2+21>: vpcmpeqb (%rdi),%ymm0,%ymm1 PC (0x7efec14c25a5) ok source "(%rdi)" (0xf1fb487a44088da) not located in a known VMA region (needed readable region)! destination "%ymm0" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1870737/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871195] Re: The adaptive layouts aren't working properly
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871195 Title: The adaptive layouts aren't working properly Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Using 3.36.1 in focal, depending of the local/labels the pages can lead to have the list of panels on the left hidding, that's quite a confusing experience (layout change, not obvious how to change back to another panel and when going back the mainview is empty) Video showing the issue on focal in french: https://gitlab.gnome.org/GNOME/gnome-control-center/uploads/205957358c22144ba761eaca649f99a7/gcc.webm That's reported on https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/942 which is about bluetooth but other panels have the same bug, e.g https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/763. The selection bug is reported as https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/764 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867548] Re: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1867548 Title: Right Alt key is suddenly switched off after invoking Settings - Keyboard Shortcuts in Focal Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: As soon as the Keyboard Shortcuts tab window is invoked in the Settings Application, Right Alt key is switched off system-wide. This happens suddenly even without any action from the user - just simple invoking of the window is enough to break the settings. This obviously happens because of the new setting in the Keyboard Shortcuts appeared in focal: Alternate Characters Key. It sets Right Alt by default immediately as this window is opened. This setting doesn't have the Not Set option, so it is even not easy to switch back to the normal behavior. This setting can be unset only through the GNOME Tweaks application: Keyboard & Mouse - Additional Layout Options - Key to choose the 3rd level - uncheck the box Right Alt. But this is not a good workaround since the Alt key setting will be destroyed again as soon as Keyboard Shortcuts are visited in Settings next time. The reasonable workaround seems to be introduction an option Not Set in the setting Alternate Characters Key and making it default. This will fix this bug and will introduce a sane default value because not every keyboard layout has a third-option for the keys. This is quite significant UX flaw since nothing should be changed without explicit user action. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 22:33:08 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-04-25 (325 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1867548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870735] Re: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size()
*** This bug is a duplicate of bug 1847112 *** https://bugs.launchpad.net/bugs/1847112 This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870735 Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I was running gnome-control-center from KDE/plasma and trying all sections. The crash occurred when I tried to enter the "Display" section. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu3 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 4 08:57:48 2020 ExecutablePath: /usr/bin/gnome-control-center ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x563298319f44 : mov(%rdi),%rax PC (0x563298319f44) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_display_config_set_minimum_size () () () (instance=, signal_id=, detail=) at ../../../gobject/gsignal.c:3554 () Title: gnome-control-center crashed with SIGSEGV in cc_display_config_set_minimum_size() UpgradeStatus: Upgraded to focal on 2020-04-02 (1 days ago) UserGroups: adm cdrom dip fuse kvm libvirt libvirtd lpadmin plugdev sambashare staff sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870600] Re: permissions pane only shows currently-connected snap interfaces
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870600 Title: permissions pane only shows currently-connected snap interfaces Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The applications applet in Gnome Control Center shows permissions that can be toggled on and off for installed applications and snap packages. When viewing a Snap package, only permissions that are currently enabled (interface is connected in Snap terms). Viewing the same Snap package's permissions in Gnome Software or the Snap Store Snap you can see that there are more permissions that can be enabled which are not currently. I have uploaded an example of both views to highlight the discrepency in a screenshot at: https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 3 19:48:07 2020 InstallationDate: Installed on 2020-03-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870600/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: No UI indication for more than 10 fingerprint enrolling progress
This bug was fixed in the package gnome-control-center - 1:3.36.1-1ubuntu5 --- gnome-control-center (1:3.36.1-1ubuntu5) focal; urgency=medium * debian/patches/git-info-crash-on-nvidia.patch: - backport a fix for an info panel segfault on nvidia cards (lp: #1870737) * debian/patches/git-nongnome-segfault.patch: - don't segfault when started outside of GNOME (lp: #1870735) [ Marco Trevisan ] * d/p/0028-user-panel-Add-reference-to-selected-user-and-clear-.patch, * d/p/0029-user-panel-Don-t-wait-for-fprintd-on-initialization.patch, d/p/0030-fingerprint-dialog-Don-t-use-sync-calls-for-deleting.patch, d/p/0031-fingerprint-dialog-Don-t-limit-the-number-of-maximum.patch: - Don't wait for fprintd on initialization and don't limit enroll stages (lp: #1865845) [ Robert Ancell ] * debian/patches/0027-window-Stop-using-HdyLeaflet.patch: - Disable adaptive layouts, theres some bugs and they're not required on desktop (LP: #1871195) * debian/patches/0028-applications-Fix-only-connected-snap-interfaces-show.patch: - Fix disconnected snap interfaces not showing (LP: #1870600) * debian/patches/0029-applications-Use-new-snapd-glib-API-for-labelling-Sn.patch: * debian/control: - Use shared names for snap interfaces, fixing some interfaces that don't have labels. [ Gunnar Hjalmarsson ] * debian/patches/0030-temporarily-revert-alt-char-key.patch: - Revert the "Alternate Characters Key" commit temporarily awaiting a proper fix of LP: #1867548. -- Sebastien Bacher Thu, 16 Apr 2020 12:30:37 +0200 ** Changed in: gnome-control-center (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: No UI indication for more than 10 fingerprint enrolling progress Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: Fix Released Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
** Changed in: mutter Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873326] Re: Icons in the appindicator are too small
Here is the corresponding upstream bug: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/215 ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #215 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/215 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1873326 Title: Icons in the appindicator are too small Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: After a recent update, the icons in the appindicator became too small. The screenshot is attached to demonstrate the issue. This bug looks the same as one of the previous bugs which has been fixed quite long ago: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730406 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:20:00 2020 InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator 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-appindicator/+bug/1873326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
We can do #3. Do you want to update the bug description for that? We'll need to file this as a potential SRU, but it might get fixed before the 20.04 LTS release. -- 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/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: Opinion Status in chrome-gnome-shell package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Opinion Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Sorry - mine is working now, you can delete the above message. With help from System76b tech support, I had to install pavucontrol and turn the microphone (input device) way up. Then I tried recording my voice in audacity and it's horribly scratchy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
(In reply to m from comment #15) > This addon is only for Firefox, so not a solution for Thunderbird, right? I don't use Thunderbird, but it isn't a lot of code, so someone could probably port it: https://github.com/kimsey0/FirefoxAutoDict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
(In reply to Jacob Bundgaard from comment #14) > I ended up making an extension that tries to detect the language used in each > input field, then switches the spell checking to the correct language for > that field: > https://addons.mozilla.org/da/firefox/addon/automatic-spelling-language/ > > However, this isn't quite the same as spell checking in multiple languages at > the same time, so I still hope this bug gets addressed. This addon is only for Firefox, so not a solution for Thunderbird, right? This 10 years old improvement proposal is still UNCONFIRMED, or the status field was not updated? Is there a general consensus that it would make sense to implement this enhancement and is it clear how to do it? I saw several tickets dealing with this same issue. This one here is the master ticket? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704870] Re: Keys can't be grabbed under Wayland
I can confirm that this bug is still present using gnome with ubuntu 18.04.lts I'll give it a try in another pc with ubuntu 20.04 beta and tell you about it -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1704870 Title: Keys can't be grabbed under Wayland Status in remmina: New Status in wayland: Confirmed Status in remmina package in Ubuntu: Confirmed Status in wayland package in Fedora: Confirmed Bug description: Special keys are not working under Remmina. Seems to be a Wayland specification and implementation of that specification. This bug could embrace all apps that need this behavior (VirtualBox, vncviewer, etc) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: remmina 1.1.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 15:36:36 2017 InstallationDate: Installed on 2017-07-04 (13 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626) SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/remmina/+bug/1704870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873365] [NEW] gedit icon is too pale
Public bug reported: The grey lines representing text on the paper sheet and the tip of the pencil in the icon are too pale. They are almost invisible so that the gedit icon is seen as a white rectangle crossed by a blue bar. Before focal, the icons of gedit and Evince used to have similar design, that is they both were pale. Now in focal, the Evince icon is redesigned and it is more clear with more contrast. The suggestion is to apply similar modifications to the gedit icon to make it more clear. For example, it can use the same dark gray color of the text lines as Evince icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:10:13 2020 Dependencies: InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (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 yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1873365 Title: gedit icon is too pale Status in yaru-theme package in Ubuntu: New Bug description: The grey lines representing text on the paper sheet and the tip of the pencil in the icon are too pale. They are almost invisible so that the gedit icon is seen as a white rectangle crossed by a blue bar. Before focal, the icons of gedit and Evince used to have similar design, that is they both were pale. Now in focal, the Evince icon is redesigned and it is more clear with more contrast. The suggestion is to apply similar modifications to the gedit icon to make it more clear. For example, it can use the same dark gray color of the text lines as Evince icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:10:13 2020 Dependencies: InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1873365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873351] Re: On two monitors configuration Super-S and search for app cut off
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 I see hat you mean! But I really need it for 3 monitors. If it monitors in side-by-side it works fine, if vertically - seems like a bug. Pls consider fixing. Any settings that can ease the pain ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873351 Title: On two monitors configuration Super-S and search for app cut off Status in gnome-control-center package in Ubuntu: New Bug description: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871320] Re: Switching alert sound will not take effect unless you switch to Default alert first
Hum, now changing that settings isn't making g-t sound change anymore for some reasons... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1871320 Title: Switching alert sound will not take effect unless you switch to Default alert first Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I installed April 5th's nightly build, of Ubuntu Focal Fossa (development branch). Description: Ubuntu Focal Fossa (development branch) Release: 20.04 The issue is, Whichever the notification sound we choose after default, only that sound will take effect. Directly changing to another type of alert sound will not take effect. To reproduce the problem, 1. Open terminal, 2. Open sound settings, initially it will be "default". Change that to some other alert sound, say, "Drip". 3. Switch to terminal and press backspace, you will hear "Drip". 4. Switch to sound settings, this time select "Glass". 5. Switch to terminal and press backspace, here is the issue. You will not hear "Glass". You will still hear "Drip". 6. Switch to sound settings, now select default first and then select "Glass". 7. Switch to terminal and press backspace, now you will hear "Glass". So to summarize, if you want to change the alert sound, first you have to switch back to "Default" and then only whichever other alert sound you select, will take effect. Since the release time is near, I thought it would be helpful to fix this before release. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
** Changed in: alsa-plugins (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: Invalid Status in jackd2 package in Ubuntu: Fix Released Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873360] Re: Ethernet driver not loaded at boot
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
wow, @kfunk and @axet, thank you so much for this effort! Alas, I get stuck at the very first step: sudo apt-get build-dep snapd Reading package lists... Done E: You must put some 'source' URIs in your sources.list -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873351] Re: On two monitors configuration Super-S and search for app cut off
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 you can move the monitors in the settings -> display panel by dragging the rectangles -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873351 Title: On two monitors configuration Super-S and search for app cut off Status in gnome-control-center package in Ubuntu: New Bug description: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872690] Re: sort by date broken
ok, closing then, feel free to reopen if you hit it again ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/1872690 Title: sort by date broken Status in nautilus package in Ubuntu: Invalid Bug description: Version: 1:3.36.1.1-1ubuntu2 Sort by date appears using the text on the screen for the sort. The result is that things done today are in the middle of the list instead of at the top/bottom. It should be using unix time in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873360] [NEW] Ethernet driver not loaded at boot
Public bug reported: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1873360/+attachment/5355779/+files/dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1873360 Title: Ethernet driver not loaded at boot Status in network-manager package in Ubuntu: New Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1873360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1267866] Re: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3
While I do not have the same USB soundcard this bug started with, I can confirm this is still happening with the 5.5 Kernel running in Ubuntu 19.10 and other USB sound cards. I am using a Schiit Fulla v3. When trying to use ALSA mixer I get the same broken pipe error. When tailing both journalctl and syslog I see the following error when the broken pipe occurs. kernel: [25828.174373] usb 1-2.3: cannot get ctl value: req = 0x81, wValue = 0x100, wIndex = 0x1100, type = 1 Considering this distro is no long maintained, should another bug be opened against the current 19.10 distro? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1267866 Title: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3 Status in alsa-driver package in Ubuntu: Incomplete Bug description: I typed in terminal: alsamixer Then I wanted to change the sound card (I have connected an external sound card via USB). I pressed F6, selected the external sound card and pressed enter. alsamixer crashed and outputed: cannot load mixer controls: Broken pipe My ALSA information is located at http://www.alsa- project.org/db/?f=1871c086b58a2965d18cfb38483794788187edfb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267866/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873351] Re: On two monitors configuration Super-S and search for app cut off
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 I guess I do use vertical as I don't even know how to use horizontal. Pls let me know how to change it and I will test -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873351 Title: On two monitors configuration Super-S and search for app cut off Status in gnome-control-center package in Ubuntu: New Bug description: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- 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/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 and 5.6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
For me it seems, that bug happens only at login after a kernel update followed by a reboot to finish update. "normal" (Re)boot without update => no bug. And i use Dropbox to (Autostart at Login). -- 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/1857539 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 and 5.6
Hi, Using the patches in the aur repository, I prepared a PPA repository for the nvidia-340. If wish you can install nvidia-340 package (supported for kernel 5.5, 5.6 series) from PPA. You can add PPA with following command. sudo add-apt-repository ppa:kelebek333/nvidia-legacy -- 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/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 and 5.6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872690] Re: sort by date broken
Close the bug, I can't reproduce it anymore. Seriously, it was doing it, but that may have been on the initial beta (without updates). -- 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/1872690 Title: sort by date broken Status in nautilus package in Ubuntu: Incomplete Bug description: Version: 1:3.36.1.1-1ubuntu2 Sort by date appears using the text on the screen for the sort. The result is that things done today are in the middle of the list instead of at the top/bottom. It should be using unix time in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872690] Re: sort by date broken
The screenshot you added there doesn't show a bug though? Nautilus sorts folders firsts and then files, is that was is creating the confusion for you? -- 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/1872690 Title: sort by date broken Status in nautilus package in Ubuntu: Incomplete Bug description: Version: 1:3.36.1.1-1ubuntu2 Sort by date appears using the text on the screen for the sort. The result is that things done today are in the middle of the list instead of at the top/bottom. It should be using unix time in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873351] Re: On two monitors configuration Super-S and search for app cut off
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 Thank you for your bug report. Do you use vertical stacking? It seems similar to bug #1869571 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1869571 Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873351 Title: On two monitors configuration Super-S and search for app cut off Status in gnome-control-center package in Ubuntu: New Bug description: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870161] Re: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface
Unfortunately the issue is back. With no action from my side (software or plugin installation or update). It was perfectly fine after https://bugzilla.mozilla.org/show_bug.cgi?id=1627689#c2 - from 2020-04-09 to 2020-04-14. But today I just had those crashes again. Reproducible after restarting the browser (clean history, cookies), even in --safe-mode. https://crash- stats.mozilla.org/report/index/4cae681d-1453-496b-8303-2aeff0200415 This related bug report was reported upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1627689 ** Bug watch added: Mozilla Bugzilla #1627689 https://bugzilla.mozilla.org/show_bug.cgi?id=1627689 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870161 Title: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface Status in firefox package in Ubuntu: Fix Released Bug description: Ubuntu: 19.10 Firefox: 74.0+build3-0ubuntu0.19.10.1 Since 2020.03.31 tabs in Firefox started to crash regularly on some websites (mainly Vbulletin and phpBB forums). This happens also in --safe-mode. stderr output (just this one line): [GFX1-]: DrawTargetCairo::Snapshot with bad surface 0x7efdd6d99b00, context 0x7efdd5cba000, status 0 When trying to reload tabs they keep crashing, but after like 10-20 retries they display properly and continue to work fine. Example of a website that regularly crashes Firefox: https://aryion.com/forum/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
By any chance is "Mouse Keys" enabled? To check, go to the "Settings" application and look under the "Universal Access" tab. In that tab there is a "Mouse Keys" option under "Pointing & Clicking". If this is enabled, please disable it and see if that restores use of your numeric keypad. -- 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/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 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-shell/+bug/1872198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870161] Re: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface
I have reviewed my "about:support" contents and found preference "gfx.canvas.azure.backends" modified to "cairo" (from default "skia"). Toggling this entry between those two values (and restarting the browser) seems to fix/reproduce the issue 100% of the time. I also had "gfx.content.azure.backends" set alike, but changing this does not seem to have any negative effect. So with both set to "skia" the issue seems solved for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870161 Title: Tabs in Firefox 74.0 crash on some websites: [GFX1-]: DrawTargetCairo::Snapshot with bad surface Status in firefox package in Ubuntu: Fix Released Bug description: Ubuntu: 19.10 Firefox: 74.0+build3-0ubuntu0.19.10.1 Since 2020.03.31 tabs in Firefox started to crash regularly on some websites (mainly Vbulletin and phpBB forums). This happens also in --safe-mode. stderr output (just this one line): [GFX1-]: DrawTargetCairo::Snapshot with bad surface 0x7efdd6d99b00, context 0x7efdd5cba000, status 0 When trying to reload tabs they keep crashing, but after like 10-20 retries they display properly and continue to work fine. Example of a website that regularly crashes Firefox: https://aryion.com/forum/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866088] Re: Problems with the Dock setting of "Show on" in the Appearance tab
Mh, i think this is more a g-c-c issue than the dock. I would prefer the `multi-monitor` key to be disabled when a specific monitor is selected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1866088 Title: Problems with the Dock setting of "Show on" in the Appearance tab Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I use a laptop with external monitor in a dual display set-up. The "Screen Display" tab of Settings application correctly shows: Display 1 as the built-in display Display 2 as the external monitor If I go to the new "Appearance" tab I see that the Dock is set to display on the Built-in display but it is actually being displayed on the external monitor. If I change this setting to display on the external monitor it displays on the laptop's built-in display. Once set to "All displays" the setting can not be unset and the dock insists on being displayed on both the laptop's built-in display and the external monitor. I used the Dconf editor to set org.gnome.shell.extensions.dash-to-dock.multi-monitor to off to correct the problem although the settings application again shows that the dock is being displayed on the built-in display when in fact it is being shown on the external monitor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 4 15:20:47 2020 InstallationDate: Installed on 2019-05-17 (292 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-11-08 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1866088/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872690] Re: sort by date broken
I am seeing it right now in my home folder (image attached). » echo $LANG en_US.UTF-8 ** Attachment added: "Here's the issue in my home folder (bottom file is not sorted properly)" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+attachment/5355769/+files/Screenshot%20from%202020-04-16%2016-43-22.png -- 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/1872690 Title: sort by date broken Status in nautilus package in Ubuntu: Incomplete Bug description: Version: 1:3.36.1.1-1ubuntu2 Sort by date appears using the text on the screen for the sort. The result is that things done today are in the middle of the list instead of at the top/bottom. It should be using unix time in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873354] [NEW] Application icons don't show when external monitor connected
Public bug reported: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET79WW (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236PA8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET79WW(1.49):bd09/05/2016:svnLENOVO:pn4236PA8:pvrThinkPadT420:rvnLENOVO:rn4236PA8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4236PA8 dmi.product.version: ThinkPad T420 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "screenshot of application icons" https://bugs.launchpad.net/bugs/1873354/+attachment/5355750/+files/screenshot.png -- 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/1873354 Title: Application icons don't show when external monitor connected Status in xorg package in Ubuntu: New Bug description: If I connect an external display to my Lenovo Thinkpad T420 via display port (laptop screen main display) and click the Applications icon in the dock, I see a brief animation and then tiny little icons appear for a split second before vanishing. The application icons appear as normal if I disconnect my external display. I've attached a screenshot which I managed to take just as the tiny icons were vanishing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:24:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T420 [17aa:21ce] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 4236PA8 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO
[Desktop-packages] [Bug 1872690] Re: sort by date broken
Thank you for your bug report. What locale do you use? On what folder do you see the issue? Does it happen in /var/log for example?. I can't confirm the issue here on an uptodate focal installation ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1872690 Title: sort by date broken Status in nautilus package in Ubuntu: Incomplete Bug description: Version: 1:3.36.1.1-1ubuntu2 Sort by date appears using the text on the screen for the sort. The result is that things done today are in the middle of the list instead of at the top/bottom. It should be using unix time in the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872073] Re: firefox can't access internet after libgd3 update to new version 2.2.5-4ubuntu 0.4 linux mint tricia bionic
It turns out if I turn off the umatrix extension, firefox works again. So must be conflict between umatrix and libgd3. Chromium works fine with all the extensions I have installed. But yes. I have to turn off umatrix extension to use firefox under libgd3. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1872073 Title: firefox can't access internet after libgd3 update to new version 2.2.5-4ubuntu 0.4 linux mint tricia bionic Status in firefox package in Ubuntu: New Status in libgd2 package in Ubuntu: Incomplete Bug description: Had to install chromium which works fine. Firefox worked fine before the 2 updates on April 4, 2020. Maybe coincidence. I don't know. Linux Mint Tricia. Bionic. Linux Mint 19.3 Cinnamon 4.4.8 Linux Kernel 5.3.0-46-generic System:Host: kathy-Parrot Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Desktop System: Google product: Parrot v: 1.0 serial: Chassis: type: 3 serial: Mobo: Google model: Parrot v: 1.0 serial: BIOS: coreboot v: 4.0-6588-g4acd8ea-dirty date: 09/04/2014 CPU: Topology: Dual Core model: Intel Celeron 1007U bits: 64 type: MCP arch: Ivy Bridge rev: 9 L2 cache: 2048 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 5986 Speed: 798 MHz min/max: 800/1500 MHz Core speeds (MHz): 1: 798 2: 798 Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0156 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 19.2.8 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20 Sound Server: ALSA v: k5.3.0-46-generic Network: Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter vendor: Foxconn driver: ath9k v: kernel port: 0400 bus ID: 01:00.0 chip ID: 168c:0034 IF: wlp1s0 state: up mac: Device-2: Broadcom and subsidiaries NetLink BCM57785 Gigabit Ethernet PCIe vendor: Acer Incorporated ALI driver: tg3 v: 3.137 port: 0400 bus ID: 02:00.0 chip ID: 14e4:16b5 IF: enp2s0f0 state: down mac: Drives:Local Storage: total: 134.12 GiB used: 24.94 GiB (18.6%) ID-1: /dev/sda vendor: SanDisk model: SSD U100 16GB size: 14.91 GiB speed: 3.0 Gb/s serial: ID-2: /dev/sdb type: USB vendor: PNY model: USB 3.0 FD size: 119.21 GiB serial: Partition: ID-1: / size: 14.62 GiB used: 11.33 GiB (77.5%) fs: ext4 dev: /dev/sda1 Sensors: System Temperatures: cpu: 45.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 1: deb https: //dl.winehq.org/wine-builds/ubuntu/ bionic main Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //packages.linuxmint.com tricia main upstream import backport 2: deb http: //archive.ubuntu.com/ubuntu bionic main restricted universe multiverse 3: deb http: //archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse 4: deb http: //archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ bionic partner Info: Processes: 199 Uptime: 36m Memory: 3.78 GiB used: 2.10 GiB (55.4%) Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Client: Unknown python3.6 client inxi: 3.0.32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873351] [NEW] On two monitors configuration Super-S and search for app cut off
Public bug reported: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description:Ubuntu Focal Fossa (development branch) Release:20.04 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "IMG_1842.jpg" https://bugs.launchpad.net/bugs/1873351/+attachment/5355735/+files/IMG_1842.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873351 Title: On two monitors configuration Super-S and search for app cut off Status in gnome-control-center package in Ubuntu: New Bug description: Please see attached. With two monitors configuration (Lenovo ThinkPad P1 Gen 2 laptop running Ubuntu 20.04 beta) when user presses on Super button and try to search for any app, the display shows cut off icons Pls fix before release! Description: Ubuntu Focal Fossa (development branch) Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873316] Re: bluetooth
** 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/1873316 Title: bluetooth Status in xorg package in Ubuntu: New Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 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 2:1.19.6-1ubuntu4.3 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: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1873316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873346] [NEW] Gnome Files icon bug focal
Public bug reported: Gnome Files icon is showing on the light background in gnome-shell, but all other icons on transparent background. See attached screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 22:48:17 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Снимок экрана от 2020-04-16 22-46-58.png" https://bugs.launchpad.net/bugs/1873346/+attachment/5355726/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-04-16%2022-46-58.png ** Description changed: - Gnome Files icon is showing on the light background, but all other icons - on transparent background. See attached screen + Gnome Files icon is showing on the light background in gnome-shell, but + all other icons on transparent background. See attached screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 22:48:17 2020 DisplayManager: gdm3 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ru_RU.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=ru_RU.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell 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 in Ubuntu. https://bugs.launchpad.net/bugs/1873346 Title: Gnome Files icon bug focal Status in gnome-shell package in Ubuntu: New Bug description: Gnome Files icon is showing on the light background in gnome-shell, but all other icons on transparent background. See attached screen ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 22:48:17 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1873346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873348] [NEW] Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured
Public bug reported: - Enable fractional scaling toggle on x11 - Scale a monitor of 200%, 300%... (any integer value) - Play a game or a video fullscreen - The monitors are reconfigured causing a black window This is expected in fractional scaling to make direct-rendering to work properly, but not when the monitor is not scaled or scaled or with an integer value ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Tags: xrandr-scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873348 Title: Fullscreen videos and direct-rendering windows cause monitors with integer-scaling to be reconfigured Status in mutter package in Ubuntu: In Progress Bug description: - Enable fractional scaling toggle on x11 - Scale a monitor of 200%, 300%... (any integer value) - Play a game or a video fullscreen - The monitors are reconfigured causing a black window This is expected in fractional scaling to make direct-rendering to work properly, but not when the monitor is not scaled or scaled or with an integer value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873316] [NEW] bluetooth
You have been subscribed to a public bug: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 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 2:1.19.6-1ubuntu4.3 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: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- bluetooth https://bugs.launchpad.net/bugs/1873316 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 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 exactly same problem ubuntu 18.04.03 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
I just found the issue second ago. It is related to SNAP_REEXEC behavior. The idea is to run snap from snap_core installed from snap. If you have system snap installed it will be reexec'd from snap core. To disable it you need to change the source. Just run this before compilation and you will be ok: sed -i 's/!osutil.GetenvBool(reExecKey, true)/true/' snapd-*/cmd/cmd_linux.go -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856251] Re: Going from apps overview screen to fullscreen'd app causes flash
Do you have any fractional scaling enabled? -- 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/1856251 Title: Going from apps overview screen to fullscreen'd app causes flash Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I like some things like terminal to be fullscreen (F11). I've noticed that whenever I look at what apps are running by tapping the Super key and then go to any app that is in fullscreen mode (by either hit the Super key again to give focus back to the app OR click the app I'd like to focus on), there is a flash of the background. This is 100% reproducible for me. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 16:10:26 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-11 (92 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-24 (79 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873052] Re: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #904 https://gitlab.gnome.org/GNOME/mutter/issues/904 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/904 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873052 Title: GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
This bug was fixed in the package jackd2 - 1.9.12~dfsg-2ubuntu2 --- jackd2 (1.9.12~dfsg-2ubuntu2) focal; urgency=medium * debian/patches/CVE-2019-13351.patch: - Set fSocket to -1 after close on an error to prevent a double close, fix CVE-2019-13351 (lp: #1833479) -- Sebastien Bacher Thu, 16 Apr 2020 10:21:43 +0200 ** Changed in: jackd2 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in alsa-plugins package in Ubuntu: New Status in jackd2 package in Ubuntu: Fix Released Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1833479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
This bug was fixed in the package wpa - 2:2.9-1ubuntu4 --- wpa (2:2.9-1ubuntu4) focal; urgency=medium * debian/patches/git_realtek_macrand.patch: - backport an upstream patch to fix issues with some realtek cards when MAC address randomization is enabled (lp: #1867908) -- Sebastien Bacher Wed, 15 Apr 2020 10:08:07 +0200 ** Changed in: wpa (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Released Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device
test pulseaudio (1:13.99.1-1ubuntu3) fixed my problem. -- 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/1872970 Title: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio package in Fedora: Unknown Bug description: I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 sound card. downgrade pulseaudio_13.0-1ubuntu1.1 sound work. https://bugzilla.redhat.com/show_bug.cgi?id=1818883 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/ please build next pulseaudio include patch, ucm: fix the port / ucm device activation on boot alsa sink/source: fix the mixer initialization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
The internal microphone is not working for System76 Gazelle gazp9 which is a Clevo laptop under the hood. Ubuntu 18.04.4 LTS bionic I think I did a Zoom interview a few years ago, and it worked, but the microphone hasn't worked for the last few months. This is an old laptop with two input jacks, one for microphone, and one for head phones. My headphones have a combo mike in the cord. Maybe if I had a separate microphone, it would work. Or if I had a splitter. But when nothing is plugged into the mike jack, the internal microphone does not work. The input settings have an orange bar that is supposed to oscillate if it picks up sound, but nothing is shown on that when I speak. If I put my combo cable in that jack, it briefly oscillates, but that's like a fluke. Something is live there - maybe the device is recognized - but it's not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872871] Re: Xdg-Shell Stable not working properly
SOLVED (code-error and not an actual issue (although perhaps the window-
selector glitching-out with improper code should be addressed)):
From
(https://www.reddit.com/r/vulkan/comments/g1ikb0/gnome_wayland_not_working_with_vulkan_on_debian/):
Thanks, I tried putting wl_proxy_marshal((struct wl_proxy *)
xdg_surface, XDG_SURFACE_ACK_CONFIGURE, serial);
(xdg_surface_ack_configure() equivalent) before every vkQueueSubmit (I
know that you meant to put the ack in response to events, but while
trying to make things work, I thought that it needed to be before every
vkQueueSubmit), and the window-menu started working, but events weren't
triggering. I then discovered that I needed to call
wl_display_roundtrip() every frame and only call
xdg_surface_ack_configure after certain events (xdg_surface_listener's
and xdg_toplevel_listener's configure events). This is what I ended-up
with in my draw loop:
retStatus = wl_display_flush(display);
if(retStatus == -1) {
//TODO: use poll() to wait until display fd is writable
again, and call wl_display_flush again
exit(1);
}
wl_display_roundtrip(display); //blocks
submitInfos[0].pCommandBuffers = [imageIndex];
vkQueueSubmit(graphicsQueue, 1, submitInfos,
fence);
wl_display_dispatch_pending(display);
** Changed in: gnome-desktop3 (Ubuntu)
Status: New => Invalid
** Changed in: gnome-desktop3 (Ubuntu)
Assignee: (unassigned) => a b (the-coder)
** Changed in: gnome-desktop3 (Debian)
Assignee: (unassigned) => a b (the-coder)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop3 in Ubuntu.
https://bugs.launchpad.net/bugs/1872871
Title:
Xdg-Shell Stable not working properly
Status in gnome-desktop3 package in Ubuntu:
Invalid
Status in gnome-desktop3 package in Debian:
New
Bug description:
I'm trying to run a simple Vulkan program on Debian Testing (GNOME
desktop using Mesa Vulkan implementation), but it seems like there
might be an issue with GNOME, since none of the xdg_shell (stable)
callbacks seem to be working and resizing the window doesn't work
(although the window is rendering correctly at least). Swapping to
another window, and then going to the list of windows to choose from
causes the window's preview (on the list of windows) to be partially-
hidden behind other windows and be unclickable (note that this is
GNOME's window-selection screen(under activities), not switching tabs
like on Windows). None of the Wayland (including xdg-shell) functions
are returning errors and Vulkan validation layers are not reporting
any warnings. is anyone else experiencing this and/or knows a solution
to this? Could this be because I'm using xdg-shell stable
(xdg_wm_base), which was released relatively recently? I'm using a .h
file (generated from the xdg-shell xml on my system) to define the
interfaces (not a static or dynamic library), but I believe that this
is correct, and that there is no xdg-shell dynamic library to load. I
was using wl_shell before this, and the window-selection screen worked
properly while using wl_shell.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1872871/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Alexey I'm having the same experience as you. It's uncanny, feels like something obvious is missing. Not sure how it's working for Kevin above. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873326] [NEW] Icons in the appindicator are too small
Public bug reported: After a recent update, the icons in the appindicator became too small. The screenshot is attached to demonstrate the issue. This bug looks the same as one of the previous bugs which has been fixed quite long ago: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730406 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:20:00 2020 InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Comparison of screensots of the appindicator with several apps running in 19.10 and in 20.04" https://bugs.launchpad.net/bugs/1873326/+attachment/5355677/+files/gnome-shell-extension-appindicator_eoan-vs-focal.png ** Description changed: After a recent update, the icons in the appindicator became too small. The screenshot is attached to demonstrate the issue. - This bug looks the same as on of the previous bugs which has been fixed quite long ago: + This bug looks the same as one of the previous bugs which has been fixed quite long ago: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730406 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:20:00 2020 InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator 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-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1873326 Title: Icons in the appindicator are too small Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: After a recent update, the icons in the appindicator became too small. The screenshot is attached to demonstrate the issue. This bug looks the same as one of the previous bugs which has been fixed quite long ago: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1730406 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 21:20:00 2020 InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator 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-appindicator/+bug/1873326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872275] Re: Orange indicator dot is rendered over text in thr app grid
Related upstream Bug: https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/2234 also (from the upstream bug report): "This issue happens on 1366x786 screen and not on 1920x1080". -- 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/1872275 Title: Orange indicator dot is rendered over text in thr app grid Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: This bug is an UI which is blocking the text from visual sight of user and hence producing a bad User experience. Steps to reproduce: 1- Click on 9 dots at bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Notice any app icon carefully and observe if it is showing up similar to what i have attached in the screenshot in this bug. Things to notice: (a) Bottom padding of icon selector (not equal to the top one). (b) Position of the orange indicator which shows that an instance of app is running. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:28:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867613] Re: Ubuntu dock does not allow drag and move icons at bottom of screen
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu20.04.4 --- gnome-shell-extension-ubuntu-dock (67ubuntu20.04.4) focal; urgency=medium [ Marco Trevisan (Treviño) ] * appIcon: Don't show the ShowAppsIcon popup in ubuntu-dock (LP: #1869635) * dash: Fix icons DnD when in horizontal mode and when the icons are using a scrolled view (LP: #1867763, #1867613) * stylesheet: Define width for top/bottom drop placeholder * fixed various JS warnings and errors [ jesusignacio ] * Updated ES translation: show mounted devices + show trash icon [ mars ] * Update Simplified Chinese translation [ Pavel Dvořák ] * Update cs.po [ Robert Mader ] * Use new convenience function to open settings -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 07:48:51 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867613 Title: Ubuntu dock does not allow drag and move icons at bottom of screen Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Ubuntu 20.04 daily development branch @ 16/3/2020 After a clean install daily at 14/3/2020 the ubuntu dock does not allow drag and move icons anymore with the dock placed at bottom you can still mouseclick and hold the icon, but it does not make space between other icons to release starting an application still showing the icon, and add to favorites still works the dock placed left or right it works better ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 12:31:30 2020 InstallationDate: Installed on 2020-03-14 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868529] Re: Stretched image previews on desktop
This bug was fixed in the package gnome-shell-extension-desktop-icons - 20.04.0-1 --- gnome-shell-extension-desktop-icons (20.04.0-1) unstable; urgency=medium * New upstream (bugfix) release - Fixed stretched thumbnails (LP: #1868529) - Honor the "don't show thumbnails" setting - Shows the hand cursor when using "single click" option - Clear file selection after a desktop refresh * debian/patches: cherry-pick new translations from git -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 09:10:08 +0200 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Fix Committed => Fix Released -- 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/1868529 Title: Stretched image previews on desktop Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Bug description: After upgrade to 20.04 desktop previews of pictures and documents became stretched. The regular previews in Nautilus have normal sizes. See attached pic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 23 11:44:13 2020 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.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/gnome-shell-extension-desktop-icons/+bug/1868529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867763] Re: gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL)
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu20.04.4 --- gnome-shell-extension-ubuntu-dock (67ubuntu20.04.4) focal; urgency=medium [ Marco Trevisan (Treviño) ] * appIcon: Don't show the ShowAppsIcon popup in ubuntu-dock (LP: #1869635) * dash: Fix icons DnD when in horizontal mode and when the icons are using a scrolled view (LP: #1867763, #1867613) * stylesheet: Define width for top/bottom drop placeholder * fixed various JS warnings and errors [ jesusignacio ] * Updated ES translation: show mounted devices + show trash icon [ mars ] * Update Simplified Chinese translation [ Pavel Dvořák ] * Update cs.po [ Robert Mader ] * Use new convenience function to open settings -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 07:48:51 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867763 Title: gnome-shell crashed with SIGABRT: assertion failure in st_bin_destroy: assertion failed: (priv->child == NULL) Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/d24a5ac63e9b00cde36f6c46ecbcc5b20442be90 https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 --- I do not know what is happened, just a reporter appeared. But 10 minutes ago when I came to my computer after 5 minutes, it was restarted. It should not be restarted, just should be sleep or locked. However I do not know even this issue related with this report or not. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 13:32:09 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-03-13 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200312) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869635] Re: the menu "Dash to Dock Settings" is visible
This bug was fixed in the package gnome-shell-extension-ubuntu-dock - 67ubuntu20.04.4 --- gnome-shell-extension-ubuntu-dock (67ubuntu20.04.4) focal; urgency=medium [ Marco Trevisan (Treviño) ] * appIcon: Don't show the ShowAppsIcon popup in ubuntu-dock (LP: #1869635) * dash: Fix icons DnD when in horizontal mode and when the icons are using a scrolled view (LP: #1867763, #1867613) * stylesheet: Define width for top/bottom drop placeholder * fixed various JS warnings and errors [ jesusignacio ] * Updated ES translation: show mounted devices + show trash icon [ mars ] * Update Simplified Chinese translation [ Pavel Dvořák ] * Update cs.po [ Robert Mader ] * Use new convenience function to open settings -- Marco Trevisan (Treviño) Thu, 16 Apr 2020 07:48:51 +0200 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869635 Title: the menu "Dash to Dock Settings" is visible Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: When the user performs a right-button mouse click on the "Show Applications" button of the Ubuntu Dock then a "Dash to Dock Settings" menu option appears as shown in the attached image. Normally, this menu option is only available on the original "Dash to Dock" GNOME shell extension used as the basis for the Ubuntu Dock and it should not be visible or functional on the Ubuntu Dock itself. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 30 02:31:58 2020 InstallationDate: Installed on 2020-02-12 (46 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-03-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1869635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873321] [NEW] The Show Applications button is unclickable in the corner and along its bottom edge
Public bug reported: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button is unclickable in the corner and along its bottom edge Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873320] [NEW] PAM Messages (as swipe finger one) are barely visible in the new lockscreen
Public bug reported: See https://imgur.com/ZU8fh5V.png ** Affects: yaru-theme (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: yaru-theme (Ubuntu Focal) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: yaru-theme (Ubuntu Focal) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: 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/1873320 Title: PAM Messages (as swipe finger one) are barely visible in the new lockscreen Status in yaru-theme package in Ubuntu: In Progress Status in yaru-theme source package in Focal: In Progress Bug description: See https://imgur.com/ZU8fh5V.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1873320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
