[Desktop-packages] [Bug 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
Command "journalctl -b 0" looks like there are data from last start-up, but "journalctl -b 1" in my case returns data from "April 2020", that is why I have searched for the biggest number to get that date data. I am attaching "journalctl -b 1" output. ** Attachment added: "journal_1.txt" https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903986/+attachment/5434687/+files/journal_1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in remmina package in Ubuntu: New Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
Confirming, it affects me at well (20.04). -- 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/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in Webkit: Fix Released Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904368] [NEW] eclipse ide has huge padding and inconsistencies
Public bug reported: Eclipse 4.6.3 has compact widgets and layout using Ambiance theme in ubuntu 20.04.1 LTS. However, when using default Yaru theme, the look and feel has huge padding and layout. GTK 3.20+ has this issue. Ubuntu 16.04 has proper themeing. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1904368 Title: eclipse ide has huge padding and inconsistencies Status in yaru-theme package in Ubuntu: New Bug description: Eclipse 4.6.3 has compact widgets and layout using Ambiance theme in ubuntu 20.04.1 LTS. However, when using default Yaru theme, the look and feel has huge padding and layout. GTK 3.20+ has this issue. Ubuntu 16.04 has proper themeing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1904368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Testing the fix for this one is actually simpler than that. Just download and install: https://launchpad.net/ubuntu/+source/gnome-shell-extension- appindicator/33.1-0ubuntu0.20.04.1/+build/20167910/+files/gnome-shell- extension-appindicator_33.1-0ubuntu0.20.04.1_all.deb Then log out and log in again. -- 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/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
I'm running Pop OS 20.04 with this bug, I'd be happy to test this if I knew how to install the patch. Do I just need to enable proposed packages? -- 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/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@smurf, I heard this wifi+bt module needs to install a dkms. I will ask my colleague about it. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions
** Tags added: fixed-in-3.36.8 -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880282] Re: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1876484 *** https://bugs.launchpad.net/bugs/1876484 ** This bug has been marked a duplicate of bug 1876484 [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all -- 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/1880282 Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi, I did try to upgrade kernel 5.6 and also 5.7. So it did fix the problem with Nvidia driver and now Xorg driver is working. But my computer doesn't give any sound. It recognizes the device and also even shows sound works, but I don't get any sound. If I use Nvidia drivers, the sound does work, but on Xorg driver it isn't - https://i.imgur.com/LmmXRad.png I did also check alsamixer and pulse control, did set up the sound, but any changes https://i.imgur.com/EHRsxj6.png If I add any headphones or others speakers, sound work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.7.0-050700rc6-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iron-mike 2519 F pulseaudio iron-mike 6505 F alsamixer CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 10:24:44 2020 InstallationDate: Installed on 2020-05-22 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: iron-mike 2519 F pulseaudio iron-mike 6505 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: AMI dmi.bios.version: F.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8519 dmi.board.vendor: HP dmi.board.version: 11.72 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.40:bd11/27/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8519:rvr11.72:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 4UU78EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-22T23:09:17.197956 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1880282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904332] Re: [HP Pavilion x360 Convertible 14-dh1xxx] No sound
** Summary changed: - no sound issue + [HP Pavilion x360 Convertible 14-dh1xxx] No sound -- 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/1904332 Title: [HP Pavilion x360 Convertible 14-dh1xxx] No sound Status in pulseaudio package in Ubuntu: New Bug description: I have a ubuntu budgie environment. Though the speakers (hardware) are detected, no sound is audible despite the volume levels being maximum. I performed tests in the sound settings window, so the issue does not seem to be specific to a particular application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berry 1239 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sun Nov 15 21:07:24 2020 InstallationDate: Installed on 2020-11-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 866E dmi.board.vendor: HP dmi.board.version: 90.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd06/11/2020:svnHP:pnHPPavilionx360Convertible14-dh1xxx:pvrType1ProductConfigId:rvnHP:rn866E:rvr90.08:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-dh1xxx dmi.product.sku: 231T1PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Confirmed Status in gnome-shell-extension-desktop-icons source package in Groovy: Confirmed Bug description: See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904101] Re: Ctrl+H in Files crashes gnome-shell
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 and Nov 16 10:23:47 kab gnome-shell[2046]: St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) Nov 16 10:23:47 kab gnome-shell[2046]: Bail out! St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) Nov 16 10:23:47 kab gnome-shell[2046]: GNOME Shell crashed with signal 6 Nov 16 10:23:47 kab gnome-shell[2046]: == Stack trace for context 0x55be7c278260 == Nov 16 10:23:47 kab gnome-shell[2046]: #0 55be7c8ff7a8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (11a11477d790 @ 10) Nov 16 10:23:47 kab gnome-shell[2046]: #1 7ffd435e1f00 b self-hosted:225 (3e1435399a60 @ 273) Nov 16 10:23:47 kab gnome-shell[2046]: #2 55be7c8ff710 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (11a11477d7e0 @ 43) Nov 16 10:23:47 kab gnome-shell[2046]: #3 55be7c8ff680 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:209 (11a11477d920 @ 32) Nov 16 10:23:47 kab gnome-shell[2046]: #4 55be7c8ff5f8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:104 (11a11477dbf0 @ 31) -- 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/1904101 Title: Ctrl+H in Files crashes gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you do Ctrl + H more than two times. Gnome will crash and close the session. The same happen if you use the GUI - menu dialogue Show Hidden Files. Description: Ubuntu 20.10 Release: 20.10 Codename: groovy 5.8.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904101] Re: Crtl + H crash Files sesion restart
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 Here it is: https://errors.ubuntu.com/oops/eee35ca0-27b2-11eb-804f-fa163e6cac46 ** Tags added: groovy ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Confirmed ** Package changed: gnome-shell-extension-desktop-icons (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - Crtl + H crash Files sesion restart + Crtl+H in Files crashes gnome-shell ** Summary changed: - Crtl+H in Files crashes gnome-shell + Ctrl+H in Files crashes gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1904101 Title: Ctrl+H in Files crashes gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you do Ctrl + H more than two times. Gnome will crash and close the session. The same happen if you use the GUI - menu dialogue Show Hidden Files. Description: Ubuntu 20.10 Release: 20.10 Codename: groovy 5.8.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Confirmed Status in gnome-shell-extension-desktop-icons source package in Groovy: Confirmed Bug description: See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904101] Re: Ctrl+H in Files crashes gnome-shell
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1898005, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1898005 gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() -- 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/1904101 Title: Ctrl+H in Files crashes gnome-shell Status in gnome-shell package in Ubuntu: Confirmed Bug description: If you do Ctrl + H more than two times. Gnome will crash and close the session. The same happen if you use the GUI - menu dialogue Show Hidden Files. Description: Ubuntu 20.10 Release: 20.10 Codename: groovy 5.8.0-26-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904230] Re: System freeze after logging onto desktop session
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904230 Title: System freeze after logging onto desktop session Status in Ubuntu: Incomplete Bug description: After performing a recent update, I am encountering a complete system freeze shortly after logging on to a graphical session but only for a single user (which may suggest a corrupted configuration file somewhere). This is repeatable - happens every time I attempt to login. The desktop is LXDE however it also occurs with Openbox as well. Furthermore, it also happens when launching a desktop with vncserver which suggests it is not a graphics driver issue. I've tried deleting (renaming) the .config and .cache folders in the account, neither of these have had any effect. Am fairly sure I have seen this once or twice in the past but it was a pretty rare event. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.25 Architecture: amd64 Date: Fri Nov 13 17:44:30 2020 InstallationDate: Installed on 2013-07-25 (2668 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to xenial on 2018-12-28 (686 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904237] Re: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1904237 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal ** Tags added: osk -- 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/1904237 Title: [regression] On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in mutter package in Ubuntu: Confirmed Bug description: mutter 3.36.6-1ubuntu0.20.04.2 shows again the incorrect behavior that was fixed in https://bugs.launchpad.net/mutter/+bug/1880596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1904237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713650] Re: Can't Alt+drag windows at all any more
We've now been using Super+drag for a few years in Ubuntu so I think people are getting used to it. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1713650 Title: Can't Alt+drag windows at all any more Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: Alt+drag doesn't move windows like it should. I think this might be a Wayland-specific problem in Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Keyboard/mouse/touchpad configuration not applied on hotplug/reconnect/resume
** Summary changed: - Keyboard and mouse configuration not persisting on USB keyboard unplug/reconnect + Keyboard/mouse/touchpad configuration not applied on hotplug/reconnect/resume ** Tags added: groovy rls-gg-incoming ** Summary changed: - Keyboard/mouse/touchpad configuration not applied on hotplug/reconnect/resume + Keyboard/mouse/touchpad configuration not applied on hotplug/reconnect/resume in Xorg sessions ** Summary changed: - Keyboard/mouse/touchpad configuration not applied on hotplug/reconnect/resume in Xorg sessions + Input device settings not applied on hotplug/reconnect/resume in Xorg sessions -- 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/1899206 Title: Input device settings not applied on hotplug/reconnect/resume in Xorg sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904325] Re: half the steam games won't launch.
Please try launching one/some from a Terminal window so we can see any errors being printed. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - half the steam games won't launch. + Half the Steam games won't launch on Intel Atom N455 -- 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/1904325 Title: Half the Steam games won't launch on Intel Atom N455 Status in Ubuntu: Incomplete Bug description: games launch only by using LIBGL_ALWAYS_SOFTWARE=1 %command% in game launch options. These games used to run fine on an older linux mint version, but now they won't launch no matter if i use lubuntu or lxde. only LIBGL_ALWAYS_SOFTWARE=1 %command% helps, but it significantly slows down the game. All the graphics drivers should be up to date. i am using Ubuntu 18.04.5 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-123.126-generic 4.15.18 Uname: Linux 4.15.0-123-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Sun Nov 15 16:18:40 2020 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-122-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-123-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-60-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] InstallationDate: Installed on 2020-11-07 (8 days ago) InstallationMedia: LXLE 18.04 - Release i386 MachineType: Hewlett-Packard HP Mini 210-2000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-123-generic root=/dev/mapper/qwerty--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-09-08 (434 days ago) dmi.bios.date: 03/14/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1584 dmi.board.vendor: Hewlett-Packard dmi.board.version: 85.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd03/14/2012:svnHewlett-Packard:pnHPMini210-2000:pvr059010202B0300100:rvnHewlett-Packard:rn1584:rvr85.37:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-2000 dmi.product.version: 059010202B0300100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1904325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904359] [NEW] window goes blank when trying to delete manual IP address
Public bug reported: I have 2 manually configured IPv4 addresses. When I click the trash bin icon beside the IP address to delete it the page goes blank and the IP address will not delete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 16:11:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-11-04 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshots" https://bugs.launchpad.net/bugs/1904359/+attachment/5434638/+files/capture.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1904359 Title: window goes blank when trying to delete manual IP address Status in gnome-control-center package in Ubuntu: New Bug description: I have 2 manually configured IPv4 addresses. When I click the trash bin icon beside the IP address to delete it the page goes blank and the IP address will not delete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 16:11:55 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-11-04 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1904359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) It seems that the patch in 171 does not work (i.e. touchpad is still dead) on kernels older than 5.8. I tried 5.4.75, 5.7.19, and 5.8.18. I don't really want to look into this further since I'm fine with the newer kernel, but wanted to give you and any other users a heads up in case they find themselves in a similar situation. The kernels I was testing were taken straight from Ubuntu's mainline kernel page, and had only the following changes: CONFIG_PINCTRL_AMD was made into a module, specified line in pinctrl-amd.c was commented out. Thanks again for all of your help in making the linux experience with this class of laptop much more enjoyable! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.boar
[Desktop-packages] [Bug 1904344] [NEW] Libreoffice window becomes unstable for one or two seconds when it opens
Public bug reported: Every time I open Libreoffice Writer in Ubuntu 20.04, the window of the application becomes unstable for one or two seconds. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1904344 Title: Libreoffice window becomes unstable for one or two seconds when it opens Status in libreoffice package in Ubuntu: New Bug description: Every time I open Libreoffice Writer in Ubuntu 20.04, the window of the application becomes unstable for one or two seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904343] [NEW] WiFi Working, Wired connection not.
Public bug reported: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: connection ethernet network network-manager wired -- 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/1904343 Title: WiFi Working, Wired connection not. Status in network-manager package in Ubuntu: New Bug description: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1904343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713650] Re: Can't Alt+drag windows at all any more
Gnome now differs from every single other window manager. I understand that alt+drag interferes with some former mac users' workflows, but really, we've been here for 20 years and they just arrived... why should we change our workflows to suit theirs? Can we please revert to the default, and make this a tick-box option upon installation, or in keyboard settings? (Ie. "Do you use . names of applications " or even better, put the option in those applications. Can anyone link to where Gnome made this decision? TLDR: it's super frustrating that Gnome now has a different default shortcut key from every single other window manager. -- 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/1713650 Title: Can't Alt+drag windows at all any more Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Alt+drag doesn't move windows like it should. I think this might be a Wayland-specific problem in Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1713650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Ok, I upgraded to 20.10, but in my case there are no changes, I see exactly the same behavior than in 20.04 . I would appreciate a lot a bit of help. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904334] [NEW] [Audigy2 - SB Audigy 5/Rx [SB1550], playback] No sound at all
Public bug reported: no sound at all. i am using creative soundblaster sound card ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 21:52:15 2020 InstallationDate: Installed on 2020-11-14 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 successful Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_SpeakerTestPulseStderr: W r i t e e r r o r : - 3 2 , B r o k e n p i p e W r i t e e r r o r : - 3 2 , B r o k e n p i p e W r i t e e r r o r : - 3 2 , B r o k e n p i p e Symptom_Type: No sound at all Title: [Audigy2 - SB Audigy 5/Rx [SB1550], playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 DL dmi.board.name: G41MT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7DL:bd10/24/2011:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904334 Title: [Audigy2 - SB Audigy 5/Rx [SB1550], playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: no sound at all. i am using creative soundblaster sound card ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 21:52:15 2020 InstallationDate: Installed on 2020-11-14 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audigy2 successful Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_SpeakerTestPulseStderr: W r i t e e r r o r : - 3 2 , B r o k e n p i p e W r i t e e r r o r : - 3 2 , B r o k e n p i p e W r i t e e r r o r : - 3 2 , B r o k e n p i p e Symptom_Type: No sound at all Title: [Audigy2 - SB Audigy 5/Rx [SB1550], playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 DL dmi.board.name: G41MT-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7DL:bd10/24/2011:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41MT-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow
My system randomly freeze with these kind of messages attached. I'm streaming music from this computer (samoa) and everything works fine, the streaming continue without problem. But I can't login locally. I can login remotely from another computer and kill many processeson samoa, but I am unable to perform a shutdown! I had to do a hard reset... ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870597/+attachment/5434542/+files/syslog.extract.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says: scheduled expiry is in the past... your system is too slow Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm-x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904332] Re: no sound issue
** Package changed: ubuntu => pulseaudio (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/1904332 Title: no sound issue Status in pulseaudio package in Ubuntu: New Bug description: I have a ubuntu budgie environment. Though the speakers (hardware) are detected, no sound is audible despite the volume levels being maximum. I performed tests in the sound settings window, so the issue does not seem to be specific to a particular application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berry 1239 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sun Nov 15 21:07:24 2020 InstallationDate: Installed on 2020-11-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 866E dmi.board.vendor: HP dmi.board.version: 90.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd06/11/2020:svnHP:pnHPPavilionx360Convertible14-dh1xxx:pvrType1ProductConfigId:rvnHP:rn866E:rvr90.08:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-dh1xxx dmi.product.sku: 231T1PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1904332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904332] [NEW] no sound issue
You have been subscribed to a public bug: I have a ubuntu budgie environment. Though the speakers (hardware) are detected, no sound is audible despite the volume levels being maximum. I performed tests in the sound settings window, so the issue does not seem to be specific to a particular application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berry 1239 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sun Nov 15 21:07:24 2020 InstallationDate: Installed on 2020-11-15 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 866E dmi.board.vendor: HP dmi.board.version: 90.08 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd06/11/2020:svnHP:pnHPPavilionx360Convertible14-dh1xxx:pvrType1ProductConfigId:rvnHP:rn866E:rvr90.08:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-dh1xxx dmi.product.sku: 231T1PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- no sound issue https://bugs.launchpad.net/bugs/1904332 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 838381] Re: The cursor in active terminal window stops blinking after ten seconds.
Taking a second look at my workaround, I realize now that the "Settings Editor" is actually xfce4-settings-editor so this presumably only applies to Xubuntu or a system which otherwise has xfce as the desktop environment. -- 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/838381 Title: The cursor in active terminal window stops blinking after ten seconds. Status in GNOME Terminal: Invalid Status in gnome-terminal package in Ubuntu: Confirmed Bug description: When the cursor stops blinking, you start to wonder if something is wrong. The point is that the cursor should never stop blinking in an active terminal window. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Wed Aug 31 23:46:47 2011 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-08-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/838381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 838381] Re: The cursor in active terminal window stops blinking after ten seconds.
I thought I would add the workaround I found which applies to Xubuntu 18.04 but possibly others: To make the cursor keep blinking in GTK-based applications (which includes gnome-terminal, xfce4-terminal, gedit, pidgin and many others): 1. Open Settings Editor from the Settings menu. 2. Select the xsettings "channel" on the left side of the interface. 3. Click New. 4. The name of the property needs to be /Gtk/CursorBlinkTimeout 5. Set it to be an integer property. 6. Specify a very large number (but less than 2 billion). 7. Click Save Here's hoping the GNOME group somehow ceases to exist in the near future. -- 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/838381 Title: The cursor in active terminal window stops blinking after ten seconds. Status in GNOME Terminal: Invalid Status in gnome-terminal package in Ubuntu: Confirmed Bug description: When the cursor stops blinking, you start to wonder if something is wrong. The point is that the cursor should never stop blinking in an active terminal window. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-terminal 3.0.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Wed Aug 31 23:46:47 2011 ExecutablePath: /usr/bin/gnome-terminal InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110402) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to oneiric on 2011-08-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/838381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Thanks, that worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904325] [NEW] half the steam games won't launch.
Public bug reported: games launch only by using LIBGL_ALWAYS_SOFTWARE=1 %command% in game launch options. These games used to run fine on an older linux mint version, but now they won't launch no matter if i use lubuntu or lxde. only LIBGL_ALWAYS_SOFTWARE=1 %command% helps, but it significantly slows down the game. All the graphics drivers should be up to date. i am using Ubuntu 18.04.5 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-123.126-generic 4.15.18 Uname: Linux 4.15.0-123-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Sun Nov 15 16:18:40 2020 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-122-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-123-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-60-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] InstallationDate: Installed on 2020-11-07 (8 days ago) InstallationMedia: LXLE 18.04 - Release i386 MachineType: Hewlett-Packard HP Mini 210-2000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-123-generic root=/dev/mapper/qwerty--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-09-08 (434 days ago) dmi.bios.date: 03/14/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1584 dmi.board.vendor: Hewlett-Packard dmi.board.version: 85.37 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd03/14/2012:svnHewlett-Packard:pnHPMini210-2000:pvr059010202B0300100:rvnHewlett-Packard:rn1584:rvr85.37:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV dmi.product.name: HP Mini 210-2000 dmi.product.version: 059010202B0300100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1904325 Title: half the steam games won't launch. Status in xorg package in Ubuntu: New Bug description: games launch only by using LIBGL_ALWAYS_SOFTWARE=1 %command% in game launch options. These games used to run fine on an older linux mint version, but now they won't launch no matter if i use lubuntu or lxde. only LIBGL_ALWAYS_SOFTWARE=1 %command% helps, but it significantly slows down the game. All the graphics drivers should be up to date. i am using Ubuntu 18.04.5 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-123.126-generic 4.15.18 Uname: Linux 4.15.0-123-generic i686 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.20 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: LXDE Date: Sun Nov 15 16:18:40 2020 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-122-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-123-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-60-generic, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] Subsystem: Hewlett-Packard Company Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [103c:1584] Instal
[Desktop-packages] [Bug 1903893] Re: [snap] Notifications do not show a custom icon
As an aside, I notice Brave browser notifications images are visible, using a different path. image-path: "/run/user/1000/snap.brave/.org.chromium.Chromium.m5lyvv" -- 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/1903893 Title: [snap] Notifications do not show a custom icon Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Notification coming from Chromium web browser ( as a snap ) show generic icon instead of favicon or website icon or any website picture. For reference ⋅ https://forum.snapcraft.io/t/notifications-in-chromium-show-generic-icon/21079 ⋅ https://github.com/solus-project/budgie-desktop/pull/2000#issuecomment-653833784 ⋅ https://discourse.ubuntubudgie.org/t/notification-issues/434 It's *not* specific to ( Ubuntu ) Budgie. And to some extent might affect any chromium snap based web browser. Interesting insight in second link, quoting : « Chromium based browser notifications pop up with broken icon images. This is due to the fact these browsers prefix the icon name in the notification with "file:///". Furthermore, snap based chromium browsers save the temporary icon in the snap, and don't pass the correct path to Raven. If the icon names start with "file:///", clearing the icon name fixes both of these issues by allowing the browsers to show the correct image (same as Firefox does), and allows the snaps to default to the fallback "mail-unread-symbolic" icon, instead of showing a broken image icon. This fix also should have absolutely no effect on any other notifications. » Attachment : top right is the actual notification ( with unread mail icon ) it should show : ⋅ ideally, picture from site ( cover art in that case, it's a music streaming site, as done in Firefox in same situation ) ⋅ or (fav)icon for the site ( deezer here, which icon is shown a bit above in workspaces applet in top panel ) ⋅ or web browser icon ( chromium ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
> The second rule allows firefox to load and run code from that location.
> But doesn't allow firefox to write to it. So if there is malware [...]
That's correct for the added rule, but the profile also has
owner @{HOME}/.{firefox,mozilla}/** rw,
which means firefox _can_ write to that location.
However, this doesn't make the new rule for @{HOME}/.mozilla/firefox
/*/gmp-widevinecdm/*/lib*so m, too bad because the profile also allows m
for plugins already.
owner @{HOME}/.{firefox,mozilla}/plugins/** rm,
owner @{HOME}/.{firefox,mozilla}/**/plugins/** rm,
which already allows to run code from more writeable locations.
--
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/1777070
Title:
firefox plugin libwidevinecdm.so crashes due to apparmor denial
Status in apparmor package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1
Running firefix, then going to netflix.com and attempting to play a
movie. The widevinecdm plugin crashes, the following is found in
syslog:
Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in
libxul.so[7fcdfb77a000+6111000]
Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in
libxul.so[7fe3b34c7000+6111000]
Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400
audit(1529046808.895:250): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16139 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:28 xplt kernel: [301357.859328] audit: type=1400
audit(1529046808.895:251): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:28 xplt kernel: [301357.859349] plugin-containe[16139]: segfault
at 0 ip 7fcf32ae06af sp 7ffeb8a136c8 error 6 in
libxul.so[7fcf307b3000+6111000]
Jun 15 19:13:25 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ERROR block_reap:328:
[hamster] bad exit code 1
Jun 15 19:13:29 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:29 xplt kernel: [301358.227635] audit: type=1400
audit(1529046809.263:252): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16188 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:29 xplt kernel: [301358.227811] audit: type=1400
audit(1529046809.263:253): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s]
[Desktop-packages] [Bug 1904323] [NEW] gnome-terminal resized and moved after resume
Public bug reported: GNOME desktop with Wayland, Dell E5450 notebook using iGPU (Intel). dGPU (nVidia) is present but never used. No proprietary drivers. Both eDP and HDMI are connected to Intel. I usually have several gnome-terminal windows open. After the following - connect TV using HDMI - suspend notebook (close lid) - open lid, notebook resumed all opened gnome-terminal windows are resized (so far always smaller size) and moved on screen to different position. I had similar effects also in 16.04 and 18.04 under X11/Unity (and also in 20.04 before switching to GNOME/Wayland). I am happy to provide any additional/debugging information if anyone explains what is necessary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-28.30~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 16:32:28 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (1963 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2020-10-03 (43 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1904323 Title: gnome-terminal resized and moved after resume Status in gnome-terminal package in Ubuntu: New Bug description: GNOME desktop with Wayland, Dell E5450 notebook using iGPU (Intel). dGPU (nVidia) is present but never used. No proprietary drivers. Both eDP and HDMI are connected to Intel. I usually have several gnome-terminal windows open. After the following - connect TV using HDMI - suspend notebook (close lid) - open lid, notebook resumed all opened gnome-terminal windows are resized (so far always smaller size) and moved on screen to different position. I had similar effects also in 16.04 and 18.04 under X11/Unity (and also in 20.04 before switching to GNOME/Wayland). I am happy to provide any additional/debugging information if anyone explains what is necessary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-28.30~20.04.1-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 15 16:32:28 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-07-02 (1963 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2020-10-03 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1904323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
I also meant to say that after logging in into this black screen you can "prime select nvidia" and reboot again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Bionic: Triaged Status in nvidia-prime source package in Eoan: Won't Fix Status in ubuntu-drivers-common source package in Eoan: Won't Fix Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
I'm facing the same problem with Ubuntu 20.04.1 LTS and GeForce 310M, using an old Samsung QX310. Without these drivers, the preinstalled intel driver works fine. But with "prime-select intel" I boot into a black screen. To go back into the DE, first I have to press Ctrl+Alt+F4 and then input my login and password. Sometimes it takes a few tries. I hope this helps others, so that booting into recovery mode is not needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Bionic: Triaged Status in nvidia-prime source package in Eoan: Won't Fix Status in ubuntu-drivers-common source package in Eoan: Won't Fix Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 34813] Re: gedit fails to save files over smbfs/cifs
This bug also affects me. For another bug, I created instructions on how to reproduce my samba setup via docker: https://gitlab.gnome.org/GNOME/gedit/-/issues/322#steps-to-reproduce This might help reproducing this bug. ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #322 https://gitlab.gnome.org/GNOME/gedit/-/issues/322 -- 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/34813 Title: gedit fails to save files over smbfs/cifs Status in gedit: Expired Status in Samba Server: Invalid Status in SSHFS Mounter: Confirmed Status in gedit package in Ubuntu: Triaged Status in gedit package in CentOS: New Bug description: Saving files over a cifs/smbfs server doesnt work. You can open file, edit then save perfectly. But repeated saves after give you this error: "The file /home/dhonn/website/arrays.php has been modified since reading it. If you save it, all the external changes could be lost. Save it anyway?" The think is lying to me because I havent made any external changes. When I click "Save Anyway", i get this error: "Could not save the file /home/dhonn/website/arrays.php." But on the third try it works just fine. Here are the error messages, btw there are also GUI glitches too: http://dhonn.com/images/gedit-0.jpg http://dhonn.com/images/gedit-1.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/34813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [apparmor] [Bug 1777070] Re: firefox plugin libwidevinecdm.so crashes due to apparmor denial
On 10/25/20 5:15 AM, baptx wrote:
> I got it working by adding the 2 lines at the end of the
> /etc/apparmor.d/usr.bin.firefox just before the closing brack "}".
> Without these lines, I had to use another workaround by disabling
> Apparmor completely on Firefox with a command like "sudo aa-complain
> /usr/lib/firefox/firefox" or using the official Firefox binary from
> Mozilla instead of the Ubuntu package.
>
> I saw Daniel wrote "this is not a great way of working (malware could
> write to that location and then load in code)" but do you have an idea
> how to make it more secure?
>
I assume by the 2 lines you mean
ptrace (trace) peer=@{profile_name},
@{HOME}/.mozilla/firefox/*/gmp-widevinecdm/*/lib*so m,
from the bug report. Neither of these lines would allow malware to
write to that location. However they do provide some danger.
The first rule allow firefox to ptrace it self, this could potentially
be exploited by injected shell code to further take control of firefox
if say the code gains control of the render process. It won't however
allow removing confinement or attacking other processes the user might
be running.
The second rule allows firefox to load and run code from that location.
But doesn't allow firefox to write to it. So if there is malware on the
system that can write to that location it could have firefox run it.
But if something manages to hack/inject code into firefox it won't be
able to put code there. Dealing with this in apparmor comes down to
making sure the rest of the system confinement is correct, preventing
said malware from writing to that location. Or you could potentially
use IMA to further restrict and only allow signed files from this
location.
The reason this is more dangerous than allowing /lib/*.so or other
system locations is the users home directory can be written by other
processes run by the user. And on most systems, most user processes
are running unconfined hence malware that exists on the system and
isn't confined could write to it.
Again this isn't some much a problem with having the rule in the
apparmor profile but have sufficient policy on the system.
> When will the fix be added officially to the Firefox Apparmor profile?
>
these can be added fairly soon.
https://gitlab.com/apparmor/apparmor/-/merge_requests/684
though that is just landing it upstream and I am not sure when the
next ubuntu upload will be
--
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/1777070
Title:
firefox plugin libwidevinecdm.so crashes due to apparmor denial
Status in apparmor package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Ubuntu 18.04, Firefox 60.0.1+build2-0ubuntu0.18.04.1
Running firefix, then going to netflix.com and attempting to play a
movie. The widevinecdm plugin crashes, the following is found in
syslog:
Jun 15 19:13:22 xplt kernel: [301351.553043] audit: type=1400
audit(1529046802.585:246): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16118 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:22 xplt kernel: [301351.553236] audit: type=1400
audit(1529046802.585:247): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:22 xplt kernel: [301351.553259] plugin-containe[16118]: segfault
at 0 ip 7fcdfdaa76af sp 7ffc1ff03e28 error 6 in
libxul.so[7fcdfb77a000+6111000]
Jun 15 19:13:22 xplt snmpd[2334]: error on subcontainer 'ia_addr' insert (-1)
Jun 15 19:13:22 xplt /usr/lib/gdm3/gdm-x-session[6549]: ###!!!
[Parent][MessageChannel::Call] Error: Channel error: cannot send/recv
Jun 15 19:13:24 xplt kernel: [301353.960182] audit: type=1400
audit(1529046804.994:248): apparmor="DENIED" operation="file_mmap"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/xav/.mozilla/firefox/wiavokxk.default-1510977878171/gmp-widevinecdm/1.4.8.1008/libwidevinecdm.so"
pid=16135 comm="plugin-containe" requested_mask="m" denied_mask="m" fsuid=1000
ouid=1000
Jun 15 19:13:24 xplt kernel: [301353.960373] audit: type=1400
audit(1529046804.994:249): apparmor="DENIED" operation="ptrace"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=24714 comm="firefox"
requested_mask="trace" denied_mask="trace"
peer="/usr/lib/firefox/firefox{,*[^s][^h]}"
Jun 15 19:13:24 xplt kernel: [301353.960398] plugin-containe[16135]: segfault
at 0 ip 7fe3b57f46af sp 7ffe6dc0b488 error 6 in
libxul.so[7fe3b34c7000+6111000]
Jun 15 19:13:28 xplt kernel: [301357.859177] audit: type=1400
audit(1529046808.895:250): apparmor="DENIED" operation="file
[Desktop-packages] [Bug 1012858]
(In reply to Wayne Mery (:wsmwk) from comment #21) > David, thanks for reporting your results. Can you retest please and tell us > if this reproduces with a curent beta? Wayne, as I wrote several times over several years at several places in this bug tracker: The problem is easily reproducible, also on Linux, with any TB version (meanwhile including 78.4.2.). Why is there apparently not a single TB developer trying this himself? Again: just enter an IP address such as 1.2.3.4 as the server name/address. Then try fetching emails. Until this timeouts, the progress bar moves forth and back with significant CPU load (10% of one core on my current Linux machine). -- 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/1012858 Title: "Sending of message failed" dialog needs 100% of one CPU as long as it is open. Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Priority: Low How to reproduce: - Attach a large file to a message to make the sending process need enough time for the third step. - press the "send" button - Interrupt the internet connection before the sending of the message can be completed Problem: The Dialog that pops up now telling the message could not be sent creates 100% CPU load for one CPU. What was to be expected: The dialog pops up and does not need any CPU power until a button is clicked. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: thunderbird 14.0~b1+build2-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 ApportVersion: 2.2.2-0ubuntu2 Architecture: amd64 Date: Wed Jun 13 22:49:39 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/thunderbird/thunderbird-bin LocalLibraries: /home/gunter/.thunderbird/fskw3xe2.default/extensions/mintr...@tn123.ath.cx/lib/tray_x86_64-gcc3.so SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1012858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890898] Re: No permission to access files on storage device
Put it as solved, I couldn't reproduce this bug again. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1890898 Title: No permission to access files on storage device Status in udisks2 package in Ubuntu: Incomplete Bug description: When I pluged in an USB Sandisk Extreme 64 gb, I received an error. After that I format the USB, and next try to save info on it. It works, save the info. Next plugged out the USB and try to plug in again in another USB port. Now I receive another error with USB, impossible to acces or similar error. If I try to press right mouse button when I am looking inside the USB storage, and press create new document (my new document is a txt file in black, saved in templates), when I did it, the system freeze. :S I think that plug and play is not working well. When I was burning a disc and plugged in an USB, the burning failed. My PC: Ryzen 2700X Nvidia GTX 1080 Ti RAM 8 Gb ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.vlc.rules 70-snap.gimp.rules 70-snap.snapd.rules 70-snap.chromium.rules Date: Sat Aug 8 15:46:30 2020 InstallationDate: Installed on 2020-04-24 (105 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS GAMING 7 WIFI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=de8f79b3-6f06-4293-9d8c-ed2a147342a5 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1890898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897307] Re: [X470 AORUS GAMING 7 WIFI, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem
Same again,when I updated my Ubuntu 20.04.1 LTS, sometimes when I switch on my PC, I lose one of my outputs of audio. For example, I switch on the PC and the HDMI DisplayPort2 GP102 Audio Contoller doesn't appear in the settings > Sound. I need to reboot the PC and sometings if you have good luck it appears again, if not, you need to reboot again and again and again. -- 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/1897307 Title: [X470 AORUS GAMING 7 WIFI, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: After last update, I have lost the sound of my Asus Monitor which has got speakers. It is a problem with ALSA Audio because, the last update installed some patch of ALSA. Now, when I use for example VLC and try to change to my HDMI Audio Controller, it works well, but If I do the same thing with a videogame of Steam, like DOTA 2, I can't obtain the sound of the game in my Asus Monitor. I installed Pulse Audio to select the sound card which I want to use, and when I try to change the sound card of the application DOTA 2, it is impossible, I can't. I change it in the menu, but the option comes back to USB Speakers. Please solve it, I have lost my speakers with this update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 17:32:21 2020 InstallationDate: Installed on 2020-04-24 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP102 HDMI Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [X470 AORUS GAMING 7 WIFI, Nvidia GPU 82 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS GAMING 7 WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSGAMING7WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSGAMING7WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS GAMING 7 WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
** Changed in: network-manager (Ubuntu Xenial) Status: Confirmed => Won't Fix ** Changed in: systemd (Ubuntu Xenial) Status: Invalid => Won't Fix -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Expired Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Won't Fix Status in systemd source package in Xenial: Won't Fix Status in network-manager source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888505] Re: Two-finger touchpad zoom extremely sensitive
@Adolfo Why low priority? @Martin, @Iain why "wontfix"? Is it a matter of reporting the bug elsewhere or a matter of touchpads being seen as unnecessary in LO? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1888505 Title: Two-finger touchpad zoom extremely sensitive Status in libreoffice package in Ubuntu: New Bug description: Open Calc -> + Expected behaviour: document viewpan zooms/unzooms at a reasonable speed Observed behaviour: document viewpan zooms/unzooms from maximum zoom in to maximum zoom out in maybe 10-15% of the height of the touchpad, i.e. it is unusably oversensitive. Also affects Draw and Writer, 100% reproducible. Other apps (Firefox, Eye of Gnome/Image viewer) behave as expected (very usable zoom/unzoom sensitivity). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 14:43:20 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2018-05-10 (804 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2020-03-04 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1888505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
