[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
** No longer affects: pulseaudio (Ubuntu) ** No longer affects: alsa-driver (Ubuntu) ** No longer affects: dell-sputnik -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in linux package in Ubuntu: In Progress Bug description: === SRU Justification === [Impact] XPS 13 9350/9360 has unbearlbe headphone noise after recent kernel updates. [Fix] Lock Headphone Mic Boost level to 1 as an workaround to solve the issue. [Test] Plug a headphone to audio jack, the noise is really bad. After applying the patch the noise is gone. [Regression Potenial] Low. This change only targets to 2 systems, so it has limited impact. === Original Bug Report === Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852048] Re: "Open new terminals in" not available in GNOME Terminal 3.28.2
Why the option "Open new terminals in" not available in GNOME Terminal 3.28.2? ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/685814 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1852048 Title: "Open new terminals in" not available in GNOME Terminal 3.28.2 Status in gnome-terminal package in Ubuntu: Invalid Bug description: The option "Open new terminals in" not available in GNOME Terminal 3.28.2 Going Edit > Preferences > General The option is not showing. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Version: 3.28.2-1ubuntu1~18.04.1 Source: ubuntu-bionic-updates-main 3) What you expected to happen The option "Open new terminals in" Should be available under Edit > Preferences > General 4) What happened instead Option "Open new terminals in" not available under Edit > Preferences > General The option is not showing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1852048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w
To install the testing kernel: sudo dpkg -i linux-modules-xxx.deb sudo dpkg- i linux-image-xxx.deb sudo dpkg -i linux-modules-extra-xxx.deb reboot To choose the kernel: you could press ESC button during the grub (bootloader) stage, then there is a menu you could choose the kernel. After booting up, you could run uname -a to verify the kernel you are running. To uninstall the testing kernel: sudo dpkg -p linux-modules-extra-xxx.deb (run dpkg --list | grep linux-modules-extra*, then you will konw the full name of linux-modules-extra-xxx.deb) sudo dpkg -p linux-image-xxx.deb sudo dpkg -p linux-modules-xxx.deb. reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in alsa-driver package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835541] Re: ibus only provides non-standard UK keyboard layouts
** Changed in: ibus (Debian) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1835541 Title: ibus only provides non-standard UK keyboard layouts Status in ibus package in Ubuntu: Confirmed Status in ibus package in Debian: Confirmed Bug description: When I attempt to add my standard UK keyboard to the layouts ibus knows about, I cannot do so. (See the attached image for the list of available layouts.) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.19-4ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: i3 Date: Fri Jul 5 10:07:41 2019 InstallationDate: Installed on 2019-05-07 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1835541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852383] [NEW] system hangs on shutdown
Public bug reported: On a Lenovo Yoga S940, the system always hangs on shutdown. The screen turns black and nothing happens anymore. I have to keep pressed for several seconds the shutdown hardware button in order to actually turn it off. I attach the journalctl output from the shutdown which present very similar 'errors' from session to session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 07:03:38 2019 InstallationDate: Installed on 2019-10-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "shutdown.log" https://bugs.launchpad.net/bugs/1852383/+attachment/5304934/+files/shutdown.log ** Description changed: - On Ubuntu 19.10 with a Lenovo Yoga S940, the system always hangs on shutdown. + On a Lenovo Yoga S940, the system always hangs on shutdown. I attach the journalctl output from the shutdown which present very similar 'errors' from session to session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 07:03:38 2019 InstallationDate: Installed on 2019-10-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: On a Lenovo Yoga S940, the system always hangs on shutdown. - I attach the journalctl output from the shutdown which present very similar 'errors' from session to session. + I have to keep pressed for several seconds the shutdown hardware button in order to actually turn it off. + + I attach the journalctl output from the shutdown which present very + similar 'errors' from session to session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 07:03:38 2019 InstallationDate: Installed on 2019-10-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: On a Lenovo Yoga S940, the system always hangs on shutdown. - I have to keep pressed for several seconds the shutdown hardware button in order to actually turn it off. + The screen turns black and nothing happens anymore. + I have to keep pressed for several seconds the shutdown hardware button in order to actually turn it off. I attach the journalctl output from the shutdown which present very similar 'errors' from session to session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 07:03:38 2019 InstallationDate: Installed on 2019-10-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1852383 Title: system hangs on shutdown Status in gdm3 package in Ubuntu: New Bug description: On a Lenovo Yoga S940, the system always hangs on shutdown. The screen turns black and nothing happens anymore. I have to keep pressed for several seconds the shutdown hardware button in order to actually turn it off. I attach the journalctl output from the shutdown which present very similar 'errors' from session to session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 07:03:38 2019 InstallationDate: Installed on 2019-10-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190916) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bug
[Desktop-packages] [Bug 1851564] Re: Daily Limit Exceeded messages for google calendars
still a problem for me as a google apps user... Ubuntu 18.04 Evolution 3.34.1 (flathub) source_credentials_required_cb: Failed to authenticate 'Contacts': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1851564 Title: Daily Limit Exceeded messages for google calendars Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: This seems to coincide with the 19.04 -> 19.10 upgrade, but I only have logs going back to mid august. The message is repeated for each calendar at various times. Nov 06 13:49:13 dipper gnome-calendar[8681]: source_credentials_required_cb: Failed to authenticate 'Kai Groner': Daily Limit Exceeded. The quota will be reset at midnight Pacific Time (PT). You may monitor your quota usage and adjust limits in the API Console: https://console.developers.google.com/apis/api/caldav.googleapis.com/quotas?project=44438659992 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:07:56 2019 InstallationDate: Installed on 2019-06-18 (141 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1851564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w
Thank you Hui Wang for your quick answer. Could you help me with install and then uninstall procedure? I understand that I have to install all these kernel packages with "sudo dpkg -i". But: 1. What is the order of installation of these packages? 2. After installation how can I switch from current kernel to this new kernel? Currently I use "5.0.0-35-generic #38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux" 3. What if this new kernel won't boot my computer? Will be there any backup kernel installed? 4. After tests what should I do get back to "stock" kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in alsa-driver package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849542] Re: Thunderbird empty after update to 19.10 - corrupted global-messages-db.sqlite
Same problem here. Release: Ubuntu 18.04.1 Package version: 1:68.2.1+build1-0ubuntu Removing global-messages-db.sqlite is solving the problem. Before removing (when empty), the Thunderbird shows me 70.1 version number, after removing it was 68.2. Strange! -- 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/1849542 Title: Thunderbird empty after update to 19.10 - corrupted global-messages- db.sqlite Status in thunderbird package in Ubuntu: Confirmed Bug description: HELP Just performed an upgrade from Ubuntu 19.04 to 19.10. Launched Thunderbird and the interface is empty. No emails, no folders, no calendar, I can't even open the "account settings" window. This is a complete disaster. I need thunderbird for my work. If I launch TB form terminal I get this: lalejand@Gedeon:~$ thunderbird JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined TypeError: aAttrDef.objectNounDef is undefined -- Exception object -- * -- Stack Trace -- defineAttribute@resource:///modules/gloda/gloda.js:1922:5 defineAttributes@resource:///modules/gloda/fundattr.js:71:35 init@resource:///modules/gloda/fundattr.js:43:12 @resource:///modules/gloda/everybody.js:13:15 @resource:///modules/gloda/public.js:8:57 nsAutoCompleteGloda@jar:file:///usr/lib/thunderbird/omni.ja!/components/glautocomp.js:516:32 createInstance@resource://gre/modules/XPCOMUtils.jsm:433:19 glodaSearch_XBL_Constructor@chrome://messenger/content/search.xml:73:16 JavaScript error: chrome://messenger/content/messenger.xul, line 1: TypeError: QuickFilterBarMuxer is undefined JavaScript error: chrome://messenger/content/msgMail3PaneWindow.js, line 470: TypeError: TagUtils is undefined JavaScript error: resource:///modules/gloda/gloda.js, line 1922: TypeError: aAttrDef.objectNounDef is undefined What can I do ? Release: Ubuntu 19.10 Package version: 1:68.1.2+build1-0ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
I observe this on my XPS 13 9360. As mentioned by others, the headphone hissing goes away when I mute the system or when I run "amixer -c0 sset 'Headphone Mic Boost' 10dB". I created an even in /etc/acpi/events to call run this whenever headphones are inserted so that it persists after reboot. Has anyone had luck advising Dell of the suspected hardware issue? James -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Attachment to #17 was incorrect (forgot to turn on coefficients) Attached is alsa-info with coefficients. ** Attachment added: "alsa-info-dell-headset3-with-coefficients.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304921/+files/alsa-info-dell-headset3-with-coefficients.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitec
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
>> nd If you have time, please redo the test of #10, after finishing all commands, please generate an alsa-info.txt-with-coeff, let us check if all those commands successfully executed. <<< Option: dell-headset3 Headphone works, and does not seem to change when any of the below settings are applied. alsa-info output attached; it was generated after the last command in the sequence. martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x8e nid = 0x20, verb = 0x500, param = 0x8e value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x20 nid = 0x20, verb = 0x400, param = 0x20 value = 0x0 NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x19 nid = 0x20, verb = 0x500, param = 0x19 value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x317 nid = 0x20, verb = 0x400, param = 0x317 value = 0x0 NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x67 nid = 0x20, verb = 0x500, param = 0x67 value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x1110 nid = 0x20, verb = 0x400, param = 0x1110 value = 0x0 NO change martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x4f nid = 0x20, verb = 0x500, param = 0x4f value = 0x0 martin@martins-samsung:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xc429 nid = 0x20, verb = 0x400, param = 0xc429 value = 0x0 NO change Thanks, Martin ** Attachment added: "alsa-info-dell-headset3-with-coefficients.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304920/+files/alsa-info-dell-headset3-with-coefficients.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0,
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
> please verify that both speaker and headphone work well under windows, then using this tool to collect a log under windows, the log is a useful reference for linux. < Output attached; looks like this might be helpful to get the speakers to work. Thank you, Martin ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304916/+files/RtHDDump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 Installati
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
If you have time, please run #13 on the windows10. And If you have time, please redo the test of #10, after finishing all commands, please generate an alsa-info.txt-with-coeff, let us check if all those commands successfully executed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTI
[Desktop-packages] [Bug 1852118] Re: Notifications don't have sound
Thanks for your prompt response Sebastien. Sorry i thought i had remembered there being a default notification sound in older versions of Ubuntu/gnome and thought this was a regression. My mistake. -- 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/1852118 Title: Notifications don't have sound Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: A fresh install of 19.10 does not have sound for new incoming notifications. Using the notify-send or alert CLIs don't produce sound either. System sounds level is at 100%. All application types in the notification settings have Sound Alerts enabled. I've experienced this on 3 separate machines: - A newer AMD 3700x machine using USB audio - Older Intel 5th gen using USB audio - 2018 Huawei Matebook X Pro with both built-in speakers and USB audio It makes the system difficult to use when relying on important notifications from messaging or email applications for example when they don't produce sound, especially on multi-monitor setups where the notification may be missed, or I'm turned away momentarily. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1852118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852254] Re: Dock stays ontop of Xscreensaver
Im using Xscreensaver by startup items i dont use gnome's lock screen Xscreensaver is set to be active after 1 minute -- 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/1852254 Title: Dock stays ontop of Xscreensaver Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date at 12/11/2019 As requested on bug: https://bugs.launchpad.net/ubuntu/+source/gnome- shell-extension-ubuntu-dock/+bug/1849787 I am creating a new bug for gnome-shell as several users experience the dock to be ontop My case the dock stays ontop of Xscreensaver, but only at random times i cannot reproduce when ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 14:49:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-25 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-10-25T10:03:18.026469 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851790] Re: Cheese webcam image dropping at random launch
Changed bug to invalid as its a hardware problem: the webcam is flashing to dark when the environment is too dark with daylight, the webcam works ** Changed in: cheese (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1851790 Title: Cheese webcam image dropping at random launch Status in cheese package in Ubuntu: Invalid Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic all up to date to latest @ 8/11/2019 After the launch of cheese webcam image drops to black image at random launches, sometimes after a reboot it works again properly, and the next launch goes to black again. Compared with Kamoso where everything works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 09:21:07 2019 InstallationDate: Installed on 2019-10-25 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) MachineType: Notebook N7x0WU RelatedPackageVersions: cheese3.34.0-1 cheese-common 3.34.0-1 SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1851790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759591] Re: [printer] segfault when printing a test page
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1759591 Title: [printer] segfault when printing a test page Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: was setting the printer ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu4 Uname: Linux 4.16.0-041600rc7-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CurrentDesktop: GNOME Date: Wed Mar 28 16:23:37 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-02-06 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: gnome-control-center printers Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d6dcdb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7fa0d6dcbc9d "corrupted size vs. prev_size") at malloc.c:5350 _int_realloc (av=av@entry=0x7fa0d7002c40 , oldp=oldp@entry=0x55f7d56c5400, oldsize=oldsize@entry=912, nb=nb@entry=928) at malloc.c:4564 __GI___libc_realloc (oldmem=0x55f7d56c5410, bytes=912) at malloc.c:3230 g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1759591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
<<< Ah, please test model=dell-headset3, it should work. And please also add options snd-hda-codec-realtek dyndbg, then boot the system without the headphone plugged. after boot up, plug headphone, and test if it works well. If it works well, please upload the dmesg. Yes, headphones work well. dmesg output is attached. Thank you. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5304905/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: New Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop:
[Desktop-packages] [Bug 1852363] [NEW] Non working button to open the printers configuration
Public bug reported: Using 19.10 with the current snap - click print - in the print dialog, select the 'destination' 'see more' option - click the manage button at the bottom The printers line has an icon to open the printer configuration dialog which doesn't work, it probably tries to call a command which isn't available from the snap environment? ** Affects: chromium-browser (Ubuntu) Importance: Low Status: New ** Tags: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1852363 Title: Non working button to open the printers configuration Status in chromium-browser package in Ubuntu: New Bug description: Using 19.10 with the current snap - click print - in the print dialog, select the 'destination' 'see more' option - click the manage button at the bottom The printers line has an icon to open the printer configuration dialog which doesn't work, it probably tries to call a command which isn't available from the snap environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852362] [NEW] ColorManager/Avahi apparmor denials when selecting printer
Public bug reported: Using 19.10 with the current snap, when clicking on printing and selecting a printer the journal gets apparmor denials about avahi and colormanager pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.Avahi.Server" member="ServiceBrowserNew" mask="send" name="org.freedesktop.Avahi" pid=24201 label="snap.chromium.chromium" peer_pid=935 peer_label="unconfined" pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/ColorManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.17" pid=24201 label="snap.chromium.chromium" peer_pid=1018 peer_label="unconfined" ** Affects: chromium-browser (Ubuntu) Importance: Low Status: New ** Tags: snap ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1852362 Title: ColorManager/Avahi apparmor denials when selecting printer Status in chromium-browser package in Ubuntu: New Bug description: Using 19.10 with the current snap, when clicking on printing and selecting a printer the journal gets apparmor denials about avahi and colormanager pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.Avahi.Server" member="ServiceBrowserNew" mask="send" name="org.freedesktop.Avahi" pid=24201 label="snap.chromium.chromium" peer_pid=935 peer_label="unconfined" pid=915 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/ColorManager" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.17" pid=24201 label="snap.chromium.chromium" peer_pid=1018 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759591] Re: gnome-control-center assert failure: corrupted size vs. prev_size
Confirmed it's still happening on 19.10 and reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/773 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #773 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/773 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - gnome-control-center assert failure: corrupted size vs. prev_size + [printer] segfault when printing a test page ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/773 Importance: Unknown Status: Unknown -- 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/1759591 Title: [printer] segfault when printing a test page Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: was setting the printer ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu4 Uname: Linux 4.16.0-041600rc7-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CurrentDesktop: GNOME Date: Wed Mar 28 16:23:37 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-02-06 (49 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcCmdline: gnome-control-center printers Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa0d6dcdb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7fa0d6dcbc9d "corrupted size vs. prev_size") at malloc.c:5350 _int_realloc (av=av@entry=0x7fa0d7002c40 , oldp=oldp@entry=0x55f7d56c5400, oldsize=oldsize@entry=912, nb=nb@entry=928) at malloc.c:4564 __GI___libc_realloc (oldmem=0x55f7d56c5410, bytes=912) at malloc.c:3230 g_realloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1759591/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852173] Re: GUI applications with root access don't open
Hi As I mentioned, none of the apps including the Users in settings is getting the root previlege. Please let me know if you want to test any specific GUI based app or system app. Thanks Shashank. -- 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/1852173 Title: GUI applications with root access don't open Status in gnome-shell package in Ubuntu: Incomplete Bug description: While opening Timekpr GUI application, it requires root access to enable or disable the time remaining for the session. From yesterday onwards, Timekpr is not opening. Upon investigation, found the below errors / messages in logs: pkexec: Error checking for authorization com.ubuntu.timekpr.pkexec: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying It is followed by Gnome shell messages: PolicyKit daemon reconnected to bus. Attempting to re-register as an authentication agent. We are now a registered authentication agent. Appreciate any help. 1. Description: Ubuntu 18.04.3 LTS Release: 18.04 2. https://launchpad.net/timekpr 3. Expect the time keeper control panel to open up 4. Nothing happens on screen. Same is the issue with User accounts as well. To change password of user, by clicking on the unlock icon at top in useers screen, nothing happens. Both the applications are looking for root access, via a GUI based application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Chromium is now incapable of managing extensions for Ubuntu's primary desktop environment? This issue is tolerable only because Google Chrome is not affected. Is Google somehow behind this apparent reluctance to remedy the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient
@Balint, thanks a lot for the information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1850775 Title: DNS info is not loaded by dhclient Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi Team, Could you please help to confirm if this is an issue on Ubuntu19.10 Desktop? 1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines. supersede domain-name "vmware.com"; supersede domain-name-servers 10.117.0.1; 2. Reboot 3. check DNS info by "systemd-resolve --status", the DNS domain and server is not set. But /run/systemd/resolved.conf.d/isc- dhcp-v4-ens160.conf contains the new DNS domain and server. 4. Manually run "systemctl try-reload-or-restart systemd- resolved.service" and then DNS is set correctly, "systemd-resolve --status" output have the new DNS domain and server. I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated correctly after reboot. Thanks, Pengpeng To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
Ok, sorry then I've no idea what in the user profile is creating the problem, maybe upstream would have a better clue... -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851127] Re: app page shows no install progress
** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress Status in gnome-software package in Ubuntu: Confirmed Bug description: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w
following the #5, the testing kernel is at: https://people.canonical.com/~hwang4/conexant-test/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in alsa-driver package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w
Please test this kernel, let us see if the kernel fixes the problem or not. If not, please upload a new alsa-info.txt. thx. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1852067 Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers works ok. Status in alsa-driver package in Ubuntu: New Bug description: Steps to replicate the bug. 1. Start laptop with Ubuntu 18.04.3 LTS. Sound from built-in speakers works fine. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio 2. Connect headphones (wired, mini-jack connector). Sound from headphones works fine. No sound from built-in speakers (which is OK, obviously). Settings -> Sound -> Output shows one device: Headphones - Built-in Audio 3. Disconnect headphones from computer. No sound from built-in speakers. Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, high volume) Changing volume, turning ON -> OFF -> ON, user logout->login doesn't help. Only full laptop restart helps. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 2115 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 12:26:58 2019 InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1672 F pulseaudio marcin 2115 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Tags added: rls-ee-incoming rls-ff-incoming -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
@kaihengfegn I guess I need this one: linux-image- unsigned-5.4.0-050400rc7-generic_5.4.0-050400rc7.201911102031_amd64.deb as well as the corresponding headers and modules. but what does "unsigned" mean? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848900 Title: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted b
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
Thanks ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in Mutter: New Status in gnome-shell package in Ubuntu: Triaged Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system
$ free totalusedfree shared buff/cache available Mem:1022440 299328 378272 808 344840 567588 Swap:603372 344256 259116 $ cat /proc/swaps FilenameTypeSizeUsedPriority /dev/sda6 partition 92156 792 -1 /dev/zram0 partition 255608 171064 5 /dev/zram1 partition 255608 171048 5 -- 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/1844739 Title: Latest Firefox update freezing my system Status in firefox package in Ubuntu: New Bug description: The latest updates of firefox renders my machine useless. I'm sending it as is hopefully before it freezes completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 BuildID: 20190828152935 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 01:22:17 2019 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:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-05-01 (506 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0/20190828152935 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852118] Re: Notifications don't have sound
** Changed in: gnome-shell Status: Unknown => 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/1852118 Title: Notifications don't have sound Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: A fresh install of 19.10 does not have sound for new incoming notifications. Using the notify-send or alert CLIs don't produce sound either. System sounds level is at 100%. All application types in the notification settings have Sound Alerts enabled. I've experienced this on 3 separate machines: - A newer AMD 3700x machine using USB audio - Older Intel 5th gen using USB audio - 2018 Huawei Matebook X Pro with both built-in speakers and USB audio It makes the system difficult to use when relying on important notifications from messaging or email applications for example when they don't produce sound, especially on multi-monitor setups where the notification may be missed, or I'm turned away momentarily. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1852118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Changed in: mutter Status: Unknown => New -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
** Changed in: mutter Status: Unknown => 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in Mutter: New Status in gnome-shell package in Ubuntu: New Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851127] Re: app page shows no install progress
I can reproduce Seb's issue in the snap-store snap as well ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851127 Title: app page shows no install progress Status in gnome-software package in Ubuntu: Confirmed Bug description: I just installed a couple of applications (bomb squad and android studio) and while installing, they show no install progress. Steps to reproduce Launch gnome-software Click an application from the front of G-S Click Install Fill in password Expected outcome I expect to be shown a progress bar, showing that installation is happening Actual outcome I see no progress, yet running `snap changes` in a terminal shows it is installing In addition, clicking "Install" again fails due to the install running. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 3 11:42:28 2019 InstallationDate: Installed on 2019-10-27 (6 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog
I can also confirm on Ubuntu 19.10 with network-manager 1.20.4-2ubuntu2 and openconnect 8.02-1build1 amd64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Fix Released Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754702] Re: Delay before you can type after switching input source
Better to use: gsettings set org.freedesktop.ibus.general switcher-delay-time -10 -- 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/1754702 Title: Delay before you can type after switching input source Status in gnome-shell package in Ubuntu: Confirmed Bug description: In ubuntu 18.04 I installed different keyboard languages: spanish latin american, japanese, japanese-ibus. To change the input method you press the selected key, and an indicator menu appears on-screen to indicate which language is selected next. The menu disapears after 2~3 seconds and during which time typing is blocked. If you type while the language input method menu is displayed, the menu will not disapear and stay as long as you type. The language input menu should not block typing, and the disapearance of the menu should not be delayed by typing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754702] Re: Delay before you can type after switching input source
Problem still exist in Ubuntu 19.10 -- 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/1754702 Title: Delay before you can type after switching input source Status in gnome-shell package in Ubuntu: Confirmed Bug description: In ubuntu 18.04 I installed different keyboard languages: spanish latin american, japanese, japanese-ibus. To change the input method you press the selected key, and an indicator menu appears on-screen to indicate which language is selected next. The menu disapears after 2~3 seconds and during which time typing is blocked. If you type while the language input method menu is displayed, the menu will not disapear and stay as long as you type. The language input menu should not block typing, and the disapearance of the menu should not be delayed by typing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #920 https://gitlab.gnome.org/GNOME/mutter/issues/920 ** Project changed: gnome-shell => mutter ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1888 => gitlab.gnome.org/GNOME/mutter/issues #920 -- 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1888 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1888 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1888 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor
Hi, no I have never touched cursor/theme setting, so always default. I turned on Wayland as requested (and also disabled x11vnc). The result was that I just got purple splash screen and no log in window at all. Likely I need to add addition UI packages, which may have been auto removed. I will do UI package update and retest. Likely will only have results later in day. Thanks John. -- 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/1851340 Title: Ubuntu 19.10 upgrade results in invisible mouse cursor Status in xorg package in Ubuntu: Confirmed Bug description: Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible cursor with my Gnone desktop. I have found the same problem when upgrading 2 machines from Ubuntu 19.04 -> 19.10. Reproducing problem is easy: 1. Open Ubuntu Update Window 2. Select "Upgrade" 3. On completion of update (after reboot) cursor is no longer visible. 4. This applies to display connected to VGA port on host with USB Keyboard + Mouse While the connected display has no visible cursor and so is usable, I have always used X11VNC Server to provide network GUI access. On the remote X11VNC display I see and can use the cursor. This bug report is being sent via Remote X11VNC window, as I cannot use the main VGA display window (due to lack of visible cursor) I have done search online and thought that maybe issue was with my USB Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same result, no visible mouse cursor. I have done: "grep usb /var/log/syslog" and can see many USB events, including both Apple and Logitech mouse detection events. NOTE: Due to compatibility issue with X11VNC, I have disable Wayland on both machines by adding the following option to: /etc/gdm3/custom.conf WaylandEnable=false Regards, John Hartley. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 18:25:23 2019 DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo G200eR2 [1d49:0a01] InstallationDate: Installed on 2018-12-17 (322 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO System x3650 M5: -[8871AC1]- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5: -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
No difference. -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by window when fullscreen SDL apps exits
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/1844222 Title: Wayland session overlaid by window when fullscreen SDL apps exits Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by window when fullscreen SDL apps exits
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/1844222 Title: Wayland session overlaid by window when fullscreen SDL apps exits Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844222] Re: Wayland session overlaid by window when fullscreen SDL apps exits
I think this is upstream bug https://gitlab.gnome.org/GNOME/mutter/issues/655. The bug has been solved by: https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815 It is a quite critical bug since it renders the shell unusable. Would you consider backporting these patches to 18.04? ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #655 https://gitlab.gnome.org/GNOME/mutter/issues/655 -- 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/1844222 Title: Wayland session overlaid by window when fullscreen SDL apps exits Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Seen on 18.04 and 19.10 In the "Ubuntu Wayland" desktop sudo apt install beneath-a-steel-sky SDL_VIDEODRIVER=wayland scummvm -f -p /usr/share/scummvm/beneath-a-steel-sky sky Press ESC a few times and Ctrl-Q to exit. Expect: session returns to normal Actual: a black rectangle covers the screen, even when switching workspaces. (I'm sure scummvm is doing something odd, but...) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851887] Re: Sound only works works again if the volume is raised more than 50%
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1851887 Title: Sound only works works again if the volume is raised more than 50% Status in linux package in Ubuntu: New Bug description: Sometimes when I play a clip (be it a Video, song or a radiostation, it doesn't matter) and I have the volume lowered to 10% I can't hear any sound whatsoever. Not until I raise the volume with Fn + F12 (F12 has a speaker icon on it to raise the volume). It's as if PulseAudio is muted until I raise the volume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kristoffer 1627 F pulseaudio /dev/snd/controlC0: kristoffer 1627 F pulseaudio CurrentDesktop: MATE Date: Fri Nov 8 23:39:31 2019 InstallationDate: Installed on 2019-10-05 (34 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
Can you move ~/.local/share/gnome-shell away and try if that makes a difference? -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
Could you report the issue upstream? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852173] Re: GUI applications with root access don't open
Thank you for your bug report. It looks like an issue with the software, do you get problems with other applications? ** Package changed: gnome-shell-extension-appindicator (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1852173 Title: GUI applications with root access don't open Status in gnome-shell package in Ubuntu: Incomplete Bug description: While opening Timekpr GUI application, it requires root access to enable or disable the time remaining for the session. From yesterday onwards, Timekpr is not opening. Upon investigation, found the below errors / messages in logs: pkexec: Error checking for authorization com.ubuntu.timekpr.pkexec: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying It is followed by Gnome shell messages: PolicyKit daemon reconnected to bus. Attempting to re-register as an authentication agent. We are now a registered authentication agent. Appreciate any help. 1. Description: Ubuntu 18.04.3 LTS Release: 18.04 2. https://launchpad.net/timekpr 3. Expect the time keeper control panel to open up 4. Nothing happens on screen. Same is the issue with User accounts as well. To change password of user, by clicking on the unlock icon at top in useers screen, nothing happens. Both the applications are looking for root access, via a GUI based application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845317] Autopkgtest regression report (linux-gcp-5.3/5.3.0-1008.9~18.04.1)
All autopkgtests for the newly accepted linux-gcp-5.3 (5.3.0-1008.9~18.04.1) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.3/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-gcp-5.3 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1845317 Title: Add new pci-id's for CML-S, ICL Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Comet Lake (CML) is basically same gen9 GPU as Sky Lake (SKL) (as is KBL, CFL, WHL). There are new CML-S desktop cpu's on the way, and they add three new pci-id's that need to be added across the stack in order to use the GPU properly. There's also one ICL pci-id which was added recently (not in 5.3). [Test case] The proper way to test is to have an actual machine and boot it up with the updated stack, but since these are just pci-id's with no regression potential on older hw, it should be fine to just accept them. [Regression potential] None, just adds new pci-id's to allow the new GPUs to load the proper drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1845317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852173] Re: GUI applications with root access don't open
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1852173 Title: GUI applications with root access don't open Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: While opening Timekpr GUI application, it requires root access to enable or disable the time remaining for the session. From yesterday onwards, Timekpr is not opening. Upon investigation, found the below errors / messages in logs: pkexec: Error checking for authorization com.ubuntu.timekpr.pkexec: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying It is followed by Gnome shell messages: PolicyKit daemon reconnected to bus. Attempting to re-register as an authentication agent. We are now a registered authentication agent. Appreciate any help. 1. Description: Ubuntu 18.04.3 LTS Release: 18.04 2. https://launchpad.net/timekpr 3. Expect the time keeper control panel to open up 4. Nothing happens on screen. Same is the issue with User accounts as well. To change password of user, by clicking on the unlock icon at top in useers screen, nothing happens. Both the applications are looking for root access, via a GUI based application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1852173/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851887] Re: Sound only works works again if the volume is raised more than 50%
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1851887 Title: Sound only works works again if the volume is raised more than 50% Status in pulseaudio package in Ubuntu: New Bug description: Sometimes when I play a clip (be it a Video, song or a radiostation, it doesn't matter) and I have the volume lowered to 10% I can't hear any sound whatsoever. Not until I raise the volume with Fn + F12 (F12 has a speaker icon on it to raise the volume). It's as if PulseAudio is muted until I raise the volume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7 Uname: Linux 5.3.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kristoffer 1627 F pulseaudio /dev/snd/controlC0: kristoffer 1627 F pulseaudio CurrentDesktop: MATE Date: Fri Nov 8 23:39:31 2019 InstallationDate: Installed on 2019-10-05 (34 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.208:bd09/26/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N550JK dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1851887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
Hi, I'm new to Ubuntu bug testing, so hopefully I've done this correctly. I can confirm the problem has been fixed, after upgrading to mutter / libmutter-5-0 3.34.1+git20191107-1ubuntu1~19.10.1. (via aptitude). Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Committed Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). [ Test case ] - From gnome-control-center display panel, enable the Night Light - Force it on, and ensure that the display color temperature increases [ Regression potential ] Display gamma value might be incorrect Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
I take it back, it just happened again. Apparently it's intermittent. I can't determine for certain whether it happens under X, because (a) as I just noted, it's intermittent, and (b) my monitor has an entirely different issue under X, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849484 . ** Changed in: gnome-shell (Ubuntu) Status: Invalid => 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in gnome-shell package in Ubuntu: New Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852118] Re: Notifications don't have sound
Thank you for your bug report, the feature has been requested upstream there https://gitlab.gnome.org/GNOME/gnome-shell/issues/486 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #486 https://gitlab.gnome.org/GNOME/gnome-shell/issues/486 ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/486 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1852118 Title: Notifications don't have sound Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: A fresh install of 19.10 does not have sound for new incoming notifications. Using the notify-send or alert CLIs don't produce sound either. System sounds level is at 100%. All application types in the notification settings have Sound Alerts enabled. I've experienced this on 3 separate machines: - A newer AMD 3700x machine using USB audio - Older Intel 5th gen using USB audio - 2018 Huawei Matebook X Pro with both built-in speakers and USB audio It makes the system difficult to use when relying on important notifications from messaging or email applications for example when they don't produce sound, especially on multi-monitor setups where the notification may be missed, or I'm turned away momentarily. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1852118/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
Yes. -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851568] Re: monitor configuration restored incorrectly upon Wayland login
I am no longer able to reproduce this issue so I'm going to close it. ** Changed in: gnome-shell (Ubuntu) Status: New => 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/1851568 Title: monitor configuration restored incorrectly upon Wayland login Status in gnome-shell package in Ubuntu: Invalid Bug description: I have an ultrawide monitor plugged into my laptop. When I log into a Wayland session, my monitor configuration (resolution, relative position, which monitor is the primary) is not restored correctly. When I unplug the monitor cable after logging in and plug it in again, the correct configuration is restored. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 15:45:21 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851568/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851554] Re: can't install gnome shell extensions
>Does it work with a new user on the same system? Yes. -- 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/1851554 Title: can't install gnome shell extensions Status in gnome-shell package in Ubuntu: New Bug description: Here's what I'm trying to do: 1. Go to https://extensions.gnome.org/extension/1379/mpris-indicator-button/ 2. Click the toggle switch to install it. 3. Use the extension after it is installed. Here's what should happen: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch goes from Off to On and the extension is added to my top bar. Here's what happens instead: 1. I am prompted for confirmation to install the extension. 2. I click Install. 3. The toggle switch stays in the Off permission, and the extension is not added to my top bar. Here's what I see in journalctl: Nov 06 13:13:24 jik-d42-x1 gnome-software[2200]: State change on user /*/*/shell-extension/mprisindicatorbutton_JasonLG1979.github.io/* from available to installed is not OK I've also tried unzipping by hand into a subdirectory of ~/.local/share/gnome-shell/extensions, restarting gnome-shell, and enabling the extension at extensions.gnome.org/local, but that doesn't work either. The toggle switch goes to On when I toggle it, but the extension isn't actually enabled and when I reload the page the switch is Off again. I've tried with https://extensions.gnome.org/extension/779/clipboard- indicator/ and https://extensions.gnome.org/extension/7/removable- drive-menu/ too. They won't install and activate either. *** I do not have this problem on a second Ubuntu 19.10 computer I use. *** I have no idea what is different between the two computers or how to troubleshoot further. I am using Xorg, not Wayland. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 14:16:34 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-12 (55 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-20 (47 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
Attached backtrace of LibreOffice after crash as described in previous message ** Attachment added: "backtrace of LibreOffice Calc crash when attempting to undo paste/cut of bitmap" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852183/+attachment/5304853/+files/gdbtrace.log -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I can only reproduce this bug in LibreOffice Calc (spreadsheet). I cannot reproduce it in Writer or Geary. But it is a consistent problem for me in Calc. Here are the symptoms/process: 1. First new copy invariably fails to copy text, instead copies/stores a bitmap image. 2. If I "cut" instead of "copy" then I have to use the "undo" function to restore the text so I can attempt again. 3. Undoing my paste/cut operations consistently causes LibreOffice to crash. 4. Second attempt at cut/copy invariably succeeds. I will try to grab a crash report as it seems specifically related to this bug. I noticed this immediately upon upgrading from 19.04 to 19.10, all with latest stock kernel/software/updates. IE, using the standard versions in the repositories. The behavior from this bug has the potential to cause data loss: When LibreOffice crashes before "undo" can restore the cut text, whatever chunk of data that was intended to be cut gets completely discarded and does not get recovered with the rest of the document, probably because it was stored in a buffer somewhere separate from the actual document data itself. So all in all this bug converts text into image and then deletes the data altogether. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
I had the exact same issue, upon upgrading I got the same issues as jhohertz, I followed the above instructions and the issue was fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system
Could you give the memory usage information from top before opening firefox? do you have any swap activated? -- 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/1844739 Title: Latest Firefox update freezing my system Status in firefox package in Ubuntu: New Bug description: The latest updates of firefox renders my machine useless. I'm sending it as is hopefully before it freezes completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 BuildID: 20190828152935 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 01:22:17 2019 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:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-05-01 (506 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0/20190828152935 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848228] Re: Impossible to unlock because keyboard language doesn't switch
Thank you for your bug report. What desktop environment do you use? Can you make a photo of the lock screen? If you use the default GNOME/Ubuntu session then gnome-shell does the locking and not gnome-screensaver Could you add 'journalctl -b 0' log after getting the issue? ** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1848228 Title: Impossible to unlock because keyboard language doesn't switch Status in gnome-screensaver package in Ubuntu: Incomplete Bug description: My password has latin characters. When my keyboard is switched to russian, after screen is locked, it is impossible to unlock. The screensaver lock screen has a language indicator and allows to switch the indicator. But it's still impossible to unlock. I believe the real keyboard layout doesn't switch, only the indicator switches on screen. Ubuntu 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1848228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- 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/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Invalid Status in mutter source package in Eoan: Fix Committed Bug description: [ Impact ] The "application is not responding" can make the shell hang under X11 [ Test case ] - Start an application (i.e. firefox) - Stop the process killall -STOP firefox - Close the window via the shell (using launcher right-click or window decoration button - if any - or using the activity view) - After some moments and interactions with the window the gnome shell dialog to kill the window should pop-up - The shell should be still responsive and you can get the program to run again (killall -CONT firefox) [ Regression potential ] Focus might be wrongly set to the applications or actors and instead be owned by the shell This is uploaded under the gnome MRE, so the fix doesn't need to be explicitly verified. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851407] Re: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS
1) Add an openvpn connection, which emits DHCP DNS servers, and is flagged "use only for resources on this connection" 2) Add a negative dns_priority to the connection via CLI or editing the connection Prior to the change, this worked fine, you could connect, and the indicated DNS server would become prioritised. After the change, this no longer works, and networkmanager will not associate a DNS server to the connection at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851824] Re: gnome shell freezes when too many notifications appear
The log is printed by the '$ journalctl' command, you can look around the time when you had the issue? -- 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/1851824 Title: gnome shell freezes when too many notifications appear Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm using 20.04. When I receive some notifications immediately one after the other, the shell sometimes freezes. I usually make it start again moving to a vt and doing `killall -3 gnome-shell`. This makes it work again (except it makes some apps like PyCharm and Chrome to crash). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 13:26:49 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-03 (277 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-07-21 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851349] Re: Xorg freeze
Could you add the journalctl log? -- 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/1851349 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: Installed Ubuntu 19.10. A short freeze or lag occurs with the cursor now and then. Problem with multitasking. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 10:29:50 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2019-10-18 (17 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5570 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=234e65b3-5622-44ae-9ba5-5d8a799fd811 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.4 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: X07 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.4:bd09/08/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrX07:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851725] Re: NetworkManager forgets VPN credentials
Hi Sebastien, I'm not unchecking any option, there is a default selected option for the password field which is "remember this password for this user only". And with this option, NetworkManager doesn't remember the password. With "remember the password for all users" option, NetworkManager works fine, but that's not what I want. (I hope the issue is more clear now) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, Since recently, I can't import a VPN connection in NetworkManager and store my credentials. NetworkManager will systematically forget the password, despite a log entry confirming that the operation was a success: nov. 07 22:26:52 NetworkManager[1518]: [1573162012.8680] audit: op="connection-update" uuid="3f985155-4e20-4351-88d7-14d5909a2d03" name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000 result="success" Please look at the video attached. Please fix. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 22:22:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851068] Re: laptop does not wakeup after suspend (when lid off). Need to had reset
** Package changed: pm-utils (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1851068 Title: laptop does not wakeup after suspend (when lid off). Need to had reset Status in linux package in Ubuntu: New Bug description: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My laptop is hp spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor
Thank you for your bug report. Do you use a non default cursor theme/config? Could you try in a wayland session to see if it has the issue as well? -- 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/1851340 Title: Ubuntu 19.10 upgrade results in invisible mouse cursor Status in xorg package in Ubuntu: Confirmed Bug description: Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have visible cursor with my Gnone desktop. I have found the same problem when upgrading 2 machines from Ubuntu 19.04 -> 19.10. Reproducing problem is easy: 1. Open Ubuntu Update Window 2. Select "Upgrade" 3. On completion of update (after reboot) cursor is no longer visible. 4. This applies to display connected to VGA port on host with USB Keyboard + Mouse While the connected display has no visible cursor and so is usable, I have always used X11VNC Server to provide network GUI access. On the remote X11VNC display I see and can use the cursor. This bug report is being sent via Remote X11VNC window, as I cannot use the main VGA display window (due to lack of visible cursor) I have done search online and thought that maybe issue was with my USB Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same result, no visible mouse cursor. I have done: "grep usb /var/log/syslog" and can see many USB events, including both Apple and Logitech mouse detection events. NOTE: Due to compatibility issue with X11VNC, I have disable Wayland on both machines by adding the following option to: /etc/gdm3/custom.conf WaylandEnable=false Regards, John Hartley. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 18:25:23 2019 DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo G200eR2 [1d49:0a01] InstallationDate: Installed on 2018-12-17 (322 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO System x3650 M5: -[8871AC1]- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5: -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852172] Re: Battery history and statistics graphs markings are unreadable on a dark theme
** Changed in: gnome-power-manager (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1852172 Title: Battery history and statistics graphs markings are unreadable on a dark theme Status in gnome-power-manager package in Ubuntu: New Bug description: 1 - Use a dark theme using Gnome Tweaks. 2 - Open Power Statistics 3 - Click on Laptop battery -> History or Statistics tab. The markings on the X and Y axes are not readable since the text colour does not adapt to the dark theme. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 12:25:29 2019 ExecutablePath: /usr/bin/gnome-power-statistics InstallationDate: Installed on 2019-10-19 (23 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1852172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
I can confirm the fix helped. I verified it according to the steps in this bug (bug 1845302) and also according to the steps in bug 1850046 (its gnome-shell's part). BTW when I run "killall -CONT firefox" (see the original description in this issue), the app is closed. I guess it's correct behavior because in the previous step I chosen "Quit" in the context menu of the app. If I don't choose "Quit", "killall -CONT firefox" continues running of the app as expected. Used SW: --- * Ubuntu 19.10 * mutter-common: 3.34.1+git20191107-1ubuntu1~19.10.1 * mutter: 3.34.1+git20191107-1ubuntu1~19.10.1 * gir1.2-mutter-5: 3.34.1+git20191107-1ubuntu1~19.10.1 * libmutter-5-0: 3.34.1+git20191107-1ubuntu1~19.10.1 * gnome-shell (gnome-shell-common): 3.34.1+git20191024-1ubuntu1~19.10.1 ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Invalid Status in mutter source package in Eoan: Fix Committed Bug description: [ Impact ] The "application is not responding" can make the shell hang under X11 [ Test case ] - Start an application (i.e. firefox) - Stop the process killall -STOP firefox - Close the window via the shell (using launcher right-click or window decoration button - if any - or using the activity view) - After some moments and interactions with the window the gnome shell dialog to kill the window should pop-up - The shell should be still responsive and you can get the program to run again (killall -CONT firefox) [ Regression potential ] Focus might be wrongly set to the applications or actors and instead be owned by the shell This is uploaded under the gnome MRE, so the fix doesn't need to be explicitly verified. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850046] Re: gedit freezes when opening PHP file with long lines
I've just verified a fix of the gnome-shell part of this issue in bug 1845302. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1850046 Title: gedit freezes when opening PHP file with long lines Status in gedit: New Status in gedit package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Bug description: Steps: * Download https://github.com/vrana/adminer/releases/download/v4.7.4/adminer-4.7.4.php (485 kB) * Open it in gedit Expected result: * It takes a few seconds. E.g. in Visual Studio Code editor it takes max 10 sec Actual result: * File isn't open even in a few minutes * I'm only getting a dialog "Text Editor not responding" with the buttons "Wait" and "Force quit". * Unfortunately neither "Wait" or "Force Quit" is working and Gnome stops responding, so I have to switch to text console by Ctrl + Alt + F4 and kill the gedit process. But then often when I switch back to Gnome desktop, it's still not responding (e.g. neither clicking to any application nor keyboard is working) and I have to restart OS. Used SW: * Ubuntu 19.10 * gedit 3.34.0-1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gedit 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 27 14:34:07 2019 InstallationDate: Installed on 2015-12-29 (1397 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1850046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852069] Re: Failed to backup to google drive on ubuntu 19.10
** Changed in: deja-dup (Ubuntu) Importance: Undecided => High ** Tags added: desktop-lts-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1852069 Title: Failed to backup to google drive on ubuntu 19.10 Status in Déjà Dup: Invalid Status in deja-dup package in Ubuntu: Confirmed Status in deja-dup package in Debian: New Bug description: On Ubuntu 19.10 can't do backup to Google Drive anymore with the following error message: BackendException: PyDrive backend requires PyDrive installation. Please read the manpage for setup details. Exception: No module named 'apiclient' I also could not find pydrive package or don't know how it properly called. $ lsb_release -d Description:Ubuntu 19.10 $ dpkg-query -W deja-dup duplicity deja-dup40.1-1ubuntu2 duplicity 0.8.04-2ubuntu1 The logfile for following command is empy: DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1852069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851964] Re: Volume indicator lags behind scroll action to change volume
Thanks ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1720 Importance: Unknown Status: Unknown ** Tags added: desktop-lst-wishlist ** Tags removed: desktop-lst-wishlist ** Tags added: desktop-lts-wishlist -- 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/1851964 Title: Volume indicator lags behind scroll action to change volume Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Changing the volume with the help of the mouse/touchpad, scrolling on top of the sound icon used to work fine in the older versions of gnome shell. In Ubuntu 19.10, it does not. I scroll, but the graphic indicator that shows on the screen lags behind, even jumps. If needed, I could try to record it as video. There is definitely some performance issue over there. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc6-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 9 23:50:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (21 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1-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/1851964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851725] Re: NetworkManager forgets VPN credentials
The description didn't mention that you are unchecking the 'for all users' option (which is default?), so it's only an issue in that case? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials Status in network-manager package in Ubuntu: Incomplete Bug description: Hi, Since recently, I can't import a VPN connection in NetworkManager and store my credentials. NetworkManager will systematically forget the password, despite a log entry confirming that the operation was a success: nov. 07 22:26:52 NetworkManager[1518]: [1573162012.8680] audit: op="connection-update" uuid="3f985155-4e20-4351-88d7-14d5909a2d03" name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000 result="success" Please look at the video attached. Please fix. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 22:22:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852254] Re: Dock stays ontop of Xscreensaver
Thank you for your bug report. How do you use Xscreensaver on GNOME? Doesn't it conflict with the build it lock screen? or are you talking about the GNOME lock screen? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1852254 Title: Dock stays ontop of Xscreensaver Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date at 12/11/2019 As requested on bug: https://bugs.launchpad.net/ubuntu/+source/gnome- shell-extension-ubuntu-dock/+bug/1849787 I am creating a new bug for gnome-shell as several users experience the dock to be ontop My case the dock stays ontop of Xscreensaver, but only at random times i cannot reproduce when ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 12 14:49:29 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-25 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-10-25T10:03:18.026469 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This work-around is working for me: https://askubuntu.com/a/1183074/256054 However, this is only a work-around and the bug remains. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852265] Re: Nautilus hangs when right-click->properties is selected on file
Thanks for your interest in helping to resolve this issue. In order to get to the bottom of this we need to figure out where the program is hanging. If you can follow the steps on https://wiki.ubuntu.com/Backtrace#Already_running_programs and attach the generated text file to this bug it would be of great help. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1852265 Title: Nautilus hangs when right-click->properties is selected on file Status in nautilus package in Ubuntu: Incomplete Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 18.04.3 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center nautilus: Installed: 1:3.26.4-0~ubuntu18.04.4 Candidate: 1:3.26.4-0~ubuntu18.04.4 Version table: *** 1:3.26.4-0~ubuntu18.04.4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) What you expected to happen 4) What happened instead A directory containing any amount of files (may be just few, may be hundreds of files) is opened. Some file is right-clicked and Properties is selected, after which Nautilus hangs immediately. It can be killed with "killall -9 nautilus" command, after which one must wait for short time before Nautilus can be started again. If it is started too soon, it will not start, it just prints text: "Failed to register: Timeout was reached" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Nov 12 15:58:19 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'958x757+2151+138'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'RabbitVCS::age_column', 'RabbitVCS::author_column', 'RabbitVCS::revision_column', 'RabbitVCS::status_column']" InstallationDate: Installed on 2018-10-25 (383 days ago) InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: copy/paste (clipboard) is broken in Ubuntu 19.10
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #919 https://gitlab.gnome.org/GNOME/mutter/issues/919 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/919 Importance: Unknown Status: Unknown ** Summary changed: - copy/paste (clipboard) is broken in Ubuntu 19.10 + [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: copy/paste (clipboard) is broken in Ubuntu 19.10
Whoops, I was testing Ubuntu on X11 and Debian on Wayland. I switch to X11 on Debian and this is indeed reproducible there (see attached). I will report this upstream. ** Attachment added: "libreoffice-6.3.3.2-snap1 - Debian X.mov" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852183/+attachment/5304850/+files/libreoffice-6.3.3.2-snap1%20-%20Debian%20X.mov ** Changed in: mutter (Ubuntu) Status: New => 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/1852183 Title: copy/paste (clipboard) is broken in Ubuntu 19.10 Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Attached is the output from that command. ** Attachment added: "Output from jounralctl -b 0 on affected system" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+attachment/5304835/+files/log.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software Status in gnome-software package in Ubuntu: Incomplete Bug description: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen in Ubuntu 18.04 and newer, with official and 3rd party packages (like those from virtualbox.org). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848399] Re: update-grub fails if zpools with unsupported feature_flags exist
** No longer affects: ubiquity (Ubuntu) ** No longer affects: zsys (Ubuntu) ** Also affects: grub2 (Ubuntu Focal) Importance: High Assignee: Jean-Baptiste Lallement (jibel) Status: Triaged -- 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/1848399 Title: update-grub fails if zpools with unsupported feature_flags exist Status in grub2 package in Ubuntu: Triaged Status in grub2 source package in Focal: Triaged Bug description: install from Oct 14 live installer failed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.20 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.425 Date: Wed Oct 16 20:03:30 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed quiet splash --- LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Possibly linked to this bug? https://bugs.launchpad.net/ubuntu/+source /gnome-software/+bug/1778607 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software Status in gnome-software package in Ubuntu: Incomplete Bug description: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen in Ubuntu 18.04 and newer, with official and 3rd party packages (like those from virtualbox.org). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Note that the output was from an Ubuntu 18.04 VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software Status in gnome-software package in Ubuntu: Incomplete Bug description: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen in Ubuntu 18.04 and newer, with official and 3rd party packages (like those from virtualbox.org). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
** Description changed: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to - happen from Ubuntu 18.04, with official and 3rd party packages (like - those from virtualbox.org). + happen in Ubuntu 18.04 and newer, with official and 3rd party packages + (like those from virtualbox.org). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software Status in gnome-software package in Ubuntu: Incomplete Bug description: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen in Ubuntu 18.04 and newer, with official and 3rd party packages (like those from virtualbox.org). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked
Can you connect to that VPN with the same settings, but from a virtual machine with a freshly installed system? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Hi, after recent update few days ago, I noticed that DNS is not configured if "Use this connection only for resources" on its network is ticked, for OpenVPN, which used to work till latest update. My config: - IPv4 Method: Automatic (DHCP) - DNS: 10.1.0.1, Automatic: Off - Routes: Automatic: On - [x] Use this connection ... If OpenVPN is setup to work for all resources, then DNS is configured properly. It would be nice if DNS is also configured as before. BR Uros Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager-openvpn: Installed: 1.8.2-1 Candidate: 1.8.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1851793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852053] Re: Nautilus Crashes when opening search field and entering first character
Thanks, could you do the same with the dbgsym mentioned installed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1852053 Title: Nautilus Crashes when opening search field and entering first character Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 19.10 one week ago. Then all worked fine. Nothing major changed as far as I know. But now: - click in Dock on the file stack icon to open Nautilus - stay in Home or browse to any folder - click Ctrl-F to open search field at the top of window - enter any character as first character of search pattern - Nautilus immediately crashes and window disappears immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked
How to test on LTS/production machine? (it's not really experimental machine) ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Hi, after recent update few days ago, I noticed that DNS is not configured if "Use this connection only for resources" on its network is ticked, for OpenVPN, which used to work till latest update. My config: - IPv4 Method: Automatic (DHCP) - DNS: 10.1.0.1, Automatic: Off - Routes: Automatic: On - [x] Use this connection ... If OpenVPN is setup to work for all resources, then DNS is configured properly. It would be nice if DNS is also configured as before. BR Uros Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager-openvpn: Installed: 1.8.2-1 Candidate: 1.8.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1851793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851793] Re: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked
The behavior described in this bug seems to be consistent with what is the default in Eoan (19.10). Uros, are you able to check if 19.10 network-manager is also affected with this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Hi, after recent update few days ago, I noticed that DNS is not configured if "Use this connection only for resources" on its network is ticked, for OpenVPN, which used to work till latest update. My config: - IPv4 Method: Automatic (DHCP) - DNS: 10.1.0.1, Automatic: Off - Routes: Automatic: On - [x] Use this connection ... If OpenVPN is setup to work for all resources, then DNS is configured properly. It would be nice if DNS is also configured as before. BR Uros Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager-openvpn: Installed: 1.8.2-1 Candidate: 1.8.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1851793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845302] Re: cannot click on others opened applications while the "application not responding" dialog is opened
** Description changed: [ Impact ] The "application is not responding" can make the shell hang under X11 [ Test case ] - Start an application (i.e. firefox) - Stop the process - killall -STOP firefox + killall -STOP firefox + - Close the window via the shell (using launcher right-click or window + decoration button - if any - or using the activity view) - After some moments and interactions with the window the gnome shell - dialog to kill the window should pop-up + dialog to kill the window should pop-up - The shell should be still responsive and you can get the program to - run again (killall -CONT firefox) + run again (killall -CONT firefox) [ Regression potential ] Focus might be wrongly set to the applications or actors and instead be owned by the shell This is uploaded under the gnome MRE, so the fix doesn't need to be explicitly verified. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME -- 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/1845302 Title: cannot click on others opened applications while the "application not responding" dialog is opened Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Invalid Status in mutter source package in Eoan: Fix Committed Bug description: [ Impact ] The "application is not responding" can make the shell hang under X11 [ Test case ] - Start an application (i.e. firefox) - Stop the process killall -STOP firefox - Close the window via the shell (using launcher right-click or window decoration button - if any - or using the activity view) - After some moments and interactions with the window the gnome shell dialog to kill the window should pop-up - The shell should be still responsive and you can get the program to run again (killall -CONT firefox) [ Regression potential ] Focus might be wrongly set to the applications or actors and instead be owned by the shell This is uploaded under the gnome MRE, so the fix doesn't need to be explicitly verified. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841709] Re: [regression] gobject.h:767: syntax error
No such error in build log for
https://launchpad.net/ubuntu/+source/mutter/3.34.1+git20191107-1ubuntu1~19.10.1/+build/18090903
So, marking it verified.
** Tags removed: verification-needed verification-needed-eoan
** Tags added: verification-done verification-done-eoan
--
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/1841709
Title:
[regression] gobject.h:767: syntax error
Status in mutter package in Ubuntu:
Fix Released
Status in mutter source package in Eoan:
Fix Committed
Bug description:
[ Impact ]
Building mutter triggers various non-fatal syntax errors:
/usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected '/' in
' do { if g_type_check_instance_is_fundamentally_a ((GTypeInstance*)
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*)
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while
(0);' at '/'
/usr/include/glib-2.0/gobject/gobject.h:767: syntax error, unexpected ')',
expecting identifier or '(' in ' do { if
g_type_check_instance_is_fundamentally_a ((GTypeInstance*)
((weak_pointer)), (((GType) ((20) << (2) ; else g_assertion_message
(/"CoglPango/", "/usr/include/glib-2.0/gobject/gobject.h", 767, ((const char*)
(__func__)), "'" "G_IS_OBJECT (weak_pointer)" "' should be TRUE"); } while
(0);' at ')'
/usr/include/glib-2.0/gobject/gobject.h:770: syntax error, unexpected ')',
expecting identifier or '(' in '# 770
"/usr/include/glib-2.0/gobject/gobject.h"' at ')'
Looks like the offending release glib2.0 (2.61.2-2) is from last
night's updates.
[ Test case ]
- Just build mutter and ensure that no such errors are triggered
[ Regression potential ]
None, once it builds we're all happy :)
---
ProblemType: BugDistroRelease: Ubuntu 19.10
Package: libglib2.0-dev 2.61.2-2
ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
Uname: Linux 5.2.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Wed Aug 28 11:30:06 2019
InstallationDate: Installed on 2019-05-02 (117 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64
(20190501)SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841709/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Fix Committed Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1051625] Re: nautilus crashed with signal 5 in _XEventsQueued()
This bug appeared on up to date ubuntu xenial just now, bugs just don't disappear themselves therefor i don't get the reasoning behind no new report added so it must be solved logic. People don't report new ones for to known bug because it is already reported, so it is not surprising that most people came here saw this bug and said "yeah that is exactly what happened to me, so they are aware of the problem no need the re- report same bug" This issue should re-open not new one this one because that is how issues work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1051625 Title: nautilus crashed with signal 5 in _XEventsQueued() Status in nautilus package in Ubuntu: Invalid Status in nemo package in Ubuntu: Confirmed Bug description: Bug report prompt appeared when printing in Libreoffice Calc. Not sure about the actual cause. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Mon Sep 17 00:02:19 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+478+220'" InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcCmdline: nautilus trash:// ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with signal 5 in _XEventsQueued() UpgradeStatus: Upgraded to quantal on 2012-09-08 (8 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1051625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791069] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
*** This bug is a duplicate of bug 1764417 *** https://bugs.launchpad.net/bugs/1764417 Please note that I have unsubscribed off this bug report because I am no longer experiencing it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1791069 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: New Bug description: This is a duplicate of #1764417 (and probably also of #1663839), I'd like to provide extra logs and not clutter the existing report. Roughly two minutes after logging in, I was confronted with another gdm login screen after this had been logged Sep 6 13:31:22 mysystem gnome-session[2983]: gnome-session-binary[2983]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 6 13:31:22 mysystem gnome-session-binary[2983]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Sep 6 13:31:22 mysystem gnome-session-binary[2983]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Sep 6 13:31:22 mysystem gnome-session[2983]: gnome-session-binary[2983]: CRITICAL: We failed, but the fail whale is dead. Sorry Sep 6 13:31:22 mysystem gnome-session-binary[2983]: CRITICAL: We failed, but the fail whale is dead. Sorry Sep 6 13:31:22 mysystem kernel: [ 163.130657] rfkill: input handler enabled Sep 6 13:31:22 mysystem at-spi-bus-launcher[3085]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 6 13:47:32 2018 SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-08-15 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1791069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
3.34.1+git20191107-1ubuntu1~19.10.1 Confirmed fixed here too. -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Fix Committed Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852101] Re: Monitors keep turning on when in power saving mode, every time.
The issue persisted on my last computer, which would have a completely different user, and I was not using GNOME Extensions at that point. -- 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/1852101 Title: Monitors keep turning on when in power saving mode, every time. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whenever I lock my computer, or it goes into power saving mode automatically, the monitors turn back on and show the lock screen a few seconds later. This has persisted now for about a year, has persisted across multiple upgrades (18.10, 19.04, 19.10) as well as complete hardware replacement (CPU intel -> AMD, GPU nVidia -> AMD). So I'm convinced this is a software bug. The first line in logging that I can find that seems to trigger this is: "gnome-shell[1967]: ../../../gobject/gsignal.c:2647: instance '0x55daa50a2920' has no handler with id '145952'" I update my system regularly, so this looks to either be a regression, or uncaught bug. I don't know if other things are causing this, but that's the first line (based on time) that is reported when it turns the monitors back on. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 09:40:42 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-03-08 (247 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-11-05 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Upstream fix is most likely https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/763
I have installed gnome-shell{,-common}
3.34.1+git20191024-1ubuntu1~19.10.1 from eoan-proposed and verified that
the "opening activities" delay goes down from ~4 seconds in
3.34.1-1ubuntu1 to <1 second in the -proposed package, while having a
total of 22 windows open.
I have not done any serious regression testing, so not changing the tag.
--
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/1848009
Title:
Delay launching application launcher gets longer the more apps are
open
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Eoan:
Fix Committed
Bug description:
[ Impact ]
On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD.
If I launch a bunch of applications - possibly a slightly unreasonable
number, but a lot anyway - with minimal CPU or memory in use, the button to
launch applications in the bottom left takes progressively longer to run.
Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ
[ Test case ]
- Launch lots of applications
- Click in the applications icon in the launcher (or press super+A)
- Animation should not be delayed (some delay is still expected depending
on the number of installed applications)
[ Regression potential ]
Windows in activities overview might have wrong positioning
This is uploaded under the GNOME MRE:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
---
Steps to reproduce.
Open application launcher
Note a ~0.6s delay before the icons fly onto the screen
Open GNOME Software
Install all the editors picks
Launch a bunch of applications
Click the application launcher
Note a 4s delay before icons fly onto the screen.
Expectation
Honestly, no delay at all, but it should be at least consistent with when no
applications are running, so 0.6s delay as per the state when no apps are
launched.
ProblemType: BugDistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 13:02:04 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-13 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1SourcePackage:
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/1848009/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
