[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Piotr Tomaszewski (nfm886) can confirm my touchpad is the MSFT0001:00 06CB:7F28. I booted kernel 5.10.1 into recovery and then resumed regular boot and my touchpad works. -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
all the changes are extract from the master branch of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git . -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
on fedora 33,with kernel 5.10.2 , i use this patch ,then touchpad work!
diff -Narup a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-acpi.c
--- a/drivers/gpio/gpiolib-acpi.c 2020-12-14 06:41:30.0 +0800
+++ b/drivers/gpio/gpiolib-acpi.c 2020-12-22 14:31:53.078877803 +0800
@@ -205,6 +205,68 @@ static void acpi_gpiochip_request_irqs(s
acpi_gpiochip_request_irq(acpi_gpio, event);
}
+static enum gpiod_flags
+acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio, int polarity)
+{
+ /* GpioInt() implies input configuration */
+ if (agpio->connection_type == ACPI_RESOURCE_GPIO_TYPE_INT)
+ return GPIOD_IN;
+
+ switch (agpio->io_restriction) {
+ case ACPI_IO_RESTRICT_INPUT:
+ return GPIOD_IN;
+ case ACPI_IO_RESTRICT_OUTPUT:
+ /*
+* ACPI GPIO resources don't contain an initial value for the
+* GPIO. Therefore we deduce that value from the pull field
+* and the polarity instead. If the pin is pulled up we assume
+* default to be high, if it is pulled down we assume default
+* to be low, otherwise we leave pin untouched. For active low
+* polarity values will be switched. See also
+* Documentation/firmware-guide/acpi/gpio-properties.rst.
+*/
+ switch (agpio->pin_config) {
+ case ACPI_PIN_CONFIG_PULLUP:
+ return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_LOW :
GPIOD_OUT_HIGH;
+ case ACPI_PIN_CONFIG_PULLDOWN:
+ return polarity == GPIO_ACTIVE_LOW ? GPIOD_OUT_HIGH :
GPIOD_OUT_LOW;
+ default:
+ break;
+ }
+ break;
+ default:
+ break;
+ }
+
+ /*
+* Assume that the BIOS has configured the direction and pull
+* accordingly.
+*/
+ return GPIOD_ASIS;
+}
+
+static struct gpio_desc *acpi_request_own_gpiod(struct gpio_chip *chip,
+ struct acpi_resource_gpio
*agpio,
+ unsigned int index,
+ const char *label)
+{
+ int polarity = GPIO_ACTIVE_HIGH;
+ enum gpiod_flags flags = acpi_gpio_to_gpiod_flags(agpio, polarity);
+ unsigned int pin = agpio->pin_table[index];
+ struct gpio_desc *desc;
+ int ret;
+
+ desc = gpiochip_request_own_desc(chip, pin, label, polarity, flags);
+ if (IS_ERR(desc))
+ return desc;
+
+ ret = gpio_set_debounce_timeout(desc, agpio->debounce_timeout);
+ if (ret)
+ gpiochip_free_own_desc(desc);
+
+ return ret ? ERR_PTR(ret) : desc;
+}
+
static bool acpi_gpio_in_ignore_list(const char *controller_in, int pin_in)
{
const char *controller, *pin_str;
@@ -290,8 +352,8 @@ static acpi_status acpi_gpiochip_alloc_e
if (!handler)
return AE_OK;
- desc = gpiochip_request_own_desc(chip, pin, "ACPI:Event",
-GPIO_ACTIVE_HIGH, GPIOD_IN);
+ desc = acpi_request_own_gpiod(chip, agpio, 0, "ACPI:Event");
+
if (IS_ERR(desc)) {
dev_err(chip->parent,
"Failed to request GPIO for pin 0x%04X, err %ld\n",
@@ -526,39 +588,6 @@ static bool acpi_get_driver_gpio_data(st
return false;
}
-static enum gpiod_flags
-acpi_gpio_to_gpiod_flags(const struct acpi_resource_gpio *agpio)
-{
- switch (agpio->io_restriction) {
- case ACPI_IO_RESTRICT_INPUT:
- return GPIOD_IN;
- case ACPI_IO_RESTRICT_OUTPUT:
- /*
-* ACPI GPIO resources don't contain an initial value for the
-* GPIO. Therefore we deduce that value from the pull field
-* instead. If the pin is pulled up we assume default to be
-* high, if it is pulled down we assume default to be low,
-* otherwise we leave pin untouched.
-*/
- switch (agpio->pin_config) {
- case ACPI_PIN_CONFIG_PULLUP:
- return GPIOD_OUT_HIGH;
- case ACPI_PIN_CONFIG_PULLDOWN:
- return GPIOD_OUT_LOW;
- default:
- break;
- }
- default:
- break;
- }
-
- /*
-* Assume that the BIOS has configured the direction and pull
-* accordingly.
-*/
- return GPIOD_ASIS;
-}
-
static int
__acpi_gpio_update_gpiod_flags(enum gpiod_flags *flags, enum gpiod_flags
update)
{
@@ -664,6 +693,7 @@ static int acpi_populate_gpio_lookup(str
lookup->desc = acpi_get_gpiod(agpio->resource_source.string_ptr,
agpio->pin_table[pin_index]);
[Desktop-packages] [Bug 1311195] Re: [touchscreen] Cannot move window by dragging title bar with default gtk decoration
** Tags added: oem-priority originate-from-1907248 somerville -- 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/1311195 Title: [touchscreen] Cannot move window by dragging title bar with default gtk decoration Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Bug description: With the default GTK decoration, it is not possible to drag the title bar of Chromium to move the window. When the setting is changed to "system" it works fine as any other window. Expected: By default chromium should be configured with system decorations. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 22 17:58:18 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 455G 4,0G 427G 1% /\nnone tmpfs 4,0K 0 4,0K 0% /sys/fs/cgroup\nudev devtmpfs 1,9G 4,0K 1,9G 1% /dev\ntmpfs tmpfs 384M 1,1M 383M 1% /run\nnone tmpfs 5,0M 0 5,0M 0% /run/lock\nnone tmpfs 1,9G 8,0M 1,9G 1% /run/shm\nnone tmpfs 100M 44K 100M 1% /run/user\n/dev/sda1 vfat 511M 3,4M 508M 1% /boot/efi\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 29M 187K 29M1% /\nnone 480K 2 480K1% /sys/fs/cgroup\nudev 477K 502 477K1% /dev\ntmpfs 480K 490 479K1% /run\nnone 480K 3 480K1% /run/lock\nnone 480K12 480K1% /run/shm\nnone 480K27 480K1% /run/user\n/dev/sda1 0 0 0 - /boot/efi\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2014-04-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1311195/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901061] Re: I'm using Ubuntu 20.04, and my super key doesn't work for any shortcuts or presses.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1901061 Title: I'm using Ubuntu 20.04, and my super key doesn't work for any shortcuts or presses. Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I've tried to rebind the key, but it doesn't work. I've tested the keyboard on other PC's, and the super key works just fine, so I'm unsure what to do. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 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.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 18:42:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-19 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-10-19T21:25:12.624476 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900992] Re: twitch erreur 4000
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1900992 Title: twitch erreur 4000 Status in firefox package in Ubuntu: Expired Bug description: -dans mon firefox 81.0.2 (en .deb) les stream sur twitch soulève l'erreure 4000. sur ce même ordi le firefox(82.0) en snap n'a pas ce problème. Es que c'est un problème de codec? -In my firefox 81.0.2 (in .deb) twitch streams raise the error 4000. On the same computer the firefox (82.0) in snap doesn't have this problem. Is it a codec problem? thanks ;) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 81.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yael 1188 F pulseaudio BuildID: 20201012085804 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 11:49:36 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-07-30 (83 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=81.0.2/20201012085804 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1900992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901061] Re: I'm using Ubuntu 20.04, and my super key doesn't work for any shortcuts or presses.
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1901061 Title: I'm using Ubuntu 20.04, and my super key doesn't work for any shortcuts or presses. Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I've tried to rebind the key, but it doesn't work. I've tested the keyboard on other PC's, and the super key works just fine, so I'm unsure what to do. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 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.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 22 18:42:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-19 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2020-10-19T21:25:12.624476 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1901061/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Verify on Dell CID 202010-28345 1. boot into Ubuntu groovy 2. check sound settings 3. Input Device is empty 4. plug the headset 5. Input Device is still empty 6. enable proposed channel 7. $ sudo apt install pulseaudio 8. $ apt policy pulseaudio pulseaudio: Installed: 1:13.99.2-1ubuntu2.2 Candidate: 1:13.99.2-1ubuntu2.2 Version table: *** 1:13.99.2-1ubuntu2.2 500 500 http://tw.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.2-1ubuntu2.1 500 500 http://tw.archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu groovy-security/main amd64 Packages 1:13.99.2-1ubuntu1 500 500 http://tw.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 9. $ sudo reboot 10. after boot into Ubuntu groovy 11. open sound settings 12. plug headset 13. can see "Headset Microphone - Built-in-Audio" in "Input Device" field. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908971] [NEW] TypeError: cannot use a string pattern on a bytes-like object
Public bug reported: user@host:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table: *** 0.8.11.1612-1 500 500 http://nz.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status user@host:~$ http_proxy= AWS_ACCESS_KEY_ID=[omitted-key-id] AWS_SECRET_ACCESS_KEY=[omitted-key] PASSPHRASE=[omitted-encryption-password] duplicity --s3-use-new-style --s3-use-ia --s3-use-multiprocessing --no-print-statistics --verbosity 1 --exclude-device-files --exclude-filelist [omitted-exclude-path] --include-filelist [omitted-include-path] --exclude '**' / [omitted-s3-storage-path] TypeError: cannot use a string pattern on a bytes-like object During handling of the above exception, another exception occurred: Traceback (most recent call last): ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Dec 22 16:37:45 2020 InstallationDate: Installed on 2020-11-19 (33 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1908971 Title: TypeError: cannot use a string pattern on a bytes-like object Status in duplicity package in Ubuntu: New Bug description: user@host:~$ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 user@host:~$ apt-cache policy duplicity duplicity: Installed: 0.8.11.1612-1 Candidate: 0.8.11.1612-1 Version table: *** 0.8.11.1612-1 500 500 http://nz.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status user@host:~$ http_proxy= AWS_ACCESS_KEY_ID=[omitted-key-id] AWS_SECRET_ACCESS_KEY=[omitted-key] PASSPHRASE=[omitted-encryption-password] duplicity --s3-use-new-style --s3-use-ia --s3-use-multiprocessing --no-print-statistics --verbosity 1 --exclude-device-files --exclude-filelist [omitted-exclude-path] --include-filelist [omitted-include-path] --exclude '**' / [omitted-s3-storage-path] TypeError: cannot use a string pattern on a bytes-like object During handling of the above exception, another exception occurred: Traceback (most recent call last): ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: duplicity 0.8.11.1612-1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Dec 22 16:37:45 2020 InstallationDate: Installed on 2020-11-19 (33 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1908971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Verify on Dell CID 202010-28345 1. boot into Ubuntu focal 2. check sound settings 3. Input Device is empty 4. plug the headset 5. Input Device is still empty 6. enable proposed channel 7. $ sudo apt install pulseaudio 8. $ apt policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.9 Candidate: 1:13.99.1-1ubuntu3.9 Version table: *** 1:13.99.1-1ubuntu3.9 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 9. $ sudo reboot 10. after boot into Ubuntu focal 11. open sound settings 12. plug headset 13. can see "Headset Microphone - Built-in-Audio" in "Input Device" field. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Tags added: originate-from-1901838 -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] On those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908960] [NEW] package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1
Public bug reported: don't have much info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs-gtk 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_73 zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: libwebkit2gtk-4.0-37:amd64: Install libjavascriptcoregtk-4.0-18:amd64: Install gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 22 07:01:24 2020 ErrorMessage: installed emacs-gtk package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: emacs Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1908960 Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 Status in emacs package in Ubuntu: New Bug description: don't have much info ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs-gtk 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_73 zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: libwebkit2gtk-4.0-37:amd64: Install libjavascriptcoregtk-4.0-18:amd64: Install gir1.2-webkit2-4.0:amd64: Install gir1.2-javascriptcoregtk-4.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Dec 22 07:01:24 2020 ErrorMessage: installed emacs-gtk package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: emacs Title: package emacs-gtk 1:26.3+1-1ubuntu2 failed to install/upgrade: installed emacs-gtk package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1908960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
Hello, what additional info can I provide to help diagnose the issue? I get these segfaults sometimes right after boot. Not sure if anything is broken though since the system works fine (aside from other segfaults/crashes). ``` aes@pop-os:~$ sudo grep segfault /var/log/kern.log | grep nautilus [sudo] password for aes: Dec 21 19:33:44 pop-os kernel: [ 23.054275] nautilus[3601]: segfault at 20 ip 7fa6d519f844 sp 7ffce8181e68 error 4 in libgio-2.0.so.0.6600.1[7fa6d50ee000+119000] Dec 21 21:10:37 pop-os kernel: [ 20.034278] nautilus[2479]: segfault at 20 ip 7f460b754844 sp 7ffd1c7d5de8 error 4 in libgio-2.0.so.0.6600.1[7f460b6a3000+119000] Dec 21 21:16:06 pop-os kernel: [ 18.599962] nautilus[2332]: segfault at 20 ip 7fa6e5036844 sp 7ffcdb30fe68 error 4 in libgio-2.0.so.0.6600.1[7fa6e4f85000+119000] ``` I also tried `nautilus --version` and it does reproduce the issue reliably. ``` aes@pop-os:~$ uname -a Linux pop-os 5.8.0-7630-generic #32~1606339263~20.10~61c3910-Ubuntu SMP Thu Nov 26 00:10:35 UTC x86_64 x86_64 x86_64 GNU/Linux aes@pop-os:~$ apt search ^nautilus$ Sorting... Done Full Text Search... Done nautilus/groovy,now 1:3.38.1-1ubuntu1 amd64 [installed,automatic] file manager and graphical shell for GNOME ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908699] Autopkgtest regression report (mesa/20.2.6-0ubuntu0.20.10.1)
All autopkgtests for the newly accepted mesa (20.2.6-0ubuntu0.20.10.1) for groovy have finished running. The following regressions have been reported in tests triggered by the package: euslisp/9.27+dfsg-6 (amd64, armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908699 Title: New bugfix release 20.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Groovy: Fix Committed Bug description: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Could you try to boot in recovery mode and then resume the normal boot process? I think i have the MSFT0001:00 06CB:7F28 touchpad installed but i'll check these days. -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Desktop-packages] [Bug 1232872]
Hi all, I can't verify this, since I don't have access to a NAS anymore, but I expect nothing has changed in the last two year. Perhaps someone else can verify? -- 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/1232872 Title: [upstream] NFS / lock problem with LibreOffice wth 13.04 Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Hi all, I have a problem very similar to what is exposed in question #234375. Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing documents via NFS with LibreOffice. The slash screen display for about 30s, then there is a popup warning saying that another user has opened the file, and offering to open a copy, open as readonly or cancel. The point is, no other user has opened that file (being the only user on my personal PC, but storing my documents on NAS). So I tried the suggestion about adding "noauto" in /etc/fstab and changing /etc/rc.local, with no luck. But the modification of /usr/lib/libreoffice/program/soffice: ## # STAR_PROFILE_LOCKING_DISABLED=1 export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ... #export SAL_ENABLE_FILE_LOCKING ### (That is, uncomment the first 2 lines, and commenting the other 2) This works OK. If this is the official way of fixing things, then I guess LibreOffice deserves an update on Ubuntu at least. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
Same as above... -- 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/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- 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/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@Robin Windey (r0wi), unfortunately it does not works with my touchpad. Tried kernel you linked on PopOS 20.10 and Ubuntu 20.04.1. Both results are same, touchpad not works. What is yours touchpad? -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Ubuntu 20.10 I installed with kernel 5.10.1 with your instructions @Robin Windey (r0wi) and neither works touchpad -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo
[Desktop-packages] [Bug 1805025] Re: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing
** Changed in: gnome-control-center Status: Fix Released => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1805025 Title: gnome-control-center power - 'Turn off Wi-Fi to save power' label is confusing Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The 'Turn off Wi-Fi to save power' setting defaults to ON. Toggling 'Turn off Wi-Fi to save power' to OFF causes the wifi device to be soft blocked. BEFORE$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no AFTER$ sudo rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: yes Hard blocked: no $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.2 Candidate: 1:3.28.2-0ubuntu0.18.04.2 Version table: *** 1:3.28.2-0ubuntu0.18.04.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: Power saving for wifi will be disabled. Actual behavior: Wifi is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1805025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908930] [NEW] libwebkit2gtk-4.0-37missing files brake epiphany
Public bug reported: libwebkit2gtk-4.0-37 version 2.30.3-0ubuntu0.18.04.1 comes without WebKitPluginProcess (should be under /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0). Similarly /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/WebKitStorageProcess is missing. If I try to follow a link to a pdf file in epiphany (epiphany-browser 3.28.1-1ubuntu1) it crashes. ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1908930 Title: libwebkit2gtk-4.0-37missing files brake epiphany Status in webkit2gtk package in Ubuntu: New Bug description: libwebkit2gtk-4.0-37 version 2.30.3-0ubuntu0.18.04.1 comes without WebKitPluginProcess (should be under /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0). Similarly /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/WebKitStorageProcess is missing. If I try to follow a link to a pdf file in epiphany (epiphany-browser 3.28.1-1ubuntu1) it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1908930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Thunderbird 78.6 is a must Regardless of LTS or not https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird78.6 -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
** Description changed: - I have `hp-systray -x` as one of the startup applications when I login. + I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. - Once logged in, if I start ``hp-systray -x` from the terminal it works + Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803604] Re: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work
It works under Ubuntu Linux 20.04 as well. Unfortunately only if you "disable" the apparmor rules for senddoc or set it to "complain" mode. In this mode the rules are not blocked, but they are logged. I have not yet figured out how to functionally adjust the rule so that it also works in "enforce" mode. Maybe someone knows better about this. The rule can be put into complain mode with the following command (at your own risk). aa-complain usr.lib.libreoffice.program.senddoc -- 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/1803604 Title: [upstream] "Send -> Document as e-mail" in Writer / Calc does not work Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.3 Sylvia Release: 18.3 LO: Version: 6.1.3.2 Build-ID: 1:6.1.3~rc2-0ubuntu0.16.04.1 In writer I have an open document. If I then want to send it: "File - send - document as e-mail" **Nothing happens** Same with send e-mail as open-document and word document. Only send with pdf opens at least the pdf dialogue. But then nothing happens. Path to thunderbird: /usr/bin/thunderbird Thunderbird opens if I use this path so the path seems correct. No error message received. Expect: Mail is opened and document attached. (which worked before) Update: Just checked in Ubuntu 18.04 and LO 6.06.2 There it works as expected. Will check my other system again. Maybe it just does not work on my other system. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1803604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] [NEW] No system tray detected by hp-systray
Public bug reported: I have `hp-systray -x` as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start ``hp-systray -x` from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: I have `hp-systray -x` as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start ``hp-systray -x` from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
*** This bug is a duplicate of bug 1715435 *** https://bugs.launchpad.net/bugs/1715435 I have this issue too. I'm using Dell latitude 5501, Xubuntu 20 and Xfce. It's very painful. Is anybody have found the solution? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908903] Re: Replace pulseaudio with pipewire
Fedora done this too https://fedoraproject.org/wiki/Changes/DefaultPipeWire -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1908903 Title: Replace pulseaudio with pipewire Status in ubuntu-meta package in Ubuntu: New Bug description: Pipewire is clearly better at supporting bluetooth codecs and have drop-in support for pulseaudio https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1908903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908903] [NEW] Replace pulseaudio with pipewire
Public bug reported: Pipewire is clearly better at supporting bluetooth codecs and have drop-in support for pulseaudio https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1908903 Title: Replace pulseaudio with pipewire Status in ubuntu-meta package in Ubuntu: New Bug description: Pipewire is clearly better at supporting bluetooth codecs and have drop-in support for pulseaudio https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1908903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
Thanks for your work so far. Please settle on TB 78.5.1 [1] (and not just 78.5.0) because it's got a highly requested "feature": "OpenPGP: Added option to disable email subject encryption" It would be better, of course, to aim for the latest version "78.6.0" but that's just a nitpick ;) Thanks & keep up your good work! xiconfjs [1] https://www.thunderbird.net/en-US/thunderbird/78.5.1/releasenotes/ -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Triaged Status in thunderbird source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
** Description changed: - The WiFi connection is aborted an the nm_applet shows the window to - enter the WLAN password. The password is pre-filled an you can click the - ok button to reconnect. + The WiFi connection is aborted and the nm_applet shows the window to + enter the WLAN password. The password is pre-filled and you can click + the ok button to reconnect. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). The problem occurs in Xubuntu 20.04.1 LTS since update to kernel 5.4.0-56 (5.4.0-58 too). With other Xubuntu versions (e.g. 18.04 LTS) or kernel 5.4.0-54 or earlier the problem did not appear. Other OS (eg W10 or div Android) do not see this problem too. Additional asked information: 1) lsb_release -rd - Description:Ubuntu 20.04.1 LTS - Release:20.04 + Description:Ubuntu 20.04.1 LTS + Release:20.04 2) apt-cache policy network-manager network-manager: - Installiert: 1.22.10-1ubuntu2.2 - Installationskandidat: 1.22.10-1ubuntu2.2 - Versionstabelle: - *** 1.22.10-1ubuntu2.2 500 - 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 1.22.10-1ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 3) What you expected to happen: WLAN witch in the background with no net abort. + Installiert: 1.22.10-1ubuntu2.2 + Installationskandidat: 1.22.10-1ubuntu2.2 + Versionstabelle: + *** 1.22.10-1ubuntu2.2 500 + 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 1.22.10-1ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 3) What you expected to happen: WLAN switch in the background with no net abort. 4) What happened instead: Network abort, window-popup with focus to password, interrupted work. All hardware that I know show the problem on laptops with Intel WLAN devices. - In /var/log/syslog you can find the error beginning with a "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available" entry. Some lines later you see the entry "asking for a new key". - The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour ca be seen in the 2,4GHz and in the 5GHz net. + In /var/log/syslog you can find the error beginning with a - In the sent .apport file you see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 29 14:18" as the repeater is forced to reboot to produce the error. + "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space + available" + + entry. Some lines later you see the entry "asking for a new key". + The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour can be seen in the 2,4GHz and in the 5GHz net. + + In the sent .apport file you'll see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 20 14:18" as the repeater is forced to reboot to reproduce the error. For further information you can see the discussion at https://answers.launchpad.net/ubuntu/+question/694566 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Dec 20 14:19:27 2020 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2019-12-28 (357 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: - default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown - 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown - 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown + default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown + 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown + 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown ProcEnviron: - LANGUAGE=de_DE - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + LANGUAGE=de_DE + PATH=(custom, user) + XDG_RUNTIME_DIR= +
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Robin Windey (r0wi), I tried to do this via ur instructions and via Mainline utility, but my touchpad isn't working... -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo
[Desktop-packages] [Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
With me the problem always occurs when in a running connection the channel is changed. This may happen in a busy neighborhood, if in the Router (FritzBox 7530) the automatic channel selection (recommended) is selected. It certainly may happen too if a Repeater is in use. If I switch of and on manually the WIFI, this procedure is treated as a new connection, and the installed password is found automatically with no request, quite as it aught to be. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled Status in network-manager-applet package in Ubuntu: Confirmed Bug description: The WiFi connection is aborted an the nm_applet shows the window to enter the WLAN password. The password is pre-filled an you can click the ok button to reconnect. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). The problem occurs in Xubuntu 20.04.1 LTS since update to kernel 5.4.0-56 (5.4.0-58 too). With other Xubuntu versions (e.g. 18.04 LTS) or kernel 5.4.0-54 or earlier the problem did not appear. Other OS (eg W10 or div Android) do not see this problem too. Additional asked information: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy network-manager network-manager: Installiert: 1.22.10-1ubuntu2.2 Installationskandidat: 1.22.10-1ubuntu2.2 Versionstabelle: *** 1.22.10-1ubuntu2.2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen: WLAN witch in the background with no net abort. 4) What happened instead: Network abort, window-popup with focus to password, interrupted work. All hardware that I know show the problem on laptops with Intel WLAN devices. In /var/log/syslog you can find the error beginning with a "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available" entry. Some lines later you see the entry "asking for a new key". The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour ca be seen in the 2,4GHz and in the 5GHz net. In the sent .apport file you see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 29 14:18" as the repeater is forced to reboot to produce the error. For further information you can see the discussion at https://answers.launchpad.net/ubuntu/+question/694566 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Dec 20 14:19:27 2020 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-28 (357 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to focal on 2020-10-28 (52 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connecting started none enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908373] Re: [Seal MT][Caribou]20.04 X59, Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Committed -- 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/1908373 Title: [Seal MT][Caribou]20.04 X59,Black screen appears when installing Ubuntu on AMD 540 graphics card and CML CPU Status in gnome-shell package in Ubuntu: Fix Committed Bug description: [Reproduce Steps] 1. Connect the system via 540 graphics card +CML CUP. 2. Clean install Ubuntu 20.04 2. A black screen appears on the system. [Result] Expected Result OS can be installed normally. [Actual Result] Clean install Ubuntu 20.04. After "Copying installation logs", the system reboots and the screen goes black. The Ubuntu system does not install successfully. The reproduce steps : Insert the U disk -> power on SUT -> error log will appear -> select the hard disk to install OS -> processing of copy files -> auto restart -> Dell logo show up -> error log appears again -> VP on CML +X59 (black screen) / VNP on RKL +X59. Others info: VNP on RKL+UMA VNP on CML+singel 550 VNP on CML +single RX640 VNP on RKL +single 540 VP on CML+UMA VP on CML+singel 540 [Additional Information] 1. Test Vault ID: adhoc 2. Checkbox test case ID : NA 3. BIOS Version: 0.5.28 4. Image/Manifest: Ubuntu 20.04.1 LTS (fossa-cubone x59) 5. SKU: OptiPlex 5090 6. CPU: CML ES QSRK 7. GPU: singel 540 8. PIMS-27206 / Launchpad:#1906140 Failure rate: 3/3 times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
very irritating bug, relates to bluetooth keyboards too. -- 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/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 Released Status in mutter source package in Focal: In Progress Status in mutter source package in Groovy: In Progress 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 1908878] Re: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Video of the issue ** Attachment added: "VID_20201221_105813.mp4" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908878/+attachment/5445467/+files/VID_20201221_105813.mp4 -- 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/1908878 Title: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in gnome-shell package in Ubuntu: New Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908889] [NEW] "Failed to install file: not supported" error
Public bug reported: On a brand new installation of Ubuntu 20.04 LTS, trying to install a .deb (say, from discord.com) gives a "Failed to install file: not supported" error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 10:59:49 2020 InstallationDate: Installed on 2020-12-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1908889 Title: "Failed to install file: not supported" error Status in gnome-software package in Ubuntu: New Bug description: On a brand new installation of Ubuntu 20.04 LTS, trying to install a .deb (say, from discord.com) gives a "Failed to install file: not supported" error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-software (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 10:59:49 2020 InstallationDate: Installed on 2020-12-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1908889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@Robin Windey (r0wi), I will try it. Thanks for the info -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ---
[Desktop-packages] [Bug 1908699] Autopkgtest regression report (mesa/20.2.6-0ubuntu0.20.04.1)
All autopkgtests for the newly accepted mesa (20.2.6-0ubuntu0.20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: wlroots/0.10.0-2 (ppc64el, armhf, amd64, arm64, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1908699 Title: New bugfix release 20.2.6 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Groovy: Fix Committed Bug description: [Impact] This is the last point-release of the 20.2.x-series, we should put it in groovy so latest bugfixes would get there, and for focal because that would minimize the risk of regressions when going from 20.0.x to 20.2.x. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1908699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902244] Autopkgtest regression report (mesa/20.2.6-0ubuntu0.20.04.1)
All autopkgtests for the newly accepted mesa (20.2.6-0ubuntu0.20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: wlroots/0.10.0-2 (ppc64el, armhf, amd64, arm64, s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#mesa [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908878] [NEW] gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?)
Public bug reported: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Summary changed: - gnome shell freezes for a couple of a seconds, then it restarts (maybe it crashes?) + gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) -- 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/1908878 Title: gnome shell freezes for a couple of seconds, then it restarts (maybe it crashes?) Status in gnome-shell package in Ubuntu: New Bug description: This is the line I always see in the log after the restart: Dec 21 09:33:55 ricsipontaz-home gsd-media-keys[5953]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shel l” on object at path /org/gnome/Shell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 09:56:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-04 (17 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201203) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902244] Autopkgtest regression report (xorg-server/2:1.20.9-2ubuntu1.1~20.04.1)
All autopkgtests for the newly accepted xorg-server (2:1.20.9-2ubuntu1.1~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: kplotting/5.68.0-0ubuntu1 (armhf) kwidgetsaddons/5.68.0-0ubuntu1 (armhf) bambam/1.0.1+dfsg-1 (armhf) xmobar/0.29.4-2build3 (ppc64el) ubuntu-release-upgrader/1:20.04.29 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libglvnd package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in libglvnd source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm libglvnd: mostly just EGL headers sync from Khronos, needed by mesa mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@Piotr Tomaszewski (nfm886) i just installed headers (all), image (generic) and modules (generic) from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.10.1/amd64/ via 'dpkg -i *.deb', rebooted with new kernel 5.10.1 and everything worked. So no special config or parameter tweaking was necessary for me. -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1785262] Re: arm64 autopkgtests are flaky
This bug was fixed in the package libreoffice - 1:7.0.4~rc2-0ubuntu2 --- libreoffice (1:7.0.4~rc2-0ubuntu2) hirsute; urgency=medium * Revert "Re-enable coinmp (LP: #1905422)" until MIR is sorted out -- Rico Tzschichholz Mon, 14 Dec 2020 10:05:19 +0100 ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- 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/1785262 Title: arm64 autopkgtests are flaky Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: See http://autopkgtest.ubuntu.com/packages/libreoffice/cosmic/arm64. In the past 30 days, 8 out of 45 test runs failed. That a 18% failure rate. It would be good to understand if all those failures are similar, what's causing them, and if they can easily be made more robust. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1785262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@Robin Windey (r0wi), Hey, did you did something more like adding kernel parameters or something, or just upgrade kernel is enough? -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Desktop-packages] [Bug 1905422] Re: CoinMP Solver not Available, option requires coinmp to be promoted
This bug was fixed in the package libreoffice - 1:7.0.4~rc2-0ubuntu2 --- libreoffice (1:7.0.4~rc2-0ubuntu2) hirsute; urgency=medium * Revert "Re-enable coinmp (LP: #1905422)" until MIR is sorted out -- Rico Tzschichholz Mon, 14 Dec 2020 10:05:19 +0100 ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- 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/1905422 Title: CoinMP Solver not Available, option requires coinmp to be promoted Status in libreoffice package in Ubuntu: Fix Released Bug description: Hi! LibreOffice Calc supports the CoinMP Linear Solver, which is an excellent solver to be used in spreadsheets and makes LO Calc superior to other office suites in that regard. However, the build provided by this PPA does not come with CoinMP Solver enabled (see Tools > Solver > Options). I posted a question at Ask LibreOffice and I was informed that CoinMP is enabled by default during build and maybe the PPA maintainers chose to disable it. https://ask.libreoffice.org/en/question/240836/coinmp-solver-on- libreoffice-calc/ In fact, I built LibreOffice from source and CoinMP was there. However, building from source is not convenient and I'd like to use the PPA. Is it possible that CoinMP Solver be included in future builds of LibreOffice provided by this PPA? I am currently using LibreOffice 7.0.3.1 on Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1905422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled Status in network-manager-applet package in Ubuntu: Confirmed Bug description: The WiFi connection is aborted an the nm_applet shows the window to enter the WLAN password. The password is pre-filled an you can click the ok button to reconnect. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). The problem occurs in Xubuntu 20.04.1 LTS since update to kernel 5.4.0-56 (5.4.0-58 too). With other Xubuntu versions (e.g. 18.04 LTS) or kernel 5.4.0-54 or earlier the problem did not appear. Other OS (eg W10 or div Android) do not see this problem too. Additional asked information: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy network-manager network-manager: Installiert: 1.22.10-1ubuntu2.2 Installationskandidat: 1.22.10-1ubuntu2.2 Versionstabelle: *** 1.22.10-1ubuntu2.2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen: WLAN witch in the background with no net abort. 4) What happened instead: Network abort, window-popup with focus to password, interrupted work. All hardware that I know show the problem on laptops with Intel WLAN devices. In /var/log/syslog you can find the error beginning with a "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available" entry. Some lines later you see the entry "asking for a new key". The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour ca be seen in the 2,4GHz and in the 5GHz net. In the sent .apport file you see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 29 14:18" as the repeater is forced to reboot to produce the error. For further information you can see the discussion at https://answers.launchpad.net/ubuntu/+question/694566 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Dec 20 14:19:27 2020 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-28 (357 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to focal on 2020-10-28 (52 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connecting started none enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
This BUG is intensively discussed in german forum: https://forum.ubuntuusers.de/topic/funknetz-schluessel-werden-staendig- abgefragt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled Status in network-manager-applet package in Ubuntu: Confirmed Bug description: The WiFi connection is aborted an the nm_applet shows the window to enter the WLAN password. The password is pre-filled an you can click the ok button to reconnect. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). The problem occurs in Xubuntu 20.04.1 LTS since update to kernel 5.4.0-56 (5.4.0-58 too). With other Xubuntu versions (e.g. 18.04 LTS) or kernel 5.4.0-54 or earlier the problem did not appear. Other OS (eg W10 or div Android) do not see this problem too. Additional asked information: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy network-manager network-manager: Installiert: 1.22.10-1ubuntu2.2 Installationskandidat: 1.22.10-1ubuntu2.2 Versionstabelle: *** 1.22.10-1ubuntu2.2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen: WLAN witch in the background with no net abort. 4) What happened instead: Network abort, window-popup with focus to password, interrupted work. All hardware that I know show the problem on laptops with Intel WLAN devices. In /var/log/syslog you can find the error beginning with a "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available" entry. Some lines later you see the entry "asking for a new key". The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour ca be seen in the 2,4GHz and in the 5GHz net. In the sent .apport file you see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 29 14:18" as the repeater is forced to reboot to produce the error. For further information you can see the discussion at https://answers.launchpad.net/ubuntu/+question/694566 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Dec 20 14:19:27 2020 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-28 (357 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to focal on 2020-10-28 (52 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connecting started none enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908822] Re: RGB of scanned image is incorrect, same scanner in 18.04 was ok
Does this issue exists also with "xsane" application. Please open terminal, run application with command "simple-scan -d", scan single page, save output from terminal to file and attach such file to this ticket. ** Changed in: simple-scan (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1908822 Title: RGB of scanned image is incorrect, same scanner in 18.04 was ok Status in simple-scan package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu from 18.04 to 20.04, my hp scanjet 2400 has stopped working for photo, but still works for BW documents. I had to use windows 10 for getting the right scanned image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 20 14:28:30 2020 InstallationDate: Installed on 2019-11-08 (407 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 90GB007WIX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=986beb8b-d947-4263-999b-217a2ba5ba78 ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-10-31 (49 days ago) dmi.bios.date: 05/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: O2TKT34A dmi.board.name: 36C5 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258082288149 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO2TKT34A:bd05/25/2017:svnLENOVO:pn90GB007WIX:pvrideacentre510S-08IKL:rvnLENOVO:rn36C5:rvrSDK0J40700WIN3258082288149:cvnLENOVO:ct3:cvrNone: dmi.product.family: ideacentre 510S-08IKL dmi.product.name: 90GB007WIX dmi.product.sku: LENOVO_MT_90GB_BU_LENOVO_FM_ideacentre 510S-08IKL dmi.product.version: ideacentre 510S-08IKL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1908822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I'm on Ubuntu 20.04 with kernel 5.10.1 (https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.10.1/) and the touchpad is working on my Lenovo Legion 5. Thanks for that guys :-) -- 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.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
