[Desktop-packages] [Bug 1892669] Re: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen
I can't see any problems in the attached files. Can you please attach a photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892669 Title: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen Status in Ubuntu: Incomplete Bug description: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 23:02:25 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-08-20 (3 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b938a820-f262-48c7-9d2c-30fed7ef6d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2262HKV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SQ530UP#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 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/1892669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892665] Re: gnome-shell occupy much space in my pc
1. Please provide output from 'ps auxw' showing all your processes with their memory usage. 2. Please don't mention any apps in this bug, since it's just about gnome-shell. ** 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/1892665 Title: gnome-shell occupy much space in my pc Status in gnome-shell package in Ubuntu: Incomplete Bug description: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892665] Re: gnome-shell occupy much space in my pc
Also please be careful to avoid measuring virtual address space (the VSZ column in ps) - that is not memory usage. We need to look at the RSS column instead. -- 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/1892665 Title: gnome-shell occupy much space in my pc Status in gnome-shell package in Ubuntu: Incomplete Bug description: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
No problem. It's not up to me anyway... Long term, to get the GUI work done you will need to request enhancements in both of these projects: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues https://gitlab.gnome.org/GNOME/mutter/-/issues Short term, to get the default changed you will need to request an enhancement here: https://gitlab.freedesktop.org/xorg/xserver/-/issues When done, please tell us the new issue IDs. -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892667] Re: On-screen-keyboard shows up after touching the screen, ignoring physical keyboard
Please look in: Settings > Universal Access > Typing > Screen Keyboard and verify the option is turned OFF. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: osk -- 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/1892667 Title: On-screen-keyboard shows up after touching the screen, ignoring physical keyboard Status in gnome-shell package in Ubuntu: Incomplete Bug description: after Every time I touch the screen (regardless of where) the minute the focus shifts to a text-entry field the on-screen-keyboard shows up. This should be disabled completely when there is a physical keyboard attached (as in a laptop with a touch screen.) Your attention to this is appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 23 17:55:48 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-06-10 (74 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor) With any lower quality component on the pipeline, dark screen or function lost is not acceptable. It should be better to provide lower default bpc than dark user's screen. Afterall, user can adjust the bpc by command in short-term or by UI in long-term plan. But if we just dark user's screen, user mostly thinks the hardware is broken or Ubuntu provides poor compatibility(if they compare the same component to Windows). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Added another two packages that are blocked by this so they are marked/linked in update excuses :-/ ** Also affects: iputils (Ubuntu) Importance: Undecided Status: New ** Changed in: iputils (Ubuntu) Status: New => Confirmed ** Also affects: ntpsec (Ubuntu) Importance: Undecided Status: New ** Changed in: ntpsec (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in iputils package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in ntpsec package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1892358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
I understand and the solution is better than the one I am used to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746420] Re: I really don't know , using diagnostic app.
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1746420 Title: I really don't know , using diagnostic app. Status in xorg-server package in Ubuntu: Expired Bug description: Machine gets slow . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-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 Date: Tue Jan 30 23:16:28 2018 DistUpgraded: 2018-01-10 16:36:41,763 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-annan-standard-precise-amd64-20130106-0 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: alsa-hda, 0.201212151034~precise1annan2, 3.2.0-32-generic, x86_64: installed asus-wmi, 1.14, 3.2.0-32-generic, x86_64: installed compat-wireless-3.4-rc3-1-alx-dkms, 1, 3.2.0-32-generic, x86_64: installed i915, 0.1, 3.2.0-32-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:115d] InstallationDate: Installed on 2018-10-10 (-251 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130106-02:29 MachineType: ASUSTeK COMPUTER INC. 1015E ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=dad73f6d-4e85-4338-83b0-0e0417a13a96 ro locale=C quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-01-10 (20 days ago) dmi.bios.date: 03/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1015E.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 1015E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1015E.302:bd03/05/2013:svnASUSTeKCOMPUTERINC.:pn1015E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rn1015E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: 1015E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jan 30 22:37:53 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4572 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884536] Re: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04
[Expired for gpm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gpm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gpm in Ubuntu. https://bugs.launchpad.net/bugs/1884536 Title: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04 Status in gpm package in Ubuntu: Expired Bug description: I have relatively recently loaded Ubuntu 20.04 to dual-boot on a Packard Bell with Windows 10 Home 64-bit already installed. The mouse- pointer moves and clicks perfectly when the PC has a single-monitor. However, for work as a developer, I should like to use a dual-monitor setup. The problem I have is, if I plug in to the PC tower a second monitor and follow the steps to Connect Another Monitor To My Computer (https://help.ubuntu.com/stable/ubuntu-help/display-dual- monitors.html), and after I confirm "join Display", the mouse-pointer jumps about and a second stationary mouse-pointer appears in the bottom right of my primary screen. This behaviour stops immediately I confirm "Single Display", but now the second screen is now turned blank. $ xinput ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB Wired Keyboard Consumer Control id=12 [slave pointer (2)] ⎜ ↳ PixArt USB Optical Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ USB Wired Keyboardid=10 [slave keyboard (3)] ↳ USB Wired Keyboard System Control id=11 [slave keyboard (3)] ↳ USB Wired Keyboard Consumer Control id=14 [slave keyboard (3)] $ sudo dmidecode -t 1 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Packard Bell Product Name: iMedia S2984 Version: Serial Number: DTU96EK00360103D0F3000 UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd Wake-up Type: Power Switch SKU Number: Family: Packard Bell Desktop $ lsb_release -a; uname -a; lsusb No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard Model KBAY211 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I am reporting this as a bug because I am unable to fix it and I have asked around, but no joy. I do need a dual-monitor set p for work. Currently, I can use Windows10 with dual-monitors, on the same machine, without a glitch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1884536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885015] Re: replace gnutls with openssl
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1885015 Title: replace gnutls with openssl Status in network-manager package in Ubuntu: Expired Bug description: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885065] Re: i fucking dont know its your shit
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1885065 Title: i fucking dont know its your shit Status in software-properties package in Ubuntu: Expired Bug description: i dont fucking nknow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1885065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892669] [NEW] the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen
Public bug reported: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 23:02:25 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-08-20 (3 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b938a820-f262-48c7-9d2c-30fed7ef6d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2262HKV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SQ530UP#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1892669 Title: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen Status in xorg package in Ubuntu: New Bug description: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 23:02:25 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-08-20 (3 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b938a820-f262-48c7-9d2c-30fed7ef6d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2262HKV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SQ530UP#ABA dmi.product.version: A0001D02 dmi.
[Desktop-packages] [Bug 1892669] Re: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen
i am about to reinstall 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/1892669 Title: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen Status in xorg package in Ubuntu: New Bug description: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 23:02:25 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-08-20 (3 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b938a820-f262-48c7-9d2c-30fed7ef6d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2262HKV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SQ530UP#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892665] Re: gnome-shell occupy much space in my pc
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892665 Title: gnome-shell occupy much space in my pc Status in gnome-shell package in Ubuntu: New Bug description: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892665] [NEW] gnome-shell occupy much space in my pc
You have been subscribed to a public bug: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- gnome-shell occupy much space in my pc https://bugs.launchpad.net/bugs/1892665 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892667] [NEW] On-screen-keyboard shows up after touching the screen, ignoring physical keyboard
Public bug reported: after Every time I touch the screen (regardless of where) the minute the focus shifts to a text-entry field the on-screen-keyboard shows up. This should be disabled completely when there is a physical keyboard attached (as in a laptop with a touch screen.) Your attention to this is appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 23 17:55:48 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-06-10 (74 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892667 Title: On-screen-keyboard shows up after touching the screen, ignoring physical keyboard Status in gnome-shell package in Ubuntu: New Bug description: after Every time I touch the screen (regardless of where) the minute the focus shifts to a text-entry field the on-screen-keyboard shows up. This should be disabled completely when there is a physical keyboard attached (as in a laptop with a touch screen.) Your attention to this is appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 23 17:55:48 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-06-10 (74 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892626] Re: Random system freeze
Thanks for the bug report. This appears to be a crash in the 'radeon' kernel driver. Please try a newer kernel like https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8.3/amd64/ and if that doesn't solve the problem then also look in the 'Additional Drivers' app to see if your system supports the proprietary AMD driver instead. ** Tags added: radeon ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Random system freeze + [radeon] Random system freeze ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892626 Title: [radeon] Random system freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889998] Re: Settings > Power suggests wifi "can" be turned off not "will" be turned off
*** This bug is a duplicate of bug 1751954 *** https://bugs.launchpad.net/bugs/1751954 ** This bug is no longer a duplicate of bug 1884660 Bluetooth and Wi-Fi items in Power are worded ambiguously ** This bug has been marked a duplicate of bug 1751954 Bluetooth and Wi-Fi items in Power are worded ambiguously -- 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/1889998 Title: Settings > Power suggests wifi "can" be turned off not "will" be turned off Status in gnome-control-center package in Ubuntu: Invalid Bug description: How to reproduce the bug: * Open control center * Go to "Power" section on the left sidebar. * Toggle this button: "Wi-Fi: Wi-Fi can be turned off to save power" Expected behavior: * Wifi should no longer be turned off to save power. * Current wifi connection should stay on. Observed behavior: * All wifi connections are immediately disabled, irrespective of how idle the system is. It looks like this button is toggling the wrong underlying setting. Version info: $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.4-0ubuntu1 Version table: 1:3.36.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 1:3.36.2-0ubuntu1 100 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 12:38:31 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-25 (676 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-05-09 (84 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1889998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884660] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
*** This bug is a duplicate of bug 1751954 *** https://bugs.launchpad.net/bugs/1751954 ** This bug has been marked a duplicate of bug 1751954 Bluetooth and Wi-Fi items in Power are worded ambiguously -- 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/1884660 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: What happens: Changing "Wi-Fi can be turned off to save power" to OFF disables Wi- Fi. So there's impossible to have Wi-Fi enabled and Wi-Fi power saving disabled (see screencast). Same thing with bluetooth. Checkboxes (swithes) disable and enable each other in completely unpredictable way. What is expected to happen: It should be possible to have wireless enabled and power saving disabled. Ubuntu 20.04 gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1884660/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
** Summary changed: - Power > Wifi should offer powersaving mode for Wi-Fi + Bluetooth and Wi-Fi items in Power are worded ambiguously ** Changed in: gnome-control-center (Ubuntu) Importance: Wishlist => Low ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: In the gnome-control-center, in the power section, there is a checkbox that says: Wi-Fi Turn off Wi-Fi to save power I have it checked, so after a few minutes without using my computer, the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this box, but it disables my wi-fi immediately. So, it's obviously wrong to disable the wi-fi when I click that checkbox. And I don't seem to have a way to keep my wi-fi enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 18:27:16 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-04 (145 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eo SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892620] Re: power management incorrect wifi & bluetooth power off handling
*** This bug is a duplicate of bug 1751954 *** https://bugs.launchpad.net/bugs/1751954 I think this is already covered by bug 1751954. Although the upstream bug is probably more helpful: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681 ** Tags added: focal ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #681 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681 ** This bug has been marked a duplicate of bug 1751954 Bluetooth and Wi-Fi items in Power are worded ambiguously -- 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/1892620 Title: power management incorrect wifi & bluetooth power off handling Status in gnome-control-center package in Ubuntu: New Bug description: Releases: Ubuntu 20.04, Ubuntu 20.04.1 Hardware: HP ProBook 4540s When in Power Management, there are 2 slider button options (my own translation from Polish): Enable Wifi power off for energy saving Enable Bluetooth power off for energy saving But they seem to be directly disabling these modules, instead of only changing the power saving feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892615] Re: screen goes down sometimes
1. Please check /var/crash for any .crash files and if you find any that might be relevant then follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. Wait until the problem happens again, and then: 2.1. Press Alt+SysRq+S 2.2. Reboot. 2.3. Open a Terminal window and run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892615 Title: screen goes down sometimes Status in Ubuntu: Incomplete Bug description: screen automatic goes down while working ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Sun Aug 23 11:46:09 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1771 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu May 28 11:49:11 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1892615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870597] Re: Xorg log: scheduled expiry is in the past... your system is too slow
It looks like this might be a fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1241 ** Summary changed: - Xorg log: scheduled expiry is in the past... your system is too slow + scheduled expiry is in the past... your system is too slow ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - scheduled expiry is in the past... your system is too slow + libinput says: scheduled expiry is in the past... your system is too slow -- 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/1870597 Title: libinput says: scheduled expiry is in the past... your system is too slow Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm-x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 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-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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/mutter/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870597] Re: Xorg log: scheduled expiry is in the past... your system is too slow
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/1870597 Title: libinput says: scheduled expiry is in the past... your system is too slow Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm-x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 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-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-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/mutter/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892573] Re: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops
*** This bug is a duplicate of bug 1870597 *** https://bugs.launchpad.net/bugs/1870597 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 1870597, 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 1870597 Xorg log: scheduled expiry is in the past... your system is too slow -- 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/1892573 Title: syslog gdm-x-session "your system is too slow" as desktop GUI slows down and eventually stops Status in mutter package in Ubuntu: New Bug description: After ~72 hours, my Gnome desktop will be very slow. In syslog I noticed that I get a bunch of these messages as the system slows down: /usr/lib/gdm3/gdm-x-session[13460]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-30ms), your system is too slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 18:02:23 2020 InstallationDate: Installed on 2020-02-23 (181 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/1892573/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892510] Re: Refresh rate locked to 24hz only on Ubuntu
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - Refresh rate locked to 24hz only on Ubuntu + [amdgpu] Refresh rate locked to 24hz only on Ubuntu ** Tags added: amdgpu -- 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/1892510 Title: [amdgpu] Refresh rate locked to 24hz only on Ubuntu Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: Ubuntu will not let me run my monitor at 1080p 60Hz, only 24hz, yet other OS like Kali and Windows are capable of running 1080p60 with no problems. I cannot find 60hz in xrandr or display settings, and monitors.xml editing returns nothing. I have tried updating my BIOS, my TV settings, my graphics drivers and everything else.. no luck. Running Ubuntu 20.04 LTS with Budgie. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Aug 21 15:33:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3801] InstallationDate: Installed on 2020-08-06 (14 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO INVALID ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-5.4.0-42-generic root=UUID=328af68c-944b-4618-83e7-bcf0237143b9 ro quiet splash vt.handoff=7 initrd=boot\initrd.img-5.4.0-42-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 1PCN72WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo LV1145 dmi.modalias: dmi:bvnLENOVO:bvr1PCN72WW:bd11/01/2019:svnLENOVO:pnINVALID:pvrLenovoLV1155:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLV1145: dmi.product.family: IDEAPAD dmi.product.name: INVALID dmi.product.sku: LENOVO_BI_IDEAPAD1P dmi.product.version: Lenovo LV1155 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1892510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I have the same problem. I ran Pop!_OS 20.04 from USB and the bluetooth worked fine. And after doing a clean install, bluetooth also worked. But when I did the initial updates, I had the same problem: device appeared in settings and connected, but no sound. Something in the initial updates messed things up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: Fix Released Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Proposed fix/hack: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6429 ** Changed in: mesa (Ubuntu) Status: Invalid => Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Importance: High => Medium ** No longer affects: mutter (Ubuntu) ** No longer affects: nvidia-graphics-drivers-418 (Ubuntu) ** Tags removed: disco -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in mesa package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892419] Re: Displayport is not working
Thanks. Since the kernel is reporting the DisplayPort is disconnected this is either a kernel bug or a hardware problem. ** No longer affects: xorg-server (Ubuntu) ** Summary changed: - Displayport is not working + DisplayPort never detected as connected ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1892419 Title: DisplayPort never detected as connected Status in linux package in Ubuntu: Confirmed Bug description: Can't get dysplayport to recognize. It is not the cable since I tested it on another PC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 16:54:01 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated Graphics Controller [103c:1993] InstallationDate: Installed on 2020-08-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Hewlett-Packard HP ProBook 650 G1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=adbe32f1-2fcd-4bb7-b8d0-7e8db010d123 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L77 Ver. 01.32 dmi.board.name: 1993 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.asset.tag: 5CG5203T6Z dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL77Ver.01.32:bd03/25/2015:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ProBook 650 G1 dmi.product.sku: K4L00UT#ABA dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892427] Re: [amdgpu] HDMI connected TV wakeup problems
That's expected and not a bug. Once a display is removed from the current configuration (or just turned off), the shell tries to help you by moving all windows to the remaining monitor. So you don't lose them. This is however a bug if it happens when you try to sleep the whole system. ** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => compiz (Ubuntu) -- 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/1892427 Title: [amdgpu] HDMI connected TV wakeup problems Status in compiz package in Ubuntu: Incomplete Bug description: The setup here is critical to understanding the problem. A laptop is connected via HDMI to a TV monitor. Two displays are thus available to the OS. Everything works great both in mirror display and regular display. At the end of day, I lock the user account and the display manager (DM) tells the monitors to blank (sleep?). When I touch the DM and login the laptop display livens up and looks good. However, the TV display often doesn't and I need to wake up the TV with the TV control stick. This works OK, and the second display comes back. And all the windows associated with that display return from sleep OK. *HOWEVER*, all the geometry for those windows (term windows is one example) are lost. I can see the windows in the term overview, but I cant get to them on the second display. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.24 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 Aug 20 17:00:58 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:8348] InstallationDate: Installed on 2018-04-20 (853 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: HP HP Laptop 17-ak0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=79cc5ed4-f740-450d-9a89-c5b4f899d10e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8348 dmi.board.vendor: HP dmi.board.version: 42.20 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd11/02/2017:svnHP:pnHPLaptop17-ak0xx:pvrType1ProductConfigId:rvnHP:rn8348:rvr42.20:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-ak0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-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 xserver.bootTime: Wed Aug 5 16:27:12 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1892427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #216 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/216 ** Also affects: gnome-shell-extension-desktop-icons via https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/216 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-07-03 (1147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886672] Re: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes re
** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => 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/1886672 Title: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes remains off Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2019-01-29 (525 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-15 (53 days ago) dmi.bios.date: 11/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.13.0 dmi.board.name: 0PVG6D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.13.0:bd11/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PVG6D:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1886672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892276/+attachment/5403971/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-07-03 (1147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
Please propose any fixes on the Gitlab site and link them to: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258 ** Tags removed: disco eoan ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #258 https://gitlab.freedesktop.org/xorg/xserver/-/issues/258 ** Changed in: xorg-server Importance: High => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #865 => gitlab.freedesktop.org/xorg/xserver/-/issues #258 -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
I have run the command as requested and opened a new issue for gnome. The issue number is #216. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-07-03 (1147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
apport information ** Tags added: apport-collected ** Description changed: - I updated all packages from the update branch and in the last week or - two the pdfs on my desktop are displayed incorrectly and stretched out. - It appears that I did not have the bug prior to the fix, but have it now - that I have updated to the new package version. + I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2017-07-03 (1147 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago) + UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp video + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1892276/+attachment/5403970/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: I updated all packages from the update branch and in the last week or two the pdfs on my desktop are displayed incorrectly and stretched out. It appears that I did not have the bug prior to the fix, but have it now that I have updated to the new package version. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-07-03 (1147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-desktop-icons 20.04.0-3~ubuntu20.04.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (118 days ago) UserGroups: adbusers adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1312376] Re: touch screen in browser not scrolling
Sounds like this is fixed by the same change as bug 1697122. ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-81 fixed-upstream -- 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/1312376 Title: touch screen in browser not scrolling Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Committed Bug description: Hi team, I wanted to highlight a problem with my touch screen laptop not scrolling on touch. It doesn't grab and scroll but highlights the text in the browser. Please feel free to ask for more information as I am more than happy to help! thanks Morlando To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1312376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
This is probably related to bug 1892440. ** Tags added: regression-release xrandr-scaling ** Tags removed: regression-release ** Tags added: regression-update -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Possibly also the same issue: bug 1892521. -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892569] Re: Font scaling not working correctly 20.04
*** This bug is a duplicate of bug 1892521 *** https://bugs.launchpad.net/bugs/1892521 Nevermind, we can just make this a duplicate of bug 1892521. ** This bug has been marked a duplicate of bug 1892521 UI bug - system fonts enlarge after every reboot -- 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/1892569 Title: Font scaling not working correctly 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892569] Re: Font scaling not working correctly 20.04
*** This bug is a duplicate of bug 1892521 *** https://bugs.launchpad.net/bugs/1892521 This is probably related to bug 1892440. Please either subscribe to that or provide more information about your system by running: apport-collect 1892569 ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892569 Title: Font scaling not working correctly 20.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867668] Re: Visual artifacts in Gnome Shell when using the 'intel' Xorg driver
Also confirming that removing xserver-xorg-video-intel solved the problem for me too. I did not also have /etc/X11/xorg.conf.d/20-intel.conf. However, I did have /etc/X11/xorg.conf.d/01-amdgpu-pro-px.conf which was trying to load the intel driver that was just removed: jsalvo@rig01:~$ cat ~/xorg.conf.d-01-amdgpu-pro-px.conf Section "ServerFlags" Option "AutoAddGPU" "off" EndSection Section "Device" Identifier "Intel" Driver "intel" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" EndSection Have to remove that file as well and then also do a: sudo apt purge xserver-xorg-video-amdgpu-pro ... as the amdgpu-pro was installed when it was on 16.04 LTS, before the upgrade to 20.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell when using the 'intel' Xorg driver Status in xserver-xorg-video-intel package in Ubuntu: Won't Fix Bug description: I've updated to Ubuntu 20.04 a couple of weeks ago, and there are some minor (but pretty annoying) issues with Gnome Shell every time I load the system. The background image has some green/violet/black visual artifacts, and the text elements in Gnome Shell incorrectly display some of the symbol. Changing the background image removes the artifacts until the next reboot (but if I select the previous one without rebooting, then I still see the same artifacts, so it's probably cached somewhere). Restarting the shell via Alt+F2 `r` usually removes the artifacts from the background image, but the text issues are still present. The issues are reprodicable with and without extensions, with 1.0, 1.5 and 2.0 display scaling factors applied, and they are not user- specific (i.e. I was able to reproduce them after creating a new user from scratch) As far as I can say, only Gnome Shell is affected. All the applications (including Gnome/GTK apps like Geary, Gedit, Tilix, both "native" and flatpak) work fine without any issues Sometimes, the application icons are also affected (as you can see on one of the attached screenshots) ~> lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ~> apt-cache policy gnome-shell gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ~> gsettings get org.gnome.mutter experimental-features ['x11-randr-fractional-scaling'] ~> uname -r 5.4.0-14-generic hwinfo (videocard, monitor): 38: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.pq3kk9M9L4C SysFS ID: /devices/pci:00/:00:02.0 SysFS BusID: :00:02.0 Hardware Class: graphics card Model: "Intel UHD Graphics 620" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x5917 "UHD Graphics 620" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x225c Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0x2ffa00-0x2ffaff (rw,non-prefetchable) Memory Range: 0x2fa000-0x2fafff (ro,non-prefetchable) I/O Ports: 0xe000-0xe03f (rw) Memory Range: 0x000c-0x000d (rw,non-prefetchable,disabled) IRQ: 161 (64308 events) Module Alias: "pci:v8086d5917sv17AAsd225Cbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown 43: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.R7Dpg_aaVOC Parent ID: _Znp.pq3kk9M9L4C Hardware Class: monitor Model: "LG Display LCD Monitor" Vendor: LGD "LG Display" Device: eisa 0x058b Resolution: 2560x1440@60Hz Size: 309x174 mm Year of Manufacture: 2016 Week of Manufacture: 0 Detailed Timings #0: Resolution: 2560x1440 Horizontal: 2560 2608 2640 2720 (+48 +80 +160) -hsync Vertical: 1440 1450 1455 1481 (+10 +15 +41) +vsync Frequencies: 241.69 MHz, 88.86 kHz, 60.00 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (VGA compatible controller) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-11-07 (130 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: third-party-packages focal U
[Desktop-packages] [Bug 1892521] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403963/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403964/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] apport information
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-01-29 (572 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-06-27 (57 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403965/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892580] Re: [HDA-Intel - HDA Intel, playback] No sound at all
please set the active profile to: output:analog-stereo: Analog Stereo Output (priority 6500, available: unknown) And make sure the Default sink name: is alsa_output.pci-_00_05.0 .analog-output. -- 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/1892580 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Linux Ubuntu 20.04 via VirtualBox but am encountering no sound. My primary laptop does have sound but when I run Ubuntu via VirtualBox, there is no sound. Did have sound initially when I first installed Ubuntu but audio went out after I installed updates. Tried installing Alsamixer and PulseAudio Volume Control but both could not fix issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Aug 22 03:12:44 2020 InstallationDate: Installed on 2020-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892580] Re: [HDA-Intel - HDA Intel, playback] No sound at all
using 'pacmd set-card-profile' -- 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/1892580 Title: [HDA-Intel - HDA Intel, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Linux Ubuntu 20.04 via VirtualBox but am encountering no sound. My primary laptop does have sound but when I run Ubuntu via VirtualBox, there is no sound. Did have sound initially when I first installed Ubuntu but audio went out after I installed updates. Tried installing Alsamixer and PulseAudio Volume Control but both could not fix issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Aug 22 03:12:44 2020 InstallationDate: Installed on 2020-08-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jtm1625 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1892580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892657] [NEW] boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
Public bug reported: This may relate to https://gitlab.freedesktop.org/bolt/bolt/-/issues/156 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bolt 0.8-4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:32:55 2020 InstallationDate: Installed on 2019-05-02 (479 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: bolt UpgradeStatus: Upgraded to focal on 2020-04-23 (121 days ago) ** Affects: bolt (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 bolt in Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd Status in bolt package in Ubuntu: New Bug description: This may relate to https://gitlab.freedesktop.org/bolt/bolt/-/issues/156 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bolt 0.8-4 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:32:55 2020 InstallationDate: Installed on 2019-05-02 (479 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: bolt UpgradeStatus: Upgraded to focal on 2020-04-23 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889784]
This is happened to me when `widget.wayland-dmabuf-vaapi.enabled` is set to **True** -- 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/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878974] Re: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues
In my case the solutions from neither comment 14 nor 16 helped. Scanner started working only after completely removing HPLIP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1878974 Title: Unable to use HP USB Printer in Ubuntu 20.04 - apear to be hplip issues Status in HPLIP: New Status in hplip package in Ubuntu: Incomplete Bug description: Hi, I am unable to connect and print with a HP USB Pinter on Ubuntu 20.04, Spent some time troubleshooting with the default (previously current) drivers hplip ver. 3.20.3 , but Ubuntu 20.04 does not seem to be supported officially due to missing dependencies. Errors about missing pyqt4 dependencies among others. When using the hplip ver. 3.20.3 from the Ubuntu Repo printer is found but fails to print. Just noticed similar bug filed, 690720 , and saw note that new hplip ver. 3.20.5 was just released and supports Ubuntu 20.04 When trying to install new package hplip ver. 3.20.5 with the .run script provided by HP I am unable to complete installatoin as it reports unmet dependency of pyqt5 , even though package python3-pyqt5 is installed on system. https://developers.hp.com/hp-linux-imaging-and-printing/gethplip Maybe the repo just needs to be updated with a newer build (3.20.5) to install on my system, or is there something that can be done in the meantime. Below hp-check -t when using the repo hplip ver. 3.20.3 , == Saving output in log file: /root/hp-check.log HP Linux Imaging and Printing System (ver. 3.20.3) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-20.04 version is not supported. Using ubuntu-19.10 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Host: judith-mini Proc: 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 GNU/Linux Distribution: ubuntu 20.04 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.20.3 HPLIP-Home: /usr/share/hplip warning: HPLIP-
Re: [Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I just did apt update && apt upgrade Now fractional scaling is working. ubuntu 20.04 nvidia 1070ti nvidia-driver-440 On Sun, Aug 23, 2020 at 12:30 AM OB <1870...@bugs.launchpad.net> wrote: > How do I install the patch? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1870736 > > Title: > [nvidia] Screen scaling 125% gives 200% > > Status in gnome-control-center package in Ubuntu: > Confirmed > Status in mutter package in Ubuntu: > Confirmed > > Bug description: > Procedure used: > 1. > Fully updated system via apt update && apt upgrade > > 2. > Select the screen setup in gnome control center > > 3. > Click the "Fractional scaling" toggle > > 4. > Select 125% and click the green "use" button top right (it says "Anvend" > in dansih) > > 5. > Observe that the window has grown a lot, click the "use new settings" > button > > 6. > The window tells me, I am at 200% scaling. The "200%" option is now > highlighted. > > 7. > Switch back to 100% and file this bug. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.16 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu22 > Architecture: amd64 > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Sat Apr 4 09:42:34 2020 > InstallationDate: Installed on 2018-01-14 (810 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=da_DK.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > Symptom: release-upgrade > UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions > -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892647] [NEW] gnome-screensaver can be failed into a locked state.
Public bug reported:
When the screen is locked, you can freeze the screensaver application by
holding escape and scrolling up to activate the unlock screen with the
mouse. 'authentication error' pops up and the password input {widget?}
is non-responsive.
this isn't likely to pose a problem, but I will poke at it a bit and if
I see an issue with commands running with the user's privilege I will
let you know.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 23 13:14:59 2020
InstallationDate: Installed on 2019-07-05 (415 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1892647
Title:
gnome-screensaver can be failed into a locked state.
Status in gnome-screensaver package in Ubuntu:
New
Bug description:
When the screen is locked, you can freeze the screensaver application
by holding escape and scrolling up to activate the unlock screen with
the mouse. 'authentication error' pops up and the password input
{widget?} is non-responsive.
this isn't likely to pose a problem, but I will poke at it a bit and
if I see an issue with commands running with the user's privilege I
will let you know.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 23 13:14:59 2020
InstallationDate: Installed on 2019-07-05 (415 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1892647/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
** Bug watch added: Debian Bug tracker #968909 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968909 ** Also affects: libgweather (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968909 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: New Status in libgweather package in Debian: Unknown Bug description: Please update libgweather to 3.36.1 to fix the unavailability of current temperature in some locations. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.1 == This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
same here , affects both the initial login screen as well as my desktop. ** Tags added: apport-collected focal ** Description changed: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-05-21 (94 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: nvidia_modeset nvidia + Package: mutter 3.36.4-0ubuntu0.20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403928/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403930/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892521/+attachment/5403929/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892605] Re: Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gnome
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 No, but its a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 ** This bug has been marked a duplicate of bug 1892440 [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards -- 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/1892605 Title: Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gnome is shrinked. Status in mutter package in Ubuntu: New Bug description: Already tried to install the nvidia 390 driver from nvidias .run installer, but this is also not running without the use of nouveau and log in to 'Ubuntu on Wayland'. The problem is that the scaling has become abnormal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 02:10:51 2020 InstallationDate: Installed on 2020-04-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892643] [NEW] [SRU] Update libgweather to 3.36.1
Public bug reported: Please update libgweather to 3.36.1 to fix the unavailability of current temperature in some locations. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.1 == This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libgweather Importance: Unknown Status: Unknown ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: gitlab.gnome.org/GNOME/libgweather/-/issues #44 https://gitlab.gnome.org/GNOME/libgweather/-/issues/44 ** Also affects: libgweather via https://gitlab.gnome.org/GNOME/libgweather/-/issues/44 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: New Bug description: Please update libgweather to 3.36.1 to fix the unavailability of current temperature in some locations. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.1 == This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892642] [NEW] liveptch indicator icon is broken
Public bug reported: See the attached screenshot, it speaks for itself ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Aug 23 18:58:13 2020 InstallationDate: Installed on 2013-10-11 (2507 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-07-12 (41 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Screenshot from 2020-08-23 18-37-56.png" https://bugs.launchpad.net/bugs/1892642/+attachment/5403909/+files/Screenshot%20from%202020-08-23%2018-37-56.png -- 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/1892642 Title: liveptch indicator icon is broken Status in ubuntu-meta package in Ubuntu: New Bug description: See the attached screenshot, it speaks for itself ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop 1.450.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sun Aug 23 18:58:13 2020 InstallationDate: Installed on 2013-10-11 (2507 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-07-12 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1892642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
Hi, This also affects the initial login screen. PFA screenshot. Thanks, Nitin ** Attachment added: "IMG_20200823_215703_LL.jpg" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+attachment/5403908/+files/IMG_20200823_215703_LL.jpg -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
Hi, I am facing similar issue. Please check the attached screenshot. Thanks, Nitin ** Attachment added: "Screenshot from 2020-08-23 21-57-29.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+attachment/5403907/+files/Screenshot%20from%202020-08-23%2021-57-29.png -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3
** Changed in: simple-scan (Ubuntu) Status: Confirmed => Fix Released ** Changed in: simple-scan (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1883819 Title: Update to 3.36.3 Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Focal: Fix Committed Bug description: [ Description ] GNOME upstream have released a new stable version of simple-scan. Overview of changes in simple-scan 3.36.3 * Change the size of the paper to avoid visual glitches. * Disable possibility of scanning if no device is found, to avoid unnecessary errors. Overview of changes in simple-scan 3.36.2.1 * Revert the higher bit depth text scans changes - they aren't working with PDF saving. Overview of changes in simple-scan 3.36.2 * Use higher bit depth on text scans. * Fix size of first page on second scan. * Don't interrupt scanning if the device is busy. * Support saving files to FUSE file systems. * Update known USB scanner IDs. * Add initial Lexmark printers support. * Add ADF duplex support for Brother DS-720. * Fix setting source for Epson scanner. Overview of changes in simple-scan 3.36.1 * Stop disabling compression to fix slow scanning [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could break existing functionality. Issue would be confined to simple-scan app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892626] Re: Random system freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892626 Title: Random system freeze Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892626/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892626] [NEW] Random system freeze
You have been subscribed to a public bug: Ubuntu 20.04.1 LTS x86_64 randomly freezing. Often when using browser (Firefox or Vivaldi) or email client (Thunderbird). Have to reboot to restart. Can occur several times a day. Didn't have problem with 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Regolith:GNOME-Flashback:GNOME Date: Sun Aug 23 14:08:35 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710] InstallationDate: Installed on 2020-06-14 (69 days ago) InstallationMedia: Regolith 20.04.0 1.4.1 LTS amd64 (20200511) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgregolith-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0903 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0903:bd10/25/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- Random system freeze https://bugs.launchpad.net/bugs/1892626 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892605] Re: Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gnome
probably a duplicate of bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521 please check and mark duplicate if you feel its the same bug thank you! -- 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/1892605 Title: Since mutter updated to 3.36.4-0ubuntu0.20.04.2, the nvidia-390 driver package from apt does not work properly. On every start the top panel and font size in gnome is shrinked. Status in mutter package in Ubuntu: New Bug description: Already tried to install the nvidia 390 driver from nvidias .run installer, but this is also not running without the use of nouveau and log in to 'Ubuntu on Wayland'. The problem is that the scaling has become abnormal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 02:10:51 2020 InstallationDate: Installed on 2020-04-24 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
Please complete the bug with apport-collect 1892521 from terminal, to import relevant info of your system so the developers can debug a better way. -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892637] [NEW] Printing a blank page with libreoffice on Lubuntu 20.04
Public bug reported: Hello maintainer, Printing from libreoffice on Lubuntu 20.04 allways produces a blank page. After removing the package libreoffice-qt5 it works. To reproducing the bug, you do not need to install a real printer. Having the package printer-driver-cups-pdf install is enough. Release Lubuntu 20.04.1 LTS libreoffice-qt5 1:6.4.5-0ubuntu0.20.04.1 Regards Reiner ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892637 Title: Printing a blank page with libreoffice on Lubuntu 20.04 Status in libreoffice package in Ubuntu: New Bug description: Hello maintainer, Printing from libreoffice on Lubuntu 20.04 allways produces a blank page. After removing the package libreoffice-qt5 it works. To reproducing the bug, you do not need to install a real printer. Having the package printer-driver-cups-pdf install is enough. Release Lubuntu 20.04.1 LTS libreoffice-qt5 1:6.4.5-0ubuntu0.20.04.1 Regards Reiner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892636] [NEW] The Files 3.36.3 directory search fails
Public bug reported: does not find keywords in PDFA1.b - files when searching the directory. In one file, it works, and on my old windows system, it works with the same files and keywords. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:20:15 2020 InstallationDate: Installed on 2020-05-22 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** 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/1892636 Title: The Files 3.36.3 directory search fails Status in nautilus package in Ubuntu: New Bug description: does not find keywords in PDFA1.b - files when searching the directory. In one file, it works, and on my old windows system, it works with the same files and keywords. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:20:15 2020 InstallationDate: Installed on 2020-05-22 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892634] [NEW] WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead
Public bug reported: File /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf contains "type=xlocal" but this gives "WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead" in lightdm.log. ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1892634 Title: WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead Status in nvidia-prime package in Ubuntu: New Bug description: File /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf contains "type=xlocal" but this gives "WARNING: Seat type 'xlocal' is deprecated, use 'type=local' instead" in lightdm.log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1892634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892620] Re: power management incorrect wifi & bluetooth power off handling
Added package affected: gnome-control-center 3.36.2 ** Package changed: ubuntu => gnome-control-center (Ubuntu) -- 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/1892620 Title: power management incorrect wifi & bluetooth power off handling Status in gnome-control-center package in Ubuntu: New Bug description: Releases: Ubuntu 20.04, Ubuntu 20.04.1 Hardware: HP ProBook 4540s When in Power Management, there are 2 slider button options (my own translation from Polish): Enable Wifi power off for energy saving Enable Bluetooth power off for energy saving But they seem to be directly disabling these modules, instead of only changing the power saving feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892620] [NEW] power management incorrect wifi & bluetooth power off handling
You have been subscribed to a public bug: Releases: Ubuntu 20.04, Ubuntu 20.04.1 Hardware: HP ProBook 4540s When in Power Management, there are 2 slider button options (my own translation from Polish): Enable Wifi power off for energy saving Enable Bluetooth power off for energy saving But they seem to be directly disabling these modules, instead of only changing the power saving feature. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- power management incorrect wifi & bluetooth power off handling https://bugs.launchpad.net/bugs/1892620 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
autopkgtests regression isn't triggered by this SRU, alsa-lib only put the device in to S/PDIF blacklist, not behavioral change. -- 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/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886672] Re: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes re
Apologies for the delayed reply. I've done some additional testing, including the Wayland session. Here my findings: removed .config/monitors.xml and .config/monitors.xml~ unplugged monitor cable, unplugged monitor power shutdown > start-up Set display preferences for single/laptop screen shutdown > start-up plugged in monitor power plugged in monitor to laptop - no change - opened display settings monitor starts up as second screen changed settings as needed for both screens > apply > keep settings second monitor switches off shutdown and restart > second monitor on and with correct settings lock screen > wait for second monitor to go back to sleep -- correct behaviour resumes -- wake screen > both monitors resume as expected suspend machine > resume > both monitors resume as expected -- END-- unplug second monitor > single/laptop display resumes correctly plug second monitor back in, display remains unchanged (laptop/single only) unplug second monitor suspend laptop plug in second monitor resume laptop, second monitor remains off logout login screen displayed with second screen now enabled login display resets to multiple display desktop but second screen remains off remove second screen > display resets correctly to single laptop screen shutdown --- correct behaviour resumes -- plugin in second monitor start both screens active including login login both screens working as expected lock screen > all screens suspend move mouse to active screens > both resume and can login suspend suspend machine > resume > both monitors resume as expected suspend > unplug second monitor > resume > single display/laptop works as expected -- END -- suspend > plugin in second monitor > resume > display remains in "single" mode > second monitor remains off restart gnome-shell (Alt+F2 > r) display resets to correct two display setup with second monitor on lock screen > monitor suspend > move mouse to activate screens > only laptop screen wakes up shutdown --- correct behaviour resumes -- start both screens active including login login both screens working as expected lock screen > all screens suspend move mouse to active screens > both resume and can login suspend suspend machine > resume > both monitors resume as expected END TESTING Wayland - setup second display, all working as expected (lock screen and suspend resume work fine) remove second screen > screen resets to single display plug in second screen > no change open display settings > display settings do not recognise second screen logout login screen, both displays work login > both displays working as expected (lock screen and suspend resume work fine) suspend > remove second display > resume single display resets as expected suspend > add second screen > resume second screen remains off, display remains in 'single' display mode. logout login screen, both displays work login > both displays working as expected (lock screen and suspend resume work fine) END WAYLAND TESTING Thanks for the time and effort all. -- 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/1886672 Title: Second screen is not always made to awaken when using multiple displays. Desktop is multiple display, but only laptop screen is on while second screen sometimes remains off Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: New bug for me. Issue was fine till last week. I think this may be related to the following as it started happening shortly thereafter. I have XPS13 with second monitor, all working fine till I lock screen or suspend. Then my second monitor will not 'resume'. I.e. stays off. This behaviour started after (or shortly after) playing a wine game using Lutris to launch. Shutting game down and almost immediately hitting suspend on the laptop. Was rushing out. It's a wild shot in the dark but I think something got messed up / not saved correctly in this process. To get it working I need to unplug monitor (using USB-C > HDMI) > suspend > plug in monitor > resume and sometimes still need to open display settings before it 'kicks in'. Damn annoying. Hope someone can help :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Jul 7 16:44:52 2020 DistUpgraded: 2020-05-15 15:17:42,708 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest:
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
The problem is still here with Kubuntu 20.04 updated today for guest and host: clipboard works erratically and sometimes is bloked. The proposed solution don't work fr me because I need to copy from host and paste in guest. The only workaround I found is to use mate desktop in the guest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 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: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891461] Re: Add proper USB audio support for Lenovo ThinkStation P620
Open GNOME Control Center's sound tab: - USB Speaker is picked by default. - USB Headphone and USB Mic was automatically picked as soon as headset is plugged. - Automatically switch back to USB Speaker when headset is unplugged. - No useless S/PDIF profile listed. - Jack detection works on both front panel and rear panel. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1891461 Title: Add proper USB audio support for Lenovo ThinkStation P620 Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-lib source package in Groovy: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Lenovo ThinkStation P620 uses TRX4 board, which doesn't have PCI audio in its chipset. Instead, it's equipped with two USB audio devices, "Main", which is for internal speaker and front headset, and "Rear", which is for rear panel I/Os. However, both USB audio don't really work out of the box. Issues and fixes will be described together below. [Fix for alsa-lib] 1) Both USB audio devices don't have S/PDIF port, so we need to disable them: https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=464c2f8b61855cb22d61c4b232f74d6767fac5fb [Fix for alsa-ucm-conf] 2) PulseAudio doesn't assign the correct stream for "Main" device, audio output stays at "Speaker" after "Headset" is selected. So we need UCM to let PulseAudio understand correct stream assignment. In addition to that, in order to not let headset port availability invalidate speaker profile, we need two UCM profiles to separate "Speaker" and "Headset" logically: https://github.com/alsa-project/alsa-ucm-conf/pull/42 [Fix for PulseAudio] 3) USB audio devices, UAC v2 and v3, support jack detection (insertion control). However, PulseAudio doesn't monitor USB jack mixer controls, so jack detection doesn't work at userspace level. We need to let PulseAudio be aware those jacks: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/e153fb870618b1dcf65f6fce1667ea76acc5a28b 4) When a headset gets plugged, PulseAudio switches the profile from "Speaker" to "Headset" automatically. However, when headset gets unplugged, PulseAudio switch the profile from "Headset" to "HDMI", skipping the "Speaker" profile. We need to fix priorities for profiles that are created from UCM to avoid the problem: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/dd70c3c5890ce27b9ba4bd041dea4a01c3e1fc0f [Test] Under g-c-c's Sound tab, "Speaker", "Headphone", "S/PDIF", etc. profiles are all selectable. Sound comes out from speaker even if "Headphone" is chosen. Microphone is already selected though there's no microphone plugged. With the above fix all applied, open Gnome Control Center -> Sound tab. Sink "Speaker" is selected. Only "Speaker" and "HDMI" are in the drop down menu. Plug a headset to front port, "Headphone" and "Microphone" appears and automatically becomes default. Unplug the headset, sink switches back to "Speaker", and source switches to none. Plug line-in, line-out and microphone to the rear panel, jack detection works for all three ports, and they all work correctly. Unplug rear line-in, line-out or microphone makes the option in dropdown menu disappears. On other systems, nothing changed. [Regression Potential] For fix 1) and 2), The UCM in alsa-lib and alsa-ucm-conf strictly match kernel provided profile name, so no other device will be affected. For fix 3), if there are UAC v2/v3 devices claim to support jack detection but don't really support it, this will make the PulseAudio consider its availability to "no". AFAIK, the USB audios that have jack ports are mostly docking stations, which already have their own UCM profiles or PulseAudio profile-sets, so they are unaffected by this change. If we ever see this kind of regression, the proper fix is to disable jack detection from kernel side. For fix 4), if user depends on the old behavior (i.e. switch to another card while other profiles are still available), this will bring a behavioral change. However, all available profiles will still be available after the fix, so users can still be chose the preferred profile from the g-c-c dropdown menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1891461/+subscriptions
[Desktop-packages] [Bug 1889992] Re: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens
Software render is in use: OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes And there isn't a lot free memory: Info: Processes: 199 Uptime: 41m Memory: 1.85 GiB used: 891.8 MiB (46.9%) ** Package changed: linux (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1889992 Title: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens Status in mesa package in Ubuntu: Incomplete Bug description: I just did a fresh first-time install of Ubuntu on a Dell Inspirion 14 with no modifications apart from installing Canon printer drivers and no 3rd party peripherals. The desktop freezes spontaneously. When it freezes, the display freezes including the mouse pointer, and all keystrokes are unresponsive (can't even do ctrl-alt-F3 to get a tty). Forced power off is the only possible action. I think this is irrelevent, but I'll mention that (I think) the lockup only happens when I'm using VLC to play MythTV-served videos from the LAN. Nothing else is running.. not even a browser. I'm simply watching a video and out of the blue it hangs. After rebooting, I play the same video I was watching just before the hang, and finish watching without a freeze up. Which means there's no relation to the video data. $ inxi -Fxz System:Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Portable System: Dell product: Inspiron 14-3452 v: 4.0.7 serial: Mobo: Dell model: 0625M8 v: A00 serial: UEFI: Dell v: 4.0.7 date: 04/26/2016 Battery: ID-1: BAT0 charge: 33.6 Wh condition: 33.6/41.4 Wh (81%) model: Samsung SD DELL 07G075A status: Full CPU: Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 Speed: 1377 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 1034 2: 1139 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: i915 resolution: 1280x800~60Hz OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-42-generic Network: Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel port: e000 bus ID: 01:00.0 IF: wlp1s0 state: up mac: Drives:Local Storage: total: 29.12 GiB used: 8.75 GiB (30.0%) ID-1: /dev/mmcblk0 model: HBG4e size: 29.12 GiB Partition: ID-1: / size: 28.05 GiB used: 8.74 GiB (31.2%) fs: ext4 dev: /dev/mmcblk0p2 Sensors: System Temperatures: cpu: 52.0 C mobo: 47.0 C Fan Speeds (RPM): cpu: 3181 Info: Processes: 199 Uptime: 41m Memory: 1.85 GiB used: 891.8 MiB (46.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.17 inxi: 3.0.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1889992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892569] Re: Font scaling not working correctly 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892569 Title: Font scaling not working correctly 20.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: During log in screen and after all text on desktop is enlarged. (no accessibility settings are turned on) During log in, text scaling can be reset by turning on and off the text scaling accessibility option, however scaling after login is still messed up. After log in, manual reset of font scaling factor in gnome-tweak software is needed. Settings are not saved after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889992] [NEW] Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens
You have been subscribed to a public bug: I just did a fresh first-time install of Ubuntu on a Dell Inspirion 14 with no modifications apart from installing Canon printer drivers and no 3rd party peripherals. The desktop freezes spontaneously. When it freezes, the display freezes including the mouse pointer, and all keystrokes are unresponsive (can't even do ctrl-alt-F3 to get a tty). Forced power off is the only possible action. I think this is irrelevent, but I'll mention that (I think) the lockup only happens when I'm using VLC to play MythTV-served videos from the LAN. Nothing else is running.. not even a browser. I'm simply watching a video and out of the blue it hangs. After rebooting, I play the same video I was watching just before the hang, and finish watching without a freeze up. Which means there's no relation to the video data. $ inxi -Fxz System:Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Portable System: Dell product: Inspiron 14-3452 v: 4.0.7 serial: Mobo: Dell model: 0625M8 v: A00 serial: UEFI: Dell v: 4.0.7 date: 04/26/2016 Battery: ID-1: BAT0 charge: 33.6 Wh condition: 33.6/41.4 Wh (81%) model: Samsung SD DELL 07G075A status: Full CPU: Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 Speed: 1377 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 1034 2: 1139 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: i915 resolution: 1280x800~60Hz OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-42-generic Network: Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel port: e000 bus ID: 01:00.0 IF: wlp1s0 state: up mac: Drives:Local Storage: total: 29.12 GiB used: 8.75 GiB (30.0%) ID-1: /dev/mmcblk0 model: HBG4e size: 29.12 GiB Partition: ID-1: / size: 28.05 GiB used: 8.74 GiB (31.2%) fs: ext4 dev: /dev/mmcblk0p2 Sensors: System Temperatures: cpu: 52.0 C mobo: 47.0 C Fan Speeds (RPM): cpu: 3181 Info: Processes: 199 Uptime: 41m Memory: 1.85 GiB used: 891.8 MiB (46.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.17 inxi: 3.0.38 ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment focal -- Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens https://bugs.launchpad.net/bugs/1889992 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
The problem is not in firefox or mate, it's in gdebi-gtk, and specifically in GDebiGtk.py, line 619: os.execv(pkexec_cmd, pkexec_args+gdebi_args) This replaces the current process with a pkexec call. This is not a valid usage of pkexec, as pkexec requires the parent process to not be init (ppid!=1). To reproduce the issue without firefox, one can just run `setsid gdebi- gtk package.deb`. In a similar bug report for update-manager (LP: #1020115), this flag was used instead of os.execv: flags = GObject.SPAWN_DO_NOT_REAP_CHILD https://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/UpdateManager/backend/InstallBackendSynaptic.py#L63 Is gdebi still maintained by Ubuntu developers, or should we report this in Debian? Can we propose a patch similar to the update manager, or even just use a simple shell wrapper? ** Summary changed: - Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox + gdebi-gtk calls pkexec inappropriately ** No longer affects: firefox (Ubuntu) ** Project changed: ubuntu-mate => gdebi -- 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/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
How do I install the patch? -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
