[Bug 2018175] Re: [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound at all

[Fernando Vilas]

Speakers work starting with kernel 6.7.0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2018175

Title:
  [Zenbook UP6502ZD_Q539ZD, Realtek ALC294, Speaker, Internal] No sound
  at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2018175/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2058428] [NEW] package ubuntu-business-defaults 39 failed to install/upgrade: el subproceso instalado paquete ubuntu-business-defaults script post-installation devolvió el código de salida de err

[Fernando Sanchez]

Public bug reported:

""Configurando ubuntu-business-defaults (39) ...
/var/lib/dpkg/info/ubuntu-business-defaults.postinst: línea 9: 
update-gconf-defaults: orden no encontrada
dpkg: error al procesar el paquete ubuntu-business-defaults (--configure):
 el subproceso instalado paquete ubuntu-business-defaults script 
post-installation devolvió el código de salida de error 127
Se encontraron errores al procesar:
 ubuntu-business-defaults
E: Sub-process /usr/bin/dpkg returned an error code (1)""

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: ubuntu-business-defaults 39
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
AptOrdering:
 ispell:amd64: Install
 ienglish-common:amd64: Install
 iamerican:amd64: Install
 ubuntu-business-defaults:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Mar 19 18:08:58 2024
ErrorMessage: el subproceso instalado paquete ubuntu-business-defaults script 
post-installation devolvió el código de salida de error 127
InstallationDate: Installed on 2024-03-19 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.11
SourcePackage: ubuntu-business-defaults
Title: package ubuntu-business-defaults 39 failed to install/upgrade: el 
subproceso instalado paquete ubuntu-business-defaults script post-installation 
devolvió el código de salida de error 127
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-business-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058428

Title:
  package ubuntu-business-defaults 39 failed to install/upgrade: el
  subproceso instalado paquete ubuntu-business-defaults script post-
  installation devolvió el código de salida de error 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-business-defaults/+bug/2058428/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2041704] Re: UBSAN: array-index-out-of-bounds

[Fernando Chaves]

*** This bug is a duplicate of bug 2037490 ***
https://bugs.launchpad.net/bugs/2037490

Same here on DELL R710 with PERC 6/iR (SAS1068E), Ubuntu 23.10, kernel
6.5.0-17-generic


scsi host4: ioc1: LSISAS1068E B3, FwRev=00192f00h, Ports=1, MaxQ=266, IRQ=30
[  958.168137] 

[  958.168197] UBSAN: array-index-out-of-bounds in 
/build/linux-eUxUe0/linux-6.5.0/drivers/message/fusion/mptsas.c:2446:22
[  958.168257] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
[  958.168296] CPU: 8 PID: 1758 Comm: modprobe Tainted: G  I
6.5.0-17-generic #17-Ubuntu
[  958.168301] Hardware name: Dell Inc. PowerEdge R410/0N051F, BIOS 1.14.0 
05/30/2018
[  958.168304] Call Trace:
[  958.168309]  
[  958.168314]  dump_stack_lvl+0x48/0x70
[  958.168329]  dump_stack+0x10/0x20
[  958.168335]  __ubsan_handle_out_of_bounds+0xc6/0x110
[  958.168346]  mptsas_sas_io_unit_pg0+0x3d9/0x3f0 [mptsas]
[  958.168364]  mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[  958.168380]  ? __pfx_scsi_runtime_idle+0x10/0x10
[  958.168387]  ? rpm_idle+0x1dc/0x2b0
[  958.168395]  mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[  958.168410]  ? scsi_autopm_put_host+0x1a/0x30
[  958.168416]  mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[  958.168433]  mptsas_probe+0x1e/0x30 [mptsas]
[  958.168452]  local_pci_probe+0x47/0xb0
[  958.168463]  pci_call_probe+0x55/0x190
[  958.168470]  pci_device_probe+0x84/0x120
[  958.168477]  really_probe+0x1c7/0x410
[  958.168488]  __driver_probe_device+0x8c/0x180
[  958.168501]  driver_probe_device+0x24/0xd0
[  958.168508]  __driver_attach+0x10b/0x210
[  958.168514]  ? __pfx___driver_attach+0x10/0x10
[  958.168521]  bus_for_each_dev+0x8d/0xf0
[  958.168527]  driver_attach+0x1e/0x30
[  958.168533]  bus_add_driver+0x127/0x240
[  958.168539]  driver_register+0x5e/0x130
[  958.168545]  ? __pfx_mptsas_init+0x10/0x10 [mptsas]
[  958.168560]  __pci_register_driver+0x62/0x70
[  958.168569]  mptsas_init+0x119/0xff0 [mptsas]
[  958.168583]  do_one_initcall+0x5e/0x340
[  958.168595]  do_init_module+0x91/0x290
[  958.168604]  load_module+0xba1/0xcf0
[  958.168612]  ? vfree+0xff/0x2d0
[  958.168620]  init_module_from_file+0x96/0x100
[  958.168626]  ? init_module_from_file+0x96/0x100
[  958.168635]  idempotent_init_module+0x11c/0x2b0
[  958.168643]  __x64_sys_finit_module+0x64/0xd0
[  958.168650]  do_syscall_64+0x5c/0x90
[  958.168658]  ? exit_to_user_mode_prepare+0x30/0xb0
[  958.168667]  ? syscall_exit_to_user_mode+0x37/0x60
[  958.168674]  ? do_syscall_64+0x68/0x90
[  958.168678]  ? do_syscall_64+0x68/0x90
[  958.168682]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[  958.168690] RIP: 0033:0x7f6fe4b25cfd
[  958.168719] Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d eb 80 0d 00 f7 d8 64 89 01 48
[  958.168723] RSP: 002b:7ffe636f3ca8 EFLAGS: 0246 ORIG_RAX: 
0139
[  958.168728] RAX: ffda RBX: 5642bce79030 RCX: 7f6fe4b25cfd
[  958.168731] RDX: 0004 RSI: 5642bcb11727 RDI: 0003
[  958.168733] RBP: 5642bcb11727 R08: 0040 R09: ff88
[  958.168736] R10: ffc0 R11: 0246 R12: 0004
[  958.168738] R13: 5642bce79140 R14: 5642bce79910 R15: 5642bce797c0
[  958.168745]  
[  958.168766] 

[  958.168819] 

[  958.168863] UBSAN: array-index-out-of-bounds in 
/build/linux-eUxUe0/linux-6.5.0/drivers/message/fusion/mptsas.c:2448:22
[  958.168918] index 1 is out of range for type 'MPI_SAS_IO_UNIT0_PHY_DATA [1]'
[  958.168956] CPU: 8 PID: 1758 Comm: modprobe Tainted: G  I
6.5.0-17-generic #17-Ubuntu
[  958.168960] Hardware name: Dell Inc. PowerEdge R410/0N051F, BIOS 1.14.0 
05/30/2018
[  958.168962] Call Trace:
[  958.168965]  
[  958.168967]  dump_stack_lvl+0x48/0x70
[  958.168975]  dump_stack+0x10/0x20
[  958.168981]  __ubsan_handle_out_of_bounds+0xc6/0x110
[  958.168988]  mptsas_sas_io_unit_pg0+0x3b1/0x3f0 [mptsas]
[  958.169006]  mptsas_probe_hba_phys.isra.0+0x55/0x490 [mptsas]
[  958.169021]  ? __pfx_scsi_runtime_idle+0x10/0x10
[  958.169026]  ? rpm_idle+0x1dc/0x2b0
[  958.169032]  mptsas_scan_sas_topology+0x32/0x210 [mptsas]
[  958.169047]  ? scsi_autopm_put_host+0x1a/0x30
[  958.169053]  mptsas_probe.part.0+0x3cc/0x570 [mptsas]
[  958.169068]  mptsas_probe+0x1e/0x30 [mptsas]
[  958.169083]  local_pci_probe+0x47/0xb0
[  958.169088]  pci_call_probe+0x55/0x190
[  958.169094]  pci_device_probe+0x84/0x120
[  958.169100]  really_probe+0x1c7/0x410
[  958.169107]  __driver_probe_device+0x8c/0x180
[  958.169114]  driver_probe_device+0x24/0xd0
[  958.169120]  __driver_attach+0x10b/0x210
[  958.169127]  ? 

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

Okay, I found this doc:
https://www.x.org/wiki/Development/Documentation/ServerDebugging/ for
the server debugging, is it enough? Do you know any other
tutorials/resources so I can try do it by myself? And I would appreciate
if a Ubuntu MATE contributor could help.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

Time that I opened Firefox through the GUI.
mai 30 16:40:37 fernando-Latitude-E5500 systemd[1562]: Started 
snap.firefox.firefox.b2449455-56d8-4537-8f78-5f51a04cd9a5.scope.

First logs after I entered the link at Firefox.
mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 
threads of 4 processes of 1 users.
mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 
threads of 4 processes of 1 users.
mai 30 16:41:43 fernando-Latitude-E5500 pulseaudio[1575]: X11 I/O error handler 
called
mai 30 16:41:43 fernando-Latitude-E5500 at-spi-bus-launcher[1921]: X connection 
to :0 broken (explicit kill or server shutdown).

16:41:43 is the exact time the session crashed.


** Attachment added: "Logs reproducing the issue."
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593923/+files/journalctl-after-issue.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

** Attachment removed: "journalctl-after-issue.log"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

I don't recall which time exactly, sorry! I will delete the previous log
and send a new one with the time it crashed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

Sebastien, here's the log file from the command after the issue.

** Attachment added: "journalctl-after-issue.log"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

Hi Alberto, I used the "echo $XDG_SESSION_TYPE" to check the display
server and it returned "x11", which I assume it's Xorg (don't know
anything about this).

I will attach the new logs for the commands you've asked.

** Attachment added: "Contains the commands asked by Alberto"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593895/+files/xdg-snapdesk.zip

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Snap.Connections.txt

[Fernando Karchiloff]

apport information

** Attachment added: "Snap.Connections.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593554/+files/Snap.Connections.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Snap.Info.snapd.txt

[Fernando Karchiloff]

apport information

** Attachment added: "Snap.Info.snapd.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593555/+files/Snap.Info.snapd.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] ProcEnviron.txt

[Fernando Karchiloff]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593553/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] ProcCpuinfoMinimal.txt

[Fernando Karchiloff]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593552/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser

[Fernando Karchiloff]

apport information

** Tags added: apport-collected

** Description changed:

  From a fresh install with Ubuntu Mate 22.04, do:
  
  1. Login into your user with password.
  2. Open Firefox.
  3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address.
  4. GUI will reset and go back to login screen like started a new session.
  
  This also happens when I tried with opening a '.log' with Pluma.
  
- I've tried a lot of things at other installation to tackle this problem,
- but I couldn't solve the problem.
+ I've tried a lot of things at other installation to tackle this problem, but 
I couldn't solve the problem.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.1
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-27 (1 days ago)
+ InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
+ ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
+ Snap: snapd 2.55.5 (latest/stable)
+ Snap.Changes:
+  ID   Status  Spawn  Ready  Summary
+  3Done2022-05-28T10:43:02-03:00  2022-05-28T10:46:00-03:00  
Auto-refresh snaps "core20", "firefox", "snapd"
+ Tags:  jammy
+ Uname: Linux 5.15.0-33-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1976161/+attachment/5593551/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976161

Title:
  Session restarts when opening Pluma or GitHub link in browser

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1967800] Re: 无法连接网络。没有WiFi标志。

[Fernando Bustos]

** Changed in: cloud-init
   Status: Incomplete => Confirmed

** Changed in: cloud-init
 Assignee: (unassigned) => Fernando Bustos (fercho89)

** Also affects: ubuntu
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967800

Title:
  无法连接网络。没有WiFi标志。

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1967800/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

[Fernando Ruiz]

I use this version: PanGPLinux-5.3.2-c3

To make it work for me in this version, I modified the configuration
file: /usr/lib/ssl/openssl.cnf

and comment the following section:

-

# [openssl_init]
# providers = provider_sect

-

and added this new section just below the section I commented on
earlier:

-

[openssl_init]
ssl_conf = ssl_sect

[ssl_sect]
system_default = system_default_sect

[system_default_sect]
Options = UnsafeLegacyRenegotiation

-

Reboot globalprotect and ready!


It is very similar to the solution of @kelly-schoenhofen, Thanks you!!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960268

Title:
  SSL handshake failed - VPN SSL broken in 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Hi,

```uname -r```

5.13.0-40-generic

Issue still ongoing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960936] [NEW] Laptop stalls, kernel log flooded with "Allocating resources"

[Fernando Laudares Camargos]

Public bug reported:

Hi,
I have experiencing this for a while now (1 year+), with the laptop (Thinkpad 
T430s) stalling at times, and often for a long period (hours). Even under very 
low load. In fact, the issue seems to affect input devices (mouse and keyboard, 
both external and built-in devices), as the screens continue to operate 
normally and receiving notifications from applications, such as Slack.

The /var/log/kern.log gets flooded with messages like:

Feb 15 13:40:12 fernando-ThinkPad-T430s kernel: [  516.556167] pci_bus :04: 
Allocating resources
Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [  518.031745] pci_bus :02: 
Allocating resources
Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [  518.031756] pci_bus :03: 
Allocating resources
Feb 15 13:40:13 fernando-ThinkPad-T430s kernel: [  518.031814] pci_bus :04: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  518.771217] pci_bus :02: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  518.771230] pci_bus :03: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  518.771291] pci_bus :04: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  519.510986] pci_bus :02: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  519.510999] pci_bus :03: 
Allocating resources
Feb 15 13:40:14 fernando-ThinkPad-T430s kernel: [  519.511058] pci_bus :04: 
Allocating resources
Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [  520.986362] pci_bus :02: 
Allocating resources
Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [  520.986374] pci_bus :03: 
Allocating resources
Feb 15 13:40:16 fernando-ThinkPad-T430s kernel: [  520.986435] pci_bus :04: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  521.722015] pci_bus :02: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  521.722026] pci_bus :03: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  521.722068] pci_bus :04: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  522.457759] pci_bus :02: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  522.457771] pci_bus :03: 
Allocating resources
Feb 15 13:40:17 fernando-ThinkPad-T430s kernel: [  522.457807] pci_bus :04: 
Allocating resources
Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [  523.933552] pci_bus :02: 
Allocating resources
Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [  523.933572] pci_bus :03: 
Allocating resources
Feb 15 13:40:19 fernando-ThinkPad-T430s kernel: [  523.933638] pci_bus :04: 
Allocating resources

Would the problem be linked to a driver that controls a pci device? A
malfunctioning hardware part? Sometimes the issue is not noticed for
days.

I should also note the disc is encrypted and even if I restart the
computer, when Ubuntu starts loading and the prompt to enter the
password to access the disk, the issue is already manifesting itself: I
type the password and sometimes the key that is pressed is not sent,
sometimes it is send twice.

Any other information I can provide, please let me know. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-99-generic 5.4.0-99.112
ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
Uname: Linux 5.4.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fernando   2655 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Feb 15 13:45:42 2022
InstallationDate: Installed on 2019-10-28 (841 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: LENOVO 23539KU
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-99-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-99-generic N/A
 linux-backports-modules-5.4.0-99-generic  N/A
 linux-firmware1.187.25
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-07-12 (583 days ago)
dmi.bios.date: 11/12/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET63WW (2.05 )
dmi.board.asset.tag: Not Available
dmi.board.name: 23539KU
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ET63WW(2.05):bd11/12/2012:svnLENOVO:pn23539KU:pvrThinkPadT430s:rvnLENOVO:rn23539KU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.pr

[Bug 1954843] Re: amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid argument

[Fernando Sclavo]

Just updated my laptop (Ubuntu 20.04.3 LTS) from 5.13.0-27-generic to 
5.13.0-28-generic and have the same issue (stuck in max brightness).
On 5.13.0-27-generic, brightness adjust works fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954843

Title:
  amdgpu_bl0: Failed to write system 'brightness' attribute: Invalid
  argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954843/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943755] [NEW] Ubuntu 21.04 install crash when update grub on sda

[Carlos Fernando Castañeda O . Bioengineering UniCauca]

Public bug reported:

Ubuntu 21.04 install crash when update grub on sda. It is possible that
fails because my old  computer has not UEFI or something wrong in my old
motherboard.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 15 13:58:00 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-16-generic
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943755

Title:
  Ubuntu 21.04 install crash when update grub on sda

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943755/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 577881] Re: gcc does not compile under ubuntu 10.04

[Fernando]

** Changed in: gcc-defaults (Ubuntu)
   Status: Expired => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577881

Title:
  gcc does not compile under ubuntu 10.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/577881/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 577881] Re: gcc does not compile under ubuntu 10.04

[Fernando]

This seems to be still an issue with Ubuntu 20.04. I am experiencing the
issue with Linux Mint 20.2, which is based on Ubuntu 20.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/577881

Title:
  gcc does not compile under ubuntu 10.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/577881/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943037] [NEW] Automounts do not reset properly after TimeoutIdleSec automatic unmounts

[Fernando]

Public bug reported:

Ubuntu version: Ubuntu 20.04.3 LTS
systemd version: 245.4-4ubuntu3.11

Expected behavior:

Automount units whose associated mount units have been auto-unmounted
with TimeoutIdleSec will trigger the associated mount unit when the
automount path is accessed again

Current behavior:

Automount units whose associated mount units have been auto-unmounted
with TimeoutIdleSec do not trigger the associated mount unit when the
automount path is accessed again until the automount unit is completely
restarted.

Steps to reproduce the problem

1. Trigger any automount unit with TimeoutIdleSec= set
2- Wait for the idle time to occur and systemd to unmount the associated mount 
unit
3. Then try to access the automount location again.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943037

Title:
  Automounts do not reset properly after TimeoutIdleSec automatic
  unmounts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1943037/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Luiz Fernando]

I sufer with this issue dor years, and it still haunts the hell out of me.
I'm tired of installing on special prepared hardware with no drives.
Please fix this asap.
Please with sugar on top!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379

Title:
  installer uses first EFI system partition found even when directed
  otherwise

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937126] Re: Multiple docks visible

[Fernando Fernandes Bonadio]

Ok agora entendi, desculpe por isso.

** Attachment added: "settings.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+attachment/5515026/+files/settings.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126

Title:
  Multiple docks visible

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937126] Re: bug found

[Fernando Fernandes Bonadio]

Eu n�o consegui executar este comando gsettings list-recursively
org.gnome.shell > settings.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126

Title:
  bug found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937126] Re: bug found

[Fernando Fernandes Bonadio]

Este é o bug que estava comentando, hoje após a sessão ser bloqueada ao
realizar o login o bug aparece.

** Attachment added: "bug encontrado"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+attachment/5514110/+files/Captura%20de%20tela%20de%202021-07-27%2014-01-40.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126

Title:
  bug found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937126] Re: bug found

[Fernando Fernandes Bonadio]

Bom dia!, na verdade o bug em si n�o est� no xorg mas sim na wayland, pe�o 
desculpa pelo erro na escolha no formul�rio.
Basicamente ap�s um per�odo de sess�o logado o painel na barra superior onde 
adicionei uma extens�o para me mostrar os locais em meu computador deixa de 
ficar traduzido para o portugu�s-br e volta para o ingl�s.
Observei tamb�m de que quando isso ocorre acontece um bug na doca o qual tamb�m 
modifiquei por extens�o e a deixei na parte inferior da tela, contudo ao 
acessar o menu de aplicativos ela acaba aparecendo na parte esquerda do meu 
monitor ficando vis�veis duas docas uma abaixo e uma ao lado.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126

Title:
  bug found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1937126] [NEW] bug found

[Fernando Fernandes Bonadio]

Public bug reported:

I downloaded version 21.04 of ubuntu, then I realized that when I downloaded 
the gnome shell tweaking tool, I realized that when I changed the theme of the 
dock and added in the top bar the option to show the option of locations on the 
system, it leaves my language after performing some accesses in the application 
menu this behavior appears.
I also noticed that by accessing the applications menu the dock that I modified 
to appear in the lower corner of the screen is now also displayed on the left 
side of my monitor.
I apologize for the English, but I live in Brazil and I am not fluent in this 
language.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 21 16:23:56 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a]
InstallationDate: Installed on 2021-07-17 (3 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
 Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81S9
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2020
dmi.bios.release: 1.50
dmi.bios.vendor: LENOVO
dmi.bios.version: ASCN50WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IWL
dmi.ec.firmware.release: 1.50
dmi.modalias: 
dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL:
dmi.product.family: IdeaPad S145-15IWL
dmi.product.name: 81S9
dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL
dmi.product.version: Lenovo IdeaPad S145-15IWL
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubuntu wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126

Title:
  bug found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1937126/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923256] Re: Unable to Upgrade from 18.04 to 20.04

[Fernando Maia]

Hi,
Sorry to only report on this, but the machine was at another location. Before 
trying the:

do-release-upgrade -p

I updated the system with the latest updates (had not been updated since
the time I reported the problem) and tried to run the normal:

do-release-upgrade

Something was changed by the recent updates, because it is running the
upgrade now. Maybe the new version of the "do-release-upgrade" package
solved it.

If you need any info from this system, please let me know.

Will Post again after the upgrade ends.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923256

Title:
  Unable to Upgrade from 18.04 to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally

[Fernando Vitor Ventilari Neder]

I can confirm this. I'm using Ubuntu 20.04.2 LTS and GNOME Terminal has
the same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927063

Title:
  Terminal prompt got strangely replicated when resizing terminal
  horizontally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925084] [NEW] package snapd 2.49+21.04build1 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1

[Fernando Lobão]

Public bug reported:

Post install

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: snapd 2.49+21.04build1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
AptOrdering:
 gnome-software-plugin-snap:amd64: Purge
 snapd:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 31 12:42:32 2021
Df:
 Filesystem 1K-blocks  Used Available Use% Mounted on
 tmpfs1616652 12556   1604096   1% /run
ErrorMessage: installed snapd package post-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2021-04-19 (0 days ago)
InstallationMedia: Ubuntu Unity 21.04
Python3Details: /usr/bin/python3.9, Python 3.9.2, python3-minimal, 3.9.2-2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.7.1ubuntu4
 apt  2.2.2
SourcePackage: snapd
Title: package snapd 2.49+21.04build1 failed to install/upgrade: installed 
snapd package post-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: snapd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925084

Title:
  package snapd 2.49+21.04build1 failed to install/upgrade: installed
  snapd package post-removal script subprocess returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1925084/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Folks would like to suggest two changes to the description:

1)

 * Users of a NetApp E-Series RDAC due to very long names increasing
   the VDP page and and cause multipathd to hang

The above is not exactly true, in fact any target (can be any storage
vendor) with long names may hit if select_checker is enabled.

2)

[Test Case]

 * #1 Case: Test on a NetApp E-Series RDAC, the reporter has such HW and
   is able to do so.

Reporter has only SolidFire storage to test with. Would like to know for
you if the test output with a SolidFire device (will hit the long names
issue) is actually enough to validate the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi folks, I will test that again using SolidFire hardware and get back
soon with the results. We don't a have E-series storage to test but my
understanding is that isn't the goal of the fix anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1923256] [NEW] Unable to Upgrade from 18.04 to 20.04

[Fernando Maia]

Public bug reported:

Trying to upgrade from 18.04 to 20.04. Machine was off for the last 2
years.

An unresolvable problem occurred while calculating the upgrade.

This was likely caused by: 
* Unofficial software packages not provided by Ubuntu 
Please use the tool 'ppa-purge' from the ppa-purge 
package to remove software from a Launchpad PPA and 
try the upgrade again. 

If none of this applies, then please report this bug using the 
command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal. If 
you want to investigate this yourself the log files in 
'/var/log/dist-upgrade' will contain details about the upgrade. 
Specifically, look at 'main.log' and 'apt.log'. 

In main.log and apt.log I only get:

sudo ack "ERROR Dist-upgrade"  /var/log/dist-upgrade
/var/log/dist-upgrade/20210409-2136/main.log
123:2021-04-09 21:32:27,108 ERROR Dist-upgrade failed: 'E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages.'

/var/log/dist-upgrade/main.log
116:2021-04-09 21:57:40,820 ERROR Dist-upgrade failed: 'E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages.'

/var/log/dist-upgrade/20210409-2156/main.log
115:2021-04-09 21:45:52,083 ERROR Dist-upgrade failed: 'E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages.'

/var/log/dist-upgrade/20210409-2144/main.log
115:2021-04-09 21:38:20,080 ERROR Dist-upgrade failed: 'E:Error, 
pkgProblemResolver::Resolve generated breaks, this may be caused by held 
packages.'


I have no held packages, and there are no packages to upgrade. 

sudo apt upgrade 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

apt-mark showhold gives nothing.

I'm at a loss...

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature: Ubuntu 4.15.0-140.144-generic 4.15.18
Uname: Linux 4.15.0-140-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr  9 21:58:11 2021
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-04-09 (0 days ago)

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923256

Title:
  Unable to Upgrade from 18.04 to 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1923256/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1918227] Re: [amdgpu] No display after sleep

[Fernando Castro]

*** This bug is a duplicate of bug 1916950 ***
https://bugs.launchpad.net/bugs/1916950

Thank you to all who worked on this. It has been fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918227

Title:
  [amdgpu] No display after sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918227/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1429446] Re: Touchpad incorrectly recognized as PS/2 mouse in 'Lenovo ThinkPad 20DF004SMC'

[Fernando]

Is anyone looking into this? It has been a long time with this bug open
and I'd like to know if I can help (testing or something, I am not very
savvy...)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1429446

Title:
  Touchpad incorrectly recognized as PS/2 mouse in 'Lenovo ThinkPad
  20DF004SMC'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429446/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1918227] [NEW] No display after sleep

[Fernando Castro]

Public bug reported:

Approximately two weeks ago after leaving the computer alone the display
turned off like normal but did not come back.The system is working in
the background but the display wont show. I've gotten it to work
sometimes by pulling out the display port cable out and putting it back
in but that hasn't been working lately. Any help would be greatly
appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  8 22:44:08 2021
DistUpgraded: 2020-05-07 22:40:27,977 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1043:0577]
InstallationDate: Installed on 2019-10-30 (495 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic 
root=UUID=cdbb24bd-9536-4aa2-b059-e849c202173a ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-08 (305 days ago)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2407
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2407:bd07/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918227

Title:
  No display after sleep

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1918227/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917974] [NEW] Xorg freeze

[José Fernando Durán Pérez]

Public bug reported:

I had been using the recommended nvidia driver (nvidia-driver-460). I
recently changed to xserver-xorg-video-nouveau for the following
reasons:

1) The resolution configuration was not saved. It is, every power off
and power on the resolution restarted to low resolution.

2) The syslog file in /var/log/ constantly was filled with logs (may be
with a rate of 1 GB per hour), then, I was enforced to install busybox-
syslogd to stop the logging and continue with activities.

3) When using xserver-xorg-video-nouveau, in contrast with nvidia-
driver-460, i didn't had to reset the resolution configuration, which
was great, but now the screen is constantly freezing and i had to use
alt+SysRq+REISUB two times in a day

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  5 22:59:16 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Today
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP108 [GeForce GT 1030] [1458:375c]
InstallationDate: Installed on 2021-02-27 (7 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Default string Default string
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=28228923-7b88-4688-b9fd-157d9ebc22df ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/03/2020
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Default string
dmi.board.name: X99-k9
dmi.board.vendor: MACHINIST
dmi.board.version: V1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd06/03/2020:br5.11:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnMACHINIST:rnX99-k9:rvrV1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal freeze ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917974

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1917974/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917091] [NEW] package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Fernando]

Public bug reported:

none

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Feb 26 18:08:41 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2020-05-30 (272 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917091

Title:
  package linux-image-5.8.0-44-generic 5.8.0-44.50~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1917091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 40148] Re: Key (Code 94) does not work anymore

[Fernando]

In my system, ubuntu 20. The bug behaves similar. Key works fine in tty
(outside X). In graphical mode what should be less greater, becomes \|

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40148

Title:
  Key (Code 94) does not work anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/40148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866619] Re: OverflowError when machine suspends and resumes after a longer while

[Luiz Fernando]

As of 2021/02/11, dstat is still spitting this error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866619

Title:
  OverflowError when machine suspends and resumes after a longer while

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 844582] Re: "Invalid argument" when trying to scan

[Fernando]

Hello,
I have the same problem:
   gscan2pdf: sane_start: Invalid argument

I run from the command line with the "--log=log" option and create the log.xz 
file that I attach.
My system is:
   * Kubuntu 20.10 (Ubuntu + KDE)
   * Scanner: Brother DCP-J562DW
I've been able to use this scanner in al ubuntu versions (I'm long linux user 
and gscan2pdf too), but I'm not sure if I've used with the previous 20.04 
version (I think that yes).

I have another PC with Windows 10 and the scanner works. So is something
with my system not with the device.


** Attachment added: "Log for gscan2pdf"
   
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+attachment/5458553/+files/log.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844582

Title:
  "Invalid argument" when trying to scan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

[Fernando]

The bug persists with accented characters if the dead key is the first
character you type. I mean, open the overview, type "á" and you see just
"a". Then type another "á" and it shows correctly. Same if you type
"lá", the accent shows correctly because the dead key wasn't the first
thing you typed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Hi,

```uname -r```
5.4.0-58-generic

Issue still ongoing.

Now, with the workaround

```sudo modprobe -r psmouse && sudo modprobe psmouse´´´

It still works, after typing several times the same command, but I
noticed some things:

1.- Mouse gets idle sometimes and changes to generic mouse after that
2.- When working, settings are not working properly; Natural scrolling is on, 
but is not working, same than 'tap to click'.

Just switching off and on again the settings make it works properly, but
this needs to be done every single time the 'modprobe' workaround
finally works...

Hope this helps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1908833] [NEW] Installation crashed at the end OS instalation (Caine Linux 18.0)

[Fernando]

Public bug reported:

Caine Linux 18.0 instalation crashed at the end, after clicking on
continue after installation.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12 [modified: lib/partman/init.d/30parted 
usr/share/ubiquity/apt-setup usr/share/ubiquity/plugininstall.py]
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CasperVersion: 1.394
Date: Sun Dec 20 20:02:33 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/custom.seed 
boot=casper iso-scan/filename= quiet splash --
LiveMediaBuild: CAINE 18.04 - Release amd64
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic custom ubiquity-18.04.14.12

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908833

Title:
  Installation crashed at the end OS instalation (Caine Linux 18.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908833/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1903230] Re: Mutter release 3.36.7

[Fernando]

Is there any expected date to ship this update?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903230

Title:
  Mutter release 3.36.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

[Fernando]

*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159

Same bug, Acer Aspire V-Nitro vn7-792G-79LX intel + Nvidia Graphics

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874194

Title:
  Ubuntu 20.04 HDMI connected, no boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874194/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553687] Re: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0'

[Fernando]

This bug only happens when windows go to hibernation instead of shutting
down; at least for my machine...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553687

Title:
  Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to
  'hd0'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1553687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Hi,

```uname -r```
5.4.0-53-generic

Issue still ongoing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

[Fernando]

Wow, thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

[Fernando]

Thanks, Daniel. Is there any way of encouraging that mutter update in
Focal? Or at least of estimating when it will be shipped?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

[Luiz Fernando Pinto de Oliveira]

Thank you very much @Sebastien for the indication of the similar bug
(bug #1871320). The same problem is happening to me. How do I solve it?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902715

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902715] Re: Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

[Luiz Fernando Pinto de Oliveira]

What desktop environment do you use?
R -> I am using the GNOME version 3.36.3 in Ubuntu 20.04. 

how do you test if it changed?
I use the terminal. I simply open the terminal and press the Tab key. And for 
example, I chose the "Sonar" alert sound, but I always hear the "Drip" sound.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902715

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1902715] [NEW] Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

[Luiz Fernando Pinto de Oliveira]

Public bug reported:

I installed the Ubuntu version 20.04 LTS. I would like to change the
alert sound. I followed these steps:

1.Open the Activities overview and start typing Sound;
2.Click on Sound to open the panel;
3.In the Alert Sound section, select an alert sound.

However, after choosing the preferred sound it does not change!

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902715

Title:
  Change alert sound ubuntu not working (Ubuntu 20.04 LTS)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1902715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

[Fernando]

GContactSync, which is the only working extension recommended by
Thunderbird to sync Google contacts (https://support.mozilla.org/en-
US/kb/thunderbird-and-gmail), doesn't work yet in version 78
(https://github.com/jdgeenen/gcontactsync/issues/163). An upgrade to 78
may lead to unexpected breakage for many.

** Bug watch added: github.com/jdgeenen/gcontactsync/issues #163
   https://github.com/jdgeenen/gcontactsync/issues/163

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895643

Title:
  Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi Christian, just to make it sure we are in sync:

Problem is not related to users using NetApp E-Series. I've reproduced
this issue in a NetApp SolidFire system that has no relation with
E-Series. My understanding is that any storage system our platform that
make use of target names larger than 254 bytes will hit this problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell

[Fernando]

I'm amazed and very grateful for how fast this has been fixed, thanks!
Will there be an SRU soon shipping this fix?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't use dead keys or input e.g. Chinese characters in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

```ùname -r```
5.4.0-48-generic

Issue still ongoing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi Christian, sorry for the late reply.

After applying the PPA, multipath no longer hangs when attaching a
SolidFire volumes. The problem with long iscsi target names seems to be
fixed now.

See the output bellow:

stack@60-sfernand-development:~$ sudo multipath -v6 -ll
Oct 13 20:22:27 | loading //lib/multipath/libchecktur.so checker
Oct 13 20:22:27 | loading //lib/multipath/libprioconst.so prioritizer
Oct 13 20:22:27 | Discover device 
/sys/devices/pci:00/:00:06.0/virtio3/block/vda
Oct 13 20:22:27 | vda: dev not found in pathvec
Oct 13 20:22:27 | 252:0: dev_t not found in pathvec
Oct 13 20:22:27 | vda: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device 
/sys/devices/pci:00/:00:06.0/virtio3/block/vda/vda1
Oct 13 20:22:27 | Discover device 
/sys/devices/pci:00/:00:06.0/virtio3/block/vda/vda14
Oct 13 20:22:27 | Discover device 
/sys/devices/pci:00/:00:06.0/virtio3/block/vda/vda15
Oct 13 20:22:27 | Discover device 
/sys/devices/platform/host4/session228/target4:0:0/4:0:0:0/block/sdc
Oct 13 20:22:27 | sdc: dev not found in pathvec
Oct 13 20:22:27 | 8:32: dev_t not found in pathvec
Oct 13 20:22:27 | sdc: udev property ID_WWN whitelisted
Oct 13 20:22:27 | sdc: mask = 0x7
Oct 13 20:22:27 | sdc: dev_t = 8:32
Oct 13 20:22:27 | open 
'/sys/devices/platform/host4/session228/target4:0:0/4:0:0:0/block/sdc/size'
Oct 13 20:22:27 | sdc: size = 10485760
Oct 13 20:22:27 | sdc: vendor = SolidFir
Oct 13 20:22:27 | sdc: product = SSD SAN
Oct 13 20:22:27 | sdc: rev = 0001
Oct 13 20:22:27 | sdc: h:b:t:l = 4:0:0:0
Oct 13 20:22:27 | sdc: tgt_node_name = 
iqn.2010-01.com.solidfire:xpsi.uuid-e100a0c6-f8d6-4927-b6ea-213248083965.3409
Oct 13 20:22:27 | open 
'/sys/devices/platform/host4/session228/target4:0:0/4:0:0:0/state'
Oct 13 20:22:27 | sdc: path state = running
Oct 13 20:22:27 | sdc: 1018 cyl, 166 heads, 62 sectors/track, start at 0
Oct 13 20:22:27 | open 
'/sys/devices/platform/host4/session228/target4:0:0/4:0:0:0/vpd_pg80'
Oct 13 20:22:27 | sdc: serial = 787073690d51f47acc01
Oct 13 20:22:27 | sdc: get_state
Oct 13 20:22:27 | sdc: detect_checker = yes (setting: storage device 
configuration)
Oct 13 20:22:27 | failed to issue vpd inquiry for pgc9
Oct 13 20:22:27 | sdc: path_checker = tur (setting: multipath internal)
Oct 13 20:22:27 | sdc: checker timeout = 30 s (setting: multipath internal)
Oct 13 20:22:27 | sdc: tur state = up
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop0
Oct 13 20:22:27 | loop0: dev not found in pathvec
Oct 13 20:22:27 | 7:0: dev_t not found in pathvec
Oct 13 20:22:27 | loop0: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop1
Oct 13 20:22:27 | loop1: dev not found in pathvec
Oct 13 20:22:27 | 7:1: dev_t not found in pathvec
Oct 13 20:22:27 | loop1: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop2
Oct 13 20:22:27 | loop2: dev not found in pathvec
Oct 13 20:22:27 | 7:2: dev_t not found in pathvec
Oct 13 20:22:27 | loop2: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop3
Oct 13 20:22:27 | loop3: dev not found in pathvec
Oct 13 20:22:27 | 7:3: dev_t not found in pathvec
Oct 13 20:22:27 | loop3: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop4
Oct 13 20:22:27 | loop4: dev not found in pathvec
Oct 13 20:22:27 | 7:4: dev_t not found in pathvec
Oct 13 20:22:27 | loop4: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop5
Oct 13 20:22:27 | loop5: dev not found in pathvec
Oct 13 20:22:27 | 7:5: dev_t not found in pathvec
Oct 13 20:22:27 | loop5: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop6
Oct 13 20:22:27 | loop6: dev not found in pathvec
Oct 13 20:22:27 | 7:6: dev_t not found in pathvec
Oct 13 20:22:27 | loop6: blacklisted, udev property missing
Oct 13 20:22:27 | Discover device /sys/devices/virtual/block/loop7
Oct 13 20:22:27 | loop7: dev not found in pathvec
Oct 13 20:22:27 | 7:7: dev_t not found in pathvec
Oct 13 20:22:27 | loop7: blacklisted, udev property missing
Oct 13 20:22:27 | Discovered 1/10 paths
= paths list =
uuid hcildev dev_t pri dm_st chk_st vend/prod/revdev_st 
 4:0:0:0 sdc 8:32  -1  undef undef  SolidFir,SSD SAN unknown
Oct 13 20:22:27 | libdevmapper version 1.02.145 (2017-11-03)
Oct 13 20:22:27 | DM multipath kernel driver v1.13.0
Oct 13 20:22:27 | tur checker refcount 1
Oct 13 20:22:27 | unloading const prioritizer
Oct 13 20:22:27 | unloading tur checker

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:

[Bug 1900906] ProcCpuinfoMinimal.txt

[Fernando]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425394/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't input accents in GNOME shell

[Fernando]

apport information

** Tags added: apport-collected

** Description changed:

- I'm running an up-to-date Ubuntu Focal. I have a standard Spanish
- keyboard. Under X, if I try to input an accentuated character, such as á
- or ü, in places like the search field in the overview or when writing a
- folder name in the app grid, nothing appears. Under Wayland, it fails
- each time on the first input of an accentuated character, then it works.
+ I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. 
Under X, if I try to input an accentuated character, such as á or ü, in places 
like the search field in the overview or when writing a folder name in the app 
grid, nothing appears. Under Wayland, it fails each time on the first input of 
an accentuated character, then it works.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.9
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-05-01 (174 days ago)
+ InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
+ Package: ibus
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
+ RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
+ Tags:  focal
+ Uname: Linux 5.4.0-52-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago)
+ UserGroups: sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425392/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] GsettingsChanges.txt

[Fernando]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425393/+files/GsettingsChanges.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] ProcEnviron.txt

[Fernando]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425395/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] monitors.xml.txt

[Fernando]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425397/+files/monitors.xml.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] ShellJournal.txt

[Fernando]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1900906/+attachment/5425396/+files/ShellJournal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900908] Re: Mutter doesn't apply gsettings appropriately to Wacom tablet

[Fernando]

** Description changed:

  I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
  + external). Under an up-to-date Ubuntu Focal running X, if I map the
  tablet to a single monitor it fails to map it more often than not. A
  reliable way of getting failure is first connecting the tablet via
  bluetooth and then via USB. The only way to revert to a correct behavior
  is reseting X (ALT+F2 r). This is necessary even after rebooting.
  
  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
  it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
  what it does when it works well).
  
  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).
+ 
+ PS I reported this bug agains the Wacom X driver but was told it's
+ really related to mutter (https://github.com/linuxwacom/xf86-input-
+ wacom/issues/148).

** Description changed:

  I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
  + external). Under an up-to-date Ubuntu Focal running X, if I map the
  tablet to a single monitor it fails to map it more often than not. A
  reliable way of getting failure is first connecting the tablet via
  bluetooth and then via USB. The only way to revert to a correct behavior
  is reseting X (ALT+F2 r). This is necessary even after rebooting.
  
  I've noticed that, when not working well, the problem is that Mutter
  sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
  it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
  what it does when it works well).
  
  Under Wayland it works well (well, the tablet buttons don't work under
  Wayland but this is unrelated).
  
- PS I reported this bug agains the Wacom X driver but was told it's
+ PS I reported this bug against the Wacom X driver but was told it's
  really related to mutter (https://github.com/linuxwacom/xf86-input-
  wacom/issues/148).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900908

Title:
  Mutter doesn't apply gsettings appropriately to Wacom tablet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1900908/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] Re: Can't input accents in GNOME shell

[Fernando]

** Description changed:

- I have a standard Spanish keyboard. If I try to input an accentuated
- character, such as á or ü, in places like the search field in the
- overview or when writing a folder name in the app grid, nothing appears.
+ I'm running an up-to-date Ubuntu Focal. I have a standard Spanish
+ keyboard. Under X, if I try to input an accentuated character, such as á
+ or ü, in places like the search field in the overview or when writing a
+ folder name in the app grid, nothing appears. Under Wayland, it fails
+ each time on the first input of an accentuated character, then it works.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900908] [NEW] Mutter doesn't apply gsettings appropriately to Wacom tablet

[Fernando]

Public bug reported:

I have a Wacom Intuos VT M tablet in a setting with two monitors (laptop
+ external). Under an up-to-date Ubuntu Focal running X, if I map the
tablet to a single monitor it fails to map it more often than not. A
reliable way of getting failure is first connecting the tablet via
bluetooth and then via USB. The only way to revert to a correct behavior
is reseting X (ALT+F2 r). This is necessary even after rebooting.

I've noticed that, when not working well, the problem is that Mutter
sends the mapping data to the "Wacom Intuos BT M Pad pad" device, while
it should be sending them to "Wacom Intuos BT M Pad stylus" (this is
what it does when it works well).

Under Wayland it works well (well, the tablet buttons don't work under
Wayland but this is unrelated).

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900908

Title:
  Mutter doesn't apply gsettings appropriately to Wacom tablet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1900908/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1900906] [NEW] Can't input accents in GNOME shell

[Fernando]

Public bug reported:

I have a standard Spanish keyboard. If I try to input an accentuated
character, such as á or ü, in places like the search field in the
overview or when writing a folder name in the app grid, nothing appears.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900906

Title:
  Can't input accents in GNOME shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900906/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

*** This bug is a duplicate of bug 1898152 ***
https://bugs.launchpad.net/bugs/1898152

Thank you very much. System is already updated. Everything went OK.
Best regards

   Fernando Isasi

El lunes, 12 de octubre de 2020 16:41:51 (CEST) usted escribió:
> *** This bug is a duplicate of bug 1898152 ***
> https://bugs.launchpad.net/bugs/1898152
> 
> This is now happening because the gnuradio-dev package is installed.
> 
> ** This bug has been marked a duplicate of bug 1898152
>upgrade fails to calculate if gnuradio-dev is installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

The same problem:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

** Attachment added: "apt-clone_system_state.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+attachment/5420525/+files/apt-clone_system_state.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

The same problem:


** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+attachment/5420524/+files/apt.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+attachment/5420526/+files/lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890638] Re: I am unable to update my Ubuntu from 18.04 to 20.4

[Fernando Isasi]

** Attachment added: "main.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+attachment/5420528/+files/main.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890638

Title:
  I am unable to update my Ubuntu from 18.04 to 20.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890638/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi Christian, I've tested the PPA and seems to work just fine. I will
post the results here by the and of this week.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi Christian, sounds good to me. I can test it for sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] Re: Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Hi Christian, you are correct. I Can't reproduce this issue in Focal
(0.8.3).

Could multipath-tools be upgraded to 0.8.3 for Bionic aswell?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891202

Title:
  Multipathd hangs with long iscsi target names in Ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1891202/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1896349] Re: PCI/internal sound card not detected

[Fernando Marcel Tarantino Martins]

Mr Wang, the computer now showed the same problem! I don't know what
happens.
w how to
I tried to solve it using your link, but I don't know how to proceed to
make the backup you ask and also don't know how to attach the other files.
I'm kind of new using Linux and sometimes it's difficult to understand what
application and what steps I have to do in order to make things work as it
should.

On Mon, Sep 21, 2020 at 8:02 AM Fernando Marcel 
wrote:

> Hi, Mr. Wang.
>
> I don't know how but in the next day it just worked normally.
>
> Thank you anyways! :)
>
> On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
> wrote:
>
>> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
>> firmware/+bug/1892714/comments/46
>> <https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1892714/comments/46>
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1896349
>>
>> Title:
>>   PCI/internal sound card not detected
>>
>> Status in alsa-driver package in Ubuntu:
>>   New
>>
>> Bug description:
>>   Description:  Ubuntu 20.04.1 LTS
>>   Release:  20.04
>>
>>   I can select my default audio hardware
>>
>>   When I test it, doesn't work.
>>
>>   When watching a Youtube video, for example, audio doesn't work as
>>   well.
>>
>>   Thru the command lspci, this shows up:
>>
>>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
>> G7 (rev 07)
>>   00:04.0 Signal processing controller: Intel Corporation Device 8a03
>> (rev 03)
>>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
>> Controller (rev 03)
>>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
>> Controller (rev 30)
>>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
>> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #0 (rev 30)
>>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
>> Serial IO I2C Controller #1 (rev 30)
>>   00:16.0 Communication controller: Intel Corporation Management Engine
>> Interface (rev 30)
>>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
>> Controller [RAID mode] (rev 30)
>>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #5 (rev 30)
>>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
>> #9 (rev 30)
>>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev
>> 30)
>>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
>> Technology Audio Controller (rev 30)
>>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
>> Controller (rev 30)
>>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev
>> a1)
>>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd.
>> RTS522A PCI Express Card Reader (rev 01)
>>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>> (rev 03)
>>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.04
>>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>>   Uname: Linux 5.4.0-47-generic x86_64
>>   ApportVersion: 2.20.11-0ubuntu27.8
>>   Architecture: amd64
>>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
>> '/dev/snd/timer'] failed with exit code 1:
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sat Sep 19 19:24:38 2020
>>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
>> (20200731)
>>   PackageArchitecture: all
>>   SourcePackage: alsa-driver
>>   Symptom: audio
>>   Title: PCI/internal sound card not detected
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>   dmi.bios.date: 02/13/2020
>>   dmi.bios.vendor: Insyd

Re: [Bug 1896349] Re: PCI/internal sound card not detected

[Fernando Marcel Tarantino Martins]

Hi, Mr. Wang.

I don't know how but in the next day it just worked normally.

Thank you anyways! :)

On Mon, Sep 21, 2020 at 12:30 AM Hui Wang <1896...@bugs.launchpad.net>
wrote:

> Please test this: https://bugs.launchpad.net/ubuntu/+source/linux-
> firmware/+bug/1892714/comments/46
> 
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896349
>
> Title:
>   PCI/internal sound card not detected
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   Description:  Ubuntu 20.04.1 LTS
>   Release:  20.04
>
>   I can select my default audio hardware
>
>   When I test it, doesn't work.
>
>   When watching a Youtube video, for example, audio doesn't work as
>   well.
>
>   Thru the command lspci, this shows up:
>
>   00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
>   00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics
> G7 (rev 07)
>   00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev
> 03)
>   00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB
> Controller (rev 03)
>   00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
> Controller (rev 30)
>   00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
>   00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i
> 160MHz Wireless Network Adapter (201NGW) (rev 30)
>   00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #0 (rev 30)
>   00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP
> Serial IO I2C Controller #1 (rev 30)
>   00:16.0 Communication controller: Intel Corporation Management Engine
> Interface (rev 30)
>   00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA
> Controller [RAID mode] (rev 30)
>   00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #5 (rev 30)
>   00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port
> #9 (rev 30)
>   00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
>   00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
>   00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
>   00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound
> Technology Audio Controller (rev 30)
>   00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
>   00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
> Controller (rev 30)
>   01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
>   02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A
> PCI Express Card Reader (rev 01)
>   03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
> (rev 03)
>   04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
>   Uname: Linux 5.4.0-47-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.8
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Sep 19 19:24:38 2020
>   InstallationDate: Installed on 2020-09-19 (0 days ago)
>   InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
> (20200731)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Title: PCI/internal sound card not detected
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/13/2020
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.04
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 875C
>   dmi.board.vendor: HP
>   dmi.board.version: 10.23
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
>   dmi.product.family: 103C_5335KV HP Envy
>   dmi.product.name: HP ENVY Laptop 17m-cg0xxx
>   dmi.product.sku: 9XM78UA#ABA
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896349

Title:
  PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896349/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1896349] [NEW] PCI/internal sound card not detected

[Fernando Marcel Tarantino Martins]

Public bug reported:

Description:Ubuntu 20.04.1 LTS
Release:20.04

I can select my default audio hardware

When I test it, doesn't work.

When watching a Youtube video, for example, audio doesn't work as well.

Thru the command lspci, this shows up:

00:00.0 Host bridge: Intel Corporation Device 8a12 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G7 (rev 
07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:0d.0 USB controller: Intel Corporation Ice Lake Thunderbolt 3 USB Controller 
(rev 03)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host 
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
00:14.3 Network controller: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz 
Wireless Network Adapter (201NGW) (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO 
I2C Controller #1 (rev 30)
00:16.0 Communication controller: Intel Corporation Management Engine Interface 
(rev 30)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 30)
00:1c.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #5 (rev 
30)
00:1d.0 PCI bridge: Intel Corporation Ice Lake-LP PCI Express Root Port #9 (rev 
30)
00:1d.4 PCI bridge: Intel Corporation Device 34b4 (rev 30)
00:1d.6 PCI bridge: Intel Corporation Device 34b6 (rev 30)
00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
00:1f.3 Multimedia audio controller: Intel Corporation Smart Sound Technology 
Audio Controller (rev 30)
00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI 
Controller (rev 30)
01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX330] (rev a1)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI 
Express Card Reader (rev 01)
03:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03)
04:00.0 Non-Volatile memory controller: Intel Corporation Device 0975

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 19 19:24:38 2020
InstallationDate: Installed on 2020-09-19 (0 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/13/2020
dmi.bios.vendor: Insyde
dmi.bios.version: F.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 875C
dmi.board.vendor: HP
dmi.board.version: 10.23
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd02/13/2020:svnHP:pnHPENVYLaptop17m-cg0xxx:pvrType1ProductConfigId:rvnHP:rn875C:rvr10.23:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY Laptop 17m-cg0xxx
dmi.product.sku: 9XM78UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896349

Title:
  PCI/internal sound card not detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1896349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

I had to delete the mainstream kernel as I was having a horrible screen
tearing (my graphic card was not supported).

I left the kernel parameter "dyndbg='file drivers/input/mouse/* +p'"
and, although the issue still exists, it reduces the frequency of times
I need to use the "modprobe" workaround.

Any news?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891202] [NEW] Multipathd hangs with long iscsi target names in Ubuntu 18.04

[Fernando Ferraz]

Public bug reported:

I've notice recently that multipathd started hanging when trying to
handle long iscsi target names. In my case these targets are generated
by the OpenStack cinder driver for SolidFire.

My guess is that the problem is occurring due to a bug introduced in
multipath-tools 0.7.4, by commit "limbultipath: prefer RDAC checker with
detect_checker*"*[1].

This change adds a routine to check RDAC compatibility during the
detect_checker procedure, which runs into an infinite loop in the piece
of code that tries to gather SCSI VPD pages larger than 254 bytes (this
is my case due to long iSCSI Target names).

This issue was later addressed by several commits in 0.7.5 and 0.7.6:
"libmultipath: sgio_get_vpd: add page argument" [2], "libmultipath: Fix
sgio_get_vpd()" [3], "libmultipath: fix return code of sgio_get_vpd()"
[4], "libmultipath: get_vpd_sgio: support VPD 0xc9" [5].

I've found a temporary work around for this by using select_checker =
“no” in Ubuntu 18. This appears to avoid the problem by skipping RDAC
compatibility check code.

Also, I've also tested 0.8.3 in a RH environment and found no issues
running default select_checker = “yes” (Ubuntu 20 also delivers 0.8.3).
‌


So, in short:

- Looks like Ubuntu multipath-tools is broken, 
- There is a fix in newer versions that aren’t in the ubuntu 18 repo yet. 
- The OpenStack Cinder driver for Solidfire just happen to hit this bug because 
of the long names
- Setting select_checker = “no” is an possible work-around until Ubuntu 
publishes 0.7.6

Bellow "multipath -r -v3" output from my env:

:/$ cat /etc/multipath.conf

devices { 
device { 
vendor "SolidFir" product "SSD SAN" detect_checker "no" 
} 
}

:/$ sudo multipath -r -v3 Jul 09 19:06:24 | loading
//lib/multipath/libchecktur.so checker Jul 09 19:06:24 | loading
//lib/multipath/libprioconst.so prioritizer Jul 09 19:06:24 | vda:
blacklisted, udev property missing Jul 09 19:06:24 | sda: udev property
ID_WWN whitelisted Jul 09 19:06:24 | sda: mask = 0x1f Jul 09 19:06:24 |
sda: dev_t = 8:0 Jul 09 19:06:24 | sda: size = 10485760 Jul 09 19:06:24
| sda: vendor = SolidFir Jul 09 19:06:24 | sda: product = SSD SAN Jul 09
19:06:24 | sda: rev = 0001 Jul 09 19:06:24 | sda: h:b:t:l = 2:0:0:0 Jul
09 19:06:24 | sda: tgt_node_name = iqn.2010-01.com.solidfire:xpsi.uuid-
7b8a927e-4dbc-4a2b-b47a-1bde324895eb.53 Jul 09 19:06:24 | sda: path
state = running Jul 09 19:06:24 | sda: 1018 cyl, 166 heads, 62
sectors/track, start at 0 Jul 09 19:06:24 | sda: serial =
787073690035f47acc01 Jul 09 19:06:24 | sda: get_state Jul 09
19:06:24 | sda: detect_checker = no (setting: storage device
configuration) Jul 09 19:06:24 | sda: path_checker = tur (setting:
multipath internal) Jul 09 19:06:24 | sda: checker timeout = 30 s
(setting: multipath internal) Jul 09 19:06:24 | sda: tur state = up Jul
09 19:06:24 | sda: uid_attribute = ID_SERIAL (setting: multipath
internal) Jul 09 19:06:24 | sda: uid = 36f47acc1787073690035
(udev) Jul 09 19:06:24 | sda: detect_prio = yes (setting: multipath
internal) Jul 09 19:06:24 | sda: prio = const (setting: multipath
internal) Jul 09 19:06:24 | sda: prio args = "" (setting: multipath
internal) Jul 09 19:06:24 | sda: const prio = 1 Jul 09 19:06:24 | loop0:
blacklisted, udev property missing Jul 09 19:06:24 | loop1: blacklisted,
udev property missing Jul 09 19:06:24 | loop2: blacklisted, udev
property missing Jul 09 19:06:24 | loop3: blacklisted, udev property
missing Jul 09 19:06:24 | loop4: blacklisted, udev property missing Jul
09 19:06:24 | loop5: blacklisted, udev property missing Jul 09 19:06:24
| loop6: blacklisted, udev property missing Jul 09 19:06:24 | loop7:
blacklisted, udev property missing = paths list = uuid hcil dev
dev_t pri dm_st chk_st vend/prod 36f47acc1787073690035
2:0:0:0 sda 8:0 1 undef undef SolidFir, Jul 09 19:06:24 | libdevmapper
version 1.02.145 (2017-11-03) Jul 09 19:06:24 | DM multipath kernel
driver v1.13.0 Jul 09 19:06:24 | sda: udev property ID_WWN whitelisted
Jul 09 19:06:24 | sda: (SolidFir:SSD SAN) vendor/product blacklisted Jul
09 19:06:24 | sda: orphan path, wwid blacklisted Jul 09 19:06:24 | const
prioritizer refcount 1 Jul 09 19:06:24 | tur checker refcount 1 Jul 09
19:06:24 | unloading const prioritizer Jul 09 19:06:24 | unloading tur
checker

[1]https://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=84e16fbdb6648e685b65781d6ef0742469bd4b18

[2]https://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=d74a79f3590f3f28d34287b64c565fd5bf9705d0

[3]https://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=1f401b69e478b35d4b54b1980be67943c6d61d9f

[4]https://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=c6140952d1b682261c07cdb7138c944ee83d8809

[5]https://git.opensvc.com/gitweb.cgi?p=multipath-
tools/.git;a=commit;h=9d0e6bffbb3e490e92cf91444cfeb4177d540707

** Affects: multipath-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You 

[Bug 1860851] Re: blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8e in position 4: invalid start byte

[Fernando Racca]

Reproduced on Ubuntu 20.04 when using my Sony WH-1000XM3 headsets

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851

Title:
  blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
  decode byte 0x8e in position 4: invalid start byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1860851/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Is there anything else I can do?
I know Lenovo has an ubuntu forum, but hey are not very responsive...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392822/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

I suspended my laptop during the night; when I logged in again, the
touchpad worked for a while, but eventually got back as a generic mouse
(still mainline kernel).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

So, with my usual kernel version, 5.4.0.40-generic, adding that line
(exactly as it was written, including spaces, " and ' ) during boot ('e'
-editing the grub), the touchpad works, but after the laptop goes idle
or the screen is locked, it goes back as a generic mouse.

The trick of disconnecting and connecting it back with ```modprobe
psmouse``` keeps working though...

I am trying it now with the latest version of the kernel
5.8.0-050800-generic.

The touchpad works from start. I have locked the screen and it keeps
working after logging in.

Even better, all the multi-finger movements work as well ( I had fusuma,
but 4 finger vertical swipe never worked; now, it is working).

I can't say yet that it has been fixed, but definitely we're on the
right track!

Please let me know if I can do anything else to help you debug this
thing.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

It was working for a while, but after the laptop goes idle or the screen
is locked, the touchpad goes back as a generic mouse; the trick of
disconnecting and connecting it back with ```modprobe psmouse``` keeps
working though...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

It is using oem2.inf

I add the line at boot, by editing the grub and adding it at the end of
the line which starts with 'linux', and I don't want to get to excited,
but so far, so good...

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392309/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Sorry, I uninstalled the updated kernel; should I install it again?

Where do I configure that line? during boot?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

** Attachment added: "deviceManager"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392298/+files/deviceManager_0.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

** Attachment added: "deviceManager_3.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392301/+files/deviceManager_3.png

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

** Attachment added: "deviceManager_2"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392300/+files/deviceManager_2.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

** Attachment added: "deviceManager_1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+attachment/5392299/+files/deviceManager_1.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1553687] Re: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0'

[Fernando]

Looks like this one is dying...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553687

Title:
  Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to
  'hd0'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1553687/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Just tried it this afternoon.

The issue is not fixed; I'm not seeing any difference...

I'm still using the new kernel (5.8.0-050800-generic); Should I delete
it?

Any other test?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882388] Re: Touchpad recognised as generic mouse

[Fernando]

Thanks for that.

I have a nVidia GeForce GTX 960M graphic card.

I am using proprietary drivers; I didn't need to do anything, it was
automatically installed when I first installed Ubuntu 20.04.

I've read on the page you sent me before, that I need to remove the
nVidia drivers before installing the new kernel.

Is that really necessary? They really insist on that point.

If so, how do I remove them and installing them back? I am looking for
answers in 'Ask Ubuntu', but as I didn't download the drivers and it was
automatic, I don't know how to do it.

Sorry, I'm a noob and I'm really scared of messing up with the system
as, although I have dual boot with Windows, I already have migrated
plenty of stuff and I don't want to have to re-install everything
back...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882388

Title:
  Touchpad recognised as generic mouse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs