[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
It's not choosing the lowest frequency. Lionel just chose that as a random example from your xrandr.txt. That same file shows the current mode is: 2560x1440 (0xbb) 241.500MHz +HSync +VSync *current +preferred -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
2560x1440 (0xbb) 241.500MHz +HSync +VSync *current +preferred h: width 2560 start 2608 end 2640 total 2720 skew0 clock 88.79KHz v: height 1440 start 1443 end 1448 total 1481 clock 59.95Hz -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
Thanks for all that. The first and biggest problem I can see is this USB device: Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Unfortunately Cambridge Silicon Radio dongles are unreliable and buggy for everyone. I had to learn that the hard way too... So I strongly recommend getting a different brand as a first step. The only remaining concern then is the other wireless dongles on the same machine: Logitech, Inc. LX-700 Cordless Desktop Receiver Valve Software Wireless Steam Controller If replacing the Bluetooth dongle with a non-Cambridge one does not solve the problem then I would try unplugging the above devices. And also moving away from other sources of 2.4GHz interference like wifi access points. But mostly I recommend avoiding dongles that have Cambridge Silicon Radio chips. They are known to cause all kinds of random failures. The only hard part is that you can't tell that's what they are until after you buy one and plug it in :( ** Summary changed: - pulseaudio bluetooth problems with profiles + [Cambridge Silicon Radio] Bluetooth has multiple connectivity issues ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1892814 Title: [Cambridge Silicon Radio] Bluetooth has multiple connectivity issues Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
But why does g-c-c choose the lowest frequency refresh instead of the highest? If I set the resolution to 1920x1080 using xrandr, it chooses the 60 Hz option: 1920x1080 60.00* 50.0059.9430.0025.0024.00 29.9723.98 which is this modeline: 1920x1080 (0xbc) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+attachment/5405336/+files/lspci.txt -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
but the problem happens with other bluetooth headsets as well -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
The headset is Avantree Audition -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
just to mention that with the same chip in 18.04 it wasn't that unstable -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems connecting
The other bluetooth bug is now here: https://bugs.launchpad.net/ubuntu/+bug/1893299 ** Description changed: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. - e..g Very frequently if I turn on the bluetooth headset and hit connect - on the bluetooth settings, it shows that it has connected, but my - headset turns off and the setting shows that it disconnects after 5-10 - seconds. This can happen multiple times. What makes it work for sure is - if the bluetooth headset is entered in pairing mode and then you try to - connect using the bluetooth settings - - please see the attached log. - --- - ProblemType: Bug - ApportVersion: 2.20.11-0ubuntu27.8 - Architecture: amd64 - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 20.04 - InstallationDate: Installed on 2019-12-08 (264 days ago) - InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) - NonfreeKernelModules: nvidia_modeset nvidia - Package: pulseaudio 1:13.99.1-1ubuntu3.6 - PackageArchitecture: amd64 - ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 - Tags: focal package-from-proposed - Uname: Linux 5.4.0-44-generic x86_64 - UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) - UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 07/02/2020 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: F20b - dmi.board.asset.tag: Default string - dmi.board.name: X570 AORUS ELITE - dmi.board.vendor: Gigabyte Technology Co., Ltd. - dmi.board.version: x.x - dmi.chassis.asset.tag: Default string - dmi.chassis.type: 3 - dmi.chassis.vendor: Default string - dmi.chassis.version: Default string - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: - dmi.product.family: X570 MB - dmi.product.name: X570 AORUS ELITE - dmi.product.sku: Default string - dmi.product.version: -CF - dmi.sys.vendor: Gigabyte Technology Co., Ltd. + A big problem comes when a bluetooth headset is connected. Sometimes it + does not show up as well in the sound settings or the wrong profile is + shown. Sometimes I try changing the profile it works, but other times it + does not alter anything - e.g. changing from hfp to a2dp shows the + change but the profile remains. If I switch settings tabs and go back to + sound settings the old profile remains. ** Summary changed: - pulseaudio bluetooth problems connecting + pulseaudio bluetooth problems with profiles -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems with profiles
** Attachment added: "lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+attachment/5405338/+files/lsusb.txt -- 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/1892814 Title: pulseaudio bluetooth problems with profiles Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. A big problem comes when a bluetooth headset is connected. Sometimes it does not show up as well in the sound settings or the wrong profile is shown. Sometimes I try changing the profile it works, but other times it does not alter anything - e.g. changing from hfp to a2dp shows the change but the profile remains. If I switch settings tabs and go back to sound settings the old profile remains. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893168] Re: groovy gnome-shell crash
Since people might get hit by this problem, I'm including a possible solution to it. WARNING, it will remove most of your packages (and install some) and their configuration. How to somewhat refresh Ubuntu by removing almost all packages and reinstalling ubuntu-desktop: 1. Download the attached file: leftpackages.list 2. Run the following lines in the folder where the leftpackagest.list file is located: rm minimum.list # make list of packages to remove which are not in leftpackages.list dpkg --get-selections | while read line; do if ! cat leftpackages.list | grep "$line" > /dev/null; then echo "$line" | sed -e 's/\([^e]\)install/\1deinstall/' >> minimum.list; else echo "$line" >> minimum.list; fi; done # mark those packages that should be removed sudo dpkg --set-selections < minimum.list # remove them sudo apt-get dselect-upgrade # remove their config sudo aptitude purge '~c' 3. Install ubuntu desktop: sudo apt install ubuntu-desktop --install-recommends ** Attachment added: "leftpackages.list" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893168/+attachment/5405337/+files/leftpackages.list -- 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/1893168 Title: groovy gnome-shell crash Status in gnome-shell package in Ubuntu: Invalid Bug description: How I produced the crash: * sudo service gdm3 stop * launch Xorg as root * open another tty * export DISPLAY=:0 * gnome-shell * CTRL-ALT-F1 to see gnome-shell, all I see is the mouse cursor blinks over a black background then stops blinking * when I go back to the previous terminal I see: $ gnome-shell Segmentation fault (core dumped) Restarting gdm3 doesn't produce the crash file but only produces a black screen with mouse pointer blinking initially. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0 Uname: Linux 5.8.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 12:19:38 2020 DisplayManager: ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1597769943 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport InstallationDate: Installed on 2015-09-28 (1794 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: gnome-shell ProcCwd: /root ProcEnviron: SHELL=/bin/bash LANGUAGE=en_PH:en LANG=en_PH.UTF-8 TERM=linux PATH=(custom, no user) RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 SegvAnalysis: Skipped: missing required field "Disassembly" ShellJournal: -- Logs begin at Thu 2020-08-27 11:28:20 PST, end at Thu 2020-08-27 12:20:01 PST. -- -- No entries -- Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
Still doesn't work for me after all updates，and there are side effects... Now every time I boot up, the Desktop's font is very small, even there is no external monitor...if ALT + F2 -> R, then restore :( libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://cn.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://cn.archive.ubuntu.com/ubuntu focal/main amd64 Packages +-+ | NVIDIA-SMI 440.64 Driver Version: 440.64 CUDA Version: 10.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce MX150 Off | :03:00.0 Off | N/A | | N/A 55CP0N/A / N/A |630MiB / 2002MiB | 7% Default | +---+--+--+ journalctl.log => restart,Desktop's font NG journalctl_r.log=> Alt+F2->r ,Desktop's font OK ** Attachment added: "journalctl.zip" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5405332/+files/journalctl.zip -- 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 1892814] Re: pulseaudio bluetooth problems connecting
Thanks. Please also mention the model of headphones/headset and run these commands so we can see what kind of wireless chip it is talking to: lspci -kv > lspci.txt lsusb > lsusb.txt And attach the resulting text files here. ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1892814 Title: pulseaudio bluetooth problems connecting Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red
I have been experiencing a similar problem with a GeForce 7300 GT on a Mac Pro 1,1. I also have visual artifacts in 18.04 and 20.04. With 18.04, there are no artifacts or other problems during installation from a DVD, but when booting the installed system there are artifacts after login and eventually programs start hanging. With 20.04, the installation program itself has artifacts when running off the DVD. Just did a clean install of 14.04.6 and that works fine. -- 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/1860483 Title: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: My desktop has both it's usual items in place; toolbar on left and desktop icons distributed around the screen. Then there's what appears to be a bunch of scan line, raster line artifacts, in red, laid over my normal background, which is a star field photo on what is ordinarily a black field. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 21 13:04:20 2020 DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405] InstallationDate: Installed on 2016-08-19 (1249 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 531 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago) dmi.bios.date: 11/09/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0RY206 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion: dmi.product.name: Inspiron 531 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 3 10:41:28 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputLogitech USB Trackball MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405327/+files/CurrentDmesg.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio bluetooth problems connecting
I submit the microphone bug as https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293 -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405328/+files/Dependencies.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405329/+files/ProcCpuinfoMinimal.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] Re: pulseaudio very unstable
apport information ** Description changed: - Pulseaudio has been super unstable since ubuntu 20.04. + Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. - Microphones randomly stop working until changing the active microphone multiple times. Today my mic stopped working 3 times. - Sometimes cannot switch bluetooth headset profiles. Or it says that it switched it but when you click on a different tab and go back, it reverts to the old setting. - I see some warnings/errors in the logs that could be related: - gsd-media-keys[2948]: Unable to get default sink - gsd-media-keys[2948]: Unable to get default source - - kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65 - - pulseaudio[2489]: q overrun, queuing locally + e..g Very frequently if I turn on the bluetooth headset and hit connect + on the bluetooth settings, it shows that it has connected, but my + headset turns off and the setting shows that it disconnects after 5-10 + seconds. This can happen multiple times. What makes it work for sure is + if the bluetooth headset is entered in pairing mode and then you try to + connect using the bluetooth settings please see the attached log. ** Summary changed: - pulseaudio very unstable + pulseaudio bluetooth problems connecting ** Tags added: apport-collected package-from-proposed ** Description changed: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-12-08 (264 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.1-1ubuntu3.6 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 + Tags: focal package-from-proposed + Uname: Linux 5.4.0-44-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/02/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F20b + dmi.board.asset.tag: Default string + dmi.board.name: X570 AORUS ELITE + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: X570 MB + dmi.product.name: X570 AORUS ELITE + dmi.product.sku: Default string + dmi.product.version: -CF + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405325/+files/AlsaInfo.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio
[Desktop-packages] [Bug 1892814] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405330/+files/ProcEnviron.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405326/+files/AudioDevicesInUse.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892814] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1892814/+attachment/5405331/+files/PulseList.txt -- 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/1892814 Title: pulseaudio bluetooth problems connecting Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. e..g Very frequently if I turn on the bluetooth headset and hit connect on the bluetooth settings, it shows that it has connected, but my headset turns off and the setting shows that it disconnects after 5-10 seconds. This can happen multiple times. What makes it work for sure is if the bluetooth headset is entered in pairing mode and then you try to connect using the bluetooth settings please see the attached log. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405322/+files/ProcCpuinfoMinimal.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405323/+files/ProcEnviron.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405324/+files/PulseList.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405321/+files/Dependencies.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405318/+files/AlsaInfo.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405319/+files/AudioDevicesInUse.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405320/+files/CurrentDmesg.txt -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893293/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893293] [NEW] pulseaudio microphone stops responding until toggling the input device
Public bug reported: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/02/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F20b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal package-from-proposed ** Attachment added: "journal_log_20200827_microphone_disconnecting.txt" https://bugs.launchpad.net/bugs/1893293/+attachment/5405317/+files/journal_log_20200827_microphone_disconnecting.txt ** Tags added: apport-collected focal package-from-proposed ** Description changed: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-12-08 (264 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.1-1ubuntu3.6 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 + Tags: focal package-from-proposed + Uname: Linux 5.4.0-44-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/02/2020 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F20b + dmi.board.asset.tag: Default string + dmi.board.name: X570 AORUS ELITE + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF20b:bd07/02/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: X570 MB + dmi.product.name: X570 AORUS ELITE + dmi.product.sku: Default string + dmi.product.version: -CF + dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1893293 Title: pulseaudio microphone stops responding until toggling the input device Status in pulseaudio package in Ubuntu: New Bug description: Very frequently my usb webcam's microphone stops working during a call and needs to be toggled as an input device several times until it starts working again. See the attached logs. This is on an up-to-date ubuntu 20.04. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-08 (264 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Tags: focal package-from-proposed Uname: Linux 5.4.0-44-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-24 (125 days ago)
[Desktop-packages] [Bug 1893265] Re: Double-click on a desktop app shortcut doesn't deselect the shortcut
Please report the issue to the developers at: https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues and then tell us the new issue ID. Please also run this command to gather more system info: apport-collect 1893265 and in future report bugs using the 'ubuntu-bug' command. ** Tags added: focal ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (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/1893265 Title: Double-click on a desktop app shortcut doesn't deselect the shortcut Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Ubuntu 20.04.1 GNOME 3.36.2 GNOME extensions: dash-to-panel 39 Xorg 7.7+19ubuntu14 Starting an app from its .desktop shortcut should deselect the shortcut icon after double-clicking on it, because it lets the user know that the double-click was registered (as opposed to a single click) and the application is starting. This makes a difference if the app is slow to start, since I'm not sure anymore whether I should double-click again or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1893265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893217] Re: display corruption
** Tags added: hybrid multi-gpu nvidia ** Summary changed: - display corruption + Display corruption with hybrid Intel+Nvidia GPUs ** Package changed: xorg (Ubuntu) => mutter (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/1893217 Title: Display corruption with hybrid Intel+Nvidia GPUs Status in mutter package in Ubuntu: New Bug description: my display doesnt work properly.it mostly gets clubbed with previous window i used in system. Even now while i m reporting the bug,i face the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: 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 27 18:10:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: built rtl8821ce, v5.5.2_34066.20200325, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX110] [103c:84a7] InstallationDate: Installed on 2020-08-26 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 011: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 (network tethering, USB debugging enabled) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-dr0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4cac576c-f749-447e-9180-b78666e12db6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 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.07:bd11/21/2018:svnHP:pnHPLaptop15g-dr0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-dr0xxx dmi.product.sku: 4ZD61PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/mutter/+bug/1893217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893065] Re: Gnome applications launching very slow
** Package changed: gnome-shell (Ubuntu) => libgphoto2 (Ubuntu) ** Also affects: gphoto2 via https://github.com/gphoto/gphoto2/issues/361 Importance: Unknown Status: Unknown ** Changed in: libgphoto2 (Ubuntu) Status: Incomplete => New ** Summary changed: - Gnome applications launching very slow + Gnome applications launching very slow due to gphoto2 services ** Changed in: libgphoto2 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1893065 Title: Gnome applications launching very slow due to gphoto2 services Status in gPhoto2: Unknown Status in libgphoto2 package in Ubuntu: New Bug description: Any time, into a fresh session or after any time of work, when I try to open any Gnome Application, including Nautilus, the app delay a lot of seconds (like 10 or more) to launch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 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 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 12:01:03 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'icon-theme' b"'Humanity'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2020-08-04 (21 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gphoto2/+bug/1893065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Icons and text corrupted and/or missing
Please run a memory test to check for physical RAM corruption using either: https://www.memtest86.com/ https://www.memtest.org/ That will take several hours. Please also try adding a line to your /etc/environment of the form: CLUTTER_PAINT=disable-offscreen-redirect and then reboot. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1886345 Title: Icons and text corrupted and/or missing Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
jonathan, Since this bug is closed, if you still have any problems then please open a new bug by running: ubuntu-bug gnome-shell-extension-desktop-icons -- 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Icons and text corrupted and/or missing
** Summary changed: - Display gets corrupted and text gets replaced by odd characters + Icons and text corrupted and/or missing ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Icons and text corrupted and/or missing Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893168] Re: groovy gnome-shell crash
OK, in that case we never need to know what was wrong. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1893168 Title: groovy gnome-shell crash Status in gnome-shell package in Ubuntu: Invalid Bug description: How I produced the crash: * sudo service gdm3 stop * launch Xorg as root * open another tty * export DISPLAY=:0 * gnome-shell * CTRL-ALT-F1 to see gnome-shell, all I see is the mouse cursor blinks over a black background then stops blinking * when I go back to the previous terminal I see: $ gnome-shell Segmentation fault (core dumped) Restarting gdm3 doesn't produce the crash file but only produces a black screen with mouse pointer blinking initially. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0 Uname: Linux 5.8.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 12:19:38 2020 DisplayManager: ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1597769943 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport InstallationDate: Installed on 2015-09-28 (1794 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: gnome-shell ProcCwd: /root ProcEnviron: SHELL=/bin/bash LANGUAGE=en_PH:en LANG=en_PH.UTF-8 TERM=linux PATH=(custom, no user) RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 SegvAnalysis: Skipped: missing required field "Disassembly" ShellJournal: -- Logs begin at Thu 2020-08-27 11:28:20 PST, end at Thu 2020-08-27 12:20:01 PST. -- -- No entries -- Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
on kernel 5.8.5 fedora 32,touchpad does not work too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug
[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
Fully aware that proposed is not supported, and that this may cause instability. Just trying to be helpful as per https://wiki.ubuntu.com/Testing/EnableProposed "Proposed updates are only for testing updates and providing development feedback. Enabling this may introduce instability." This bug report was intended to help provide development feedback. -- 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/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) Status in gnome-shell package in Ubuntu: Incomplete Status in libffi package in Ubuntu: Incomplete Bug description: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
** Attachment added: "ps_20200827.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405303/+files/ps_20200827.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
** Attachment added: "corrupted text in menus. corrupted icons in dash." https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405304/+files/IMG_20200827_184732%20%281%29.jpg -- 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/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
** Attachment added: "free_20200827.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405302/+files/free_20200827.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
Attached a photo of the right click menu and the dash. Attached the results of free -h > free.txt ps auxw > ps.txt ** Attachment added: "IMG_20200825_170044.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405293/+files/IMG_20200825_170044.jpg -- 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/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
** Attachment added: "free_20200825.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405294/+files/free_20200825.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886345] Re: Display gets corrupted and text gets replaced by odd characters
** Attachment added: "ps_20200825.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886345/+attachment/5405295/+files/ps_20200825.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~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/1886345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
I did that before getting this e-mail. Actually I deleted EVERYTHING relating to printing and scanning and installed hplip and other packages one at a time until things worked again. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Thu, 27 Aug 2020, Till Kamppeter wrote: > Date: Thu, 27 Aug 2020 14:20:41 - > From: Till Kamppeter <1871...@bugs.launchpad.net> > To: nan...@eskimo.com > Subject: [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd > conflict > > Please uninstall ippusbxd. Then your device should work with HPLIP > normally. ippusbxd wa supposed to allow driverless printing and scanning > without HPLIP. Unfortunately there were problems in its design. > > In Groovy we will replace ippusbxd by ipp-usb which finally allows > driverless printing and scanning without HPLIP to work reliably. > > See bug 1891157. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873748). > https://bugs.launchpad.net/bugs/1871011 > > Title: > USB scanning broken on focal --> hpmud and ippusbxd conflict > > Status in HPLIP: > Invalid > Status in hplip package in Ubuntu: > Expired > > Bug description: > On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. > > Previously there was a libmtp (udev) bug erroneously detecting HP > printers as mtp devices. This was fixed. Now, I can try to scan-- from > both simple-scan and hp-scan, hplip errors out: > > > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=1, altset=0, index=1 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=1 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface 7/1/2: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=0, altset=1, index=3 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=0 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface 7/1/4: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=3, altset=0, index=9 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=3 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface ff/4/1: Device or resource busy > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found > interface conf=0, iface=0, altset=0, index=11 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active > kernel driver on interface=0 ret=0 > Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid > claim_interface ff/cc/0: Device or resource busy > > Printer/scanner is an Officejet 4635. Scanning previously worked just > fine a few months ago. Regression? > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions > -- 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/1871011 Title: USB scanning broken on focal --> hpmud and ippusbxd conflict Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
I'm currently running the latest KDE Neon (based on Ubuntu 20.04) and no glitches so far even on Xorg. I can confirm that Fedora 32 also presented the same graphical artifacts on Xorg. Wayland Gnome sessions on both Ubuntu and Fedora were absent of glitches. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893277] Re: please provide an evince mailcap file
** Description changed: Hello; when I try to view PDFs from mutt, gimp is selected. Gimp is a very poor choice for viewing PDFs. I have evince installed, but evince is listed after gimp in my /etc/mailcap file. I tried to fix this by using the /etc/mailcap.order file but this failed: $ grep application/pdf /etc/mailcap application/pdf; gimp-2.10 %s; test=test -n "$DISPLAY" application/pdf; evince %s; test=test -n "$DISPLAY" $ cat /etc/mailcap.order ### # # Mailcap.order: This file allows a system-wide override of MIME program # preferences. See the mailcap.order(5) man page for more information. # # After modifying this file, be sure to run /usr/sbin/update-mime (as root) # to propagate the changes into the /etc/mailcap file. # qiv:image/* evince:application/pdf $ sudo update-mime Warning: package evince listed in /etc/mailcap.order does not have mailcap entries. $ dpkg -L evince | grep -i mailcap + $ dpkg -L evince-common | grep -i mailcap $ Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 22:02:01 2020 ProcEnviron: - TERM=rxvt-unicode-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=rxvt-unicode-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-01-24 (216 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1893277 Title: please provide an evince mailcap file Status in evince package in Ubuntu: New Bug description: Hello; when I try to view PDFs from mutt, gimp is selected. Gimp is a very poor choice for viewing PDFs. I have evince installed, but evince is listed after gimp in my /etc/mailcap file. I tried to fix this by using the /etc/mailcap.order file but this failed: $ grep application/pdf /etc/mailcap application/pdf; gimp-2.10 %s; test=test -n "$DISPLAY" application/pdf; evince %s; test=test -n "$DISPLAY" $ cat /etc/mailcap.order ### # # Mailcap.order: This file allows a system-wide override of MIME program # preferences. See the mailcap.order(5) man page for more information. # # After modifying this file, be sure to run /usr/sbin/update-mime (as root) # to propagate the changes into the /etc/mailcap file. # qiv:image/* evince:application/pdf $ sudo update-mime Warning: package evince listed in /etc/mailcap.order does not have mailcap entries. $ dpkg -L evince | grep -i mailcap $ dpkg -L evince-common | grep -i mailcap $ Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 22:02:01 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-01-24 (216 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1893277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
The deps are now out of date. At least mozjs68 has now moved. -- 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/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) Status in gnome-shell package in Ubuntu: Incomplete Status in libffi package in Ubuntu: Incomplete Bug description: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
also using groovy-proposed is not supported, as it contains incompatible mix of packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892915 Title: gnome-shell crashing (libffi8ubuntu1 upgrade issue) Status in gnome-shell package in Ubuntu: Incomplete Status in libffi package in Ubuntu: Incomplete Bug description: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893277] Re: please provide an evince mailcap file
Oh yes, this was reported by other people (though not in any useful way) at https://askubuntu.com/questions/1118437/promote-evince-in-etc- mailcap-order Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1893277 Title: please provide an evince mailcap file Status in evince package in Ubuntu: New Bug description: Hello; when I try to view PDFs from mutt, gimp is selected. Gimp is a very poor choice for viewing PDFs. I have evince installed, but evince is listed after gimp in my /etc/mailcap file. I tried to fix this by using the /etc/mailcap.order file but this failed: $ grep application/pdf /etc/mailcap application/pdf; gimp-2.10 %s; test=test -n "$DISPLAY" application/pdf; evince %s; test=test -n "$DISPLAY" $ cat /etc/mailcap.order ### # # Mailcap.order: This file allows a system-wide override of MIME program # preferences. See the mailcap.order(5) man page for more information. # # After modifying this file, be sure to run /usr/sbin/update-mime (as root) # to propagate the changes into the /etc/mailcap file. # qiv:image/* evince:application/pdf $ sudo update-mime Warning: package evince listed in /etc/mailcap.order does not have mailcap entries. $ dpkg -L evince | grep -i mailcap $ Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 22:02:01 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-01-24 (216 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1893277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893277] [NEW] please provide an evince mailcap file
Public bug reported: Hello; when I try to view PDFs from mutt, gimp is selected. Gimp is a very poor choice for viewing PDFs. I have evince installed, but evince is listed after gimp in my /etc/mailcap file. I tried to fix this by using the /etc/mailcap.order file but this failed: $ grep application/pdf /etc/mailcap application/pdf; gimp-2.10 %s; test=test -n "$DISPLAY" application/pdf; evince %s; test=test -n "$DISPLAY" $ cat /etc/mailcap.order ### # # Mailcap.order: This file allows a system-wide override of MIME program # preferences. See the mailcap.order(5) man page for more information. # # After modifying this file, be sure to run /usr/sbin/update-mime (as root) # to propagate the changes into the /etc/mailcap file. # qiv:image/* evince:application/pdf $ sudo update-mime Warning: package evince listed in /etc/mailcap.order does not have mailcap entries. $ dpkg -L evince | grep -i mailcap $ Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 22:02:01 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-01-24 (216 days ago) ** Affects: evince (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 evince in Ubuntu. https://bugs.launchpad.net/bugs/1893277 Title: please provide an evince mailcap file Status in evince package in Ubuntu: New Bug description: Hello; when I try to view PDFs from mutt, gimp is selected. Gimp is a very poor choice for viewing PDFs. I have evince installed, but evince is listed after gimp in my /etc/mailcap file. I tried to fix this by using the /etc/mailcap.order file but this failed: $ grep application/pdf /etc/mailcap application/pdf; gimp-2.10 %s; test=test -n "$DISPLAY" application/pdf; evince %s; test=test -n "$DISPLAY" $ cat /etc/mailcap.order ### # # Mailcap.order: This file allows a system-wide override of MIME program # preferences. See the mailcap.order(5) man page for more information. # # After modifying this file, be sure to run /usr/sbin/update-mime (as root) # to propagate the changes into the /etc/mailcap file. # qiv:image/* evince:application/pdf $ sudo update-mime Warning: package evince listed in /etc/mailcap.order does not have mailcap entries. $ dpkg -L evince | grep -i mailcap $ Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 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.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 22:02:01 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-01-24 (216 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1893277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888942]
>Ctrl-A still does not work works with Ubuntu Triple-Click works too. -- 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/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Incomplete Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'
** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css' Status in gnome-shell package in Ubuntu: New Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893271] [NEW] Space not freed after deleting files.
Public bug reported: I'm using Ubuntu 20.04 on installed on ZFS. Currently no matter how many files I delete the space isn't being freed so I cannot add new files. OS: Ubuntu 20.04.1 LTS x86_64 Host: Inspiron 13-7359 Kernel: 5.4.0-42-generic Uptime: 31 mins Packages: 2077 (dpkg), 66 (flatpak), 37 (snap) Shell: bash 5.0.17 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Adwaita-dark [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-6500U (4) @ 3.100GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 5290MiB / 7818MiB ** Affects: zsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1893271 Title: Space not freed after deleting files. Status in zsys package in Ubuntu: New Bug description: I'm using Ubuntu 20.04 on installed on ZFS. Currently no matter how many files I delete the space isn't being freed so I cannot add new files. OS: Ubuntu 20.04.1 LTS x86_64 Host: Inspiron 13-7359 Kernel: 5.4.0-42-generic Uptime: 31 mins Packages: 2077 (dpkg), 66 (flatpak), 37 (snap) Shell: bash 5.0.17 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Adwaita Theme: Adwaita-dark [GTK2/3] Icons: Yaru [GTK2/3] Terminal: gnome-terminal CPU: Intel i7-6500U (4) @ 3.100GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 5290MiB / 7818MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1893271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'
Sorry, I am new to using launchpad and marked it the status incorrectly. ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css' Status in gnome-shell package in Ubuntu: New Bug description: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893139] Re: Firefox 80 blocks flash
*** This bug is a duplicate of bug 1893021 *** https://bugs.launchpad.net/bugs/1893021 Apparently its fixed now, I Googled some and found 2 things to try to get rid of it. 1. Shutdown my system completely and boot fresh in the hope that Ubuntu would clear the file itself... (which it did for me it seems luckily) or 2. Take my Ubuntu SSD to a Windows PC and delete the file. (Not quite sure how that works unless you use LinuxReader or some other program to see the ext4 filesystem because I'm pretty sure Windows doesn't see it) -- 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/1893139 Title: Firefox 80 blocks flash Status in firefox package in Ubuntu: New Bug description: Up until last night I was using Firefox 79.0 on Ubuntu 16.04, I got an update to Firefox 80, now I can no longer play games on Kongregate as it seems all flash is blocked. I can still play Kongregate games in Chrome, but as Firefox is my main browser I wish to enable functionality in it once more or rollback to version 79, can anyone inform me how to go back to 79? I cannot even find my way to the repository for 79, only 80 is shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1893139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893233] Re: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826)
Thank you for your bug report, did you do a minimal install? ** Package changed: baobab (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1893233 Title: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826) Status in ubiquity package in Ubuntu: New Bug description: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
@Marco: The issue was caused by the fact that LP used an older (xenial) version of gettext. So as soon as they upgrade, it should be possible to drop the workaround. Can't tell if they have done that yet; easiest to ask Colin or William. -- 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/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: Confirmed Status in Ubuntu Translations: Triaged Status in gettext package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893265] [NEW] Double-click on a desktop app shortcut doesn't deselect the shortcut
Public bug reported: Ubuntu 20.04.1 GNOME 3.36.2 GNOME extensions: dash-to-panel 39 Xorg 7.7+19ubuntu14 Starting an app from its .desktop shortcut should deselect the shortcut icon after double-clicking on it, because it lets the user know that the double-click was registered (as opposed to a single click) and the application is starting. This makes a difference if the app is slow to start, since I'm not sure anymore whether I should double-click again or not. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "bug screencast" https://bugs.launchpad.net/bugs/1893265/+attachment/5405274/+files/out-1.ogv -- 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/1893265 Title: Double-click on a desktop app shortcut doesn't deselect the shortcut Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04.1 GNOME 3.36.2 GNOME extensions: dash-to-panel 39 Xorg 7.7+19ubuntu14 Starting an app from its .desktop shortcut should deselect the shortcut icon after double-clicking on it, because it lets the user know that the double-click was registered (as opposed to a single click) and the application is starting. This makes a difference if the app is slow to start, since I'm not sure anymore whether I should double-click again or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893110] Re: Cant remove desktop icons ubuntu 20.04
GNOME Flashback has builtin desktop icons! Only org.gnome.gnome- flashback.desktop settings control whether gnome-flashback shows or not desktop icons. "org.gnome.gnome-flashback.desktop show-icons false" shows that icons are disabled. :) If you still get icons you have some other application auto-started that provides desktop icons. From your GSettings list it could be nemo. Check if there is nemo and/or nemo-desktop process running. ** Package changed: metacity (Ubuntu) => gnome-flashback (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1893110 Title: Cant remove desktop icons ubuntu 20.04 Status in gnome-flashback package in Ubuntu: New Bug description: I've just upgraded to 20.04 from 18.04 and am having this issue using Gnome Flashback(metacity) desktop. The 'Home' and 'Trash' icons on my desktop continue to be there even after i have changed the settings using gsettings set the text below shows the output of gsettings list-recursively | grep icons -- i tried to add a screenshot but failed! edited to add screenshot link: https://imagizer.imageshack.com/img923/6561/LHeSfQ.png (base) matt@zakk-jr:~$ gsettings list-recursively | grep icons org.gnome.evolution.calendar show-icons-month-view false org.nemo.icon-view labels-beside-icons false org.gnome.gnome-flashback.desktop show-icons false org.cinnamon.desktop.interface menus-have-icons true org.cinnamon.desktop.interface buttons-have-icons false org.cinnamon.desktop.interface toolbar-icons-size 'large' org.gnome.gnome-flashback.desktop.icons icon-size '48px' org.gnome.gnome-flashback.desktop.icons column-spacing uint32 10 org.gnome.gnome-flashback.desktop.icons show-home false org.gnome.gnome-flashback.desktop.icons sort-by 'name' org.gnome.gnome-flashback.desktop.icons show-trash false org.gnome.gnome-flashback.desktop.icons placement 'free' org.gnome.gnome-flashback.desktop.icons row-spacing uint32 2 org.gnome.gnome-flashback.desktop.icons extra-text-width uint32 48 org.gnome.shell.extensions.openweather use-symbolic-icons true org.gnome.shell.extensions.topicons icon-size 24 org.gnome.shell.extensions.topicons icon-saturation 0.40002 org.gnome.shell.extensions.topicons tray-pos 'center' org.gnome.shell.extensions.topicons icon-contrast 0.0 org.gnome.shell.extensions.topicons icon-spacing 12 org.gnome.shell.extensions.topicons tray-order 1 org.gnome.shell.extensions.topicons icon-brightness 0.0 org.gnome.shell.extensions.topicons icon-opacity 220 org.gnome.desktop.background show-desktop-icons false org.gnome.desktop.interface menus-have-icons false org.gnome.desktop.interface buttons-have-icons false org.gnome.desktop.interface toolbar-icons-size 'large' org.gnome.shell.extensions.desktop-icons show-trash false org.gnome.shell.extensions.desktop-icons icon-size 'standard' org.gnome.shell.extensions.desktop-icons show-home false org.nemo.desktop show-desktop-icons false org.nemo.desktop show-orphaned-desktop-icons false org.gnome.gnome-panel.general prefer-symbolic-icons false I cant find any other settings that relate to this. If i create another user and use the metacity desktop the command gsettings set ortg.gnome,gnome.flashback.desktop show-icons false removes the icons, but not with my main user account further edit to show dconf-editor settings screenshot: https://imagizer.imageshack.com/img923/6079/l1CVh1.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1893110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893233] Re: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826)
Problem comes from ubiquity removing too much: Aug 27 14:10:53 ubuntu ubiquity: Removing baobab (3.34.0-1) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing branding-ubuntu (0.10) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing 'diversion of /usr/share/aisleriot/pixmaps/slot.svg to /usr/share/aisleriot/pixmaps/slot.svg.unbranded by branding-ubuntu'#015 Aug 27 14:10:53 ubuntu ubiquity: Removing 'diversion of /usr/share/aisleriot/pixmaps/baize.png to /usr/share/aisleriot/pixmaps/baize.png.unbranded by branding-ubuntu'#015 Aug 27 14:10:53 ubuntu ubiquity: Removing 'diversion of /usr/share/aisleriot/cards/bonded.svg to /usr/share/aisleriot/cards/bonded.svg.unbranded by branding-ubuntu'#015 Aug 27 14:10:53 ubuntu ubiquity: Removing 'diversion of /usr/share/gnome-mahjongg/themes/postmodern.svg to /usr/share/gnome-mahjongg/themes/postmodern.svg.unbranded by branding-ubuntu'#015 Aug 27 14:10:53 ubuntu ubiquity: Removing btrfs-progs (5.7-1) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing cheese (3.34.0-1build1) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing cifs-utils (2:6.10-0ubuntu1) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing cryptsetup-run (2:2.3.3-1ubuntu4) ...#015 Aug 27 14:10:53 ubuntu ubiquity: Removing cryptsetup-initramfs (2:2.3.3-1ubuntu4) ...#015 Aug 27 14:10:53 ubuntu ubiquity: update-initramfs: deferring update (trigger activated)#015 Aug 27 14:10:54 ubuntu ubiquity: Removing deja-dup (42.2-1ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing lvm2 (2.03.07-1ubuntu3) ...#015 Aug 27 14:10:54 ubuntu ubiquity: /usr/sbin/policy-rc.d returned 101, not running 'stop blk-availability.service lvm2-monitor.service'#015 Aug 27 14:10:54 ubuntu ubiquity: Running in chroot, ignoring request.#015 Aug 27 14:10:54 ubuntu ubiquity: invoke-rc.d: policy-rc.d denied execution of stop.#015 Aug 27 14:10:54 ubuntu ubiquity: Running in chroot, ignoring command 'daemon-reload'#015 Aug 27 14:10:54 ubuntu ubiquity: message repeated 2 times: [ Running in chroot, ignoring command 'daemon-reload'#015] Aug 27 14:10:54 ubuntu ubiquity: Removing dmraid (1.0.0.rc16-8ubuntu3) ...#015 Aug 27 14:10:54 ubuntu ubiquity: update-initramfs: deferring update (trigger activated)#015 Aug 27 14:10:54 ubuntu ubiquity: Removing duplicity (0.8.11.1612-1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing finalrd (5) ...#015 Aug 27 14:10:54 ubuntu ubiquity: /usr/sbin/policy-rc.d returned 101, not running 'stop finalrd.service'#015 Aug 27 14:10:54 ubuntu ubiquity: Running in chroot, ignoring command 'daemon-reload'#015 Aug 27 14:10:54 ubuntu ubiquity: Running in chroot, ignoring command 'daemon-reload'#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-de (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-es (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-fr (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-it (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-pt (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-ru (78.0.1+build1-0ubuntu1) ...#015 Aug 27 14:10:54 ubuntu ubiquity: Removing firefox-locale-zh-hans (78.0.1+build1-0ubuntu1) ...#015 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1893233 Title: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826) Status in baobab package in Ubuntu: New Bug description: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1893233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893110] Re: Cant remove desktop icons ubuntu 20.04
** Package changed: ubuntu => metacity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1893110 Title: Cant remove desktop icons ubuntu 20.04 Status in metacity package in Ubuntu: New Bug description: I've just upgraded to 20.04 from 18.04 and am having this issue using Gnome Flashback(metacity) desktop. The 'Home' and 'Trash' icons on my desktop continue to be there even after i have changed the settings using gsettings set the text below shows the output of gsettings list-recursively | grep icons -- i tried to add a screenshot but failed! edited to add screenshot link: https://imagizer.imageshack.com/img923/6561/LHeSfQ.png (base) matt@zakk-jr:~$ gsettings list-recursively | grep icons org.gnome.evolution.calendar show-icons-month-view false org.nemo.icon-view labels-beside-icons false org.gnome.gnome-flashback.desktop show-icons false org.cinnamon.desktop.interface menus-have-icons true org.cinnamon.desktop.interface buttons-have-icons false org.cinnamon.desktop.interface toolbar-icons-size 'large' org.gnome.gnome-flashback.desktop.icons icon-size '48px' org.gnome.gnome-flashback.desktop.icons column-spacing uint32 10 org.gnome.gnome-flashback.desktop.icons show-home false org.gnome.gnome-flashback.desktop.icons sort-by 'name' org.gnome.gnome-flashback.desktop.icons show-trash false org.gnome.gnome-flashback.desktop.icons placement 'free' org.gnome.gnome-flashback.desktop.icons row-spacing uint32 2 org.gnome.gnome-flashback.desktop.icons extra-text-width uint32 48 org.gnome.shell.extensions.openweather use-symbolic-icons true org.gnome.shell.extensions.topicons icon-size 24 org.gnome.shell.extensions.topicons icon-saturation 0.40002 org.gnome.shell.extensions.topicons tray-pos 'center' org.gnome.shell.extensions.topicons icon-contrast 0.0 org.gnome.shell.extensions.topicons icon-spacing 12 org.gnome.shell.extensions.topicons tray-order 1 org.gnome.shell.extensions.topicons icon-brightness 0.0 org.gnome.shell.extensions.topicons icon-opacity 220 org.gnome.desktop.background show-desktop-icons false org.gnome.desktop.interface menus-have-icons false org.gnome.desktop.interface buttons-have-icons false org.gnome.desktop.interface toolbar-icons-size 'large' org.gnome.shell.extensions.desktop-icons show-trash false org.gnome.shell.extensions.desktop-icons icon-size 'standard' org.gnome.shell.extensions.desktop-icons show-home false org.nemo.desktop show-desktop-icons false org.nemo.desktop show-orphaned-desktop-icons false org.gnome.gnome-panel.general prefer-symbolic-icons false I cant find any other settings that relate to this. If i create another user and use the metacity desktop the command gsettings set ortg.gnome,gnome.flashback.desktop show-icons false removes the icons, but not with my main user account further edit to show dconf-editor settings screenshot: https://imagizer.imageshack.com/img923/6079/l1CVh1.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1893110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893110] [NEW] Cant remove desktop icons ubuntu 20.04
You have been subscribed to a public bug: I've just upgraded to 20.04 from 18.04 and am having this issue using Gnome Flashback(metacity) desktop. The 'Home' and 'Trash' icons on my desktop continue to be there even after i have changed the settings using gsettings set the text below shows the output of gsettings list-recursively | grep icons -- i tried to add a screenshot but failed! edited to add screenshot link: https://imagizer.imageshack.com/img923/6561/LHeSfQ.png (base) matt@zakk-jr:~$ gsettings list-recursively | grep icons org.gnome.evolution.calendar show-icons-month-view false org.nemo.icon-view labels-beside-icons false org.gnome.gnome-flashback.desktop show-icons false org.cinnamon.desktop.interface menus-have-icons true org.cinnamon.desktop.interface buttons-have-icons false org.cinnamon.desktop.interface toolbar-icons-size 'large' org.gnome.gnome-flashback.desktop.icons icon-size '48px' org.gnome.gnome-flashback.desktop.icons column-spacing uint32 10 org.gnome.gnome-flashback.desktop.icons show-home false org.gnome.gnome-flashback.desktop.icons sort-by 'name' org.gnome.gnome-flashback.desktop.icons show-trash false org.gnome.gnome-flashback.desktop.icons placement 'free' org.gnome.gnome-flashback.desktop.icons row-spacing uint32 2 org.gnome.gnome-flashback.desktop.icons extra-text-width uint32 48 org.gnome.shell.extensions.openweather use-symbolic-icons true org.gnome.shell.extensions.topicons icon-size 24 org.gnome.shell.extensions.topicons icon-saturation 0.40002 org.gnome.shell.extensions.topicons tray-pos 'center' org.gnome.shell.extensions.topicons icon-contrast 0.0 org.gnome.shell.extensions.topicons icon-spacing 12 org.gnome.shell.extensions.topicons tray-order 1 org.gnome.shell.extensions.topicons icon-brightness 0.0 org.gnome.shell.extensions.topicons icon-opacity 220 org.gnome.desktop.background show-desktop-icons false org.gnome.desktop.interface menus-have-icons false org.gnome.desktop.interface buttons-have-icons false org.gnome.desktop.interface toolbar-icons-size 'large' org.gnome.shell.extensions.desktop-icons show-trash false org.gnome.shell.extensions.desktop-icons icon-size 'standard' org.gnome.shell.extensions.desktop-icons show-home false org.nemo.desktop show-desktop-icons false org.nemo.desktop show-orphaned-desktop-icons false org.gnome.gnome-panel.general prefer-symbolic-icons false I cant find any other settings that relate to this. If i create another user and use the metacity desktop the command gsettings set ortg.gnome,gnome.flashback.desktop show-icons false removes the icons, but not with my main user account further edit to show dconf-editor settings screenshot: https://imagizer.imageshack.com/img923/6079/l1CVh1.png ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Cant remove desktop icons ubuntu 20.04 https://bugs.launchpad.net/bugs/1893110 You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity 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 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d
Could we also add gettext to this bug so that we can monitor when it will be fixed on that side and thus remove the ubuntu workaround? ** Also affects: gettext (Ubuntu) Importance: Undecided Status: New ** Changed in: gettext (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/1756547 Title: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d Status in Launchpad itself: Confirmed Status in Ubuntu Translations: Triaged Status in gettext package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Released Bug description: Some strings of GNOME Shell are untranslated in the Czech translation on Ubuntu 18.04 although they are translated upstream and when I try to manually translate them on launchpad, I get this error: "number of format specifications in 'msgid_plural' and 'msgstr[0]' does not match". The bad strings are: %d minute ago %d minutes ago %d hour ago %d hours ago %d week ago %d weeks ago %d month ago %d months ago %d year ago %d years ago They seem to be correct, but they are not accepted for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Same here. Ubuntu 20.04 laptop HP 8540p. -- 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: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 Status in mutter package in Ubuntu: Confirmed Bug description: See also bug 1892521. 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 1892783] Re: [SRU] libreoffice 6.4.6 for focal
** Also affects: libreoffice (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Focal) Assignee: (unassigned) => Heather Ellsworth (hellsworth) ** Changed in: libreoffice (Ubuntu Focal) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Focal) Status: New => In Progress -- 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/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892783] Re: [SRU] libreoffice 6.4.6 for focal
** Changed in: libreoffice (Ubuntu) Status: Confirmed => In Progress ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- 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/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: In Progress Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893168] Re: groovy gnome-shell crash
It works with the daily-live/current iso. So I purge all packages until I get to the minimum ones (attached), removed almost all traces of gnome-shell and gdm3 from the file system, then run apt install ubuntu- desktop --install-recommends and when I reboot it works! ** Attachment added: "leftusr.list" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893168/+attachment/5405232/+files/leftusr.list -- 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/1893168 Title: groovy gnome-shell crash Status in gnome-shell package in Ubuntu: Incomplete Bug description: How I produced the crash: * sudo service gdm3 stop * launch Xorg as root * open another tty * export DISPLAY=:0 * gnome-shell * CTRL-ALT-F1 to see gnome-shell, all I see is the mouse cursor blinks over a black background then stops blinking * when I go back to the previous terminal I see: $ gnome-shell Segmentation fault (core dumped) Restarting gdm3 doesn't produce the crash file but only produces a black screen with mouse pointer blinking initially. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0 Uname: Linux 5.8.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 27 12:19:38 2020 DisplayManager: ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1597769943 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport InstallationDate: Installed on 2015-09-28 (1794 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: gnome-shell ProcCwd: /root ProcEnviron: SHELL=/bin/bash LANGUAGE=en_PH:en LANG=en_PH.UTF-8 TERM=linux PATH=(custom, no user) RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 SegvAnalysis: Skipped: missing required field "Disassembly" ShellJournal: -- Logs begin at Thu 2020-08-27 11:28:20 PST, end at Thu 2020-08-27 12:20:01 PST. -- -- No entries -- Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893233] Re: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826)
Other apps missing from ISO 20200826 but existing in ISO 20200714: < io.github.celluloid_player.Celluloid.desktop < libreoffice-calc.desktop < libreoffice-draw.desktop < libreoffice-impress.desktop < libreoffice-math.desktop < libreoffice-startcenter.desktop < libreoffice-writer.desktop < libreoffice-xsltfilter.desktop < org.gnome.baobab.desktop < org.gnome.Calendar.desktop < org.gnome.Cheese.desktop < org.gnome.ChromeGnomeShell.desktop < org.gnome.DejaDup.desktop < org.gnome.Extensions.desktop < org.gnome.Mahjongg.desktop < org.gnome.Mines.desktop < org.gnome.Sudoku.desktop < org.gnome.Todo.desktop < org.gnome.Totem.desktop < org.remmina.Remmina.desktop < remmina-file.desktop < remmina-gnome.desktop < rhythmbox.desktop < rhythmbox-device.desktop < shotwell.desktop < shotwell-viewer.desktop < simple-scan.desktop < sol.desktop < thunderbird.desktop < transmission-gtk.desktop < usb-creator-gtk.desktop < vino-server.desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1893233 Title: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826) Status in baobab package in Ubuntu: New Bug description: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1893233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886653] Re: cups-pki-expired
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886653] Re: cups-pki-expired
Same here. Newly installed Linux Mint 20 XFCE, Xerox 7225 printer. Driver installed, printing stops with "cups-pki-expired" message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Thanks, Looking at your xrandr.txt there is the modeline : 1920x1080 (0xc6) 74.176MHz +HSync +VSync h: width 1920 start 2558 end 2602 total 2750 skew0 clock 26.97KHz v: height 1080 start 1084 end 1089 total 1125 clock 23.98Hz That means the refresh rate accepted by your display should be : 74.176MHz / (2750 x 1125) = 23.9760808081 Hz Due to floating point error, in monitors.xml you get 23.976079940795898 Hz Maybe the issue comes from this ? -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893065] Re: Gnome applications launching very slow
Hi! After running nautilus from the command line, I received a log showing what is happening in my case. The problem is generated by the gphoto2 services. To fix it, I removed the service. After that, the Nautilus and Gnome applications that depend on file system services returned to work fine again. I have opened a issue in gphoto2 repositoy on Github for investigation and fix. The link with bug description is: https://github.com/gphoto/gphoto2/issues/361#issuecomment-681670207 ** Bug watch added: github.com/gphoto/gphoto2/issues #361 https://github.com/gphoto/gphoto2/issues/361 -- 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/1893065 Title: Gnome applications launching very slow Status in gnome-shell package in Ubuntu: Incomplete Bug description: Any time, into a fresh session or after any time of work, when I try to open any Gnome Application, including Nautilus, the app delay a lot of seconds (like 10 or more) to launch. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 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 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 12:01:03 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'icon-theme' b"'Humanity'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2020-08-04 (21 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.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/1893065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892136] Re: reverse prime produces corrupted output on specific resolutions
Managed to reproduce on fresh download 20.10, too. OTOH, I remember seeing that gone in some cases on 20.04. I wonder what the exact cases are, as apparently this seems more complicated than "reproduces always". ** Tags added: groovy -- 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/1892136 Title: reverse prime produces corrupted output on specific resolutions Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: In Progress Bug description: The issue has initially been discovered for resolution 1366x768 on a DisplayLink (evdi)-backed device, but applies also to UDL, as well as reverse prime setups (rendering on Intel, output through NVidia). The issue manifests with 1366x768 and several other resolutions only, due to the fact that the GPU seems to use 64-aligned framebuffer stride. This is "accidentally" fine with the most popular VGA resolutions (e.g. assuming 32bits/4bytes per pixel and FullHD, the stride would be 1920*4 -> 7680, which is divisible by 64 w/o a remainder, yet 1366*4=5464, 5464/64 = 85.375). The proposed fix is to update the stride with the GPU-provided value instead of the Xorg- calculated one at the stage of sharing the pixmap between GPUs. Doing that at earlier stage would probably require distinguishing between allocation of a FB and a generic pixmap, which is the same for Xorg. Issue for sure was seen on 18.04 and 19.04, probably still there for 20.04. Upstream report: https://gitlab.freedesktop.org/xorg/xserver/-/issues/889 And posted (not yet integrated) fix: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/496 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1892136/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 299261]
Oh, that was removed decades ago. It never should've been removed, because what aceman says makes sense. I preferred pre-tabs Thunderbird, and majority such changes have been annoying: I still wish I could just have one inbox (multiple movemail AND multiple POP3) which '"one' inbox' also means NO tabs opening EVER (sure, I disabled them, but they still open from various things)... got a bit off-topic now but I don't think wishes of users, to not have such changes forced, were addressed. So anyway, yes, please re-add the feature of global inbox for movemail (people I know who use IMAP would also like global inbox.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/299261 Title: movemail account does not work with global inbox Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird When setting up a movemail account in Thunderbird, the wizard provides the option to use the Global Inbox with the account. However, this type of account seems not to support the global inbox. To reproduce: - Create a new account of type 'Unix Mailspool (Movemail)'. In the wizard choose 'Use Global Inbox' (it is checked by default). - Send mail to yourself (verify that it arrived with ls -l /var/mail/) - Get mail for the movemail account Expected behaviour: - new messages from the /var/mail/username mailbox are moved to the global inbox under the Local Folders account. Observed behaviour: - Nothing happens, the Local Folders account does not even have an 'Inbox' folder. - Instead, messages are copied to the account-local inbox (.mozilla-thunderbird/.../Mail/localhost/Inbox). - In the movemail account settings, there is no option to control the use of the global inbox (as with POP accounts). Without the global inbox option reading mail works. Note: I have no other account configured which could make use of the global inbox (only IMAP accounts) -- in case this matters. thunderbird 2.0.0.17+nobinonly-0ubuntu1 Ubuntu 8.10 Intrepid ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.utf8 SHELL=/bin/tcsh SourcePackage: thunderbird Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/299261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 299261]
Don't remove it! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/299261 Title: movemail account does not work with global inbox Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird When setting up a movemail account in Thunderbird, the wizard provides the option to use the Global Inbox with the account. However, this type of account seems not to support the global inbox. To reproduce: - Create a new account of type 'Unix Mailspool (Movemail)'. In the wizard choose 'Use Global Inbox' (it is checked by default). - Send mail to yourself (verify that it arrived with ls -l /var/mail/) - Get mail for the movemail account Expected behaviour: - new messages from the /var/mail/username mailbox are moved to the global inbox under the Local Folders account. Observed behaviour: - Nothing happens, the Local Folders account does not even have an 'Inbox' folder. - Instead, messages are copied to the account-local inbox (.mozilla-thunderbird/.../Mail/localhost/Inbox). - In the movemail account settings, there is no option to control the use of the global inbox (as with POP accounts). Without the global inbox option reading mail works. Note: I have no other account configured which could make use of the global inbox (only IMAP accounts) -- in case this matters. thunderbird 2.0.0.17+nobinonly-0ubuntu1 Ubuntu 8.10 Intrepid ProblemType: Bug Architecture: i386 Dependencies: DistroRelease: Ubuntu 8.10 Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] PackageArchitecture: all ProcEnviron: LC_TIME=en_DK.utf8 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.utf8 SHELL=/bin/tcsh SourcePackage: thunderbird Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/299261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893236] [NEW] package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: I was trying to upgrade Can't locate Debian/DocBase/Common.pm in @INC (you may need to install the Debian::DocBase::Common module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/sbin/install-docs line 8. BEGIN failed--compilation aborted at /usr/sbin/install-docs line 8. dpkg: error processing package doc-base (--unpack): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_amd64.deb /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_i386.deb doc-base ProblemType: Package DistroRelease: Ubuntu 16.04 Package: doc-base 0.10.7 ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Thu Aug 27 17:37:49 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-08-23 (1100 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: doc-base Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: doc-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to doc-base in Ubuntu. https://bugs.launchpad.net/bugs/1893236 Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in doc-base package in Ubuntu: New Bug description: I was trying to upgrade Can't locate Debian/DocBase/Common.pm in @INC (you may need to install the Debian::DocBase::Common module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/sbin/install-docs line 8. BEGIN failed--compilation aborted at /usr/sbin/install-docs line 8. dpkg: error processing package doc-base (--unpack): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_amd64.deb /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_i386.deb doc-base ProblemType: Package DistroRelease: Ubuntu 16.04 Package: doc-base 0.10.7 ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Thu Aug 27 17:37:49 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-08-23 (1100 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: doc-base Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/1893236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893236] Re: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to doc-base in Ubuntu. https://bugs.launchpad.net/bugs/1893236 Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in doc-base package in Ubuntu: New Bug description: I was trying to upgrade Can't locate Debian/DocBase/Common.pm in @INC (you may need to install the Debian::DocBase::Common module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /usr/sbin/install-docs line 8. BEGIN failed--compilation aborted at /usr/sbin/install-docs line 8. dpkg: error processing package doc-base (--unpack): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_amd64.deb /var/cache/apt/archives/libc6_2.23-0ubuntu11.2_i386.deb doc-base ProblemType: Package DistroRelease: Ubuntu 16.04 Package: doc-base 0.10.7 ProcVersionSignature: Ubuntu 4.15.0-106.107~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Thu Aug 27 17:37:49 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2017-08-23 (1100 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SourcePackage: doc-base Title: package doc-base 0.10.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/doc-base/+bug/1893236/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
On my laptop, the fonts get larger each time. Temporary workaround which helps me is changing the font scale in Tweaks tool (Fractional Scaling doesn't help). Ubuntu 20.04.1 LTS Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8 Quadro K1000M/PCIe/SSE2 -- 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: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 Status in mutter package in Ubuntu: Confirmed Bug description: See also bug 1892521. 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 1893233] Re: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826)
corrado@corrado-n3-gg-0826:~$ apt policy baobab cheese baobab: Installed: (none) Candidate: 3.34.0-1 Version table: 3.34.0-1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages cheese: Installed: (none) Candidate: 3.34.0-1build1 Version table: 3.34.0-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages corrado@corrado-n3-gg-0826:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1893233 Title: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826) Status in baobab package in Ubuntu: New Bug description: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1893233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893233] [NEW] baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826)
Public bug reported: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: baobab (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to baobab in Ubuntu. https://bugs.launchpad.net/bugs/1893233 Title: baobab not installed by ISO Ubuntu 20.10 Alpha amd64 (20200826) Status in baobab package in Ubuntu: New Bug description: Installing from Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) Some applications (baobab, cheese..) are missing from usr/bin and usr/share/applications but some of their components are there ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: baobab (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 27 17:11:43 2020 InstallationDate: Installed on 2020-08-27 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826) SourcePackage: baobab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1893233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 304393] Re: rpcbind grabs ports used by other daemons such as cupsd
Hello Alvin, or anyone else affected, Accepted rpcbind into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rpcbind/0.2.3-0.2ubuntu0.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: rpcbind (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/304393 Title: rpcbind grabs ports used by other daemons such as cupsd Status in cups package in Ubuntu: Invalid Status in rpcbind package in Ubuntu: Fix Released Status in rpcbind source package in Xenial: Fix Committed Status in rpcbind source package in Bionic: Fix Released Status in rpcbind package in Debian: Fix Released Status in Fedora: Confirmed Bug description: [impact] rpcbind binds to a 'random' reserved port at startup, which can conflict with the reserved port number for other applications that actually 'own' the reserved port number. One example is cups, which uses the reserved port 631. This prevents the actual 'owner' of the reserved port from starting, since it can't bind to its reserved port. Additionally, this can raise alarms from security monitoring software that does not expect programs to be listening on random reserved ports. [test case] start rpcbind and check which ports it is listening on, e.g.: $ sudo netstat --inet -p -l | grep rpcbind | grep -v sunrpc udp0 0 0.0.0.0:614 0.0.0.0:* 4678/rpcbind each time rpcbind is restarted, it will be listening to a different 'random' port. [regression potential] this adds a way to disable rpcbind from listening to the 'random' port. any regression would likely prevent rpcbind from starting, or may cause problems with the interaction between rpcinfo and rpcbind, as rpcinfo may use the random reserved port in some cases, as detailed in the Debian bug. [scope] This is needed only for Bionic and earlier. In Focal and later, and in Debian, rpcbind defaults to not opening the random reserved port. The admin can use the -r parameter to cause rpcbind to restore the old behavior of opening the random reserved port. [other info] Note that the -r parameter is a Debian addition, and the upstream rpcbind has disabled the random port functionality at build time; there is no runtime parameter to allow the admin to choose the behavior. Also, as discussed in the Debian bug, disabling this rpcbind 'feature' is known to cause problems for the rpcinfo program, which is why Debian introduced the -r parameter. So, when this -r parameter is backported to Bionic and earlier, we must retain the default behavior for those releases, which is for rpcbind to open the random reserved port. Thus, the patch for this will first backport the upstream patch that adds functionality to be able to disable the 'remote calls' function, and also backports the debian patch to change that from a compile-time to run-time option. Then, another patch is added, which changes the default back to the behavior of x/b, which is for remote calls to be enabled by default, and also adds a check for the existence of an environment variable "RPCBIND_RMTCALL_DEFAULT_DISABLED" which, if defined (to anything), will change the default to disabled. This allows 1) retaining the existing default behavior of rpcbind in x and b, while also 2) providing a mechanism to change that default for anyone who does *not* want remote calls to be enabled, and 3) allowing the mechanism to change the default to remain in place after an upgrade to Focal. Using the environment variable allows anyone to disable the remote calls in x and/or b, and then upgrade
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
This is monitors.xml after changing to the (non-working) 1920x1080 configuration. It seems to have chosen a refresh rate of 23.976079940795898 Hz (is that the last option in xrandr's modeline "1920x1080 60.0050.0059.9430.0025.0024.00 29.9723.98"?). When I use xrandr to (successfully) change the resolution to 1920x1080, it chooses the 60 Hz option. ** Attachment added: "monitors-1920x1080.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405209/+files/monitors-1920x1080.xml -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
This is after changing to the (working) 2560x1440 resolution. ** Attachment added: "monitors-2560x1440.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405199/+files/monitors-2560x1440.xml -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards, auto-login will fail due to the old vt-handoff patch in grub2. [ Test Case ] 1. Boot ubuntu into desktop environment. 2. Enabled auto login in System->Users 3. Reboot the system [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Low, the patch just removes vt.handoff part in grub2 package, and I can't find any regression in several runs of stress tests. PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1871011] Re: USB scanning broken on focal --> hpmud and ippusbxd conflict
Please uninstall ippusbxd. Then your device should work with HPLIP normally. ippusbxd wa supposed to allow driverless printing and scanning without HPLIP. Unfortunately there were problems in its design. In Groovy we will replace ippusbxd by ipp-usb which finally allows driverless printing and scanning without HPLIP to work reliably. See bug 1891157. -- 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/1871011 Title: USB scanning broken on focal --> hpmud and ippusbxd conflict Status in HPLIP: Invalid Status in hplip package in Ubuntu: Expired Bug description: On Ubuntu 20.04 focal (with -proposed enabled). HPLIP=3.20.3. Previously there was a libmtp (udev) bug erroneously detecting HP printers as mtp devices. This was fixed. Now, I can try to scan-- from both simple-scan and hp-scan, hplip errors out: Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=1, altset=0, index=1 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=1 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/2: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Apr 05 21:27:37 dani-mbp15 simple-scan[3464]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Printer/scanner is an Officejet 4635. Scanning previously worked just fine a few months ago. Regression? To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1871011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry
** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Focal) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Triaged ** Changed in: mutter (Ubuntu Focal) Assignee: Marco Trevisan (Treviño) (3v1n0) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1862308 Title: Desktop wallpaper is slightly blurry Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Triaged Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34 and 3.36 Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1862308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Triaged -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Triaged Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-390 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: nvidia-graphics-drivers-435 (Ubuntu Focal) Status: New => Won't Fix ** Changed in: mutter (Ubuntu Focal) Status: New => Triaged ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1893113] Re: Cannot add music
** Tags added: focal ** Description changed: + * In progress - need to complete* + + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + Please refer: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1790 ** Summary changed: - Cannot add music + Rhythmbox: Cannot add more music after a collection has been created ** Summary changed: - Rhythmbox: Cannot add more music after a collection has been created + [SRU] Rhythmbox: Cannot add more music after a collection has been created -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox-plugin-alternative-toolbar in Ubuntu. https://bugs.launchpad.net/bugs/1893113 Title: [SRU] Rhythmbox: Cannot add more music after a collection has been created Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu: Fix Released Status in rhythmbox-plugin-alternative-toolbar source package in Focal: Triaged Status in rhythmbox-plugin-alternative-toolbar source package in Groovy: Fix Released Bug description: * In progress - need to complete* [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. [Regression Potential] * discussion of how regressions are most likely to manifest as a result of this change. * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance Please refer: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1790 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1893113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878392] Re: Ubuntu 20.04 Focal Fossa desktop launchers not working
The default position should be that the system creates an 'application' for each .desktop in ~/.local/share/applications. it does not, and is rather particular... in my case requiring full addresses was the issue. even then, add to favourites was not immediately available, which is frustrating. for newbies, and aren't we all, if the 'app' appeared, but did not work, at least we could have faith... as it is its just a black box, with no insight as to what the issue may be. -- 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/1878392 Title: Ubuntu 20.04 Focal Fossa desktop launchers not working Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: Using the procedure here = https://linuxconfig.org/how-to-create-desktop-shortcut-launcher-on-ubuntu-20-04-focal-fossa-linux AND OTHERWISE I have successfully created launchable desktop app shortcuts. But they stop working: (1) no launch; (2) no right click context to make launchable; and (3) no app icon. They can even remain in ~/Desktop but disappear from the desktop view. A logout kills them. Creating another new launcher is successful and peculiarly triggers the temporary reactivation of all the others. But euphoria soon dies as they all revert to inertia later. My work around at present is to install PCManFM 1.3.1. Navigating to ~/Desktop on PCManFM, my Nautilus created launchers are all visible, launchable and have the usual colourful app icon features. But they remain inert in Nautilus. My Gnome version is: 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1878392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893217] [NEW] display corruption
Public bug reported: my display doesnt work properly.it mostly gets clubbed with previous window i used in system. Even now while i m reporting the bug,i face the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: 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 27 18:10:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: built rtl8821ce, v5.5.2_34066.20200325, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:84a7] Subsystem: Hewlett-Packard Company GM108M [GeForce MX110] [103c:84a7] InstallationDate: Installed on 2020-08-26 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 003: ID 04f2:b65d Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 011: ID 04e8:6864 Samsung Electronics Co., Ltd GT-I9070 (network tethering, USB debugging enabled) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15g-dr0xxx ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4cac576c-f749-447e-9180-b78666e12db6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A7 dmi.board.vendor: HP dmi.board.version: 80.31 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.07:bd11/21/2018:svnHP:pnHPLaptop15g-dr0xxx:pvrType1ProductConfigId:rvnHP:rn84A7:rvr80.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15g-dr0xxx dmi.product.sku: 4ZD61PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu ** Attachment added: "while reporting the bud,the right side of the screen did not respond" https://bugs.launchpad.net/bugs/1893217/+attachment/5405157/+files/Screenshot%20from%202020-08-27%2018-18-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1893217 Title: display corruption Status in xorg package in Ubuntu: New Bug description: my display doesnt work properly.it mostly gets clubbed with previous window i used in system. Even now while i m reporting the bug,i face the same issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module
[Desktop-packages] [Bug 1876352] Re: [ubuntu-dock] App Grid icons out of alignment when opening from overview
Yeah, this bug went away when I disabled ubuntu-dock. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1876352 Title: [ubuntu-dock] App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
