[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry
** Changed in: mutter (Ubuntu) Milestone: ubuntu-20.03 => ubuntu-20.04 -- 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/1862308 Title: Desktop wallpaper is slightly blurry Status in mutter package in Ubuntu: In Progress Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34. Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 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 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/mutter/+bug/1862308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799266] Re: gnome-shell uses high CPU when simply moving windows
** Changed in: gnome-shell (Ubuntu) Milestone: ubuntu-20.03 => None -- 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/1799266 Title: gnome-shell uses high CPU when simply moving windows Status in Mutter: Fix Released Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gjs source package in Bionic: Fix Released Status in gjs source package in Cosmic: Fix Released Status in gjs source package in Disco: Fix Released Bug description: After doing a stock install Ubuntu 18.04.1 LTS on an imac 27" 2010 8G ram, Intel® Core™ i7 CPU 870 @ 2.93GHz × 8 Simply moving a window around on the screen increases the cpu usage by gnome-shell to 44%. When displaying a movie, totem takes 10%, gnome-shell takes 22%. etc etc System:Host: oldie Kernel: 4.15.0-36-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Machine: Device: desktop System: Apple product: iMac11 3 v: 1.0 serial: N/A Mobo: Apple model: Mac-F2238BAE v: iMac11 3 serial: N/A UEFI: Apple v: IM112.88Z.0057.B01.1112090906 date: 12/09/11 CPU: Quad core Intel Core i7 870 (-MT-MCP-) cache: 8192 KB clock speeds: max: 2927 MHz 1: 1271 MHz 2: 1206 MHz 3: 1374 MHz 4: 1271 MHz 5: 1377 MHz 6: 1266 MHz 7: 1693 MHz 8: 1279 MHz Graphics: Card: Advanced Micro Devices [AMD/ATI] Broadway PRO [Mobility Radeon HD 5850] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 2560x1440@59.95hz OpenGL: renderer: AMD JUNIPER (DRM 2.50.0 / 4.15.0-36-generic, LLVM 6.0.0) version: 3.3 Mesa 18.0.5 Audio: Card-1 Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel Card-2 Advanced Micro Devices [AMD/ATI] Juniper HDMI Audio [Radeon HD 5700 Series] driver: snd_hda_intel Sound: Advanced Linux Sound Architecture v: k4.15.0-36-generic Network: Card-1: Broadcom Limited NetXtreme BCM5764M Gigabit Ethernet PCIe driver: tg3 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: c4:2c:03:30:ce:8e Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express) driver: ath9k IF: wls1 state: down mac: d8:30:62:67:2a:19 Drives:HDD Total Size: 2500.5GB (38.0% used) ID-1: /dev/sda model: WDC_WD1001FALS size: 1000.2GB ID-2: USB /dev/sdb model: MK1059GSM size: 1000.2GB ID-3: USB /dev/sdd model: Elements_10B8 size: 500.1GB Partition: ID-1: / size: 226G used: 125G (58%) fs: ext4 dev: /dev/sda2 ID-2: /home size: 701G used: 876M (1%) fs: btrfs dev: /dev/sda4 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: 936 Info: Processes: 342 Uptime: 3:07 Memory: 2087.3/7967.4MB Client: Shell (bash) inxi: 2.3.56 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 19:09:59 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-10-22 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- 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/1862308 Title: Desktop wallpaper is slightly blurry Status in mutter package in Ubuntu: In Progress Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34. Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 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 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/mutter/+bug/1862308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"
Remark: In Ubuntu 19.04, if the user/domain/password is not piped, `gio mount` requests the `user/domain/password`: `$ gio mount smb://192.168.178.1/Fritz7490` `Password required for share fritz7490 on 192.168.178.1 `User [SessionUserName]: NewUserIfDifferent `Domain [WORKGROUP]: NewDomainIfDifferent `Password: PassWord -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872286 Title: gio - cifs mount smb not possible "Location is not mountable" Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Triaged Bug description: 1) Release $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2) Package $ apt-cache policy libglib2.0-bin libglib2.0-bin: Installed: 2.64.1-1 Candidate: 2.64.1-1 Version table: *** 2.64.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) Expected to happen The path should be mounted at /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/ 4) What happened instead: Error Message: gio: smb://192.168.178.1/PathName/: Location is not mountable 5) Long description / explanation Since some years, I mount a Windows drive with gio mount smb://192.168.178.1/PathName After upgrading from 19.04 to 20.04 beta, this does not work any more, I get the error message gio: smb://192.168.178.1/PathName/: Location is not mountable ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libglib2.0-bin 2.64.1-1 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: XFCE Date: Sun Apr 12 12:43:53 2020 InstallationDate: Installed on 2019-02-17 (420 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: glib2.0 UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1872286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872162] Re: crash report fail to submit
** Package changed: firefox (Ubuntu) => apport (Ubuntu) -- 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/1872162 Title: crash report fail to submit Status in apport package in Ubuntu: New Bug description: Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5 years before). Though, all crash reports failed to submit. My firefox crash report submit.log reads: [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect to server [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect to server [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect to server [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect to server [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect to server [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect to server [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect to server [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect to server [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect to server [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect to server [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect to server [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect to server [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect to server [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Tags added: performance -- 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 1872258] Re: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored"
** Changed in: gnome-software (Ubuntu) Status: Triaged => Fix Committed -- 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 Committed 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 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: Triaged Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751269] Re: Compiz related colour-swapping bug (Endianness bug somewhere)
** Summary changed: - Compiz related bug (Endianness bug somewhere) + Compiz related colour-swapping bug (Endianness bug somewhere) ** Package changed: xorg (Ubuntu) => compiz (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/1751269 Title: Compiz related colour-swapping bug (Endianness bug somewhere) Status in compiz package in Ubuntu: New Bug description: Hello, I suspect a endianness problem in this BigEndian Machine (Apple PowerBook G4 with ATI Radeon Mobility 9700). The same architecture (bigEndian) shows no this specific issue on PowerMac G5 Quad with PCI-Express ATI Radeon HD4670 with VGA BIOS (not powerpc flashed card). The problem seems to be a screen changing resolution or similar having Compiz activated. If I switch the screen resolution on this laptop, the garbage on the screen is more visible than using NO COMPOSITE Marco Mate Display Manager. The problem is enhanced using a second monitor attached to a DVI connector on this laptop. Can be easly reproduced. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-powerpc-smp 4.4.98 Uname: Linux 4.4.0-116-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.15 Architecture: powerpc CurrentDesktop: MATE Date: Fri Feb 23 14:01:47 2018 InstallationDate: Installed on 2018-02-21 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release powerpc (20160719) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1751269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752728] Re: My pc is going in blank after sleep and nothing works
** Package changed: xorg (Ubuntu) => 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/1752728 Title: My pc is going in blank after sleep and nothing works Status in Ubuntu: New Bug description: My pc is going in blank after sleep and nothing works ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 1 17:12:11 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Subsystem: Dell Device [1028:0774] NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07c0] InstallationDate: Installed on 2017-09-27 (155 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Alienware Alienware 15 R3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=55e321af-6860-4c50-a132-9e8fe6024cd7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.0:bd09/14/2017:svnAlienware:pnAlienware15R3:pvr1.2.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.version: 1.2.0 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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/+bug/1752728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()
Tracking in: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a ** Description changed: + https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf + https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a + + --- + nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] + Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD - Bus 001 Device 003: ID 8087:0029 Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD + Bus 001 Device 003: ID 8087:0029 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: - __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 - __GI_abort () at abort.c:79 - ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so - ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so + __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 + __GI_abort () at abort.c:79 + ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so + ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: - + dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: - + version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush()
[Desktop-packages] [Bug 1872888] Re: /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1872888 Title: /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872594] Re: Ubuntu logo shifts upward about 1px when the purple login screen appears
** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Changed in: plymouth (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/1872594 Title: Ubuntu logo shifts upward about 1px when the purple login screen appears Status in gnome-shell package in Ubuntu: Triaged Status in plymouth package in Ubuntu: Triaged Bug description: Ubuntu logo shifts upward about 1px when the purple login screen appears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() from
** Summary changed: - Xorg crashed with SIGABRT in __GI_raise() + Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() from ** Summary changed: - Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() from + Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() ** Information type changed from Private to Public ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872887] Re: /usr/bin/Xwayland:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 ** This bug has been marked a duplicate of bug 1871959 Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush() from dri2_make_current() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1872887 Title: /usr/bin/Xwayland:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872888] [NEW] /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1872888 Title: /usr/lib/xorg/Xorg:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872887] [NEW] /usr/bin/Xwayland:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush
*** This bug is a duplicate of bug 1871959 *** https://bugs.launchpad.net/bugs/1871959 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1872887 Title: /usr/bin/Xwayland:6:__GI_raise:__GI_abort:_iris_batch_flush:iris_fence_flush:st_glFlush Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1859774 Title: Full screen window becomes "small" in the upper left of the screen... Status in gnome-shell package in Ubuntu: Expired Bug description: This happens with a number of different programs, so I suspect it is a window manager bug. The best way to describe it is with a screen shot. The only responsive part of the screen is the small window in the upper left. You can hit the little maximize box and it goes back to full screen okay, but after a while it comes back to this. It can be annoying, because sometimes you can't quickly see what happened to the title bar. I'm using Ubuntu 19.10. This has been happening for about a week. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872879] Re: update to land on ff-main before release
** Description changed: Right now we are trying to update wslu 2.3.2 on focal to 2.3.6 (2.3.6-0ubuntu1) to address some critical issues reported on Launchapad before the focal release rather than SRU now: - * Upstream update to 2.3.6 to address critical issues (LP: #1871986) - - wslupath manpage update - - fixes that imported distro cannot be properly handled by baseexec_gen - - fix an issue in handling dirty output in regenerate baseexec - - fix an issue in generating ~/.config/baseexec - - wslusc: fix an issue that will cause generated shortcut cannot be opened - for some users - * debian/wsl-integration.sh: Fix issue that space in username breaks - wsl-integration.sh. (LP: #1869878) - * debian/wsl-integration.sh: Use /tmp folder for system users who do not have - $HOME. (LP: #1859509) - * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right - variable at the end of script. (LP: #1857426) + * Upstream update to 2.3.6 to address critical issues (LP: #1871986) + - wslupath manpage update + - fixes that imported distro cannot be properly handled by baseexec_gen + - fix an issue in handling dirty output in regenerate baseexec + - fix an issue in generating ~/.config/baseexec + - wslusc: fix an issue that will cause generated shortcut cannot be opened for some users + * debian/wsl-integration.sh: Fix issue that space in username breaks wsl-integration.sh. (LP: #1869878) + * debian/wsl-integration.sh: Use /tmp folder for system users who do not have $HOME. (LP: #1859509) + * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right variable at the end of script. (LP: #1857426) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1872879 Title: update to land on ff-main before release Status in wslu package in Ubuntu: New Bug description: Right now we are trying to update wslu 2.3.2 on focal to 2.3.6 (2.3.6-0ubuntu1) to address some critical issues reported on Launchapad before the focal release rather than SRU now: * Upstream update to 2.3.6 to address critical issues (LP: #1871986) - wslupath manpage update - fixes that imported distro cannot be properly handled by baseexec_gen - fix an issue in handling dirty output in regenerate baseexec - fix an issue in generating ~/.config/baseexec - wslusc: fix an issue that will cause generated shortcut cannot be opened for some users * debian/wsl-integration.sh: Fix issue that space in username breaks wsl-integration.sh. (LP: #1869878) * debian/wsl-integration.sh: Use /tmp folder for system users who do not have $HOME. (LP: #1859509) * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right variable at the end of script. (LP: #1857426) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1872879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872879] Re: update to land on ff-main before release
I concur on the urgency of these fixes at this late date. wslu is a distinguishing feature of Ubuntu on WSL. It is important to address these bugs in 20.04. callmepk is the upstream author of wslu so I have confidence in his patches. I am running a build from callmepk's branch and have not encountered any issues in my testing. We will continue testing as this moves through the review process. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1872879 Title: update to land on ff-main before release Status in wslu package in Ubuntu: New Bug description: Right now we are trying to update wslu 2.3.2 on focal to 2.3.6 (2.3.6-0ubuntu1) to address some critical issues reported on Launchapad before the focal release rather than SRU now: * Upstream update to 2.3.6 to address critical issues (LP: #1871986) - wslupath manpage update - fixes that imported distro cannot be properly handled by baseexec_gen - fix an issue in handling dirty output in regenerate baseexec - fix an issue in generating ~/.config/baseexec - wslusc: fix an issue that will cause generated shortcut cannot be opened for some users * debian/wsl-integration.sh: Fix issue that space in username breaks wsl-integration.sh. (LP: #1869878) * debian/wsl-integration.sh: Use /tmp folder for system users who do not have $HOME. (LP: #1859509) * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right variable at the end of script. (LP: #1857426) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1872879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling
My proposed branch (for integer scaling cases) was closed in favor of https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1124 which is in mutter 3.36.1 already. -- 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/1825625 Title: Some apps appear blurry with framebuffer scaling Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Microsoft VScode bug: https://github.com/Microsoft/vscode/issues/72759 Chromium bug?: https://bugs.chromium.org/p/chromium/issues/detail?id=578890 Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry
** Summary changed: - Desktop wallpaper is slightly blurry in Gnome 3.34 + Desktop wallpaper is slightly blurry -- 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/1862308 Title: Desktop wallpaper is slightly blurry Status in mutter package in Ubuntu: Triaged Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34. Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 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 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 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/mutter/+bug/1862308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Summary changed: - Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen + 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870776] Re: No smooth scrolling on Firefox (and Chrome)
Note they are all different issues so please choose one for this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1870776 Title: No smooth scrolling on Firefox (and Chrome) Status in firefox package in Ubuntu: Incomplete Bug description: I'm on Ubuntu Beta 20.04 and I observe that smooth scrolling is not working in Firefox or Chrome, while it works well in other apps, like Nautilus/Files GNOME settings or within GNOME shell applications listing. I tried with Firefox in safe mode (so without any extension) with the same result. I also tried with a completely new GNOME user account (without any customization), with the same result. While I'm not so used to Chrome, it seems that smooth scrolling is not working with it either. Another test I did is to boot from a Fedora Workstation 32 Beta USB stick (with GNOME) and the smooth scrolling was working well in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870259] Re: firefox fullscreen display glitches with hidpi scalingb
*** This bug is a duplicate of bug 1862081 *** https://bugs.launchpad.net/bugs/1862081 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 1862081, 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 1862081 Gnome resizes framebuffer when playing fullscreen video over and over again (when using X11 fractional scaling) -- 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/1870259 Title: firefox fullscreen display glitches with hidpi scalingb Status in firefox package in Ubuntu: New Bug description: When I go on fullscreen on a video on Firefox with HIDPI scaling factors more than 100%, I get odd behavior of the fullscreen video. This behavior is not seen on Chrome, or if the scaling factor is 100%. Basically, it seems like there is some resizing of the video to a smaller window in the upper left, and when I escape fullscreen, sometimes the firefox window itself is scaled off the display. At times, this glitches a few times and eventually resets, sometimes, it stays this way. It appears to have changed behavior multiple times over the past few weeks of updates of various parts of the stack, and may just be narrowed down for me now to something repeatable. For instance sometimes I could not trigger it until I pressed volume up or volume down. Now it appears to happen just waiting for a few seconds on the running video. This is on X11, and on focal with the latest updates as of today 2020-04-01. Happy to debug more, not sure what information is useful. thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dpb1522 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 21:12:08 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-02-22 (39 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 10.10.0.1 dev wlp4s0 proto dhcp metric 600 10.10.0.0/16 dev wlp4s0 proto kernel scope link src 10.10.1.4 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2020-02-22 (39 days ago) dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET59W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET59W(1.44):bd11/25/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th
[Desktop-packages] [Bug 1870776] Re: No smooth scrolling on Firefox (and Chrome)
Which of these are you referring to with "smooth scrolling"? * Touchpads * Touch screens * Mouse wheels ** Tags added: focal ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/1870776 Title: No smooth scrolling on Firefox (and Chrome) Status in firefox package in Ubuntu: Incomplete Bug description: I'm on Ubuntu Beta 20.04 and I observe that smooth scrolling is not working in Firefox or Chrome, while it works well in other apps, like Nautilus/Files GNOME settings or within GNOME shell applications listing. I tried with Firefox in safe mode (so without any extension) with the same result. I also tried with a completely new GNOME user account (without any customization), with the same result. While I'm not so used to Chrome, it seems that smooth scrolling is not working with it either. Another test I did is to boot from a Fedora Workstation 32 Beta USB stick (with GNOME) and the smooth scrolling was working well in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825625] Re: Some apps appear blurry with framebuffer scaling
** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1825625 Title: Some apps appear blurry with framebuffer scaling Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Microsoft VScode bug: https://github.com/Microsoft/vscode/issues/72759 Chromium bug?: https://bugs.chromium.org/p/chromium/issues/detail?id=578890 Setting the framebuffer scaling (with gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']") allows the display on HiDPi to be scaled to something different than 100%/200%/300%. Which would be fine. However, the display is rendered such that most applications provide blurred display of text and graphics. This is not always the case (e.g. system settings are displayed correctly, Thunderbird and Firefox are blurred). Also the screen flickers when selection menus or resizing the windows. A black border appears around the windows where the shadow should appear. It gets removed a few seconds later but still is irritating. This issue is not urgent, just annoying. It can be worked around by removing the settings in gsetting / dconf. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 11:11:55 2019 InstallationDate: Installed on 2018-04-30 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1825625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I see a riscv64 build failure, not armhf - is that what you mean? -- 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 Committed Status in gnome-software source package in Focal: Fix Committed 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 1870991] Re: Update gnome-software to 3.36.0 for Focal
The riscv64 build failure seems to be the test timing out after 30s, but the stress test can take longer that this. -- 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 Committed Status in gnome-software source package in Focal: Fix Committed 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 1872126] Re: focal: Firefox YouTube videos full screen motion glitch/tearing
*** This bug is a duplicate of bug 1754284 *** https://bugs.launchpad.net/bugs/1754284 ** This bug has been marked a duplicate of bug 1754284 Fullscreen windows are tearing in Xorg sessions -- 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/1872126 Title: focal: Firefox YouTube videos full screen motion glitch/tearing Status in firefox package in Ubuntu: New Bug description: https://www.youtube.com/watch?v=MfL_JkcEFbE Intel® Core™ i7-8700 CPU @ 3.20GHz × 12 Mesa Intel® UHD Graphics 630 (CFL GT2) HDMI to Sony TV 1920x1080 Playing YouTube video full screen in Firefox there is some fast motion glitch/tearing. The problem does not show in chromium on same machine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi9241 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 22:05:40 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) IpRoute: default via 192.168.88.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.88.0/24 dev wlo1 proto kernel scope link src 192.168.88.109 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-I GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-IGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869122] Re: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308
** Changed in: mutter (Ubuntu) Status: Fix Committed => 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/1869122 Title: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308 Status in mutter package in Ubuntu: Fix Released Bug description: mutter 3.36.0-2ubuntu1 changelog mentions wrong bug ID: * d/p/clutter-master-clock-default-Sync-timelines-to-hardware-v.patch: - Improves smoothness and reduce input-to-output latency levels (LP: #1862308) That last line should be deleted. Actually there is no Launchpad bug for that patch. Original proposal: https://salsa.debian.org/3v1n0-guest/mutter/-/merge_requests/1/diffs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872879] [NEW] update to land on ff-main before release
Public bug reported: Right now we are trying to update wslu 2.3.2 on focal to 2.3.6 (2.3.6-0ubuntu1) to address some critical issues reported on Launchapad before the focal release rather than SRU now: * Upstream update to 2.3.6 to address critical issues (LP: #1871986) - wslupath manpage update - fixes that imported distro cannot be properly handled by baseexec_gen - fix an issue in handling dirty output in regenerate baseexec - fix an issue in generating ~/.config/baseexec - wslusc: fix an issue that will cause generated shortcut cannot be opened for some users * debian/wsl-integration.sh: Fix issue that space in username breaks wsl-integration.sh. (LP: #1869878) * debian/wsl-integration.sh: Use /tmp folder for system users who do not have $HOME. (LP: #1859509) * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right variable at the end of script. (LP: #1857426) ** Affects: wslu (Ubuntu) Importance: Critical Status: New ** Changed in: wslu (Ubuntu) Importance: Undecided => Critical ** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/381868 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1872879 Title: update to land on ff-main before release Status in wslu package in Ubuntu: New Bug description: Right now we are trying to update wslu 2.3.2 on focal to 2.3.6 (2.3.6-0ubuntu1) to address some critical issues reported on Launchapad before the focal release rather than SRU now: * Upstream update to 2.3.6 to address critical issues (LP: #1871986) - wslupath manpage update - fixes that imported distro cannot be properly handled by baseexec_gen - fix an issue in handling dirty output in regenerate baseexec - fix an issue in generating ~/.config/baseexec - wslusc: fix an issue that will cause generated shortcut cannot be opened for some users * debian/wsl-integration.sh: Fix issue that space in username breaks wsl-integration.sh. (LP: #1869878) * debian/wsl-integration.sh: Use /tmp folder for system users who do not have $HOME. (LP: #1859509) * debian/wsl-integration.sh: debian/wsl-integration.sh unset the right variable at the end of script. (LP: #1857426) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1872879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Medium -- 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 1872796] Re: gnome-shell animations are stuttery
> 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). Yes I have been suspecting the same. ** Summary changed: - gnome-shell animations are stuttery + gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
Probably related to bug 1832812. -- 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 1832812] Re: Locking and unlocking the screen is slow and stuttery
Probably related to bug 1872796. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1832812 Title: Locking and unlocking the screen is slow and stuttery Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 14 10:10:38 2019 InstallationDate: Installed on 2019-06-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-06-13T15:35:30.513049 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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 1872796] Re: gnome-shell animations are noticeably stuttery when the Ubuntu extensions are enabled
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-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 1872822] Re: opening utilities folder has strange behavior
*** This bug is a duplicate of bug 1869737 *** https://bugs.launchpad.net/bugs/1869737 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 1869737, 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 1869737 App icons shrink or disappear after closing an app folder -- 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/1872822 Title: opening utilities folder has strange behavior Status in gnome-shell package in Ubuntu: New Bug description: Dear All, in a fresh install of Ubuntu 20.04 beta: luca@blpcfl1:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 luca@blpcfl1:~$ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.1-4ubuntu1 Candidato: 3.36.1-4ubuntu1 Tabella versione: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What Expected: After opening and closing utilities folder (showed as X-GNOME-Utilities.directory) in the Application list, the Applications list is showed as before. What happen: After opening and closing utilities folder in the Applications list, the Applications list disappeared (or tiny) (picture 3 in the attached png) and pages dots are incremented by n. The frequently applications are tiny (picture 4) and returning to all Applications page, pages dots are incremented by n (picture 5). Best regards, Luca 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 22:32:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-05 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.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/1872822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- 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 1872802] Re: Resizing any window will randomly result in glitchy appearance for a fraction of a second
Interesting two of two reports so far are both on Kaby Lake. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Changed in: mutter (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/1872802 Title: Resizing any window will randomly result in glitchy appearance for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 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 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) 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/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200
** Also affects: pulseaudio via
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852
Importance: Unknown
Status: Unknown
--
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/1872791
Title:
PulseAudio doesn't see analog output on Dell Inspiron 6400 with
STAC9200
Status in PulseAudio:
Unknown
Status in pulseaudio package in Ubuntu:
New
Bug description:
PulseAudio currently doesn't see the analog audio output in my Dell
Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
SPDIF output. This is the situation in both "pactl list sinks" and
pavucontrol. I hear no sound from applications, probably because it's
going to SPDIF. I don't have a way to listen to SPDIF to see if that
is indeed the case.
ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
through the laptop's speakers.
This problem never happened in Ubuntu 19.10 and earlier. It might have
worked earlier in 20.04 also, but I'm not sure of that. Rebooting
didn't help. Purging and reinstalling pulseaudio and its automatically
installed dependencies didn't help.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-21-generic.
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1414 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 14 13:37:43 2020
InstallationDate: Installed on 2012-01-19 (3008 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1872791/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal
*** This bug is a duplicate of bug 1866134 *** https://bugs.launchpad.net/bugs/1866134 ** This bug has been marked a duplicate of bug 1866134 Yaru icons are not shown in Gnome-Software -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in snap-store: New Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1864307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa
*** This bug is a duplicate of bug 1867610 *** https://bugs.launchpad.net/bugs/1867610 ** This bug has been marked a duplicate of bug 1867610 snap-store cannot install local deb packages -- 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/1872522 Title: Ubuntu software will not install .deb files on focal fossa Status in gnome-software package in Ubuntu: Incomplete Bug description: On focal fossa Ubuntu software will not install .deb files (such as Google Chrome installer) however gdebi has no problem with the same files. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) 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: Mon Apr 13 19:36:10 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872788] Re: super key searching show incomplete icon
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 Yeah the attached Xrandr.txt shows this is another variation on bug 1869571. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** 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 eigth 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/1872788 Title: super key searching show incomplete icon Status in gnome-shell package in Ubuntu: Incomplete Bug description: compare to bionic, bionic will show complete icon when I press super key and type prefix of application. But in Focal, the icon is incomplete as attache screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1007.7-oem 5.6.2 Uname: Linux 5.6.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 01:37:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-12 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1007-oem root=UUID=0b23d7d3-fb6c-4ee1-9681-71d148d364d1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.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/gnome-shell/+bug/1872788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871986] Re: Wslusc shortcut not working
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/381868 ** Changed in: wslu (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1871986 Title: Wslusc shortcut not working Status in wslu: New Status in wslu package in Ubuntu: Fix Committed Bug description: Upstream bug reported: https://github.com/wslutilities/wslu/issues/110 **Background Information:** WSL: Ubuntu 18.04 Version: 2.3.2-0ubuntu2~18.04.3 When creating a Win shortcut for a GUI Linux program I end up with a shortcut that is not working. **To Reproduce** wslusc --gui pycharm.sh This results in a shortcut with the following target: C:\Windows\System32\wscript.exe C:\Users\Marco Brieden\wslu\runHidden.vbs C:\Users\Marco Brieden\AppData\Local\Microsoft\WindowsApps\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\ubuntu1804.exe run "cd ~; . /usr/share/wslu/wsl-integration When opened it gives this error: "There is no file extension in "C:\Users\Marco" **Additional context** It looks like there are two separate issues: 1. The space in my username breaks the shortcut. 2. The max length of the "target" field has been exceeded and the command got cut off. To manage notifications about this bug go to: https://bugs.launchpad.net/wslu/+bug/1871986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869878] Re: Space in username breaks wsl integration cache
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/381868 ** Changed in: wslu (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1869878 Title: Space in username breaks wsl integration cache Status in wslu package in Ubuntu: Fix Committed Bug description: * What you're doing and what's happening: launching bash from a user whose name includes a space breaks /etc/profile.d/wsl-integration.sh * What's wrong / what should be happening instead: > PS C:\Users\Jack Troughton\git\dcp-jason> bash > -bash: [: /mnt/c/Users/Jack: binary operator expected > mkdir: cannot create directory ë/mnt/c/Users/Jackí: Permission denied > -bash: $WSL_INTEGRATION_CACHE: ambiguous redirect > > The reason it breaks is due to incorrect quoting around $HOME and things derived from it. It looks like you have parallel issues as well which could break pulse audio on a machine with a space in its hostname (is that legal in windows-land?) I have created a zip file containing a fix, both the complete script and a unified context diff. I hereby place my changes in the public domain, free for use by anybody for anything. The fix is at http://people.kingsds.network/wesgarland/wsl- integration-fix.zip Windows build number: Microsoft Windows [Version 10.0.18362.720] My WSL is the Ubuntu flavour of Linux version 4.4.0-18362-Microsoft (micros...@microsoft.com) (gcc version 5.4.0 (GCC) ) #476-Microsoft Fri Nov 01 16:53:00 PST 2019 lsb_release -rd says Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy wslu says wslu: Installed: (none) Candidate: 2.3.2-0ubuntu2~18.04.3 Version table: 2.3.2-0ubuntu2~18.04.3 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1869878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857426] Re: Unset right variable at the end of wsl-integration.sh
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/381868 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1857426 Title: Unset right variable at the end of wsl-integration.sh Status in wslu package in Ubuntu: Fix Committed Bug description: There is a typo in the name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1857426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872681] Re: Overview shortcut does not work on non-latin keyboard layout
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 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 1871913, 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 1871913 super key does not work with secondary keyboard layout -- 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/1872681 Title: Overview shortcut does not work on non-latin keyboard layout Status in gnome-shell package in Ubuntu: New Bug description: Hello, Latest Ubuntu 20.04. After latest upgrade the shortcut key for the Overview (Expose?) function doesn't work on non-latin keyboard layout: 1. Switch current input language to Russian 2. Press Super key. 3. Nothing happens 4. Switch language to English 5. Press Super key 6. Windows overview screen is opened /usr/bin/xev reports the same keyscan for the button, if that matters. Other Super- shortcuts (like Super-`) do work in any keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 13:00:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (124 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1872681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
** Merge proposal linked: https://code.launchpad.net/~callmepk/ubuntu/+source/wslu/+git/wslu/+merge/381868 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created Status in wslu package in Ubuntu: Fix Committed Bug description: [ Impact ] * When $HOME/.cache can't be created an error is shown: mkdir: cannot create directory ‘//.cache’: Permission denied [Test Case] * TODO [Regression Potential] * TODO [Other Info] Originally reported to: https://github.com/wslutilities/wslu/issues/101 In addition to suppressing the error message it would probably be also useful to disable the detection by default for system users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872864] Re: appstream metadata not created
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-meta (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872864 Title: appstream metadata not created Status in snap-store: Triaged Status in ubuntu-meta package in Ubuntu: In Progress Bug description: The gnome-software packaged depends on appstream, which was bringing in that binary package in previous releases. With the switch to seeding the snap this is causing a problem with the appstream cache never getting populated. The appstream package includes an apt config that triggered the appstream cache refresh after update. We need to explicitly seed the appstream package in ubuntu-desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1872864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872325] Re: key opens Activities overview only when the XKB layout used by the first source in the list of input sources is active
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 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 1871913, 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 1871913 super key does not work with secondary keyboard layout ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872325 Title: key opens Activities overview only when the XKB layout used by the first source in the list of input sources is active Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using the Ubuntu 20.04 Focal Fossa Beta version. The ibus-unikey package is at version 0.6.1-1.1build1 What should happen: I should be able to press the Meta key regardless of input sources chosen. What happened: When Vietnamese (Unikey) is chosen as the input source, the Meta key cannot be pressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872026] Re: App icon aspect ratio in the panel is broken
Thanks for the bug report. I can't seem to find any existing reports of this problem. Please: 1. Make sure the bug still happens even with extensions (if any) disabled/uninstalled; and 2. If the bug still happens then report it to the upstream developers at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues and then tell us the new issue ID. ** Summary changed: - Activity Bar icon aspect ratio broken + App icon aspect ratio in the panel is broken ** 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/1872026 Title: App icon aspect ratio in the panel is broken Status in gnome-shell package in Ubuntu: Incomplete Bug description: The aspect ratio of the icon on the top left of the screen (Activites bar?) is broken so it looks taller and thinner than normal. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:10:09 2020 InstallationDate: Installed on 2020-01-24 (76 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-04-10 09:03:51.154471 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-04-03T20:22:43.358127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa
Correction when you set it to open with Software install it fails with: "failed to install: not supported". -- 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/1872522 Title: Ubuntu software will not install .deb files on focal fossa Status in gnome-software package in Ubuntu: Incomplete Bug description: On focal fossa Ubuntu software will not install .deb files (such as Google Chrome installer) however gdebi has no problem with the same files. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) 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: Mon Apr 13 19:36:10 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872146] Re: Audio on Headphones stopped working
Please try moving or deleting your: ~/.config/pulse and then log out and in again. Does audio device selection now work? ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1872146 Title: Audio on Headphones stopped working Status in pulseaudio package in Ubuntu: Incomplete Bug description: Audio via my headphones worked yesterday, Today no such luck. When I plug in my headphone, Plasma picks it up but no sound. Bluetooth headset still works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 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 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Apr 10 23:03:09 2020 InstallationDate: Installed on 2020-04-05 (5 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404) PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not a
This worked for me! Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnutls28 package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] Xdg-Shell Stable not working properly
Public bug reported: 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. ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-desktop3 (Debian) Importance: Undecided Status: New ** Description changed: 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 functions are returning errors and 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 + the Wayland 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. ** Description changed: 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 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. + 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
[Desktop-packages] [Bug 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
** Tags added: eoan ** Changed in: bluez (Ubuntu) Status: Expired => Confirmed ** Changed in: ubuntu-power-consumption Status: Expired => Confirmed ** Bug watch added: Linux Kernel Bug Tracker #204275 https://bugzilla.kernel.org/show_bug.cgi?id=204275 ** Also affects: bluez via https://bugzilla.kernel.org/show_bug.cgi?id=204275 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in Bluez Utilities: Unknown Status in The Ubuntu Power Consumption Project: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1717796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Re: Latest snap channel not showing
Tested gnome-software in 3.30.6-2ubuntu10.19.10.1 in eoan, confirmed the problem is fixed. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Eoan: Fix Committed Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859509] Re: wsl-integration.sh shows error when .cache/ can't be created
** Changed in: wslu (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1859509 Title: wsl-integration.sh shows error when .cache/ can't be created Status in wslu package in Ubuntu: Fix Committed Bug description: [ Impact ] * When $HOME/.cache can't be created an error is shown: mkdir: cannot create directory ‘//.cache’: Permission denied [Test Case] * TODO [Regression Potential] * TODO [Other Info] Originally reported to: https://github.com/wslutilities/wslu/issues/101 In addition to suppressing the error message it would probably be also useful to disable the detection by default for system users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1859509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871416] Re: alt-TAB hightlight colour almost indistinguishable from the background
The cost of your monitor actually doesn't have much to do with its colour accuracy. Although I find it strange even an iPad would exhibit the problem because Apple is good at colour... I still don't see any issue on a factory calibrated (100% sRGB) Dell U2413. The contrast is quite high enough. ** Changed in: yaru-theme (Ubuntu) Status: Opinion => Fix Committed -- 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/1871416 Title: alt-TAB hightlight colour almost indistinguishable from the background Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Almost impossible to see which item is highlighted. See attached image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:53:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-02-28 (1500 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1871416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software
** Also affects: snap-store Importance: Undecided Status: New ** Changed in: snap-store Importance: Undecided => Critical ** Changed in: snap-store Status: New => Triaged ** Changed in: snap-store Assignee: (unassigned) => Robert Ancell (robert-ancell) -- 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/1866134 Title: Yaru icons are not shown in Gnome-Software Status in GNOME Software: New Status in snap-store: Triaged Status in gnome-software package in Ubuntu: Triaged Bug description: When an icon theme different from Adwaita is selected, the icons from that theme are not shown in Gnome-Software. This is confusing for user because they now see two different icons for the same application (see the screenshot upstream). It would be great if Gnome-Software would look for the icon in the selected icon theme. Reported upstream here: https://gitlab.gnome.org/GNOME/gnome- software/issues/929 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1866134/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Re: Latest snap channel not showing
Tested gnome-software in 3.28.1-0ubuntu4.18.04.15 in bionic, confirmed the problem is fixed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-doe-bionic ** Tags removed: verification-doe-bionic ** Tags added: verification-done-bionic -- 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/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Eoan: Fix Committed Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
What we should actually do is to distinguish the bugs by call stack, as that will be a little different for each flavour of this crash. Unfortunately several of the most recent reports (focal) have no call stack at all. So separating them is not an option yet. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. This actually seems to happen most frequently in VirtualBox. WORKAROUND: Select "Ubuntu on Wayland" from the login screen before logging in. --- It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
^^^ I had heard hints of that elsewhere but nobody has opened a bug for it. Please open a new bug for that. -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
The upstream link has moved to bug 1872230. Maybe they will turn out to be the same issue deep down. ** No longer affects: gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869042] Re: [nvidia] all monitor scaling fails due to overlapping monitors
^^^ I had heard hints of that elsewhere but nobody has opened a bug for it. Please open a new bug that that. -- 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/1869042 Title: [nvidia] all monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
Confusingly, the upstream bug describes both bug 1872230 and this one... https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2603 -- 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/1871913 Title: super key does not work with secondary keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872230] Re: The left Ctrl key does not work when using pointer location
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2603 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2603 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2603 Importance: Unknown Status: Unknown -- 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/1872230 Title: The left Ctrl key does not work when using pointer location Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
Ian, Please try this: 0. Delete ~/.config/monitors.xml 1. Configure your preferred monitor arrangement. 2. Log out. 3. Ctrl+Alt+F4 and log into the text console. 4. cp ~/.config/monitors.xml monitors-before.xml 5. Ctrl+Alt+F1 and log into the graphics console. 6. Compare ~/.config/monitors.xml and monitors-before.xml - do either or both contain the arrangement you wanted? ** 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Mutter: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa
I can help complete his notes by adding details to this bug. The specific issue is that when downloading .deb files from an external source, i.e. www.chrome.com and you download the .deb to your computer and double click the completed file it will in fact not open in software to engage the software install process. I have found that double clicking invokes the action of opening the archive with archive manager and trying to "unzip" the file instead of install it. I have tried manually setting the file to "open with" "Ubuntu Software". I have found that installing with gdebi works and also by using dpkg -i via terminal. Thanks I hope this helps. -- 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/1872522 Title: Ubuntu software will not install .deb files on focal fossa Status in gnome-software package in Ubuntu: Incomplete Bug description: On focal fossa Ubuntu software will not install .deb files (such as Google Chrome installer) however gdebi has no problem with the same files. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) 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: Mon Apr 13 19:36:10 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Nope, sorry... Just re-experienced. -- 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: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Bionic: Confirmed Status in mutter source package in Focal: Triaged 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 1793496] Re: scaling changes when closing/re-opening the lid
Matthias, I don't see this happening now as per 3.36.1 mutter changes, can you confirm? -- 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: Fix Released Status in mutter package in Ubuntu: Triaged Status in mutter source package in Bionic: Confirmed Status in mutter source package in Focal: Triaged 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 1872434] Re: Utilities folder labeled as "X-GNOME-Utilities.directory" on Ubuntu 20.04
** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => In Progress -- 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/1872434 Title: Utilities folder labeled as "X-GNOME-Utilities.directory" on Ubuntu 20.04 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: The utilities folder is labeled as "X-GNOME-Utilities.directory" on latest Ubuntu 20.04. This is caused by a regression in latest gnome- shell (https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2623) and fix for this regression is already available: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1196 Please, fix this issue downstream before Ubuntu 20.04 is released. Otherwise it will look bad, unprofessional and be confusing to users. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872791] Re: PulseAudio doesn't see analog output on Dell Inspiron 6400 with STAC9200
I did some more investigation and found that without the workaround the
analog output only appears while headphones are plugged in. The SPDIF
output disappears while headphones are plugged in.
The bug has been submitted with this new information at
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #852
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/852
--
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/1872791
Title:
PulseAudio doesn't see analog output on Dell Inspiron 6400 with
STAC9200
Status in pulseaudio package in Ubuntu:
New
Bug description:
PulseAudio currently doesn't see the analog audio output in my Dell
Inspiron 6400 laptop with Intel HDA STAC9200 audio. It only sees the
SPDIF output. This is the situation in both "pactl list sinks" and
pavucontrol. I hear no sound from applications, probably because it's
going to SPDIF. I don't have a way to listen to SPDIF to see if that
is indeed the case.
ALSA sees the analog output and "speaker-test -D plughw:0" plays sound
through the laptop's speakers.
This problem never happened in Ubuntu 19.10 and earlier. It might have
worked earlier in 20.04 also, but I'm not sure of that. Rebooting
didn't help. Purging and reinstalling pulseaudio and its automatically
installed dependencies didn't help.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-21-generic.
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 1414 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 27'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,102801bd,00102201
HDA:14f12bfa,14f100c3,0009'
Controls : 22
Simple ctrls : 9
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 14 13:37:43 2020
InstallationDate: Installed on 2012-01-19 (3008 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-04-05 (9 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0XD720
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872791/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872861] Re: Sound applet won't change output device
** Description changed: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) In case this is useful at all, I've playing around on the command prompt:: - $ pactl list sinks short - 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ - module-alsa-card.c s16le 2ch 44100Hz SUSPENDED - 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ - module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + $ pactl list sinks short + 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED - $ pacmd set-default-sink 1 - $ paplay Chicken\ Cluck.wav # Headphone output working! - $ pacmd set-default-sink 0 - $ paplay Chicken\ Cluck.wav # Monitor output + $ pacmd set-default-sink 1 + $ paplay Chicken\ Cluck.wav # Headphone output working! + $ pacmd set-default-sink 0 + $ paplay Chicken\ Cluck.wav # Monitor output Unfortunately, the command that let me listen to chickens on my headphones (pacmd set-default-sink 1) had no effect on sounds from the rest of the system (mpv and Rhythmbox tested). -- 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/1872861 Title: Sound applet won't change output device Status in gnome-control-center package in Ubuntu: New Bug description: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) In case this is useful at all, I've playing around on the command prompt:: $ pactl list sinks short 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ module-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pacmd set-default-sink 1 $ paplay Chicken\ Cluck.wav # Headphone output working! $ pacmd set-default-sink 0 $ paplay Chicken\ Cluck.wav # Monitor output Unfortunately, the command that let me listen to chickens on
[Desktop-packages] [Bug 1872842] Re: PCI/internal sound card not detected
Is there an audio enable option in the BIOS? Maybe it is disabled? Or the codec is damaged physically? You could install the newer kernel to verify if the codec is good or not, if it is good and newer kernel could work, then we will bisect the kernel to find the fix for this issue. -- 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/1872842 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Upsstream says try a newer kernel, but I am on the LTS HWE kernels for Xenial, and want to solve this on this version. This is a Think Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads, but finds no codecs. This is the onboard audio card, and don't think they have chnaged it much in years, so I expect that at least SOME codecs should be detected. Played with various alsa conf settings, no joy.. options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 options snd-hda-intel model=thinkpad options snd-hda-intel position_fix=3 Tried model(s) generic, and auto.. always the same in bootup.. [ 12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 [ 12.830129] snd_hda_intel :00:1f.3: no codecs found! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon Date: Tue Apr 14 15:00:59 2020 InstallationDate: Installed on 2019-11-03 (163 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1ZKT23A dmi.board.name: 313C dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305181519567 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710e dmi.product.name: 10UR001JUS dmi.product.version: ThinkCentre M710e dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872861] Re: Sound applet won't change output device
** Description changed: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) + + In case this is useful at all, I've playing around on the command + prompt:: + + $ pactl list sinks short + 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ + module-alsa-card.c s16le 2ch 44100Hz SUSPENDED + + $ pacmd set-default-sink 1 + $ paplay Chicken\ Cluck.wav # Headphone output working! + $ pacmd set-default-sink 0 + $ paplay Chicken\ Cluck.wav # Monitor output + + Unfortunately, the command that let me listen to chickens on my + headphones (pacmd set-default-sink 1) had no effect on sounds from the + rest of the system (mpv and Rhythmbox tested). -- 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/1872861 Title: Sound applet won't change output device Status in gnome-control-center package in Ubuntu: New Bug description: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) In case this is useful at all, I've playing around on the command prompt:: $ pactl list sinks short 0 alsa_output.pci-_03_00.1.hdmi-stereo-extra3\ module-alsa-card.c s16le 2ch 44100Hz SUSPENDED 1 alsa_output.usb-Schiit_Schiit_USB_Audio_Device-00.iec958-stereo\ module-alsa-card.c s16le 2ch 44100Hz SUSPENDED $ pacmd set-default-sink 1 $ paplay Chicken\ Cluck.wav # Headphone output working! $ pacmd set-default-sink 0 $ paplay Chicken\ Cluck.wav # Monitor output Unfortunately, the command that let me listen to chickens on my headphones (pacmd set-default-sink 1) had no effect on sounds from the rest of the system (mpv and Rhythmbox tested). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872862] [NEW] When plugging in encrypted USB the ask password dialog will not close
Public bug reported: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I have a LUKS encrypted USB disk. When I plug it in, it should mount it and ask me for the password. It asks me for the password which I type in, but the dialog never goes away if I hit Cancel or Enter. The only way to make it go away is to physically remove the USB drive. After I remove it, it asks me for the password again, and the same problem occurs. So I remove it again. But it never decrypts and mounts the drive. So I basically cant use it anymore. It works fine on my Manjaro KDE: with dolphin, thunar and nautilus. This behavior only happens in Ubuntu and nautilus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:15:12 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1872862 Title: When plugging in encrypted USB the ask password dialog will not close Status in nautilus package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I have a LUKS encrypted USB disk. When I plug it in, it should mount it and ask me for the password. It asks me for the password which I type in, but the dialog never goes away if I hit Cancel or Enter. The only way to make it go away is to physically remove the USB drive. After I remove it, it asks me for the password again, and the same problem occurs. So I remove it again. But it never decrypts and mounts the drive. So I basically cant use it anymore. It works fine on my Manjaro KDE: with dolphin, thunar and nautilus. This behavior only happens in Ubuntu and nautilus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:15:12 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1872862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
Ok, I've also fixed the limited number of enroll of the current UI (still available as part of the gnome-control-center!727 MR), so that is enough to fix the first part of this bug. As per ubuntu, I've the packaging bits ready at https://salsa.debian.org /gnome-team/gnome-control-center/-/merge_requests/15 so let me know whether I should proceed with that. -- 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: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress 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 1872221] Re: Updates installed snap-store snap and uninstalled ubuntu-software
> Updates installed snap-store snap and uninstalled ubuntu-software This is normal behavior, unless you have manually installed the "gnome- software" package. The Ubuntu Software application on 20.04 is now provided by the "snap-store" snap instead of the "gnome-software" package. More info in https://discourse.ubuntu.com/t/is-ubuntu-software- going-to-be-remove-for-snap-snap-store/14542/ and bug 1868409. > snap store app is also see thru (100% transparent) I'm not sure what you mean, but it sounds like a different bug, possibly against the display system? -- 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/1872221 Title: Updates installed snap-store snap and uninstalled ubuntu-software Status in gnome-software package in Ubuntu: New Bug description: snap store app is also see thru (100% transparent) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 14:29:33 2020 InstallationDate: Installed on 2020-02-05 (66 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872861] [NEW] Sound applet won't change output device
Public bug reported: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1872861 Title: Sound applet won't change output device Status in gnome-control-center package in Ubuntu: New Bug description: Using the gnome-control-centre sound applet to change the output device from the motherboard's default to an external USB device used to work well on 19.10, but does not work on 20.04 Beta. I use a USB headphone DAC/amp on my desktop (Schiit Modi/Magni combo). Under Ubuntu 19.10 I could use the sound applet in the gnome-control- center to select either that USB device or basic audio through the HDMI cable on my monitor (it would always default to the basic audio on reboot, but that's another story) then use my headphones happily. Using Ubuntu 20.04 Beta the sound applet shows all of the expected devices, but choosing different devices has no effect - any music then played continues to come only from the monitor. Using the 'Test' button plays sound only through the monitor also. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 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: Wed Apr 15 11:44:27 2020 InstallationDate: Installed on 2020-01-11 (94 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe78:26c2. Apr 08
[Desktop-packages] [Bug 1872857] [NEW] attribute-invalid : timestamp is in the future
Public bug reported: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy libappstream-glib8 libappstream-glib8: Installed: 0.7.16-1ubuntu1 Candidate: 0.7.16-1ubuntu1 Version table: *** 0.7.16-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I'm UK based with time set to BST. If I set the date to the current date, then between 12:00 midnight and 1:00am, flatpak-builder fails with and error: org.pjbroad.EternallandsClient:AppData problem: attribute-invalid : timestamp is in the future Error loading AppData file: AppData file /app/share/appdata/org.pjbroad.EternallandsClient.appdata.xml was not valid Error: ERROR: appstream-compose failed: Child process exited with code 1 I would expect using my local date to be valid. This bug is fixed upstream in version 0.7.17 https://github.com/hughsie/appstream-glib/commit/72789b6ff59f5d1741d1cbc29e90bfa57079c514 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libappstream-glib8 0.7.16-1ubuntu1 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 15 00:31:43 2020 InstallationDate: Installed on 2019-11-02 (164 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: appstream-glib UpgradeStatus: Upgraded to focal on 2020-03-28 (17 days ago) ** Affects: appstream-glib (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 appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1872857 Title: attribute-invalid : timestamp is in the future Status in appstream-glib package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy libappstream-glib8 libappstream-glib8: Installed: 0.7.16-1ubuntu1 Candidate: 0.7.16-1ubuntu1 Version table: *** 0.7.16-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I'm UK based with time set to BST. If I set the date to the current date, then between 12:00 midnight and 1:00am, flatpak-builder fails with and error: org.pjbroad.EternallandsClient:AppData problem: attribute-invalid : timestamp is in the future Error loading AppData file: AppData file /app/share/appdata/org.pjbroad.EternallandsClient.appdata.xml was not valid Error: ERROR: appstream-compose failed: Child process exited with code 1 I would expect using my local date to be valid. This bug is fixed upstream in version 0.7.17 https://github.com/hughsie/appstream-glib/commit/72789b6ff59f5d1741d1cbc29e90bfa57079c514 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libappstream-glib8 0.7.16-1ubuntu1 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-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 15 00:31:43 2020 InstallationDate: Installed on 2019-11-02 (164 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: appstream-glib UpgradeStatus: Upgraded to focal on 2020-03-28 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1872857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
Hi Jonathan and Dan: > I am not sure what you mean. There is no "snap-store" deb on my > 20.04 system, nor does "apt search snap-store" yield any results. It's a snap application, which you'll see in the output of the "snap list" command if it is installed. It provides the Ubuntu Software application on 20.04 and replaces the "gnome-software" deb, cf https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-remove- for-snap-snap-store/14542 and bug 1868409. If I understand correctly, at this point in time, your system shouldn't have the "gnome-software" deb any longer unless you've manually installed it yourself, and it should have the "snap-store" snap instead. > Furthermore, this bug was initially reported about the output of > apticron showing up in cron job emails; as far as I know, apticron > is independent of gnome-software. This is unclear to me too, but Matthias Klumpp identified the cause of this error as lying with gnome-software metadata, and he fixed it upstream in gnome-software, cf comment 3 on this bug. Perhaps apticron runs apt-get update? > I have an up-to-date focal system and I am still seeing this. I don't see it any more. The plot thickens. You may still have the "gnome-software" deb? If yes, and you don't mind migrating to the "snap- store" snap for you Ubuntu Software application, then you could run the update-manager (the graphical application), it will take care of the transition, see bug 1868409 for details. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." Status in appstream package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: In Progress Bug description: `apt-get update` and the nightly `apticron --cron` job are reporting: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." This is pretty much meaningless to most people who have no idea what AppStream is and what "verbose log" is being referred to. I dug around and managed to discover `appstreamcli refresh-cache --force --verbose`, whose output is attached. I don't know what the "bad" output is or how to fix it. All I know is that I hope Focal isn't going to be generating this message when it ships, because it isn't going to make sense to most people and most people won't know how to fix it and it causes annoying emails from apticron every night. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: appstream 0.12.10-1 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: Sun Feb 2 16:01:24 2020 InstallationDate: Installed on 2019-08-16 (170 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: appstream UpgradeStatus: Upgraded to focal on 2020-01-31 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Thanks! Taking a glance at the log it looks as if there have been a couple of Firefox updates (to version 74.0 then 75.0) which would more likely be causing your networking issues. Reinstalling would certainly be worth a try. -- 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 1872844] [NEW] Changing theme Light<->Standard preserves theme for title bar
Public bug reported: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872844 Title: Changing theme Light<->Standard preserves theme for title bar Status in gnome-control-center package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872842] [NEW] PCI/internal sound card not detected
Public bug reported: Upsstream says try a newer kernel, but I am on the LTS HWE kernels for Xenial, and want to solve this on this version. This is a Think Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads, but finds no codecs. This is the onboard audio card, and don't think they have chnaged it much in years, so I expect that at least SOME codecs should be detected. Played with various alsa conf settings, no joy.. options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 options snd-hda-intel model=thinkpad options snd-hda-intel position_fix=3 Tried model(s) generic, and auto.. always the same in bootup.. [ 12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 [ 12.830129] snd_hda_intel :00:1f.3: no codecs found! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon Date: Tue Apr 14 15:00:59 2020 InstallationDate: Installed on 2019-11-03 (163 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1ZKT23A dmi.board.name: 313C dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305181519567 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710e dmi.product.name: 10UR001JUS dmi.product.version: ThinkCentre M710e dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1872842 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Upsstream says try a newer kernel, but I am on the LTS HWE kernels for Xenial, and want to solve this on this version. This is a Think Centre M710e Model/Type 10UR, and the snd_hba_intel correctly loads, but finds no codecs. This is the onboard audio card, and don't think they have chnaged it much in years, so I expect that at least SOME codecs should be detected. Played with various alsa conf settings, no joy.. options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 options snd-hda-intel model=thinkpad options snd-hda-intel position_fix=3 Tried model(s) generic, and auto.. always the same in bootup.. [ 12.684107] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.827419] snd_hda_intel :00:1f.3: CORB reset timeout#1, CORBRP = 0 [ 12.830129] snd_hda_intel :00:1f.3: no codecs found! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: X-Cinnamon Date: Tue Apr 14 15:00:59 2020 InstallationDate: Installed on 2019-11-03 (163 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: M1ZKT23A dmi.board.name: 313C dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305181519567 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1ZKT23A:bd06/05/2018:svnLENOVO:pn10UR001JUS:pvrThinkCentreM710e:rvnLENOVO:rn313C:rvrSDK0J40697WIN3305181519567:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M710e dmi.product.name: 10UR001JUS dmi.product.version: ThinkCentre M710e dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-13T16:09:19.881423 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1872716] Re: Evince crashes when trying to open djvu
Here's the new bug: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1872835 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1872716 Title: Evince crashes when trying to open djvu Status in evince package in Ubuntu: Invalid Bug description: I tried to open a djvu file with evince. Instead of opening, the evince window shows for less than a second, and then it crashes. The djvu file is fine and opens well with evince 3.18.2 on ubuntu 16.04. When I try to open the file through the terminal (with 'evince ') I get the output: "Segmentation fault (core dumped)". Additional info: 'lsb_release -rd': Description: Ubuntu 18.04.4 LTS Release: 18.04 'apt-cache policy evince': evince: Installed: 3.28.4-0ubuntu1.2 Candidate: 3.28.4-0ubuntu1.2 Version table: *** 3.28.4-0ubuntu1.2 500 500 http://il.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://il.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 16:55:19 2020 InstallationDate: Installed on 2020-02-24 (49 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_IL:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1872716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.15 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Eoan: Fix Committed Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871281] Re: Latest snap channel not showing
Hello Robert, or anyone else affected, Accepted gnome-software into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.6-2ubuntu10.19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-eoan. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan ** Changed in: gnome-software (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1871281 Title: Latest snap channel not showing Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Eoan: Fix Committed Bug description: [Impact] Due to a code change for channel names in snapd gnome-software in bionic doesn't show versions in the 'latest/*' channels. Solution is to backport changes that always use the full name for channels to avoid this problem. Noticed in https://forum.snapcraft.io/t/track-request-v6-for-postman/13425/9 [Test Case] 1. Open GNOME Software 2. Search for the 'postman' snap Expected result: latest/stable channel shown with version like 7.21.1 Observed result: No version shown in for latest/* channels. [Regression potential] Risk of introducing new bugs in relation to channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1871281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872452] Re: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD / Thinkpad T495)
Meanwhile after some updates I manage to login even without power supply. After that the screen is distorted and looks like this - s. attachment. In the screen you see right a shadow - my taskbar. You can only see the top bar of windows. ** Attachment added: "IMG_20200414_230842.jpg" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1872452/+attachment/5354178/+files/IMG_20200414_230842.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1872452 Title: [amdgpu] Boot into black screen without power supply (Kubuntu on AMD / Thinkpad T495) Status in kwin package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Always when I turn on my Lenovo Thinkpad T495 (AMD CPU)- without the power supply connected - the laptop boots correctly at the beginning, but then just before going to the login screen it gets black. It can only be restarted. When I attach the power supply before the laptop boot everything works correctly. I see this behavior only on Kubuntu (with KDE desktop). On Ubuntu 20.04 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 13 14:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-04-02 (10 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d6957960-70a9-45a8-98b1-b0a14d07b829 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET46W(1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1872452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Thank you Simon Déziel! That worked. I couldn't quite figure that out on my own. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: New Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-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 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872825] Re: nm-online crashed with SIGSEGV in g_source_set_ready_time()
*** This bug is a duplicate of bug 1866783 *** https://bugs.launchpad.net/bugs/1866783 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1866783, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872825/+attachment/5354154/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354156/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354166/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354167/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354168/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354170/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872825/+attachment/5354171/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1866783 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1872825 Title: nm-online crashed with SIGSEGV in g_source_set_ready_time() Status in network-manager package in Ubuntu: New Bug description: can't find kernel on boot ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 14 15:36:00 2020 ExecutablePath: /usr/bin/nm-online InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) IpRoute: default via 192.168.43.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.43.0/24 dev wlp2s0 proto kernel scope link src 192.168.43.91 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/bin/nm-online -s -q --timeout=30 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f8526942bf3 : cmp 0x10(%rax),%rbp PC (0x7f8526942bf3) ok source "0x10(%rax)" (0x0010) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nm-online crashed with SIGSEGV in g_source_set_ready_time() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: 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 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1872825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872822] [NEW] opening utilities folder has strange behavior
Public bug reported: Dear All, in a fresh install of Ubuntu 20.04 beta: luca@blpcfl1:~$ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 luca@blpcfl1:~$ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.1-4ubuntu1 Candidato: 3.36.1-4ubuntu1 Tabella versione: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What Expected: After opening and closing utilities folder (showed as X-GNOME-Utilities.directory) in the Application list, the Applications list is showed as before. What happen: After opening and closing utilities folder in the Applications list, the Applications list disappeared (or tiny) (picture 3 in the attached png) and pages dots are incremented by n. The frequently applications are tiny (picture 4) and returning to all Applications page, pages dots are incremented by n (picture 5). Best regards, Luca 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 22:32:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-05 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.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: "bug-gnome-shell-utilities.png" https://bugs.launchpad.net/bugs/1872822/+attachment/5354147/+files/bug-gnome-shell-utilities.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872822 Title: opening utilities folder has strange behavior Status in gnome-shell package in Ubuntu: New Bug description: Dear All, in a fresh install of Ubuntu 20.04 beta: luca@blpcfl1:~$ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 luca@blpcfl1:~$ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.1-4ubuntu1 Candidato: 3.36.1-4ubuntu1 Tabella versione: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What Expected: After opening and closing utilities folder (showed as X-GNOME-Utilities.directory) in the Application list, the Applications list is showed as before. What happen: After opening and closing utilities folder in the Applications list, the Applications list disappeared (or tiny) (picture 3 in the attached png) and pages dots are incremented by n. The frequently applications are tiny (picture 4) and returning to all Applications page, pages dots are incremented by n (picture 5). Best regards, Luca 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 22:32:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-05 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.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/1872822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not a
Oops, it should have been LOW, not LEGACY. Here it is again to avoid any confusion: As a workaround, can you try lowering the profile from MEDIUM [1] to LOW [2]: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 2: https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnutls28 package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 As a workaround, can you try lowering the profile from MEDIUM [1] to LOW [2]: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LOW EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 2: https://gnutls.org/manual/html_node/Selecting-cryptographic-key-sizes.html#Selecting-cryptographic-key-sizes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: New Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-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 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not a
As a workaround, can you try lowering the profile from MEDIUM [1] to LEGACY: sudo mkdir /etc/gnutls cat << EOF | sudo tee -a /etc/gnutls/config [overrides] default-priority-string = NORMAL:-VERS-ALL:+VERS-TLS1.3:+VERS-TLS1.2:+VERS-DTLS1.2:%PROFILE_LEGACY EOF 1: https://git.launchpad.net/ubuntu/+source/gnutls28/tree/debian/rules#n38 ** Changed in: gnutls28 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnutls28 package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
